2 Windows Servers - 2 Locations
Hello all !
I have a Windows 2000 Server, with Exchange 2000, operating in location A as a Domain Controller. Location A is head office with 15 Users.
The firm are opening a new branch office in Location B with 5 new users. A Windows 2003 Server is proposed for the new office to act as file and print server.
The 2 locations are linked via VPN over broadband. This is in place already and has been tested. Each location has it's own different IP range within the private address ranges.
My question lies with the new 2003 Server in location B. My primary concern is that users in Location B should have access to Exchange in Location A. Also all users should be able to access files on server in either location.
How should the new server be configured in order to best achieve these requirements?
Thanks
I have a Windows 2000 Server, with Exchange 2000, operating in location A as a Domain Controller. Location A is head office with 15 Users.
The firm are opening a new branch office in Location B with 5 new users. A Windows 2003 Server is proposed for the new office to act as file and print server.
The 2 locations are linked via VPN over broadband. This is in place already and has been tested. Each location has it's own different IP range within the private address ranges.
My question lies with the new 2003 Server in location B. My primary concern is that users in Location B should have access to Exchange in Location A. Also all users should be able to access files on server in either location.
How should the new server be configured in order to best achieve these requirements?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
FYI - When mapping a drive to DFS do not specifiy the name of the server hosting it but use the domain name like this
net use g: \\domainname.local\dfs_Nam
not like this:
net use g: \\servername\dfs_sharename
net use g: \\domainname.local\dfs_Nam
not like this:
net use g: \\servername\dfs_sharename
ASKER
That's fantastic guys... exactly what I need to know, I will be configuring the server early next week and come back if I have any queries.
Cheers,
Peter
Cheers,
Peter
ASKER
On reflection, a couple more Q's on this one...
Forgive me if I'm making this very simplistic, but would the process go as follows:
1. Configure the new server physically at Location A
2. Join it to the domain at Location A
3. Configure AD Sites and Services
4. Move the new server into the new site within Sites and Services
5. Ensure Server is a Global Catalog Server
5. Physically bring server to Location B
6. Configure DNS and DHCP appropriately
Will it cause problems if the existing server at location A is already a Global Catalog Server?
Thanks
Forgive me if I'm making this very simplistic, but would the process go as follows:
1. Configure the new server physically at Location A
2. Join it to the domain at Location A
3. Configure AD Sites and Services
4. Move the new server into the new site within Sites and Services
5. Ensure Server is a Global Catalog Server
5. Physically bring server to Location B
6. Configure DNS and DHCP appropriately
Will it cause problems if the existing server at location A is already a Global Catalog Server?
Thanks
For simplicity I would dcpromo it at the new branch, I would even suggest joining it to the domain on its correct IP address. It is quite possible to do it the other way but I think you will find it easier without having to deal with possible wrong entries in dns against the temporary IP.
Suggest build it where you are, enable rdp, change its IP to correct for the other site and have it connected to the lan then you can finish it off over the wan usinf rdp.
Suggest build it where you are, enable rdp, change its IP to correct for the other site and have it connected to the lan then you can finish it off over the wan usinf rdp.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
sorry dragon...it's like I you were reading my mind
Just the best way to do it eh!
ASKER
Hello Guys...
Server went in over the weekend and all went well. Had a couple of hiccups but process went as you suggested but before I could promote the server, I had to run 'adprep' on the forest and domain from the Location A Windows 2000 Server. Also had to apply InetOrgPersonfix, but once the preparation work was done, the promotion went without problems.
So thanks for your help and going to split the points between mcsween and dragon-it
Thanks!
Server went in over the weekend and all went well. Had a couple of hiccups but process went as you suggested but before I could promote the server, I had to run 'adprep' on the forest and domain from the Location A Windows 2000 Server. Also had to apply InetOrgPersonfix, but once the preparation work was done, the promotion went without problems.
So thanks for your help and going to split the points between mcsween and dragon-it
Thanks!
Good point, sorry had missed the '2000 as existing DC, new one is 2003...". Thanks for the points.
Steve
Steve
1. On the Server at Location A set the primary DNS to itself with a secondary pointing at the DNS server at Location B.
2. On the Server at Location B set the primary DNS to DNS at Location A and secondary to itself.
3. Dragon-it said this but make sure Loc B ADC is a Global catalog
4. Setup an AD Integrated DFS Root and publish the shares from both file servers to it. This will allow users to get files off each server from only 1 mapped drive. DFS root should be hosted from the File server at Site A.