#Vmware workstation for learning lab how to#
#Vmware workstation for learning lab install#
#Vmware workstation for learning lab windows 10#
#Vmware workstation for learning lab Pc#

Verify that there are no users logged in to any published resource.įrom the Connection Server, log in to the Horizon 7 Console. Delete any remaining Horizon-related Lease records from DHCP.Remove any remaining Horizon-related computer accounts in Active Directory.Revoke any issued certificates for any Horizon-related computer accounts from the domain CA.Remove the DEM and Horizon agents from any physical computers.Remove any Organizational Units created.Remove the DEM Configuration and Profile shares and folder trees.Remove the Parent VMs, Replica VMs, Internal Templates, Sync VMs, and the Folders created by the Instant Clone process.Verify that there are no users logged in to any published resource.Others may prefer their order, but I am sure we all accomplish the same end goal, returning the lab to the pre-Horizon 7.12 state.Īfter the testing of Horizon 7.12 is over, you may want to remove all the components, pieces, and parts. After completing your Horizon testing, there is a step-by-step process to undo all the work done in Chapters 1 through 15. So if anyone is looking to build a nested LAB on Ryzen -> go with bare metal ESXi.Īfter that you can enable GPU pass-through (AMD RX570 in my case) to a Windows VM along with a USB controller pass-through (I used a dedicated PCIe controller) for the mouse and keyboard and if everything works as intended, you can use the VM as a standard workstation and even game on it! Not suitable for professional gamers as there is some input lag, but for the occasional player it’s just fine.Whew, that was a lot to cover in over 400 screenshots and 450 pages. I've successfully tested this with every setup that I had on my hand.

On the other hand, running an ESXi (6.7 U1) on bare metal does the trick, and nested VMs run without issues. Thus my conclusion that this will not work until MS enables this feature. The issues were the same or very similar on every system. The MBs were from Asus, Asrock and Gigabyte. I've even tested this out on a older AMD Bulldozer platform.

#Vmware workstation for learning lab Pc#

The above was tested on my home PC and a couple (7 to be precise) of other 1st gen. Windows simply doesn't allow nested VMs running on AMD CPUs (something with errors in instruction forwarding). Doesn't matter if the virtualization solution is Hyper-V, VMware Workstation, Virtual Box (the 3 I tried).

#Vmware workstation for learning lab windows 10#

Nested virtualization on AMD Ryzen (1st gen) on Windows 10 is not supported as of now. Is this some limitation of the architecture, or is nested virtualization simply not allowed on Ryzen CPUs? Any way arround it, other than selling this setup and buying a new one? I have another Intel based PC at home (old i5) and that one works OK and is able to run nested virtualization without any problem (same SW setup). I tried a couple of UEFI version on the MB, different OS versions and Workstation versions, different OS iso files, but the results are still the same. I tried importing a VM from template to the virtual ESX, but this has the same results. Sometimes it goes through boot OK and starts to load the iso, but then the whole virtual ESX crashes. But when I create a VM on top of this virtual ESX when the VM starts and after it tries to boot, the VM crashes and just powers off.

#Vmware workstation for learning lab install#

I am able to install a virtual ESXi host (6.5U2) on top of the setup and it runs OK.

#Vmware workstation for learning lab how to#

Hello to all, I'm trying to build my own home lab for VMware solution testing, mainly to learn about the technologies and how to get arround them (install, configure, manage kind of stuff).ĬPU: AMD Ryzen 1700X, MB: Asrock X370 Taichi UEFI 4.80, 64 GB RAM, Windows 10 Pro with Workstation 14 pro installed atop of it (latest patches on both OS and workstation).