is the domain credential used correct or has the permission to add a computer?

Could be a few things, best way to find out is to have a look in the View Composer Logfiles on the vDesktop and maybe on the vCenter Server.

// Linjo

If domain and View are in different VLAN could you please check the firewall.

Also i hope you are using fqdn of the domain name, and the same name i sresolvable from Connection server, and VC server.

(Remember, View makes domain membeship according to the Domain Name selected in Guest Customization page and not in the sysprep.

For more error checklist refer Common errors with SVI Pools and View Composer

Yes , domain Credentials and correct and its creating a computer account in OU successfully  .

Its not adding the machine to the domain and also the customizing status always remains same after deployment and never completes the task to available

Yes , this feature worked before and all of sudden it Stopped working for any deployments . I tried with different templates and images to check it and its still same issue .

It just stays on customizing

If you look under C:\windows\temp on the VDI machine there will be View composer logs.  These logs might help us figure out what is happening.  

Attached the VMware composer logs and also attempted the steps in this KB article but still no luck .

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102441...

Now I get this error "View Composer agent initialization state error (18): Failed to join the domain (waited 790 seconds)" After Re-compose with the Master image changes to registry as per the link

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102441....

I don't have a clone log file to compare with at the moment but I did see a waiting for Sysprep message.   Are you using quickprep or sysprep?   

Hi,

    Check the following information http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102816...

Hope this information helps you.

Always remember you're unique, just like everyone else

Its resolved , after uninstalling the View agent and tools from the parent machine and rebooted the machine.  Re-installed VMware tools and Agent and re-deployed the linked clones and everything started working.