Tag Archives: Config Manager Client

Config Manager client scan error

Yup, I’ve been a bit quiet of late.

Out of the blue, my Windows 10 device suddenly stopped patching. I checked the WUAHANDLER.log and found something new. Which is always nice. Here is the log:

Cheers Microsoft.

Continue reading

Advertisements

Config Manager client Deployment Error – VCREDIST

Every now and then I’ll work through the Fallback Status Point deployment failures; it’s good to keep on top of the numbers and it’s obviously needed if you wan to patch your PCs. There are naturally an abundance of errors, but this one was quite interesting:

FSP for the win.

FSP for the win.

Deployment Error: 0x80070652. Pre-req: vcredist_x86.exe

Continue reading

WSUS Boot-Strapper Error

Following a client upgrade, I did notice a niggle with one of Config Manager’s Components:

So fustrating at times... the error doesn't really tell what the real issue is.

So frustrating at times… the error doesn’t really tell what the real issue is.

A constant stream of:

WSUS Configuration Manager failed to publish client boot-strapper package

So basically something is wrong, but there were no details to give me a definitive direction. I delved into the logs, and headed straight for the WSUS logs. I opened the WCM.log, and although nothing was flagged in red, I did find some interesting text:

Continue reading

Config Manager 2012 SP2 CU1 et al

So we upgraded to CU1 (KB3074857), and applied the following hofixes:

KB3082531
KB3084586
KB3089193

Another fine mess.

Another fine mess.

All looked ticketyboo, however when testing the client, I received the following error when attempting to uninstall the Config Manager client:

<![LOG[Failed to load mdmregistration.dll with error 0x8007007e]LOG]!><time=”14:49:36.523+00″ date=”11-03-2015″ component=”ccmsetup” context=”” type=”3″ thread=”5224″ file=”mdmreg.h:78″>

Continue reading

%APPDATA% Error When Installing The Config Manager Client

I’ve been seeing this for a few PCs across the domain, and decided it was the time to give it some attention. PCs were failing to install the Config Manager client; I was getting the following error from the Fallback Status Point:

5.0.8239.1000 Deployment ExitCode: 1603 Action: CostFinalize. ErrorMessages: Could not access network location %APPDATA%\. Could not access network location %APPDATA%\.

Equally, the CCMSETUP.LOG reported:

Pesky thing... why do pesky things always get peskier?

Pesky thing… why do pesky things always get peskier?

Continue reading

Automatic Client Upgrade

With the advent of 5.00.8239.1000, the site had a major build upgrade (as opposed to a minor build change a la hotfix) and yet another client update to rollout. Normally I would do a client push and slipstream in the client MSI using the clientpatch hack here.

Quite frankly, I was getting a bit tired of pushing the client over the course of a month 😀

So I decided to investigate something that had been bugging me for a while: Automatic Client Upgrade, and why the option was greyed out to enable it was greyed out.

I believe this is a new, as in new to Config Manager 2012, option. We still have the tradition client deployment options either as an automated Client Push or as a Software Update based installation:

Old skool Config Manager!

Old skool Config Manager!

Continue reading

SCCM 2012 R2 CU5

Short but sweet…

System Centre COnfiguration Manager 2012 R2 CU5 has been released, and it is rather delicious! For me personally, it allegedly addresses an issue I have ben seeing, and in fact, quite possibly made Microsoft aware of via TechNet and our Microsoft Support Partner. Specifically:

Software distribution fails when the client cache is full and virtual applications have been deployed.

Errors that resemble the following are recorded in the Cas.log file on the client:

  • IsCacheCopyNeeded returned ‘true’ by {content id}

Continue reading