Uninstalling a defunct Exchange server from Active Directory

[CyberNerd]

2 x Windows 2003 Active Directory servers.
1 old Exchange server.

I have completed the following steps:

removed old mailboxes
made sure MSexchHomeServerName is not set for any accounts
run setup /removeorg
run setup /domainprep
uninstalled Exchange from the server.
shut down old exchange server

however - I'm still seeing the server in "Sites and Services" and the msexchange schema still seems to be visible in adsiedit.....
how do I remove it?

[CyberNerd]

^ Bump

[SYNACK]

Did you run DCpromo to demote the old server from being a domain controler and with exchange you will need to remove the organisation:
http://trycatch.be/blogs/ddv/archive...anization.aspx

[CyberNerd]

I assumed that was part of the exchange setup, so I only followed that. I'll see if it allows me to dcpromo it.

[timzim]

Is it Exchange 2003? Did you replace/upgrade it?

[CyberNerd]

Is it Exchange 2003? Did you replace/upgrade it?

Yes 2003. We upgraded it to Google apps, the server is no longer needed as an internal mail (generated by devices) goes through a postfix relay.

[CyberNerd]

Did you run DCpromo to demote the old server from being a domain controler and with exchange you will need to remove the organisation:
How to

I already removed the organisation using "setup /removeorg" before I uninstalled exchange. It completed successfully.
The problem seems to be that it still exists in AD.
I tried DCPROMO, but it only wants to install a new DC - so I guess the server knows it is's not a DC/exchange, but the domain doesn't.

[Domino]

Had to go through this myself recently... How to remove data in Active Directory after an unsuccessful domain controller demotion

[CyberNerd]

Had to go through this myself recently... How to remove data in Active Directory after an unsuccessful domain controller demotion

Joyous. I'll probably fall asleep halfway through doing that. Job for tomorrow.
Thanks though.

[Domino]

It actually doesn't take too long - just make sure you do it methodically and step by step.

Good Luck!

[CyberNerd]

Reading the instructions, I think I've been here before - a few years back.

[CyberNerd]

I gave it a go; but just to add to my confusion the exchange server isn't listed as a DC in ntdsutil or under OU=domain controllers in adsiedit !

but it still appears as a server in "active Directory sites and services" and there are exchange system objects visible in adsiedit !

any other ideas?

[SYNACK]

Is it listed under the domain controllers OU, if not then it is not a DC anymore. Sometimes the AD connectors in AD sites and services are not cleaned up especially if they were added manually and so you just need to delete them manually. Did not see that you had run the exchange org removal but if so I would not worry about the stuff in AD unless you are planning on reinstalling Exchange 2003 at some point.

[CyberNerd]

Is it listed under the domain controllers OU, if not then it is not a DC anymore. Sometimes the AD connectors in AD sites and services are not cleaned up especially if they were added manually and so you just need to delete them manually.

It's definitely not a Domain Controller. Ok. I'll just delete it then.
What about all the schema changes in the active directory? theres a bunch of exchange related stuff. I guess it's ok to just leave it?

Did not see that you had run the exchange org removal but if so I would not worry about the stuff in AD unless you are planning on reinstalling Exchange 2003 at some point.

Sorry, I only edited the post after you said to run it. I did do it but forgot to mention in the first post.

[SYNACK]

It's definitely not a Domain Controller. Ok. I'll just delete it then.
What about all the schema changes in the active directory? theres a bunch of exchange related stuff. I guess it's ok to just leave it?

Schema mods are one way so the additional attributes are there to stay, thats why there are so many warnings about customizing the schema as there is no going back because the potential for dataloss or corruption is too high (When scaled out to possibly - depending on the environment - thousands of servers via replication). I'm sure there are ways to force it but nothing that you would want to do in production. It will be fine and the standard practice, just leaving it is the only avalible option anyhow short of a domain migration to a fresh forrest.

Sorry, I only edited the post after you said to run it. I did do it but forgot to mention in the first post.

Cool, I'm glad I didn't missread or forget it.