none
Domain SIDs remain unchanged after sysprep

    Question

  • Hi,

    as the tittle the Domain SIDs remain unchanged after using sysprep. the wmic useraccount get name,sid output:

    Administrator      S-1-5-21-1969756259-3681859664-2810091318-500
    Guest            S-1-5-21-1969756259-3681859664-2810091318-501
    user            S-1-5-21-1969756259-3681859664-2810091318-1000

    Administrator    S-1-5-21-1686072512-342896159-184421646-500
    Guest                S-1-5-21-1686072512-342896159-184421646-501
    krbtgt                S-1-5-21-1686072512-342896159-184421646-502
    aska                  S-1-5-21-1686072512-342896159-184421646-1107
    tani                  S-1-5-21-1686072512-342896159-184421646-1109

    After doing the sysprep the local accaunt change the SIN (3 first lines )but for the domain is still the same(5 line at the end)

    Does anyone have this problem and how should i proceed because I have to PC (cloned) and have this problem on WSUS server using only one at time

    Saturday, September 07, 2013 9:49 AM

Answers

All replies

  • how should i proceed because I have to PC (cloned) and have this problem on WSUS server using only one at time

    Sysprep has absolutely nothing to do with WSUS.

    The issue is caused because the machine used to create the image had been updated using the WUAgent, which created a SusClientId, which then got duplicated across all of the clone machines because the master image was not properly prepared.

    See KB903262 for remediation steps.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Saturday, September 07, 2013 6:46 PM
    Moderator
  • Hi,

    Based on my knowledge, domain SID won’t be changed when you run sysprep.

    To solve the duplicate SUSClientID issue, you can refer to the blog below:

    Resolving the duplicate SUSClientID issue, or “Why don’t all my clients show up in the WSUS console?”

    http://blogs.technet.com/b/sus/archive/2009/05/05/resolving-the-duplicate-susclientid-issue-or-why-don-t-all-my-clients-show-up-in-the-wsus-console.aspx

    Hope this helps.

    • Marked as answer by emirjonb Monday, September 09, 2013 7:32 AM
    Monday, September 09, 2013 6:50 AM
    Moderator
  • Thanks for writing

    I have done the updates from windows update and than cloned. After cloning I added the PC to domain and WSUS server. So I don't understand why is generated the same SusClientID from WUAgent ?

    Anyway I found this, and did the job

    "Please delete the "SusClientID" and "SusClientIDValidation" registry values in the key
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate " 

    Thanks

    Monday, September 09, 2013 7:29 AM
  • Thanks for writing

    After sysprep OOBE the SID was changed but didn't help for WSUS problem and than I found a solution like this modifying the register values and did work

    Thanks

    Monday, September 09, 2013 7:32 AM
  • I have done the updates from windows update and than cloned. After cloning I added the PC to domain and WSUS server. So I don't understand why is generated the same SusClientID from WUAgent ?

    Because of the exact order in which you did things.

    1. You updated the master from Windows Update (which generated a SusClientID on the master).
    2. Then you cloned the master (which duplicated the master's SusClientID to each of the clones).

    The missing step is that after updating the master from WU, but before cloning, you need to explicitly delete the SusClientID and SusClientIDValidation from the master system. Then clone. The clones will not have a SusClientID, so will generate their own unique SusClientID on first contact with WU/WSUS.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, September 09, 2013 7:43 PM
    Moderator
  • After sysprep OOBE the SID was changed but didn't help for WSUS problem

    Just to emphasize the point.. .SYSPREP only works on *MACHINE* identifiers.

    The SusClientID is an *APPLICATION* identifier and therefore is not affected by SYSPREP.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, September 09, 2013 7:45 PM
    Moderator
  • Thanks

    Next time when I create a more updated clone

    Tuesday, September 10, 2013 7:10 AM