View Composer agent initialization state error (18): Failed to join the domain (waited 640 seconds)

[JasonMcElvoy]

Yesterday we started getting messages on several of our View sessions about a domain trust relationship and the View sessions weren't allowed to sign on.  Read through several articles that suggested it might be the computer account password being expired and to do a Recompose to fix.  Before doing a full Recompose, I simply did a Remove on one of the View sessions and let it rebuild and it was then able to connect just fine.  So I Removed another 5 and they all worked as well.  I scheduled a Recompose of the entire pool last night and when I got in this morning I had 19 of the 60 in an error state. 

The error is: View Composer agent initialization state error (18): Failed to join the domain (waited 640 seconds) 
So I found this article online and implemented the suggested resolution http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102816...

After implementing this, I picked 5 of the View sessions that had the error and did a Remove.  3 of the 5 worked but the other 2 still got the same error message.  I signed in to 1 of them and found out it is actually on the domain and has a corresponding AD account.  So the error states it can NOT join the domain and in reality is has in fact already joined the domain.  So I kept doing a Removed and eventually of the 19, 11 are now working fine.  The remaining 8 have been Removed 3 more times and get the same error each time.  Has anyone experienced this before?  If I sign in to the View session, drop it from the domain then rejoin it, will View pick that up and set the View session as Available? 

Agent Version 4.6.0

Windows 7 Parent

Server 2008 R2 View servers

2 ESXi 4.1 hosts

2 VDI storage pools

[Gaurav_Baghla]

1)Could you please check if the version of composer is comaptible with Horizon view Connection server

2)How long are you facing this problem ?Any changes that you can think of ?

3)Could you please have a look at this article

4)Appreciate if you could attach logs from Composer and agent Machine that is failing

http://kb.vmware.com/kb/1027744

[JasonMcElvoy]

Last night I dropped my Pool settings from 60 provisioned sessions down to 2, let View remove the VM's and their AD accounts, then I powered on the Master workstation and dropped it from the domain.  In trying to add it back to the domain I received this error: the following error occurred attempting to join the domain: logon failure the target account name is incorrect.  Googling that led me to doing some additional AD cleanup for the Master workstations AD account.  After that additional cleanup and another reboot on the Master workstation, I was able to create a new snapshot, point the pool at it, and set the pool back to 60 from 2 and all the new sessions worked as they should.  I think there was just something really jacked up with the Master workstations AD account on this one.