Software Update Services

[Allan Snow]

Hi all, we installed a fresh copy of Windows 2000 advanced server (PIII-1GHz, 512MB RAM etc. basically exceeds min specs). After that we went thru the typical sus install, lock down and synch with MS (and package approval) we are not getting any client updates (checked windowsupdate.log, local policy templates points to correct server, server resolves properly, we are autheticating etc.).
When we actually browse to an individual update package it downloads to the client. When you browse to the default server link ie http://servername all we get is "under construction". Is there a default file or asp that should be put in the IIS root that should trigger (or link) to the update packages that we are missing.

[shovel204]

After running the setup, did you add the template to your group policy, and set the two new policies that actually affect the clients? Did you push the client for sus to the client computers? The address should be set as the FQDN and then browse to the http page using the provided path, you will be prompted for a user name and password with rights to view it. If server called george the address would be http://george/susadmin
The clients cannot browse to the page, this is only an administrative page.

The white paper is hard to read, but after adding the administative template to the group policy browse to the new admin templates/windows components/windows update and click on the two new policy settings in the right hand pane. One sets the preferred sus server the other allows you to set how the clients get updated and when.


------------
Allan Snow at 9/9/2002 1:28:41 PM


Hi all, we installed a fresh copy of Windows 2000 advanced server (PIII-1GHz, 512MB RAM etc. basically exceeds min specs). After that we went thru the typical sus install, lock down and synch with MS (and package approval) we are not getting any client updates (checked windowsupdate.log, local policy templates points to correct server, server resolves properly, we are autheticating etc.).
When we actually browse to an individual update package it downloads to the client. When you browse to the default server link ie http://servername all we get is "under construction". Is there a default file or asp that should be put in the IIS root that should trigger (or link) to the update packages that we are missing.