Hi everyone,
Getting a warning when selecting arbritation mailboxes to move to Exchange 2016 (from Exchange 2010 SBS 2011):
The object domain.local/Microsoft Exchange System Objects/SystemMailbox{746E229B-0847-44FE-A23B-A2F68E467C25} has been corrupted or isn't compatible with Microsoft support requirements, and it's in an inconsistent state. The following validation errors happened: Database is mandatory on UserMailbox.
???
Patrick,
That sometimes happens and you can ignore that. Exchange System mailboxes can be recreated if that is needed and if that mailbox is still on the old server we can disable that before we uninstall old Exchange.
Also, last question : when is it appropriate to change port forwarding of port 443 to the new exchange server ? Because connecting on Outlook Web Access from the outside now gives errors...
It is considered the best practice to always forward traffic on port 443 as soon as the URLs are configured on the new Exchange Server and you have the certificate installed. Exchange Server 2016/2013 will down proxy to Exchange Server 2010/2007 if a mailbox is still on the old server.
Your browser doesn't have Flash, Silverlight or HTML5 support.
Ok, started moving user mailboxes... hope all goes well :)
Step 12: Migrate Public Folders... If I don't have any can I just go to 13 or is there any steps in there that should still be done ?
Yes, if you don't use Public Folders skip that chapter. Pay special notice to the uninstall doc of the old Exchange when removing PF Folders and Databases.
Ok, all of the mailbox moving was completed last weekend... port 25 and 443 pointing to Ex2016 server, nobody complained all week :)
Now, did all of the first 12 chapters of Migrating SBS2011 to 2016 Essentials, at chapter 13 I need to remove old SBS 2011 client agents from clients on network... Didn't I see somewhere that you had a script to automate this procedure ?
Also completed first 13 chapters of the Exchange migration, chapter 14 is configuring ARRConfig after Ex2010 from SBS is uninstalled. SO I guess it's time to go through the Uninstall Exchange 2010 from SBS2011 guide.
Makes me nervous ! How do I know with absolute certainty that I must start the uninstallation of Exchange 2010 now ? How to be positive that nothing was forgotten, that nothing is left to do ?
Don't want to skip any steps, since we're going through 3 different migration guides!
Me again :)
Tod you before that I didn't have public folders... well it seems I have old stuff, maybe from the old 2003, that still roams within the public folders... went through all of the steps, and got error messages relating to having spaces in aliases when the initial replication finished with errors...
Tried to rename them and retry the migration and that's when I had no idea of how to do any of this.
After googling for the better part of the day I thought I'd just ask the experts :)
Thanks again,
Patrick
OK, if you don't use Public Folders at all you can remove them. That is described in this guide Uninstall Exchange Server 2010 from SBS 2011. Or you may want to connect to me so I can help you Premier Support for SMB
Hi Mariette,
But like I said, I do have some...
Migrating my public folders from my SBS2011 to Ex2016 and got an error :
Me again :) Tod you before that I didn't have public folders... well it seems I have old stuff, maybe from the old 2003, that still roams within the public folders... went through all of the steps, and got error messages relating to having spaces in aliases when the initial replication finished with errors...
Now you got me confused....
If you have PF's and you must migrate them we need to fix the problems, otherwise skip that chapter where we migrate PF's and go ahead and uninstall the Exchange Server 2010 from the SBS 2011 if the Exchange migration is completed.
Even if that old stuff is there you can still remove them during the guide that tells you how to uninstall Exchange Server 2010 from an SBS 2011
Well, that's the problem... can't complete migration even if I didn't care anymore about the public folders, because there's still an error.
So I figured might as well fix the public folders' names (which I think I did correctly with this command :
Get-MailPublicFolder [Public Folder Name] |Set-MailPublicFolder -Alias [PublicFolderAlias]
But now how to restart the public folder migration ? If I redo the same start-migrationbatch command, well the first time it did it it completed with error so for Exchange it's technically finished and cannot be restarted.
Should I just erase this migrationbatch from Ex2016 and start over chapter 12 ? Would that create all other folders twice in Ex2016 ?
If we don't care about the public folders we can delete the Migration batch. After doing that you should be able to uninstall Exchange 2010 from the SBS 2011. After that has completed check what PF instances you have in Exchange 2016 and delete them.
You did not do any other steps after that you started the Migration Batch? I mean the steps where you run Set-OrganizationConfig -PublicFoldersLockedForMigration:$true and after that?
Yes I did do the rest of the chapter, thinking it might continue and forget about the errors:
Set-OrganizationConfig -PublicFoldersLockedForMigration:$true
Set-OrganizationConfig -PublicFoldersEnabled Remote
Complete-MigrationBatch PFMigration
(that one told me it couldn't continue since status had failed mailboxes)
Can you go to the guide and check what is the last step you did, see Migrate Exchange Server 2010 from SBS 2011 to a new Exchange Server 2016 on Windows Server 2016. You need to reverse the steps you did.
An example, you set at step 26 you did 'Set-OrganizationConfig -PublicFoldersEnabled Local'. If you want to reverse that type 'Set-OrganizationConfig -PublicFoldersEnabled Remote'.
Once you have reversed all steps delete the batch and continue with the rest you need to after Chapter 12 and uninstall Exchange Server 2010.
Let me know how things go?
Ok, seems to have gone well... up to uninstalling Exchange 2010 from SBS.
In step 7, you say that we have 3 arbitration mailboxes... then you say that if we're migrating to Exchange 2016 we don't need to remove them.
So do we need to do step 8 (Disable-Mailbox) or we skip it since we're going to Exchange 2016 ?
If you are migrating to Exchange Server 2016 you will see that the output shows that the arbitration mailboxes are on the new server. No need to disable them, skip step 8 and continue with step 9. If you still see any arbitration mailboxes that are not on your new server it could be those are from an earlier migration that was not completed the way it supposed to be but fixing that issue is not in this guide.
Me again...
Ok, did a rookie mistake when configuring ARRconfig... in the command line (ARRconfig config...) I put in the "remote" certificate and not the ''mail'' certificate...
Was wondering why my Anywhere access wasn't working from the outside !
Easy way to fix this ?
Actually, just found one of your documents :
https://server-essentials.com/support/arrconfig-an-error-occurred-while-configuring-iis-fore-more-details-check-the-log-a-specified-logon-session-does-not-exist-it-may-already-have-been-termina
Repaired binding to correct certificate :)