windows 10 1709 customization sysprep issue

[stephenyu05]

I had windows 10 1709 iso. I created guest VM to use this ISO without additional windows patches to be installed. I cloned the vm which could use vcenter "customization specification" to joint to domain successfully.

So, I used windows 10 vm to install all windows patch (up to April 2018). I cloned the vm again. the vm cannot join to domain.

How can I fix the issue?

[BenFB]

What version of Horizon are you running? For 1709 you need to be on 7.2, 7.3.2 or 7.4.0. For 7.2 and 7.3.2 you need to apply the workaround in KB 51518.

Supported versions of Windows 10 on Horizon Agent Including All VDI Clones (Full Clones, Instant Clo...

Production Support for VMware Horizon 7.4, 7.3.2, and 7.2 with Win 10 1709 Semi-Annual Channel (SAC)...

[surajr04]

Are you able to create a clone of the image Windows 10 Build 1709 using the current sysprep scripts in vCenter directly ( bypassing horizon view). In case if direct cloning of master image using the Sysprep script fails in vCenter, then it is not Horizon View issue. The above need to be investigated from vCenter or Sysprep end.

You can refer to KB VMware Knowledge Base . for Sysprep logs as it will tell you why it failed to join to the domain.

You can also try to join the failed VM manually to Domain and check if it fail or able to join as it will help you to isolate the issue.