Preboot execution environment (commonly known as PXE) is used to boot a device or virtual machine over a network. You can use PXE to achieve the following scenarios and this is used to remotely install a guest operating system over a network without needing the operating system installation media.
Hyper-V currently has two generations of VM hardware which are; – Generation 1: These VMs has a legacy version of Hyper-V, and has a little bit of overhead when it comes to using to PXE boot because it uses the legacy BIOS, while – Generation 2: Hyper-V machine is a UEFI-based VMs.
Note: A machine configured with UEFI will use bootx64wdsmgfw.efi on the WDS server when starting the boot. A legacy boot will use bootx64wdsnbp.com.
The generation of the Hyper-V virtual machine matters, because PXE uses different boot files depending on if the machine boots either using Legacy BIOS or UEFI. It is recommended to use Generation 2 VMs and if you do not feel the need to, this could be because you have not yet enabled UEFI in your environment.
What does the term scaling up and scaling out mean?
Scaling up, or vertical scaling means to increase the memory, storage, or compute power on an existing virtual machine. For example, you can add additional memory to a web or database server to make it run faster. The reverse is referred to as Scaling down.
Scaling out, or horizontal scaling means to add extra virtual machines to power your application. For example, you might create many virtual machines configured in exactly the same way and use a load balancer to distribute work across them.
Note: The Cloud is elastic and scaling up and down is possible.
To Scale Up, that is to increase the memory, storage, or compute power on an existing virtual machine, follow these steps below.
To Scale-Out which means to means to add additional virtual machines to power your application. Follow these steps.
– Click on Scale-Out (App Service Plan) under settings – Click on the scale Out (App Service plan as shown below) and follow the steps
Part A – Infrastructural Requirements for deploying and testing Pass-Through Authentication (PTA)
Created four VMs in Hyper-V Server
Two (2) Windows10 clients for testing
1. Assign memory to easy VM of 4096MB 2. Assigned Virtual Hard Disk Size of 100 GB 3. Installed Operating System “Windows Server 2019 Standard (desktop Experience) and Windows 10 Enterprise for testing.
Part B – Infrastructural Requirements for deploying and testing AD FS
Created five (5) VMs in Hyper-V Server
AzureADFS (for ADFS testing only)
Two (2) Windows10 client for testing
1. Assign memory to easy VM of 4096 MB 2. Assigned Virtual Hard Disk Size of 100GB 3. Installed Operating System “Windows Server 2019 Standard (desktop Experience) and Windows 10 Enterprise for testing.
In this project, I will be setting up two (2) test Domain Controllers (Dc), Windows 10 PCs for the test and ADFS Server to ensure users are authenticated on Premise.
VMs Setup in Hyper-V environment – Click on New under Actions on the Hyper-V Manager window
– This will open the window below
– Click on next and specify the VM name as shown below
– Under the Specify Generation, Select generation 2 because it provides better virtualization features etc., as shown below
– Under Assign Memory, enter your desired memory
Note: You can decide to also assign Dynamic Memory for this virtual machine. Under Configure Networking, select the right network adapter. This depends if you also want the internet to connect or just want for the VMs to be able to communicate with each other.
From the drop-down menu, select the right network adapter. Note: You can decide to leave it as not connected
– Under “Connect Virtual Hard Disk”, enter your desired size in GB and click on next.
– Under the installation option, select install an operating system from a bootable image file and browse to it.
– Now finish the New Virtual Machine Wizard
– Now the virtual machine creation is complete.
Part C – Continue with the Operating System Installation – This will display the VM in the list of Virtual Machines as shown below – Right-click on the created VM
Note: Only follow this step if you wish to use a static ACA Address, otherwise go straight and “Connect” to the server using the next step below.
Click on settings, locate the Network Adapter and expand it and click on the Advanced features.
Here you can select static and enter the MAC Address. Finally, click on Apply and Ok.
Click on connect (by right-clicking on the VM)
– Click on start and select any key to boot as shown below
– This will lunch the Windows setup window
– Follow – This will open the menu showing that status of “Installing Windows”
– When this finishes, it will prompt you to enter the Administrator Password as shown below.
Part D:Configure Networking and Other Server Basic Setup – Open the Server Manager Note: This opens automatically most times.
– Set the IP parameters (Static) Note: Based on your need, this could also be dynamic if you have a DHCP Server. – Set the Server name