VMM Agent Not Monitored By Operations Manager

I am getting this alert 
VMM Agent Not Monitored By Operations Manager
I have VMM 2012 sp1 and SCOM 2012 sp1 so please kindly tell me the solution.

For VMM Agent Not Monitored By Operations Manager, Please, Send if there is error in event viewer
Also Check below link to help you in Fix your Issue
http://blogs.technet.com/b/operationsmgr/archive/2012/01/23/potential-issues-with-vmm-2012-opsmgr-integration.aspx
For Configuration of Operation Manager to monitor VMM, Refer to below link
http://www.systemcentercentral.com/configuring-pro-integration-between-opsmgr-2012-and-vmm-2012/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer".

Similar Messages

  • Can you connect multiple VMM Instances to a single Operations Manager 2012/R2 Deployment

    Hi Everyone,
    Just seeking some clarification around the Operations Manager and Virtual Machine Manager integration.  Is it possible to integrate multiple Virtual Machine Manager 2012 Deployments with a single Operations Manager 2012 Deployment or is the connection
    between VMM and OM a 1:1 relationship?
    Thanks in advance,
    Hayden

    Yes VMM and OM 1:1 is supported. 
    Theoretically many VMM can integrate with single OM but its not very realistic and well tested as it puts several configuration and performance constraints on each of the VMMs.
    I’d recommend installing SCOM (inside a VM is fine)  per VMM if possible .
    [Disclaimer] This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all.

  • Disable monitor in Operation Manager for 1 host

    Hi,
    I need to create a poweshell script that disable a monitor for a given host.
    With the Disable-SCOMMonitor, I managed to disable it for a class, not an individual host. It looks feasable since you can disable it for a specific host of a class in the console.
    So far I've got:
    $Host =  Read-Host "Enter computer name"
    $MonitorName = "Total CPU Utilization Percentage"
    $Monitors=Get-SCOMMonitor -ComputerName $strComputerName | where {$_.DisplayName -eq $MonitorName}
    $MP = Get-SCOMManagementPack -DisplayName "BMA - Override - Orchestrator_Generated" | where {$_.Sealed -eq $False}
    foreach ($Monitor in $Monitors) {
         $Instance3 = Get-SCOMclass -name $Monitor.target.identifier.path | Get-SCOMClassInstance | where {$_.Path -eq $Host}
         Disable-SCOMMonitor -Instance $Instance3 -ManagementPack $MP -Monitor $Monitor -Enforce
    This does not return any error (besides when $Instance3 is empty, but that's an easy fix), but does not disable the monitor either...
    I would appreciate some help to get that working :)
    Thank you !

    Hi,
    I am a little confused, as you have the specified the monitor name as Total CPU Utilization Percentage, why are you still try to get an array of monitors?
    If you want to disable one monitor for a computer, please try follow code, you may need to change some parameters according to your environment:
    $Host = Read-Host "Enter computer name"
    $MP = Get-SCOMManagementPack -DisplayName "BMA - Override - Orchestrator_Generated" | where {$_.Sealed -eq $False}
    $Instance = Get-SCOMclass -displayname "The class name for the instance“| Get-SCOMClassInstance | where {$_.Path -eq $Host}
    $Monitor = Get-SCOMMonitor -DisplayName "Total CPU Utilization Percentage"
    Disable-SCOMMonitor -instance $Instance -ManagementPack $MP -Monitor $Monitor -Enforce
    Hope this helps.
    Regards,
    Yan Li
    Regards, Yan Li

  • Cannot monitor Windows Operating Systems

    In the process of attempting a SCOM 2012 R2 deployment, I cannot get SCOM to monitor the Windows systems on which the management agent has been deployed.  I have installed the "Microsoft Windows Server" MP, as well as a bunch of other "server"
    related MPs (i.e., DNS, AD, etc.)
    Selecting the "Microsoft Windows Server" entry in the monitoring view shows all the entries I would expect to see, but none of the selections show any data being collected.  All of the Windows Updates have been applied and the systems rebooted.
    I have searched this forum as well as the web, and haven't found anything that works.  I'm wondering what I've missed.
    BTW, the SCOM server is clearly having issues (see my other "Log on locally" thread) but I don't know if there is any connection.  In other words, my SCOM deployment may need to be done over.  (Although it is unclear to me just what tables
    and other information would need to be removed from the SQL database.)
    - Mark

    Hi,
    For the issue that Windows operating system not monitored, the cause may be not importing the Windows Server based OS management pack:
    System Center Management Pack for Windows Server Operating System
    http://www.microsoft.com/en-us/download/details.aspx?id=9296
    Windows Server base OS monitoring is not a part of the default management packs shipped with SCOM, we have to download and import it.
    In addition that, this issue can occur because the new agent has the same NetBIOS name as a previously installed agent. When the agent is deleted from Operations Manager, the grooming of the deleted agent is hard coded to occur after two days. Therefore,
    the agent is not immediately groomed out of the database completely. 
    To work around this issue after the old agent is deleted from the console, wait three days, and then add the new agent to Operations Manager. Alternatively, make sure that two full days have passed and then add the new agent to Operations Manager.
    Quote from:
    http://support.microsoft.com/kb/979387/en-us
    Hope this helps.
    Regards,
    Yan Li
    Regards, Yan Li

  • Agents stopped repoting to the manager server

    Hi,
    I have two forests which connected via two way trust relationship. (lets call them A.domainA & B.domainB)
    My MS server is a member server on Forest A.domainA and there are some servers on domin A.domainA which reports It.
    Additionally there are some servers in domain B.domainB that reports to the MS server on domain A,DomainA.
    After upgrading one of the Domain Controllers in domain B, All the agents stopped reporting to the MS. (the servers from domain A still reports)
    I verified the trust relationship and it seem to be working fine.
    What could be the reason for this kind of problem ? What should I check to understand the root cause of the problem ?
    Kobi  

    1) I suggest that you should check the event log of the agent machine especially the operations manager event log and check any error message.
    2) Open the operations console, go to monitoring workspace --> Operations Manager --> Agent Details --> Agent Health state --> Select the agent machine and click flush health service state and cache
    Roger

  • Manually Installed Agent is not showing up in the Operations Manager Console Under Pending Management.

    Hi Community,
    I submitted this question because I'm a bit stuck with SCOM 2012 R2, I'll try to explain briefly what is happening right now in my environment,  we have a DEV SCOM Deployment in which all the roles are installed in a single server, this servers is a
    VMware machine running Windows Server 2008R2.
    The Initial installation of the SCOM Operations Manager and all the other components was not performed by me but by a co-worker, unfortunately he doesn't remember much about the initial configuration. So i had to pickup where he left things about a year
    ago, neither of us are SCOM experts, and we have almost no previous experience with previous versions of this application.
    Now the problem that I'm facing is the following, all the DEV Servers are Domain Controllers and one of the indication within the "Guide for System Center Management Pack for Active Directory for Operations Manager 2012" states the following
    Configuration
    Supported?
    Agent-less monitoring
    No
    After my first review I notice that our servers were being monitor by agent-less mode and given the above statement from the Operations Guide the only way that we could ever get those domain controllers monitor by SCOM would be by installing the agent on
    each server, so I read somewhere (Can't remember where) that in order to install the agents in all the servers I should first remove them from the Agent-less node, which I did. Then I tried to use the discovery wizard to get the agent install in all of them
    but it didn't matter how many times I try the servers never show up.
    I read in a Tech Net Article that you had to modify the security settings so SCOM would let me decide if I wanted to approve it or not.
    --> http://technet.microsoft.com/en-us/library/hh212853.aspx
    I performed the suggested steps from the article but still the servers were not showing up, not even if I run the Discovery wizard, so I decided to go and perform the installation manually in a couple of servers I was able to install the agent in one of
    the Domain Controllers, I configured the agent to use a service account that has Domain Admin rights. An hour after I installed the agent I went back to the Operations Console Manager and I check under Pending Action but the Server was not showing up. So i
    went back to the Internet to try to find out if someone else had experience the same problem, and in one website some mentioned that if the servers were not showing up it was probably because they were still register in the SCOM Database, now I have no idea
    of how i can check that or How can i remove them from there to have them available again, but what troubles me the most is that even after i installed the agent manually the server were not being recognize.
    I went to the Event Viewer and I found one particular event that caught my attention, see below :
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          6/12/2014 12:48:19 PM
    Event ID:      11551
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MyManagementServer
    Description:
    Computer verification failure for Machine Name: MyManagementServe is 0x800706BA. The RPC server is unavailable.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11551</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-12T16:48:19.000000000Z" />
        <EventRecordID>1945680</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>MyManagementServer</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MyManagementServe</Data>
        <Data>0x800706BA</Data>
        <Data>The RPC server is unavailable.</Data>
      </EventData>
    </Event>
    Not sure if this is related to the problem that I'm facing right now, but , I make sure that the RPC Services were running and also the related dependencies too. There's no Firewall enable in any of the servers and DNS seems to be working properly.
    Ports 135 / 5723 are open and listening so since I ran out of ideas, I would like to know if some of the experts in this field could perhaps give me some guidelines.
    There's one caveat that I haven't mention yet and that is related to SQL, I checked and my user just has read access to SQL i'm not sure if that could affect this but i think is worth mentioning.
    My main goal is to have all the servers showing up in the Operations Manager Console.
    So thanks all in advance !
    Oscar Loria

    So you can ping and nslookup from your ms to these agents and vice versa right?  I wouldn't do a manual install, I would push the agent from the management server.  You can uninstall the agent manually, or use cleanmom to get rid of them.  Then
    do an install from the console.  When you initiate the install from the console (management server), should it run into any issues it will dump out an error which will give you an idea of where the problem may be.
    From Holmans post on this:
    e MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on 
    computer “servername.domain.com” 
    Operation: Agent Install 
    Install account: DOMAIN\account 
    Error Code: 800706BA 
    Error Description: The RPC server is unavailable.
    The MOM Server could not execute WMI Query "(null)” on 
    computer “servername.domain.com” 
    Operation: Agent Install 
    Install account: DOMAIN\account 
    Error Code: 800706BA 
    Error Description: The RPC server is unavailable.
    8004100A 
    800706BA
    1.  Ensure agent push account has local admin rights 
    2.  Firewall is blocking NetBIOS access.  If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed.  We need port 135 (RPC) and the DCOM port range opened for console push through a firewall.  
    3.  Inspect WMI service, health, and rebuild repository if necessary 
    4.  Firewall is blocking ICMP  (Live OneCare) 
    5.  DNS incorrect 
    http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

  • VMM Agent is not monitored by OPSMANAGEr

    Hello Sir,
    Could you please help us to fix this issue:"VMM Agent is not monitored by OPSMANAGEr"
    From few agents we are getting the above alert. When we check the agent status in administration==> Agentmanaged it is showing as healthy.
    We have tried the below steps on the agent server but no luck.
    Restarted VMM Agent Service
    Restarted SCOM agent service.
    I have gone through the below blog:
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/103d93a8-be24-4c30-8061-428da07369fe/scom-2012-alert-system-center-2012-virtual-machine-manager-vmm-agent-monitored-by-opsmgr?forum=virtualmachinemgrproscintegration
    Instead of disabling the alert, please let us know is there any work around to fix.
    Regards,
    Sanjeev Kumar N

    Hi,
    Please refer to the link below:
    SCOM 2012 Alert - System Center 2012 Virtual Machine Manager VMM Agent Monitored By OpsMgr
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/103d93a8-be24-4c30-8061-428da07369fe/scom-2012-alert-system-center-2012-virtual-machine-manager-vmm-agent-monitored-by-opsmgr?forum=virtualmachinemgrproscintegration
    It seems that the only workaround is disable the alert.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SC 2012 R2 - Operations Manager - All servers except Management server show Not Monitored

    Hi all,
    I have installed System Centre 2012 R2 - Operations Manager and configured on our Domain and running without a problem. I used the VHD available here: http://www.microsoft.com/en-gb/download/details.aspx?id=40844
    I have created a single VM called VM1 and installed Windows Server 2012 R2. VM1 has also been joined to our domain.
    The management packs for Server 2012 R2 have been downloaded to the SC2012 OM.
    I have discovered and added in VM1 server to the OM Server. I can see the agent running in VM1 (Microsoft Monitoring Agent) but it always shows as "Not monitored".
    I have restarted both servers, found the guide regarding "Greyed out or Not monitored" but the steps outlined have not resolved the issue.
    The account used in the test domain to install and run the service is a Domain Admin account. The test domain network also disabled the firewall on all member servers.
    I have stopped all services on the OM server, renamed the "Health Service State" folder as suggested but nothing has resolved the issue.
    Could anyone please help me? If more information is needed I would be happy to provide it.
    Thanks in advance,
    Graham

    Thank you all. After coming into the office today I checked the event logs on VM1. All afternoon I had been getting 4 events every 15 minutes;
    Three x 21023 - OpsMgr has no configuration for management group SCOM12 and is requesting new configuration from the Configuration Service
    And one error, 20070 The OpsMgr Connector connected to SCOM12.test.local, but the connection was closed immediately after authentication occurred.  The most likely cause of this error is that the agent is not authorized to communicate with the
    server, or the server has not received configuration.  Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
    However at 00:04, I can see an event log 21019 - OpsMgr has returned to communicating with it's primary hostSCOM12.test.local and since then regular Health Service logs.
    I checked in OM and now it is showing as Healthy and monitored - I guess this just needed a lot of time to configure itself? Is this normal behaviour?
    I also checked VM1 TCP 5723 which it says was not open (the firewall is off on the server however it is working in OM.
    PS C:\PSScripts> Test-Port -computer VM1 -port 5723 -tcp
    Server   : VM1
    Port     : 5723
    TypePort : TCP
    Open     : False
    Notes    : Connection to Port Timed Out
    Thanks again for your help. If it goes again I shall create a new post.

  • SCOM 2012 SP1 - Windows operating system is not monitored in a SCOM agent

    Hi All,
    I have an agent with windows 2012 operating system that i am trying to monitor.
    At the "Windows computers" view the "Windows operating system" column is empty ("Agent" column is Healthy).
    Why SCOM doesn't recognized that the agent have operating system?
    Please help.
    Thanks.
    TechNet

    Hi,
    On workgroup servers, you have to make sure you've used the momcertimport tool to import the certificate into the SCOM service.
    In addition, I would like to suggest you go through the below article to monitor non-domain servers with SCOM:
    Monitoring non-domain members with OM 2012
    http://blogs.technet.com/b/stefan_stranger/archive/2012/04/17/monitoring-non-domain-members-with-om-2012.aspx
    Hope this helps.
    Regards,
    Yan Li
    Regards, Yan Li

  • All Agents Greyed Out or Not Monitored

    Hello,
    I am running SCOM 2012 R2.  All of my clients were re-imaged (Over 500) during the summer.  Each image that was created had the SCOM 2012 R2 Agent installed.  The images were installed on all of my clients.  Now, most of the clients are
    listed as greyed out or not monitored.  The server has Event Log entries of the following:
    Operations Manager has received a connection from a system running an older version of Operations Manager
    None of my clients are running an older version of the agent.  What's also new is that I cannot tell if my clients are turned on or not.  The clients that are green are always green.  Even when they are powered off, they are never grey
    in the console.  Even after I ping them or refresh.  They always stay green.  Any help would be appreciated.

    Hello,
    I deleted the Health Service State folder and I modified the DB so they are remotely manageable.  Now I am trying a repair.  But what I dont understand is why the healthy clients do not show when they are turned off?  They normally go from
    green to grey.  I've tried a ping and a refresh and I cannot get them to go grey.

  • Operations Manager log flooded with 11903 errors due to "Virtual Hard Disk free disk space" monitor

    Management Pack: Microsoft Windows Hyper-V 2012 R2 Monitoring (7.1.10104.0)
    Monitor: Virtual Hard Disk free disk space
    There appears to be an issue with this monitor. Every hour, each of my Hyper-V servers is reporting dozens of errors similar to the following. It seems like there is a disconnect between the expected return type (integer) and the actual type (decimal) when
    checking the free space on VHDX files.
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          2/5/2014 7:59:47 AM
    Event ID:      11903
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      BEAST.corp.technologytoolbox.com
    Description:
    The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
    Property Expression: Property[@Name='Microsoft:9AC8FCAB-800D-424F-ABCB-747063E5FCF1\559D22F4-A565-4AD4-9B71-44FC5D815C0C\0\0\L.FreeSpace']
    Property Value: 488033.99609375
    Conversion Type: DataItemElementTypeInteger(5)
    Original Error: 0x80FF005A
    One or more workflows were affected by this. 
    Workflow name: Microsoft.Windows.HyperV.2012.R2.VirtualDrive.FreeSpaceMonitor
    Instance name: Hard Disk
    Instance ID: {0C0E0759-D846-963C-21E6-3C1A1C096D5F}
    Management group: HQ
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11903</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-05T14:59:47.000000000Z" />
        <EventRecordID>32395</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>BEAST.corp.technologytoolbox.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>HQ</Data>
        <Data>Microsoft.Windows.HyperV.2012.R2.VirtualDrive.FreeSpaceMonitor</Data>
        <Data>Hard Disk</Data>
        <Data>{0C0E0759-D846-963C-21E6-3C1A1C096D5F}</Data>
        <Data>Property[@Name='Microsoft:9AC8FCAB-800D-424F-ABCB-747063E5FCF1\559D22F4-A565-4AD4-9B71-44FC5D815C0C\0\0\L.FreeSpace']</Data>
        <Data>488033.99609375</Data>
        <Data>DataItemElementTypeInteger(5)</Data>
        <Data>0x80FF005A</Data>
      </EventData>
    </Event>

    SCOM agent is running as SYSTEM. (I used to run SCOM agents as a low-privilege domain account but eventually surrendered to "The Dark Side" due to the number of issues encountered with that approach.)
    PS HKU:\.DEFAULT\Control Panel\International> dir
    Hive: HKEY_USERS\.DEFAULT\Control Panel\International
    Name Property
    Geo Nation : 244
    User Profile Languages : {en-US}
    ShowAutoCorrection : 1
    ShowTextPrediction : 1
    ShowCasing : 1
    ShowShiftLock : 1
    User Profile System Backup Languages : {en-US}
    ShowAutoCorrection : 1
    ShowTextPrediction : 1
    ShowCasing : 1
    ShowShiftLock : 1

  • Agent Failover and AD Integration in Operations Manager

    Hi
    I got some queries around SCOM agent failover and AD Integration:
    Does the discovery wizard differentiates between domain-joined and workgroup systems in terms of deploying agent on them?
    Why do we ever need Active Directory Integration with Operations Manager as described here
    http://technet.microsoft.com/en-us/library/hh212922.aspx
    - is it required for non-domain joined Windows systems or any other systems? All the other documents I read are saying that Windows agents can failover to other available MS in resource pool if their currently assigned MS fails and fails back automatically
    as soon as it comes back online.
    Is the automatic failover applicable to agents installed using client push (Discovery Wizard) Or it applies to agents installed manually using MOMAgent.msi?
    Also referred to this article
    http://blogs.technet.com/b/meamcs/archive/2013/05/10/is-ad-integration-or-manual-scom-agents-required-to-allow-automatic-windows-agent-failover-between-multiple-scom-management-servers.aspx
    but doesn’t seems to be having grip on it so far. Request some details on the above points.
    Thanks
    Taranjeet Singh
    zamn

    Hi,
    For the first question, I don't think we can use discovery wizard to install agent on non-domain joined computers. Please refer to the below links for how to deploy SCOM agent to non-domain computers:
    http://blogs.technet.com/b/quenguyen/archive/2011/07/13/monitoring-non-domain-servers-using-scom.aspx
    http://blogs.technet.com/b/stefan_stranger/archive/2012/04/17/monitoring-non-domain-members-with-om-2012.aspx
    For the second question, as we can read from the below link:
      http://blogs.technet.com/b/meamcs/archive/2013/05/10/is-ad-integration-or-manual-scom-agents-required-to-allow-automatic-windows-agent-failover-between-multiple-scom-management-servers.aspx
    SCOM windows agents automatic failover does not require AD integration or PowerShell scripting or Configuration Manager or manual agents installation specially for small to medium environment and agents distribution between different SCOM management servers
    can be accomplished through push agents wizard, and windows agents failover can be simply verified from event viewer.
    Regards,
    Yan Li
    Regards, Yan Li

  • Windows Operating System Health Status Not Monitoring

    Hi, I have installed SCOM agent to all my servers (Picture attached) and found some windows server not report health status and also i have already Installed Windows server Monitoring pack
    I have run below list troubleshooting step but no luck on this
    1. Flush agent cash and try refresh the agent
    2. remove agent and wait for 3 days and install agent again
    3. remove agent clear registry, re installed
    but the result is same, even scom server itself windows health services show as not monitored, 
    Could anyone help on this
    << picture attached >>

    Hi,
    Did you import the below management pack for Winddows Server Operating System?
    https://www.microsoft.com/en-hk/download/details.aspx?id=9296
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • VMM Connection to Configuration Manager and Operations Manager

    Hi,
       i was wondering how do i connect Virtual Machine Manager to Configuration Manager. do i need to have operations manager installed and up and running? or can i connect it to SCCM directly as it is being the main component.
    From my understanding of the VMM is that it is used for provisioning and controlling of Hyper visors (cytrix, Vmeare, etc.).
    why do i need to go through the Operation Manger? why can i not connect directly to SCCM?
    whats the Advantages of using operations manager instead of using CM?
    Thanks.

    VMM has no direct link to Configuration Manager at all. 
    VMM has a direct link to Operations Manager, which can be integrated and monitor the entire fabric (compute, networking and storage). 
    The synergy here is that every thing in VMM, will get exposed for monitoring in SCOM.
    Configuration Manager has a different approach - as VMM is responsible for the
    datacenter - while Configuration Manager manages the clients and eventually applications within the servers/clients. 
    -kn
    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

  • Windows Operating System "Not Monitored"

    Hi, I have seen multiple posts regarding this, and I have tried many things without luck. I thought I'd contribute what helped me. Funnily, I actually fixed the problem while posting my question. But I thought this may be useful to anyone else with the same
    issue.
    We have SCOM 2012 7.0.8560.0
    We have the Windows Server Operating System MP installed, 6.0.7061.0
    3 servers are reporting that the Windows Operating System is "Not Monitored".
    The 3 servers which are not being monitored all appear to be Windows Server 2012 R2 operating system.
    What we've tried
    Uninstall SCOM agent from the SCOM console. Remove SCOM agent folder. Reboot. Reinstall SCOM Agent from SCOM Console (push install). install completes successfully.
    Enable Proxy Discovery
    Reboot SCOM Servers
    Ensured the SCOM service account has Admin rights on the server
    Disabled Windows Firewall
    Set User Account Control to minimum
    Verified DNS (DNS functions 100% in our environment, with scavenging every 7 days)
    SCOM Database Grooming runs every 7 days
    The problem has existed for weeks\months, so this is not a DNS or Database grooming issue (unless there is something lingering in the database?)
    Re-Ran the "download SCOM Management Packs" from the console - all MP's are up to date
    After reading through the release notes of the Windows Server Management Pack, I searched my discovery rules to perhaps see if we had disabled the Server 2012 discoveries, or something careless like that. To my amazement,
    there we NO Windows Server 2012 R2 Discoveries present in our environment! This confused me greatly, since we are running the latest version of the Windows Server management pack.
    For some reason, it appears that updating your MP's from the console wizard does not pull this down.
    After manually downloading
    the Windows Server Operating System management pack, and installing it manually, everything started to work.
    I'm not sure why the SCOM wizard doesn't do this, but this has kept me busy for days, for something so easily missed.
    I suggest MS enhances the SCOM "update MP" downloads to pull down an entire management pack if it says it was "imported successfully". I now wonder what else I think it "up to date", which may have rules missing without
    my knowledge.
    Cheers

    Hi,
    It is really nice of you to share this, this will help others who encounter the same issue.
    And as far as I know, we need to manually download the Windows opearting system management pack to management group, then we can monitor windows operating system:
    http://www.microsoft.com/en-hk/download/details.aspx?id=9296
    Regards,
    Yan Li
    Regards, Yan Li

Maybe you are looking for