$VhdxPath = "V:\Hyper-V\Virtual Hard Disks\ $VMName.vhdx " # some definitions for Network and VM storage path If (( $CPUCount = Read-Host –Prompt "CPU count? ") -eq " ") $VMName = Read-Host –Prompt 'Enter VM name '
# ask some parameters like VM name, CPU count or latest Win10 or Insider
TESTOUT LAB BOOTORDER WINDOWS
I use Hyper-V native VM Connect and not the “ Enhanced Session Mode“, as this blocks the capability to test Windows Hello for Business within my VM, I know I give up convenience in regards of copy paste, but I can easily live with that, as I have other options which are for me sufficient enough:.All scripts can be found on my GitHub account here: Now when it comes to work with the VMs I follow a few simple rules and have a few support utilities and scripts always available. The setup I described above, brings a fair amount of power and throughput to work with 10 devices in parallel. vhdx files can be stored very efficiently, as they all have a large portion of the same data in it (around 80-95% space saving for this data type). An important fact is to make sure to enable Data Deduplication on your VM data drive to store the VM data files ( vhdx) efficiently. This post is not about choosing the best hardware setup. Make sure to have a good SSD to provide good throughput especially when testing all these enrollments this is the best way to speed things up. I’m using a Server with an Intel i7 processor with 4 Cores and 64 GB of memory. First of all you need a performant Hyper-V Server with enough memory to support your test server/devices.
TESTOUT LAB BOOTORDER HOW TO
For this I will share my approach how to work in my lab setup. It is absolutely necessary to have a good lab setup to test all these new features in a save way. As a lot of my blog readers probably know :-), I’m working a lot with Microsoft Endpoint Manager – Intune and testing a lot of things in the Modern Management approach with Windows 10.
0 kommentar(er)
