WUAU22.msi

[Tim Petlock]

I'm trying to deploy the software update service. I have
the in-house web server with the program (probably)
working and approved updates. I made a copy of the
directory as best I could (inconsistent instructions) and
hosted it on my production intranet server.

I created a group policy to install WUAU22.msi on a test
group of Win2k machines, as well as a group policy to set
the registry settings appropriately.

The registry settings get to the machines but that's
about it.
In the application log I first get a 301 event from
Application Management saying the assignment of the
application succeeded.
Then I get a 10000 from MsiInstaller saying: The
description for Event ID ( 10000 ) in Source (
MsiInstaller ) cannot be found. The local computer may
not have the necessary registry information or message
DLL files to display messages from a remote computer. You
may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The
following information is part of the event: Product:
Microsoft Windows Update Auto Update -- Microsoft Windows
Update Auto Update requires Windows 2000 SP2 or Windows
XP., (NULL), (NULL), (NULL), (NULL), (NULL), (NULL).
After that I get a 102 from Application Management saying
the application install failed.
Then I get a 303 from Application Management saying that
the removal of the policy succeeded.
Finally I get 108 from Application Management saying that
there was a fatal error during installation.

I'm running Windows 2000 SP3 - is this the cause? Does
this mean the automatic updates client in Win2kSP3 just
needs the registry settings to work?

I have seen exactly zero traffic on my web server. I'm
not sure I have it configured correctly because the
instructions are ambiguous. (Steps 2 and 3 make sense
but 5 confused me)
1. Confirm that IIS is installed.
2. Create a folder named \Content
3. Copy all the files and folders under the
\Content\cabs directory from the source server running
SUS to the \Content directory on the server with the
manually-created content distribution point:
4. Copy the following files under the VROOT of the
default web site
.. <root of the SUS Web site>\Aucatalog1.cab
.. <root of the SUS Web site>\Aurtf1.cab
.. <root of the SUS Web site>\approveditems.txt
5. Create a VROOT called "Content" and point to
the "\Content\Cabs" directory

I interpreted this as meaning my virtual root
called "Content" should have the two cab files and the
text file. Does it really mean that the "default"
default web site should have those files?

This is confusing.

Sorry to post it here but I can't find the appropriate
newsgroup through this web interface.

Tim Petlock

 

[Scott]

Tim,

For simplicity, it is probably best to break your project down into
individual problems.

1. AutoUpdate client deployment. If you have Win2000-SP3, then that is
complete. There is an error produced if you attempt to install the
WUAU22.msi client on a Win2000-SP3 computer.

2. The content distribution point. The doco does sound a little odd. For
Step 5, try just creating the Virtual directory "Content" pointing to the
/content directory. Also, with Step 2, it does not mean you need to create
the directory under the website. This method of distribution requires
babysitting, you may wish to consider an active SUS server.

3. AutoUpdate client configuration. You have an AD environment. Break you
computers down into different OUs and use a Group Policy to configure them.

For a follow-up, you may want to select the appropriate newsgroup for the
individual issues.

I hope that gives you a start.

Scott

 

[Martin]

HI
Why don't you deploy SP4 instead?
Then you don't need the wuau22
/Martin