|
|
In WSUS 2.0, I enabled client side targeting but not auto-assignment on the
server end. The computer object would then show up in WSUS with a "Requested
Group" (I did not enable automatic assignment to groups on the server side
because sometimes people travel and computers would end up in the wrong
group).
Anyway, because the computer object showed the requested group, I could
check and then move it to the right group.
Now, when a new computer shows up in the Unassigned list, I have no idea
which Group Policy the computer used.
I would like to see the return of the Requestd Group feature,
|
|
In the details for the Computer there is a "Group Membership" line. This is
where the Groups that are assigned by the GPO will reside.
--
Cecil [MSFT]
Deployment, WSUS
Microsoft
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"HB" <HB[ at ]discussions.microsoft.com> wrote in message
news:C453662D-1156-41F1-980C-70477B8289AE[ at ]microsoft.com...
[Quoted Text] > In WSUS 2.0, I enabled client side targeting but not auto-assignment on
> the
> server end. The computer object would then show up in WSUS with a
> "Requested
> Group" (I did not enable automatic assignment to groups on the server side
> because sometimes people travel and computers would end up in the wrong
> group).
>
> Anyway, because the computer object showed the requested group, I could
> check and then move it to the right group.
>
> Now, when a new computer shows up in the Unassigned list, I have no idea
> which Group Policy the computer used.
>
> I would like to see the return of the Requestd Group feature,
>
>
|
|
Thanks for your reply. Unfortunately, this is not the case. For example, I
have a server that showed up in the Unassigned Computers group. I know for a
fact the GPO for this server sets a target a group called "Servers".
However, all I see in the Group Membership field is All Computers and
Unassigned Computers.
"Cecils(MSFT)" wrote:
[Quoted Text] > In the details for the Computer there is a "Group Membership" line. This is > where the Groups that are assigned by the GPO will reside. > -- > Cecil [MSFT] > Deployment, WSUS > Microsoft > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "HB" <HB[ at ]discussions.microsoft.com> wrote in message > news:C453662D-1156-41F1-980C-70477B8289AE[ at ]microsoft.com... > > In WSUS 2.0, I enabled client side targeting but not auto-assignment on > > the > > server end. The computer object would then show up in WSUS with a > > "Requested > > Group" (I did not enable automatic assignment to groups on the server side > > because sometimes people travel and computers would end up in the wrong > > group). > > > > Anyway, because the computer object showed the requested group, I could > > check and then move it to the right group. > > > > Now, when a new computer shows up in the Unassigned list, I have no idea > > which Group Policy the computer used. > > > > I would like to see the return of the Requestd Group feature, > > > > > > |
|
Cecil,
I am having the same issue as HB with the Requested Group issue. I cannot
get any machine to report directly into the group based on the GPO/Registry
settings.
"Cecils(MSFT)" wrote:
[Quoted Text] > In the details for the Computer there is a "Group Membership" line. This is > where the Groups that are assigned by the GPO will reside. > -- > Cecil [MSFT] > Deployment, WSUS > Microsoft > > This posting is provided "As Is" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm> > "HB" <HB[ at ]discussions.microsoft.com> wrote in message > news:C453662D-1156-41F1-980C-70477B8289AE[ at ]microsoft.com... > > In WSUS 2.0, I enabled client side targeting but not auto-assignment on > > the > > server end. The computer object would then show up in WSUS with a > > "Requested > > Group" (I did not enable automatic assignment to groups on the server side > > because sometimes people travel and computers would end up in the wrong > > group). > > > > Anyway, because the computer object showed the requested group, I could > > check and then move it to the right group. > > > > Now, when a new computer shows up in the Unassigned list, I have no idea > > which Group Policy the computer used. > > > > I would like to see the return of the Requestd Group feature, > > > > > > |
|
We do not display the requested target group names in the details pane for a
computer in WSUS 3.0. We display that information as a "To do" item in the
Home Page. The home page will list all the missing target group names.
Thanks, Siva
"deltaxi60" <deltaxi60[ at ]myalias.postalias> wrote in message
news:956CAA3F-35CF-45CF-BC9B-7BBFAF5D0C3A[ at ]microsoft.com...
[Quoted Text] > Cecil, > > I am having the same issue as HB with the Requested Group issue. I cannot > get any machine to report directly into the group based on the > GPO/Registry > settings. > > "Cecils(MSFT)" wrote: > >> In the details for the Computer there is a "Group Membership" line. This >> is >> where the Groups that are assigned by the GPO will reside. >> -- >> Cecil [MSFT] >> Deployment, WSUS >> Microsoft >> >> This posting is provided "As Is" with no warranties, and confers no >> rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm>> >> "HB" <HB[ at ]discussions.microsoft.com> wrote in message >> news:C453662D-1156-41F1-980C-70477B8289AE[ at ]microsoft.com... >> > In WSUS 2.0, I enabled client side targeting but not auto-assignment on >> > the >> > server end. The computer object would then show up in WSUS with a >> > "Requested >> > Group" (I did not enable automatic assignment to groups on the server >> > side >> > because sometimes people travel and computers would end up in the wrong >> > group). >> > >> > Anyway, because the computer object showed the requested group, I could >> > check and then move it to the right group. >> > >> > Now, when a new computer shows up in the Unassigned list, I have no >> > idea >> > which Group Policy the computer used. >> > >> > I would like to see the return of the Requestd Group feature, >> > >> > >> >>
|
|
On Thu, 24 May 2007 10:34:09 -0700, "Siva Shanmugam [MSFT]"
<sivsha[ at ]online.microsoft.com> wrote:
[Quoted Text] >We do not display the requested target group names in the details pane for a
>computer in WSUS 3.0. We display that information as a "To do" item in the
>Home Page. The home page will list all the missing target group names.
You have to create groups in the WSUS console before the group is available to
the client. It is not automatically created just because it is in the GPO. Hence
the To List for missing ones.
>
>Thanks, Siva
>"deltaxi60" <deltaxi60[ at ]myalias.postalias> wrote in message
>news:956CAA3F-35CF-45CF-BC9B-7BBFAF5D0C3A[ at ]microsoft.com...
>> Cecil,
>>
>> I am having the same issue as HB with the Requested Group issue. I cannot
>> get any machine to report directly into the group based on the
>> GPO/Registry
>> settings.
>>
>> "Cecils(MSFT)" wrote:
>>
>>> In the details for the Computer there is a "Group Membership" line. This
>>> is
>>> where the Groups that are assigned by the GPO will reside.
>>> --
>>> Cecil [MSFT]
>>> Deployment, WSUS
>>> Microsoft
>>>
>>> This posting is provided "As Is" with no warranties, and confers no
>>> rights.
>>> Use of included script samples are subject to the terms specified at
>>> http://www.microsoft.com/info/cpyright.htm
>>>
>>> "HB" <HB[ at ]discussions.microsoft.com> wrote in message
>>> news:C453662D-1156-41F1-980C-70477B8289AE[ at ]microsoft.com...
>>> > In WSUS 2.0, I enabled client side targeting but not auto-assignment on
>>> > the
>>> > server end. The computer object would then show up in WSUS with a
>>> > "Requested
>>> > Group" (I did not enable automatic assignment to groups on the server
>>> > side
>>> > because sometimes people travel and computers would end up in the wrong
>>> > group).
>>> >
>>> > Anyway, because the computer object showed the requested group, I could
>>> > check and then move it to the right group.
>>> >
>>> > Now, when a new computer shows up in the Unassigned list, I have no
>>> > idea
>>> > which Group Policy the computer used.
>>> >
>>> > I would like to see the return of the Requestd Group feature,
>>> >
>>> >
>>>
>>>
>
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
|
|
|