ConfigMgr Client Broke after applying Windows Updates to Site Servers

Ho there expert

In Preperation for ConfigMgr 2012 R2 SP1 (Currently R2 CU1) i performed some update Tasks on my site Servers to be ready to install SP1 in a few weeks. During this maintenance Tasks i did the following things:

- Install Internet Explorer 11
- Install .NET Framework 4.5.2
- Install Windows Updates (June 2015 + SCEP 4.8)

I did that on my Primary site Server (2008 R2), Database Server (2012 R2) and my two Site Servers (2008 R2) which are MP and DP. Now a week later i noticed in the Console, that in the Endpoint Protection Engine / Definition Version Column in the Devices View, the Version is "0.0.0.0". The Server itself has the latest Version according to the SCEP Interface. I tried to reinstall SCEP but that didn't solve the Problem.

The next step i tried, was to remove the Client from the ConfigMgr Console, hoped that the rediscovery will solve the issue. The Client then got rediscovered via Active Directory System Recovery, but with "Not Client installed"

The next step i tried, was to uninstall the ConfigMgr Client on this System. Now after the reinstallation the console Displays "Client -> Yes" and Active. But the Client doesn't get any policy. The only error i see in all the site Servers "CcmMessaging.log" is:

The site System roles on those Server are Healthy, according to the Site / Component Status in the ConfigMgr Console.

Thank you for an

June 22nd, 2015 3:36am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics