%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?

 

I found that the PC’s registry had issues; specifically with the UserShell keys. In my instance, the following key:

I've no idea how this happened. I do wonder if people have been "tinkering".

I’ve no idea how this happened. I do wonder if people have been “tinkering”.

 

The hive and key.

The hive and key.

 

…should have a value of:

This is what the value the key should have.

This is what the value the key should have.

 

Once changed, I stopped the ccmsetup service and then started it. The client then installed:

Huzzah. By the way, incoming updates?

Huzzah. By the way, incoming updates?

 

So to summarise. A registry key had its value changed from %USERPROFILE%\AppData\Roaming to %APPDATA%. Changing it back had an immediate remedial effect.

Yay.

Advertisements

Flame on xD

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s