AD Connect - sync AD information and not Exchange info - using CodeTwo Migration tool

I want to use AD Connect only to sync AD information and not Exchange info for I'm migrating on premise Exchange to Office 365, however, I'm using a 3rd party tool to migrate.. This being CodeTwo Office 365 migration..  So.. Here's where I'm at..  AD Connect synced users to Office 365 Online Exchange, however, the mailbox isn't created yet for it assumed I'm migrating via AD connect and not my 3rd party tool.. So.. On the user details page I get the below message.  I found a few articles stating to not sync the ExchangeGUID, however, the accounts are already synced.  So.. What should I do?  

This user's on-premises mailbox hasn't been migrated to Exchange Online. The Exchange Online mailbox will be available after migration is completed.
gopher_49Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sajid Shaik MSr. System AdminCommented:
check this best article

regarding the same

https://www.codetwo.com/kb/msexchmailboxguid-problems/

al lthe best
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Adam BrownSr Solutions ArchitectCommented:
AD Connect isn't a migration tool. It's a Directory Sync tool that copies attributes from Onprem DCs to Azure AD. This allows you to have Single Sign On, password sync, and other great features. Not really sure why CodeTwo has issues when you sync the msexchmailboxguid attribute, but whatevs. Sajid's link gives specifics on how to block that from happening. Note, though, that it requires you to delete all existing users for it to work.

That said, onprem Exchange to O365 migrations are usually best handled with the migration tools available in O365. Third party tools add cost and complexity that is rarely justified, because they don't significantly improve migration speed or ease.
1
MaheshArchitectCommented:
stop AD connect synchronization schedules
Set-ADSyncScheduler -SyncCycleEnabled $false

Open in new window


Then delete all already synced objects in cloud forcefully by running below command
Get-Msoluser -All | remove-Msoluser -Force
Get-Msoluser -All | remove-Msoluser -RemovefromRecycleBin -Confirm:False

Open in new window


change AD sync configuration to exclude exchangeguid attribute from Azure AD Connect and resync AD connect
https://www.cloudsupport.help/hc/en-us/articles/115000721848-Removing-msExchMailboxGUID-attribute-from-AD-synchronization

Also note that with this attribute removed, you won't be able to do reverse migration in case if required with MS native tools, check with 3d party vendor if he can provide that functionality as well
0
RoninCommented:
Agree with Adam Brown,
Microsoft provides you a detailed, excellent guidance.
The most important resources are:
1. Microsoft Deployment Assistant.
2. Ways to migrate to Office365.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.