|
|
Hi,
I've two questions:
Because I store all updates locally on the WSUS 3.0 Server, what happens
when the user starts Windows Update from their workstation. Does it ask the
WSUS Server for what is available or does it go to Microsoft.com? Also, if
it finds an update, where does it get it from? WSUS or Microsoft?
And then the same questions when WSUS is down. Does the user initiated
Windows Update realize WSUS is down and goes to Microsoft.com as an
alternate?
Thanks!
---
Bob
|
|
"Bob" <86c6c2e6-2146512712[ at ]news.postalias> wrote in message
news:%23wiCmwZvHHA.1164[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Because I store all updates locally on the WSUS 3.0 Server, what happens
> when the user starts Windows Update from their workstation. Does it ask
> the WSUS Server for what is available or does it go to Microsoft.com?
> Also, if it finds an update, where does it get it from? WSUS or
> Microsoft?
Running Windows Update from the web interface is totally oblivious to the
presence of a WSUS server, as a default configuration. If Windows
Update/Microsoft Update is accessed via a web interface, the user has full
access to the entire library of updates, and will download all content
directly from microsoft.com.
The WUA will report the installation of the update(s) to the WSUS Server
(via a detection event registering available updates as "Installed"), but
the WSUS Server will not receive any detailed reporting data, such as the
installation date/time.
> And then the same questions when WSUS is down. Does the user initiated
> Windows Update realize WSUS is down and goes to Microsoft.com as an
> alternate?
If the WSUS server is offline, the WUA does not perform any alternative
sourcing of updates. The WUA will record an 0x80072efd error (Cannot
Connect), and reschedule the detection event.
--
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
.....
|
|
Thanks Lawrence,
I'm assuming Windows Update/Microsoft Update (that runs on the client) and
WUA (which I presume also runs on the client), are two different things.
I'm guessing that WUA runs on the client and is maybe part of Automatic
Updates?
If so, I'm inferring from your post that WUA will only interface with one
source and no alternates. Therefore, if WSUS is installed, that is its
source. If not, then Microsoft.com is its source.
It also sounds like Windows Update/Microsoft Update web interface is a beast
all to its own and it only interfaces with Microsoft.com regardless if WSUS
is in place or not.
And lastly, regardless of where the update comes from, WUA knows about it
and will inform WSUS (less the date stamp).
Is that correct?
Bob.
|
|
"Bob" <86c6c2e6-2146512712[ at ]news.postalias> wrote in message
news:eCVoonavHHA.4132[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Thanks Lawrence,
>
> I'm assuming Windows Update/Microsoft Update (that runs on the client) and
> WUA (which I presume also runs on the client), are two different things.
Not quite. The WUA (Windows Update Agent) is the client-side software that
does all of the work. It's actually the thing that talks to Windows
Update/Microsoft Update or the WSUS Server.
> I'm guessing that WUA runs on the client and is maybe part of Automatic
> Updates?
It also provides the services that are Automatic Updates.
> If so, I'm inferring from your post that WUA will only interface with one
> source and no alternates. Therefore, if WSUS is installed, that is its
> source. If not, then Microsoft.com is its source.
Not necessarily. Think of the three products (AU, WU/MU, and WSUS) as of two
different types -- Automatic, or Manual. A system can be configured to use
Automatic Updates, and it can have one of two sources -- Microsoft.Com, or a
local WSUS Server. This is driven by the policy "Specify intranet Microsoft
update service location". If this policy is disabled, the WUA queries via
"Automatic Updates" to microsoft.com for the availability of Critical and
Security Updates *only*. If this policy is enabled, the WUA queries via a
configured WSUS Server for the availability of all types of updates,
including Critical and Security Updates.
In addition, a user sitting at a computer can fire up the browser and use
Windows Update/Microsoft Update. The intelligence is the same software on
the client system -- the Windows Update Agent -- but it's interfacing with
the update catalog in a web-based interactive mode, rather than an automated
fashion (as with AU or WSUS).
> It also sounds like Windows Update/Microsoft Update web interface is a
> beast all to its own and it only interfaces with Microsoft.com regardless
> if WSUS is in place or not.
Actually, all three methods get their data, ultimately, from exactly the
same source, which is the Microsoft Update Catalog (a database of all
updates available via AU, WU/MU, or WSUS).
> And lastly, regardless of where the update comes from, WUA knows about it
> and will inform WSUS (less the date stamp).
If an update is installed to a WSUS-enabled machine, regardless of where/how
the update was installed (including via download from the Microsoft Download
Center, or installation from a TechNet CD/DVD), the WUA will report the
'status' of that update (Installed / Needed) to the WSUS Server.
--
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
.....
|
|
Okay, now I understand it. Thanks Lawrence!
|
|
|