Changing the order of the HRA servers in a trusted server group
To change the order of the HRA servers in 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 then click OK.
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, click the URL of a trusted server that you want to move up or down in the list, and then click Move Up or Move Down.
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 change the order of the HRA servers in a trusted server group by using a command line |
To open a command prompt, click Start, click All Programs, click Accessories, and then click Command Prompt.
Type: netsh nap client set 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 URL of the HRA server that you want to move up or down in the trusted server group. |
<processingorder> |
Any integer. Cannot be zero (0). (Required) |
The processing priority 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.