DCPromo

[Mark McCurdy]

I'm upgrading one of my DC's tonight to faster server. Here is my plan and
does anyone see any foreseeable problems?

1. Remove the Global Catalog. (It is running on a second DC as well)
2. Run the DCPromo wizard so that it de-promotes the old box.
3. Delete the machine name from the domain.
4. Join the new box to the domain with the SAME name and SAME IP.
5. DCPromo it.
6. Reapply Global Catalog.

Of course I will allow plenty of time between each of the steps so
replication can take place. Does that look like a good plan?

Thanks for you help,
Mark

 

[Simon Geary]

Step 1 is unnecessary. So long as you properly dcpromo the server down to a
member server you don't have to manually remove the GC although step 6 would
still have to be done. Looks like a good plan otherwise.

 

[I.is.Who.I.am]

Question - would it be necessary to check the roles on this machine and make
sure it is not the PDC or Schema Master etc. before dcpromo???

 

[Diane McCorkle]

With a graceful and healthy dcpromo down the roles should be handed off to
other DC's

I prefer to move the roles off manually myself before, but the dcpromo down
should do it.

Diane


Question - would it be necessary to check the roles on this machine and make
sure it is not the PDC or Schema Master etc. before dcpromo???

 

[Enkidu]

I'm upgrading one of my DC's tonight to faster server. Here is my plan and
does anyone see any foreseeable problems?

1. Remove the Global Catalog. (It is running on a second DC as well)
2. Run the DCPromo wizard so that it de-promotes the old box.
3. Delete the machine name from the domain.
4. Join the new box to the domain with the SAME name and SAME IP.
5. DCPromo it.
6. Reapply Global Catalog.

Of course I will allow plenty of time between each of the steps so
replication can take place. Does that look like a good plan?

Just wondering. There's probably a good reason for using the old name
and IP in your case, but sometimes it's easier to use a new name and
IP. That way you can be sure that any references to the old machine
and IP are bogus.

Cheers,

Cliff

 

[Darren D]

I concur with Diane, I perfer move the fsmo's manually..
I did this in my exchange2000 forest enviroment , and it work like a charm

Hope this Helps
Darren

 

[Cary Shultz [A.D. MVP]]

Correct. And make sure that you give AD enough time to replicate the
removal of "old name / old IP" to all other DCs ( looks like there are only
two currently ) and then make sure to clean things up well before using the
old name / old IP.

As Cliff suggested, using the old name / old IP more often than not ends up
creating problems with AD replication and the like as the admin doing this
procedure did not give AD enough time to replicate things and then go in
behind that and clean thing sup - if necessary ( and it usually is a little
bit ).

HTH,

Cary