Jump to content


FromTheUnderground

Computer with agent showing as Not monitored

Recommended Posts

I am taking over an instance of SCOM 2012 R2 and running into issues when trying to add new machines to monitor. I go through the Discovery Wizard and choose the specific machines I want to monitor. The agent gets installed; I confirmed this by logging into each of the machines. After the agent is installed, the Health state stays at Not monitored. When I run Get-SCOMAgent in Powershell, those same machines show Uninitialized under the HealthState column. The machines were added roughly 15 hours ago.

 

Am I missing something? Are there specific things I should be looking for in the log files?

 

Thanks in advance.

Share this post


Link to post
Share on other sites

Try this:

 

On one of the systems that are not showing as monitored, stop the Microsoft Monitoring Service (aka the SCOM Agent), and then rename the HealthState folder, and then restart the Agent.

 

The Health State folder will re-generate the files/folders within. It may start out with 11 folders/objects, but should eventually contain 13. There will be 2 folders with "temporary files" in the name (I can't remember the full name). This will normally be in succession (i.e. "1",, "2"). If there is an issue, then one of the folders will disappear and be re-created constantly; and thus increasing the number each time.

 

Start with that, and let us know.

Share this post


Link to post
Share on other sites

Hi AdinE,

 

I tried the steps you mentioned and all the folders were recreated when I stared the Agent service again. Still the machines show as No Monitored.

 

I decided to do some more tests and found that I am only having this issue with systems running Server 2012 R2. All other systems, Server 2008, 2008 R2, and 2012 all connect up and are monitored without any issues. I verified the 2012 R2 management pack was imported and available.

Share this post


Link to post
Share on other sites

FromTheUnderground,

 

Can you try the following.

 

- Uninstall the Windows Server Management Packs

- Uninstall the SCOM Agent from the affected system(s)

- Delete (or re-name) the Health Services folder

- Re-install SCOM Agent

 

By doing this, I want to see if the issue is with the Agent itself not reporting/showing as 'Healthy', or if it's something from the Management Pack.

Also, can you let us know if the Windows Server 2012 R2 system(s) are running/configured with any Server Roles?

Share this post


Link to post
Share on other sites

I think I have it working now. Under further investigation, I found there was a SCOM update that had not been applied yet. Once I installed that update, all my 2012 R2 servers started getting monitored.

 

Thanks for your help with this.

Share this post


Link to post
Share on other sites

Glad to hear it is working.

 

Maybe for the benefit of everyone else, can you specific what update it was (i.e. was it a SCOM UR that wasn't applied, or an OS patch, etc.)? If it was an OS patch, maybe provide the KB number so that it can be used for reference?

 

Thanks.

Share this post


Link to post
Share on other sites

Hi,

 

I have the same problem like "From the Underground"

KB2965445 hasn't fixed my problem. I see NO ERRORS on client or server. Very strange!

It's a new installation of SCOM 2012 R2 with UR3

 

All Clients will stay in "Not monitored". I also tested with cleaning the health state.

Nothing changed for me.

 

Firewall are disabled on clients and management server!

HealthState InMaintenanceMode
----------- -----------------
Uninitialized False

 

 

Any ideas? How can i troubleshoot this problem?

 

Thanks for your reply,

 

Mav

Share this post


Link to post
Share on other sites

Hi Maverick_1980,

 

Can you first confirm the state of your Management Server(s)? Let's start with making sure you main SCOM system is functioning correctly.

 

If you want, you can even revert back, and uninstall any SCOM Agents, Management Packs you imported, etc. so that we are only working with the SCOM Management server(s), as a starting point.

 

Can you also provide additional information about your setup/installation? For example, is it a single server? Do you have SQL on a dedicated server, is SQL clustered, how many Management Servers do you have? Did you install SCOM Reporting? The Web Console? ACS? and so forth.

Share this post


Link to post
Share on other sites

Hi AdinE,

 

it's an standalone installation (Version 7.1.10226.0) with installed Web- and Operation Console. Reporting Services are not installed. The database has been installed on a dedicated server. It's an shared Microsoft SQL server 2012.

SQL is not clustered!

 

I have uninstalled Management Packs and SCOM Agents.

Share this post


Link to post
Share on other sites

OK, so the first thing you should do is reboot the Management Server, then open the Console and check the health status of the Management Server. We want to ensure that it is green. You should also confirm that the Data Access Service Account (DAS) has the correct permissions on the SCOM Management Server.

 

See the following TechNet article for information on account access: http://technet.microsoft.com/en-us/library/hh457003.aspx.

Share this post


Link to post
Share on other sites

Now i have reset the environment.

Everything is now installed on one system. DB and all components of SCOM.

SCOM Management Server is now healthy and also the Management Agents!

I have imported MP from Windows Server 2003 to Windows Server 2012 R2

 

But how can i monitor for example CPU and RAM usage of a system?

Do i have to move a computer account to a template with counter information?

 

I only have to import the MP? That's it?

Share this post


Link to post
Share on other sites

OK, that's good that everything is reset, and the Management Server is healthy.

 

Quick point, only import the Management Packs for the technology that you are using (and actually want to monitor). For example, if you are not using Windows Server 2003 in your environment, then don't import that MP (as it adds more work to SCOM and the Agents to process).

 

So, un-import any MPs that you don't need. I'd suggest to only import the Windows Server OS management pack into the environment first, and as mentioned, only for the OS version you want/will monitor. Now, you may have to import previous OS version DISCOVERY MPs, but you don't have to import the MONITORING MPs.

 

With the Windows Server (assuming 2012/R2) MP imported, move onto installing the SCOM Agent on one or two servers. With the Agents installed, wait a little while for them to report back to SCOM. Within the Agent Managed area, they should report back as "green" or healthy in a little while.

 

If they report back as healthy, wait a while longer, and check it periodically. See if it changed from Healthy to Un-monitored. If it does, you can check the state/status to see when (and hopefully some details as to why) it changed. You will also want to ensure that the Agent Action Account used during the discovery and Agent installation has the required rights on the system. Within the MP documentation, it will tell you what security permissions are required for that specific MP, etc. So take a look at that as well.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...