• Home
  • Consulting
  • Contact Us
    • About this site
    • Contact Wayne
    • Media Room
    • Wayne’s Bio

SBSFAQ.COM

Supporting IT Pro's & MSP's since 2000

  • Blog
  • FAQs
  • Reviews
  • Downloads

How to do Exchange 2013 Migration Without Migrating Public Folders

February 4, 2015 by Wayne Small 9 Comments

We’ve been doing a number of migrations from SBS 2008 and SBS 2011 over to Windows Server 2012 R2 Essentials + Exchange 2013., or other variations.  So far all the clients have needed to migrate their public folders which is a long and complicated process that really is a pain.

Recently we’ve had the need to migrate a client that has no Public Folders in their Exchange environment, so it gave me the chance to figure out how to do it.  Whilst I searched for answers, I found that there was no single document on the Internet that showed exactly what needed to be done, so I’ve created one here.

Overview

Use this process if you wish to entirely remove the public folders from an Exchange 2007/2010 Organisation instead of performing a migration. This is a one way process. Data will be lost if you proceed.

Procedure

Verify what Public Folders are in use

Use Outlook or OWA to open the Public Folder tree from a client machine. Verify what public folders are present. Export any required information to a PST file just in case the client requires it later.

 

Delete unnecessary public folders

Use the Exchange 2007/2010 Public Folder Management Console on the Exchange 2007/2010 server

Expand the Default Public Folders Tree

Select each public folder in the middle pane and right click and select Remove

clip_image001

If the Exchange Organisation you are migrating has been on Exchange 2000 and then later 2003 – you will have an Internet Newsgroups folder. This folder cannot be deleted using the method above. Instead you will need to use ADSIEdit later in the procedure to delete the Public Folder Database to resolve this issue.

 

Remove any Public Folder hosted Offline Address lists

Verify that the new Exchange 2013 Offline Address list is now the default with this command

Get-offlineaddressbook |fl name,isdefault

It should show as below with True against the new Ex2013 version

clip_image002

On the old Exchange 2007/2010 server, use the command below to remove the old Default Offline Address Book

Remove-offlineaddressbook –identity “Default Offline Address List”

clip_image004

 

Associate mailbox databases with another default public folder database

You can’t actually do this – as in you can’t clear the Public folder Database field using PowerShell.  Therefore you will need to use ADSIEdit.  Firstly however, check out what the settings are using the command below.

Get-MailboxDatabase |fl Name,Pub*

Check the output and as you see below it shows that we’ve associated the public folder databases on the new server with a database on the old server

clip_image005

To resolve this situation, you need to use ADSIEdit.msc

Connect to the Configuration naming context as below

clip_image006

Expand the tree and navigate to CN=Services, CN=Microsoft Exchange, CN=(your organisation name), CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Databases

You will see the databases in the middle pane. Right click the first one and select Properties

Scroll down until you locate the msExchHomePublicMDB attribute as below and select Edit

clip_image007

Select Clear and Ok – you should see the attribute cleared.

Repeat this process for all the Mailbox databases you have. It may take a few minutes for AD replication to send these changes to your other domain controllers.

Repeat the command below to verify that the changes are complete

Get-MailboxDatabase |fl Name,Pub*

clip_image008

 

Remove the public folder database

You will need to do this on the old Exchange 2007 / 2010 server

Remove-publicfolderdatabase “Public Folder Database”

This should remove the DB from Exchange and AD.

However if you have had Internet Newsgroups in your public folder database then you will find that you cannot remove it – you will instead get an error similar to below.

clip_image010

In that case – you will use ADSIEdit.msc to remove it.

Connect to the Configuration Naming context as you did earlier

Expand to CN=Services, CN=Microsoft Exchange, CN=your organization name, CN=Administrative Groups, CN=Exchange Administrative Group, CN=Servers, CN=Your MailBox Server, CN=Information Store.

Expand each node and locate the Public Folder Database as per the screenshot below

clip_image012

Right click on the Public Folder database and delete it.

Then navigate up the tree and delete the Second Storage Group container IF and ONLY IF the Public Folder Database was the only database inside that container.

 

Back to Normal

Once you’ve done this procedure then you may continue with your normal Exchange Migration and complete the other tasks needed before uninstalling the Exchange 2007/2010 server from the network.

Share this:

  • Click to share on Facebook (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to print (Opens in new window)

Filed Under: FAQs Tagged With: Exchange 2007, Exchange 2010, Exchange 2013, Exchange Server, Migration, SBS 2008, SBS 2011, SBS 2011 Standard, Windows Server 2012 Essentials, Windows Server 2012 R2, Windows Server 2012 R2 Essentials

About The Author

Wayne has been working with Microsoft Server products in the SMB market for over 20 years. He has a passion for technology and been a Microsoft MVP for over 15 years. Read More…

Comments

  1. Darren says

    October 14, 2016 at 7:18 pm

    Thank you, thank you, thank you!!!
    I was beating my head against a brick wall trying to remove our old Exch2007 Public Folders and your info worked flawlessly.
    And again thank you!

    Reply
  2. Chris says

    July 21, 2017 at 4:53 am

    Thanks a lot for this awesome guide to remove public folder association. We just migrated from 2010 to 2016 and we’re not using and did not want public folders. When I noticed the new dbs had linked to the old public folders on 2010 I was stumped as to how to clear this connection via power shell. Thanks for the adsi info, saved me a lot of time.

    Reply
    • Ifrah Haviv says

      September 14, 2017 at 7:41 am

      Hi Chris,

      In your migration process, the fact that the outlook connects to the 2010 public folder causes the password prompt on client outlook? Does it solved that issue?

      Thanks,

      Ifrah

      Reply
      • Wayne Small says

        September 15, 2017 at 10:50 am

        Yes Ifrah – this should resolve that problem for you.

        Reply
        • Ifrah says

          September 17, 2017 at 9:54 pm

          Thanks!

          just to be on safe side, first i need to migrate all mailboxes to the new 2016 server and then to remove public folders from the old 2010 server?
          i have public folder DB that i am not using at all but still all my 2010 databases are associated with that PF.

          so after all mailbox migration is will be safe to just remove it as your article describe?

          Thanks again!

          Ifrah.

          Reply
  3. Bino says

    August 4, 2017 at 4:36 am

    Thank you dear this post help me.

    Reply
  4. Röhner, Sebastian says

    August 4, 2017 at 4:02 pm

    Vielen Dank,

    bei mir war es noch schlimmer, ein Windows Server 2003 ohne PowerShell 2.0 und Exchange 2007. Hier ist ein Update auf PowerShell 2.0 nicht so einfach möglich, man solle angeblich alle Exchange Dienste beenden, PowerShell 1.0 deinstallieren, PowerShell 2.0 installieren und dann Exchange wieder starten. Und dann sollen die Public Folder Skripte fkt. -> Da der Kunde aber keine öffentlichen Ordner besitzt, werde ich die manuelle Entfernung durchführen, danke für den Leitfaden!

    Reply
    • Wayne Small says

      August 4, 2017 at 8:02 pm

      Vielen Dank für Ihre Kommentare. Du hast recht, es ist nicht leicht zu reparieren. Ich bin froh, dass dieser Artikel hilft Ihnen, das Problem zu lösen.

      Reply
  5. Ashhh says

    February 7, 2018 at 5:01 pm

    Hi,
    I am in pursuit of transition of ex2010 to 2016,and i dont want to migrate the public folder DB as we are not using it and it has been in dismount state.Can i remove the default PF database before i will start the transition.Is this safe or will it have any adverse effect.
    Regards

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Connect Online With Us

  • Facebook
  • Twitter

Reviews

Splashtop – Cost Effective Remote Control Software

September 22, 2017 By Wayne Small 2 Comments

Western Digital DL4100 NAS

March 3, 2015 By Wayne Small Leave a Comment

SBS 2011 Configuring Certification Guide (70-169)

August 7, 2012 By Wayne Small 4 Comments

Site News

Exchange Bug Stops Mail Delivery in 2022

January 2, 2022

Huge bug found in Intel CPU that could permit hackers to steal your data

January 4, 2018

Recent Posts

  • MS Exchange Zero Day and RemotePowerShell Disabling on Admin accounts
  • Setup changes for Exchange 2016 and Exchange 2019
  • Bluetooth Mouse and Keyboard Randomly Stop Responding
  • Exchange Bug Stops Mail Delivery in 2022
  • How to open and search extremely large text log files

Tags

Antivirus Backup Business Focus Cloud Computing Community Conferences Disaster Recovery Exchange 2010 Exchange Server Future Products Hyper-V Installation Microsoft Migration Patches Personal Rants SBS 4.5 SBS 2000 SBS 2000 SP1 SBS 2003 SBS 2003 Premium SBS 2003 R2 SBS 2003 R2 Premium SBS 2003 R2 Standard SBS 2003 SP1 Premium SBS 2003 SP1 Standard SBS 2003 Standard SBS 2008 SBS 2008 R2 SBS 2011 SBS 2011 Essentials SBS 2011 Standard Security Service Packs ShadowProtect SMB Community Software Software I use StorageCraft Training TrendMicro Troubleshooting Virtualisation Windows Server 2012 Essentials

Terms of Use

Privacy Policy

Copyright © 2023 · Magazine Pro Theme on Genesis Framework · WordPress · Log in