OS Deployment - Initial Configuration

Version 2
    Share This:

    Preparing the OS Deployment manager

    1. Ensure the system which will become the OS Deployment manager has a copy of the Asset Core agent installed, and that the system appears in the Asset Core console. In this example, the master server will also act as the OS Deployment manager.
    2. Install the Windows 7 Automated Installation Kit on the OS Deployment Manager. The Automated Installation Kit can be downloaded from Microsoft here.
    3. In the Asset Core console, click the OS Deployment node on the left side of the console window, then click the Add a new OSD Manager toolbar button:
      Add OSD manager.png
    4. Select the device which will become the OSD manager, and click OK.
    5. A directory to store network boot files will be created as C:\PXETFTP\, please ensure this folder is shared, and can be written to over the network. If desired, this directory can be moved to a different drive.
      share pxetftp.png
    6. In the Asset Core console, click the Configuration node under your OSD manager, then click the Properties toolbar button. The following window will be displayed:
      configuration properties.png
    7. Ensure the parameters entered in the properties window are appropriate for your environment. If you have already shared the PXETFTP folder as described in step 5, clicking the Automatic button for the TFTP UNC path field will fill in the appropriate path for you. In most cases, you will need only to click this button, and edit the TFTP UNC Credentials.
      • If the "Use the internal DHCP gateway" option is not checked, configuration changes on your DHCP server will be required. Please set option 66 in your DHCP server's configuration to be the IP address of the OS Deployment manager, and set option 67 to "pxelinux.0" (without the quotes).
      • If the OS Deployment manager, and the systems which will receive an image are on separate subnets, you must configure options 66 and 67 on your DHCP server; the internal gateway will not be able to pass the required DHCP options to the target devices.
      • Many DHCP server systems have a separate parameter for identifying the PXE boot server (often called "next boot server"); if your DHCP server has this type of configuration, please ensure that the IP address of the OSD manager has been entered in the next boot server option as well.
    8. Click the Check Environment button. The status field should read "OK" as shown in the above screenshot.
      • If a message stating the DHCP server check failed is shown, and you have already ensured that DHCP options 66 and 67 are correctly configured on your DHCP server, please check the "Skip DHCP Check" option, and click Check Environment again.
    9. Click the OK button after ensuring the status field reads "OK".
    10. Click the Properties button in the Configuration node for this OSD manager again.
    11. In the Properties window, click the Create New Test Project button, and enter the subnet which contains the target devices. For example, if the target devices are on the 10.1.2.0/24 subnet, please enter "10.1.2.*" (without the quotes), and click OK.
      • The test project will not make any changes to any target devices; this project is intended only to ensure that the OS Deployment environment is properly configured
    12. Once the dashboard shows that the build has completed, please PXE boot a PC on the subnet defined in the test project parameters in the previous step.

     

    The most common problem with booting the test project is the "failed to mount log share" error. Further details on troubleshooting this error can be found in this post.

     

    Below is a video showing a target device boot into the OS Deployment test project successfully: