In preparing for the upgrade to SP1 for SCOM I decided to finally put in some alerting and simi-auto resolution to the settings for Veeam KB1036 that needs the SCOM agent reconfigured after every patch to the SCOM agent.

Issue: When the health service agent is upgraded with a CU/SP patch it stops reporting into the management server, this triggers a Health service alert but doesn’t directly tell everyone that we also just lost all of our monitoring into ESX.
Continue reading

There is a known bug with the SCCM MP and powershell/WMI v3 if you have the SCCM agent installed on your Management Point Server.  When the SCCM agent health check runs nightly it rebuilds WMI and breaks the MP.

Update 1/30/2014

please see my follow up post here on how to setup a Configuration Item to find this on your network if you are running Pre SP1 ConfigMgr still.

I opened a case with Microsoft support they confirmed that there was a known bug with WMF 3.0 and SCCM MP. they had two options to resolve this

1. unisntall WMF 3.0 and uninstall the SCCM agent from the Management point Server (would need to uninstall and reinstall the MP after SCCM agent is removed)

2. edit the NotifyOnly Regkey to TRUE. full path to the Key HKLMSoftwareMicrosoftCCMCcmEvalNotifyOnly

They attempted to uninstall WMF 3.0 and reinstall the Management Point with the following steps
Continue reading

Update 1/30/2013: I don’t recommend this as a primary way to install the SCCM agent on computers now that there is a supported solution from Microsoft, this was just a temporary workaround until SCCM SP1 was released.

In this blog post I’m going to document the high level steps to get the SCCM agent (Pre beta 1) on Server 2012, Windows 8 and this can be used also as a secondary method to catch any machines that didn’t get the agent installed by client push or WSUS depending on your main deployment method for the client.
Continue reading