DC not on network still in Domain

[snapster]

Hi,

I have a domain controller that has not been connected to the network for a few months but it is still in Active Directory as a domain controller and I want to remove it completely.

Should I connect it to the network and run dcpromo? (I don't know what might happen as it has been so long since it spoke to the other domain controllers)

Or should I remove it manually from Active Directory?

Any help is appreciated.

Regards

Snaps.

[nitroshift]

I assume you already have another domain controller in-place. If so, you can safely delete the old one in the AD.

[valter]

Better connect it and demote it properly, as when just DELETE it from AD, there is many referenes left in AD towards that DC...

[snapster]

So you don't think there will be any Active Directory replication issues if it is connected to the domain again?

Snaps.

[Zartach]

Replication works with version numbers, the online DC's have a higher number so no 'old' data will ever overwrite the 'new' data.

the old dc would be treated as it would have when there was no data on it, the thing has nothing to add to the ad since its version number is too low. It would actualy grab replication from the other dc's and overwrite its own 'old' data.

[snapster]

OK, I will switch it back on next week and then run dcpromo. I'll let you know how it goes.

Thanks for all your help.

Snaps.