56.3 Checking the Preboot Services Server Setup

This section provides information on how to check the configuration of Desktop Management Preboot Services after it is installed, and how to set up standard DHCP and Proxy DHCP services on the same server.

56.3.1 Overview of Preboot Services Components

The Preboot Services components are different for the supported imaging servers:

Preboot Services Components for Linux Imaging Servers

The following components are installed as part of Preboot Services:

Table 56-4 Preboot Service Components

Daemon

Description

libzmgserv.so

This library file is used by eDirectory to provide imaging services to the devices.

novell-proxydhcp

The novell-proxydhcp daemon runs alongside a standard DHCP server to inform PXE devices of the IP address of the TFTP server. The Proxy DHCP server also responds to PXE devices to indicate which bootstrap program (nvlnbp.sys) to use.

novell-tftp

The novell-tftp daemon is used by PXE devices to request files that are needed to perform imaging tasks. The TFTP server also provides a central repository for these imaging files, such as the Linux kernel, initrd, and nvlnbp.sys.

A PXE device uses this server to download the bootstrap program (nvlnbp.sys).

novell-zmgprebootpolicy

The PXE devices use the novell-zmgprebootpolicy daemon to check if there are any images associated with the device.

The novell-proxydhcp daemon must be started manually and does not need to be run on all ZENworks Imaging servers.

The other three daemons are started automatically when installing ZENworks Linux Management, or any time the server is rebooted, and must run on all ZENworks Imaging servers.

For more information on these daemons, see Section 63.6, Imaging Server (Imgserv.nlm or .dll or .dlm, or Linux Daemons).

Preboot Services Components for NetWare and Windows Imaging Servers

The following components are installed as part of Preboot Services:

Proxy DHCP Server

The Preboot Services Proxy DHCP server runs alongside a standard DHCP server to inform Preboot Services clients of the IP address of the TFTP, MTFTP, and Transaction servers. The Proxy DHCP server also responds to PXE clients to indicate which boot server (TFTP or MTFTP) to use.

TFTP/MTFTP Server

The Preboot Services TFTP/MTFTP server is used by the Preboot Services client to request files that are needed to perform imaging tasks. The TFTP server also provides a central repository for these imaging files (/srv/tftp/boot/linux and linld.com).

A PXE client uses this server to download the Preboot Services client.

TFTP is used by default because it speeds up the workstation’s boot process; however, you can change the configuration to use MTFTP.

Transaction Server

The Preboot Services client connects to the Transaction server to check if there are any imaging actions that need to be performed on the workstation.

56.3.2 Checking Imaging Server Setup

The methods for checking the setup on ZENworks Imaging servers depends on the server’s platform:

Checking the Setup on a Linux Server

After the Desktop Management Preboot Services components are installed, the following services should be installed and running on the server:

Table 56-5 Preboot Services Daemons

Service

Command to Check Its Status

novell-tftp

/etc/init.d/novell-tftp status

novell-zmgprebootpolicy

/etc/init.d/novell-zmgprebootpolicy status

You should not need to change the default configuration of these daemons.

The status of the libzmgserv.so file cannot be checked.

If the Preboot Services components are installed to a Linux server that is also a standard DHCP server, see Linux DHCP Server.

Checking the Setup on a NetWare Server

After the Desktop Management Preboot Services components are installed, the following services should be installed and running on the server:

  • pmap.nlm

  • tftp.nlm

  • pdhcp.nlm

  • dts.nlm

You can use the pxestart.ncf file to start Preboot Services with a single command.

You can use the pxestop.ncf file to stop Preboot Services with a single command.

You should not need to change the default configuration of these services unless the default multicast IP is already in use in your environment or you moved any of the PXE-installed files from their default directories.

For information about configuring these services, see Configuring Preboot Services Servers in NetWare.

If the Preboot Services components are installed to a NetWare® 6.x server that is also a standard DHCP server, see NetWare 6.x DHCP Server.

Checking the Setup on a Windows Server

After the Desktop Management Preboot Services components are installed, the following services should be installed and running on the server:

  • Proxy DHCP Server

  • MTFTP Server

  • TFTP Server

  • Transaction Server

You should not need to change the default configuration of these services unless the default multicast IP is already in use in your environment or you moved any of the PXE-installed files from their default directories.

For information about configuring these services, see Server Configurations.

If the 2000/XP/2003 server where the Preboot Services components are installed is also a DHCP server, see Windows 2000 Advanced Server.

56.3.3 Setting up Standard DHCP and Proxy DHCP Services on the Same Server

When you have standard DHCP and Proxy DHCP services on the same server, do the following according to the server’s platform:

Linux DHCP Server

For the case where you have Preboot Services and DHCP running on separate servers, no network configuration is required.

For the case where you have Preboot Services and DHCP are running on the same server, option tag 60 must be set on the DHCP server. Do the following to set up standard DHCP and Proxy DHCP on the same server:

  1. Stop the DHCP services on the Linux imaging server.

  2. On this server, open the dhcp.conf file in an editor.

  3. Insert the following line in the file:

    option vendor-class-identifier "PXEClient";
    
  4. Save the file.

  5. Restart the DHCP service.

NetWare 6.x DHCP Server

Use the following steps to set up standard DHCP and Proxy DHCP Services on the same NetWare 6.x DHCP server.

IMPORTANT:Installing and running the Proxy DHCP server on a NetWare 5.x server that is already running a standard DHCP server is not supported because the DHCP protocol on NetWare 5.1 does not deliver option 60.

If you are running a NetWare 5.1 server but have upgraded the DHCP service to NetWare 6.x, perform the following steps. However, If you are running a NetWare 6.x server, then begin at Step 7.

  1. Install the DNS-DHCP client from NetWare 6.x.

  2. Copy dhcpsrvr.nlm, dnipinst.nlm, and nddprefs.dat from the sys:\system directory on the server to a backup location.

  3. Copy dhcpsrvr.nlm, dnipinst.nlm, and nddprefs.dat from the sys\system directory on the NetWare 6.x CD to the sys\system directory on the server.

  4. Using the DNS-DHCP console, export the DNS and DHCP records.

    Note the Novell eDirectory™ locations of the DNS-DHCP locator and group objects and the DNS zone objects.

  5. At the system console, enter load DNIPINST to install the updated DNS-DHCP and schema extensions.

  6. Using the DNS-DHCP console, import the DNS and DHCP records.

  7. Using the DNS-DHCP console, click Global Preferences on the toolbar, then click the Global DHCP Options tab.

    or

    Using the DNS-DHCP console, click the subnet in the left panel, then click the Other DHCP Options tab.

  8. Click Modify.

  9. Select Option 60 under Available DHCP Options, then click Add.

  10. Type PXEClient in the Vendor Class Identifier text box, then click OK twice.

  11. If this server is also a DNS server, enter load NAMED at the system console.

  12. At the system console, enter load DHCPSRVR.

  13. Using a text editor, make the following changes to sys\system\pdhcp.ini:

    Set USE_DHCP_Port to 0.

    Make sure USE_BINL_PORT is set to 1.

  14. Unload and reload pdhcp.nlm.

Windows 2000 Advanced Server

Use the following steps to set up standard DHCP and Proxy DHCP Services on the same Windows 2000 Advanced Server:

  1. At the command prompt, enter netsh.

  2. At the netsh prompt, enter dhcp server.

  3. At the dhcp server prompt, enter the following:

    add optiondef 60 ClassID STRING 0 PXEClient
    
  4. Add the definition type in the DHCP setup menus.