I've just discovered the nested target groups in WSUS 3.0 but I can't
get my computers (not on a domain) to get into their own groups.
The registry keys are set just fine on the client :
"TargetGroup"="MyGroup"
"TargetGroupEnabled"=dword:00000001
TargetGroupEnabled can be set to 0 or 1, it makes no difference (I
suppose it has to be set to 1, right ?)
The tree on the server side is dead simple :
Clients/MyGroup
But they all end up in the "Unassigned computers"...
No big deal here but I'd like it to work the way it should...
Thanks in advance.
PJ
Hope it helps
Cheers
--
augusto alvarez | it pro | southworks
http://staff.southworks.net/aalvarez
"PJ" <p...@none.com> wrote in message news:frau8q$vh5$1...@aioe.org...
Thanks very much, that's it !
But before I change this setting I'd like to know if the registry
setting will override the console settings.
Say, if a computer has a wrong group setting in its registry (or if I
create a new group), will I be able to move it from the console to the
right group and will it stay there ?
Otherwise I think it's safer for us to stay with the "sort by hand"
option because we only use registry settings and no GPOs.
Thanks for your help.
PJ
> But before I change this setting I'd like to know if the registry
> setting will override the console settings.
>
> Say, if a computer has a wrong group setting in its registry (or if I
> create a new group), will I be able to move it from the console to the
> right group and will it stay there ?
No. If you have WSUS configured to use group policy to assign membership, you
can no longer change the membership via the console.
Harry.