+ Post New Thread
Results 1 to 13 of 13
Windows Thread, A most weird WSUS problem in Technical; Never had much of a problem with WSUS until now and this one is really odd. 25 New PCs in ...
  1. #1

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740

    A most weird WSUS problem

    Never had much of a problem with WSUS until now and this one is really odd.
    25 New PCs in our IT Room - all built and ready to go. They all update without any problems from the WSUS server but here is weird point number 1.
    The PCs DO NOT appear in the console !! I have run the usual switches and checked the windowsupdate.log file and they report fine. I have even reset the clients using the:

    wuauclt /resetauthorization /detectnow

    Switch. I have also run a clear up of unwanted updates / computers etc. I have also removed all duplicate entries from DHCP and DNS as of course these new PCs have the same name as the old ones - they have new SIDs. So why do they update from the WSUS server but don't appear ?
    Also weird point number 2 is really weird !! If I run the:

    wuauclt /resetauthorization /detectnow on a client

    Switch, then hit re-fresh, the PC appears !! Hooray, then if you run the same switch on another PC that PC on which you first ran it on disappears and the new PC appears !! And so on !! So all in all I can only get ONE PC out of the 24 to appear in the console !!

  2. #2

    Join Date
    Mar 2007
    Posts
    1,782
    Thank Post
    80
    Thanked 293 Times in 224 Posts
    Rep Power
    86
    forgive the question,but they machines do have seperate sids from each other dont they?

  3. #3

    Join Date
    Jun 2008
    Location
    Essex
    Posts
    47
    Thank Post
    2
    Thanked 17 Times in 15 Posts
    Rep Power
    15
    Have you reset the WSUSID on each machine?

  4. #4

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    http://support.microsoft.com/kb/903262

    Have found this - will give it a bash...

    Code:
    Rem - Batch script to delete duplicate SusClientIDs
    Rem - Implement this script as a "Startup" or "Logon"  script
    Rem - Script creates an output file called %Systemdrive%\SUSClientID.log
    Rem - If the %Systemdrive%\SUSClientID.log is already present, then the script simply exits
    
    @Echo off
    if exist %systemdrive%\SUSClientID.log goto end
    net stop wuauserv
    net stop bits
    reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f  > %systemdrive%\SUSClientID.log 2>&1
    reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f  >> %systemdrive%\SUSClientID.log 2>&1
    reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f  >> %systemdrive%\SUSClientID.log 2>&1
    net start wuauserv
    wuauclt.exe /resetauthorization /detectnow         
    :end
    exit
    Last edited by mattx; 13th August 2009 at 10:02 AM.

  5. #5
    p858snake's Avatar
    Join Date
    Dec 2008
    Location
    Queensland
    Posts
    1,490
    Thank Post
    37
    Thanked 175 Times in 151 Posts
    Blog Entries
    2
    Rep Power
    51
    How did you give them new SIDs? Sysprep or NewSID?

  6. #6

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    Quote Originally Posted by p858snake View Post
    How did you give them new SIDs? Sysprep or NewSID?
    Sysprep - the script works btw - got them all where I want them now !!

  7. #7
    gshaw's Avatar
    Join Date
    Sep 2007
    Location
    Essex
    Posts
    2,662
    Thank Post
    166
    Thanked 220 Times in 203 Posts
    Rep Power
    67
    Yup that reg file is the usual fix as Sysprep doesn't reset the WSUS client ID

  8. #8

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    Quote Originally Posted by gshaw View Post
    Yup that reg file is the usual fix as Sysprep doesn't reset the WSUS client ID
    Now part of my build process......

  9. #9
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,461
    Thank Post
    10
    Thanked 496 Times in 436 Posts
    Rep Power
    113
    Quote Originally Posted by gshaw View Post
    Yup that reg file is the usual fix as Sysprep doesn't reset the WSUS client ID
    Which version of sysperp are you using? I've never had to reset the IDs here.

  10. #10

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    I was using the version that comes with Ghost 8.0 - I have to say this is the first time I have experienced this problem - I have upgraded rooms before with the same name in regards to WSUS and never had a problem - strange why it happened this time round....

  11. #11
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,461
    Thank Post
    10
    Thanked 496 Times in 436 Posts
    Rep Power
    113
    You should be using the Deployment tools from the current service pack on the machine, older versions can be broken by the SP updates.


    Download details: Windows XP Service Pack 3 Deployment Tools

  12. #12

    mattx's Avatar
    Join Date
    Jan 2007
    Posts
    9,240
    Thank Post
    1,058
    Thanked 1,068 Times in 625 Posts
    Rep Power
    740
    Quote Originally Posted by DMcCoy View Post
    You should be using the Deployment tools from the current service pack on the machine, older versions can be broken by the SP updates.


    Download details: Windows XP Service Pack 3 Deployment Tools
    Thanks for the link, the new builds had SP3 streamlined - I'll use this updated version from now on though...

  13. #13
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,461
    Thank Post
    10
    Thanked 496 Times in 436 Posts
    Rep Power
    113
    Quote Originally Posted by mattx View Post
    Thanks for the link, the new builds had SP3 streamlined - I'll use this updated version from now on though...
    It's just an updated sysprep.exe and the tools for sysprep to run - just replace the ones in the sysprep config folders on the ghost server in All users, although I usually run sysprep manually then take an image with ghost.

SHARE:
+ Post New Thread

Similar Threads

  1. [MS Office - 2007] Weird Font Problem
    By Simcfc73 in forum Office Software
    Replies: 1
    Last Post: 27th May 2009, 03:45 PM
  2. Weird smartcache 2 problem.
    By K.C.Leblanc in forum Network and Classroom Management
    Replies: 1
    Last Post: 18th March 2008, 08:40 AM
  3. Weird problem
    By akatuk in forum How do you do....it?
    Replies: 9
    Last Post: 10th October 2007, 08:30 PM
  4. Promethean weird problem
    By sbutterworthtj in forum Windows
    Replies: 6
    Last Post: 19th June 2007, 09:37 PM
  5. Weird AD problem
    By SpuffMonkey in forum Windows
    Replies: 3
    Last Post: 29th March 2006, 10:57 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •