I'm currently evaluating View 4.6 on top of our vSphere 4.1 Update 1 environment.
My problem relates to getting DNS set properly for the ethernet adapters in linked clones. DHCP currently hands out an external DNS service, not our internal Active Directory which has the records for our View Connection server and AD DC's.
I set the DNS statically on the adapter in the parent image, but it appears that this NIC is being removed and replaced when linked clones are deployed because the adapters in the linked clones have the label "Local Area Connection 2".
I tried adding a post-synchronization QuickPrep script to do this. It points to a .bat file with the two lines:
netsh interface ip set dns "Local Area Connection 2" static <AD DC 1 ip>
netsh interface ip add dns "Local Area Connection 2" <AD DC 2 ip> index=2
This does not however seem to have any effect, or it is being overwritten by DHCP when the interface card comes up.
To fix the problem of finding our View connection server, I added a static host entry to the parent image. Now when I create the pool, it fails at the Customizing stage with the error: View Composer agent initialization state error (18): Failed to join the domain (waited 730 seconds)
I understand it can't find my DCs, and I don't think I can remedy this by putting entries in the hosts file since the machine still wouldn't know that the hosts specified there are DCs to be used to join the domain.
How can I set the proper DNS automatically after the linked clones are deployed and get their initial DNS addresses from DHCP?
Cheers