SCCM Gurus - Strange client problem. Any help?

Pestilence

Pestilence

Pestilence

Soldato
Joined
22 Feb 2008
Posts
11,108
Hey folks!

So, SCCM 2007, I had a client a few days ago which wasn't receiving an advertised package. Found that the advertisement wasn't making its way through.

We noticed that the client wasn't approved and recognised by the server, so sorted that but also noticed some WMI issues when trying to connect via SCCM Client Center. WMI was repaired, and the ccm client successfully reinstalled. Now it reports as installed and approved on the server, and can be connected to just fine with Client Center.

Problem is, it now isn't updating ANY policies when told to do so, and checking the "Components" tab of Client Center shows all of the components as "False" under the Enabled column (so essentially the client is disabled with no policies).

Checking logs, I can't see any reported failures (though it does mention skipping the User Policy download - can post the exact message if it would help). Location logs show it locating the correct local Management Point all OK etc.

So I'm stumped. The SMS Agent Host service is running all OK as well. Any idea how to kick-start this bugger?
 
Hoping it doesn't come to that. :(

I'll be on site with the physical machine on Tuesday so will see what I can do with it then as well. Such a pain having to reimage the things (not so much the process, but the users ;)).

Thanks for the reply!
 
Any errors in ccmexec.log after you restart ccmexec?

To start with, can you please open;

policyagent
policyevaluator

(use trace and merge the log files)

Kick off a machine policy and post me back the messages in between the time you kicked off the policy request and the time
 
Kicked off a machine policy download/apply.

Here's PolicyAgent:

Requesting Machine policy assignments PolicyAgent_RequestAssignments 15-03-2013 12:03:39 2204 (0x089C)
Requesting policy from authority 'SMS:SITE1' PolicyAgent_RequestAssignments 15-03-2013 12:03:39 2204 (0x089C)
Raising event:

instance of CCM_PolicyAgent_AssignmentsRequested
{
AuthorityName = "SMS:SITE1";
ClientID = "GUID:<GUID>";
DateTime = "20130315120339.090000+000";
ProcessID = 1540;
ResourceName = "COMPUTERNAME";
ResourceType = "Machine";
ThreadID = 2204;
};
PolicyAgent_RequestAssignments 15-03-2013 12:03:39 2204 (0x089C)
Click to expand...


And policyevaluator for the instance:

<![LOG[Evaluating policy in \\COMPUTERNAME\ROOT\ccm\Policy\Machine\RequestedConfig]LOG]!><time="12:04:09.777+000" date="03-15-2013" component="PolicyAgent_PolicyEvaluator" context="" type="1" thread="6004" file="policyutil.cpp:6557">
<![LOG[Evaluation not required. No changes detected.]LOG]!><time="12:04:09.777+000" date="03-15-2013" component="PolicyAgent_PolicyEvaluator" context="" type="1" thread="6004" file="policyutil.cpp:6571">
<![LOG[Raising event:

instance of CCM_PolicyAgent_PolicyEvaluationComplete
{
ClientID = "GUID:<Contains GUID>";
DateTime = "20130315120409.793000+000";
PolicyNamespace = "\\\\COMPUTERNAME\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";
ProcessID = 1540;
ThreadID = 6004;
};
]LOG]!><time="12:04:09.793+000" date="03-15-2013" component="PolicyAgent_PolicyEvaluator" context="" type="1" thread="6004" file="event.cpp:525">
Click to expand...
 
You need to go to the Client, manually uninstall the agent, reboot and install the agent again.

You can't do it from add/remove programs though. It has to be done from the command line. Google for the command

c:\windows\system32\ccm\ccmsetup /uninstall?
 
glen8 said:
You need to go to the Client, manually uninstall the agent, reboot and install the agent again.

You can't do it from add/remove programs though. It has to be done from the command line. Google for the command

c:\windows\system32\ccm\ccmsetup /uninstall?
Click to expand...

Did that for the previous removal (ccmsetup /uninstall) from interactive command prompt, confirmed the uninstall then had the user reboot. After that, ran Push installation which completed and left us where we are now.

I'll give it all a go manually when I'm there next week, though.
 
You will only be able to find the issue by looking through the logs. Drop me an email with the logs (zipped) and I will take a look to see what the issue is over the weekend if you like.

I've never had a client that's not fixable and have certainly never had to reload a machine.

Out of curiosity how many actions have you got available?
 
n30_mkii said:
You will only be able to find the issue by looking through the logs. Drop me an email with the logs (zipped) and I will take a look to see what the issue is over the weekend if you like.

I've never had a client that's not fixable and have certainly never had to reload a machine.

Out of curiosity how many actions have you got available?
Click to expand...

Out of the office now, but will undoubtedly update this on Tuesday when I have the machine in-hand. I'm assuming when I get to it that the client will only offer the User and Machine policy actions. I've seen this happen before, but it was easily fixable with a policy update. They just don't seem to be getting through somehow in this instance.
 
The only time I've seen this happen is when the client is on a different subnet and cant find the management point

There is an install command which specifies where the server is

something like ccmsetup /mp=SITECODE

That command is wrong but it's something like that (memory is rubbish)
 
Site assignment (or MP location) is one reason yes... However I believe in this instance locationservices is correctly locating its MP.

Once full logs are posted it will be easier to troubleshoot, but there are numerous issues that can cause this behaviour.

(And FYI you are referring to SMSMP - MP just tells ccmsetup where to pull it's files from (slightly different with 2012 of course, using MP produces DP list for ccmsetup content)).
 
Quick update, folks!

All sorted. Turned out when I got to the office that others weren't receiving packages they should have, but didn't report it. Also tried to reimage a desktop that needed doing for a different issue and found that PXE boot images didn't seem to be available anymore from the local server. Took a look at the most recent packages and found they weren't actually getting to the DP/MP in question.

Quick look at distmgr.log and hey presto - WMI problem on the server itself. Fixed that, rebooted, and everything kicked into gear. The client was innocent on this occasion, Your Honour!

Thanks for all the help and suggestions. :)
 
You must log in or register to reply here.
Back
Top Bottom