UPDATED - CCMExec Fails, CCMRepair caught in a loop (SCCM Remote Tools getting Disabled in Registry)

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

UPDATED - CCMExec Fails, CCMRepair caught in a loop (SCCM Remote Tools getting Disabled in Registry)

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> UPDATED - CCMExec Fails, CCMRepair caught in a loop (SCCM Remote Tools getting Disabled in Registry)

Page: [1]

Message

<< Older Topic Newer Topic >>

UPDATED - CCMExec Fails, CCMRepair caught in a loop (SC... - 9/8/2008 11:20:34 AM

legacy99

Posts: 3
Score: 0
Joined: 12/13/2007
Status: offline

Greetings.
In the last week or two some of the SCCM clients are losing thier settings under HKLM\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control. It looks like a default policy when compared to a working client (eg: Audible Signals are disabled on working pc's but not the broken ones, etc). All other client components seem to be working fine. The only recent change we made was we rolled out IE7 to the pc's that have been affected but I can't see that causing the problem. What client logs or settings could I look at to tell me why the remote tools are not getting the right policy from the server or even better, how could I kickstart them to read the right policy?
Thanks

< Message edited by legacy99 -- 9/10/2008 12:58:25 PM >

Post #: 1

RE: SCCM Remote Tools getting Disabled in Registry - 9/10/2008 12:56:41 PM

legacy99

Posts: 3
Score: 0
Joined: 12/13/2007
Status: offline

Hi Again
It looks like I jumped the gun, the remote error is a side effect. What appears to be happening is ccmexec is failing and ccmrepair is caught in a loop. So far it looks like a WMI component is broken (what? WMI broken??). I can quickly identify the pc's affected if I do a machine policy refresh, I get:
Acion failed on %computername% Error: -2147024891 Description: Access is Denied
In the CCMExec logs I see:
-Performance counter registrations are missing or corrupted. Repair required.
-Detected faulty configuration. Repair will be started in 5 minutes. CcmExec 9/9/2008 4:38:24 PM 832 (0x0340)
-Error invoking shutdown system tasks (0x8000ffff) CcmExec 9/9/2008 4:43:24 PM 832 (0x0340)
-Error waiting for tasks (0x8000ffff), will shut down anyway.
-UninitCommandExec failed (0x800401fb). CcmExec 9/10/2008 11:32:36 AM 648 (0x0288)

CCMRepair log has nothing useful. I've tried resetting WMI and repairing WMI with mixed results, some will take others will fail at next reboot, others dont work at all.
WMIDiag has 1 line of question that I can see:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {B019CAE0-D910-410F-AD15-5AFA0E58DF61}
I compared the Dcom settings on an offending pc with a working one and there was no difference.
Anyone seen this or know what I should look at next?

(in reply to legacy99)

Post #: 2