Error Publishing the Master Image

[chrischay]

Hi,

I have an issue where whenever I publish a new master image it will fail. I noticed that it will try to create the cp-template, but eventually it will power it off and then delete. Also, sometimes it will reach to the point that it will create the cp-replica but then it will power it off and then delete.

My Horizon is 2312, DEM is 2312 and vSphere is v7.0.3.

I tried to use both Windows 10 and Windows 11 and all showing the same issues.

Any idea?

I attach the error message.

 

Thanks for any inputs.

 

[Victor León]

Hello Chris, 

The error message 'AGENT_CUSTOMIZATION_FAULT' indicates that it failed during the customization of the guest OS which consist in joining the machine to the domain, create the AD object, generating SIDs and network settings. 

The customization process happens in the cp-template internal vm. You need to enable ClonePrep debug mode or the cp-template vm will be deleted upon failure, this is expected bahavior. 
Troubleshooting Instant Clones in the Internal VM Debug Mode

Agent logs from the cp-template are helpful to try identify the issue. I would check debug/netlogon/netsetup  log files to know more why it failed. 

Additionally, I would check the list of the domain controllers available for Horizon cloneprep customization. It is located in the krb5.conf file of each CS. Check> https://kb.omnissa.com/s/article/2147129 Note: There are 4 methods, try each one and test deploying new vms,  to make sure IC attempt to connect the right DCs. If the old/decommissioned dcs are listed, modify accordingly. 
 

 

Edited November 29 by Victor León

[GoShen]

Hi Victor, could it be the password to the account used to add to the domain changed that would cause this? 

[Victor León]

On 11/30/2024 at 12:03 AM, GoShen said:

Hi Victor, could it be the password to the account used to add to the domain changed that would cause this? 

Yes. 

[Ivan de Mes]

An additional log file that may be useful when troubleshooting domain (join) issues, when "internal VM debug mode" is enabled is:

%windir%\system32\NetSetup.LOG

You may also try to join the domain using the default OU (CN=Computers) or join manually (via GUI) to rule out incorrect credentials or incorrect permissions on OU(s).

Edited December 3 by Ivan de Mes