|
|
I am new to WSUS and have a 3.0 SP1 server that, after an automatic update,
is showing machines as still needing updates. A report shows the "Approval"
as "Install" and the "Status" as "Not Installed". This is happening on all
of my test machines. When I go to the Windows Update site it shows that it
needs the same updates.
Any idea as to why the WSUS server is not pushing down those updates? I've
looked at the WindowsUpdate.log file and don't see any messages that indicate
that it checked those updates and does/does not need them.
|
|
"Mark Toby" <MarkToby[ at ]discussions.microsoft.com> wrote in message
news:3DC80364-26FE-4CFD-B1A6-A93789F335BF[ at ]microsoft.com...
[Quoted Text] > I am new to WSUS and have a 3.0 SP1 server that, after an automatic
> update,
> is showing machines as still needing updates. A report shows the
> "Approval"
> as "Install" and the "Status" as "Not Installed". This is happening on
> all
> of my test machines. When I go to the Windows Update site it shows that
> it
> needs the same updates.
>
> Any idea as to why the WSUS server is not pushing down those updates?
[1] The WSUS Server does not push down updates.
[2] The *clients* execute a detection for available updates every 22 hours,
and then download the updates, and then scheduled the update for
installation (by default at 3am the next morning). Thus, theoretically, it
could be up to 22 hours after you approve an update before any given client
system even knows it's available, plus another duration until 3am the next
morning before the update is actually installed and reported as such.
The most likely reason you're seeing what you're reporting is because the
client(s) have not yet detected/downloaded/installed the update.
Might I suggest the WSUS documentation for a good overview of the basics of
how WSUS operates.
> I've looked at the WindowsUpdate.log file and don't see any messages that
> indicate
> that it checked those updates and does/does not need them.
There it is. :-)
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
On Fri, 12 Dec 2008 18:36:41 -0600, "Lawrence Garvin \(MVP\)"
<lawrence[ at ]news.postalias> wrote:
[Quoted Text] >"Mark Toby" <MarkToby[ at ]discussions.microsoft.com> wrote in message
>news:3DC80364-26FE-4CFD-B1A6-A93789F335BF[ at ]microsoft.com...
>> I am new to WSUS and have a 3.0 SP1 server that, after an automatic
>> update,
>> is showing machines as still needing updates. A report shows the
>> "Approval"
>> as "Install" and the "Status" as "Not Installed". This is happening on
>> all
>> of my test machines. When I go to the Windows Update site it shows that
>> it
>> needs the same updates.
>>
>> Any idea as to why the WSUS server is not pushing down those updates?
>
>[1] The WSUS Server does not push down updates.
>
>[2] The *clients* execute a detection for available updates every 22 hours,
>and then download the updates, and then scheduled the update for
>installation (by default at 3am the next morning). Thus, theoretically, it
>could be up to 22 hours after you approve an update before any given client
>system even knows it's available, plus another duration until 3am the next
>morning before the update is actually installed and reported as such.
>
>The most likely reason you're seeing what you're reporting is because the
>client(s) have not yet detected/downloaded/installed the update.
Additionally they could be updates to the updates. e.g. XP SP3 get installed.
After that any updates to SP3 could be detected and queued for installation then
any updates to the updates are detected as needed and queue for installation.
Generally an XP system at say SP2 with no update yet installed. will require
updates to be installed as a prerequisite to installing SP3 which then needs
updates itself and I think there may also be to odd update to the updates. So up
to 3 or 4 round trips.
>
>Might I suggest the WSUS documentation for a good overview of the basics of
>how WSUS operates.
>
>> I've looked at the WindowsUpdate.log file and don't see any messages that
>> indicate
>> that it checked those updates and does/does not need them.
>
>There it is. :-)
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|
|
Ok, so I shouldn't have said that the WSUS server wasn't "pushing" the
update.
What I'm saying is that:
1. I approved all updates 5 days ago.
2. The clients have been looking to the WSUS server for 5 days and have not
pulled those updates.
3. The WSUS server lists the machine as needing the updates.
4. If I go to Windows Update and check for updates, the same updates are
listed.
5. The WindowsUpdate.log file appears to be saying that the PC is up to date.
6. Where is the disconnect? Why does WSUS and Windows Update feel that there
are updates that need to be applied, but Automatic Update does not.
"DaveMills" wrote:
[Quoted Text] > On Fri, 12 Dec 2008 18:36:41 -0600, "Lawrence Garvin \(MVP\)"
> <lawrence[ at ]news.postalias> wrote:
>
> >"Mark Toby" <MarkToby[ at ]discussions.microsoft.com> wrote in message
> >news:3DC80364-26FE-4CFD-B1A6-A93789F335BF[ at ]microsoft.com...
> >> I am new to WSUS and have a 3.0 SP1 server that, after an automatic
> >> update,
> >> is showing machines as still needing updates. A report shows the
> >> "Approval"
> >> as "Install" and the "Status" as "Not Installed". This is happening on
> >> all
> >> of my test machines. When I go to the Windows Update site it shows that
> >> it
> >> needs the same updates.
> >>
> >> Any idea as to why the WSUS server is not pushing down those updates?
> >
> >[1] The WSUS Server does not push down updates.
> >
> >[2] The *clients* execute a detection for available updates every 22 hours,
> >and then download the updates, and then scheduled the update for
> >installation (by default at 3am the next morning). Thus, theoretically, it
> >could be up to 22 hours after you approve an update before any given client
> >system even knows it's available, plus another duration until 3am the next
> >morning before the update is actually installed and reported as such.
> >
> >The most likely reason you're seeing what you're reporting is because the
> >client(s) have not yet detected/downloaded/installed the update.
> Additionally they could be updates to the updates. e.g. XP SP3 get installed.
> After that any updates to SP3 could be detected and queued for installation then
> any updates to the updates are detected as needed and queue for installation.
>
> Generally an XP system at say SP2 with no update yet installed. will require
> updates to be installed as a prerequisite to installing SP3 which then needs
> updates itself and I think there may also be to odd update to the updates. So up
> to 3 or 4 round trips.
> >
> >Might I suggest the WSUS documentation for a good overview of the basics of
> >how WSUS operates.
> >
> >> I've looked at the WindowsUpdate.log file and don't see any messages that
> >> indicate
> >> that it checked those updates and does/does not need them.
> >
> >There it is. :-)
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that don't.
>
|
|
On Fri, 12 Dec 2008 21:28:01 -0800, Mark Toby <Mark
Toby[ at ]discussions.microsoft.com> wrote:
[Quoted Text] >Ok, so I shouldn't have said that the WSUS server wasn't "pushing" the
>update.
>
>What I'm saying is that:
>
>1. I approved all updates 5 days ago.
>2. The clients have been looking to the WSUS server for 5 days and have not
>pulled those updates.
Check to see if the updates have been downloaded to the WSUS server.
When an update is listed as needed the next step is it has to be approved for
install then WSUS downloads the content. Only after the content is downloaded to
the server can the client begin its download. Until then the client detects the
update as needed but not available to download.
>3. The WSUS server lists the machine as needing the updates.
>4. If I go to Windows Update and check for updates, the same updates are
>listed.
>5. The WindowsUpdate.log file appears to be saying that the PC is up to date.
>6. Where is the disconnect? Why does WSUS and Windows Update feel that there
>are updates that need to be applied, but Automatic Update does not.
>
>
>"DaveMills" wrote:
>
>> On Fri, 12 Dec 2008 18:36:41 -0600, "Lawrence Garvin \(MVP\)"
>> <lawrence[ at ]news.postalias> wrote:
>>
>> >"Mark Toby" <MarkToby[ at ]discussions.microsoft.com> wrote in message
>> >news:3DC80364-26FE-4CFD-B1A6-A93789F335BF[ at ]microsoft.com...
>> >> I am new to WSUS and have a 3.0 SP1 server that, after an automatic
>> >> update,
>> >> is showing machines as still needing updates. A report shows the
>> >> "Approval"
>> >> as "Install" and the "Status" as "Not Installed". This is happening on
>> >> all
>> >> of my test machines. When I go to the Windows Update site it shows that
>> >> it
>> >> needs the same updates.
>> >>
>> >> Any idea as to why the WSUS server is not pushing down those updates?
>> >
>> >[1] The WSUS Server does not push down updates.
>> >
>> >[2] The *clients* execute a detection for available updates every 22 hours,
>> >and then download the updates, and then scheduled the update for
>> >installation (by default at 3am the next morning). Thus, theoretically, it
>> >could be up to 22 hours after you approve an update before any given client
>> >system even knows it's available, plus another duration until 3am the next
>> >morning before the update is actually installed and reported as such.
>> >
>> >The most likely reason you're seeing what you're reporting is because the
>> >client(s) have not yet detected/downloaded/installed the update.
>> Additionally they could be updates to the updates. e.g. XP SP3 get installed.
>> After that any updates to SP3 could be detected and queued for installation then
>> any updates to the updates are detected as needed and queue for installation.
>>
>> Generally an XP system at say SP2 with no update yet installed. will require
>> updates to be installed as a prerequisite to installing SP3 which then needs
>> updates itself and I think there may also be to odd update to the updates. So up
>> to 3 or 4 round trips.
>> >
>> >Might I suggest the WSUS documentation for a good overview of the basics of
>> >how WSUS operates.
>> >
>> >> I've looked at the WindowsUpdate.log file and don't see any messages that
>> >> indicate
>> >> that it checked those updates and does/does not need them.
>> >
>> >There it is. :-)
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that don't.
>>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|
|
It looks like you have hit on the issue.
But I don't see why they haven't downloaded yet. I've selected "Store update
files locally on this server". I don't have any of the subordinate boxes
checked under that radio button. I have reduced the number of languages
selected, but English is one that is selected. The upstream sync runs every 6
hours and is set to sync with Microsoft. It looks like it has been running
successfully. I don't see any errors in the event viewer.
It looks like most of this weeks updates have not downloaded, but there are
several older (Nov 23 and earlier) that have not downloaded also.
Any other areas I could check?
"DaveMills" wrote:
[Quoted Text] > On Fri, 12 Dec 2008 21:28:01 -0800, Mark Toby <Mark
> Toby[ at ]discussions.microsoft.com> wrote:
>
> >Ok, so I shouldn't have said that the WSUS server wasn't "pushing" the
> >update.
> >
> >What I'm saying is that:
> >
> >1. I approved all updates 5 days ago.
> >2. The clients have been looking to the WSUS server for 5 days and have not
> >pulled those updates.
> Check to see if the updates have been downloaded to the WSUS server.
> When an update is listed as needed the next step is it has to be approved for
> install then WSUS downloads the content. Only after the content is downloaded to
> the server can the client begin its download. Until then the client detects the
> update as needed but not available to download.
>
> >3. The WSUS server lists the machine as needing the updates.
> >4. If I go to Windows Update and check for updates, the same updates are
> >listed.
> >5. The WindowsUpdate.log file appears to be saying that the PC is up to date.
> >6. Where is the disconnect? Why does WSUS and Windows Update feel that there
> >are updates that need to be applied, but Automatic Update does not.
> >
> >
> >"DaveMills" wrote:
> >
> >> On Fri, 12 Dec 2008 18:36:41 -0600, "Lawrence Garvin \(MVP\)"
> >> <lawrence[ at ]news.postalias> wrote:
> >>
> >> >"Mark Toby" <MarkToby[ at ]discussions.microsoft.com> wrote in message
> >> >news:3DC80364-26FE-4CFD-B1A6-A93789F335BF[ at ]microsoft.com...
> >> >> I am new to WSUS and have a 3.0 SP1 server that, after an automatic
> >> >> update,
> >> >> is showing machines as still needing updates. A report shows the
> >> >> "Approval"
> >> >> as "Install" and the "Status" as "Not Installed". This is happening on
> >> >> all
> >> >> of my test machines. When I go to the Windows Update site it shows that
> >> >> it
> >> >> needs the same updates.
> >> >>
> >> >> Any idea as to why the WSUS server is not pushing down those updates?
> >> >
> >> >[1] The WSUS Server does not push down updates.
> >> >
> >> >[2] The *clients* execute a detection for available updates every 22 hours,
> >> >and then download the updates, and then scheduled the update for
> >> >installation (by default at 3am the next morning). Thus, theoretically, it
> >> >could be up to 22 hours after you approve an update before any given client
> >> >system even knows it's available, plus another duration until 3am the next
> >> >morning before the update is actually installed and reported as such.
> >> >
> >> >The most likely reason you're seeing what you're reporting is because the
> >> >client(s) have not yet detected/downloaded/installed the update.
> >> Additionally they could be updates to the updates. e.g. XP SP3 get installed.
> >> After that any updates to SP3 could be detected and queued for installation then
> >> any updates to the updates are detected as needed and queue for installation.
> >>
> >> Generally an XP system at say SP2 with no update yet installed. will require
> >> updates to be installed as a prerequisite to installing SP3 which then needs
> >> updates itself and I think there may also be to odd update to the updates. So up
> >> to 3 or 4 round trips.
> >> >
> >> >Might I suggest the WSUS documentation for a good overview of the basics of
> >> >how WSUS operates.
> >> >
> >> >> I've looked at the WindowsUpdate.log file and don't see any messages that
> >> >> indicate
> >> >> that it checked those updates and does/does not need them.
> >> >
> >> >There it is. :-)
> >> --
> >> Dave Mills
> >> There are 10 types of people, those that understand binary and those that don't.
> >>
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that don't.
>
|
|
On Sat, 13 Dec 2008 09:07:01 -0800, Mark Toby
<MarkToby[ at ]discussions.microsoft.com> wrote:
[Quoted Text] >It looks like you have hit on the issue.
>
>But I don't see why they haven't downloaded yet. I've selected "Store update
>files locally on this server". I don't have any of the subordinate boxes
>checked under that radio button. I have reduced the number of languages
>selected, but English is one that is selected. The upstream sync runs every 6
>hours and is set to sync with Microsoft. It looks like it has been running
>successfully. I don't see any errors in the event viewer.
>
>It looks like most of this weeks updates have not downloaded, but there are
>several older (Nov 23 and earlier) that have not downloaded also.
>
>Any other areas I could check?
Try this for a start
http://blogs.technet.com/sus/archive/2008/07/09/troubleshooting-wsus-downloads.aspx
There are various file types that need to download, sometime exe file sometime
other type. Look for firewall issues which may be blocking certain file types.
Sonicwall is a known cause of issues so if you are using that firewall search
for WSUS and Sonicwall and you will get loads of relevant info.
>
>"DaveMills" wrote:
>
>> On Fri, 12 Dec 2008 21:28:01 -0800, Mark Toby <Mark
>> Toby[ at ]discussions.microsoft.com> wrote:
>>
>> >Ok, so I shouldn't have said that the WSUS server wasn't "pushing" the
>> >update.
>> >
>> >What I'm saying is that:
>> >
>> >1. I approved all updates 5 days ago.
>> >2. The clients have been looking to the WSUS server for 5 days and have not
>> >pulled those updates.
>> Check to see if the updates have been downloaded to the WSUS server.
>> When an update is listed as needed the next step is it has to be approved for
>> install then WSUS downloads the content. Only after the content is downloaded to
>> the server can the client begin its download. Until then the client detects the
>> update as needed but not available to download.
>>
>> >3. The WSUS server lists the machine as needing the updates.
>> >4. If I go to Windows Update and check for updates, the same updates are
>> >listed.
>> >5. The WindowsUpdate.log file appears to be saying that the PC is up to date.
>> >6. Where is the disconnect? Why does WSUS and Windows Update feel that there
>> >are updates that need to be applied, but Automatic Update does not.
>> >
>> >
>> >"DaveMills" wrote:
>> >
>> >> On Fri, 12 Dec 2008 18:36:41 -0600, "Lawrence Garvin \(MVP\)"
>> >> <lawrence[ at ]news.postalias> wrote:
>> >>
>> >> >"Mark Toby" <MarkToby[ at ]discussions.microsoft.com> wrote in message
>> >> >news:3DC80364-26FE-4CFD-B1A6-A93789F335BF[ at ]microsoft.com...
>> >> >> I am new to WSUS and have a 3.0 SP1 server that, after an automatic
>> >> >> update,
>> >> >> is showing machines as still needing updates. A report shows the
>> >> >> "Approval"
>> >> >> as "Install" and the "Status" as "Not Installed". This is happening on
>> >> >> all
>> >> >> of my test machines. When I go to the Windows Update site it shows that
>> >> >> it
>> >> >> needs the same updates.
>> >> >>
>> >> >> Any idea as to why the WSUS server is not pushing down those updates?
>> >> >
>> >> >[1] The WSUS Server does not push down updates.
>> >> >
>> >> >[2] The *clients* execute a detection for available updates every 22 hours,
>> >> >and then download the updates, and then scheduled the update for
>> >> >installation (by default at 3am the next morning). Thus, theoretically, it
>> >> >could be up to 22 hours after you approve an update before any given client
>> >> >system even knows it's available, plus another duration until 3am the next
>> >> >morning before the update is actually installed and reported as such.
>> >> >
>> >> >The most likely reason you're seeing what you're reporting is because the
>> >> >client(s) have not yet detected/downloaded/installed the update.
>> >> Additionally they could be updates to the updates. e.g. XP SP3 get installed.
>> >> After that any updates to SP3 could be detected and queued for installation then
>> >> any updates to the updates are detected as needed and queue for installation.
>> >>
>> >> Generally an XP system at say SP2 with no update yet installed. will require
>> >> updates to be installed as a prerequisite to installing SP3 which then needs
>> >> updates itself and I think there may also be to odd update to the updates. So up
>> >> to 3 or 4 round trips.
>> >> >
>> >> >Might I suggest the WSUS documentation for a good overview of the basics of
>> >> >how WSUS operates.
>> >> >
>> >> >> I've looked at the WindowsUpdate.log file and don't see any messages that
>> >> >> indicate
>> >> >> that it checked those updates and does/does not need them.
>> >> >
>> >> >There it is. :-)
>> >> --
>> >> Dave Mills
>> >> There are 10 types of people, those that understand binary and those that don't.
>> >>
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that don't.
>>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|
|
|