SCCM client on SCCM server/MP itself - patching
Hi. I've a query about the SCCM client on the SCCM server itself. Can't find much previous discussion on this on the web. My SCCM server is also my MP and WSUS. Apart from the fact that the logs for the client are located in ?:\sms_ccm\logs, is there anything else I should that is special or one should be aware of?
Also, I've successfully gotten the SCCM server to patch workstations and servers, and used maintenance windows to patch servers and automatically reboot them. Now I am looking at trying to do this for the SCCM server itself. Is this recommended? You you treat the server like any other server when it comes to patch updates?
At the moment, this isn't working. I can't see any errors in the logs. And there is a prompt in the system tray to say "software update(s) are available for installation". These are the October updates which I have successfully rolled out to other servers. If I click on the prompt and use the wizard to try and manual install the updates, this does not work. The "status" of each update is "failed". Can anyone suggest where I could be going wrong here?
Thanks!
Answers
- Thanks John. Think I have it resolved. (first started Remote Registry service) I was able to reinstall the client by right-clicking on the server in a collection and follwoing the "install client" wizard. The "sms_ccm" folder looks better now, and some updates installed successfully. I'll leave it over the weekend now and see if the automated tasks, maintenance windows, etc kick in.
All Replies
I may have found a simple answer. By checking the "states 1 - enforcement states for a deployment" I saw there was a 2147217406 error message. This can be related the the Remote Registry service, and this was indeed stopped. I started it and and now the report has changed the status to "Waiting for maintenance window before installing". Hopefully this is good, test another patch deployment without maintenance windows.
But as a related issue, is there anything particular to be aware of in relation to the SCCM client on the SCCM server?- I have always treated it as if it were any other client.
In fact, every night at 3AM, our WSUS policy enforces machines to reboot if WUA indicates it is waiting on said reboot, including our SCCM boxes and all non-essential Windows servers.
We have also sent DST patches to all boxes, including itself, using SUP and have never noticed an issue. - Something isn't right with my SCCM client on my SCCM server. When I try and click on "repair" in the Components tab of the client properties, nothing happens. Unlike any other server where you clearly see activity (both on-screen and in Task Manager). I also notice that "[drive letter]:\sms_ccm" does not contain a "cache" folder, unlike other servers which have "c:\windows\system32\ccm\cache".
Would anyone have tips on how to fix this? Would you recommend uninstalling the client and reinstalling it? The SCCM server is also the WSUS location and MP. Not sure which log files will best tell me what it going on with it. All my other SCCM clients are behaving normally with one other exception, an ISA server, but that has it own issues. - You could try removing and reinstalling it. I have had mixed results trying to do remove the client from MP's. Try it first in the supported manner (ccmsetup /uninstall) if that doesn't work and it gets hung there's something else I can tell you to try but it's TOTALLY unsupported so I won't post it unless Ihave too ;-)
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum - Thanks John. Think I have it resolved. (first started Remote Registry service) I was able to reinstall the client by right-clicking on the server in a collection and follwoing the "install client" wizard. The "sms_ccm" folder looks better now, and some updates installed successfully. I'll leave it over the weekend now and see if the automated tasks, maintenance windows, etc kick in.
