Forum Discussion
Move from Staged Hybrid Migration to full Exchange Online
Every configuration involving dirsync, including password sync, requires you to keep an Exchange box for management purposes. Otherwise you will be in "unsupported" configuration. You dont have to follow the Microsoft recommendations on it, you can manage the objects just fine with other tools, but you riks being denied support.
Here's an example article that goes into more detail: https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises/
Ok, i will try one last time.
He wanted to sync users/passwords from his on-premise AD - yes, you can use AD Connect for that and no Exchange installation is needed for that.
He wanted to decomission his Exchange installation and still be able to sync on-premise users/passwords to Office 365 - yes, having only AD Connect is enough for that (although who would just sync users? Usually some other services like Exchange, SharePoint, OneDrive, etc. are used with these users).
He wanted to decommission his Exchange installation and be able to manage Exchange in Office 365 Admin Center > Exchange Online console - you can change some settings, but you can't change user settings that are synced from on-premise AD like SMTP addresses. You will get a read-only error and will have to change these settings locally in your AD and then sync them to Exchange Online. You can use PowerShell or AD Users and Computers console to change these attributes, but Microsoft is calling a supported setup if you leave one Exchange server on-premises and do such changes via Exchange Admin Center (or Exchange Management Shell).
I will type this ssssslllllllooooooooowwwwwwwlllllllyyyyyyy so you can understand it. There is NOTHING in his post that said ANYTHING about wanted to sync users. NOTHING. Only passwords. What seems to be happening now is that you may have realized that you have made a mistake but are too proud to simply bow out gracefully. Here is entire post
Good Day,
I have moved and finalized approx 60 mailboxes from Exchange 2010 On premisis to Exchange online.
Currently all mail clients are pointing to Exchange online, however mail is still being delivered on-premise as well.
The following article on decomissioning on-premisis has been helpful, however just need to get a plan solidified.
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx
Currently, no MX records have been changed to redirect mail permanently.
I would still like to use ADSync after the cutover to unify password management between on premise and online, however I would like to do all exchange managent from portal administration.
I would like to completely decomission on-premise exchange post cutover.
Can anyone share any info on whether the scenario outlined is possible at all and what I need to do to accomplish it?
Thanks
- BTW, you can clean up your Exchange Server Databases, shrink your Disks, etc. You only need a small VM after that, just in case you need to edit User Settings. Maybe you can migrate it to Azure and use Azure Automation to start it regularly for 30 minutes and than shut it down to save costs. Just to get a connect to your DCs.
OMG, you didn´t understand anything... He wants to stay with his local AD, so he needs ADConnect. But with ADConnect and not Azure AD Pure online, you will need to have an Exchange installation to edit your Exchange specific Attributes in your local AD, which then will get synced to AAD. If you have ADConnect, local AD is the leading Authentication Provider.
Hope this helps any new Readers, Oleg is absolutely correct with his statements.
- Ok ok guys! You’re just going back and forth here! Let’s just call it a day :)
Adam
