SCCM "components" out of date

Hello everyone,
 
I'm finding a small number of client machines in my environment, whose client version is out-of-date.  Specifically, the CCM Framework and ConfigMgr Software Distribution agent are 4.0.6487.2000, though we are approved/running at 4.0.6487.2155/2154 respectively.
 
The clients with outdated components do not regularly get Windows Updates and other software, so it's not just a cosmetic problem.  I've tried the "Repair" option in the Control Panel -> Configuration Manager, but that does not typically fix anything.  Is there a way to troubleshoot/fix without completely uninstalling and reinstalling the SCCM client?  I ask because some of these machines are servers, and if there is a way to fix without too much fiddling, that would be ideal.
 
If I do have to uninstall and reinstall the SCCM client, is a reboot required before the reinstallation process?  What about "CCMClean" recommendations?  Sorry if these are newbie questions; I'm relatively new to the SCCM world.
 
Thanks,
Chris

If "repair" doesn't work from the control panel, here's a few things to try before an uninstall / reinstall (which isn't a big deal, by the way, even if you do have to).
1) using Roger Zander's Client Center, on the Agent Actions, Install/Repair tab; you could try Repair WMI there (and click on the yellow folder icon to watch the log).  Once the repair is done, try something to see if it works correctly now.
2) Delete root\ccm; then give the client a while to recover from that.  then test again.
3) otherwise, yeah; just ccmsetup /uninstall  (watch ccmsetup.log until it's gone), and then whatever you use to ccmsetup normally to put the client back on.  A reboot should not be necessary; the only time I've seen a reboot due to the ccmsetup is because a BITS requirement isn't there.  Since the client was previously installed, the BITS pre-req is there already.
 
Regarding ccmclean; it's not meant for CM07.  That's not to say I haven't used it anyway.  I have run ccmsetup /uninstall, waited until ccmsetup.log says successfully uninstalled, then ccmclean /client, then reinstalled the client.  Never seemed to hurt, even though it's not supported to use ccmclean.  If you are going the uninstall/reinstall route, I'd try it without ccmclean first.

Thanks for the suggestions.  I tried option 3 (uninstalled and reinstalled the SCCM client) yesterday, but it doesn't seem to have done the trick on the server that I'm currently troubleshooting.  The current symptoms are that the approved Windows Updates are not downloading/installing (no SCCM update icon ever shows up on this server.)  If I look at the server through the SCCM Client Center Tool, clicking on "Show Approved Patches" doesn't show anything at all.  "Show All Patches" does however show an accurate report of what's installed on the server.
 
Does that sound like a WMI problem?  Before I uninstalled/reinstalled the SCCM client, I did a "Reset Policy" last week, but that did not work.  If this sounds like a WMI issue, I guess the next step would be a "Repair WMI" through the client center tool.  What exact commands does that entail?  Is it the same as running "winmgmt /salvagerepository"?  This is a Windows 2008 R2 SP1 server...
Two additional pieces of info that may help:
1) in ClientIDManagerStartup.log, I'm seeing "GetCurrentClientVersion failed (0x80070002)"
2) in CAS.log, I'm seeing "GetLogonUserSid failed at GetTokenSids (0x800703f0)"
 
Thanks

if nothing shows up in "show approved patched", to me that means the client isn't in a collection which is a target of a currently active Deployment.
 
Does policyagent.log show that it's picked up policies recently?  what collections is that box inside when looking at the console? 

Thank you Sherry.  It does indeed appear that this particular server is missing from the target collection.
 
Now the question is why that collection query (which is supposed to compile all servers that are part of the domain into a specific collection) is failing.  I'll start another thread if I can't get that query part figured out.
 
Chris