none
Does sysprep /generalize /oobe reset also the WSUS-SID? RRS feed

  • 問題

  • Hi,

    my question as written in title.

    Does sysprep /generalize /oobe reset also the WSUS-SID?

    I sysprepped a cloned Windows Server 2008R2 but it seems as the WSUS-ID is still similar to the existing old server. I recognize it when searching for the old servername in my WSUS-MMC. It is disappeared... It was replaced with the new Server it seems. If i search manually for Updates on my old system i find again the old system in WSUS-MMC but the new cloned server-entry disappears...

    Kind regards

    philipp

    2019年8月28日 上午 11:25

解答

  • Hi,

    please take a look into the following article for detailed deep dive information:

    https://blogs.technet.microsoft.com/markrussinovich/2009/11/03/the-machine-sid-duplication-myth-and-why-sysprep-matters/

    "..Note that Sysprep resets other machine-specific state that, if duplicated, can cause problems for certain applications like Windows Server Update Services (WSUS), so Microsoft’s support policy will still require cloned systems to be made unique with Sysprep.."

    To check if the WSUS-ID is equal, you can take a look into the following Reg-Key:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SUSClientID

    Further you can manually reset your WSUS ID (e.g. in case of Troubleshooting) with the following steps:

    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f

    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f
    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f


    net stop wuauserv
    net start wuauserv
    wuauclt /resetauthorization /detectnow

    regards, pat

    • 已提議為解答 marc-sysadmn 2019年8月28日 下午 02:08
    • 已標示為解答 P4il1pp 2019年8月28日 下午 02:10
    2019年8月28日 下午 12:11

所有回覆

  • Generalize sollte eigentlich alle SID löschen
    2019年8月28日 上午 11:49
  • Hi,

    please take a look into the following article for detailed deep dive information:

    https://blogs.technet.microsoft.com/markrussinovich/2009/11/03/the-machine-sid-duplication-myth-and-why-sysprep-matters/

    "..Note that Sysprep resets other machine-specific state that, if duplicated, can cause problems for certain applications like Windows Server Update Services (WSUS), so Microsoft’s support policy will still require cloned systems to be made unique with Sysprep.."

    To check if the WSUS-ID is equal, you can take a look into the following Reg-Key:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SUSClientID

    Further you can manually reset your WSUS ID (e.g. in case of Troubleshooting) with the following steps:

    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f

    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f
    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f


    net stop wuauserv
    net start wuauserv
    wuauclt /resetauthorization /detectnow

    regards, pat

    • 已提議為解答 marc-sysadmn 2019年8月28日 下午 02:08
    • 已標示為解答 P4il1pp 2019年8月28日 下午 02:10
    2019年8月28日 下午 12:11
  • Hello/ Hallo P4il1pp, Pat_306,

    As this is a German forum I would kindly ask you to either translate your Post in German or to post it again on the English Forum.

    Da wir uns in einem deutschsprachigen Forum befinden, würde ich Sie gerne bitten wollen, dass Sie entweder alle Ihre Beiträge ins Deutsche übersetzen oder die Thematik erneut im englischsprachigen Forum veröffentlichen.

    Best Regards/ Mit freundlichen Grüßen,

    Mihaela

    Bitte haben Sie Verständnis dafür, dass im Rahmen dieses Forums, welches auf dem Community-Prinzip „IT-Pros helfen IT-Pros“ beruht, kein technischer Support geleistet werden kann oder sonst welche garantierten Maßnahmen seitens Microsoft zugesichert werden können.

    2019年8月28日 下午 01:24
    版主