I have a few older servers still using SnapManager rather than SnapCenter, and the critical security update that Microsoft released a few days ago (KB5001779) completely breaks SnapManager compatibility - backup jobs no longer run, and console reports "Unable to determine Exchange virtual server group status before SnapManager operation" straight upon opening. This is happening both in Exchange 2013 and Exchange 2019, same error. I have opened a case with support, but while I'm waiting for a response, has anyone else run into this, and is there a workaround?
[04/16 12:59:23 754] Getting dash board info... [04/16 12:59:23 754] Calling PowerShell to get current exchange server... [12:59:23.754] [PowerShell Cmdlet]: get-exchangeserver -status -identity <Exchange server name> [04/16 12:59:23 754] [PowerShell Cmdlet]: get-exchangeserver -status -identity <Exchange server name> [12:59:23.911] [Remote PowerShell Cmdlet Error]:The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode. [04/16 12:59:23 912] [Remote PowerShell Cmdlet Error]:The syntax is not supported by this runspace. This can occur if the runspace is in no-language mode.
Please verify if you are seeing the same errors in your environment , it is an indication that Exchange Powershell cmdlets are failing.
For what it's worth, I've been advised by support to uninstall the security update. Since that would open the servers up to severety 9.8 remote code execution vulnerabilities, I'd rather forgo backups for a while, or even look for an alternative solution in general.