In this example I’m going to show how you can safely setup Group Policy for ConfigMgr software updates to be able slowly transition off of existing WSUS environment without impacting all systems at once or modifying existing group policies and OU structure.

 

I won’t get into step by step instructions on how to create a GPO because if you aren’t familiar with that then you probably should ask for assistance as it’s relativley easy to make disastrous mistakes here.

 

Scroll down to WMI Filters in Group Policy Management console and create new filter.  This filter will be used to check if the ConfigMgr client is installed if it returns true then the policy will apply.

Namespace:
root\CIMv2

Query:
Select * from Win32_Product where name = “Configuration Manager Client”

 

WMIFilter

 

Create a new GPO and add settings for Windows Updates under Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Updates and enable settings for “Specify intranet Microsoft update service location” and enter your ConfigMgr update server url with port.

 

If you want to be able to deploy internally published updates using Updates Publisher(SCUP) you should also enable “Allow signed updates from an intranet Microsoft Update service location”.

 

GPO

 

Apply WMI filter to the GPO by selecting the one you created earlier for ConfigMgr client.

 

ApplyFilter

 

Now link the new GPO to the OU that has your target systems.  We want the link order for this ploicy to be lower than the policy that applies the existing WSUS policy.

Please refer to Technet for Group Policy processing and precedence order to ensure you have it applied correctly.
http://technet.microsoft.com/en-us/library/cc785665(v=WS.10).aspx