Clients don't look to SUS server for updates

From: Manfred Manthey (manfred.manthey_at_siemens.com)
Date: 08/19/04 

Date: Thu, 19 Aug 2004 02:01:17 -0700

Hi, if you dont not have a domain, then you have to
manually edit the registry-keys.
For more information, which keys are neede, refer to the
whitepaper: Deploying Microsoft Software Update Services

>-----Original Message-----
>
>>-----Original Message-----
>>Clients don't look to SUS servers for updates no matter
>what OS they are nor
>>what ever patch level they are patched.to. They always
>try to get to the
>>Microsoft site. There are no settings on the client
>where you can tell it
>>where to look. Waiting a couple days does not cause
>your clients to look
>>for updates on the local SUS server. Is there a way to
>make this stuff
>>work?
>>
>>Thanks,
>>Jack T.
>>
>>
>>.
>>As far as I know, the only way to point the clients at
>the SUS server is through Group Policy, and the adm
>template for that isn't included with XP prior to SP2.
>
>First of all, confirm that you have SUS SP1 installed.
>Along with the install files for that version there is
>the adm file that you need or you can download it here -
>http://www.microsoft.com/downloads/details.aspx?
>FamilyId=D26A0AEA-D274-42E6-8025-
>8C667B4C94E9&displaylang=en
>You will need to import the template into your Group
>Policy.
>That template adds 4 settings to Computer Configuration,
>Administrative Templates, Windows Components, Group
>Policy - The setting you're looking for to point the
>clients to your SUS server, another that configures how
>your clients will download and install the updates,
>another that will keep the computers from rebooting after
>an update install if the user is logged on and the last
>one will start a missed installation after the computer
>is next started.
>Another way to update the Group Policy is to use a
>Windows XP service pack 2 machine. The template will be
>already be installed on that machine, with several extra
>settings besides the ones I listed above. As you may
>know, once you open the Group Policy object, it will be
>updated with the new templates. You can then configure
>the Windows Update Group Policy settings.
>If you are not in an active Directory environment, you
>will have to go around to every machine to set the local
>Group Policy to do this.
>
>.
>

Relevant Pages

  • Re: Windows Update
    ... As long as your clients are SUS-aware, ... Laura E. Hunter - MCSE, MCT, MVP ... > SUS server automatically as long as they have Automatic Updates enabled. ... > (Also configurable through Group Policy.) If your 2K clients aren't on ...
    (microsoft.public.win2000.active_directory)
  • Re: Installs and Such
    ... I assume that the clients are ... Make sure that the domain user account object is not a member of the ... Use Group Policy to not allow them to install certain applications. ...
    (microsoft.public.win2000.active_directory)
  • Re: RPC Server Unavailable on clients...
    ... install... ... RPC Server Server is Unavailable ... Should I be adding another setting into the client's firewall policy to allow me to do these Group Policy Results? ... Any ideas how I open this up (I'm RDP'd into this network- so I can't exactly walk over to the clients workstation to make these changes, I have to change it in the GPO and wait for it to get pushed out to the clients). ...
    (microsoft.public.windows.server.sbs)
  • Clients dont look to SUS server for updates
    ... >Clients don't look to SUS servers for updates no matter ... >for updates on the local SUS server. ... Along with the install files for that version there is ...
    (microsoft.public.windowsupdate)
  • Re: SUS Server:- Client updation without group policy
    ... While I'm no expert on the subject, what Group Policy does, is push a ... configuration set out to your clients. ... > without Active directory architecture using SUS Server. ...
    (microsoft.public.win2000.windows_update)
Loading