My Customer is trying to enable Hyper-V on a Windows 10 workstation. We have a requirement for some of our call-center support staff that they need to troubleshoot varying workstation operating systems. So to accomplish this, we enable Hyper-V and load a Windows7 or other OS to work off of.
Issue is that:
As soon as we install Hyper-V on my Windows 10 workstation, all of posture checks fail immediately. Also it seems that the NAM no longer recognizes the local interface once you have a vswitch mapped to it.
Before we even load another OS, just enabling Hyper-V all of the posture checks that were working for the host workstation now fail.
Customer Deployment:
- ESXi running ISE version 2.2 Patch 4
- The ISE servers are running on VM’s but the Windows 10 workstations are physical laptops trying to run Hyper-V.
- Use NAM (4.5.02033) and ISE posture on all of our workstations.
- EAP-FAST (EAP-MSCHAPv2,EAP-TLS)
Is there any workaround that can be implemented? I see that the Nexus1000v is setup for this but it only works with Windows 2012.
