Symptoms
After the January 2023 Exchange Server 2016 Security Update is installed on a computer that’s running Windows Server 2012 R2, some of the Microsoft Exchange Server services that are in automatic startup mode might not start after the server is restarted. Additionally, the following event is logged in the event log in the System channel:
Log Name: System
Source: Service Control Manager
Date: 1/19/2023 3:22:51 AM
Event ID: 7022
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EXCHLAB01.contoso.com
Description:
The Microsoft Exchange Active Directory Topology service hung on starting.
Cause
This behavior occurs because of a timing issue that exists between the Microsoft Exchange Active Directory Topology Service (MSExchangeADTopology) and the WMI Performance Adapter (wmiApSrv) service on Windows Server 2012 R2.
Resolution
To fix this issue, install the following security update:
Workaround
To work around this issue, use either of the following methods.
Workaround 1
Add the WMI Performance Adapter service to the dependent services of the Microsoft Exchange Active Directory Topology Service. To do this, run the following PowerShell commands:
-
$dependentServices = (Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\MSExchangeADTopology).DependOnService
-
Set-ItemProperty -Name "DependOnService" -Path HKLM:\SYSTEM\CurrentControlSet\Services\MSExchangeADTopology -Value ($dependentServices + 'wmiApSrv')
Workaround 2
Start the services after the computer restarts. To do this, run the following PowerShell command:
-
Get-Service -DisplayName "Microsoft Exchange*" | Where-Object {$_.Starttype -eq "Automatic" -and $_.Status -ne "Running"} | Start-Service
Note You can also run the command automatically after a system restart by using Windows Task Scheduler.
