Jim Stiveson
asked on
Exchange 2016 Phantom Public Folder Mailbox Migration Requests
Good day all
So we have run into a somewhat interesting but annoying situation. We have a 3 node DAG that we have started to migrate from to a new DAG in the same organization. After migrating all mailboxes from a particular database, yes, ALL mailboxes of every type, we removed all copies and then attempted to delete the last copy. When we attempted to remove the last copy we received the following error:
This mailbox database is associated with one or more active PublicFolderMailboxMigrati on requests. To get a list of all PublicFolderMailboxMigrati on requests associated with this database, run
Get-PublicFolderMailboxMig rationRequ est | ?{ $_.RequestQueue -eq "<Database ID>" }. To remove a PublicFolderMailboxMigrati on request, run Remove-PublicFolderMailbox MigrationR equest <Recipient I ... etc etc
Well, here is the funny thing. When we run Get-PublicFolderMailboxMig rationRequ est | ?{ $_.RequestQueue -eq "<Database ID>" } it returns absolutely nothing. So, that is a problem since one cannot remove a request that does not exist. So after some web research we were able to find a few posts on this situation along with a potential solution. The following links are what we found: https://social.technet.mic rosoft.com /Forums/of fice/en-US /54fd0db4- 11d3-421c- 92e8-d4050 338a907/tr ouble-remo ving-2016- mailbox-da tabase?for um=Exch201 6Adm and http://terenceluk.blogspot .com/2017/ 01/attempt ing-to-del ete-exchan ge-server. html
After reading these we opened ADSI edit and navigated to: CN=Configuration,DC=Domain Name,DC=lo cal ==> Services ==> Microsoft Exchange ==> Organization Name ==> Mailbox Replication ==> PublicFolderMailboxMigrati onRequests
Here we found four PublicFolderMailboxMigrati on Request from two years ago. This matches pretty much exactly what was contained in the two articles we found. Our questions are: Does anyone else out there have experience with this? Both articles state that they were able to resolve the issue and delete the database by using ADSIedit to manually delete these orphaned migration requests. What are your thoughts on the safety of doing this? In the past I have personally deleted orphaned mailbox databases themselves in AD but I also consider that the "Nuclear Option" and I like to avoid doing so. Does anyone know of another way to resolve this issue?
Any and all input will be greatly appreciated.
So we have run into a somewhat interesting but annoying situation. We have a 3 node DAG that we have started to migrate from to a new DAG in the same organization. After migrating all mailboxes from a particular database, yes, ALL mailboxes of every type, we removed all copies and then attempted to delete the last copy. When we attempted to remove the last copy we received the following error:
This mailbox database is associated with one or more active PublicFolderMailboxMigrati
Get-PublicFolderMailboxMig
Well, here is the funny thing. When we run Get-PublicFolderMailboxMig
After reading these we opened ADSI edit and navigated to: CN=Configuration,DC=Domain
Here we found four PublicFolderMailboxMigrati
Any and all input will be greatly appreciated.
Yes you can delete it it's safe to delete since the request is 2 yrs. old and will not impact the production.
ASKER
Justa bit more information:
Get-PublicFolderMailboxMig rationRequ est does not return anything, the dates on the request objects in AD are two years old. However, the Public Folder mailboxes the reference do still exist. As a matter of fact, I just successfully migrated them to a new database a few days ago.
Get-PublicFolderMailboxMig
ASKER
Deleting the orphaned objects in AD allowed us to remove the Database.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No