Issues implementing SUS

  • Thread starter Thread starter David
  • Start date Start date
D

David

Good afternoon,

I've been tasked with implementing a Software Updates
Services system on my local network. We do not,
currently, utilize active directory services on the
network. I have downloaded and successfully installed the
SUS v1.0 SP1 software on a system running Win2K server
with SP4. However, I am unable to determine how to cause
the Automated Update client to point to the local SUS
server rather than the Microsoft Windows Update site.

When I have attempted to install the v2.0 AU client, it
errors with a message that it requires Windows 2000/Sp2
or Windows XP to install. Since I was installing it on a
brand new, unpatched version of XP at the time, I found
that error interesting. However, presumably - according
to things I've read - when you install SP1 to XP, it
upgrades the AU client to the 2.0 version anyway, even
though I can find no evidence of that.

How do I get my local NT, 2000 and XP machines to query
and receive new updates from the local SUS server?

Thanks, in advance, for any help
David Nolan,
Network Admin
 
The white paper and\or deployment guide for SUS go into greater detail about
how to get the clients to use the SUS server. These are available here:

http://www.microsoft.com/downloads/...E4-6E41-4F54-972C-AE66A4E4BF6C&displaylang=en

The links are on the right side of the page. There is also a third-party web
site that may come in very handy:

http://www.susserver.com/

--
Tim Newton [MSFT]
(e-mail address removed)

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. The views and opinions
expressed in this newsgroup posting are mine and do not necessarily express
or reflect the views and / or opinions of Microsoft.
 
-----Original Message-----
The white paper and\or deployment guide for SUS go into greater detail about
how to get the clients to use the SUS server. These are
Click to expand...
available here:
<snip>

Good morning,

Thank you, I appreciate your response. I had and have
downloaded and read the white paper and it leads me to a
few additional questions. Having no Active Directory,
it's going to be necessary for me to modify the registry
of each system that I'm going to have utilizing the SUS
server. Following the directions of the White Paper, I
attempt to navigate to the keys listed and none of them
exist on my local workstation. Since the white paper
directs the reader to navigate to these keys, should
they, if the AU client is properly installed, already
exist? If they don't exist, then, is the client truly and
properly installed? I'm currently working on an XP
workstation which has SP1 installed. Next to it, I have a
Win2000 server system with SP4. I can not find any of
these registry keys on either box.

Am I doing something wrong? The last time I attempted
just creating these keys and assigning the specified
values I wound up rebuilding the workstation from
scratch - which is how I wound up with an XP workstation
with no patches to attempt installing the AU v2.2 client
to begin with.

Thanks
David
 
Back
Top