thanks, that was helpful.
Main Topics
Browse All TopicsOur SCCM server is stuck at 100% CPU Utilization. This problem started after pushing clients out via enabling the 'Automatic client push for discovered computers' option . We have cancelled all of the client pushes, and are trying to get the CPU utilization to return to normal by doing the following:
*Unchecked the Automatic client push for discovered computers option.
*There are no CCR records within the \inboxes\ccr.box and \inboxes\ccrretry.box (had to delete a few files)
*There are no DDR records within the \inboxes\ddm.box
*Ran %windir%\system32\ccmsetup
*Removed boundaries which displayed (but were not needed)
*Ran a AD System Discovery as soon as the boundaries were cleared (The Assigned value for machines in those boundaries did not change from Yes to No like we expected them to after the refresh)
*The only discovery methods enabled are AD System Discovery and Heartbeat Discovery, set for once a day at 12am
*When the SMS_Executive service is manually stopped, the CPU usage returns to normal.
I am not quite sure what else to do. What I need is:
*Verify which clients received the client, remove if not yet needed.
*Figure out what is causing the SMS_Executive Service to use 100% CPU utilization and stop it.
Can anyone offer any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: JonLambertPosted on 2009-09-04 at 13:46:16ID: 25263211
Try http://support.microsoft.c om/kb/8373 72 to work out what SMSEXEC thread(s) is causing the issue.. I've seen this on Secondaries (and have a work around), but never on a primary. It's more than likely that SMSEXEC is continuing to create threads for a particular proccess.