Multisite Remote Access is found in the Configuration section of the Remote Access Management Console. The Enable Multisite task within Multisite Deployment in the task pane startsthe Enable Multisite Deployment Wizard, which guides you through the process of configuring Multisite Remote Access.
For deployment of Multisite Remote Access, both the Network Location Server and the IP-HTTPS server must use trusted certificates and cannot use self-signed certificates.
The Enable Multisite Deployment Wizard begins with configuration related to the multisite deployment name and the first entry point (see Figure 3-7).
FIGURE 3-7 Beginning the Enable Multisite Deployment Wizard.
The wizard’s next step enables you to choose how clients can find the best entry point:
- Assign entry points automatically and allow clients to select manually
- Assign entry points automatically only
The next step of the Enable Multisite Deployment Wizard (shown in Figure 3-8) deals with load balancing.
FIGURE 3-8 Choosing the load-balancing configuration as it relates to a multisite deployment.
Figure 3-9 shows the wizard’s Client Support pane, where you choose whether to support Windows 8 clients on the deployment or if down-level Windows 7 computers should be allowed as well.
FIGURE 3-9 Choosing the level of client support for a multisite deployment.
After you configure the initial deployment, you typically perform additional configuration, such as add another entry point. This is accomplished through the Add an Entry Point Wizard.
-------------------
NOTE: ADDING ENTRY POINTS
The Remote Access server role must be configured on the server to be added to the multisite configuration. However, Remote Access should not be configured on that new server. In other words, the Getting Started Wizard cannot have been run on the new server. If it has, the Add an Entry Point Wizard can’t get past step 1 and returns an error indicating that the new server has already been configured.
-------------------
The Add an Entry Point Wizard first gathers the name of the server to be added to the multisite deployment. After that, the network topology is gathered, followed by the name that the clients use to contact this entry point. The network adapters are configured next (see Figure 3-10). This pane enables you to choose the network adapter to be used for the entry point along with the appropriate IP-HTTPS certificate.
FIGURE 3-10 Choosing network adapter settings when adding an entry point to a multisite deployment.
Client support is next in the wizard (similar to Figure 3-9), and finally the GPO settings, which are typically left at their default settings. With that, the entry point is configured and can then be managed through the Remote Access Management Console on the server on which the multisite deployment is configured.
You can also change the settings for the multisite deployment through the Configure Multisite Settings dialog box, which provides a wizard-like interface to reconfigure many of the settings configured during initial deployment. Disabling a multisite deployment requires all the entry points to first be removed. This is accomplished within each entry point’s Configuration Summary.
However, if the entry point to be removed exists on a Remote Access server that’s currently being managed by this server, you can’t simply click Remove Entry Point. Instead, you must first select Manage a Remote Server to begin the process of removing the entry point. This is true only for Remote Access servers managed by this server, not for servers that are simply members of the multisite deployment.
