remove exchange 2003 after exchange 2010 migration

I have exchange 2010 live and all users migrated, i am now going through the uninstall of exchange 2003 and it seems to go through ok but fails on removoing microsoft exchange collaboration services, does anyone know why or how to remove this manually and ensure that my environment is clean of 2003...

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.

Can you please give any error messages you receive when the removal fails.
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
This is pretty common:
Ragu RamachandranCommented:
If you are absolutely positive that you don't need Exchange 2003 servers. Then you can use ADSIEDIT to remove the server.
But this should be done as a last resort.
Make sure the Public folders are replicated and working alright on 2010
CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

zingabAuthor Commented:
during uninstall i get 2 prompts that say "setup failed while installing sub-component microsoft exchange oma browse with error code 0x80072030" i select cancel an dthe uninstall continues but places a red x on microsoft exchange messagin and collaboration services, i then get the unintsall to complete with an error that states "there is no such object ont he server, facility ldap provider, id no 80072030 microsoft exchange setup"
Do not force to uninstall or even worse to try to manually remove exchange server from your organization.
It is better to keep running your old server for additional two weeks, than force the removal and finish with problems also on new server. Just take your time and don't rush!
Use this drastic measures only when you don't have any other options.

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
Concur with Davorin and the others and to validate that all is well I would turn the Exchange 2003 server off for a few weeks before trying to remove.
zingabAuthor Commented:
ok at this point it is off, what would be the next step on the force removal to get exchange 2003 out of my environment when that time comes?

thanks all for your responses, just want to make sure i get back to a clean point.
Follow this MS article
Troy Werelius
zingabAuthor Commented:
Lucid8 - thanks! -article specifies exchange 2007 - is this the same if i have exchange 2010? Also, for safety sake can some other experts let me know if t this is the correct path to take?

Yes its correct and when you are done then run a ExBPA health check from your new server to ensure all is well.
Here is more on the topic and moving from Exchange 2003 to Exchange 2010:

Upgrade Exchange 2003 to Exchange 2010
Upgrade Exchange 2003 to Exchange 2010 – Part II
Free e-book by the same author, Jaap Wesselius, also a chapter on migration from 2003 to 2010: Exchange 2010 - A Practical Approach By Jaap Wesselius
Troy Werelius
It is a little bit difficult to help without knowing what step or procedure you have taken, until you came to this point. And if you had any problems during this procedure.
From the info you posted in question EndureKona was on the right path.
Most of the problems during exchange migration can happen because mailboxes or public folders are not properly migrated. Especially public folders can take days to properly replicate on new server.
At exchange migration I always:
- do by book migration procedure (Anytime you can say: I have followed this procedure and the problem appeared at this and this point.
- do things by lots of patience. Even if the migration would take a week or more.
- have finished migration procedure by uninstalling the old exchange server. This part I take like same sort of fuse or checkout that migration procedure was OK.

And yes, the procedures lucid8 listed are correct.
zingabAuthor Commented:
Davorin, ty, i did not run into any problems and do not use public folders currently in my environment, the only issue i am having is during the uninstall process - i did have a coupld of users that had some exchange attributes poitning to my 2003 server, but i had found those and removed them and the unintsall let me this point i am just stuck on getting the 2003 server out of there!
if you have done all the above and there are no problems except the old object is till in the management console you can just right click and delete the object.  
Then run ExBPA health check from your new server to ensure all is well.
There are also some system folders under public folders (Schedule+ Free Busy folder, Offline address book, ...) that are important for exchange 2003 organization and even you have not used public folders, the public folder database is not empty. If the database is not empty you are not allowed to remove it.
If you don't have Outlook 2003 clients, most of them you won't need on new server, but anyway it is worth to check. Maybe it is this cause of this problems.
It is for only exchange 2003 organization and similar to lucid8's link, but at least is all stuff on one page.
As shown in Upgrade Exchange 2003 to Exchange 2010 – Part II ( lucid8's link) you can try to delete public folders and you will be notified if they are empty.

zingabAuthor Commented:
problem is that since part of the uinstall worked, i can no longer start the information store or get to public folder store...
Is any of exchange services on old server running?
I would do two tests:
1. Run Exchange best practice analyzer on new server and check if it reports any problems
2. This time disconnect network cable from old server and run Exchange best practice analyzer again.

Compare if the two results are identical. Do you get any errors? Does new server shows any problems while old server is disconnected?This can help you to determine the severity of the problem.

You should have also two log files located on the root of the drive where exchange server is/was installed (Setup.log and Exchange Server Setup Progress.log). Maybe they can help you to see where was the problem. You can also post the logs.

Here are listed cases when exchange 2003 refuses to uninstall.
But I'm almost certain that the exchange was not uninstalled becouse of missing some prerequisites, but an error at deinstallation procedure.
zingabAuthor Commented:
Thanks all i will check and get back to you guys early next week. Thanks again!
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

From novice to tech pro — start learning today.