+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 23 of 23
Windows Thread, WSUS Question in Technical; Doesn't work in what way? It doesn't generate any visual output but it does reset the WSUSSID on the machine ...
  1. #16

    Join Date
    Jun 2008
    Location
    Essex
    Posts
    47
    Thank Post
    2
    Thanked 17 Times in 15 Posts
    Rep Power
    16
    Doesn't work in what way?

    It doesn't generate any visual output but it does reset the WSUSSID on the machine and force the machine to contact the WSUS server

  2. #17
    Osprey's Avatar
    Join Date
    Mar 2007
    Location
    West Yorkshire
    Posts
    65
    Thank Post
    0
    Thanked 6 Times in 4 Posts
    Rep Power
    17
    The article says "This symptom only occurs if the image was not created by Sysprep or other unique SID-generating technology"

    We have regularly made images which we have used to re-image workstations using either sysprep or Ghostwalker and the machines appear in WSUS without problem. We did once, accidentally not do this and at that point only one workstation appeared in the WSUS console. We used newsid on them and they started to appear in the console.

  3. #18

    Join Date
    Jun 2008
    Location
    Essex
    Posts
    47
    Thank Post
    2
    Thanked 17 Times in 15 Posts
    Rep Power
    16
    That article was written before Microsoft started playing with the WSUS client but it does describe the problem.

    Sysprep will not reset the WSUS client ID.

    Just Google 'sysprep wsus3'

    We are now working on using wsus to update our images and then deleting the WSUS registry keys before using sysprep.

    Hopefully it will ease our summer re-imaging marathon!

  4. #19


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,715
    Thank Post
    288
    Thanked 788 Times in 615 Posts
    Rep Power
    226
    Quote Originally Posted by greatone View Post
    Doesn't work in what way?

    It doesn't generate any visual output but it does reset the WSUSSID on the machine and force the machine to contact the WSUS server
    I suspect it's the typo in the reg key, you have a space between i and n:

    sRegKey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Wi ndowsUpdate"

    Edit: (or rather, the board displays a space, despite there not being one in the line I typed above)

  5. #20

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,373
    Thank Post
    906
    Thanked 1,811 Times in 1,559 Posts
    Blog Entries
    12
    Rep Power
    468
    Quote Originally Posted by greatone View Post
    Doesn't work in what way?

    It doesn't generate any visual output but it does reset the WSUSSID on the machine and force the machine to contact the WSUS server
    I have but an echo in so I know the script has finished but the clients I run it on have still not reported back to wsus.

  6. #21

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,373
    Thank Post
    906
    Thanked 1,811 Times in 1,559 Posts
    Blog Entries
    12
    Rep Power
    468
    Quote Originally Posted by greatone View Post
    Thanks - I had been looking for that but couldn't find it!

    Here is the script to reset those keys for those that are interested:

    Set oShell = CreateObject("WScript.Shell")

    sRegKey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Wi ndowsUpdate"

    ' suppress error in case values does not exist
    On Error Resume Next

    ' check for marker
    sIDDeleted = oShell.RegRead( sRegKey & "\IDDeleted")

    ' to be sure values is only deleted once, test on marker
    If sIDDeleted <> "yes" Then
    ' delete values
    oShell.RegDelete sRegKey & "\AccountDomainSid"
    oShell.RegDelete sRegKey & "\PingID"
    oShell.RegDelete sRegKey & "\SusClientId"

    ' Stop and start the Automatic updates service
    oShell.Run "%SystemRoot%\system32\net.exe stop wuauserv", 0, True
    oShell.Run "%SystemRoot%\system32\net.exe start wuauserv", 0, True

    ' Run wuauclt.exe with resetauthorization
    sCmd = "%SystemRoot%\system32\wuauclt.exe /resetauthorization /detectnow"
    oShell.Run sCmd, 0, True

    ' create marker
    oShell.RegWrite sRegKey & "\IDDeleted", "yes"
    End If


    Copy the script into notepad

    Save as text file then rename to .vbs

    Double click the file and it will reset the WSUS SID etc.
    NB It can only be run once on each machine as it sets a marker to say that it has been run.
    Sorry to pester & drag up the old post, the script did work just a typo. If needed how would i remove that marker please?

    Thanks

    Z

  7. #22

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,373
    Thank Post
    906
    Thanked 1,811 Times in 1,559 Posts
    Blog Entries
    12
    Rep Power
    468
    Hi there

    i have found the marker but what is the purpose of it please?

    thanks

  8. #23

    Join Date
    Jun 2006
    Location
    Belfast, N\'Ireland
    Posts
    190
    Thank Post
    10
    Thanked 9 Times in 7 Posts
    Rep Power
    19
    The author seems to have written the script with the intention that it might be put in a user logon or workstation logon script. The marker is to prevent the SID being regenerated every time the mahcine restarts.

    ie. If the mahcine already has the marker SID wont be regenerated the script will just finish without making changes.



SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Wsus
    By ricki in forum Wireless Networks
    Replies: 1
    Last Post: 19th June 2008, 09:37 AM
  2. WSUS - small question regarding GPO's
    By DanW in forum Windows
    Replies: 4
    Last Post: 10th April 2008, 03:12 PM
  3. Replies: 3
    Last Post: 21st February 2008, 09:50 AM
  4. Quick WSUS Question
    By mattx in forum Windows
    Replies: 3
    Last Post: 10th May 2007, 04:14 PM
  5. Replies: 1
    Last Post: 8th November 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
  •