loadingleo.blogg.se - Group policy link enabled

The SCCM Software Update supports third party updates when used in conjunction with System Center Updates Publisher 2011.

You want to ensure that computers are only patched during a “Maintenance Window” (however even this can be done using Group Policy) and that these patches do not install if it will take longer than that window.

(However there is a way to do something similar using Group Policy).

You require to wake computers using WOL for them to be patched out of hours.

However there are a couple of reason why I think SCCM should still be used over WSUS and they are: The reason why I still normally recommend that people using WSUS over SCCM is that the product overall is much easier to use and its just human nature for people to want to do the easier tool where possible…

I also believe that even if you have bought and implemented System Center Configuration Manager in your environment then you are probably still better off using WSUS for manage you updates for your Microsoft software. Having implement WSUS for an environment of over a combination of 10,000 servers and workstations I can truly say that this tool scales really well. I am also going to assume that you are familiar with WSUS and already have it deployed in your organisation… Is WSUS the right tool for your organisation? What I hope this post will teach you is how to use Group Policy in your environment to milk the absolute most out of your existing WSUS infrastructure. WSUS is also a requirement for the Software Update option in SCCM 2007.

In my experience this tool is pretty much used by every organisation in the world that has more than a hand full of computers.

WSUS) is Microsoft free tool they provide for deploying patches and updates.