instant clone agent initialization state error (26)

[nielsliao]

After I composed new desktop pool,
This error show up at some desktops,
and those desktops with this error cannot be used.

Google cannot find any error code information.

[orgilplus]

Did you join domain on original image?

[nielsliao]

Joined by DHCP.

[LGabutti]

I have the same problem and I can't find the error code 26 anywhere.

I'm going to generate a support case to see if I can solve it.

[cperryCocoa]

Same error here as well... been dealing with it for a couple of weeks.  Work around of removing, resetting, or recovering the clones usually will get provisioned, but requires someone to be regularly watching it.  I have a case open with VMware, but so far no resolve, as the issue comes back just when you think it was fixed.  Logs haven't been very helpful either.  Does anyone know if there is knowledge base article that goes into these codes more in detail? 

[nielsliao]

I also opened a support case to VMware.
They recommend us to review the pae-AdDomainControllers Config in the Adam DB.
In our case, because we just create some new AD servers,
and the version is 2019 different from the old servers like 2012 or 2008,
maybe the connection from connection server to those new domain controller got some trouble.
After we removed the new servers from pae-AdDomainControllers, the problem fixed.

Deployment of instant-clone desktop pools fails after the successful cloning of the parent virtual machine (2147129)
https://kb.vmware.com/s/article/2147129

[nielsliao]

You can check the logs in the problem VDI desktop at this location.
C:\ProgramData\VMware\VDM\logs
Search the domain name in the log file (log-YYYY-MM-DD).
Find out which domain controller makes this problem,
then remove it from pae-AdDomainControllers.