Forum Discussion
Remove On Premises exchange Hybrid and go fully Online
Now after updating MX,CNAME and TXT record you can remove the hybrid config (https://www.agileit.com/news/remove-hybrid-configuration-exchange-server-2010/) and decomm your server.
DeepakRandhawa
You had post a link for how to license a Exchange Hybrid Server. The License now is offered in the HCW (Hybrid Configuration Wizard). So I have to finish the HCW and implement a hybrid Exchange Organisation. Is it not possible to install the Exchange Server only for Management and without a hybrid Installation?- you don't have to configure hybrid, just run the HCW, license the server and close the wizard.
I'm getting ready to migrate my Exchange Server 2013 to Exchange Online in about 8 weeks. What if I don't implement Azure AD Connect, and simply manually configure the passwords online to match the passwords in on-premises AD? With only about 30 users, it would be easier for me to simply configure the same passwords in Azure AD manually (for the convenience of my users) than it would be to have AD Connect take care of that, but then have to continue maintaining the on-premises Exchange Server. Do I have to implement Azure AD Connect for some reason? And if not, and I don't, can I then do all my email admin (e.g. aliases, email addresses, hide from address book, distro groups, etc.) online?
- Are you keeping your on premises AD?
Yes, we will keep on premises AD. I would keep Exchange Server on premises except given our size and the new hardware requirements for Exchange 2019, and our upgrade cycle, it's now more cost-effective to move Exchange to the cloud.
- Well, the whole reason to have passwords is that they are secret and admins shouldn't know them, because then you can't prove if something was done by a user or ad admin who knew the password. That being said, 10 years ago i knew passwords of every user in my company :) But we have long ago moved away from that practice. If you want, you can do that. I suppose you also want to manually export and import all the emails as well (PST or something). This will take some time, but with 30 users maybe not so long, especially if they don't have tons of emails (with manual migrating they would have to wait for the moving, this is disruptive). And then you may ask them to change their passwords. But then you will have two passwords for every user, one in local AD and one in Azure AD. Unless you plan to get rid of local AD along with Exchange 2013.
Thanks wroot-- good to know.
I'm actually doing a cutover migration for the mailboxes. There are only 30 or so, but the cutover migration seems the more efficient/less painful approach.
