Hi everyone, I recently pushed some SCOM agents to servers using a script that uses the powershell command, "install-agentbyname." This script will read hostnames from a text file and automatically install the agent onto all servers listed in the text file. After the script loads the Operations Manager Snap-in and connects to the RMS, the command that reads the hostnames from the text file and pushes the agents is: gc c:\scripts\agents.txt | foreach {install-agentbyname -Name: $_} The issue is that the agents that were installed are not monitoring all parts of the server. For example, in the Monitoring > Computers view, the Windows Operating System column is showing as "Not monitored" for those servers. Also, in Health Explorer, "Windows Computer Role Health Rollup" (under Entity Health > Availability) is showing as Not Monitored. Interesting thing is that under State Change Events for Windows Computer Role Health Rollup, it shows that the state is "Uninitialized" with context, "The monitor has entered maintenance mode or was requested not to change state when it had exited maintennace mode." I've tried performing a repair, but the Windows OS still does not start showning as monitored. Has anyone seen this before or have any ideas what could be the issue? Also, I don't think pushing the agent via a Powershell script was the cause of this, but I was just throwing it out there anyway. Thanks!

It could be that the servers are still in pending management. It could be that you haven't imported the server operating system management pack. What is the health state of the agents? Gray or Green?Microsoft Corporation

Hi Dan, So there's been a little miscommunication on our end. Apparently these servers were installed as Windows XP systems. We don't have the Windows XP MP installed since we only monitor server systems, so SCOM is working as expected. Thank you for your reply and sorry for the confusion.