Deploying by multicast setup mode

This example creates a setup deployment, applicable to both UEFI and legacy computes, which is distributed by multicast.

To be able to execute this example you need to prepare two computers, preferably one with UEFI and one with legacy BIOS, to use for the multicast deployment.

  1. To launch the OS Deployment Wizard select the Wizards> OS Deployment menu item.
    The wizard appears with its first window, OSD Manager .
  2. Select Your OSD Manager .
  3. Click Next to go to the following wizard page.
  4. Do not modify anything in this window and click Next to go to the following wizard page.
  5. In the Project Parameters window define the following parameters:

    Parameter

    Description

    Name

    Enter a self-explanatory name for the project into this text box, for example Windows 2008 (64 bit) Setup Deployment.

    Architecture

    This list box indicates the type of architecture for the OS deployment, that is, the architecture of the WinPE image launching the setup program. Select the 64 Bit option for the 64-bit Windows 2008 setup deployment.

    Supported BIOS Type

    The type of BIOS mode supported by the project, that is, if it supports legacy as well as UEFI deployments or only one of them. Only the setup mode supports projects valid for legacy and UEFI at the same time. Make sure the Legacy and UEFI value is selected.

    Target Drive

    Select from this list box the drive letter on which the operating system is to be installed, in our example we will use the C drive, therefore select C from this list box.

    Use Model Drivers

    Uncheck this box, this example does not used model drivers.

  6. Check the Deployment by Multicast box.
  7. Click Next to continue.
  8. In the Edit Multicast Options window clear the After (Min.) option of the Automatic Start Conditions parameter.
  9. Click the drop-down-list to the right of the Registered Targets option and enter_2_ instead of the prepopulated value.
  10. Click Next to continue.
  11. The option to create a new image ( Create a new OS image or setup ) is selected by default, therefore click Next to go directly to the following wizard page to define the parameters of the new image.
    In the Image Parameters window define the following parameters:

    Parameter

    Description

    Name

    Enter a descriptive name for the image in the Name box, for example Windows 2008 (64 bit) Setup Deployment.

    Supported BIOS Type

    The type of BIOS mode supported by the project, that is, if it supports legacy as well as UEFI deployments or only one of them. Only the setup mode supports projects valid for legacy and UEFI at the same time.

    Type

    This parameter defines the image type being used for the deployment. This list is already pre-filtered and only provides image types applicable to the selected deployment mode. For our example select the Windows Vista / 7 / 8 / 10 Setup option.

    Location

    Enter into this text box the network path to the image or setup folder, where you copied the image files required for the installation, for example, \\192.168.196.13\Windows2008-64bit. This is the folder which contains the setup.exe file for the deployment. This directory can be located on any device in your network, as long as it can be accessed by the OSD Manager.

    Connection Parameters

    Enter the login and password to be used by the deploying device to access the network location in read and write mode.

    1. To enter the login information click Edit to the right.
      The Properties window appears. 
    2. Enter the login name and corresponding password in the respective text boxes and re-enter the password for confirmation. The login name must have one of the following formats:
      <domain name>\<user logon>
      <local host name>\<user logon>
      Be aware that . is not a valid domain in this case. 
    3. To view the passwords clear the Hide Passwords check box. Both password boxes will now be displayed in clear text format. 
    4. To confirm the credentials click OK at the bottom of the window.
      The account will be added in the wizard window boxes.

    After all parameters are defined they must be checked that they are correct. Until the verification is executed and returns the Status Done , the wizard cannot continue.

  12. To verify click Check Image to the right of the Status box.
    CM will now verify all entries of this page, that is, the directory and the access rights to it. 
    If all values are correct the StatusDone is returned, otherwise an error message displays in the Status box indicating where the parameter value is not correct.
  13. After the StatusDone is returned click Next to go to the following wizard page.
  14. Select the drivers that are needed by the operating system, that is, any other required video, audio, modem drivers, and so on, by checking their respective boxes.

    If you have not yet defined the necessary drivers you can do so also in this wizard window. For this see topics Scanning a Directory for Drivers and Defining OS Drivers which describe the different processes.

  15. Click Next to go to the following wizard page, Target List Configuration .
  16. (Optional) In the OS Drivers select the necessary operating system drivers and click Next .
  17. (Optional) In the OS Drivers ) select the necessary drivers by model and click Next .
  18. The option to create a new target list ( Create a new target list ) is selected by default, therefore click Next to go directly to the following wizard page to define the members of the new target list.
  19. Enter for example the name Windows 2008 (64 bit) Setup Deployment into the Name box.
  20. Select the template of the unattended file that is to be used for the deployment.

    You can either use the template which is provided by BMC , leave the text box empty, or you can use you own custom defined file. For this example we will use the BMC default file, therefore do not modify the entry. If you use your own customized Unattend.xml file make sure it is in UTF-16 encoding.

    If the unattended file template box is empty, the OSD Manager will use the default unattended file template corresponding to the image type.

  21. This deployment will only have two target devices and we will add them as a new targets. For this select Create Target on top of the empty list box.
    The Create a New Target window appears with its three tabs, General Information , Parameters and Unattended Information .
  22. Enter the following information into the respective boxes of the General Information tab for the new device:

    Parameter

    Description

    Name

    Enter into this text box the short name that the new device is to have, for example, scotty. Be aware that the name of the new target can only have a maximum of 15 characters and can only contain the following characters: A-Z, a-z, 0-9, the underscore (_) and a dash (minus).

    Target

    Leave the radio button selected as we are defining a single target and enter the information for at least one of the three following text boxes. If the device is already up and running the wizard will recover information about the MAC address, based on the provided IP address or DNS name.

    MAC Address

    Enter into this text box the current MAC address of the target device. This is the most precise information to identify the device and should be preferred to the other two following identification options. The MAC address can be entered in one of the following formats: xx:xx:xx:xx:xx:xx, xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx.

    IP Address

    Enter into this text box the current IP address of the target device in its dotted notation. This option can be used if the MAC address is unknown and device is already running. In this case the respective target device will try to find its MAC address and provide this information.

    DNS

    Enter into this text box the current DNS information of the target device. This option can be used if the MAC and IP addresses are unknown and device is already running. In this case the respective target device will try to find its IP address which in turn will then search for the MAC address and provide this information.

  23. Select the Parameters tab and fill in the boxes for the target operating system information.

    Parameter

    Description

    Edition

    Select from the drop-down box the Windows edition that is being installed, for example Windows Vista Enterprise. The listed editions were automatically detected from the installation CD/DVD.

    Language

    Select from the drop-down box the language. This language setting will be applicable to the setup, the operating system to be installed, the keyboard layout and the user locale. The listed languages were automatically detected from the installation CD/DVD.

    Product Key

    Enter into this text box the OS product key (for example, ABCDE-FGHIJ-KLMNO-PQRST-UVWXY).

    TCP/IP Parameters

    Leave the preselected option Dynamic IP in this box, this will automatically assign the target device its new IP address via DHCP.

  24. Select the Unattended Information tab and fill in the boxes for your organization.
  25. Click OK at the bottom of the window to confirm the data for the new target device and add it to the target list.
  26. Repeat the preceding steps to add the second device.
  27. Click Next to go to the following wizard page and the Disk Configuration .
  28. (Optional) In the MBR Disk Configuration select the desired disk configuration for legacy installations and click Next .
  29. (Optional) In the GPT Disk Configuration ) select the desired disk configuration for UEFI installations and click Next .
  30. In the list of available disk configurations select the Disk with two partitions option.

    This configuration will create two partitions on the hard disk, the first, the boot or active partition with 30 GB and the second with the remaining space.

  31. Click Next to go to the following wizard page.
  32. In the Deployment Drivers window mark the check boxes for all required WinPE drivers, that is, at least one network and possibly a SATA driver.
  33. Click Next to go to the last wizard page.
  34. As we want to activate and execute this first deployment right away leave all values as they are and click Finish to launch the deployment.
    The project is now built, that is, all parameters are verified, the files are copied to the location required for the remote installation, and so on. You can follow the progress of the project in its console node, because the focus of the console is automatically moved to this object when the wizard is finished. In this view you can follow the different stages of the build. If any other than the final status Build completed successfully. is displayed, the build failed and you need to review the parameters of the project and maybe the source files. The Multicast transfer is launched at once. Both targets are listed here and have the status In Progress .
  35. Manually switch on the target devices.
    It will boot on the PXE boot section and the operating system installation is executed.

    Note:

    Do not start the target devices before the project is finished and ready to launch the installation. If the target devices are already running the PXE boot will not find the files for the installation and the deployment and installation of the new OS on the target devices will not take place.

  36. Select the Multicast Sessions> Your Multicast Server> Your Multicast Session subnode.
    In this view you can follow the Multicast transfer.

    Note:

    The column Sent (%) indicates the advancement of the transfer for both devices. The transfer is terminated when the parameter Server Status displays Done .

  37. You can follow the progress of the installation by selecting the Assigned Objects> Target List> Your Target List node in the left window pane.
    The right pane displays the target list members with their status information. Find your target devices and follow the different stages in this view. At the same time you can see on the screen of the target device the advancement of the process.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments