Critical Status for SMS_CLIENT_CONFIG_MANAGER component
For the two years I have been running SCCM 2007 My SMS_CLIENT_CONFIG_MANAGER component has been in an almost constant state of "critical because it continuously tries to connect to machine... that are most likely off, or don't exist anymore... is there a way to get it too not do this? It makes the logs rather large as well. BELOW IS AN EXAMPLE MESSAGE OF WHAT I AM GETTING: SMS Client Configuration Manager cannot connect to the machine "LMS-RM205-01". The operating system reported error 67: The network name cannot be found. Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. Possible cause: A remote client installation account was not specified in the SMS Admin console, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active remote client installation accounts are specified in the SMS Admin console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines Thank you!
July 6th, 2011 5:42pm

So the client has been removed from the server and all your reports show that machine isn't there. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2011 5:45pm

No, those machines still exist... its summer and a lot of them are turned off right now between school years. Is it normal for it to try and contact machines and complain because there offline though?
July 6th, 2011 5:49pm

Are these site servers or BDP's? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2011 6:06pm

Its a smaller school district, its the only SCCM Server besides the SQL/Reporting server.
July 6th, 2011 6:08pm

So to answer your question then: There is nothing you can do. You basically either need to get the machine turned on so ConfigMgr can complete it's operation such as copying a package or whatever it needs access to the machine to do or ignore the error (increase the threashold so you don't turn red as quickly) If it is trying to install the ConfigMgr client via a right click push then it will give up after 7 days of trying. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2011 4:12pm

Ok, I kind of thought that would be the answer... Just wanted to check and see if maybe I was missing something. Thanks!
July 7th, 2011 5:13pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics