We have two Windows Server 2016 servers that are not discovered as a Windows Server class instance on our SCOM 1801 environment. They are only discovered as “System Center Managed Computer (Server OS)”.
There are no errors in their operations manager event log and we never had this issue before with other Windows Server 2016 servers.
One thing to note is that both of the servers are Domain Controllers.
We have tried to use the SCOM 2016 agent and tried to use HSLockdown.exe /A “NT AUTHORITY\SYSTEM” but this doesn’t help to solve the issue.
The Windows Server discovery is not coming through.
Anyone has a solution for this issue?
I don’t have DCs running 2016 near to me. – But usual 2016 servers are discovered fine. Have you installed / updated the Management Packs for 1801?
In my lab I have 10.0.21.0 for Windows Server 2016 and 1709+ and 7.5.8501.0 for Windows Core Library
What are urs?
I believe you need to install the agent as domain admin, and then run it as Local System with the HSLockdown that you mention above (I’ve not actually got round to doing it yet due to reluctance from our AD Team!). I’ve got the same version management packs as Ruben above and normal 2016 servers are discovered fine, so this must be because they’re domain controllers.
Sorry that doesn’t help much, but if you fix it please update what the solution was 😀
We have installed the latest version (10.0.21.0) of the Windows Server 2016 and 1709+ management pack.
And we still have these two Windows Server 2016 Domain Controllers that won’t get discovered as a Windows Server only as “System Center Managed Computer (Server OS)”.
Yesterday we added two other Windows Server 2016 Domain Controllers and they have been discovered succesfully as a Windows Server 2016 Operating System and Server object.
What could be causing this issue?