Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 417
  • Last Modified:

AD replication tombstone - exchange query

We have had a replication failure and the server in question has gone into stand alone mode.  i have searched these pages and the received wisdom is to demote the server, clear off any reference to the AD on it (plus the primary DC) and then re-promote and start replication.

this is fine.  however - the server in question is also our exchange server for that site, and i would appreciate some reassurance that doing what i have outlined above wont interfer with exchange operations?

Its a windows 2003 server with exchnage 2003 on it as well.
Many thanks in advance

alex
0
Brookdaleal
Asked:
Brookdaleal
  • 3
  • 2
1 Solution
 
Redwulf__53Commented:
You don't have any choice...
Your Exchange services should survive the operation.
Well, since it is never recommended to combine AD and Exchange (and now you know why), you might consider adding a new server as domain controller after you demote the Exchange server, instead of promoting it again.
0
 
BrookdalealAuthor Commented:
thanks for the quick reply!  
If i demoted this server, it would leave the Primary domain controller on that site (called server A) and this server as a member server, and third member server running SQL (server C)
would you suggest promoting serve C or could we just leave the PDC (server A) on its own?
i guess the risk is that if the PDC goes down, there's no-one else around to run the shop?

thanks!
alex
0
 
Redwulf__53Commented:
Thinking about it a bit more, you may run into a couple of problems.
I suggest following this method for safest result:
-Disconnect the Exchange box from the network
-Make sure server A holds all FSMO roles (seize the roles if necessery)
-On server A: in AD Users& Computers, move the server B account to the Computers OU, and remove the membership from the "Domain Controllers" Group.
-On server A: in AD Sites And Services, remove all references to Server B
-On server A: in DNS, remove all records referring to server B
-Do not delete the computer account from AD, as Exchange server is linked to that account!
-Stop all Exchange services and set startup type to "disabled"
-Run DCPromo, and mark the server as last domain controller in the domain.
-Restart. The server will now be stand-alone
-Reconnect the server to the network, and make it member of the domain (again). It should now reconnect to its still existing account in AD, so it's exchange server group memberships should still be intact.
-Start the Exchange services.

Good luck!

PS about redundancy: combining AD with SQL may also not be a good idea... especially if you need high availability of either... ultimately it's your own choice, but now you've experienced it's not a good idea to combine roles, you may convince your managers to invest in another Windows license. If you virtualize it, the additional hardware cost would be minimal.

0
 
BrookdalealAuthor Commented:
thanks for the pointers!

i dont plan to do this until either tomorrow night or the weekend when people are off line... whats the EE protocol on closing this question before testing out... can i leave open for a few days in case i have further questions?
thanks
alex
0
 
BrookdalealAuthor Commented:
there were some really useful caveats here - and some good general advice about server setup.  thanks for the help!
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now