Adding and configuring the OSD Manager

The following topics provide more information about adding and configuring the OSD manager:

Adding the OSD Manager

The first step for any type of operating system deployment is the selection and configuration of the OSD Manager.

To add the OSD Manager you have two different possibilities:

• Add the OSD Manager under the main OS Deployment node
• Assign a device the OSD Manager role via the device's properties, either in the Device Topology or under the Device Groups node

Configuring a Device as OSD Manager under the OS Deployment Node

1. Select OS Deployment in the left window pane.
2. Select Edit > Add Device
   The Add a new OSD Manager pop-up menu appears displaying the list of all devices that can be OSD Managers due to their operating system.
3. Select the future OSD Manager from one of the list boxes.
4. Click OK to confirm and close the window.

The device is added to the table of OSD Manager and its configuration parameter is updated.

Configuring a device as OSD Manager in the device's properties

1. Select Device Groups > Your Device Group > Your Device or Device Topology > Your Device in the left window pane.
2. Click Edit > Properties .
   The Properties pop-up menu appears.

3. Check the OSD Manager box.

   For devices, which do not have the required operating system, this option is not accessible.

4. Click OK to confirm and close the window.

The device is added to the table of OSD Manager and its configuration parameter is updated.

Configuring the OSD Manager

When configuring the OSD Manager, two or three different parts must be configured, depending on its assigned roles:

• The specific OSD Manager parameters
• The parameters for the image repository role
• If it is also assigned the network boot agent role, the parameters for the network boot agent

1. Go to the OS Deployment> Your OSD Manager> Configuration node in the left window pane.
2. Click Properties.
   The Properties window appears.

3. Define the following parameters for the OSD Manager role:

   Parameter	Description
   Windows ADK Path	Enter into this text box the path to the Windows ADK. If you do not enter any value, the default installation path is used. To directly select the path click Select next to the text box. A pop-up menu appears with the directory structure of the device where you can directly select the installation directory. Click OK to confirm and close the window.
   Windows ADK Status	To test if the Windows ADK (WADK) is correctly installed, click Test next to the box. The agent verifies the WADK installation and updates the displayed status accordingly.
   TFTP Local Path	Enter into this text box the local path to the shared TFTP server directory. To directly select the path click Select next to the text box. A pop-up menu appears with the directory structure of the device where you can directly select the path. Click OK to confirm and close the window.
   Driver Root Folder	This text box contains the complete path to the directory where the drivers are copied to for later use. The default directory for this is <InstallDir>/Master/data/OSDeployment/drivers/. Do not modify this value, if you are following a standard deployment. To directly select the path click Select next to the text box. A pop-up menu appears with the directory structure of the device where you can directly select a different directory. Click OK to confirm and close the window.
   Status	This field displays the overall progress of the WinPE initialization process which generates files based on the images of the WIM Windows ADK. These files are then used as the base for any OSD project in the BMC Client Management - Software Distribution. Here you can see the advancement of the initialization in percent values and any error messages should errors occur. Be aware, that this process might take several minutes to complete. During this process, which is required only once when defining the OSD Manager for the first time, the console can be used for any type of viewing but no writing operations. To start the process click Check Environment.

   The definition of the OSD Manager cannot be completed until the environment check completes without errors and the Status shows OK - Initialization Complete .

4. To verify click Check Environment to the right of the Status box.
   CM now verifies all entries of this page, that is, the directories and the access rights to them and the DHCP server address, if it is installed on another device. If all values are correct, the StatusOK is returned, otherwise an error message displays in the Status box indicating where the parameter value is not correct.

5. Click the double arrow in the Image Repository line.
   For the image repository you need to define the following parameter:

   Parameter	Description
   Storage Path	Enter into this text box the relative path for the storage location for all necessary OSD data. The path is relative to the agent installation directory. Click Browse to select the path in the storage path selection window. Click OK to confirm and close the window. If this field is left empty, the default path (../data/OsDeployment/streams) is used.

6. If the OSD Manager is also a network boot listener, click the double arrow in the Network Boot Listener line to define the parameters of this role as well:

   Parameter	Description
   Internal DHCP	Check this box if you want to use the DHCP gateway of the OSD module instead of specifically configuring your own DHCP server. In this case a DHCP gateway is installed that is redirecting the computers to the OSD manager and get installed, instead of adding the necessary options to your existing DHCP server.If you do not use this option make sure you have a DHCP server on a different machine that is configured as explained in the configuration options of the Prerequisites topic, preferably with the 066/067 options. If you clear this box, the following two boxes become available.
   DHCP Server Address	Enter the IP address or DNS name of the DHCP server which redirects the PXE requests to the local TFTP server. The DHCP server must have the protocol BOOTP activated.This option is only available, if the internal DHCP gateway is not used.
   Skip DHCP Check	If the DHCP server is installed on the same device as the OSD Manager device, you must check this text box, because the DHCP server cannot be verified in this case. This test verifies, if the BOOTP protocol is activated on the DHCP server.This option is only available, if the internal DHCP gateway is not used.
   Unicast Server Port (TCP)	This parameter determines on which port the unicast server should listen and to which port the clients should send their requests and acknowledgements. It is only available in the general configuration, not on project level. Modifying this parameters requires restarting the unicast server and, to be correctly applied, restarting all related OSD agents as well. In addition all projects need to be rebuilt if this parameter is modified as it is embedded during the WinPE ISO image build. The default would be the agent port in TCP, typically 1613. Only modify this default value, if absolutely necessary.
   Multicast Server Port (UDP)	This parameter determines on which port the multicast server should listen and to which port the clients should send their requests and acknowledgements. It is only available in the general configuration, not on project level. Modifying this parameters requires restarting the multicast server and, to be correctly applied, restarting all related OSD agents as well. In addition all projects need to be rebuilt if this parameter is modified as it is embedded during the WinPE ISO image build. The default would be the agent port in UDP, typically 1610. Only modify this default value, if absolutely necessary.
   Interfaces	For the Interfaces you need to define on which local interfaces the agent is to listen. You have the following options: All Interfaces: Check this radio button, to listen on all local network interfaces. Custom Interfaces: Check this radio button, to only listen on some local network interfaces. The box below displays the list of available interfaces. Check the boxes of all interfaces to listen to.

7. Click OK to finalize the OSD Manager definition.

   Note:

   Be aware that the first initialization might take several minutes.