Clients don't look to SUS server for updates

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.

>-----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.

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.
>
>.
>

As I said in my previous post, you can use Local Group
Policy if you aren't in an AD environment. The same
whitepaper that you mention gives instructions for using
Local Group Policy as well as the Registry.
In either case, you would pretty much need to configure
each machine individually.
>-----Original Message-----
>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.
>>
>>.
>>
>.
>

"Charlie" <> wrote in news:943c01c4861c
$0ddc8aa0$:

> As I said in my previous post, you can use Local Group
> Policy if you aren't in an AD environment. The same
> whitepaper that you mention gives instructions for using
> Local Group Policy as well as the Registry.
> In either case, you would pretty much need to configure
> each machine individually.

Ugh! Why didn't Microsoft simply include a way to make the
updates work like in 9x? Just toss them all in the update
folder where Windowsupdate will find them and if the version
on the WU site is NOT newer, it'll install the local file?

So bloody simple and LOGICAL! (But this is Microsoft we're
talking about...)

I have all 33 current critical updates for a 2000 Pro SP4
install with IE6 SP1, Media Player 9 plus extra codecs and
DirectX 9c. I just want a simple way to make WU use a local
copy of the update files on the machine being updated.