Phunky Monkey

So I was thinking of just throwing all the Windows updates my various clients would need, including servers. My only concern is, if a client only needs a small handful of updates, will it download the entire package, or just the updates it needs? Thanks, Brenden

SD, Although the errors aren't exactly the same, I had issues with adding a '12 client where a '07 was previously installed. I too wasn't able to assign a site code. Check the client's registry to make sure it's not getting an old site code. HKEY LOCAL MACHINE/Software/Microsoft/SMS/Mobile Client, Key Name: Assigned Site Code. If it's pointing to the old site, delete it and try reassigned the client through the client's CCM GUI.

I believe I found out why the source files were deleted. I had two packages pointed to the same source location. Typically SCCM doesn't allow this to occur, but one source entry used the FQDN while the other used shorthand. I'm guessing each package saw the other package's files, decided they didn't belong, and deleted them. Hope this helps someone.

All sorts of fun questions from me today. I noticed that my sources folder, where I downloaded my Windows Updates to, is now empty. The log file looks like it considered them "orphaned" and removed the files from the source folder. Now the deployment package is reporting as failed since it can't locate any of its source files. Does this deletion occur after it creates all of the packages for the DPs? I don't seem to remember this happening in SCCM 2007. Thanks, Brenden

I am configuring Windows Updates to be pushed from SCCM 2012. I have a few collection of user computers in an collection that I have successfully pushed updates to. But a funny thing happened to one of our servers when installing the SCCM client. It looks like when the client was installed, it installed updates that I had not pushed via a deployment. I noticed the Windows Updates settings on the server were set to auto download and auto install. Does an SCCM client find updates that have been downloaded, and see them as available, regardless if they're pushed via a deployment?

So if it's onsite, it will adhere to the deployment deadline; but if it's offsite, it requires user intervention?

Had a curious question relating to Software Updates and a user going offsite. If a deployment package is set to be available on Monday, with the client downloading the package shortly after being available, and a deadline of Friday night. If a user shutdown their laptop Friday afternoon, prior to the deadline, and fired it back up Saturday offsite, would the CCM client install the software, or does it have to be in communication with the site system to do so?