Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SUSserver client problems

Status
Not open for further replies.
Feb 19, 2004
59
I have installed my susserver and set it to manually approve updates. However my client doesn't seems to be abled to get those approved updates from my SUSserver.
Here is my scenario...

I created an OU called testing and move my testing PC called ABC into the OU. From the Group Policy, I add the wuau.adm templates under computer settings. Also on windows configurations, windows updates, under configure automatic updates, i enable auto updates and schedule it to download the updates at 10am everyday. Under specify intranet Microsoft update service location, i point the settings to my SUSserver. However, my client doesn't seems to get the update. What could have gone wrong? Please advise
 
Make sure you have at least xp sp1 on your client, and check event logs to make sure that your client is having the group policy applied. make sure that you have put the client computername into the correct OU in active directory.
 
Also make sure you have approved the necessary updates for downloading on your sus server admin page.
 
hi snipesnab:

My client is a windows 2000 professional running SP4. I have checked the event logs for this client, but there it nothing inside. But my autoupdate is gray out and it is getting the settings from my Group policy. I have also approve the updates in my sus server admin page.
Any idea what is the problem, more help is needed.

Thanks
 
Similiar problem:
I can get it to work with a local security policy but when I try to apply a GPO to with the wuau.adm applied it does not appear to apply the policy to the computer or user that I specify in the GPO security tab. I am running in mixed mode. Also I have added this test policy as the second policy in the order (we only have two, default and this test GPO for SUS).I think this should still work for 2000 clients right?
Thanks for any help in advance
 
Best to create the policy for rollout right at the top level of your AD tree (so that the computer objects are in the scope of the GPO) and then control access that way. I have got it working now but like yourself, I put it above an OU before which didn't work!
Hope that helps!
 
Hi,

Check that what Configuration IIS Lockdown utility is running. This can block requests from the client to the server.

Make sure your DNS settings on the client are correct. e.g. no additional suffixes.

enbw
 
was the windowsupdate.log created on the client machine? < c:\winnt\windowsupdate.log >

Also, is the BITS service running on this client machine? AU requires both the Automatic Updates and Background Intelligent Transfer Service to be running for the packets to be delivered. There is also a daily log file on the SUS server that will log clients and what they are accessing from the server...

scottie
 
But my autoupdate is gray out"

Are you sure the Automatic Updates service is running on the client? I always make sure that service is set to enabled/autostart in any GPO that points to a SUS server.

"and it is getting the settings from my Group policy"

How are you determining that? With gpresult or registry?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top