none
Unable to uninstall exchange 2007

    Question

  • I am trying to uninstall a Exchange 2007 server that is in the same forest as a Exchange 2003 server. I'm getting the following error:
    -------------------
    Mailbox Role Prerequisites
    Failed

    Error:
    Uninstall cannot proceed. Database 'Public Folder Database': The public folder database specified contains folder replicas. Before deleting the public folder database, remove the folders or move the replicas to another public folder database.
    Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=EN&v=ExBPA.3&id=b6e3b32a-8848-46cb-9567-72288ac15f60
    --------------------
    I can see that its some of the system folders that are set up to replicate with the Exchange 2003 server. But I can't find the Exchange Management Shell command to remove the replicas.
    Thursday, September 14, 2006 10:52 PM

All replies

  • Take a look at the set-publicfolder cmdlet.  One of the options that can be set is the replicas.

    If you do a get-publicfolder command, this should list all public folders that exist on your 2007 server.

    Friday, September 15, 2006 6:29 PM
  • Hello,

     

    I'm having the same problem.

    Did you resolved the issue?  How?

    Tuesday, January 02, 2007 9:05 PM
  • I am having the exact same problem.  Have tried the command shell but receive the same error.  I read someplace folks using ADSI edit to remove them but haven't seen a clean description of that yet.

    Help would be greatly appreciated.
    Thursday, January 11, 2007 1:47 AM
  • Well, using ADSIEdit certainly can be used, but you should do so carefully.  I've done this on my system when I experienced this issue, but only because I knew that there were no replicas of any folders, and because it was a VM.

    If you choose to do this via ADSIEdit, you would navigate to the location of the Public Folder Store, and simply delete it there.  As an example location, in ADSIEdit, you would go to Configuration, Configuration, Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Group, Servers, Servername, Information Store, First Storage Group.  Then on the right hand pane, you would highlight the Public Folder Store and Delete it.  This performs basically the same function as the cmdlet does, or removing it via the Exchange Management Console.

    Thursday, January 11, 2007 4:11 PM
  • Also, as to the original question, if you are just trying to remove replicas, you can also do that via the Exchange 2003 server.  Simply remove the 2007 server from the replica list and see if that helps.
    Thursday, January 11, 2007 4:15 PM
  • Open Exchange 2007 management shell (CMD line) and type following commands:

    Get-PublicFolder -server xxxxx "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -server xxxxx
    -Recurse -ErrorAction:SilentlyContinue

    Get-PublicFolder -Server xxxxx "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder
    -Server xxxxx -Recurse -ErrorAction:SilentlyContinue

    Replace xxxxx with your Exchange server name in the above command.

    Wednesday, January 24, 2007 12:48 PM
  • Thanks Navin,

    I tried all my tricks but nothing was working till this.

    Tuesday, January 30, 2007 5:59 PM
  • Try this..
    dismount the public store, rename the old public store db folder, remount (it will recreate the public folder db)  use adsiedit tool to navigate to the Configuration/Services/Microsoft Exchange/<your organization container>/  Find the 2nd storage container that contains the public folder object and delete it. 

    This allowed me get past the uninstall check tools, because there was no pf db to be found.  The problem looks like MS doesn't display the folder replicas too easily. Exchange 2007 is more of a downgrade for experienced exchange admins rather than an upgrade!
    Sunday, February 11, 2007 8:17 PM
  • ziki -

     

    What was your resolutions to this issue, where you able to remove EXH2007? or did you do something else?
    let me know, I'm still stock with the folder replication issue, I also noticed when trying to run all four commands suggested to you, I was prompt to type a "Identity" right after the command.

    Please help

     

    Thanks,

     

     

    Sam Taveras

     

    Sunday, February 25, 2007 9:31 PM
  •  Navin Tah wrote:

    Open Exchange 2007 management shell (CMD line) and type following commands:

    Get-PublicFolder -server xxxxx "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -server xxxxx
    -Recurse -ErrorAction:SilentlyContinue

    Get-PublicFolder -Server xxxxx "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder
    -Server xxxxx -Recurse -ErrorAction:SilentlyContinue

    Replace xxxxx with your Exchange server name in the above command.

     

    Thanks for the suggestion - I tried this command - replied A to say yes to all questions for both - looked like it was doing something but when I went back to the exchange MMC, and tried to remove the public folder it says the same thing - the public folder specified contains replicas...  funny thing is I never specified anything about replicating.

    Exchange 2007 has some cool new features but why is it so kludgy?   No more real integration with AD computers and users, and why the heck do we have to runs scripts do do everything - did MS think typing is easier than a GUI?   Why not have a purely DOS based exchange server?   And last - I can't find squat in the new MMC - I knew where everything was in 2000 and 2003 - can't find so many simple things like the protocol status (e.g. IMAP) I don't see a quick listing of what size peoples mailboxes are...

    Sunday, February 25, 2007 11:40 PM
  • Thanks - I did that and it did allow me to finally release my public folders - not sure what the hell is wrong with MS - Exchange 2007 seems pretty poorly cobbled together.   Why did they put so much effort into MS BOB or Clippy and so little work into Vista, Zune, Office 2007, Exchange 2007...

     

    Monday, February 26, 2007 1:42 AM
  • Hello All-

    I had Exchange 2007 running on two servers and I deleted these servers. Then I reinstalled and installed Exchange 2003 (2007 was a MAJOR pain in the you know what). Then I saw the old Administrative Groups from the Exchange 2007 instance. So I used adsiedit.msc and removed them and thought everything was okay. Now when I use Exchange Tasks on a user's account and enable the mailbox it says it works but if I go into Exchange System Manager - no mailbox! I am so confused and don't know what to do next.

     

    Thanks,

    locoytravieso

    Thursday, March 01, 2007 5:01 AM
  • Extreme Thanks for this post.!!!

    I installed to quick thinking it was just another version of Exchnage and I would figure it out along the way,

    Needed and Edge Transport from the start! Had to uninstall after mailboxs and databases. Huge mess and then I could not uninstall!

    This post allowed me to move on!

    Thanks again!

     

    Tuesday, March 13, 2007 5:34 PM
  • Beleive me !

    The best way to uninstall Exchange 2007 with Public folder replication problems, is to follow instruction from this guy Ben Winzenz - MSFT.

    The below post of Ben, help me to solve all immediatelly.

     

    Giuseppe

     

    Tuesday, March 13, 2007 7:09 PM
  • Try uninstall Exchange 2007 from a DOS command C:\Program Files\Microsoft\Exchange Server\bin\setup.com /mode:uninstall works for me.  But if you have an another Exchange 2007 server try this link: http://technet.microsoft.com/en-us/library/aa998329.aspx.
    Thursday, April 12, 2007 3:09 AM
  • After loosing most of my hair having the same problems as you guys the ADSIedit util saved my life. I removed the references to first and second storage groups, and voila, the add/remove let me take out exchange.

     

    Perhaps somebody at MS could make this a little more difficult to do. After all, I only lost 9 hours of my life trying to uninstall exchange!

    Thursday, April 19, 2007 2:44 PM
  • Even in a single exchange 2007 server i could not uninstall before i found this. i would have hoped there was an easier way to do this. But it did work for me.

    D
    Friday, April 20, 2007 10:19 AM
  • Thank you!!!!!!!!
    Wednesday, April 25, 2007 8:30 PM
  • i agree completely!!!

    with adsiedit you manage to uninstall exchnage 2007

    it's unbelievable!!

    thank you Ben

    Wednesday, May 16, 2007 4:06 PM
  • This worked for me... Thanks!
    Monday, May 28, 2007 9:30 AM
  • Wow, thanks for this.

     

    I've spent hours trying to get round the public folder replication issuses!

     

    What a complete pile of junk Exchange 2007 is. The exchange development team have discovered CLI. Terrific, as an administrator they've made my job even harder. Hey Microsoft as someone who has to develop and maintain numerous platforms I don't want to have to learn a new version of mandarin to control my exchange server. Remember the concept of an effective UI? Isn't that what Microsoft's philosophy is all about?

     

    Exchange 2007 is clearly aimed at large scale organisations who are able to employ back room geeks who can spend their entire time learning a new CLI language. For small-medium organisations it's a complete waste of time

    Tuesday, May 29, 2007 3:34 PM
  • The advice from Ben was perfect. Resolved my issue quickly and allowed me to complete the uninstall of Exchange 2007. This being my first Exchange rollout, I was hoping for something a bit more intuitive. Kinda wishing I had a license for 2003.
    Tuesday, May 29, 2007 7:52 PM
  • Couldn't have said it better myself.  This version of exchange is intended for newbies.  Its like Vista where you can't find anything.

     

    Thursday, May 31, 2007 6:13 PM
  • you rock that just saved my ***. Thanks Man great advice Ben's Information is right on
    Thursday, May 31, 2007 8:40 PM
  • That woks perfectly with ADSEDIT, I mean as perfectly as uninstalling Exch by ADSEDIT is concerned. no comments  !

    Thaks for the tip!

    Monday, June 04, 2007 4:04 PM
  • I just wanted to post a thank you to you Ben.  I have tried for several days, different methods to remove the replication from the Public Folder store, all with no luck as I have no other server to move the replications.  Your post above allowed me to uninstall Exchange 2007.  Not that I wanted to, but after a lack of reading, we were not prepared to learn that a migration to Exchange 2007 now REQUIRES two servers.

     

    Aloha to you Ben.

    Tuesday, June 05, 2007 4:49 PM
  • To solve the uninstall issue, the really way is from Ben's. thanks to Ben.
    Wednesday, June 13, 2007 3:02 PM
  • Hiii Ben,

     

    You are simply great. This solution worked. I tryied lot through commands to remove the public folders but failed. but Adsiedit is simply great solution.

     

    Thanks a lot.

    Friday, June 22, 2007 6:53 AM
  • How can i get the ADSIedit tool on exchange 2007?

     

    Friday, June 22, 2007 3:05 PM
  • I got ADSIedit to work...now how do i get this fixed?

     

     

    Summary: 3 item(s). 2 succeeded, 1 failed.
    Elapsed time: 00:00:16

     


    Hub Transport Role Prerequisites
    Failed

    Error:
    This computer is configured as a bridgehead server for 1 routing group connector(s) in the organization. These must be moved or deleted before Setup can continue.

    Elapsed Time: 00:00:04


     

     Ok, nevermind, i got it fixed Smile thanks!

     

    Friday, June 22, 2007 3:19 PM
  • You guys think you have problems.

     

    Try unintalling Exchange 2007 when the server has died with no backup.

    MS says the only supported method is with Add/Remove programs or by re-running the setup cd.

     

    Haha, what about in a DR situation?

     

    Actual problem is that msx2k7sp1b on Longhorn latest April Beta is so dodgy it failed install and wont now uninstal, just craps out all the time.

     

    Wish me luck, Im going in with ADSI edit and into the Services node in "Sites and Services"

    Sunday, June 24, 2007 11:05 AM
  • Hey everyone,

    Does anyone know how to resolve this error?

     


    Hub Transport Role
    Failed

    Error:
    Could not find the default Routing Group 'Exchange Routing Group (DWBGZMFD01QNBJR)'.

    Elapsed Time: 00:00:12

    Monday, June 25, 2007 4:11 PM
  • just when i was about to give up hope you've helped us... thanks Navin!

    the first command didn't solve it for me, it was the second line. seems its a common problem, glad someone knew how to fix it. Thanks!
    Thursday, June 28, 2007 3:58 AM
  • Try to browse the "First Administrative Group" which contain the Exhchange 2000 - 2003 Server.

    You will see the connector from Connectors. Delete it manually then you can uninstall the Hub Transport Role!!

     

    Monday, July 30, 2007 7:31 PM
  •  

    Hello there..

    Could you please state the HTTP link of the document you're talking about?

     

    Thanks...

    Thursday, September 13, 2007 9:00 AM
  • Follwed Ben Winzenz instructions and uninstall worked flawlessly.

     

    Thnk you!

     

    Wednesday, October 10, 2007 4:36 PM
  • Follwed Ben Winzenz instructions and uninstall worked flawlessly.

     

    Thank you!

     

    Wednesday, October 10, 2007 4:36 PM
  • This worked perfectly. Somehow during my installation something went horribly wrong while reading from the disc and I couldnt get the server to boot correctly. This allowed me to remove Exchange 2007 seeing as I had no replica's. Thanks.
    Friday, October 12, 2007 4:56 AM
  • I followed the posts containing the cmdlet to remove the public folder subtree and etc, however that was not necessary.  Under exchange management console, all you have to do is go to your mailbox database, right click and hit properties, and repoint it to your other server (exchange 2003) for its public folder database and you're all set to uninstall.  So many complex things for such a simple task.

     

    Don't forget to repoint your exchange 2003 public folder database to itself now as well if your exchange 2007 was a primary holder for the public folder database.

     

    If you then run into the public folder problem of not being able to delete the public folder database due to replicas, you need to remove it using adsi edit under your first organization, exchange administrative group, servers, information store, public folder key, and under the folder heirarchy key.

    Tuesday, October 16, 2007 5:15 PM
  •  Navin Tah wrote:

    Open Exchange 2007 management shell (CMD line) and type following commands:

    Get-PublicFolder -server xxxxx "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -server xxxxx
    -Recurse -ErrorActionTongue TiedilentlyContinue

    Get-PublicFolder -Server xxxxx "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder
    -Server xxxxx -Recurse -ErrorActionTongue TiedilentlyContinue

    Replace xxxxx with your Exchange server name in the above command.

     

    I had the same issues with removing replicas from a clean install of Exchange Server 2007 SP1 Beta 2 with no prior attachments to any other servers.  Though I did not try Ben's suggestion, Navin's worked.  Thanks!

    Tuesday, November 06, 2007 4:05 AM
  •  Navin Tah wrote:

    Open Exchange 2007 management shell (CMD line) and type following commands:

     

    Get-PublicFolder -server xxxxx "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -server xxxxx -Recurse -ErrorAction: SilentlyContinue

     

    Get-PublicFolder -Server xxxxx "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server xxxxx -Recurse -ErrorAction: SilentlyContinue

     

    Replace xxxxx with your Exchange server name in the above command.

     

    Worked for me too.  Failed at first because I was missing the last bit with the silentlycontinue part.  Did not try Ben's option as I was having replication issues.  Here's my question, my environment consisted of one Exch 2007 server so what was it replicating too?  As I understand replicas (and not having read anything about the way Exch does it) its a copy of whatever it is your dealing with.  A copy of NDS in Novell, a copy of ADS in Windows so why or how did the Exch server make replicas if it was the first and only exch server on the network?

     

    Thanks for the info

     

    Note: had to put a space between the colon and S in silentlyrun to display properly.  Delete space if you are copy,pasting.

    Friday, November 09, 2007 4:39 PM
  • I can't tell you how grateful I am for this post...
    I have spent the last 4 days trying to uninstall Exchange 2007 from my organisation purely because i need to get it off the Windows Server 2008 Virtual Machine I have and onto a Windows Server 2003 x64 Virtual Machine.
    Why? you ask - because Microsoft thought it would be a good idea to include a backup utility in Server 2008 (Windows Server Backup) that is not Exchange Aware > and that removing the remote streaming API would be a good idea forcing people to buy either DPM 2007 or a 3rd party backup solution.
    It has been a great learning opportunity and Exchange 2007 definitely has some great new features (like the Edge Transport role, and the "modular" roles concept itself) but they have complicated the management console a bit too much.
    I finally used ADSI Edit as suggested by Ben Winzenz and i could remove the mailbox role.
    I just dont like having to "rip" the pf database out like that, but hey - it worked!
    Thank You
    Thursday, May 15, 2008 6:43 PM
  • Ben your a legend.  I even registered just to say thanks and what a crock of (insert bad word!) Exchange 2007 is.  If Exchange 2000 wasn't bad enough, this seems to have taken it to a whole new level of ***!

     

    Friday, May 16, 2008 10:57 AM
  • Thanks For that. this post worked fine to me.

    ANdy.
    Sunday, January 18, 2009 1:55 AM
  • Thank you very much Ben, i was able to take it out after removing the storage group and mailbox store that contained the public folder using adsiedit.
    Saturday, January 24, 2009 12:53 AM
  • Speeddensity,

     

    Have you tried using the recoverserver mode of Exchange?  Basically in a situation where the server is lost you can reformat the machine, give it the same name and then run Setup.com /m:recoverserver.  That will install Exchange on the machine using the settings of the previous installation stored in AD.  After you do this you can perform a clear uninstall of the server.

     

     

     

    Thursday, January 29, 2009 9:36 PM
  • Thanks Ben it worked for me.
    Friday, September 11, 2009 4:51 PM
  • this is the solution, thanks Ben
    Friday, September 11, 2009 4:51 PM
  • Navin, I Love You :)
    Sorry for the useless comment.
    Thanks for your help - still useful almost 3 years later.
    Saturday, October 24, 2009 6:49 PM
  • Hallo zusammen,

    hatte das gleiche Problem. Bekam die Öffentlichen Ordner Replikate nicht weg. Skripte oder ähnliches hat alles nicht funktioniert, außer mit ADSIEDIT.

     

    Danke an alle / Thanks for all

     

    Tuesday, June 22, 2010 11:39 AM
  • I can confirm right now that ADSIEdit.msc worked where nothing else did. We are now completely migrated to Exchange 2010 and off of 2007. Highly recommend using ADSIEdit for anyone else with trouble removing Public Folder Databases due to replication problems.
    Friday, February 11, 2011 9:16 PM
  • Can you ensure that you no longer have any data on Exchange 2007.
    Saturday, February 12, 2011 12:54 AM
  •  From ADSIEDIT >>>>Configuration, Configuration, Services, Microsoft Exchange, First Organization, Administrative Grups, Exchange Administrative Group, Servers, Servername, Information Store, First Storage Group

    It was worked on my test enviornment.


    Arun Khatri
    Sunday, April 17, 2011 1:36 PM
  • Open Exchange 2007 management shell (CMD line) and type following commands:

    Get-PublicFolder -server xxxxx "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -server xxxxx
    -Recurse -ErrorAction:SilentlyContinue

    Get-PublicFolder -Server xxxxx "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder
    -Server xxxxx -Recurse -ErrorAction:SilentlyContinue

    Replace xxxxx with your Exchange server name in the above command.


    Please, please, do NOT use this command. Customers keep calling in with their public folders wiped out, because they do not understand that Remove-PublicFolder deletes the folder out of the hierarchy. This is just like going into Outlook, highlighting the folder, and choosing Delete. If you do not quickly dismount the database or shut off transport, that change will replicate to your other public folder stores and wipe out all the public folders. Even if you do quickly dismount, the directory objects for the folders will be deleted, breaking email to any mail-enabled public folders.

    This command line iterates through the whole hierarchy and deletes every folder. You should only do this when you are removing the very last public store in the org.

    Otherwise, just use Ben's workaround (delete using ADSI Edit) if you don't want to solve the replication problem that is preventing the replicas from going away.

    Saturday, June 11, 2011 4:45 AM
  • Thanks for the information Bill, really appreciate.

    Anyways i never use that command, rather than using that command i prefer using adsiedit

    Cheers, 


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Tuesday, June 14, 2011 1:09 PM
  • The Above worked for me, thank you very much 

    Friday, May 10, 2013 1:54 AM
  • None of these solutions worked for me.

    The ADSI procedure.  Didn't work.

    Mount, unmount, remount public folders.  Nothing works.  I could have messed up everything because I "disabled" all my public folders (now I don't know how to re-enable them, because they don't show up anywhere).

    Anyhow, the error I get trying to uninstall Exchange 2007 is "Uninstall cannot continue.  Datbase "Public Folder": Exchange cannot remove the public folder database EXCHANGE07\Second Storage Group\Public Folder because it is the last public folder database in the organization that has pre-Exchange 2007 servers.

    I don't know what th means.  Exchange is running on a clunky Win 2003.  My AD is 2008.  I didn't build this enviornment, I just inherited it - but I believe my client used to run Windows 2000 with Exchange 2003.  I'm only guessing.  Either way, I don't care.  I just want exchange off this server for good.  I don't care how badly I destroy this server.  It's getting reprovisioned for something else.

    Nevertheless, all the solutions provided here - nothing worked.  Anyone have any suggestions to just blow up this exchange 100%?

    Thanks

    Monday, December 23, 2013 3:02 AM
  • If you choose to do this via ADSIEdit, you would navigate to the location of the Public Folder Store, and simply delete it there.  As an example location, in ADSIEdit, you would go to Configuration, Configuration, Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Group, Servers, Servername, Information Store, First Storage Group.  Then on the right hand pane, you would highlight the Public Folder Store and Delete it.  This performs basically the same function as the cmdlet does, or removing it via the Exchange Management Console.

    Worked like a charm, thank you so much!
    Tuesday, February 25, 2014 7:16 AM