David Shen,
Can you please clarify this instruction?
"And it is recommended that we use administrator credential of source domain
to logon the target domain from source domain controller."
To me, that reads: While connected to or sitting at source domain
controller, at the logon prompt, enter a username and password from the
source domain, but the log on to field should be target domain. If this is
correct, I am confused as to how source domain credentials can logon to a
target domain. I am able to logon to a target DC with source credentials but
the log on to field says sourcedomain.
I am going through a similar project as poster vdz did almost a year ago
where I am consolidating an external Windows Server 2003 forest of an
acquired company
into our Windows Server 2003 forest. In addition to the clarification
requested above I do have one more question if I may post it here.
We have two physical sites, one here in the US and newly acquired company
site is outside US. Outside US site is source domain. Connectivity exists
between the two. In our situation, source domain controller also servers as
their only DHCP and DNS server. I intend to install a second Windows Server
2003 server at their site, join it to the target domain, and promote it to a
domain controller. This new target domain controller will need to become THE
only DHCP and DNS server for their site only. In other words, I don't want
their DHCP server leasing addresses to our site here. What is the correct
procedure for standing up a new DHCP and DNS server in the target domain?
How can I ensure that after successful migrations, clients at remote site get
the correct DNS settings from the new DHCP server?
I apologize in advance if any of this was confusing. Any help would be
appreciated.
|
Similar Threads
Linear Mode
