Today we are re-releasing the November 2024 SUs for Exchange Server. The original release of these SUs (released on 11/12/2024) introduced an issue with Exchange Server transport rules stopping after...
Updated Jan 28, 2025
Version 11.0
Blog Post
One idea Nino_Bilic LukasSMSFT rennstrecke
According to the german forum:
Perhaps "add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.Setup -ea SilentlyContinue" in servicecontrol.ps1 is not done correctly on non-English systems after January Updates. Perhaps with the mentioned assembly error.
The snapin brings the commands CMDlets "Stop-SetupService" und "Start-SetupService" into the Powershell. I can't test it at the moment, perhaps someone can test it ad-hoc.
So it would explain that a Alias creation workaround mentioned in the German post makes the setup complete successfully.
On windows server 2016 with Exchange Server 2016 without January patches it worked an the CMDlets are available in Exchange Powershell.
Nino_Bilic
Microsoft
MicrosoftYup, thank you; we are aware of the German post and managed the repro the issue internally (after a few customer escalations). Will provide an update once we figure out what is going on (I don't think we really understand yet what is it with January Windows updates that breaks us).
A bit off topic but possibly related to January Windows updates.. We got a few complaints that search in outlook fails after Jan Win updates installed in Ex2019 servers. These servers do not have November SU. Never before had any kind of issues with search or indexes.
Hi, I'm a contributor of the mentioned German forum and an author in the above linked thread.
Maybe it has something to do with the script %ExchangeInstallPath%\bin\servicecontrol.ps1 and these two cmd-lets:
Stop-SetupService Start-SetupServiceThese cmd-lets werent recognized on my system.
I had to create two aliases.
New-Alias Stop-SetupService Stop-Service New-Alias Start-SetupService Start-Service- Nino_Bilic
We do not expect that this is related... there are cmdlets that are registered only during Exchange setup (this has always been the case).
If it's any help, we have an English install of Windows Server 2019 and English install of Exchange 2019. We don't have those aliases either and did experience the error on the server (we already had applied January 2025 patch tuesday updates before trying to install Nov 2024 SUv2).
