Home » Exchange Server » Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal

Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal

During a transition from Exchange Server 2007 to Exchange Server 2010 you may encounter an error removing a Public Folder Database from the Exchange 2007 server.

The error message tells you that the “Object is read only because it was created by a future version of Exchange”.

The solution is to use the Exchange Server 2010 Management Shell to remove the Public Folder Database. From an Exchange Server 2010 server run the following command to retrieve the identity of the Public Folder Database you wish to remove.

Then run this command to remove the Public Folder Database, using the Identity that was retrieved in the previous command.

The Public Folder Database is now removed from the Exchange 2007 server.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server


  1. Paulk says:

    Worked for me also, strange thing is that even if you check the ExchangeVersion on the Public Folder Database is 0.1! where does it find that the version is 0.10 ?!?!? 🙂

  2. Alan Ingram says:

    OK, its been a while since this article but Exchange 2013 throws a spanner in the works in that whilst it causes exactly the same error, because it no longer has public folder databases (it just uses the normal mailbox database instead) the Remove-PublicFolderDatabase command no longer exists?!


  3. Mike says:

    Alan, did you manage to solve your issue? I’ve run into the same: Migrated Public Folders from Exch2007SP3RU10 to Exch2013CU1, and now I can’t remove the Public Folder Database from the Exch2007.

    Running the command on the new server is not possible as Remove-PublicFolderDatabase is not available on Ecxh2013.

      • Mike says:

        No, not yet. I’m not sure though if it is really necessary for us as we’re just trying to get rid of that Exch2007, and I’m guessing the uninstallation will work eventhough the public folder database has not been removed.

        • Mike says:

          Darn it, at what stage are you getting that error? I’m afraid the only way around this is via ADSIedit, although that feels awkward…

  4. Alan says:

    I can’t really recall exactly what I did I am afraid. I know I had a really bad week trying to get everything across but in the end I managed it and have since taken the old Exchange 2007 server off-line.

    Maybe I never worked out how to remove it from 2007 and just left it until I took the server off-line?

    • Alan says:

      I recall using ADSIedit for something too, but I think I just killed the server and then used ADSIedit to remove the server from the domain…

  5. David Hitchcock says:


    I have found a way to remove the unwanted Public Folder database in 2007 without using ADSI Edit or migrating the publicfolders.

    After you have removed all public folders and system folders using (from exch2007):-

    Get-PublicFolder -Server SERVERNAME “Non_Ipm_Subtree” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server SERVERNAME -Recurse -ErrorAction:SilentlyContinue


    Get-PublicFolder -Server SERVERNAME “” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server SERVERNAME -Recurse -ErrorAction:SilentlyContinue

    Use this command:-

    Get-OrganizationConfig | Set-OrganizationConfig -PublicFolderMigrationComplete $True

    Ignore the warning (As the name has been changed by Exchange 2013)

    Then remove the database from the exchange 2007 gui without problems 🙂

    • John Tawney says:

      Thank you!!! This is the only thing that worked outside of reverting to using ADSIEDIT (which I did NOT want to have to use unless I had to).

    • Steven L. says:


      Thank you!! This worked for us, too. We are currently coexisting in a 2007 and 2013 environment.

      We tried to use ADSIEdit, but the PF was not in there…

  6. Dave Eckersley says:

    Get-OrganizationConfig | Set-OrganizationConfig -PublicFolderMigrationComplete $True

    This worked for me in exchange 2007 removal after migration to exchange 2013 when everything else failed!!


  7. christopher mackintosh says:

    Get-OrganizationConfig | Set-OrganizationConfig -PublicFolderMigrationComplete $True

    Saved me otherwise public folders are a pain in the butt when removing Exchange 2007 from Exchange 2013 only environment

Leave a Reply

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