Forum Discussion
Problem with EMS console, Exchange Toolbox console and permission to serialize tokens
Hi,thank you ror your relpy.
- Why?
We use Ex2016 on WS22016. We setup WS2025 with EX2019 as temporary Exchange server to upgrade it to Ex SE (as suggested in the article below). Everything should be simple, because Ex SE is an unusual CU for Exchange 2019 (as described in this article): Why “in-place upgrade” from Exchange 2019 to Exchange SE is low risk | Microsoft Community Hub
- Disabling antivirus software doesn't change anything. Of course, all exceptions have been added to the antivirus software (we use the built-in Defender and Palo Alto Cortex).
- I used Healtchecker of course. No errors.
Seiun That article does not say you need to install Exchange Server 2019 first and then move to Exchange Server SE. If you were already running Exchange Server 2019 then an in-place upgrade would make sense. But for a fresh install, no that is the wrong path.
You cannot use multiple AV solutions at the same time. So, if you are using PAC, you need to disable Defender. And if you're happy with Defender, there's no reason to run PAC.
As Health Checkers runs in the EMS and you're not able to access the EMS, how did you run it?
Did you check to make sure the proper services and app pools are running on your server?
What's in your IIS logs and event logs? Any errors?
Have you enabled Certificate Signing in PowerShell - https://aka.ms/HC-SerializedDataSigning
Have you verified your environment can use Extended Protection, which is enabled by default?
