Configuring and modifying the configuration of OSD Manager
The following topics guide you through configuring and modifying the OSD Manager:
To configure the OSD Manager
The second wizard window allows you to specifically configure the OSD Manager.
- Enter the name of the new OSD Manager into the Name box.
Now enter all other required values into the respective boxes.
Parameter
Description
Windows AIK Installation Path
The complete path of the Windows Automated Installation Kit (AIK). If not path is specified the default installation path ( C:Program FilesWindows AIK ) is used.
Driver Root Folder
The complete path of the directory into which the drivers are copied to for later use. Format: [InstallDir]MasterdataOSDeploymentdrivers .
TFTP Local Path
The local full path of the TFTP server root directory, for example, C:PXETFTP .
TFTP UNC Path
Enter into this field the network path to the shared TFTP server directory, for example, [IP address OSD Manager]PXETFTP .
TFTP UNC Credentials
The login name to the share on the TFTP server.
Use the internal TFTP server
Check this box if you want to use the internal TFTP server of the OSD module instead of specifically configuring your own TFTP server. Only use this option if you do not have another TFTP server running. If another server is running see the Configure TFTP Server section of your OSD manual on how to configure your existing TFTP server for use with the BCM OSD functionality first.
Internal TFTP Status
Shows the current status of the internal TFTP server. If the status Executing is displayed the TFTP server runs as expected. If another TFTP server is running at the same time an error is displayed in the Status due to a conflict between the internal and external server.
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.
Internal DHCP Status
Shows the current status of the internal DHCP server. If the status Executing is displayed the DHCP server runs as expected. If any other status value is displayed check if the DHCP server is configured as explained in the prerequisites.
DHCP Server Address
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.
Skip DHCP Check
If the DHCP server is installed on the same device as the OSD Manager device you must check this box, as the DHCP server cannot be verified in this case. This test verifies if the BOOTP protocol is activated on the DHCP server.
Status
Displays the configuration verification status of the OSD Manager. If the status is not OK you finds an error message to indicate which parameter is incorrect.
- To verify click Check Environment to the right of the Status box.
BMC Client Management - Software Distribution will now verify 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 Status OK is returned, otherwise an error message displays in the Status box indicating where the parameter value is not correct. After the Status OK is returned click Next to go to the following wizard page.
To modify the OSD Manager configuration
To modify the configuration of the OSD Manager proceed as follows:
- Select OS Deployment > Your OSD Manager > Configuration in the left window pane.
- Select Edit > Properties

The Properties window appears. Make the desired changes in the respective boxes.
Click Check Environment to the right of the Status box to verify your changes.
- Click OK to confirm the changes and close the window.
Any changes made are saved and applied to the OSD Manager.