GhostRidr

I recently had some Office 2010 clients hang at installing the service pack with an SCCM push. Saying "Waiting to Install" in Software Center. All other updates installed. It took manually downloading that SP and installing to get that resolved. Today comes the same thing, except this time with a newly installed 2008R2 server, and the SP1 patch. It installed other updates ok, but is hanging in Software Center at "Waiting to Install" for the SP1. Not knowing where the package was on the system, I deleted the entire CCM cache and rebooted. Reran some of the actions to initiate the download, and it did pull down the SP1 package. I can see it sitting there in the only folder I have now in CCM cache. But once again it is stuck at Waiting to Install. I'd rather not manually try installing SP1 and figure out why SCCM is not working in this instance, and further understand why Office 2010 SP1 was failing for me recently too. Any ideas?

Turning off the notifications to users would definitely be a big help, though I'm unsure how to apply this through GP. But ultimately restricting their access to Software Center would be best. Becasue even if they don't get the update notification they would still be able to go to it and possibly end up restarting the system.

Very new to SCCM. Have recently installed SCCM 2012 and it's working good, but still learning. One particular problem I have is the desire to limit access to the Software Center on a specific computer. Actually a server. It's a server we use for terminal access. I don't need users rebooting the server when they see that updates are available. Yet I want ever other computer in the building to have user interaction with Software Center and the decision of when to let updates install. How can I limit access for just one PC to administrators only?