Comments
2 comments
-
You could try checking the WMI namespace permissions for
root\CIMV2and make sure the account still has the required access after the Windows Server 2025 upgrade. Also, checking the WMI service and related event logs may help indentify what changes. -
Turns out our problem was caused by a missing privilege for all user accounts after an OS upgrade. “Access this server from the network” was missing.
This issue has been resolved.
Add comment
Please sign in to leave a comment.
We are testing upgrading the OS on our SQL Servers to Windows Server 2025, doing an in-place upgrade of the OS (SQL Server version is not changing.)
After doing the update, we had to re-do the permissions for the Monitor service account, as we want to avoid adding it to the local Administrators. Despite setting the permissions as listed in the Monitor documentation, the account was not able to access the WMI root and CIMv2 folders. Adding the account to the local Administrators worked around the issue.
Lastly, the “wmic useraccount…” command to get the SID of the Monitor service account did not work in Windows Server 2025, we instead had to use Powershell (get-aduser -identity “service account” | select-object name,sid"