Child pages
  • Setting up a PXE image in a Hyper-V virtual session
Skip to end of metadata
Go to start of metadata

Overview

These instructions show how to set up a Hyper-V virtual session to allow a PXE-boot and imaging from SCCM.

BEFORE YOU BEGIN

  1. You may want to increase the allowed number of MAC addresses on your port in Switch Management.  Creating more virtual sessions than your port is allocated for may shut off your port.

  2. Make sure your BIOS has Virtualization Support enabled:

    1. DELL BIOS:

      1. Check Virtualization

      2. Check VT for Direct I/O

    2. HP BIOS: In ADVANCED > SYSTEM OPTIONS:

      1. Check Virtualization Technology (VTx)

      2. Check Virtualization Technology for Directed I/O (VTd)

  3. Enable Hyper-V in Windows 10:

    1. Click START
    2. Type Turn Windows Features On or Off
    3. Check ALL Hyper-V check boxes
    4. Reboot

STEPS

Once Hyper-V has been enabled on the computer, run Hyper-V Manager (AS AN ADMIN!), right-click your physical computer in the upper-left pane and click New > Virtual Machine.  If you don't see a physical computer name, you probably did not run Hyper-V Manager as an admin.



Specify a name and a file location > NEXT


Select Generation 1 > NEXT


Assign Memory > Allocate your desired amount of RAM.  I chose 8192 (8GB), on a computer with 16384 (16GB) total  > NEXT


Configure Networking > Connection > Not Connected > NEXT


Connect Virtual Hard Disk > Create a virtual hard disk > NEXT


Connect Virtual Hard Disk > Installation options > Install an operating system later > NEXT > FINISH


CREATING A BRIDGED VIRTUAL SWITCH

NOTE: Creating a bridged virtual switch only needs to be done once.  Subsequent virtual machines can point to the same virtual switch.  If you've already created a bridged virtual switch, skip the next two steps.

To create a bridged virtual switch, run Virtual Switch Manager on the right side of the screen. To create a new virtual network switch, select the Create Virtual Switch button.


Name the switch Bridged > OK.  You may receive a warning that this may disrupt the network.  Allow it anyway.


Back to Virtual machine, edit settings by highlighting the virtual machine and clicking Settings.... Highlight the Network Adapter in the left pane, then click the Remove button in the right pane. Click Add Hardware at the top of the window, highlight Legacy Network Adapter in the right pane and click Add.  Next, highlight the new legacy adapter and set the virtual switch to Bridged OK.


Click the plus to the left of the new network adapter, and select Advanced Features. Give the machine a static MAC address > APPLY.


Highlight BIOS in the left pane, then set the boot order to Legacy Network Adapter first and Hard Drive (IDE) second > OK.


Next, attempt to PXE-boot the VM by right-clicking the VM and selecting CONNECT > START.  If your virtual machine has the proper PXE tags, you should see the familiar spinning cursor PXE-boot attempt.  Press F12 when asked at the bottom of the screen.  Note that it may take some time before the F12 is accepted and the VM begins to PXE-boot.  Once PXE-boot is done, you should see a typical Welcome to the Task Sequence Wizard.  There is currently no password, so press ENTER.


Select UMS Windows 10 Staff and Faculty from the list of Task Sequences.


NOTE: Did your session crash?  If so, you may need to partition the virtual drive before attempting to image.  While the error is on the screen, press F8 to get a command prompt, then perform the following steps:

  • diskpart <ENTER>
  • select disk 0 <ENTER>
  • clean <ENTER>
  • create partition primary <ENTER>
  • select partition 1 <ENTER>
  • formart fs=ntfs quick label=windows <ENTER>
  • active <ENTER>
  • assign letter=c <ENTER>
  • exit <ENTER>

Once you are out of DISKPART, type EXIT <ENTER> to get out of the command prompt window.  Reboot the VM, then try PXE-booting again.


Enter your MaineStreet credentials when asked

Set your campus

The virtual session should then download and install the image from the Task Sequence you've chosen.

NOTE: You may see a pop-up window noting that the computer model is unknown.  This may be because (as of this writing on 4/9/2018) Hyper-V sessions have not yet been confirmed for use with supplied drivers.  For testing purposes, you should be able to continue anyway.