nic disappears from virtual desktop
i have an issue building a horizon view (6.2) pool on vsphere 6
the vm (windows 7) is built with the horizon agent and vmware tools installed. pool created using the last snapshot
in the view admin, i can see it provisioning and customizing but eventually ends in error stating there is no communication between the client and connection server
if i login to it, i see the nic (vmxnet3) is gone; no longer in device manager
i can remove from the guest and add again and immediately starts working and view administrator says the guest is available
i have tried disabling hot plug but no difference. another articled referred to a microsoft patch but the files in there are older than what is already on the system. i tested a manual clone and that had no issues. not sure why this isn't working with horizon or what else to try
the vm (windows 7) is built with the horizon agent and vmware tools installed. pool created using the last snapshot
in the view admin, i can see it provisioning and customizing but eventually ends in error stating there is no communication between the client and connection server
if i login to it, i see the nic (vmxnet3) is gone; no longer in device manager
i can remove from the guest and add again and immediately starts working and view administrator says the guest is available
i have tried disabling hot plug but no difference. another articled referred to a microsoft patch but the files in there are older than what is already on the system. i tested a manual clone and that had no issues. not sure why this isn't working with horizon or what else to try
FOX
Do you have the latest version of VMware tools installed on it?
ASKER
i stated the tools are installed
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i actually changed to using that adapter last week but didn't have time to update this
seems to work better; hopefully there won't be a reason to switch back
it's an acceptable workaround for the time being though doesn't explain why the other adapter disappears
seems to work better; hopefully there won't be a reason to switch back
it's an acceptable workaround for the time being though doesn't explain why the other adapter disappears