Skip to end of metadata
Go to start of metadata

Windows Imaging (PXE):

The following are the steps you will need, from start to finish, to create a Windows image from FileWave and send it out to your devices. 
This guide assuming the following:

  • FileWave Imaging Server is set up
  • Devices are on the same subnet (unless the proper steps were taken to image across subnets)
  • Windows devices are in the FileWave Admin with valid Mac addresses either as an active client or a placeholder where the name isn't longer than 15 characters

IMPORTANT:

PLEASE NOTE for UEFI imaging:

  • If you are wanting to create/deploy an image from/to a native UEFI machine you will need to create a new master from a native UEFI machine using IVS v5
  • The DHCP server has to be the same as the THTP server. If not the following error message will be thrown in the boot sequence: PXE-E99: Unexpected network error. Because this is caused by the PXE UEFI firmware, PXE legacy mode should still work normally.

Prepare and Download all needed parts

Before starting be sure you have:

  1. FileWave Management Server and Admin
  2. FileWave Imaging server setup: Network Imaging Guide
  3. FileWave Custom Client MSI download from here
  4. Supported Windows device
  5. FileWave manual: accessed from here 

Procedures

Creation and Importation of an Image:

To create an image we will need to capture it off a pre-configured device. 
Note: You will need to have the Windows device you are capturing the image from in FileWave prior to the capture. This can be done with either enrolling the Windows device in FileWave with the Client or using a Placeholder.
NOTE: You will only be able to deploy your image to devices with a hard drive that is larger than or equal to the drive the image was captured on. So best practice would be to capture your image off the smallest hard drive possible so that you may deploy the image to any larger drive. A VM would be perfect for this task.

  1. Install a clean version of Windows
  2. Make any desired changes you want to the OS, including installing the FileWave Custom Client MSI
  3. Follow the guide below to create an answer file, run chkdsk, and sysprep.
    If you have an existing answer file then skip to the chkdsk and sysprep steps in the article 
    Note: The sysprep guide is valid for other versions other than Windows 7
    Sysprep is REQUIRED
    Windows 10 & Windows 7 Sysprep - Automated Install Settings
  4. Once the computer has restarted with sysprep you will need to make an association in FileWave
  5. Launch the FileWave Admin and navigate to the the Imaging section
  6. Once there use the drop down menu to select Windows
    This then filters the devices and images seen below for Windows


    imagingsection

  7. Now find your device on the left pane and the object called Master Image on the right pane. Click, drag, and drop Master Image to your device on the left.
    This will then launch a dialog box stating that the association has been made.


    masterimageassocaiation

  8. Open the FileWave Preferences, go to the Imaging tab, select your imaging server, and then click Monitor
    You will need to make sure it is on the same model number as your FileWave server by waiting 2 mins or clicking the verify button


    ivsmonitor358

  9. Once the IVS is on the same model as your FileWave server you can now PXE boot your target machine for image capture.
    The device will then find an IP address from DHCP, see the FileWave server, and go through the booting process.


    PXEmasterimage

  10. You will then be prompted Enter a name for the image to be uploaded.


    namemasterimage

  11. Once you have named the image it will go through the capture process for all of the partitions.
    After the IVS has captured the image it will automatically upload to your FileWave server. The image will appear in the Filesets and the Imaging section.


    masterimagecapture

You have now successfully created an image to be deployed to your Windows machines.

Associating and deploying the Image:

To deploy an image you already have in FileWave is a very easy process and is similar to the steps above for creating an image.

  1. Launch the FileWave Admin and navigate to the Imaging section
  2. Once there use the drop down menu to select Windows
    This then filters the devices and images for Windows

  3. Now find your device, or group of devices, on the left pane and your image on the right pane. Click, drag, and drop your image to the device, or group of devices, on the left.
    This will then launch a dialog box stating that the association has been made.
    NOTE: If you have a Driver fileset in FileWave you will follow the same steps in step 3 above to assign those drivers after you assign the image. Creating Windows Driver Filesets
    NOTE: If you have association to another image (including the master image) you will need to delete that first prior to making a new image association.



    creatingimageassocation


  4. Open the FileWave Preferences, go to the Imaging tab, select your Imaging server, and then click Monitor
    You will need to make sure it is on the same model number as your FileWave server by waiting 2 mins or click the verify button.
    Note: If there are no other associations to this image then the image has to be transferred to your IVS before you PXE boot your devices.



    ivsmonitor371


  5. When the imaging server is on the same model as your FileWave server (and the image has been copied over) you are now ready to PXE boot your devices.
  6. Connect your Windows device to ethernetpower on the device, and hold down the F12 key. Or go into the boot menu and select to boot from the NIC
    Note: Boot keys can change between hardware, you may need to check the devices manual for the correct key to push.

  7. Your device(s) will then find an IP address from DHCP, see the FileWave Imaging server, and go through the booting process
  8. From here the image will be deployed to the machine, named accordingly to the FileWave client object, driver files will be copied over in preparation for first boot, and the machine will restart to launch into the OS.
    Note: After the image process has completed the imaging association in FileWave will be disabled. You can see this by looking at the assocation's column Enabled is set to false.



    deployingimage



Congratulations, you have successfully associated and deployed a Windows image through the network!