How do I know???


Jonathan Telep

I have another question... How do I know that the
workstations configured to pull packages from the sus
server are pulling them or not? Unless I'm totally off
base here, my understanding is that, the server brings
them all in locally and then the internal workstations get
their updates off of the sus server. When I look at the
logs from the workstations though, this is what I see:

2003-10-27 13:00:31 18:00:31 Success IUENGINE
Shutting down
2003-10-27 13:00:31 18:00:31 Success IUCTL
Shutting down
2003-10-27 13:05:14 18:05:14 Success IUENGINE
Querying software update catalog from
2003-10-27 13:05:18 18:05:18 Success IUENGINE
Asynchronous Download started
2003-10-27 13:05:18 18:05:18 Success IUENGINE
Download destination root folder is: C:\WUTemp
2003-10-27 13:05:34 18:05:34 Success IUENGINE
Downloaded file

and so on and so forth. It seems like the workstation
only queries the sus server but when it comes to actually
downloading packages, it still goes out to the MS
website. Am I doing something wrong or is this how it's
supposed to work and if so then why download 13 GB worth
of packages that will never be used.




Try this from your sus server

should work if you did the following when you set up sus

To log windows updates you need to change the properties
for the default web site.
From Internet Information Services right click Default web
site the click properties.
On the Home Directory tab for the default web site clear
the check mark for Log visits.
In the right windowpane right click wutrack.bin and then
click properties.
Check the Log visits box on the wutrack.bin properties
file tab

You can also check the austate in the registry

0 Initial 24 hour timeout (the AU wizard does not run
until 24 hours after it first detects an Internet
1 Waiting for user to run AU wizard
2 Detect pending
3 Download pending (waiting for user to accept pre-
download prompt)
4 Download in progress
5 Install pending
6 Install complete
7 Disabled (Adoptions will also be set to a value of 0x1)
8 Reboot pending (updates that require a reboot were
installed but the reboot was declined - AU will not do
anything until the reboot occurs and this value is

if it is stuck at 4 then the client PC couldn't get to the
updates which means you need to change the select where
you want to store updates option on you sus server to save
the updates to a local folder.

Jonathan Telep

Hey thanks a lot, that was really helpful because I can at
least get a better idea for what's happening on the SUS
server but now I have a couple more questions for you in
light of that:

1.) Whenever I look at the "austate" in the registry now,
I keep seeing a "2" there, no matter how many downloads I
grab and install. I'm guessing that number should change
every time I successfully download and install an update
so I'm not really sure what's going on there.

2.) That site is great and gives me a lot more detail than
I could ever figure out on my own but, again, I have one
question about that too:

What does the "Client Type" field define? I'm
guessing "AU" means "automatic update" but I have no idea
what "IU" stands for or even, more importantly, "Windows
Update Site". Would that definition be for the user who
simply runs "Windows Update" on his own instead of
scheduling it? And also, although the "Status"
says "succeeded" and there are no "error codes", should I
still assume that the successful updates that came from
all of the entries came from my SUSServer? I just want to
verify that when the "client type" field changed
to "Windows Update Site" that that doens't mean that the
workstation is right back to grabbing it's updates from
the web.

Thanks in advance,


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question