Removing Exchange 2007 (post Exchange 2010 migration) – Offline Address Book Error

I have now done two separate migrations to Exchange 2010, and in each instance I hit a snag at the final stage – removing the now redundant / last Exchange 2007 server that remains as part of the MS Exchange setup.

Please note, before following the below, make sure you have completed all steps of migration before attempting this process. You must make sure all your mailboxes, public folders, Send Connectors, etc, etc, are migrated, and that you truly are just stuck with an empty vessel of an Exchange 2007 that refuses to uninstall. This is not a short-cut for all the proper processes to follow!

The issue I found, after completing all official removal steps, was that Exchange 2007 would not uninstall stating:

“Uninstall cannot continue. Database ‘Public Folder Database’: The public folder database “MAIL\Second Storage Group\Public Folder Database” contains the following offline address book(s): \Default Offline Address List. Before deleting the public folder database, move the offline address book(s) to a web-based distribution point.”

Needless to say, I have already moved the offline address book in every context to my new Exchange 2010 server. Replication has taken place, and I can see all is well.

So why is this happenning? I suspect (like me) you are asking the same question, and hence you are on this blog.

The answer is that the uninstaller finds an entry in Active Directory that still indicates your Exchange 2007 server is a valid and primary holder for a copy of the public folder, and so fails to remove Exchange 2007. The solution is therefore simple – we remove this errant entry in Active Directory using ADSIEdit.

Here are the steps to follow:

1) You probably don’t have ADSIEdit registered by default, so bring up a command line with admin elevation, and type:

regsvr32 adsiedit.dll

A info box should confirm registration of this mmc snap-in.

2) Bring up the run box and type mmc and press enter.

3) In the MMC console that appears,  go to File and then Add / Remove Snap In…

4) Select the ADSI Edit option from the available snap-ins list, and use the Add> button to add it to the right column. Then click OK.

5) With the ADSI Edit option now available in the MMC console, right click on it and select Connect To… from the properties list that appears.

6) In the Connection Settings properties box that appears, change the option for Select a well known Naming Context to ‘Configuration’, make sure your old Exchange 2007 server name is listed in the ‘Path’ field above this, and then click ok.

7) This should load up a tree structure, with your Exchange 2007 server shown in its internal Fully Qualified Domain Name at the top of the tree (e.g. Configuration [mail2007.mydomain.local].

8) Here’s the disclaimer – editing Active Directory incorrectly can render your domain unusable if done incorrectly, and must be done with extreme caution. I accept no liability for my advice – you have been warned!!!

9) Follow the directory tree as follows, right from the top (I have simplified this, instead of putting every AD naming context in) till you are in the folder at the bottom of this list:

Configuration [servername]->
Configuration ->
Services ->
Microsoft Exchange ->
Your Organisational Name->
Administrative Groups->
Exchange Administrative Group->
Exchange 2007 Server Name->
Second Storage Group->

In that final Second Storage Group branch, you will find a sub-entry called Public Folder Database. Right click this entry, and delete it.

10) Now re-run your uninstall of Exchange 2007, and you should find the error message is gone, and providing you have done everything else to move correctly to another Exchange server, the setup will uninstall your copy of Exchange 2007 :)

11 thoughts on “Removing Exchange 2007 (post Exchange 2010 migration) – Offline Address Book Error”

  1. You’re the man…exact same problem you were having, and this did the trick.

    1. That’s great – really happy to have helped, and thanks for the feedback this is still working :)

  2. Thank you!!! This was the last step that I couldn’t figure out! Worked perfectly

Comments are closed.