View registers different hostname in AD

[KWKirchner]

We are running Horizon v5.3 in a vSphere 5.5 environment. I have noticed lately that when I build a large pool, sometimes the host names registered in AD DNS do not match the View generated names on the VM. We are using linked clones with a delete on logoff, no persistent disk configuration.  What components are involved in the name passing? Is it between the Composer and the View agent on the VM? I am not sure how this could be getting screwed up so intermittently.

[mittim12]

Can you duplicate it if you scale back the size of the pool being reprovisoned?     How recompose options are happening at the same time?

[KWKirchner]

It happens in a pool with as few as 10 desktops in it.

 

[Gaurav_Baghla]

How many Connection servers do you have ????????? If you have multiple Connection servers check in the events if there is a replication failure issues.

[KWKirchner]

We have 2 connection servers and 1 composer. There are no replication failures in the vCenter logs.

[Rorus]

You won't see ADAM replication issues in the vCenter logs, you'll have to run a repadmin command on the View connection servers as per this KB: http://kb.vmware.com/kb/2014488 to see if thats the issue.

[KWKirchner]

Thank you for that. I checked both connection servers and the output of the command indicates that the last attempt on both was successful.

[KWKirchner · Accepted solution]

This problem eventually went away for us. I believe View 5.3.4 was ok and so far 6.1 also appears to not have this issue. I am not 100% sure it was a Horizon problem, but that seems most likely.