For those who have it live. Is it possible to have the software update point just for offline updating the images for os deployment and not replacing wsus for clients?
Printable View
For those who have it live. Is it possible to have the software update point just for offline updating the images for os deployment and not replacing wsus for clients?
In my experience having WSUS set up "normally" can cause problems with SCCM.
As a matter of interest, why would you want to do this? The updates management in 2012 is far superior to using WSUS alone. With SCCM 2007 there was a lot of hand-holding for sure, but now you really can "set and forget"
I would recommend against it - as @eejit has said, it can really screw up the updates.
Most of the time it will just fail, but I have seen it where end users get their updates from SCCM correctly, and then get updates from WSUS!
This is more of a problem if you have suppressed reboots in SCCM, as the WSUS updates will forceably reboot the system when the updates are complete
Thanks for the replies. Basically the NM sees no reason to switch to sccm for windows updates as wsus works. But I would like the ability to update images rather than re-capturing an image with updates applied.
This definitely a nice feature they have included into SCCM 2012. But just like the others have said, definitely go for the whole package!
Putting a CD in each computer to install software and an OS works. Going round with a pen and paper and making a note of what's installed on the machine works. Why do you need SCCM at all? There's no reason to use any of it! :p
I kid, I echo the rest of the responses really. Setting up software updates is a bit of a pain in the bum but it will make your life easier, if only because of the reporting facilities.
Echoing others here really...it can take a bit of getting your head around it but its worth it. Its much more set and leave since there are now auto approval, which you had to use wsus for.
Did those of you who use SCCM 2012 exclusively to push out updates transfer your WSUS database into SCCM so it knows what updates have already been applied to clients? Does this feature exist or does SCCM already know what updates have been applied once the client has been installed?
I'm not aware of such a feature other than SCCM's inbuilt Software Inventory which it uses to decide what is installed and what needs to be installed - including Windows Updates. This is because SCCM prefers to have a clean WSUS installation with no configuration at all - in fact it is recommended that if you have WSUS already installed, that you uninstall WSUS and install it, then cancel the configuration wizard and let SCCM do that for youQuote:
Originally Posted by jaminben
Whilst you can use an existing WSUS install, its not best practice to do so.
Thanks Gatt,
So what your saying is that we need to remove WSUS from our current DC and dump the database?
We'll be installing SCCM on a new 2008 R2 server which will have WSUS installed as a role but wont have any Products & Classifications selected and too let SCCM control/manage the deployment of updates. What we don't get was how to go about making sure all the old updates we had are pre-selected for SCCM to download.... if that makes sense.
Yeah - remove the current WSUS role
install it on the SCCM servers (its a prereq anyway iirc) but DO NOT run through the config wizard - cancel out of it
Finish installing SCCM, and then goto Admin -> Site Config -> Servers and Site System Roles -> Server where WSUS will go -> Add the Software Update Point role
Once its installed goto Admin -> Site Config -> Sites -> <site name> -> Configure Site Components (on the ribbon) -> Software update Point. Its this dialog that you actually configure WSUS via SCCM - its pretty much the same dialog as is in WSUS.
Ok, and then we would go through the list and manually select all the updates we had previously installed via WSUS.Quote:
Originally Posted by jaminben
Yeah - SCCM will then pull the metadata down via WSUS so you can then select what updates you want / need
It will only download them when you are ready to deploy them to clients - unlike WSUS which downloads everything anyway!
Ok Gatt, thats great.
Thanks for taking the time to reply to my questions :)
No worries :)
Give us a yell if you get stuck :)