Wanted - Easy update of 10 PC's with one download set

I haven't exhaustively researched all options that Microsoft currently
provide, but it seems there isn't a nice simple way of keeping a group of
PC's updated from a single download session of all current updates.

This is how I think a nice system could work:

1. Say you have 5 to 10 PC's. Every so often you might do a clean
re-install of Windows XP SP3 on some, others may have various stages of
post-SP3 updates installed. You can't afford the cost of repeated downloads
of all updates re-occurring many times – Automatic Updates works, but it’s
too costly.

2. Microsoft should have available something like Microsoft Catalogue, but
allow the simply one-click selection of all current, for example, XP 32bit
post-SP3 updates for download to a single local master update folder – call
it a local catalogue.

3. On one master PC, you download all current updates from Microsoft. The
best would be to have something like SyncToy to keep the local copy in sync
with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
removing replaced updates, and adding new ones. When the Sync process is
run, it quickly deletes old local copies and downloads any/all new updates
since the last Sync. Download costs are minimised by only adding updates not
already present in the local catalogue (master folder), and there is only one
download needed for the updates for as many PC’s as required.

4. On each local PC, you run a process similar to Automatic Updates. This
AutoUpdater process is a little different though – it only checks with the
local master to see what updates are needed, and instead up downloading each
update from Microsoft, it copies and/or simply runs the updates from the
local master folder. Perhaps the local AutoUpdater process could include an
online check to Microsoft to see if the local master catalogue has all
current updates present and let the operator know.

What do you think? Ideas for a better system are encouraged! And how can
we encourage Microsoft to set this up? – (if they haven’t already done it and
I haven’t found it!!!)

 

Doesn't WSUS suit that purpose?

"Peter Tanner" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I haven't exhaustively researched all options that Microsoft currently
> provide, but it seems there isn't a nice simple way of keeping a group of
> PC's updated from a single download session of all current updates.
>
> This is how I think a nice system could work:
>
> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> re-install of Windows XP SP3 on some, others may have various stages of
> post-SP3 updates installed. You can't afford the cost of repeated downloads
> of all updates re-occurring many times – Automatic Updates works, but it’s
> too costly.
>
> 2. Microsoft should have available something like Microsoft Catalogue, but
> allow the simply one-click selection of all current, for example, XP 32bit
> post-SP3 updates for download to a single local master update folder – call
> it a local catalogue.
>
> 3. On one master PC, you download all current updates from Microsoft. The
> best would be to have something like SyncToy to keep the local copy in sync
> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
> removing replaced updates, and adding new ones. When the Sync process is
> run, it quickly deletes old local copies and downloads any/all new updates
> since the last Sync. Download costs are minimised by only adding updates not
> already present in the local catalogue (master folder), and there is only one
> download needed for the updates for as many PC’s as required.
>
> 4. On each local PC, you run a process similar to Automatic Updates. This
> AutoUpdater process is a little different though – it only checks with the
> local master to see what updates are needed, and instead up downloading each
> update from Microsoft, it copies and/or simply runs the updates from the
> local master folder. Perhaps the local AutoUpdater process could include an
> online check to Microsoft to see if the local master catalogue has all
> current updates present and let the operator know.
>
> What do you think? Ideas for a better system are encouraged! And how can
> we encourage Microsoft to set this up? – (if they haven’t already done it and
> I haven’t found it!!!)<!--colorc--><!--/colorc-->

 

Peter Tanner wrote:
:: I haven't exhaustively researched all options that Microsoft
:: currently provide, but it seems there isn't a nice simple way of
:: keeping a group of PC's updated from a single download session of
:: all current updates.
::
:: This is how I think a nice system could work:
::
:: 1. Say you have 5 to 10 PC's. Every so often you might do a clean
:: re-install of Windows XP SP3 on some, others may have various stages
:: of post-SP3 updates installed. You can't afford the cost of
:: repeated downloads of all updates re-occurring many times -
:: Automatic Updates works, but it's too costly.
::
:: 2. Microsoft should have available something like Microsoft
:: Catalogue, but allow the simply one-click selection of all current,
:: for example, XP 32bit post-SP3 updates for download to a single
:: local master update folder - call it a local catalogue.
::
:: 3. On one master PC, you download all current updates from
:: Microsoft. The best would be to have something like SyncToy to keep
:: the local copy in sync with the "Microsoft Catalogue" - Microsoft
:: keep their "catalogue" current by removing replaced updates, and
:: adding new ones. When the Sync process is run, it quickly deletes
:: old local copies and downloads any/all new updates since the last
:: Sync. Download costs are minimised by only adding updates not
:: already present in the local catalogue (master folder), and there is
:: only one download needed for the updates for as many PC's as
:: required.
::
:: 4. On each local PC, you run a process similar to Automatic
:: Updates. This AutoUpdater process is a little different though - it
:: only checks with the local master to see what updates are needed,
:: and instead up downloading each update from Microsoft, it copies
:: and/or simply runs the updates from the local master folder.
:: Perhaps the local AutoUpdater process could include an online check
:: to Microsoft to see if the local master catalogue has all current
:: updates present and let the operator know.
::
:: What do you think? Ideas for a better system are encouraged! And
:: how can we encourage Microsoft to set this up? - (if they haven't
:: already done it and I haven't found it!!!)


Security updates are available on ISO-9660 CD image files from the Microsoft
Download Center

--

TaurArian [MVP] 2005-2010 - Update Services

======================================
Disclaimer: The information has been posted "as is" with no warranties
or guarantees and doesn't give any rights.

 

Peter Tanner wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I haven't exhaustively researched all options that Microsoft currently
> provide, but it seems there isn't a nice simple way of keeping a group of
> PC's updated from a single download session of all current updates.
>
> This is how I think a nice system could work:
>
> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> re-install of Windows XP SP3 on some, others may have various stages of
> post-SP3 updates installed. You can't afford the cost of repeated downloads
> of all updates re-occurring many times – Automatic Updates works, but it’s
> too costly.
>
> 2. Microsoft should have available something like Microsoft Catalogue, but
> allow the simply one-click selection of all current, for example, XP 32bit
> post-SP3 updates for download to a single local master update folder – call
> it a local catalogue.
>
> 3. On one master PC, you download all current updates from Microsoft. The
> best would be to have something like SyncToy to keep the local copy in sync
> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
> removing replaced updates, and adding new ones. When the Sync process is
> run, it quickly deletes old local copies and downloads any/all new updates
> since the last Sync. Download costs are minimised by only adding updates not
> already present in the local catalogue (master folder), and there is only one
> download needed for the updates for as many PC’s as required.
>
> 4. On each local PC, you run a process similar to Automatic Updates. This
> AutoUpdater process is a little different though – it only checks with the
> local master to see what updates are needed, and instead up downloading each
> update from Microsoft, it copies and/or simply runs the updates from the
> local master folder. Perhaps the local AutoUpdater process could include an
> online check to Microsoft to see if the local master catalogue has all
> current updates present and let the operator know.
>
> What do you think? Ideas for a better system are encouraged! And how can
> we encourage Microsoft to set this up? – (if they haven’t already done it and
> I haven’t found it!!!)<!--colorc--><!--/colorc-->
See


Jim

 

Peter Tanner wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I haven't exhaustively researched all options that Microsoft
> currently provide, but it seems there isn't a nice simple way of
> keeping a group of PC's updated from a single download session of
> all current updates.
>
> This is how I think a nice system could work:
>
> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> re-install of Windows XP SP3 on some, others may have various
> stages of post-SP3 updates installed. You can't afford the cost of
> repeated downloads of all updates re-occurring many times -
> Automatic Updates works, but it's too costly.
>
> 2. Microsoft should have available something like Microsoft
> Catalogue, but allow the simply one-click selection of all current,
> for example, XP 32bit post-SP3 updates for download to a single
> local master update folder - call it a local catalogue.
>
> 3. On one master PC, you download all current updates from
> Microsoft. The best would be to have something like SyncToy to
> keep the local copy in sync with the "Microsoft Catalogue" -
> Microsoft keep their "catalogue" current by removing replaced
> updates, and adding new ones. When the Sync process is run, it
> quickly deletes old local copies and downloads any/all new updates
> since the last Sync. Download costs are minimised by only adding
> updates not already present in the local catalogue (master folder),
> and there is only one download needed for the updates for as many
> PC's as required.
>
> 4. On each local PC, you run a process similar to Automatic
> Updates. This AutoUpdater process is a little different though -
> it only checks with the local master to see what updates are
> needed, and instead up downloading each update from Microsoft, it
> copies and/or simply runs the updates from the local master folder.
> Perhaps the local AutoUpdater process could include an online check
> to Microsoft to see if the local master catalogue has all current
> updates present and let the operator know.
>
> What do you think? Ideas for a better system are encouraged! And
> how can we encourage Microsoft to set this up? - (if they haven't
> already done it and I haven't found it!!!)<!--colorc--><!--/colorc-->

WSUS

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way

 

Egaskrad wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Doesn't WSUS suit that purpose?<!--colorc--><!--/colorc-->

Not really - most folks with 5 to 10 PC's probably don't want to shell out for
an expensive Windows server license.

Harry.
<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> "Peter Tanner" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>> I haven't exhaustively researched all options that Microsoft currently
>> provide, but it seems there isn't a nice simple way of keeping a group of
>> PC's updated from a single download session of all current updates.
>>
>> This is how I think a nice system could work:
>>
>> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
>> re-install of Windows XP SP3 on some, others may have various stages of
>> post-SP3 updates installed. You can't afford the cost of repeated downloads
>> of all updates re-occurring many times – Automatic Updates works, but it’s
>> too costly.
>>
>> 2. Microsoft should have available something like Microsoft Catalogue, but
>> allow the simply one-click selection of all current, for example, XP 32bit
>> post-SP3 updates for download to a single local master update folder – call
>> it a local catalogue.
>>
>> 3. On one master PC, you download all current updates from Microsoft. The
>> best would be to have something like SyncToy to keep the local copy in sync
>> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
>> removing replaced updates, and adding new ones. When the Sync process is
>> run, it quickly deletes old local copies and downloads any/all new updates
>> since the last Sync. Download costs are minimised by only adding updates not
>> already present in the local catalogue (master folder), and there is only one
>> download needed for the updates for as many PC’s as required.
>>
>> 4. On each local PC, you run a process similar to Automatic Updates. This
>> AutoUpdater process is a little different though – it only checks with the
>> local master to see what updates are needed, and instead up downloading each
>> update from Microsoft, it copies and/or simply runs the updates from the
>> local master folder. Perhaps the local AutoUpdater process could include an
>> online check to Microsoft to see if the local master catalogue has all
>> current updates present and let the operator know.
>>
>> What do you think? Ideas for a better system are encouraged! And how can
>> we encourage Microsoft to set this up? – (if they haven’t already done it and
>> I haven’t found it!!!)<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

"Harry Johnston [MVP]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Egaskrad wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Doesn't WSUS suit that purpose?<!--colorc--><!--/colorc-->
>
> Not really - most folks with 5 to 10 PC's probably don't want to shell out for
> an expensive Windows server license.
>
> Harry.<!--colorc--><!--/colorc-->

I know. I mentioned that just in case. They never said that they do not have
a Windows Server around.
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> <!--coloro:green--><span style="color:green <!--/coloro-->
> >
> > "Peter Tanner" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> I haven't exhaustively researched all options that Microsoft currently
> >> provide, but it seems there isn't a nice simple way of keeping a group of
> >> PC's updated from a single download session of all current updates.
> >>
> >> This is how I think a nice system could work:
> >>
> >> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> >> re-install of Windows XP SP3 on some, others may have various stages of
> >> post-SP3 updates installed. You can't afford the cost of repeated downloads
> >> of all updates re-occurring many times – Automatic Updates works, but it’s
> >> too costly.
> >>
> >> 2. Microsoft should have available something like Microsoft Catalogue, but
> >> allow the simply one-click selection of all current, for example, XP 32bit
> >> post-SP3 updates for download to a single local master update folder – call
> >> it a local catalogue.
> >>
> >> 3. On one master PC, you download all current updates from Microsoft. The
> >> best would be to have something like SyncToy to keep the local copy in sync
> >> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
> >> removing replaced updates, and adding new ones. When the Sync process is
> >> run, it quickly deletes old local copies and downloads any/all new updates
> >> since the last Sync. Download costs are minimised by only adding updates not
> >> already present in the local catalogue (master folder), and there is only one
> >> download needed for the updates for as many PC’s as required.
> >>
> >> 4. On each local PC, you run a process similar to Automatic Updates. This
> >> AutoUpdater process is a little different though – it only checks with the
> >> local master to see what updates are needed, and instead up downloading each
> >> update from Microsoft, it copies and/or simply runs the updates from the
> >> local master folder. Perhaps the local AutoUpdater process could include an
> >> online check to Microsoft to see if the local master catalogue has all
> >> current updates present and let the operator know.
> >>
> >> What do you think? Ideas for a better system are encouraged! And how can
> >> we encourage Microsoft to set this up? – (if they haven’t already done it and
> >> I haven’t found it!!!)<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->

 

Thanks TaurArian, but burning CD's every week or so, and updating all the
PC's from them would be really slow and tedious...

"TaurArian" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Peter Tanner wrote:
> :: I haven't exhaustively researched all options that Microsoft
> :: currently provide, but it seems there isn't a nice simple way of
> :: keeping a group of PC's updated from a single download session of
> :: all current updates.
> ::
> :: This is how I think a nice system could work:
> ::
> :: 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> :: re-install of Windows XP SP3 on some, others may have various stages
> :: of post-SP3 updates installed. You can't afford the cost of
> :: repeated downloads of all updates re-occurring many times -
> :: Automatic Updates works, but it's too costly.
> ::
> :: 2. Microsoft should have available something like Microsoft
> :: Catalogue, but allow the simply one-click selection of all current,
> :: for example, XP 32bit post-SP3 updates for download to a single
> :: local master update folder - call it a local catalogue.
> ::
> :: 3. On one master PC, you download all current updates from
> :: Microsoft. The best would be to have something like SyncToy to keep
> :: the local copy in sync with the "Microsoft Catalogue" - Microsoft
> :: keep their "catalogue" current by removing replaced updates, and
> :: adding new ones. When the Sync process is run, it quickly deletes
> :: old local copies and downloads any/all new updates since the last
> :: Sync. Download costs are minimised by only adding updates not
> :: already present in the local catalogue (master folder), and there is
> :: only one download needed for the updates for as many PC's as
> :: required.
> ::
> :: 4. On each local PC, you run a process similar to Automatic
> :: Updates. This AutoUpdater process is a little different though - it
> :: only checks with the local master to see what updates are needed,
> :: and instead up downloading each update from Microsoft, it copies
> :: and/or simply runs the updates from the local master folder.
> :: Perhaps the local AutoUpdater process could include an online check
> :: to Microsoft to see if the local master catalogue has all current
> :: updates present and let the operator know.
> ::
> :: What do you think? Ideas for a better system are encouraged! And
> :: how can we encourage Microsoft to set this up? - (if they haven't
> :: already done it and I haven't found it!!!)
>
>
> Security updates are available on ISO-9660 CD image files from the Microsoft
> Download Center
>
> --
>
> TaurArian [MVP] 2005-2010 - Update Services
>
> ======================================
> Disclaimer: The information has been posted "as is" with no warranties
> or guarantees and doesn't give any rights.
>
>
>
> <!--colorc--><!--/colorc-->

 

Spot on Harry - I don't have a server. All PC's only have XP Pro SP3.

"Egaskrad" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
>
> "Harry Johnston [MVP]" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Egaskrad wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Doesn't WSUS suit that purpose?<!--colorc--><!--/colorc-->
> >
> > Not really - most folks with 5 to 10 PC's probably don't want to shell out for
> > an expensive Windows server license.
> >
> > Harry.<!--colorc--><!--/colorc-->
>
> I know. I mentioned that just in case. They never said that they do not have
> a Windows Server around.
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > >
> > > "Peter Tanner" wrote:
> > >
> > >> I haven't exhaustively researched all options that Microsoft currently
> > >> provide, but it seems there isn't a nice simple way of keeping a group of
> > >> PC's updated from a single download session of all current updates.
> > >>
> > >> This is how I think a nice system could work:
> > >>
> > >> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> > >> re-install of Windows XP SP3 on some, others may have various stages of
> > >> post-SP3 updates installed. You can't afford the cost of repeated downloads
> > >> of all updates re-occurring many times – Automatic Updates works, but it’s
> > >> too costly.
> > >>
> > >> 2. Microsoft should have available something like Microsoft Catalogue, but
> > >> allow the simply one-click selection of all current, for example, XP 32bit
> > >> post-SP3 updates for download to a single local master update folder – call
> > >> it a local catalogue.
> > >>
> > >> 3. On one master PC, you download all current updates from Microsoft. The
> > >> best would be to have something like SyncToy to keep the local copy in sync
> > >> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
> > >> removing replaced updates, and adding new ones. When the Sync process is
> > >> run, it quickly deletes old local copies and downloads any/all new updates
> > >> since the last Sync. Download costs are minimised by only adding updates not
> > >> already present in the local catalogue (master folder), and there is only one
> > >> download needed for the updates for as many PC’s as required.
> > >>
> > >> 4. On each local PC, you run a process similar to Automatic Updates. This
> > >> AutoUpdater process is a little different though – it only checks with the
> > >> local master to see what updates are needed, and instead up downloading each
> > >> update from Microsoft, it copies and/or simply runs the updates from the
> > >> local master folder. Perhaps the local AutoUpdater process could include an
> > >> online check to Microsoft to see if the local master catalogue has all
> > >> current updates present and let the operator know.
> > >>
> > >> What do you think? Ideas for a better system are encouraged! And how can
> > >> we encourage Microsoft to set this up? – (if they haven’t already done it and
> > >> I haven’t found it!!!)<!--colorc--><!--/colorc-->
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Thanks Jim. Does WSUS run on XP Pro?

"Jim" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Peter Tanner wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > I haven't exhaustively researched all options that Microsoft currently
> > provide, but it seems there isn't a nice simple way of keeping a group of
> > PC's updated from a single download session of all current updates.
> >
> > This is how I think a nice system could work:
> >
> > 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> > re-install of Windows XP SP3 on some, others may have various stages of
> > post-SP3 updates installed. You can't afford the cost of repeated downloads
> > of all updates re-occurring many times – Automatic Updates works, but it’s
> > too costly.
> >
> > 2. Microsoft should have available something like Microsoft Catalogue, but
> > allow the simply one-click selection of all current, for example, XP 32bit
> > post-SP3 updates for download to a single local master update folder – call
> > it a local catalogue.
> >
> > 3. On one master PC, you download all current updates from Microsoft. The
> > best would be to have something like SyncToy to keep the local copy in sync
> > with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
> > removing replaced updates, and adding new ones. When the Sync process is
> > run, it quickly deletes old local copies and downloads any/all new updates
> > since the last Sync. Download costs are minimised by only adding updates not
> > already present in the local catalogue (master folder), and there is only one
> > download needed for the updates for as many PC’s as required.
> >
> > 4. On each local PC, you run a process similar to Automatic Updates. This
> > AutoUpdater process is a little different though – it only checks with the
> > local master to see what updates are needed, and instead up downloading each
> > update from Microsoft, it copies and/or simply runs the updates from the
> > local master folder. Perhaps the local AutoUpdater process could include an
> > online check to Microsoft to see if the local master catalogue has all
> > current updates present and let the operator know.
> >
> > What do you think? Ideas for a better system are encouraged! And how can
> > we encourage Microsoft to set this up? – (if they haven’t already done it and
> > I haven’t found it!!!)<!--colorc--><!--/colorc-->
> See
>
>
> Jim
> <!--colorc--><!--/colorc-->

 

Thanks Shenan. Does WSUS run under/on XP Pro? I don't have any Windows
Server OS.

"Shenan Stanley" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Peter Tanner wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > I haven't exhaustively researched all options that Microsoft
> > currently provide, but it seems there isn't a nice simple way of
> > keeping a group of PC's updated from a single download session of
> > all current updates.
> >
> > This is how I think a nice system could work:
> >
> > 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> > re-install of Windows XP SP3 on some, others may have various
> > stages of post-SP3 updates installed. You can't afford the cost of
> > repeated downloads of all updates re-occurring many times -
> > Automatic Updates works, but it's too costly.
> >
> > 2. Microsoft should have available something like Microsoft
> > Catalogue, but allow the simply one-click selection of all current,
> > for example, XP 32bit post-SP3 updates for download to a single
> > local master update folder - call it a local catalogue.
> >
> > 3. On one master PC, you download all current updates from
> > Microsoft. The best would be to have something like SyncToy to
> > keep the local copy in sync with the "Microsoft Catalogue" -
> > Microsoft keep their "catalogue" current by removing replaced
> > updates, and adding new ones. When the Sync process is run, it
> > quickly deletes old local copies and downloads any/all new updates
> > since the last Sync. Download costs are minimised by only adding
> > updates not already present in the local catalogue (master folder),
> > and there is only one download needed for the updates for as many
> > PC's as required.
> >
> > 4. On each local PC, you run a process similar to Automatic
> > Updates. This AutoUpdater process is a little different though -
> > it only checks with the local master to see what updates are
> > needed, and instead up downloading each update from Microsoft, it
> > copies and/or simply runs the updates from the local master folder.
> > Perhaps the local AutoUpdater process could include an online check
> > to Microsoft to see if the local master catalogue has all current
> > updates present and let the operator know.
> >
> > What do you think? Ideas for a better system are encouraged! And
> > how can we encourage Microsoft to set this up? - (if they haven't
> > already done it and I haven't found it!!!)<!--colorc--><!--/colorc-->
>
> WSUS
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
>
>
>
> <!--colorc--><!--/colorc-->

 

Yes

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Peter Tanner" <PeterTanner@discussions.microsoft.com> wrote in message
news:C7160E3E-C746-40F3-A818-4E203953FAE7@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Thanks Jim. Does WSUS run on XP Pro?
>
> "Jim" wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>> Peter Tanner wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>> > I haven't exhaustively researched all options that Microsoft currently
>> > provide, but it seems there isn't a nice simple way of keeping a group of
>> > PC's updated from a single download session of all current updates.
>> >
>> > This is how I think a nice system could work:
>> >
>> > 1. Say you have 5 to 10 PC's. Every so often you might do a clean
>> > re-install of Windows XP SP3 on some, others may have various stages of
>> > post-SP3 updates installed. You can't afford the cost of repeated downloads
>> > of all updates re-occurring many times – Automatic Updates works, but it’s
>> > too costly.
>> >
>> > 2. Microsoft should have available something like Microsoft Catalogue, but
>> > allow the simply one-click selection of all current, for example, XP 32bit
>> > post-SP3 updates for download to a single local master update folder – call
>> > it a local catalogue.
>> >
>> > 3. On one master PC, you download all current updates from Microsoft. The
>> > best would be to have something like SyncToy to keep the local copy in sync
>> > with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
>> > removing replaced updates, and adding new ones. When the Sync process is
>> > run, it quickly deletes old local copies and downloads any/all new updates
>> > since the last Sync. Download costs are minimised by only adding updates not
>> > already present in the local catalogue (master folder), and there is only one
>> > download needed for the updates for as many PC’s as required.
>> >
>> > 4. On each local PC, you run a process similar to Automatic Updates. This
>> > AutoUpdater process is a little different though – it only checks with the
>> > local master to see what updates are needed, and instead up downloading each
>> > update from Microsoft, it copies and/or simply runs the updates from the
>> > local master folder. Perhaps the local AutoUpdater process could include an
>> > online check to Microsoft to see if the local master catalogue has all
>> > current updates present and let the operator know.
>> >
>> > What do you think? Ideas for a better system are encouraged! And how can
>> > we encourage Microsoft to set this up? – (if they haven’t already done it and
>> > I haven’t found it!!!)<!--colorc--><!--/colorc-->
>> See
>>
>>
>> Jim
>> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

The CD generated by the site I referenced works fine on my XP Pro & Home
systems okay.

Jim

Peter Tanner wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Thanks Jim. Does WSUS run on XP Pro?
>
> "Jim" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>> Peter Tanner wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> I haven't exhaustively researched all options that Microsoft currently
>>> provide, but it seems there isn't a nice simple way of keeping a group of
>>> PC's updated from a single download session of all current updates.
>>>
>>> This is how I think a nice system could work:
>>>
>>> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
>>> re-install of Windows XP SP3 on some, others may have various stages of
>>> post-SP3 updates installed. You can't afford the cost of repeated downloads
>>> of all updates re-occurring many times – Automatic Updates works, but it’s
>>> too costly.
>>>
>>> 2. Microsoft should have available something like Microsoft Catalogue, but
>>> allow the simply one-click selection of all current, for example, XP 32bit
>>> post-SP3 updates for download to a single local master update folder – call
>>> it a local catalogue.
>>>
>>> 3. On one master PC, you download all current updates from Microsoft. The
>>> best would be to have something like SyncToy to keep the local copy in sync
>>> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
>>> removing replaced updates, and adding new ones. When the Sync process is
>>> run, it quickly deletes old local copies and downloads any/all new updates
>>> since the last Sync. Download costs are minimised by only adding updates not
>>> already present in the local catalogue (master folder), and there is only one
>>> download needed for the updates for as many PC’s as required.
>>>
>>> 4. On each local PC, you run a process similar to Automatic Updates. This
>>> AutoUpdater process is a little different though – it only checks with the
>>> local master to see what updates are needed, and instead up downloading each
>>> update from Microsoft, it copies and/or simply runs the updates from the
>>> local master folder. Perhaps the local AutoUpdater process could include an
>>> online check to Microsoft to see if the local master catalogue has all
>>> current updates present and let the operator know.
>>>
>>> What do you think? Ideas for a better system are encouraged! And how can
>>> we encourage Microsoft to set this up? – (if they haven’t already done it and
>>> I haven’t found it!!!)<!--colorc--><!--/colorc-->
>> See
>>
>>
>> Jim
>><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Peter Foldes - what does this mean? - "Please Reply to Newsgroup" - how do I
do that?

And what does this mean? - "Requests for assistance by email" - I'm not
using e-mail - I'm using this Microsoft Discussion Groups web service
whatever...

"Peter Foldes" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Yes
>
> --
> Peter
>
> Please Reply to Newsgroup for the benefit of others
> Requests for assistance by email can not and will not be acknowledged.
>
> "Peter Tanner" <PeterTanner@discussions.microsoft.com> wrote in message
> news:C7160E3E-C746-40F3-A818-4E203953FAE7@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
> > Thanks Jim. Does WSUS run on XP Pro?
> >
> > "Jim" wrote:
> ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> Peter Tanner wrote:
> >> > I haven't exhaustively researched all options that Microsoft currently
> >> > provide, but it seems there isn't a nice simple way of keeping a group of
> >> > PC's updated from a single download session of all current updates.
> >> >
> >> > This is how I think a nice system could work:
> >> >
> >> > 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> >> > re-install of Windows XP SP3 on some, others may have various stages of
> >> > post-SP3 updates installed. You can't afford the cost of repeated downloads
> >> > of all updates re-occurring many times – Automatic Updates works, but it’s
> >> > too costly.
> >> >
> >> > 2. Microsoft should have available something like Microsoft Catalogue, but
> >> > allow the simply one-click selection of all current, for example, XP 32bit
> >> > post-SP3 updates for download to a single local master update folder – call
> >> > it a local catalogue.
> >> >
> >> > 3. On one master PC, you download all current updates from Microsoft. The
> >> > best would be to have something like SyncToy to keep the local copy in sync
> >> > with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
> >> > removing replaced updates, and adding new ones. When the Sync process is
> >> > run, it quickly deletes old local copies and downloads any/all new updates
> >> > since the last Sync. Download costs are minimised by only adding updates not
> >> > already present in the local catalogue (master folder), and there is only one
> >> > download needed for the updates for as many PC’s as required.
> >> >
> >> > 4. On each local PC, you run a process similar to Automatic Updates. This
> >> > AutoUpdater process is a little different though – it only checks with the
> >> > local master to see what updates are needed, and instead up downloading each
> >> > update from Microsoft, it copies and/or simply runs the updates from the
> >> > local master folder. Perhaps the local AutoUpdater process could include an
> >> > online check to Microsoft to see if the local master catalogue has all
> >> > current updates present and let the operator know.
> >> >
> >> > What do you think? Ideas for a better system are encouraged! And how can
> >> > we encourage Microsoft to set this up? – (if they haven’t already done it and
> >> > I haven’t found it!!!)
> >> See
> >>
> >>
> >> Jim
> >> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

Peter Tanner, Peter Foldes answered your question and said "yes".

The rest of the writing is in the signature.
As to how do you reply to the Newsgroup - you're doing it.
Personal requests sent via email to Peter Foldes will not be acknowledged.

Surely you can work that out.

K


Peter Tanner wrote:
:: Peter Foldes - what does this mean? - "Please Reply to Newsgroup" -
:: how do I do that?
::
:: And what does this mean? - "Requests for assistance by email" - I'm
:: not using e-mail - I'm using this Microsoft Discussion Groups web
:: service whatever...
::
:: "Peter Foldes" wrote:
::
::: Yes
:::
::: --
::: Peter
:::
::: Please Reply to Newsgroup for the benefit of others
::: Requests for assistance by email can not and will not be
::: acknowledged.
:::
::: "Peter Tanner" <PeterTanner@discussions.microsoft.com> wrote in
::: message news:C7160E3E-C746-40F3-A818-4E203953FAE7@microsoft.com...
:::: Thanks Jim. Does WSUS run on XP Pro?
::::
:::: "Jim" wrote:
::::
::::: Peter Tanner wrote:
:::::: I haven't exhaustively researched all options that Microsoft
:::::: currently provide, but it seems there isn't a nice simple way of
:::::: keeping a group of PC's updated from a single download session
:::::: of all current updates.
::::::
:::::: This is how I think a nice system could work:
::::::
:::::: 1. Say you have 5 to 10 PC's. Every so often you might do a
:::::: clean re-install of Windows XP SP3 on some, others may have
:::::: various stages of post-SP3 updates installed. You can't afford
:::::: the cost of repeated downloads of all updates re-occurring many
:::::: times - Automatic Updates works, but it's too costly.
::::::
:::::: 2. Microsoft should have available something like Microsoft
:::::: Catalogue, but allow the simply one-click selection of all
:::::: current, for example, XP 32bit post-SP3 updates for download to
:::::: a single local master update folder - call it a local catalogue.
::::::
:::::: 3. On one master PC, you download all current updates from
:::::: Microsoft. The best would be to have something like SyncToy to
:::::: keep the local copy in sync with the "Microsoft Catalogue" -
:::::: Microsoft keep their "catalogue" current by removing replaced
:::::: updates, and adding new ones. When the Sync process is run, it
:::::: quickly deletes old local copies and downloads any/all new
:::::: updates since the last Sync. Download costs are minimised by
:::::: only adding updates not already present in the local catalogue
:::::: (master folder), and there is only one download needed for the
:::::: updates for as many PC's as required.
::::::
:::::: 4. On each local PC, you run a process similar to Automatic
:::::: Updates. This AutoUpdater process is a little different though
:::::: - it only checks with the local master to see what updates are
:::::: needed, and instead up downloading each update from Microsoft,
:::::: it copies and/or simply runs the updates from the local master
:::::: folder. Perhaps the local AutoUpdater process could include an
:::::: online check to Microsoft to see if the local master catalogue
:::::: has all current updates present and let the operator know.
::::::
:::::: What do you think? Ideas for a better system are encouraged!
:::::: And how can we encourage Microsoft to set this up? - (if they
:::::: haven't already done it and I haven't found it!!!)
::::: See
:::::
:::::
::::: Jim

 

Peter Tanner wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Thanks Jim. Does WSUS run on XP Pro?<!--colorc--><!--/colorc-->

No. It requires Windows Server.

Harry.
<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> "Jim" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>> Peter Tanner wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> I haven't exhaustively researched all options that Microsoft currently
>>> provide, but it seems there isn't a nice simple way of keeping a group of
>>> PC's updated from a single download session of all current updates.
>>>
>>> This is how I think a nice system could work:
>>>
>>> 1. Say you have 5 to 10 PC's. Every so often you might do a clean
>>> re-install of Windows XP SP3 on some, others may have various stages of
>>> post-SP3 updates installed. You can't afford the cost of repeated downloads
>>> of all updates re-occurring many times – Automatic Updates works, but it’s
>>> too costly.
>>>
>>> 2. Microsoft should have available something like Microsoft Catalogue, but
>>> allow the simply one-click selection of all current, for example, XP 32bit
>>> post-SP3 updates for download to a single local master update folder – call
>>> it a local catalogue.
>>>
>>> 3. On one master PC, you download all current updates from Microsoft. The
>>> best would be to have something like SyncToy to keep the local copy in sync
>>> with the "Microsoft Catalogue" – Microsoft keep their "catalogue" current by
>>> removing replaced updates, and adding new ones. When the Sync process is
>>> run, it quickly deletes old local copies and downloads any/all new updates
>>> since the last Sync. Download costs are minimised by only adding updates not
>>> already present in the local catalogue (master folder), and there is only one
>>> download needed for the updates for as many PC’s as required.
>>>
>>> 4. On each local PC, you run a process similar to Automatic Updates. This
>>> AutoUpdater process is a little different though – it only checks with the
>>> local master to see what updates are needed, and instead up downloading each
>>> update from Microsoft, it copies and/or simply runs the updates from the
>>> local master folder. Perhaps the local AutoUpdater process could include an
>>> online check to Microsoft to see if the local master catalogue has all
>>> current updates present and let the operator know.
>>>
>>> What do you think? Ideas for a better system are encouraged! And how can
>>> we encourage Microsoft to set this up? – (if they haven’t already done it and
>>> I haven’t found it!!!)<!--colorc--><!--/colorc-->
>> See
>>
>>
>> Jim
>><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

No.

I upgraded my DC from 2000 to 2003 and later to 2008 then 2008R2 just for
this WSUS...

"Peter Tanner" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Thanks Shenan. Does WSUS run under/on XP Pro? I don't have any Windows
> Server OS.
>
> "Shenan Stanley" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Peter Tanner wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > I haven't exhaustively researched all options that Microsoft
> > > currently provide, but it seems there isn't a nice simple way of
> > > keeping a group of PC's updated from a single download session of
> > > all current updates.
> > >
> > > This is how I think a nice system could work:
> > >
> > > 1. Say you have 5 to 10 PC's. Every so often you might do a clean
> > > re-install of Windows XP SP3 on some, others may have various
> > > stages of post-SP3 updates installed. You can't afford the cost of
> > > repeated downloads of all updates re-occurring many times -
> > > Automatic Updates works, but it's too costly.
> > >
> > > 2. Microsoft should have available something like Microsoft
> > > Catalogue, but allow the simply one-click selection of all current,
> > > for example, XP 32bit post-SP3 updates for download to a single
> > > local master update folder - call it a local catalogue.
> > >
> > > 3. On one master PC, you download all current updates from
> > > Microsoft. The best would be to have something like SyncToy to
> > > keep the local copy in sync with the "Microsoft Catalogue" -
> > > Microsoft keep their "catalogue" current by removing replaced
> > > updates, and adding new ones. When the Sync process is run, it
> > > quickly deletes old local copies and downloads any/all new updates
> > > since the last Sync. Download costs are minimised by only adding
> > > updates not already present in the local catalogue (master folder),
> > > and there is only one download needed for the updates for as many
> > > PC's as required.
> > >
> > > 4. On each local PC, you run a process similar to Automatic
> > > Updates. This AutoUpdater process is a little different though -
> > > it only checks with the local master to see what updates are
> > > needed, and instead up downloading each update from Microsoft, it
> > > copies and/or simply runs the updates from the local master folder.
> > > Perhaps the local AutoUpdater process could include an online check
> > > to Microsoft to see if the local master catalogue has all current
> > > updates present and let the operator know.
> > >
> > > What do you think? Ideas for a better system are encouraged! And
> > > how can we encourage Microsoft to set this up? - (if they haven't
> > > already done it and I haven't found it!!!)<!--colorc--><!--/colorc-->
> >
> > WSUS
> >
> > --
> > Shenan Stanley
> > MS-MVP
> > --
> > How To Ask Questions The Smart Way
> >
> >
> >
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->