Lude....
Installing the "latest windows update client".. will /NOT/ enable
Microsoft Update.
Furthermore, the "latest windows update client" has already been installed
by Windows Update or Automatic Updates, if the system has been updated in the
past several months.
Sebekiz....
Currently the /only/ way to enable Microsoft Update is to browse to the
site and OPT-IN to the use of Microsoft Update. This is necessary due to legal
obligations. It's not likely to change.
Frankly.. if you have 600 computers spread over 8 states, you need to be
looking at Windows Server Update Services as a corporate managed process, not
trying to manage 600 individual implementations of Automatic Updates (or
worse, Windows Update or Microsoft Update -- which requires user interaction
to be useful).
As for your management ruling out 'updates' because of SOX.... that's
incredible!!! -SOX- is EXACTLY the reason they /SHOULD/ be upgrading SMS,
using MBSA v2, or deploying Windows Server Update Services.
Just as a clue... you will /never/ be able to establish SOX compliance if
600 individual desktop computers have access to Windows Update and/or
Microsoft Update at the whim of the local user.
"Lude" <> wrote in message
news:EB04BADA-A69B-4980-A730-...
> Hello,
>
> You can obtain the latest windows update client from the following:
>
> http://download.windowsupdate.com/v6...gent20-x86.exe
>
> Hope this helps you out!
>
>
> "Sebekiz" wrote:
>
>> Currently I am using scripts to trigger Windows Update to download and
>> install patchs on some 600 desktops spread over 8 states. I'd like to know
>> if there is a way to update those systems to the new Microsoft Update
>> without
>> having to manually log each one onto the Windows Update Website and allow
>> the
>> softwar to download and install?
>>
>> Changes to our servers (such as updating SMS to support the new version of
>> MBSA or depoloying SUS) have been ruled out by management while they try to
>> implement Sarbanes-Oxley.
>>
>>