none
Issues with Cloning Server 2016 Azure RDSH VM - Failed to Provision - Sysprep Failure. RRS feed

  • Question

  • We have been experiencing issues with cloning our RDSH servers, which are Azure hosted VMs running Windows Server 2016 Standard. 

    When attempting to clone the VMs we use DSC scripts which use the following process.

    - Take a snapshot of the source VM.
    - Build a new VM using the new OS disk.
    - Runs sysprep on this VM.
    - Creates an image of this VM.
    - Deploys the new servers(s) (clones) from this image.  

    However, when attempting to do this the process fails, eventually producing an error message stating that the server failed to be provisioned, or "The resource operation completed with terminal provisioning state 'Failed'."

    When logging on to the clone VM in these cases, it appears as though the issue is likely that sysprep failed either on this VM or on the original VM that the image was created from, as it still has the original source server's hostname, and all registry keys normally removed by Sysprep are still present.  Additionally, attempting to manually run sysprep on the cloned VM fails (sysprep log will be included below).

    We have attempted more troubleshooting steps with this than can be documented in this note, but many of the key steps that we have tried include:

    - Set GeneralizedState value to 7.  
    - Reinstalled MSTDC service.
    - Verified existence of the following registry keys.
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\StreamProvider] “LastFullPayloadTime”=dword:00000000
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\StreamProvider] “LastTargetUri”=dword:00000000
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\SoftwareInventoryLogging] “Identity”=dword:00000000
    - Removed all cached profiles and registry keys.  
    - Created separate administrator account, after removing all other user profiles, and attempted running sysprep from this account.  
    - Removed suspect third party applications.  
    - Ran the following to remove the builtin Windows apps, although this just returns errors.
       Get-AppxPackage -AllUsers | Remove-AppxPackage
    - Set the "Start" value in the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tiledatamodelsvc] registry key to 4, essentially disabling the TileDataServiceModel service, and rebooted the server.
    - Accessed the registry and system drive admin share remotely, to ensure that no profiles whatsoever existed on the server.  
    - Tried both hot and cold cloning.  

    Has anyone had similar trouble with cloning Windows Server 2016 RDSH servers, either in Azure or in general?

    Syspreperrr Log

    2017-08-16 08:36:55, Error                 SYSPRP setupdigetclassdevs failed with error 0
    2018-02-21 23:09:34, Error                 SYSPRP setupdigetclassdevs failed with error 0
    2018-12-11 23:07:25, Error                 SYSPRP setupdigetclassdevs failed with error 0
    2018-12-17 19:39:24, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2018-12-17 19:39:24, Error                 SYSPRP WinMain:Hit failure while processing sysprep re-specialize internal providers; hr = 0x8007001f
    2018-12-17 19:46:42, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2018-12-17 19:46:42, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f

    Tuesday, January 8, 2019 10:35 PM

All replies