Add an HRA Server to a Trusted Server Group
Applies To: Windows Server 2008, Windows Server 2012
Adding an HRA server to a trusted server group
Using the Windows interface
Using a command line
To add an HRA server to a trusted server group by using the Windows interface
To open the NAP client configuration console, click Start, click All Programs, click Accessories, click Run, type NAPCLCFG.MSC, and click OK.
In the console tree, double-click Health Registration Settings, and then click Trusted Server Groups.
In the middle pane, double-click the name of your trusted server group.
In the trusted server group properties dialog box, type the URL of a trusted server that you want to add, and then click Add.
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 add an HRA server to a trusted server group by using a command line
To open a command prompt, click Start, click All Programs, click Accessories, and click Command Prompt.
Type: netsh nap client add server group = <group> url = <url> processingorder = <processingorder>
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 modifying. |
<url> |
Any valid URL, UNC path, or IP address. (Required) |
The HRA server that you want to add to the trusted server group. |
<processingorder> |
Any integer. Cannot be zero (0). (Optional) |
The processing priority you wish to assign to this HRA server. |
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.