Another significant thing to consider is the Network Location Server (NLS), which allows your clients to know they are connected directly to the corporate network, when the user is in the office. The clients look for the NLS server by name, and try to connect to it to make this determination. With remote offices or sites, you will need to place a network location server in each site so that local clients have their own NLS rather than going through the WAN to other offices.
When you configure URA, you need to provide the name for the network location server, and the same name will be used by all URA clients everywhere, to connect to one of the multiple servers that will be set up by the wizard. Since the NLS servers in all the sites will answer to the same name, you need to set up your DNS name resolution appropriately, so that in each site, it will resolve to the IP of the local NLS:
The multiple servers will also need to have certificates for this, and...