locked
Server 2016 LTSB 1603 - Update problems after cloning VM RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys,

    i have a problem that my Update Client on a Windows Server 2016 bricks itself after the VM got cloned.

    I have to use the "wuapp_diagNrepair_win10.diagcab" aka Windows Update Troubleshooter to got it back running ...

    Does anyone has the same problem?

    Best regards, Michele

    miki

    Tuesday, March 13, 2018 1:18 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Please delete SUS Client GUID as below,

    a. Stop the automatic service 
    b. Delete the SUSclientID reg key

    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

    c. Restart the automatic service  
    d. Run wuauclt /resetauthorization /detectnow  
    e. Run wuauclt /reportnow

    Please refer below guidance for further troubleshooting,

    https://gallery.technet.microsoft.com/office/Troubleshooting-WSUS-d63da113

    • Marked as answer by M.E.42 Thursday, March 15, 2018 8:55 AM
    Wednesday, March 14, 2018 3:23 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    If that 1 SusClientId didn't fix it, try the following client side script for fixing this (Run from an Admin Cmd Prompt on any affected client):

    net stop bits
net stop wuauserv
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
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
rd /s /q "C:\WINDOWS\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

    The master image should NOT be allowed to check any WSUS server before sysprepping. If it does somehow contact a WSUS Server before sysprepping, you must remove all 4 (if existing) registry entries before sysprepping.

    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    • Marked as answer by M.E.42 Thursday, March 15, 2018 8:55 AM
    Thursday, March 15, 2018 3:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys thank you for your help.

    It was already brick on the template so i've had to use the troubleshooter first and after that the following script to clear the cache:

    net stop wuauserv

net stop cryptSvc
 
net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

    The SUSClient was also a Problem and i had to delete the SUSClientId in the REG. I thought that sysprep would delete that ID to but that was not true. Cause WU Client is an application it gets ignored by sysprep cause this program also delete OS related IDs.

    Problems got solved thanks for your help.

    Best regards, Michele

    miki

    • Marked as answer by M.E.42 Thursday, March 15, 2018 8:55 AM
    Thursday, March 15, 2018 8:55 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Please delete SUS Client GUID as below,

    a. Stop the automatic service 
    b. Delete the SUSclientID reg key

    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

    c. Restart the automatic service  
    d. Run wuauclt /resetauthorization /detectnow  
    e. Run wuauclt /reportnow

    Please refer below guidance for further troubleshooting,

    https://gallery.technet.microsoft.com/office/Troubleshooting-WSUS-d63da113

    • Marked as answer by M.E.42 Thursday, March 15, 2018 8:55 AM
    Wednesday, March 14, 2018 3:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for the fast response.

    I will try that solution but i guess i'll have to do those steps in our w2k16 template to prevent that i have to do this every time a vm gets build from that template.

    Best regards,

    Michele

    miki

    Wednesday, March 14, 2018 7:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    OK. What is the current status of your issue?
    Wednesday, March 14, 2018 7:40 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    If that 1 SusClientId didn't fix it, try the following client side script for fixing this (Run from an Admin Cmd Prompt on any affected client):

    net stop bits
net stop wuauserv
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
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
rd /s /q "C:\WINDOWS\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

    The master image should NOT be allowed to check any WSUS server before sysprepping. If it does somehow contact a WSUS Server before sysprepping, you must remove all 4 (if existing) registry entries before sysprepping.

    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    • Marked as answer by M.E.42 Thursday, March 15, 2018 8:55 AM
    Thursday, March 15, 2018 3:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys thank you for your help.

    It was already brick on the template so i've had to use the troubleshooter first and after that the following script to clear the cache:

    net stop wuauserv

net stop cryptSvc
 
net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

    The SUSClient was also a Problem and i had to delete the SUSClientId in the REG. I thought that sysprep would delete that ID to but that was not true. Cause WU Client is an application it gets ignored by sysprep cause this program also delete OS related IDs.

    Problems got solved thanks for your help.

    Best regards, Michele

    miki

    • Marked as answer by M.E.42 Thursday, March 15, 2018 8:55 AM
    Thursday, March 15, 2018 8:55 AM