failed exchange 2003 uninstall

Here goes! have a domain with a single exchange 2003 and single 2010 exchange servers.
moved all info (i think everything) to the new 2010 server (mailboxes, offline address books, etc, using an article from petenetlive) When I tried the exchange 2003 uninstall, it fails, but removes exchange 2003 from the installed programs list. Now I still have references to the old server in the domain and no way to clean up. I have disconnected the server for a week and it seems there are no services still needing the old server.
How can I clean up the domain and leave the 2010 exchange organization functional??
thanks in advance.
Pizza's on me.
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.

Going to need a little bit more info, if Exchange 2003 didnt remove clean, there are various things it leaves behind that might impact you later,

These postential iissue include but are not limited to

Broken Public Site Folder
Broken Public Folder Heirachy
Broken Reciepient Polices

However if the Recipient Update service was assigned to the 2010 server (its not used and it legacy anyway) and your public folders were moved using the moveallreplicas.ps1 script then it's likely only the public site folder is broken and you can use ADSIEdit to remove the failed Exchange server.

If you look at the end of this article, you can see how its possible to remove the reference from active directory.

I will hasten to add do not rmove the legacy Administrative Group in ADSI edit, just remove the failed server.

To fix a broken Public site folder, follow this.

Start > run > adsiedit.msc > configuration > services > exchange > org name >administrative group name > Exchange Administrative Group (FYDIBOHF23SPDLT) > servers > Databases > Exchange 2010 public folder store and go to properties and look for distinguishedname copy the value.
now again go to
start > run > adsiedit.msc > configuration > services > exchange > org name >administrative group name > Exchange Administrative Group (FYDIBOHF23SPDLT) go to properties look for sitefolderserver
check if thevalue is same as the one you copied above if the value is not same then replcae it.

Taken from

scottzechAuthor Commented:
thanks for your response. I did not use the replicate all folders script, since I didn't know about it. what should I do to assure nothing will get lost??
Also, it appears after looking at what you mentioned in your post, that the site folder server is set correctly. I don't see any broken replicas lying around anywhere with references to the old server..
Thats a good thing, usually various aspects of public folders get broken. Of course if your using Outlook 2007 or later you no longer have any requirement for public folders at all but Outlook 2003 or earlier still uses them for Free/Busy and OAB generation.

Did you replicate public folders or were you not concerned with them? if your organisation just isnt using them then its ok, just  go ahead and remove the exchange server from the domain using ADSI Edit

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

scottzechAuthor Commented:
also i'm on the public folder management on the exchange 2010 and it does show some folders that didn't get replicated, it appears. for example, schema root still shows the old server as having the only replica...this makes me nervous!
scottzechAuthor Commented:
again thanks for your help. just trying to hit all the details. and yes we are still on outlook 2003, which is why I want to make sure I do this right. We don't really use public folders, but the oab would be a real mess.
Dont be woried too much about system folders, as I said you dont really need them moving forward. As long as you have all your users data you can work around the rest.
scottzechAuthor Commented:
Ok, so then your first response references "If you look at the end of this article, you can see how its possible to remove the reference from active directory."
but I've looked at the articles and see nothing about where exacty to remove the server in adsiedit.
Your comment about LEAVING the legacy administrative group is also interesting. It should not cause further problems down the road??
thanks again.

scottzechAuthor Commented:
I ran the EXBPA and got this issue about the public folders also which is worriesome.
The default public folder database for mailbox database 'Mailbox Database 0503543736' on server NCIEXCH isn't local. Public folder database: CN=Public Folder Database 0437608833,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=nci,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ncssds,DC=com.

not sure what the NOT local issue is.
scottzechAuthor Commented:
and thanks. Points and pizza are yours for helping.
For the NCIEXCH isn't local. error, this is because you need to assign a default public folder database to your mailbox database. But I will add, unless your organisation is using public folders for data storage or your still using Outlook 2003 then you dont need Public folders at all and you can probably ignore most of these errors.
Also Set-MailboxDatabase -Identity (name of your DB) -PublicFolderDatabase (name of your public folder database on Exchange 2010)
scottzechAuthor Commented:
yes we are using outlook 2003. I also still need help on where to remove the old server reference using adsiedit. thanks.
scottzechAuthor Commented:
I did the set database command, and also checked it in ex console, and it is pointing to the correct value, but still give the "isn't local message".
Your pizza is waiting!!
Ok, as your using Outlook 2003 then your using Public Folders for OAB and Free/Busy, if you have not already done so, create a public folder database in Exchange 2010 and assign it as the default PF store for your mailbox databases as stated above.

This blog details removal of the dead Exchange 2003 server, just remove the server and not the admin group it sits in.

This error public folder isnt local is caused because you didnt update public folder heirachly

You can fix this in ADSIEDIT as well but i would be tempted to try what the suggestion here.

Also more information regarding removal of Exchange 2003 to see if there is anthing else you didnt do :-)

scottzechAuthor Commented:
OK, so I followed the suggestion you were "tempted" to try, and moved the public folders  hierarchy  to the new exchange 2010 server  but exbpa still shows the "isn't local" error.
did the remove server from the ex 2003 esm and that worked fine too.
so, still disturbed by the isn't local message, and I'm getting an error 6 related to get-publicfolderdatabase in event viewer on the 2010 server. Please get back to me quick. I'm supposed to be on a plane tonight! thanks for your help.
scottzechAuthor Commented:
and now when I go on exchange 2010 server info public folders, and try to open system public folders, I get a can't open the public folder database using legacy distingushed name..... Help me please!!
Did you update public folder hierarchy, The suggestion was to install exchange 2003 esm and move it that way.
scottzechAuthor Commented:
Yes, I believe I did that. can you please email me at myname@hotmail and deal with this on the phone maybe?? pizza is on me ?? exchange 2003 esm was still available on the old server and I did it there.
scottzechAuthor Commented:
and I can't do it again cause I did the remove server... This sure is frustrating..

Anybody else got comments on this? I'm burning time here and could use some help right away.... thanks.

This should be usefull. Basically uninstalling exchange 2003 has orphaned these services, your going to have to reassign them. The site folder you said you fixed or was ok but the public folder hierachy looks like its not been updated and still lists the now dead server as its master. Review the link there are some fixes in there.
scottzechAuthor Commented:
Nope, no joy. Did as the article states (the values were identical) and restarted me information store.
ran exbpa, same error.
You might as well pick this up remotely. Put it this way until I scared you you didn't know you had a problem,  you can try recovering the old public folder database and mounting it on exchange 2010 but I've never tried it, don't know I you can. Ideally what you need to do is to recover the old exchange 2003 server (if you removed it from ad then reinstall it with the same name) once rebuilt restore the system state and restore the public folder database. Once the errors are gone you will need to wait for replication to finish and then moveallreplicas.ps1 to move the folders, update the hierachy and remove the replicas from the old public folder.

Once that's done the errors should be gone and the public folder store on ex2010 should be the master.

Also just double check in Adsiedit that the DNs are correct for site folder etc, basically anything you might have edited manually double check it.

It might be an idea to leave it and sort it later if you have a plain to catch.
scottzechAuthor Commented:
The thing is that the public folders didn't have any data. The only thing in there that concerns me is the offline address books. Can't I just recreate the public folders? Will that kill the existing oab's?
thanks again for your help. I don't know if this is going to be aproblem on Monday, so I can't leave now till I get a fix. thanks,
The server rebuild, etc, seems like overkill if there is nothing in the database anyway..
As long as you have an offline address book, you can create one no problem. And an offline address boos is really only used for cache mode or when working remotely. I've left servers in worst state so don't be too worried. The default public folder issue is wierd if you say the site folder is fixed and you updated the hierachy.

Just check that you can edit your recipient policies in exchange 2010 these need to be updated, if you get an error you need to run some powershell

If the public folders have no data then it's just system stuff they are storing, the worst that will happen is free/busy and oab will remain broken. As long as you have remote access you can fix remotely.

You can easily test free busy from owa or outlook, if it works then don't worry about it.

Best thing to do is don't panic, you don't have major issues.

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
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.