When we started using ZCM Imaging we still had ZENworks 7 Imaging enabled in the network. We do the imaging only using PXE and because you should only have one pdhcp service in your network the migrating scenario should be as simple as possible. When we migrated we experiences several minor and major problems what explains this page. One day you have to do it all over and you don't want to have these problems again. These are the steps that have to be followed:

• Create / Add diskspace for images
• Configure the diskspace for imaging
• Unload pdhcp on old server
  • And, if necessary remove DHCP option 60
• Load pdhcp on new server
• Start imaging

Since my ZENworks server is a VMware machine I could add a new disk using vmware. After adding the disk you'll have to run the command:

sudo rescan-scsi-bus.sh

It will show a message telling it hasn't found any devices but you can ignore that message. When you start yast2 and select the partitioning tool the new disk is there. Since the disk will be hosting the images I created the mountpoint /images to mount it. The default (and non-changeble) start point for image files within ZENworks is however /var/opt/novell/zenworks/content-repo/images. However, according to this Novell documentation you can delete the original images directory and make a symbolic link instead. You can also create folders below the start point for organizing reasons. So, all that means these steps:

• Delete the original images directory:
  • rm -rf /var/opt/novell/zenworks/content-repo/images/
• Create the symbolic link to the /images directory:
  • ln -s /images /var/opt/novell/zenworks/content-repo/images
• Create folders to organize images:
  • mkdir /images/lenovo
  • mkdir /images/hp
• Make the zenworks user owner of the directory:
  • cd /images
  • chown zenworks:zenworks -R *

Unload the pdhcp and ZENworks imaging services from the old server:

• unload pdhcp
• unload tftp
• unload dts
• unload imgserv

Make sure you comment these services out from the corresponding startup file: zfdstart.ncf:

#ZENworks WakeOnLan Settings
#startWOL.ncf


SEARCH ADD SYS:\JAVA\NJCLV2\BIN
LOAD JAVA.NLM
load nwsnut
cls


SYS:\system\zenWSImp.ncf
SYS:\system\zenWSRem.ncf
#SYS:\system\pxeStart.ncf
#load SYS:\system\imgserv

Note: pxestart.ncf starts pdhcp, tftp and dts.

In the old setup the dhcp and pdhcp services were running on the same server. This means that in the DHCP options 'option 60' called 'Vendor Class Identifier' was enabled with the value 'PXEClient'. Remove the option from the configuration and restart the dhcp service on the server:

netwarebox:unload dhcpsrvr

28-04-2010   9:40:37 :    DHCPSRVR-3.14-0
     DHCPSRVR termination initiated.

SERVER-5.70-68: DHCPSRVR terminated at 28-4-2010 09:40:37.
Module DHCPSRVR.NLM unloaded
netwarebox:load dhcpsrvr
Loading Module DHCPSRVR.NLM                                     [     OK     ]

28-04-2010   9:40:39 :    DHCPSRVR-3.14-0
     IP Database loaded.

In the end (after also doing the next steps) we still got the error:

ProxyDHCP service did not respond to request on port 4011

Port 4011 is only used in combination with option 60. No option 60, no port 4011 (but port 69). This means that the option 60 was still in use!!! Which was, I thought, impossible because I removed the option from all our subnets. Turns out that somewhere in the past a colleague of mine configured the option in the global configuration options:

So after removing the option from the global configuration and restarting the dhcp service again it all worked.

When you install a primary ZENworks server you get a few ZENworks services that are needed to run on every primary server. For PXE booting there is one more service that need to be started.

These services are started by default:

/opt/novell/zenworks/preboot/bin/novell-pbservd
/opt/novell/zenworks/preboot/bin/novell-zmgprebootpolicyd
/opt/novell/bin/novell-tftpd

This service has to be started manually:

/opt/novell/bin/novell-proxydhcpd

To do so, issue this command:

/etc/init.d/novell-proxydhcp start

Of course, don't forget to make sure the service also starts after a reboot. To do so, start 'Yast2' → go to 'System' → go to 'System Services (Runlevel)'. Find the novell-proxydhcp service in the list and enable it:

Create an image using this command:

img -makep lenovo/mgmtpc.zmg

Restore the image using this command:

img -restorep lenovo/mgmtpc.zmg