Recently I’ve stumbled on the following error when trying to update VMM agent on hosts:
An internal error has occurred trying to contact the hv01.contoso.com server: NO_PARAM: NO_PARAM.
Continue reading “Error (2912) When You Try to Update VMM Agent on Hosts” →
Final version of PowerShell 3.0 is here and it is now available for Windows 7 SP1, Windows Server 2008 R2 SP1 & Windows Server 2008 SP2 systems. PowerShell 3.0 is provided ad windows update that actually contains updates for several technologies:
- Windows PowerShell 3.0
- Management OData IIS Extensions
- Server Manager CIM Provider
The update and additional information can be found here.
Note: This update requires .Net Framework 4.0
Once again I’ve stumbled on another interesting SCOM issue. First here is the environment:
SCOM01 – RMS server, HP OpenView connector service – Active
SCOM01 – MS server, OpsMgr DB, DW DB, Report server, HP OpenView connector service – Passive
OMU01 – HP Operations Manager for Unix server
SCOM01 is sending alerts to OMU01 via HP OpenView connector. After patching SCOM01 and SCOM02 the connector service stops sending alerts to OMU01. When the following command is ran on SCOM01:
winrm identify –r:OMU01:1270 –auth:basic –u:username –p:password –encoding:utf-8
HTTP error 501 is given. I’ve found similar issue with communication with Unix/Linux servers:
As SCOM is using winrm for communication with Unix\Linux and connectors the resolutions is the same:
- Uninstall the update KB2585542
- Make a registry modification to disable the SecureChannel changes implemented in the update
Modifying the registry to disable the SecureChannel changes:
A “FixIt” package is available in the KB article under the Known Issues section that can be used to disable the security update
Alternatively, you can add the 32bit DWORD value:
SendExtraRecord = 2
After implementing those changes the connector started to work properly again.
Another case solved.