Re-Import VMs into Hyper-V
Normaly you can only import a Virtual Machine (VM) into Hyper-V if you have exported it. If you lose your Hyper-V settings or have to import it into a new Hyper-V Server in case of a desaster recovery than you can use the steps descripted in this (and other) blog post: http://blogs.msdn.com/b/robertvi/archive/2008/12/19/howto-manually-add-a-vm-configuration-to-hyper-v.aspx
The problem is that you have to handle many long pathes and cryptical GUIDs. I had to do that for a bunch of different VMs and being chronical lacy I created three batch files for it:
- importVM.cmd “GUID” “Path to Virtual Machine” creates the link and corrects the permissions on the link and the vm folder
- importSnapshot.cmd “SnapshotGuid” “VMGuid” “Path to Snapshot” creates the snapshot link and the right permission.
Not very impressiv? Well, the third batch files combines this two scripts:
- addMachine.cmd: Takes the basis path (the path where the sub-folder Virtual Machine, Snapshots exists) and extracts the VM-GUID, all Snapshots-GUIDs and the other pathes to automaticly create the links and permissions.
So with one simple command (addMachine.cmd C:\ClusterStorage\Volume4\VM1) you can import the complete VM.
— addMachine.cmd ——
SCOM ACS over forest borders
Sometimes the acs forwarder doesn’t connects successfully to the acs server and states in the operations manager event log, that you have to activate debugging to see more details.
You can activate it by following this instruction:
- Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AdtAgent\Parameters
- Create DWORD value = TraceFlags
- Edit the TraceFlags entry and enter decimal value 524420
- Restart the AdtAgent service
(Source: http://helpmemanage.blogspot.com/2007/05/enable-detailed-logging-for-acs.html)
You can find the log under c:\windows\temp
One cause can be that the acs cannot operate over forest borders or from a workgroup (kerberos authentication – some reason for the scom agent).
Manual activate debug for GPP
Sometimes you have to debug group policy preferences (gpp) and don’t want to activate the debugging with another group policy.
You can simpe activate the debugging with two registry entries:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Group Policy\{728EE579-943C-4519-9EF7-AB56765798ED}]
"LogLevel"=dword:00000003
"TraceLevel"=dword:00000002
SCOM2Nagios 1.4
Find the newest version on top of: </tag/scom2nagios/>
Released a new Version of the SCOM2Nagios Connector. Changes:
1.4
- NEW: variables for processing instruction
- NEW: change case of output (upper/lower)
- BUG: no crash if scom connection is lost
- BUG: no longer needs fullpath in config
Example:
mcscom
If path contains mcscom than replace the host in the output with the upper case of the ObjectFullPath variable of the input alert.
SCOM2Nagios 1.3
Find the newest version on top of: </tag/scom2nagios/>
I have uploaded a release of the Nagios Connector 1.3. You can read about the changes in this post:
/2009/10/preinfo-nagios2scom-1-3/
I have only made some short and fast tests. So be cautious.
Download: SCOM2Nagios (141 downloads )
OpenUMR – Cross Monitoring Integrator
If you not only want to connect OpsMgr to Nagios with my connector but other management systems to OpsMgr than the OpenUMR can perhaps help you.
It does more than just creating alerts in SCOM: it even creates the correct objects for the alerts.
More infos: http://openumr.codeplex.com/
PreInfo: SCOM2Nagios 1.3
The new version is released here: /category/tools/scom2nagios/
The next release will address two feature requests:
- Possibility to change the hostname (you don’t use fqdn host names in nagios…)
- Possibility to use more than one service in nagios (you want to separate the alerts for dns and acitve directory)
I will try to solve both by using “processing instructions”. This instructions will use the scom alert as an input filter and the nagios alert as the object to manipulate.
SCOM2Nagios 1.2
Find the newest version on top of: </tag/scom2nagios/>
Attached is the new version of the SCOM2Nagios Connector.
There is just one small thing changed:
You can now define the OK message in config file. So no more german status messages in your nagios :-)
And thanks to Thomas Karatzoglou we now have an english installation instruction in the file.
Download Link: SCOM2Nagios (254 downloads )
FB_Addon_TelNo{ height:15px !important; white-space: nowrap !important; background-color: #0ff0ff;}