| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,17 +1,17 @@ | ||
| The management checks for a pending reboot requirement in four places... ??These three registry locations are checked for values that indicate a reboot is required: | ||
|
|
||
| HKLM\System\CurrentControlSet\Control\Session Manager\ | ||
| HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\ | ||
| HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing | ||
|
|
||
| And,??Microsoft.Update.SystemInfo is queried for a requirement to reboot. | ||
|
|
||
| After testing though, I did notice that some applications can create registry entries that would normally indicate that a system reboot is required, however a reboot isn't actually required, it's just the way the app works. ??Therefore, I have also added the ability to configure whether the reg keys are checked, or if??Microsoft.Update.SystemInfo is queried, or both. ??This can be configured by overriding the Script Arguments property on the monitor to one of these values: | ||
|
|
||
| "11" -- All reg keys and SystemInfo queried (Default) | ||
|
|
||
| "01" -- No reg keys checked, only SystemInfo queried | ||
|
|
||
| "10" -- All reg keys checked, SystemInfo not queried | ||
|
|
||
| [](https://i1.wp.com/aquilaweb.net/wp-content/uploads/2015/07/RebootOverrides2.png) |
But you can view the diff anyway.
A simple Management Pack to help add and remove Management Groups to/from agents.
Hello, just fulfilling a quick ask with this one. With SCOM 2012 we were given the ability to manage agent Management Group configuration using the Agent Config Manager Object or AgentConfigManager.MgmtSvcCfg. It can be leveraged in VBS or PowerShell to Add, Remove, and List SCOM management groups configured on the agent. This isn’tisn?t groundbreaking news and the methods are well documented, and plenty of community examples exists already.
That said, I see it asked frequently about what the best method of running a script to modify MG settings against their agent install base. SCCM and remote PowerShell are common solutions, but with this last go-around, I thought why not leverage SCOM itself (assuming it’sit?s not an all-out removal).
Below is a link to a VSAE project for a Management Pack that contains two disabled rules and a script-based data source (VBS) to help automate the addition and removal of management groups for agents. The rules can be overridden and enabled to Add a MG w/a Management Server, or remove a MG.
I’veI?ve done my best to include logging and protections against bad things (like removing the last MG on an agent), but please be cautious as this MP could be dangerous and easily break every agent. As always:
This is provided AS-IS, as an example only, and contains no warranty. The MP should not be used in a production environment without careful review and planning.
The NiCE Log File MP lets you perform a multitude of functions that are critical in your role as system, application or database administrator.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,12 @@ | ||
| # Nutanix SCOM Management Pack | ||
| ------------------------------- | ||
|
|
||
| The management packs collect information about software (cluster) elements through SNMP and hardware??elements through ipmiutil??[(Intelligent Platform Management Interface Utility)](https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface)??and REST API calls and then package that information for SCOM to digest.??*Note:??The Hardware Elements Management Pack leverages the ipmiutil program to gather information from Nutanix block for Fans, Power Supply and Temperature.* | ||
|
|
||
| **[](https://i2.wp.com/www.netwatch.me/wp-content/uploads/2015/06/scom01.png)** | ||
|
|
||
| Nutanix provides two management packs: | ||
| ====================================== | ||
|
|
||
| - **Cluster Management Pack --??**This management pack collects information about software elements of a??cluster including Controller VMs, storage pools, and containers. | ||
| - **Hardware Management Pack --**This management pack collects information about hardware elements of??a cluster including fans, power supplies, disks, and nodes. |
Here you can download Ping Management Pack for SCOM 2012 & 2016. .?If you are using SCOM 2007R2, please download the 2007R2 version of the Ping Management Pack ?here.
Please provide your contact details to download Ping Management Pack. We will send your personal download link to the email address you provide us with.
The ?OpsMgr Health Synchronization Library ?management pack is designed to provide a workaround to this limitation. This management pack provides a template that enables OpsMgr users to create monitoring objects named "Health State Watcher" hosted by All Management Servers Resource Pool. Health State Watcher objects have monitors configured to query health state of monitoring objects located in a remote management group using OpsMgr SDK.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,35 +1,35 @@ | ||
| Community based Management Pack for Hyper-V 2012 R2 to overcome the limitations of the standard ones. Importing this MP disables the VM monitoring delivered by the Microsoft authored Hyper-V Management Pack. | ||
|
|
||
| Check for latest commits on hitgub??<https://github.com/brandubh/HypervMP>?? | ||
|
|
||
| Current Version: 1.1.0.72 - 14/01/2017?? | ||
|
|
||
| Added VM Tasks. | ||
|
|
||
| Some features of the MP. | ||
|
|
||
| -?????????????????? Comprehensive discovery with at least the same information you can get from the VMM integration, some properties discovered | ||
|
|
||
| - OS and platform | ||
| - Farm (very useful to create dashboards and groups) | ||
| - Hardware configuration | ||
| - Connected VHD(x) | ||
| - Connected NICs | ||
|
|
||
| -?????????????????? An optimized discovery that is triggered when VMs are moved, started or stopped | ||
|
|
||
| -?????????????????? A complete replica monitoring scenario with diagnostics, recoveries (disabled by default) and tasks to resume replica | ||
|
|
||
| -?????????????????? A couple of monitor related to GPUs and remoteFX inherited from the MS provided MP, disabled by default since I consider them not useful. But in any case I didn't want to lose monitoring capabilities. | ||
|
|
||
| -?????????????????? Integration services obsolescence (only for Windows VMs since I don't know how to update *nix VMs now that MS isn't releasing anymore IS for platforms that have the services included in the kernel) | ||
|
|
||
| -?????????????????? VHD(x) fragmentation level monitoring, this one can be noisy, but if you have fragmented VHDs you better know it, since the performance impact can be significant | ||
|
|
||
| -?????????????????? VM uptime in % in the observation period (as you wish @Stas), this can useful to bill on uptime | ||
|
|
||
| -?????????????????? VM measures as performance counters for enabled virtual machines (Enable-VMMeasure) | ||
|
|
||
| More On GitHub:??<https://github.com/brandubh/HypervMP> | ||
|
|
||
| and on??[http://nocentdocent.wordpress.com](http://nocentdopcent.wordpress.com/)??search for Hyper-V and management pack. |
A few weeks ago I started with a Task Collection MP MP?found on this post. As I am getting new ideas I will add more tasks to make life easier. In the latest version SCOM Task Collection MP version 1.2.0.0 I added 3 more tasks...
09) Get DNS Settings
This task shows you the configured DNS server settings and the server's IP address.
10) Fix Support Tool Path
If you try to execute Active Directory related tasks from the Active Directory management pack like DCDiag, Repadmin etc. they will not work because the path to these tools has changed on Windows 2008 (R2) domain controllers. I have written a ?blog post ?about it. This task will create the necessary symbolic link as written ?here ?to get it working.
New are task 11, 12 and 13:
**11) Remove Management Group from Agent
**If you have multi-homed agents which report to two management groups your agent will have two management group settings. This scenario is very likely in a SCOM side-by-side migration where you have the SCOM 2012 agent reporting to SCOM 2007 R2 AND SCOM 2012. If you need to remove one of the management group settings from the agent you can execute this task. You just need to provide the management group name (click the Override button and type the management group name) which you want to remove from the agent in the format:
"MANAGEMENTGROUP"
**12) Add Management Group to Agent
**If you need to add another management group setting to an agent you can execute this task. Just select a managed Windows computer in SCOM, run this task and click the Override button. You need to provide 3 parameters:
The values need to be in the format:
*"MANAGEMENTGROUP" "MANGEMENT SERVER" 5723
*
**13) Mark Windows Server in Registry
**This task is able to write 2 registry values into two predefined registry keys. First, this tasks creates a key in ?HKLM\SOFTWARE\SpecialKeys ?. Within this key two additional keys are generated one is called ?Category ?and one is called ?Team. ?Now you can add values to Category and Team if you run this task click Override and provide the values in the following format:
"PRODUCTION" "SQL"
This would write ?PRODUCTION ?into the Category key and ?SQL ?into the Team key, the task looks like this...
...and the result like this...
Well, you think now cool and so what? My intension is to have a quick way to set registry values to which will be discovered by attributes in SCOM. These attributes which discover the Category and Team key could be used to build dynamic groups based on the respective value in SCOM.
Now what do you think, huh ?
If you want to delete the registry values (not the keys!) just execute the task as it is without modifying anything.
Updated 8-11-2017
This is a SCOM management pack for Operations Manager 2012 and 2016, which will ease the burden of SQL RunAs Accounts. ?Instead of using a domain credential, we will use a service SID and a special login to SQL to provide secure access for monitoring.
But you can view the diff anyway.
