topic Re: Linux Automated full clone: Error during Provisioning class com.vmware.vim25.CustomizationLinuxP in Horizon for Linux

Linux Automated full clone: Error during Provisioning class com.vmware.vim25.CustomizationLinuxPrep

vybihal — Wed, 26 Jul 2023 09:23:39 GMT

Hi everyone, I am trying to create Automated Full Clone desktop pool using RHEL8.

After creating the pool, this error is shown in Horizon admin interface:

[07/26/2023, 10:54 AM] Error during Provisioning class com.vmware.vim25.CustomizationLinuxPrep cannot be cast to class com.vmware.vim25.CustomizationSysprep (com.vmware.vim25.CustomizationLinuxPrep and com.vmware.vim25.CustomizationSysprep are in unnamed module of loader java.net.URLClassLoader @6fa8ac93)

I have verified that the Customization Specification works fine when creating new VM from the same Template in vCenter. Maybe anybody have an idea what is going on?

Horizon 8.10.0 build - 21972440 Version 2306

Re: Linux Automated full clone: Error during Provisioning class com.vmware.vim25.CustomizationLinuxP

JrcLsaTeam — Thu, 27 Jul 2023 13:21:43 GMT

We have the same problem.

The template and Customization Specification work fine in another workload, I tried both duplicating (and editing) the existing Customization Specification and creating a new one

The vcenter version is for all workloads 7.0.3 instead the Horizon version on which we have the problem is 8.10.0 build - 21972440 Version 2306

Re: Linux Automated full clone: Error during Provisioning class com.vmware.vim25.CustomizationLinuxP

vybihal — Thu, 27 Jul 2023 14:54:42 GMT

I have figured out that this is happening (on two separate installs) when you create new pool and you check the "Select AD Container from Domain Accounts" box... Once you check it, you can not deselect it using edit button.

My guess is that this part is for Sysprep or linked clones only and does not apply to full clones. When leaving it unchecked it works - but ofcourse I have to handle domain rejoin using RunOnceScript= then. Which is shame when it works for instant clones I see no obstacle why it could not work for full clones as well. The machine account is properly created in AD, and agent could easily use offlinejoin as it does with linked clones. Or am I missing something?