Solved

Migrating Exchange 2007 > 2013 Public Folder

Posted on 2013-06-25
3
4,259 Views
Last Modified: 2013-06-30
I am pulling my hair out with the final step of migraitng my public folder form exchange 2007 to exchange 2013. I have a co-existence setup, my exchange 2007 server is named 'exchange' and my exchange 2013 server is called 'exchange2013'.

I have follwod both of these guides:

http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part2.html (part 1 aswell)

http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

Which both cover the same thing really.

The problem is, when i get to the stage of resuming the migration, is never completes. Executing Get-PublicFolderMigrationRequest | GetPublicFolderMigrationRequestStatistics shows status as 'StalledDueToMailboxLock'.

It never leaves this state. I have restarted both servers, have confirmed that the status of the migration on the source 'exchange' server as both:

PublicFoldersLockedForMigration : True
PublicFolderMigrationComplete: True

In the EAC, it does show the public folder mailbox, however on the public fodlers tab it continues to say there are no active public folder mailboxes and shows no folders because of this. In outlook however, we can see the folders and all operates ok from there.

I am lost on this now and don't know what to do. Please help somebody!
0
Comment
Question by:sparky2156
  • 2
3 Comments
 
LVL 11

Expert Comment

by:James Hodge
ID: 39274301
Hello,

I would suggest try the following:

1) Reboot both servers
2) Ensure Public Folders are still locked for migration
3) Run cmdlet
Resume-PublicFolderMigrationRequest -Identity \PublicFolderMigration

James
0
 
LVL 3

Accepted Solution

by:
sparky2156 earned 0 total points
ID: 39274472
Amazingly, removing the lock from the publicfoldermailbox on the 'exchange' (2007) server and resuming the migration resolved the issue. I tried this several times before without success but after posting this question it magically went through.

I think for anybody else having this same problem in the future, rebooting both of the servers and then removing the lock on the 2007 server, and then resuming the migration on the 2013 server, is the solution. It might not work first time, but keep trying! Not a very good solution I know.

The command to unlock the database is as follows:

Get-OrganizationConfig -PublicFoldersLockedForMigration:$False

Then the following command to confirm:

Get-OrganizationConfig | Format-List PublicFoldersLockedForMigration, PublicFolderMigrationComplete

Thanks.
0
 
LVL 3

Author Closing Comment

by:sparky2156
ID: 39287885
This was the solution
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This video discusses moving either the default database or any database to a new volume.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question