Blog Post

Exchange Team Blog
1 MIN READ

Re: Re-release of November 2024 Exchange Server Security Update packages

daniel299's avatar
daniel299
Copper Contributor
Jan 24, 2025

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-SetupService

These 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

 

Updated Jan 24, 2025
Version 2.0

5 Comments

  • Nino_Bilic's avatar
    Nino_Bilic
    Icon for Microsoft rankMicrosoft

    We do not expect that this is related... there are cmdlets that are registered only during Exchange setup (this has always been the case).

    • cvanoort2's avatar
      cvanoort2
      Copper Contributor

      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).

      • Nino_Bilic's avatar
        Nino_Bilic
        Icon for Microsoft rankMicrosoft

        I just updated the blog post with our current understanding of the failure (we did reproduce this). The issue seems to be related to January .NET update having been installed, but the server was not rebooted after installation was completed.