Pointing clients to new SUS server

OK, in a nutshell :

Had a server named XXXSUS, replaced it with a new server named XXXSUS1

Running SUS in an active directory environment with GPO's controlling
the updates.

Afer new server brought on line, all GPO's were edited to point clients
to New server using FQDN in the format HTTP://XXSUS1.XX.XX.XX.

Since that time, there has been absolutely NO client side activity in
the windows update.log file.

Looking at event viewer, I'm seeing the follow errors on almost all
randomly selected clients :


Event Type: Warning
Event Source: Automatic Updates
Event Category: Download
Event ID: 16
Date: 1/24/2005
Time: 12:32:02 PM
User: N/A
Computer: XXXX-XXXXXXXX
Description:
Unable to connect: Windows is unable to connect to the Automatic Updates
service and therefore cannot download and install updates according to
the set schedule. Windows will continue to try to establish a connection.



I'm assuming this has to do with BITS and not being able to communicate
with the orginal server.

Any ideas on how to resolve this. I'm actually thinking of changing the
SUS server name back to the old name to see if that will kick things.

Please visit the following pertinent newsgroup
news://msnews.microsoft.com/microsof...wareupdatesvcs

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/secu...t/default.aspx

----------------------------------------------------------------------------

"James Bator" wrote:

| OK, in a nutshell :
|
| Had a server named XXXSUS, replaced it with a new server named XXXSUS1
|
| Running SUS in an active directory environment with GPO's controlling
| the updates.
|
| Afer new server brought on line, all GPO's were edited to point clients
| to New server using FQDN in the format HTTP://XXSUS1.XX.XX.XX.
|
| Since that time, there has been absolutely NO client side activity in
| the windows update.log file.
|
| Looking at event viewer, I'm seeing the follow errors on almost all
| randomly selected clients :
|
|
| Event Type: Warning
| Event Source: Automatic Updates
| Event Category: Download
| Event ID: 16
| Date: 1/24/2005
| Time: 12:32:02 PM
| User: N/A
| Computer: XXXX-XXXXXXXX
| Description:
| Unable to connect: Windows is unable to connect to the Automatic Updates
| service and therefore cannot download and install updates according to
| the set schedule. Windows will continue to try to establish a connection.
|
|
|
| I'm assuming this has to do with BITS and not being able to communicate
| with the orginal server.
|
| Any ideas on how to resolve this. I'm actually thinking of changing the
| SUS server name back to the old name to see if that will kick things.