DS7.1 / DS7.5 How to create a bootable WinPE CD/DVD/Thumbdrive in Deployment Server that includes and deploys an image.

book

Article ID: 181389

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

 

Resolution

There are times when a location needs to have a self-contained image that is not distributed over the network, is bootable, and essentially hands-free.  This may be done on a DVD, or Thumb Drive, or some other portable media.  This procedure is designed to help you create one using the Symantec Management Platform and Deployment Solution 7.x.  A similar article for DS 6.9 can be found in HOWTO9572.

 

Short Version:

Step 1: Create an image.  We recommend you use Ghost, though any image format will work.  For the purpose of this article, we'll assume you have a Ghost image.  This is no different than any other image capture you would perform so no steps will be included.

Step 2: using BootWiz (BDC), make a WinPE configuration (this cannot be done in the console)

  1. Run BootWiz from the file system
  2. Create a New configuration
  3. Next next next through the entire first “stuff” and click Finish
  4. You'll start the process of creating the disk/configuration and be on Step 1 of 4 – select Cancel.   This will return you to the BootDiskCreatorYou’ll be in the BDC now with your new configuration.

Step 3: Modify the configuration by adding the image, and instructions to load it.
In this step, you are going to essentially "insert" the image, imaging tools, and scripts necessary to launch the image automatically once the preboot OS has loaded.

  1. Add the imaging tools to the configuration.  Normally, you would create a new folder and then copy the ghost folder into here.
  2. Add the image to the configuration.  Normally, you would create a new folder for the image directly off the root for easier access in the following step
  3. Modify the Startup.bat (listed in BootWiz) file to call the imaging tools from the location you added in 3.1 above along with the image in 3.2 above.  Essentially, this is a manual execution of Ghost. Remember the root drive will be X.

Step 4: Create the ISO / Boot disk

  1. Once the appropriate tools and image is in your configuration, right-click the configuration and choose Create Boot Disk. This will put you back in the step you cancelled from in 2.1 above.
  2. Select either ISO or boot Disk (your choice) on the left, and on the right, select stand-alone boot.
  3. Finish creation
  4. Burn to disk

 

More Detailed version:

  1. Create an image.

    1. This will eventually be stored on the portable media, so ensure it is configured completely and correctly.
    2. We recommend deploying it on all supported models to ensure it works correctly first.
       
  2. Create a Preboot Configuration to be installed on your portable media (installation will be done later)
     
    1. NOTE: This cannot be done in the SMP Console.
    2. From the file system, launch BootWiz on the SMP Server
      1. 7.1 Location = program files\Altiris\Altiris Agent\agents\Deployment\Task Handler\Bootwiz\Bootwiz.exe
      2. 7.5 Location = program files\Altiris\Deployment\BDC\BootWiz\Bootwiz.exe
    3. If prompted, create a new configuration. If not, right-click in the left pane and create a new configuration.
    4. Complete Wizard Step 1 and click Next:
      1. Add a configuration name.
      2. Description is optional.
      3. Default OS should be PE 2.1, and for this example, we’re going to use WinPE, not LinuxPE.
      4. The default OEM Extension is DS and should be used. If you have your own, that’s unsupported but should work if you did it right.
         
    5. Click Next on step 2
    6. Step 3 must be modified if you are in a static IP environment. Otherwise, just click Next.
    7. Click Next on step 4.
    8. Click Finish
    9. Click Cancel on Step 1 of the next wizard. We’ll return here later.
       
  3. Modify the newly Created Preboot configuration:

    1. After 2.i, you should be in the BootWiz main screen. Find your configuration on the left, and under it, find statup.bat.
    2. Edit this file to perform all the actions you will need for a fully automated or manually intervened process. Examples might include:
      1. Launch Ghost with all the requisite command lines for your default image. This might be in a highly normalized environment for instance.
      2. Launch another batch-file menu that has several options, including running an image, or configuring the computer (e.g. Servers) or whatever.
      3. Have its own menu, maybe of a couple of images
      4. Do nothing, allowing the engineer to do all manually.
         
    3. Add the image to the folder structure
      1. Find the files just created under Deployment \ Task handler \ Bootwiz \ Configs. There will be a folder there with the name you just created. NOTE: No folders will be present for those created in the console.
      2. Create a folder for your files. For instance, you might have a company folder called Symantec, or “MyCompany”.
      3. Place any supplementary files and/or scripts in the folder. This should include any custom menu/scripts and especially the ghost image created in Step 1 above.
      4. Verify that the Startup.bat file in the Shared folder is correct per your edits. You can also edit it here.
         
  4. Create / Compile the content.
     
    1. Back in the Boot Disk Creator (BootWiz), right-click the new configuration and select “Create Boot Disk”. This places you in step 1 of the next wizard.
    2. Configure Wizard Step 1 and click Next:
      1. Select the appropriate Boot Media
      2. Select “stand-alone Boot”
      3. Take CAREFUL note of the path.
      4. Select the appropriate media type at the bottom (x86 vs x64)
      5. When you click Next, if Prompted, click Yes.
         
    3. Wizard Step 2 runs automatically and builds the image in the path noted in 5.b.iii above.
    4. Wizard step 3 should simply show success and remind you of the path.
       
  5. Burn / copy the content to Disk. For the thumb drive, it should be an EXE, for the CD, and ISO. The process for doing this though is outside the control of this product.
     
  6. Test and deploy.