How to de-commission a CC3 replica domain controller

[morganw]

RM do supply a TEC article on how to do this (TEC1433990) but i'm not entitled to look at it.

I'm not looking to do this immediately, just wanting to see what is involved. I'm assuming all the Server 2003 guides still have to followed as per technet articles (Decommissioning a Domain Controller: Active Directory) but am I going to run into problems with it still being listed in RM configuration files or is everything based on Active Directory?

[mb2k01]

I'm not sure on the RM side of things, but do you know what AD functionality and FSMO roles are held by the server? Are they exclusively held or all replicated elsewhere?

 

If there are no unique roles I'd be tempted to shutdown the server at a planned time and test the normal server / AD stuff - replication etc.

[mtdmitchell]

I decomisioned 4 rm cc3 servers in the summer, didnt bother to read the Tech Article. I demoted and formatted two servers and installed 2003, transfered the roles and then did the other two. Easy

 

As long as you have other dc's . then just transfer the roles

[Theblacksheep]

Done alot of this lately! If its still an active server....

 

1) get a backup

2) remove important cc3 services and information

3) remove ad (dc promo) and restart

4) uninstall DNS

5) update DHCP scope taking out the cc3 server you just removed.

6) remove from domain, put in a workgroup and reboot

7) remove server from AD and DNS

[morganw]

Thanks for the info...

 

All of the FSMO roles are on the PDC, it is a global catalogue server but there are 3 others.

So hopefully AD should come off gracefully, there may be a slight issue though, when running dcdiag i get:

 

The DS has corrupt data: rIDPreviousAllocationPool value is not valid

No rids allocated -- please check eventlog.

......................... SERVER-NAME failed test RidManager

 

Eventlog is full of SAM errors (ID:16650)

The account-identifier allocator failed to initialize properly. The record data contains the NT error code that caused the failure. Windows 2000 will retry the initialization until it succeeds; until that time, account creation will be denied on this Domain Controller. Please look for other SAM event logs that may indicate the exact reason for the failure.

 

I've had an RM technician remotely try to fix this about 6 months ago, in the end he just said it wouldn't cause any issues and it was safer to leave it than do something drastic to try and fix it. It started to happen after the server virus protection went wrong and filled the C drive with virus defintions, had to restore AD from a backup using directory restore mode. Since RID pools seem to be operating properly on the other 3 servers I'm hoping this won't be an issue, but as it leaves AD is this server going to attempt to release it's RID pool, see an invalid value, and fail?

[Tallwood_6]

I have the instructions RM send me on how to remove a CC3 replica DC i will PM you them on Monday. Its quite straightforward there isnt alot RM specfic stuff that needs to be removed or modified if i remember rightly.

[morganw]

That would be ideal!

Thank you.

[bs239654]

Hi sorry if this is digging up an old post but im in the same situation and need to demote 3 rm servers .. do you still have the instructions on how to do this? please:>

[Tallwood_6]

PM Sent

[jamiesev]

Hi could you please also PM me with the details?

 

thank you!

[richbrowncardiff]

Hi Sorry if you still have details could you pm me with them please ? i have 3 RM cc3 DC's and am slowly getting rid of them. this will be the first of the 3 to go.

 

Many thanks in advance