patrickm

Well........ after several hundred posts to this newsgroup and a $270.00
phone call to MS, it finally works. For all of you who are have problems
with your clients not updating, my problem was finally resolved by this
undo***ented tidbit: We had to ********ly grant the anonymous internet user
( IUSR_SUSSERVER) Read & Execute permissions on the c:\SUS\content folder
and all of it's contents. By default it has a "Deny" permission for writing,
which is ok but no other permissions are granted, by simply checking off
Read& Execute permissions. Everything is working wonderfully. For all of you
who replied to any of my previous posts - Thanks for your help

jason helms

Patrick-

Glad to hear that it is working.

Best wishes-

JH

darren faulke

I've just made the changes and I now cross my fingers waiting to see
whether it will work for me.

If it was undo***ented and lots of other people are having problems then
is it particularly fair for you to have been charged. If it works then
I appreciate you're openness, considering it cost you money.

Regards

Darren

darren faulke

I've just realised what I said - whether it works or not, you should be
praised.

Regards

Darren

patrickm

Please keep in mind, I had made some other changes prior to this resolution.
FIRST OFF - Remove URLscan, this was my first problem, it was blocking
everything (You can always reinstall it after you get it working). Secondly
make sure your GPO is being propagated and functioning, I changed the
install time in the GPO a couple of different times and then checked my
clients to see that the install time had changed on the client. There is a
utility called "nwsusutil.exe" that works fairly good for testing updates
from the client, unfortunately I don't recall the website but I got it from
a post in this newsgroup. Monitors the log files, Client = c:\winnt\windows
update.log, Server= c:\winnt\system32\logfiles\w3svc1\ex_date.log. - Good
Luck, and be patient

darren faulke

Thanks for that. I've checked gpo policies are being propagated and
they are. I was under the impression that urlscan was reconfigured
during the installation of sus.

Anyway, I'm not forcing updates so I'll know either way tomorrow morning.

cheers

Darren

gessyjr

Hi folks,

I´ve got the same kind of problem, my client´s wont update using my
SUS, But I can do this using windows update web site, I´ve tried that
solution, but the problem still, and now I have no ideas to solve this
problem anymore.
Folow my windows update.log, if you guys have any Idea, I realy
apreciate that.
2004-07-22 08:25:28 11:25:28 Success IUCTL Starting
2004-07-22 08:25:29 11:25:29 Success IUCTL Downloaded
iuident.cab from http://susserver to C:\Arquivos de
programas\WindowsUpdate\V4
2004-07-22 08:25:29 11:25:29 Success IUENGINE Starting
2004-07-22 08:25:29 11:25:29 Success IUENGINE Determining
machine configuration
2004-07-22 08:25:30 11:25:30 Success IUENGINE Querying
software update catalog from
http://susserver/autoupdate/getmanifest.asp
2004-07-22 08:25:30 11:25:30 Success IUENGINE Determining
machine configuration
2004-07-22 08:25:30 11:25:30 Success IUENGINE Querying
software update catalog from
http://susserver/autoupdate/getmanifest.asp
2004-07-22 08:25:30 11:25:30 Success IUENGINE Determining
machine configuration
2004-07-22 08:25:30 11:25:30 Success IUENGINE Querying
software update catalog from
http://susserver/autoupdate/getmanifest.asp
2004-07-22 08:25:36 11:25:36 Success IUENGINE Determining
machine configuration
2004-07-22 08:25:37 11:25:37 Success IUENGINE Querying
software update catalog from
http://susserver/autoupdate/getmanifest.asp
2004-07-22 08:25:37 11:25:37 Success IUENGINE Shutting down
2004-07-22 08:25:37 11:25:37 Success IUCTL Shutting down

Thanks
Gessy