Remove an HRA Server from a Trusted Server Group

Updated: March 29, 2012

Applies To: Windows Server 2008, Windows Server 2012

Removing an HRA server from a trusted server group

To remove an HRA server from a trusted server group by using the Windows interface

  1. To open the NAP client configuration console, click Start, click All Programs, click Accessories, click Run, type NAPCLCFG.MSC, and click OK.

  2. In the console tree, double-click Health Registration Settings, and then click Trusted Server Groups.

  3. In the middle pane, double-click the name of your trusted server group.

  4. In the trusted server group properties dialog box, click the URL of a trusted server that you want to remove, and then click Remove.

  5. Click OK.

Additional considerations

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.

To remove an HRA server from a trusted server group by using a command line

  1. To open a command prompt, click Start, click All Programs, click Accessories, and click Command Prompt.

  2. Type: netsh nap client delete server group = <group> url = <url>

The following table provides a guideline for the placeholder text in the Netsh command.

 

Placeholder Possible Values Description

<group>

Any text string. (Required)

The name of the trusted server group that you are changing.

<url>

Any text string. (Required)

The URL of the HRA server that you want to remove from the trusted server group.

Additional considerations

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.

Additional references

Community Additions

ADD
Show: