[Note] This thread was originally posted on MSDN. As the MSDN Exchange Dev forum mainly focuses on developing issues and the TechNet Exchange forums for general questions have been locked down, we manually migrated this one to Microsoft Q&A platform to continue the troubleshooting.
We just noticed that all of our Exchange 2016 servers (running on Win 2012 R2) will no longer launch as administrator.
When we right click the EMS and select "run as adminstrator", the shell window opens up as "Administrator: Serveraname.domainname but, when the 2nd "Verbose: Connected to Servername.domainname" appears, the shell goes to "Machine: Servername.domainname"
We discovered this when we tried to run a command "Get-Inboxrule" and it said the mailbox did not exist, which it does.
We had 2 things happen this past weekend - 1st, we updated our external certificate and 2nd, we installed CU18 over the weekend. We checked the new cert and it's assigned to SMTP, IIS, IMAP, POP on all exchange servers. I didn't think the EMS was tied to an external cert, only the Exchange certificate (Which does not expire until late next year)
Anyone heard of any issues with CU18 causing this issue? We have 1 issue with CU18, users who log into OWA to access a shared mailbox can no longer download a file (it points to O365, and we are not setup for Hybrid), so we are waiting for the next CU release to fix that issue (we have a work around until then).
Thoughts?