There is no need to use WSUS console if you are using ConfigMgr and SUP for patch management. We can configure everything from SCCM console. Local policies, not based on AD. More details on policies, please have a look at Jason Sandy's blog posts mentioned below http://myitforum.com/cs2/blogs/jsandys/archive/2010/05/09/software-update-management-and-group-policy-for-configmgr-what-else.aspx http://blogs.catapultsystems.com/jsandys/archive/2010/05/28/software-updates-management-and-group-policy-for-configmgr-cont-.aspx Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

The ConfigMgr client creates a local policy and they can be found here: http://technet.microsoft.com/en-us/library/cc978269.aspx.Torsten Meringer | http://www.mssccmfaq.de

Thanks Jason. I'll create an stand alone WSUS infrastructure to manage the workstations. And a second one managed by SCCM for the servers. Is that supported, working ?Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Quick ammendment to the above. You can use WDS for serving up non-ConfigMgr boot images (http://www.mssccmfaq.de/2010/05/18/parallelbetrieb-von-wds-und-pxe-servicepoint/) if you are not using unknown computer support. With unknown computer support, the PSP will always server up a ConfigMgr boot image. On the WSUS, yes, it works fine. You'll control the workstations with a GPO (nothing different there) and ConfigMgr will control the servers. Nothing different there either. The local WUA agents on the systems tell them where to go which is controlled by a group policy (see my blog posts listed by Anoop above for details).Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys

ThanksPeter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Dear. I’m new to SCCM and I have some questions about how to place SCCM and WSUS/WDS. Microsoft says that SCCM integrates smoothly with WSUS and WDS, but they don’t tell you the global conceptual view. Today, we have a WSUS infrastructure with one primary WSUS, and a lot of child WSUS servers. Settings to clients is done through GPO. We’re in the process of installing an SCCM infrastructure and I miss the global conceptual feeling about the SCCM-WSUS/WDS relation. SCCM seems to be an additional management layer on top of WSUS. But: · What about the settings, settings can now be done in WSUS and in SCCM. Who’s the master? ON SCCM, I configured to download 2 languishes, on the WSUS, I still see only one language configured??? · With SCCM, It’s the SCCM agent who installs the updates. In our case, workstations are out of scope and they still need to be updated through WSUS. Can both exists next to each other while the WSUS servers are now managed by SCCM? · Do we still need the AD policy to deploy the settings to servers that are managed through SCCM? · Do I install the software update points onto the existing WSUS servers? If I deploy the software update point on an existing WSUS server, do I need a SCCM server license? Actually, I have the same remarks and question about WDS and SCCM · SCCM is an additional management layer on top of WDS?? SCCM is used as management interface to manage the underlying WDS? · We have an existing WDS infrastructure, should I enroll my distribution service point onto this server? Do I need an additional SCCM Server license for this role? Thanks a lot in advance, Regards, PeterPeter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

WSUS - ConfigMgr will control the WSUS settings - ConfigMgr triggers/controls the WUA client - no need for GPOs: ConfigMgr creates local policies that configure the WUA client - you could install a SUP on an existing WSUS server but I'd use "clean" WSUS servers WDS - yes, ConfigMgr takes over control; no need to configure WDS manually - PXE servers can be installed on existing WDS servers, but it depends on the requirements (parallel usage of classic WDS and the PXE service point for example)Torsten Meringer | http://www.mssccmfaq.de

Thanks ! ConfigMgr will control the WSUS settings: But what with the settings on the WSUS console. Do they still have impact? What If Someone change the settinsg through the WSUS console? Why are my language settings I made in SCCM different from the one I can see through the WSUS interface. no need for GPOs: ConfigMgr creates local policies that configure the WUA client: Are that AD or computer based policies? Or settings pushed to the SCCM client on the computer. Where Can I see these policies? Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

There is no need to use WSUS console if you are using ConfigMgr and SUP for patch management. We can configure everything from SCCM console. Local policies, not based on AD. More details on policies, please have a look at Jason Sandy's blog posts mentioned below http://myitforum.com/cs2/blogs/jsandys/archive/2010/05/09/software-update-management-and-group-policy-for-configmgr-what-else.aspx http://blogs.catapultsystems.com/jsandys/archive/2010/05/28/software-updates-management-and-group-policy-for-configmgr-cont-.aspx Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

The ConfigMgr client creates a local policy and they can be found here: http://technet.microsoft.com/en-us/library/cc978269.aspx.Torsten Meringer | http://www.mssccmfaq.de

A handful of comments here. Updating non-ConfigMgr managed systems from a ConfigMgr integrated WSUS instance is not supported and will cause you issues. Approving and in particular declining updates directly in the WSUS console will mess up the update catalog for ConfigMgr. If you change settings directly in WSUS, ConfigMgr should eventually change them back to whatever is configured in the ConfigMgr -- ConfigMgr is the master. However, as mentioned by the others, you should never go into the WSUS console and change anything as it is unsupported to do so. No extra ConfigMgr licensing is needed to host site roles on separate servers. You pay per primary site and per managed client. Installing the PSP on an existing WDS instance will make that WDS instance unusuable for stand-alone WDS operations. Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys