Hi, I have just gone through the companies method for windows updates, and its seems amazingly labour intensive. I have yet to find out the reasons for not "just" using" wsus so can we assume this is sthe mothod of choice just looking for corners to cut.
secure environment
WSUS server out of domain just sat on adsl line.
when a list of updates gets approved by the patch release people.
we go to this machine and approve for install the releavnt updates
taking note of the url of each eg CF\238923R38JFDSJ and the KB
then they are approved in WSUS then the folder is compared to the old one and the new files piped out to a NEw folder, thus giving me all the files i need to do this months updates.
i then usb this on to the real enviroemnt do the testing, and then it all goes in to SCCM for deployment.
when you add in the paperwork and the long list of variables xp32 xp64 2003 32 etc etc its a really big piece of work and just seems wastful of my time.
we allso create uninstall files for each for SCCM.
so basic questions is, do you use SCCM to deploy WSUS and if so what method do you use to get only th eupdate syou want in to sccm, (no internet connection!!)
hope that makes sense.
winodws 2003 sccm2007
ASKER
when i say test there more integration rigs, so its our method that gest used.
Last compoany i used WSUS and it was fine, this just sems such a ball ache to do (because im doing it this month.
in a way the method works is secure, deals with testing double checks they uninstall etc.
but, you know when you choose a particular KB in wsus, it downloads every iteration not just say 2003 64 is that doable?
ill read links when rugrats are in bed cheers