Partager via

Agent Management Pack – Making a SCOM Admin’s life a little easier

  • Article

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    May 09, 2017
    Kevin, I am trying to seal this mp but keep getting XSD verification failed for management pack. The SchemaVersion is not declared. I have sealed mps I have exported from SCOM 2012 before, it requires the different exe, but this one is not working. Any thoughts?
    • Anonymous
      May 09, 2017
      Nevermind. I was in fact using the wrong mpseal. ;-)
  • Anonymous
    May 10, 2017
    Kevin, It a very useful as a SCOM administrator. The only problem what i face that it not allowing to select multiple object to copy . I need to pass those missing software for any agent to the concern team so that they can install the missing software/Powershell module But unfortunately i am not able to copy and paste it. Please let me know if you can provide any workaround.I have 1000+ agent don't have Powershell installed.Thanks for providing a very useful article,
    • Anonymous
      May 10, 2017
      I am able to pull those information through PowerShell.Once again thanks Kevin and Team for this article.
  • Anonymous
    May 11, 2017
    Kevin, thanks very much for this management pack, it's really useful! I've got hundreds of manually installed agents to update and this is making short work of it.
  • Anonymous
    May 11, 2017
    Looking Forward to using this pack.It would be great if there was a way to schedule flush agents in bulk as part of a regular maintenance schedule. It was also be good to see a powershell management pack or repository in SCOM where you could build a custom library of scripts and target them against computers or groups.
    • Anonymous
      August 07, 2017
      You can schedule flushing agents if you want, just create a rule with a scheduler datasource and use the flush write action. That said - I do not recommend this as I do not see that to be needed. The only time you should have to flush the cache is when the ESE DB grows huge, or gets stuck/corrupt, which is pretty infrequent.
  • Anonymous
    May 12, 2017
    Great stuff as usual. Why not hosting this on github to accpet community contribution?
  • Anonymous
    May 16, 2017
    Great contribution once again. Thank you!
  • Anonymous
    May 17, 2017
    Kevin,As always another great contribution.It would be nice to have a task to set proxy enabled and see this as a property. And the same for setting the agent remotely manageable.
  • Anonymous
    May 17, 2017
    Kevin,As always another great contribution.It would be nice to have a task to set proxy enabled on the agents and see this as a property. The same for remotely manageable.
  • Anonymous
    May 19, 2017
    Thanks for MP. For server 2016 and Windows 10 OS version 6.3 incorrect.
    • Anonymous
      May 19, 2017
      Why is that "incorrect" ? That's what the registry reports.
      • Anonymous
        May 29, 2017
        Hello! You read HKLM "SOFTWARE\Microsoft\Windows NT\CurrentVersion"But In W10 and Server 2016 new registry key apply https://stackoverflow.com/questions/31072543/reliable-way-to-get-windows-version-from-registry
        • Anonymous
          May 29, 2017
          Ok - good feedback. I updated to version .77 and switched this discvoery to powershell to better handle this situation. The numbers now align to the same way the built in OS version discovery works.Thanks!
          • Anonymous
            May 29, 2017
            Ok, thanks!
  • Anonymous
    May 22, 2017
    The comment has been removed
    • Anonymous
      May 22, 2017
      The comment has been removed
      • Anonymous
        May 22, 2017
        The comment has been removed
        • Anonymous
          June 07, 2017
          Furthermore you could always create a seperate security group in SCOM that excludes operators from using those risky tasks.
          • Anonymous
            August 23, 2017
            The whole point is, ppl tend to forget that after the import. So operators unexpectedly get admin powers. That's where the biggest risk is imho.
  • Anonymous
    May 28, 2017
    Really great and useful stuff, before I implement this, i would like to know if there are any prerequisites for running powershell script? And what is the account that this task uses?
    • Anonymous
      May 28, 2017
      The prereq for a PowerShell script is PowerShell.The credentials tasks will run under is the same as any task in SCOM - console task runs as the console user, agent tasks run as the default agent action account (or runas account if specifically configured)
  • Anonymous
    June 13, 2017
    Great MP and I found a few old Management Groups that I cleared but one is proving difficult to remove. It is called SCOM12 MESSAGING DEPT. On the first try I received the following message.Failed to remove SCOM12So the task does not like spaces.After experimenting using double quotes seemed to get it work but Failed to remove SCOM12 MESSAGING DEPTExit code 0This is an AD Integrated MG. Is that a problem for the task?
    • Anonymous
      June 19, 2017
      Yikes! I don't know. I didn't even know we allowed spaces in a management group name. I can probably fix the task to allow for that.
  • Anonymous
    June 28, 2017
    Hi Kevin,would it be possible to add a task to configure a failover MS on an agent?If would be really useful to do this from this state view in the console.Thanks.
    • Anonymous
      August 05, 2017
      I'm working on this.
  • Anonymous
    July 25, 2017
    Hi Kevin. As always you work is incredible. It would be great to add a task that check the root cause of a grey agent (wmi, Ping, port check, etc) in one single task OR add a view that only show the grey agents with colums that check these information as you do with the versión of Powershell and agents. What you think?
    • Anonymous
      August 05, 2017
      I added a HealthService Watcher view.Root cause for grey agents is next to impossible. The grey agent is not communicating with SCOM. To know why from the server perspective would be very difficult.
      • Anonymous
        August 17, 2017
        Yeah but keep in mind that with the Powershell MP, you can track for example the port connection, WMI, FQDN, etc and this way reach a possible root cause. Am I right?
  • Anonymous
    August 06, 2017
    The comment has been removed
    • Anonymous
      August 06, 2017
      and also it would be a good idea to see active thresholds on healthservice from this posthttps://blogs.technet.microsoft.com/kevinholman/2017/05/29/stop-healthservice-restarts-in-scom-2016/
      • Anonymous
        August 07, 2017
        Active thresholds in place are derived from config which is derived from the management group config service. This is something I can easily pick up from the agent in a discovery.
    • Anonymous
      August 07, 2017
      My problem with discovery of ACS, is that so few customers use ACS, and we already discover the forwarder, and settings in another MP I wrote: https://blogs.technet.microsoft.com/kevinholman/2015/06/05/audit-collection-services-forwarder-addendum-management-pack/I am hesitant to include more properties than absolutely needed - because the more properties a class has - the slower it returns data to the console.
  • Anonymous
    August 08, 2017
    We have recently built a new 2016 environment and have installed this MP to ease the administrative overhead. However, when I tried using the HealthService-Restart task, it failed citing health service is not present. Need to manually login to the server & restart the service. Any parameters which needs to be changed while running this task??
    • Anonymous
      August 09, 2017
      Hi Kevin,we upgraded from RTM directly to UR3 (because of the cumulative UR) and the dll spotchecks for the agents, gateways etc. were fine.Nevertheless states your SCOM Management Pack for the gateway servers that they are still on 2016 RTM because the HealthService.dll won't be updated with UR3 there (but it will with UR2 to 8.0.10949.0 according to https://support.microsoft.com/en-us/help/3209591/update-rollup-2-for-system-center-2016-operations-manager). So the file version is still 8.0.10918.0 (RTM) with release date 7/8/2016...I noticed the "Special case for bug in SCOM 2016 UR3 missing HealthService.dll patch" in the SCOM.Management.Server.Class.PowerShell.Properties.Discovery.ps1 where you use instead the MOMWsManModules.dll (used for the dll spotcheck in the UR3 step by step guide) in case the fileversion for the HealthService.dll is on UR2 (8.0.10949.0). After checking for both versions (UR2 + RTM) for the bug($ServerURFileVersion -eq "8.0.10949.0" -or $ServerURFileVersion -eq "8.0.10918.0")the SCOM Servers view states the correct Server UR Level for the gateways.Communication between gateways and agents/mgmtservers work correctly but wanted to mention and make sure that it is "expteced" and by design. I know it is quite complicated to check for all conditions because with UR2 HealthService.dll was updated and with UR3 MOMWsManModules.dll... so which file can be used that is universal...Kind Regards,Konstantin
  • Anonymous
    August 15, 2017
    Systems with PS 4/5 do not necessarily have HLKM\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine\PowerShellVersion but definitely have instead SOFTWARE\Microsoft\PowerShell\3\PowerShellEngine\PowerShellVersion. Question how to merge that...That's why the SCOM Agents view states on several systems "PS Installed" = false but "PS Ver" = 4.0/5.0/5.1 (you get this from $PSVersionTable).Regards,Konstantin
    • Anonymous
      August 15, 2017
      What OS/Build version doesn't have the key I am using? Everything in my lab has it. Trying to repro.
      • Anonymous
        August 15, 2017
        I've seen this on some systems with Windows Server 2012 R2/6.3.9600.
        • Anonymous
          August 17, 2017
          I will update the discovery in the next version to just look for HLKM\SOFTWARE\Microsoft\PowerShell
  • Anonymous
    August 16, 2017
    The comment has been removed
    • Anonymous
      August 17, 2017
      Thanks!Apparently POSH 2.0 on WS2008R2 doesn't like the switch statement and the full number. I need to encapsulate each number in quotes to resolve this. I will fix this in the next version update soon.
  • Anonymous
    August 21, 2017
    In the SCOM HealthService view you can display the install date but you cannot sort the column on the date. In the Agent Managed view in Administration you can sort by the installed date. It would be nice if that column was sortable to avoid going back to the Administration view,ThanksIan
    • Anonymous
      August 26, 2017
      Ian - I added this capability in version .45. All you have to do in the XML is change the view default IsSortable=TrueI have no idea why SCOM defaults to some view columns as not sortable. To me, they should ALL be sortable!
  • Anonymous
    August 25, 2017
    Hi Kevin,Does the previous version of the MP need to be uninstalled before importing this one?Thx,John Bradshaw
    • Anonymous
      August 26, 2017
      Not that I know of. Unsealed MP's simply replace previous unsealed MP's. However, if you sealed it - you will likely need to replace it because of structural changes.
  • Anonymous
    August 31, 2017
    The comment has been removed
    • Anonymous
      August 31, 2017
      I see the bug now - I have it fixed - will publish after testing next week.
      • Anonymous
        September 04, 2017
        Thanks Kevin!
  • Anonymous
    September 14, 2017
    The comment has been removed
    • Anonymous
      October 05, 2017
      For the ones using the mp for upgrade from scom 2012 to 2016 and want to have an excel list:import-module operationsmanagerNew-SCOMManagementGroupConnection -ComputerName $class = get-scomclass -displayname "SCOM Agent Management Class"$instances = Get-SCOMClassInstance -Class $class|Sort-Object displayname$serverlist= @()foreach ($instance in $instances) { $props = @{ Server = $instance.DisplayName OS = ($instance|Select-Object -ExpandProperty *.OSName).value PSver = ($instance|Select-Object -ExpandProperty *.PSVersion).value dotNet = ($instance|Select-Object -ExpandProperty *.CLRVersion).value } $serverprops = New-Object psobject -Property $props $serverlist += $serverprops }$serverlist|export-csv -Path "C:\temp\serverlist.csv"
  • Anonymous
    October 06, 2017
    Kevin, what an awesome MP. Immeasurably helpful in migrating a large MG to new servers. I have been using the MG - ADD task. I found that although the task is successful, the output always reads "Failed to add MY MG" even when modifying just one agent. My MG has spaces in it so I'm putting both the MG and the FQDN of the MS in quotes - not sure if that matters.
    • Anonymous
      October 06, 2017
      Yeah - someone else brought that to my attention. You might have to find workarounds for that. I'd never recommend a management group with spaces, I am surprised we allow for that. :-)
  • Anonymous
    October 10, 2017
    Hi, Kevin is it possible to make from "SCOM.Management.DeleteAgent.WA" a fragement to use this in other MP´s.I want to make a RecoveryTask for a Evententry to delete the Agent in the Scomlandscape.cuDirk
  • Anonymous
    November 01, 2017
    Hi KevinI'm sure this yet another great tool from you and your colleagues. But apparently I can't use the Management Pack :( I have imported the managment pack in our newly installed SCOM 2016 environment, but I don't get the folder "SCOM Management" in the console.Is this management pack not supported in SCOM 2016?
    • Anonymous
      November 01, 2017
      Okay I figured it out - wrong Management Pack - DoH :(
  • Anonymous
    November 01, 2017
    Great!
  • Anonymous
    November 23, 2017
    Good day. I think what is missing in this section is "SCOM Server Tasks:" agent Repair tasks.
  • Anonymous
    December 17, 2017
    That would be nice to have some Linux equivalent (to know the OMS Workspace, etc).
  • Anonymous
    January 03, 2018
    Kevin no se que tan adecuado sea que el MP contenga una tarea de verificación y remediacion del estado del WMI.
  • Anonymous
    February 07, 2018
    The comment has been removed
  • Anonymous
    March 07, 2018
    Everything about this MP is amazing. Well done sir.
    • Anonymous
      March 07, 2018
      thanks!
  • Anonymous
    March 21, 2018
    Kevin,Will you release an updated version that will be compatible with SCOM 1801?This is a very usefull MP and I would like to see it supported in our 1801 environment.Thanks,Frederik
  • Anonymous
    April 23, 2018
    Hi Kevin!Great MP - well done! Is it possible to add one more SCOM task to "clean uninstall SCOM agent"? For our scom users in our company it would be the easiest way to trigger an uninstall of agents without being SCOM-administrator (but being local administrator on the monitored system). So for SCOM-admins it is ensured that the SCOM agent is uninstalled on the monitored system and it is deleted in SCOM itself in a clean way.Thank you very much!Regards,Florian
  • Anonymous
    April 25, 2018
    The comment has been removed
  • Anonymous
    November 13, 2018
    The comment has been removed