Exchange 2003

Hi,

I'm trying to decommission an Exchange 2003 Server, which was the master within a particular routing Group, but all users that were on this Exchange Server have now been moved to a Central Exchange 2013 Server.  When I attempt to remove Exchange (after following the decomissing instructions) it says it is still a master within the Routing Group Connector and then won't uninstall Exchange.  When I go into System Manager and attemt to delete this server from within Members under the routing Group Connector, it just sits there and doesn't remove.

Any advice would be appreciated.

Cheers!
minniejpAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jian An LimSolutions ArchitectCommented:
if this is the last exchange 2003 server, just remove it by force

https://support.microsoft.com/en-us/kb/833396
minniejpAuthor Commented:
I had hoped to avoid removing it by force and allowing the Exchange Install to do it.  I do have one more server in the org that needs to be removed.
Ibrahim BennaTechnology LeadCommented:
How did you manage to migrate from Exchange 2003 to Exchange 2013?? (http://blogs.technet.com/b/mconeill/archive/2013/04/03/migration-from-exchange-2003-to-2013-a-no-go.aspx)
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Download eBook now!
minniejpAuthor Commented:
I moved the mailboxes to an existing Existing Exchange 2010 server.
minniejpAuthor Commented:
Apologies, it was a typo.
Ibrahim BennaTechnology LeadCommented:
Have you tried deleting the routing group connector from ADSIEdit? I would also advice against manual removal of Exchange unless as a last resort.
minniejpAuthor Commented:
I haven't, I wanted to ensure I wasn't missing something via the GUI first.  Would you mind pointing me in the right direction?
Ibrahim BennaTechnology LeadCommented:
Lets try it from a number of places first.

From your Exchange 2010, use the Exchange Powershell and run get-routinggroupconnector. It should return 2 connectors. Run "get-routinggroupconnector | Remove-RoutingGroupConnector" to delete them all.

If so try the uninstall process.
minniejpAuthor Commented:
I have removed the routing group via the Exchange 2010 server but it is still appearing on the 2003 server...
minniejpAuthor Commented:
Any futher thoughts?
Ibrahim BennaTechnology LeadCommented:
I guess next option  is to remove it through ADSIEdit. I will check the exact path and post later or tomorrow.
minniejpAuthor Commented:
cheers!
Ibrahim BennaTechnology LeadCommented:
Check under the following path for any connectors:

CN=Configuration\CN=Services\CN=Microsoft Exchange\CN=OrganizationName\CN=administrative Groups\CN=First Routing Groups\CN=Connections
minniejpAuthor Commented:
cheers, should I just delete this routing group in particular as its now showing the member service in particular under connections.  As I'm removing this exchange server anyway, does it matter if I manually delete the routing group?
Ibrahim BennaTechnology LeadCommented:
I do not recommend that you delete the routing group. Only delete the connector in question as this was what the uninstall process was complaining about. Lets take it one step at a time - delete the connector and run the uninstall process. if it errors out, we can deal with it then.
minniejpAuthor Commented:
Ok I have done that and I am getting this error message:

A problem has been encountered int he Microsoft Exchange Messaging and Collaboration Services setup component.  Cancelling setup.
Ibrahim BennaTechnology LeadCommented:
Make sure you are trying to remove Exchange from Add/Remove programs in Control Panel. Try rebooting the server and try again.
minniejpAuthor Commented:
I was removing it from the Add/Remove programsin Control Panel.  It asked for a reboot which I did and Microsoft Exchange is no longer available in the Add/Remove programs but i can still access it on this machine and can still see references to it.
Ibrahim BennaTechnology LeadCommented:
I guess it is time for last resort - manually removing Exchange 2003 from the server.

http://clintboessen.blogspot.ca/2012/10/a-problem-has-been-encountered-in.html will help. In the MS article, it talks about reinstalling IIS and what not - if you do not plan to reuse this server or plan to wipe it clean, ignore the reinstall statements.

Some other articles that may help:

http://blogs.msmvps.com/bradley/2011/01/28/manually-removing-exchange-2003-from-the-migration-process/

If you are planning on wiping the server completely, you can simply delete the server object from ADSIEdit from the following path:

Configuration Container
CN=Configuration, DC=Domain_Name,DC=com
CN=Services
CN=Microsoft Exchange
CN=Your_Organization_Name
CN=Administrative Groups
CN=Your_Administrative_Group_Name
CN=Servers
Delete ServerName

Do NOT delete any other container!

Once that is done, the server is removed from AD permanently and you can just remove the server from the domain and format it. This avoids the hassle of manually removing the services and registry keys from the server (this is only needed if you plan to reinstall the server). This would be my best option at this point.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
minniejpAuthor Commented:
The Server is a virtual Server and I plan on just deleting the VHD when I have finished.  If i carry out the above, will the other Exchange Servers see that it has been removed as well?

Cheers!
Ibrahim BennaTechnology LeadCommented:
the moment you delete the server Object from AD, the remaining servers will detect this change after replication has occurred.

Even though this is a VM, I would suggest you remove it from the domain first so its computer account is removed OR you can manually delete its computer account.
minniejpAuthor Commented:
When I go to delete the server name, it comes back with "do you want to delete this container and everything in it".  I said no to see what was in the container before it is deleted and below is what is there:

CN=InformationStore
CN=Microsoft MTA
CN =Microsoft System Attendant
CN=Protocols

I'm assuming its still ok to delete.  This is everything within the server name that I can trying to remove (under the Servers Container), the other Exchange 2003 Servers are at the same level but I will be leaving them as is.

Cheers again
Ibrahim BennaTechnology LeadCommented:
Other exchange 2003 servers?? How many other 2003 servers do you have still?

Yes go ahead and delete the server object and everything under it.
minniejpAuthor Commented:
Just one more and then that is it.  Thanks i'll try that now.
minniejpAuthor Commented:
Thanks worked succsesfully! Cheers its great to finally get rid of that one!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.