Forum Discussion
Solved
Unable to move from CU7 further
Hi all! Recently I've started having issues when upgrading Exchange 2019 721.2 (CU7) . I am not able to move past step 11 of 17 - Mailbox role: Transport service. I keep getting an error : The...
- Well, something in your setup is off as this normally should be straightforward. While I personally would want to work out the underlying problem, there is a point where it may take up too much time and redeploying it might be quicker, especially when you run hybrid and you have (automated, scripted) config procedures at hand. You could also run setup using the /Mode:RecoverServer switch to recover the server (replacing, same name) using the information from AD to speed things up; one of the things to do afterwards is getting the certificate on it.
What path you choose here is yours.
Sounds like a certificate issue. Did you try the following:
1) IIS Manager > Default Web Site > Edit Bindings > https
2) Check if SSL certificate is bound to "Microsoft Exchange"; if not, configure it so.
3) Re-run setup to upgrade
4) Post upgrade, reconfigure the 3rd party certificate
1) IIS Manager > Default Web Site > Edit Bindings > https
2) Check if SSL certificate is bound to "Microsoft Exchange"; if not, configure it so.
3) Re-run setup to upgrade
4) Post upgrade, reconfigure the 3rd party certificate
Hi , I've tried this approach last night. I didn't get too far. I think this helped to overcome the intial problem but then the next one showed up . Still in the "Front End" section. I've even followed some instruction on the net to completly remove IIS Management tools, but it was not able to finish the installation . Don't know why something that was an easy process before now got stuck and won't move forward.
Since this is a hybrid environment. Is building a fresh new Exchange and moving mailboxes to it something I should consider? Can it mess up hybrid config ? Any idea ?
Since this is a hybrid environment. Is building a fresh new Exchange and moving mailboxes to it something I should consider? Can it mess up hybrid config ? Any idea ?
- Well, something in your setup is off as this normally should be straightforward. While I personally would want to work out the underlying problem, there is a point where it may take up too much time and redeploying it might be quicker, especially when you run hybrid and you have (automated, scripted) config procedures at hand. You could also run setup using the /Mode:RecoverServer switch to recover the server (replacing, same name) using the information from AD to speed things up; one of the things to do afterwards is getting the certificate on it.
What path you choose here is yours.