SCOM Agent Version Addendum Management Pack

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    February 27, 2017
    Thank you Kevin... much needed
  • Anonymous
    February 28, 2017
    Great Work Kevin!What is missing for me is an exact up-to-date SCOM Server / Agent Version Overview from MS :-(
    • Anonymous
      February 28, 2017
      Hmmm, I can write that.
      • Anonymous
        February 28, 2017
        Would be great!
        • Anonymous
          December 18, 2017
          Totally agree, please do that Kevin!
  • Anonymous
    February 28, 2017
    Thanks Kevin!Many customer's pains, resolved in one shot :-)
  • Anonymous
    March 01, 2017
    The comment has been removed
  • Anonymous
    March 03, 2017
    It's a much awaited things that we are waiting to get this. Thanks for the new MAP.
  • Anonymous
    March 08, 2017
    Thank You Kevin....
  • Anonymous
    April 13, 2017
    Thanks for this post, after install MP i can see the version changed but for the patch list in "Agent by version" view its blank ! normal ?
  • Anonymous
    May 12, 2017
    I just did my upgrade and the "Agent by Version" view is not updated.
    • Anonymous
      May 12, 2017
      What part? Can you be more descriptive?
  • Anonymous
    June 02, 2017
    My agents haven't updated in the view. Is this normal?I've added the MP you specified and they are still showing 8.0.10918.0. Any ideas?Thanks.
    • Anonymous
      June 02, 2017
      No - that's not normal. Have you updated the agents? Did you manually inspect the version of the file?This is updated via config update. If your config service is broken - you wont get updates. Look at the event logs on the SCOM management servers.
  • Anonymous
    December 06, 2017
    Hi,I have changed icons in the diagram view and imported the management pack however scom picks up old icons, is there any way to fix this?Regards,Vikas
  • Anonymous
    December 19, 2017
    Kevin,Will this work changing the agent initially from SCOM2012 R2 7.1.10184.0 to SCOM2016 8.0.10918.0?This would be part of a parallel migration.Thanks.
    • Anonymous
      December 19, 2017
      This simply runs a discovery on the agent, gets a version number from a specific file, then reports that back. It doesn't care what version of SCOM you have.
  • Anonymous
    April 28, 2018
    Hi Kevinwe have installed this MP to SCOM 2016 UR5, most of agents have changed version to 8.0.10990.0 from 8.0.10918.0, but all cluster nodes are changed to "unknown" from 8.0.10918.0.we have repaired/reinstalled agent from console, no different.these nodes are running windows 2016 datacenter edition with/without desktop experience.is possible let these nodes display right version?
  • Anonymous
    September 06, 2018
    Morning,This is truly wonderful, thanks as always! Is there a resource you can point me to that shows me the correct version(s) of the agent I should be using for monitoring Windows 10 and Server 2016 clients? My SCOM environment is still 2012R2 UR12. Working on getting it up to UR14 and then this winter moving to the 2016 version of SCOM.Regards!Tony
    • Anonymous
      September 12, 2018
      Operations Manager 2012R2 agent supports Windows 10 and Windows Server 2016:https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/dn281934(v%3dsc.12)
      • Anonymous
        September 12, 2018
        Morning and thank you for your response. I asked because I was seeing where people where using a newer agent for server 2016 servers (Domain Controllers, DHCP servers) vs non domain controller 2016 servers. I use the UR12 agent for all of our 2012R2, 2008R2 servers and not had any issues there.Regards,Tony