Question : Best practice. Multisite, single domain?

We are setting up a regional office, to be linked to tour main site by VPN. All remote traffic will be sent down the tunnel (so we can use our websense proxy) This is up and running fine.

We have build a DC for the remote site, and created a separate site for it in AD sites and services with a site link between the two. This is to enable logons and file access (dfs) in the event of a network outage.

It has been recommended that we set up a sub domain for the remote site. Is this necessary?

Is there anything else that we need to do? Our single exchange server is on our main site, we have added it to sites and services.

Answer : Best practice. Multisite, single domain?

There is no need for a sub domain - the situation described is what sites are for.

As you have a DC in the remote site it would be a good idea to make sure that this is also a DNS server and Global Catalog. Clients in the remote site could then be set to use this as their preferred DNS server keeping DNS queries local.

If you have set up subnets and Sites in AD sites and services machines on the remote site will use the local DC in preference for authentication