Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4507
  • Last Modified:

Migrating Exchange 2007 > 2013 Public Folder

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
sparky2156
Asked:
sparky2156
  • 2
1 Solution
 
James HodgeManaging DirectorCommented:
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
 
sparky2156Author Commented:
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
 
sparky2156Author Commented:
This was the solution
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now