Pointing clients to new SUS server

Discussion in 'Windows Update' started by James Bator, Jan 28, 2005.

  1. James Bator

    James Bator Guest

    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.
     
    James Bator, Jan 28, 2005
    #1
    1. Advertisements

  2. Please visit the following pertinent newsgroup
    news://msnews.microsoft.com/microsoft.public.softwareupdatesvcs

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

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

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

    :

    | 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.
     
    Carey Frisch [MVP], Jan 29, 2005
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.