Am I missing a step?

  • Thread starter Thread starter Jeremy Schafer
  • Start date Start date
J

Jeremy Schafer

I plan to migrate my only DC (DC1) to another (DC2) and then to another
DC with DC1's name (DC1-a). From this group and various websites, I
think I have gathered enough information that I need. I just wanted to
bounce it off this group to see if there is anything I missed.

I need to keep my main dc as the same name because I have printers being
shared off of there. Shares are pointing there (dont have DFS up and
working yet) and a slew of other services (GPOs, WINS).

Here are the services running on DC1:
printing, file sharing, DNS, AD, RIS, IAS, and WINS.

I have already brought up DC2. It is a global catalog server and has
been for at least 3 days. I have run dcdiag and netdiag with no errors.

[This all plans to be done with no users logged on.]
My plan was to change the FSMO roles to DC2. Bring DC1 off-line. Then
bring DC1a with DC1's name and finish configuring the services. Finally,
I was going to move the FSMO roles to DC1a.

Is there anything I forgot? Am I making this harder than it has to be?
Will DNS be fine as long as a transfer over the zone files?

Thanks in advance for everyone's help. I am learning as I am going and
appreciate the help.
 
Jeremy said:
I plan to migrate my only DC (DC1) to another (DC2) and then to another
DC with DC1's name (DC1-a). From this group and various websites, I
think I have gathered enough information that I need. I just wanted to
bounce it off this group to see if there is anything I missed.

I need to keep my main dc as the same name because I have printers being
shared off of there. Shares are pointing there (dont have DFS up and
working yet) and a slew of other services (GPOs, WINS).
Click to expand...


Printers can be migrated from one server to another with some tools or
scripts and user configuration (printer mappings) can be changed adter
this migration with login scripts assigned at the domain level so
printer mapping is not a problem with migration to the new server name.

Using catalog objects to map a printer instead UNC path (as I think You
are doing in Your network) can save You some work also.
Here are the services running on DC1:
printing, file sharing, DNS, AD, RIS, IAS, and WINS.

I have already brought up DC2. It is a global catalog server and has
been for at least 3 days. I have run dcdiag and netdiag with no errors.

[This all plans to be done with no users logged on.]
My plan was to change the FSMO roles to DC2. Bring DC1 off-line.
Click to expand...

This step "bring DC1 off-line" should be demoting DC1 from the DC role,
and then removing it from the domain (or reseting the account but i will
suggest to remove this computer from the domain and create new account)

Then
bring DC1a with DC1's name and finish configuring the services. Finally,
I was going to move the FSMO roles to DC1a.

Is there anything I forgot? Am I making this harder than it has to be?
Will DNS be fine as long as a transfer over the zone files?
Click to expand...

Zones should be transfered with AD (as far as You have AD integrated zones)
 
Back
Top