Also if there's somebody who know something about this, also can share solutions.įinally it wasn't necessary.

I'm thinking maybe is something about, when Install stops at first time somehow, installed something already and now is unable to continue becuase it detects something is not right installed. I tried numerous times, but none of them work since then, still the same error. I decide to move back and try again, but now in the install step, stops. Hybrid agent was downloaded correctly, then in in the install, ask me for login to Office365, and seemed to move to the next step, but something happen and it stops. At first I saw that progress was going on.

I was mounting a lab to make sure that changing from Classic to Modern is possible.Īs documented I removed the migration endpoint and migration batches.Īlso, this wasn't documented I changed the EWS url and Autodiscover url, due I think I didn't need them.įirst run, I chose Modern Hybrid Agent option. If that is a trusted 3rd party cert and those URLs are accessible to the client, it will be transparent to the end user. Yes, the subject name on the cert needs to match the client URLs. I just wanna know if there's something more to consider to be sure that this operation will be transparent for the user. Something like that with all services EWS, Autodiscover, Outlook Anywhere etc. Outlook Desktop client after we checked, is connecting by the local URL as it suppose to.Ĭhanging all services with an external URL would be enough to not encounter certificate errors in Outlook? Then, for the hybrid configuration we add the externarlUrl as documented but didn't change yet the internal one. So our client had something similar to this: This problem is something that happen frequently when our client didn't configure external URLs before. Im afraid of something that I show you below: The thing is that we are afraid that changing the certificate could provoke that users using Outlook client could be notified about this change in a popup everytime they open Outlook desktop client or there's a desconnection. I will try to explain better our situation. First, thanks for all help I'm receiving.

Exchange hybrid modern authentication