On Fri, 8 Aug 2008 06:58:08 -0700 (PDT), email@example.com wrote:
>On Aug 8, 5:08*am, DaveMills <DaveMi...@newsgroup.nospam> wrote:
>> On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote:
>> >I am happy to report I have got it working. Clients are reporting and
>> >getting updates. The only issue now is they are not populating the
>> >WSUS Computer Groups as in GP OUs.
>> Two possibilities:
>> 1) The client is not being told which group to use in the GPO or the spelling of
>> the group does not match that is WSUS console.
>> 2) The WSUS server is not set to use Client Side Targeting.
>> > I followed instructions from
>> >To summarise what I have done:-
>> >1. check the correct level of permission, ISUR_IISserver user for all
>> >the relevant folders. and anonynous user is checked on the Default
>> >2. IP address is Unassign for Default website
>> >Thank for all the help
>> Dave Mills
>> There are 10 type of people, those that understand binary and those that don't.
>I have Client side targeting setup. The OUs are nested like
>1. Client systems\XP\Workstations
>2. Client systems\XP\Laptops
>How do I name them in GP ?
Use the setting in the WSUS policy settings
Computer\Windows Components\Windows Update\Target group name for this computer
You can either create a separate GPO for Laptops and Workstations with all the
setting you need for each.
Create a GPO for XP with all the settings for all sub OUs and then have other
GPO for Loptops OU etc which supply just the different settings such as
You decide which, is it easier to have central setting for everything and
overwrite these with the exception or just have totally separate GPOs and have
to make change in all if something changes.
I would definitely have WSUS setting in a GPO or their own and not added to
Workstation Settings or Laptop Settings. It is too hard to maintain otherwise.
There are 10 type of people, those that understand binary and those that don't.