Member_2_4384294
asked on
one domain, two sites
I am setting up a branch office in a different location to the main but using the same domain. I realise this is a common scenario but am looking for the basic principles to follow in designing the server topography.
Main office is 120 users and hosts the Exchange server. Branch office is just 15 users. Offices have separate subnets but are joined by VPN. Limited file sharing will be required. Branch office users will access the Exchange server.
At this point I believe a read only DC, DNS and DHCP (for this subnet) are required in branch office. Is this the correct?
We use roaming profiles in the mail office. I can set the location to store the branch office users' profiles individually group policy to configure the location of redirected desktops and documents folders, is this the best method?
Do I use DFS for the file-shares to keep copies at both offices?
Main office is Server 2008R2, branch is server 2012. Are there any compatibility issues?
Any other considerations I should be aware of?
Thanks for input.
Main office is 120 users and hosts the Exchange server. Branch office is just 15 users. Offices have separate subnets but are joined by VPN. Limited file sharing will be required. Branch office users will access the Exchange server.
At this point I believe a read only DC, DNS and DHCP (for this subnet) are required in branch office. Is this the correct?
We use roaming profiles in the mail office. I can set the location to store the branch office users' profiles individually group policy to configure the location of redirected desktops and documents folders, is this the best method?
Do I use DFS for the file-shares to keep copies at both offices?
Main office is Server 2008R2, branch is server 2012. Are there any compatibility issues?
Any other considerations I should be aware of?
Thanks for input.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Went for the roaming profiles as people don't move between offices much .
roaming profiles can create at additional domain controller for their local users so bandwidth consumption will be reduced... sharing is not an issue...
All the best