what you want is not that difficult to acchieve and by far not needed to
have two domains.
Remember that an AD domain can span multiple sites and it is not a rule to
create a domain for each site...
As I understand it you want to acchieve the following:
* DNS/WINS/DHCP services at both locations
To make things more clear let's invent some names....
Location A -> physical location A
Location B -> physical location B
Site A -> AD site for location A
Site B -> AD site for location B
DC1 -> domain controller 1 (with DNS, WINS, DHCP)
DC2 -> domain controller 2 (with DNS, WINS, DHCP)
REMARK: these names are just for this message so that things are more clear.
For location A install a fresh W2K3 server with SP1. In this case its name
will be DC1
Also install DNS, WINS and DHCP
Give DC1 it own IP address
As preferred DNS for DC1 enter the IP of DC1
As alternate DNS for DC1 enter the IP of DC2
As WINS server enter the IP of DC1
For location B install a fresh W2K3 server with SP1. In this case its name
will be DC2
Also install DNS, WINS and DHCP
Give DC2 it own IP address
As preferred DNS for DC2 enter the IP of DC2
As alternate DNS for DC2 enter the IP of DC1
As WINS server enter the IP of DC2
Promote DC1 from a stand-alone server to a DC and have it configure DNS for
you during DCPROMO.
Create a new AD forest and a new AD domain
For the DNS name of the AD domain you could choose something like
COMPANY.LOCAL (or something similar)
For the NetBIOS name of the AD domain you could choose something like
COMPANY (it is best this is the same as the most left part of the DNS name
of the AD domain)
Make the DC also a GC (afterwards)
For AD configure the following stuff:
Create a site for location A --> e.g. Site A (or rename the default one)
Create a site for location B --> e.g. Site B
Site A and Site B should be linked by the Default IP Site link (you can
rename as you wish or you can leave it as is)
Create AD subnet definitions for subnets within location A and assign those
to Site A
Create AD subnet definitions for subnets within location B and assign those
to Site B
DC1 should be in Site A
Promote DC2 from a stand-alone server to a DC and have it configure DNS for
you during DCPROMO.
Use an EXISTING forest and an EXISTING domain!!!
Make the DC also a GC (afterwards)
DC2 should be in Site B
For DNS yo are ready to go
For WINS:
* On DC1 configure DC2 as a push/pull replication partner
* On DC2 configure DC1 as a push/pull replication partner
For DHCP:
* On DC1 configure the necessary DHCP scopes for location A to distribute
IPs and DHCP options like DNS Name (e.g. COMPANY.LOCAL), like Default
Gateway, like DNS servers (1st= IP DC1 and 2nd = IP DC2), like WINS servers
(1st= IP DC1 and 2nd = IP DC2)
* On DC2 configure the necessary DHCP scopes for location B to distribute
IPs and DHCP options like DNS Name (e.g. COMPANY.LOCAL), like Default
Gateway, like DNS servers (1st= IP DC2 and 2nd = IP DC1), like WINS servers
(1st= IP DC2 and 2nd = IP DC1)
* Create a user account in AD for DHCP, just a simple user account, nothing
special. Configure DHCP to use that account for the registrations in DNS
when using DDNS
Perform additional configuration as necessary!
To prevent rebuilding this again in the future. Fully backup both servers
using a supported backup mechanism and tool! (No images!!!) If a third party
backup and restore tool is expensive just use NTBACKUP to backup to tape or
to file. If you backup to file make sure the backup are also stored on
ANOTHER server!
From the orphaned domain, migrate everything needed (users, groups,
computers, etc.) to the new domain
This should help you on your way. Good luck!
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)-->
http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)-->
http://blogs.dirteam.com/blogs/jorge/rss.aspx