Click on the VM you would like to revert to an old (previous) state.
– Under the Checkpoint pane,
– Select the checkpoint you would like to restore (revert)
– Right-click on it and select Apply

Next, the apply dialog box appears,
– Click on apply.

When this is applied, this will turn off (shutdown) the VM.
– Click o start to start the VM and
-Click on connect to open a session (connection) to the VM

The VM will reboot and revert to the desired state you want it (have selected).

When prompted with this error as shown below, it could mean different things.

In my case, the WDS service were not running. a simple restart of the service solved the issue.

When prompted with this error as shown below, kindly follow the possible solutions to have this resolved.

Found this workaround
– From the VM itself, you can shutdown the VM or
– Use the turn off the feature in hyper-v works.

When prompted with this error “The Virtual Machine Management service encountered an error while configuring the hard disk on a virtual machine”

Solution: This is because the system failed to create a new hard disk file of the same name on the same path.
– Locate where the VHDX files are stored and deleted them.
– And then try to create a new Virtual Machine (VM).

To boot a virtual machine (VM) using PXE boot, the VM has to support an emulated Legacy Network Adapter. Follow the steps below to perform this.

– Shut down or turn off the virtual machine.
– Edit the settings of the virtual machine.
– Browse to Add Hardware, select Legacy Network Adapter, and click Add.
– Click OK to save your changes.

Now the virtual machine is PXE capable, with the lower performing Legacy Network Adapter.

Follow up with other manual steps

Add the legacy network adapter
– Click on Add

Click Expand the legacy Network Adapter recently added
– Enter the Mac Address (Depending on your environment, you have to set a Static MAC address that will enable the VM search for the WDS server or else it will fail)

– Click on the Next, click on the legacy Network adapter and
– under the virtual switch, select the right network adapter

Lastly, ensure that the client boots first using the Legacy Network Adapter. Just select the Legacy Network Adapter and move it to the top using the buttons.

Start your Virtual Machine, and now PXE boot should function correctly 

Here is the result below of a successful deployment.

A Hyper-V Generation 2 VM is similar to a workstation running UEFI workstation and as such cannot communicate with legacy PXE, but with UEFI boot images.

A VM configured with UEFI will use bootx64wdsmgfw.efi on the WDS server when starting the boot process while a legacy boot will use bootx64wdsnbp.com.

If your network is configured to deploy boot images using legacy methods, this will require you to configure the hardware of the virtual machine. See the link for how this is done. https://techdirectarchive.com/2020/01/19/how-to-setup-a-vm-via-pxe-boot-on-a-generation-1-vm-hyper-v/

Here are the steps for hosting a website in Azure.

Open the Azure Market Place Window

Type WordPress and this will display all WordPress resources

Select one and create

Next, you’re presented several options to configure your deployment. Enter the following information.

Selected Database is my SQL In-App, under the App Service Plan and Location

Click on Ok

– Click on apply
– Next Click on create. And this will be validated and if everything is fine. The WebApp will be created.

– To see the status of this WebApp, click on the notification bell (menu) and the progress will be displayed.

Note: The status changes to a green check as each component in the deployment completes.

You can pin this to the bar or click go-to resources.

Access the URL and it will prompt you to install WordPress and proceed with your customization of WordPress  in Azure.