Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.update_services
Thread: WSUS 2.0 Client-Side to Server-Side

HTVi
TV Discussion Newsgroups

WSUS 2.0 Client-Side to Server-Side
John 5/18/2007 12:04:01 AM
All,

We have WSUS 2.0. I need to change (at least temporary) from Client-Side
Targeting to Server-Side Targeting. Currently have GPO's in my machine OU's
pointing to my Computer Groups in WSUS.

If I change my WSUS Computer Options to "Use the Move computers task in
Windows Server Update Services" for Server-Side Targeting, can I leave my
GPO's alone or will I need to Disable or Not Configure the "Enable
client-side targeting" setting in the GPO's?

Also, working while with Server-Side Targeting, I assume any new machine
will appear in the Unasigned Computers Group in WSUS regardless of it's
Machine OU as long as the OU has the GPO. Then I'll simply move the machine
into it's appropriate WSUS Computer Group for manageability. Please correct
me if I'm wrong.

Thanks,
John


Re: WSUS 2.0 Client-Side to Server-Side
"Matthew Wetmore \(MSFT\)" <mattwe[ at ]online.microsoft.com> 5/18/2007 1:56:36 AM
Having the GPO set while the server is in server side targeting mode is not
a problem. The value is ignored.

I'm not entirely sure whether computers that have checked in under a group
will stay there after the switch to server side. I'll try to ask an
appropriate person to find out - though my newsgroup time is sporadic.
Another participant may know. I *suspect* the group membership will stick
for machines that have already checked in.

And yes, new machines checking in will go to Unassigned and can then be
moved.

--
Matthew Wetmore
Developer, WSUS (Windows Server Update Services)

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

"John" <John[ at ]discussions.microsoft.com> wrote in message
news:29DF3208-338C-4FDC-AA7D-3CB940E02C0B[ at ]microsoft.com...
[Quoted Text]
> All,
>
> We have WSUS 2.0. I need to change (at least temporary) from Client-Side
> Targeting to Server-Side Targeting. Currently have GPO's in my machine
> OU's
> pointing to my Computer Groups in WSUS.
>
> If I change my WSUS Computer Options to "Use the Move computers task in
> Windows Server Update Services" for Server-Side Targeting, can I leave my
> GPO's alone or will I need to Disable or Not Configure the "Enable
> client-side targeting" setting in the GPO's?
>
> Also, working while with Server-Side Targeting, I assume any new machine
> will appear in the Unasigned Computers Group in WSUS regardless of it's
> Machine OU as long as the OU has the GPO. Then I'll simply move the
> machine
> into it's appropriate WSUS Computer Group for manageability. Please
> correct
> me if I'm wrong.
>
> Thanks,
> John
>
>


Re: WSUS 2.0 Client-Side to Server-Side
"Cecils\(MSFT\)" <cecils[ at ]online.microsoft.com> 5/18/2007 10:43:25 PM
Yes, Machines that have already checked into a group, before the switch to
Server side targeting, will remain in that group when you switch the server.
If you change the GPO while in Server side targeting will not change on the
WSUS server.

--
--
Cecils [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

"Matthew Wetmore (MSFT)" <mattwe[ at ]online.microsoft.com> wrote in message
news:OPFcF$OmHHA.4552[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> Having the GPO set while the server is in server side targeting mode is
> not a problem. The value is ignored.
>
> I'm not entirely sure whether computers that have checked in under a group
> will stay there after the switch to server side. I'll try to ask an
> appropriate person to find out - though my newsgroup time is sporadic.
> Another participant may know. I *suspect* the group membership will stick
> for machines that have already checked in.
>
> And yes, new machines checking in will go to Unassigned and can then be
> moved.
>
> --
> Matthew Wetmore
> Developer, WSUS (Windows Server Update Services)
>
> 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
>
> "John" <John[ at ]discussions.microsoft.com> wrote in message
> news:29DF3208-338C-4FDC-AA7D-3CB940E02C0B[ at ]microsoft.com...
>> All,
>>
>> We have WSUS 2.0. I need to change (at least temporary) from Client-Side
>> Targeting to Server-Side Targeting. Currently have GPO's in my machine
>> OU's
>> pointing to my Computer Groups in WSUS.
>>
>> If I change my WSUS Computer Options to "Use the Move computers task in
>> Windows Server Update Services" for Server-Side Targeting, can I leave my
>> GPO's alone or will I need to Disable or Not Configure the "Enable
>> client-side targeting" setting in the GPO's?
>>
>> Also, working while with Server-Side Targeting, I assume any new machine
>> will appear in the Unasigned Computers Group in WSUS regardless of it's
>> Machine OU as long as the OU has the GPO. Then I'll simply move the
>> machine
>> into it's appropriate WSUS Computer Group for manageability. Please
>> correct
>> me if I'm wrong.
>>
>> Thanks,
>> John
>>
>>
>
>

Re: WSUS 2.0 Client-Side to Server-Side
John 5/21/2007 12:59:00 AM
Matthew & Cecils,

I appreciate your assistance. Sounds good. We will make the change & give it
try for the June Updates after the machines all settle down from the May push.

Thank you both for your reply,
John



"Cecils(MSFT)" wrote:

[Quoted Text]
> Yes, Machines that have already checked into a group, before the switch to
> Server side targeting, will remain in that group when you switch the server.
> If you change the GPO while in Server side targeting will not change on the
> WSUS server.
>
> --
> --
> Cecils [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
>
> "Matthew Wetmore (MSFT)" <mattwe[ at ]online.microsoft.com> wrote in message
> news:OPFcF$OmHHA.4552[ at ]TK2MSFTNGP05.phx.gbl...
> > Having the GPO set while the server is in server side targeting mode is
> > not a problem. The value is ignored.
> >
> > I'm not entirely sure whether computers that have checked in under a group
> > will stay there after the switch to server side. I'll try to ask an
> > appropriate person to find out - though my newsgroup time is sporadic.
> > Another participant may know. I *suspect* the group membership will stick
> > for machines that have already checked in.
> >
> > And yes, new machines checking in will go to Unassigned and can then be
> > moved.
> >
> > --
> > Matthew Wetmore
> > Developer, WSUS (Windows Server Update Services)
> >
> > 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
> >
> > "John" <John[ at ]discussions.microsoft.com> wrote in message
> > news:29DF3208-338C-4FDC-AA7D-3CB940E02C0B[ at ]microsoft.com...
> >> All,
> >>
> >> We have WSUS 2.0. I need to change (at least temporary) from Client-Side
> >> Targeting to Server-Side Targeting. Currently have GPO's in my machine
> >> OU's
> >> pointing to my Computer Groups in WSUS.
> >>
> >> If I change my WSUS Computer Options to "Use the Move computers task in
> >> Windows Server Update Services" for Server-Side Targeting, can I leave my
> >> GPO's alone or will I need to Disable or Not Configure the "Enable
> >> client-side targeting" setting in the GPO's?
> >>
> >> Also, working while with Server-Side Targeting, I assume any new machine
> >> will appear in the Unasigned Computers Group in WSUS regardless of it's
> >> Machine OU as long as the OU has the GPO. Then I'll simply move the
> >> machine
> >> into it's appropriate WSUS Computer Group for manageability. Please
> >> correct
> >> me if I'm wrong.
> >>
> >> Thanks,
> >> John
> >>
> >>
> >
> >
>
>
Re: WSUS 2.0 Client-Side to Server-Side
"Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/21/2007 1:19:39 AM
"Matthew Wetmore (MSFT)" <mattwe[ at ]online.microsoft.com> wrote in message
news:OPFcF$OmHHA.4552[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> Having the GPO set while the server is in server side targeting mode is
> not a problem. The value is ignored.
>
> I'm not entirely sure whether computers that have checked in under a group
> will stay there after the switch to server side.

Actually, the newsgroup participants have some empirical experience from
this scenario in the early days of WSUS 2.0. A regular poster in the
newsgroup intentionally configured client-side GPOs, but left the server set
at server-side targeting to facilitate temporary local assignment of groups
for specific deployment scenarios (e.g. Windows XP Service Pack 2).

Provided that the targeting cookie properly expired, the clients picked up
the server-side assignments in preference to the client-side GPO
assignments. Apparently the WUA (v5.8) reported the client-side assignments
as a "preferred" target group, but not a *required* target group. I do not
know if this is still the behavior of WUA v7.0, however.

--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....



Re: WSUS 2.0 Client-Side to Server-Side
"Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/21/2007 1:21:56 AM
"Cecils(MSFT)" <cecils[ at ]online.microsoft.com> wrote in message
news:u3L8y3ZmHHA.4872[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
> Yes, Machines that have already checked into a group, before the switch to
> Server side targeting, will remain in that group when you switch the
> server.

This was not the observed behavior with WSUS 2.0 (and WUA v5.8) -- (or else
I'm misunderstanding your statement).

> If you change the GPO while in Server side targeting will not change on
> the WSUS server.

Because the server-side assignment takes precendence over a client-side
"preferential" choice.

--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....


Re: WSUS 2.0 Client-Side to Server-Side
John 5/21/2007 1:30:00 AM
Lawrence,

I'll reply to the post after we make the change to let everyone know what
happens. It may be a couple weeks though.

John



"Lawrence Garvin (MVP)" wrote:

[Quoted Text]
> "Matthew Wetmore (MSFT)" <mattwe[ at ]online.microsoft.com> wrote in message
> news:OPFcF$OmHHA.4552[ at ]TK2MSFTNGP05.phx.gbl...
> > Having the GPO set while the server is in server side targeting mode is
> > not a problem. The value is ignored.
> >
> > I'm not entirely sure whether computers that have checked in under a group
> > will stay there after the switch to server side.
>
> Actually, the newsgroup participants have some empirical experience from
> this scenario in the early days of WSUS 2.0. A regular poster in the
> newsgroup intentionally configured client-side GPOs, but left the server set
> at server-side targeting to facilitate temporary local assignment of groups
> for specific deployment scenarios (e.g. Windows XP Service Pack 2).
>
> Provided that the targeting cookie properly expired, the clients picked up
> the server-side assignments in preference to the client-side GPO
> assignments. Apparently the WUA (v5.8) reported the client-side assignments
> as a "preferred" target group, but not a *required* target group. I do not
> know if this is still the behavior of WUA v7.0, however.
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)
> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>
> Everything you need for WSUS is at
> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>
> And, almost everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>
>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen