|
|
Hello:
I have a question/problem and hope that somebody will help me.
I built WSUS 3.0. I understand how I can manage group; remotely update my
clients and etc. However, I’d like to let my clients to do Windows Updates
on their own and at the same time I’d like to reduce bandwidth. So, I’d like
to build the system that will redirect my clients, when they click icon
Windows Update, to WSUS (where all updates are stored) instead of
http://windowsupdate.microsoft.com and have possibility to choose/install
updates.
So, my questions are as follows:
Is it possible to redirect clients to WSUS and let them choose/install
updates when they click Windows Update? If “YESâ€, then how can I do it? If
“NOâ€, then is there other way to do it?
Thank you very much in advanced.
|
|
There is no equivalent Windows Update/Microsoft Update website included in
WSUS.
At the closest, you could make them administrators in WSUS, and thus able to
administer their own machines - but they'd also be able to control
installations for other's machines.
ISA servers allow you to cache files requested by the client, which would
somewhat lessen your traffic to outside servers. Unfortunately, that won't
include all updates as many end up as range requests instead of full files.
--
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
"oleg" <oleg[ at ]discussions.microsoft.com> wrote in message
news:576C678E-493D-4269-BEA7-01B6F3330E32[ at ]microsoft.com...
[Quoted Text] > Hello: > > I have a question/problem and hope that somebody will help me. > > I built WSUS 3.0. I understand how I can manage group; remotely update my > clients and etc. However, I'd like to let my clients to do Windows > Updates > on their own and at the same time I'd like to reduce bandwidth. So, I'd > like > to build the system that will redirect my clients, when they click icon > Windows Update, to WSUS (where all updates are stored) instead of > http://windowsupdate.microsoft.com and have possibility to choose/install > updates. > > So, my questions are as follows: > > Is it possible to redirect clients to WSUS and let them choose/install > updates when they click Windows Update? If "YES", then how can I do it? > If > "NO", then is there other way to do it? > > Thank you very much in advanced. > >
|
|
Not possible. WSUS doesn't have any interface that resembles WU/MU to send
clients to.
Kurt [MSFT]
"oleg" wrote:
[Quoted Text] > Hello: > > I have a question/problem and hope that somebody will help me. > > I built WSUS 3.0. I understand how I can manage group; remotely update my > clients and etc. However, I’d like to let my clients to do Windows Updates > on their own and at the same time I’d like to reduce bandwidth. So, I’d like > to build the system that will redirect my clients, when they click icon > Windows Update, to WSUS (where all updates are stored) instead of > http://windowsupdate.microsoft.com and have possibility to choose/install > updates. > > So, my questions are as follows: > > Is it possible to redirect clients to WSUS and let them choose/install > updates when they click Windows Update? If “YESâ€, then how can I do it? If > “NOâ€, then is there other way to do it? > > Thank you very much in advanced. > > |
|
Thank you very much for your help and explanation.
Do you by any chance know if Microsoft is working on something like simular,
that will be available soon or not at all?
Again, thank you very much for your help.
Best regards,
oleg
"Matthew Wetmore (MSFT)" wrote:
[Quoted Text] > There is no equivalent Windows Update/Microsoft Update website included in > WSUS. > At the closest, you could make them administrators in WSUS, and thus able to > administer their own machines - but they'd also be able to control > installations for other's machines. > > ISA servers allow you to cache files requested by the client, which would > somewhat lessen your traffic to outside servers. Unfortunately, that won't > include all updates as many end up as range requests instead of full files. > > > -- > 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> > "oleg" <oleg[ at ]discussions.microsoft.com> wrote in message > news:576C678E-493D-4269-BEA7-01B6F3330E32[ at ]microsoft.com... > > Hello: > > > > I have a question/problem and hope that somebody will help me. > > > > I built WSUS 3.0. I understand how I can manage group; remotely update my > > clients and etc. However, I'd like to let my clients to do Windows > > Updates > > on their own and at the same time I'd like to reduce bandwidth. So, I'd > > like > > to build the system that will redirect my clients, when they click icon > > Windows Update, to WSUS (where all updates are stored) instead of > > http://windowsupdate.microsoft.com and have possibility to choose/install > > updates. > > > > So, my questions are as follows: > > > > Is it possible to redirect clients to WSUS and let them choose/install > > updates when they click Windows Update? If "YES", then how can I do it? > > If > > "NO", then is there other way to do it? > > > > Thank you very much in advanced. > > > > > > > |
|
Hi Oleg,
That really defeats the purpose of WSUS, though - which is central
management and off-loading the update responsibility from the users.
I believe you could however, via GP, configure the workstations to 'download
and notify', or perhaps even just 'notify', when updates are available at
the WSUS server. (you'd still need to ensure applicable updates are approved
in WSUS).
Users would be responsible to complet the installations themselves, at
whatever time suits them. But that's the behaviour most want to avoid ;-).
--
Les Connor [SBS MVP]
"oleg" <oleg[ at ]discussions.microsoft.com> wrote in message
news:576C678E-493D-4269-BEA7-01B6F3330E32[ at ]microsoft.com...
[Quoted Text] > Hello: > > I have a question/problem and hope that somebody will help me. > > I built WSUS 3.0. I understand how I can manage group; remotely update my > clients and etc. However, I’d like to let my clients to do Windows > Updates > on their own and at the same time I’d like to reduce bandwidth. So, I’d > like > to build the system that will redirect my clients, when they click icon > Windows Update, to WSUS (where all updates are stored) instead of > http://windowsupdate.microsoft.com and have possibility to choose/install > updates. > > So, my questions are as follows: > > Is it possible to redirect clients to WSUS and let them choose/install > updates when they click Windows Update? If “YESâ€, then how can I do it? > If > “NOâ€, then is there other way to do it? > > Thank you very much in advanced. > >
|
|
On Thu, 17 May 2007 16:12:15 -0500, "Les Connor [SBS MVP]"
<les.connor[ at ]DEL.cfive.ca> wrote:
[Quoted Text] >Hi Oleg,
>
>That really defeats the purpose of WSUS, though - which is central
>management and off-loading the update responsibility from the users.
>
>I believe you could however, via GP, configure the workstations to 'download
>and notify', or perhaps even just 'notify', when updates are available at
>the WSUS server. (you'd still need to ensure applicable updates are approved
>in WSUS).
>
>Users would be responsible to complet the installations themselves, at
>whatever time suits them. But that's the behaviour most want to avoid ;-).
And they would need local admin rights. Even more to be avoided.
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
|
|
On Thu, 17 May 2007 11:20:01 -0700, oleg <oleg[ at ]discussions.microsoft.com> wrote:
[Quoted Text] >Thank you very much for your help and explanation.
>
>Do you by any chance know if Microsoft is working on something like simular,
>that will be available soon or not at all?
Not in the near future and possibly never. It is hard to see why you would want
it. Either the client choose their update from WU/MU or you decide as an admin,
in which case the don't need a choice.
>Again, thank you very much for your help.
>
>
>Best regards,
>oleg
>
>
>"Matthew Wetmore (MSFT)" wrote:
>
>> There is no equivalent Windows Update/Microsoft Update website included in
>> WSUS.
>> At the closest, you could make them administrators in WSUS, and thus able to
>> administer their own machines - but they'd also be able to control
>> installations for other's machines.
>>
>> ISA servers allow you to cache files requested by the client, which would
>> somewhat lessen your traffic to outside servers. Unfortunately, that won't
>> include all updates as many end up as range requests instead of full files.
>>
>>
>> --
>> 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
>>
>> "oleg" <oleg[ at ]discussions.microsoft.com> wrote in message
>> news:576C678E-493D-4269-BEA7-01B6F3330E32[ at ]microsoft.com...
>> > Hello:
>> >
>> > I have a question/problem and hope that somebody will help me.
>> >
>> > I built WSUS 3.0. I understand how I can manage group; remotely update my
>> > clients and etc. However, I'd like to let my clients to do Windows
>> > Updates
>> > on their own and at the same time I'd like to reduce bandwidth. So, I'd
>> > like
>> > to build the system that will redirect my clients, when they click icon
>> > Windows Update, to WSUS (where all updates are stored) instead of
>> > http://windowsupdate.microsoft.com and have possibility to choose/install
>> > updates.
>> >
>> > So, my questions are as follows:
>> >
>> > Is it possible to redirect clients to WSUS and let them choose/install
>> > updates when they click Windows Update? If "YES", then how can I do it?
>> > If
>> > "NO", then is there other way to do it?
>> >
>> > Thank you very much in advanced.
>> >
>> >
>>
>>
>>
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
|
|
So far, that's still largely a dream ;-). (in the SB world, at least).
hehe.
--
Les Connor [SBS MVP]
"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
news:n7lp435tfro9ffgkvo9rocs6e1iq1ftbj6[ at ]4ax.com...
[Quoted Text] > On Thu, 17 May 2007 16:12:15 -0500, "Les Connor [SBS MVP]"
> <les.connor[ at ]DEL.cfive.ca> wrote:
>
>>Hi Oleg,
>>
>>That really defeats the purpose of WSUS, though - which is central
>>management and off-loading the update responsibility from the users.
>>
>>I believe you could however, via GP, configure the workstations to
>>'download
>>and notify', or perhaps even just 'notify', when updates are available at
>>the WSUS server. (you'd still need to ensure applicable updates are
>>approved
>>in WSUS).
>>
>>Users would be responsible to complet the installations themselves, at
>>whatever time suits them. But that's the behaviour most want to avoid ;-).
>
> And they would need local admin rights. Even more to be avoided.
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that
> don't.
|
|
Two additional points here:
1) You can deploy most of the regularly needed updates via WSUS, and not
configure the clients to restrict access to WU. If there's something else
they need, or want updates you may not have otherwise approved in WSUS -
they can still go the site. That will reduce the bandwidth by the updates
that you cause installation via WSUS. For instance, that might reduce you
usage if you deploy critical/security updates that every client *must* have,
and then let them get everything else from the update site.
2) We've had related customer feedback around this issue, so it's not a new
thing. WSUS 3 was largely based on customer feedback, so having validation
of customer need is a good thing in future planning. Thanks for that.
--
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
"Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message
news:9E3A27FE-2FA1-4CEC-819D-78D9A944C761[ at ]microsoft.com...
[Quoted Text] > So far, that's still largely a dream ;-). (in the SB world, at least).
>
> hehe.
>
> --
> Les Connor [SBS MVP]
>
>
> "DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
> news:n7lp435tfro9ffgkvo9rocs6e1iq1ftbj6[ at ]4ax.com...
>> On Thu, 17 May 2007 16:12:15 -0500, "Les Connor [SBS MVP]"
>> <les.connor[ at ]DEL.cfive.ca> wrote:
>>
>>>Hi Oleg,
>>>
>>>That really defeats the purpose of WSUS, though - which is central
>>>management and off-loading the update responsibility from the users.
>>>
>>>I believe you could however, via GP, configure the workstations to
>>>'download
>>>and notify', or perhaps even just 'notify', when updates are available at
>>>the WSUS server. (you'd still need to ensure applicable updates are
>>>approved
>>>in WSUS).
>>>
>>>Users would be responsible to complet the installations themselves, at
>>>whatever time suits them. But that's the behaviour most want to avoid
>>>;-).
>>
>> And they would need local admin rights. Even more to be avoided.
>> --
>> Dave Mills
>> There are 10 type of people, those that understand binary and those that
>> don't.
>
|
|
"Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message
news:A8002714-E1EB-401B-B7DD-48CB66A3423D[ at ]microsoft.com...
[Quoted Text] > That really defeats the purpose of WSUS, though - which is central
> management and off-loading the update responsibility from the users.
>
> I believe you could however, via GP, configure the workstations to
> 'download and notify', or perhaps even just 'notify', when updates are
> available at the WSUS server. (you'd still need to ensure applicable
> updates are approved in WSUS).
>
> Users would be responsible to complet the installations themselves, at
> whatever time suits them. But that's the behaviour most want to avoid ;-).
Ya know.. Les.... I *can* see where a very small organization with limited
internet bandwidth might want to use WSUS as nothing more than "proxy"
server for Microsoft Update. Set everything to auto-approve for install and
configure all clients with AU Option #2 (or AU Option #5).
Although another scenario that might be even more appropriate is in an
Executive Suite where a service of the E.S. is providing network management
and common internet access bandwidth for individually operated "offices" (or
individual professionals); or in a technology consulting department, where
all users are IT Pros managing their own desktop/notebook systems and you
want to ensure the earliest possible deployment of content to the desktop
filesystem.
(Ain't it interesting how creative I can get when I've had a couple of good
shots of Canadian Whiskey?)
--
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
.....
|
|
|
[Quoted Text] > (Ain't it interesting how creative I can get when I've had a couple of
> good shots of Canadian Whiskey?)
Have fun, but do be careful, Lawrence - somewhere after creativity, there is
manufacturing <a hangover>, and it's never obvious to me when I cross over
;-).
Tomorrow Canadians celebrate the Queen of England's birthday, so even though
we cross that line today we'll be OK by Tuesday when we have to report for
work.
--
Les Connor [SBS MVP]
"Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message
news:%23rl%23gV0mHHA.668[ at ]TK2MSFTNGP05.phx.gbl...
> "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message
|
|
On May 17, 6:12 pm, oleg <o...[ at ]discussions.microsoft.com> wrote:
[Quoted Text] > Hello: > > I have a question/problem and hope that somebody will help me. > > I built WSUS 3.0. I understand how I can manage group; remotely update my > clients and etc. However, I'd like to let my clients to do Windows Updates > on their own and at the same time I'd like to reduce bandwidth. So, I'd like > to build the system that will redirect my clients, when they click icon > Windows Update, to WSUS (where all updates are stored) instead of http://windowsupdate.microsoft.comand have possibility to choose/install > updates. > > So, my questions are as follows: > > Is it possible to redirect clients to WSUS and let them choose/install > updates when they click Windows Update? If "YES", then how can I do it? If > "NO", then is there other way to do it? > > Thank you very much in advanced.
For what it's worth - and if I read you right - in Vista, doing a
Windows Update actually starts the standalone Windows Update program;
the process doesn't happen in IE any more.
And if you are configured to use WSUS in Vista, then all your Windows
Updates, whether scanned for manually or not, will go to WSUS and not
to MS.
Just a thought..
|
|
|