This section provides solutions to problems you might encounter when using Preboot Services and Imaging in ZENworks.
A Windows device with Windows 10 updates might not boot
Take and restore an image of the device using the Tuxera driver.
Take and restore an image of the device in the .zmg format using WinPE
Check Disk might run on a device with Windows 2019
Applying the MDT Deployment bundle to re-install the operating system on a device that already has an operating system results in an infinite loop
Customize the corresponding MDT Deployment Share which the MDT WIM uploaded in the bundle contacts on booting. Use the ISDTool.exe to clear the MBR:
Download the 32-bit ISDTool.exe from the ZENworks Download page (https://zenworks_server_IP_address:port/zenworks-setup) under Imaging Tools. Place it in the MDT Deployment Share under the /Tools/x86 folder.
Download the 64-bit ISDTool.exe from the ZENworks Download page (https://zenworks_server_IP_address:port/zenworks-setup) under Imaging Tools. Place it in the MDT Deployment Share under the /Tools/x64 folder.
Open the ZTIDiskpart.wsf script file present in the MDT Deployment Share under the Scripts folder and insert the following lines just above the Open an instance for diskpart.exe, and dynamically pipe the commands to the program line:
Dim sampCmd Dim aScriptDir Dim aArchitecture aScriptDir = oFSO.GetParentFolderName(WScript.ScriptFullName) aArchitecture = oEnvironment.Item("Architecture") sampCmd = aScriptDir & "\..\tools\" & aArchitecture & "\ISDTool.exe cleandisk " & iDiskIndex oShell.Exec(sampCmd)
When the device boots the MDT WIM and contacts the above customized MDT Deployment Share, the script prevents MDT from wiping out the ZISD data,
Clear the MBR using WinPE Imaging Script Preboot bundle before applying the MDT Deployment bundle on the device:
Create WinPE Imaging Script Preboot bundle in ZENworks. Add the following command as the:
isdtool cleandisk disk_index
For more information, see Section 3.9, ISDTool.
Apply the WinPE Imaging Script Preboot bundle on the device.
Apply the required MDT Deployment bundle on the device.
IMPORTANT:Exercise extreme caution when using this option. The above dd command clears the MBR. After running this command, the operating system will not boot. Hence, the command should be run only before re-installing the operating system on the device.
An error message is displayed when Windows Managed devices, or Windows Servers reboot after you restore an image with size greater than 2 TB
After the image is restored, insert the appropriate Windows installation CD.
Choose the option to repair Windows, and follow the instructions.
The ZENworks Server continues to write to the image file even if the Imaging operation to take an image of the device fails
bad cluster chain, run chkdsk.exe
Consequently, the image file size grows.
The Imaging tools downloaded from the ZENworks Download page are not installed to the specified drive
msiexec -i novell-zenworks-zmgexplorer-11.0.xxxx.msi TARGETDIR="complete_path_of_the_target_directory"
For example, if you want to download and install the Imaging tools to c:\program files, use the following command:
msiexec -i novell-zenworks-zmgexplorer-11.0.xxxx.msi TARGETDIR="C:\Program Files"
Unable to browse for the image files on the Satellite while taking an image or applying a Preboot bundle to a managed device
Could not start ZenHttpServer - Port 80 is already in use.
Change the port number used by Satellite:
In ZENworks Control Center, click thetab.
In the Server Hierarchy panel, select the check box next to the Satellite whose port number needs to be changed.
The Configure Satellite Server dialog box is displayed.
In thefield, specify a new port number.
Ensure that the managed device is running on the port specified in Step 1.d:
Open a Web browser on the managed device to the following address: http://localhost:port_number.
A message containing the Novell ZENworks Content Server version is displayed.
(Conditional) If the ZENworks Content Server version is not displayed, restart the ZENworks Agent or the managed device.
The ZENworks Images stored in the images directory on the Primary Server are not replicated on the Secondary Server or Satellite
How do I generate a developer log for ZENworks Imaging?
The imglog file is created in the root directory ( / ).
NOTE:The log file is available only until the device is rebooted. To retain the log file, you must upload it to an FTP server.
How do I exclude a particular partition from ZENworks Imaging?
How do I prevent ZENworks Third-Party Imaging from restarting in the Auto mode?
Image Explorer help opens only in Firefox on Linux devices
The ZENworks icon properties page of a managed device that is in private network displays that the server IP address is not available
The third-party Imaging distro and tools are not immediately replicated on the Satellite
Unable to take an image of the managed device
Can't browse the file system on the specified server: com.novell.zenworks.datamodel.exceptions. InternalDataModelException: java.rmi.UnknownHostException: server_name.
If you have a DNS server in your network, ensure that it contains a DNS entry for the server you select in theoption in the Server and Path Information dialog box.
If you do not have a DNS server in your network, edit the operating_system_drive\windows\system32\drivers\etc\hosts file on the device running ZENworks Control Center to add the IP address and the DNS name of the server select in the option in the Server and Path Information dialog box.
In the Server and Path Information dialog box, try to browse for the image file.
The device might not pick up the assigned imaging task when booted to the Imaging Automatic mode
Boot the device in the Imaging Maintenance mode.
At the bash prompt, run the following commands:
In ZENworks Control Center, assign the task again to the device and boot the device to Imaging Automatic mode.
How to enable debug logs?
The Novell Proxy DHCP service is automatically stopped on the Imaging Satellite
In ZENworks Control Center, click thetab.
In the Server Hierarchy panel, select the Windows Imaging Satellite, then click> .
Click thelink next to the check box.
In the Configure Imaging Role dialog box, select.
A new workstation ID is created after restoring image on a non-registered device
Option 1: After restoring the image on a non-registered device, perform the following tasks on the device:
In ZENworks Control Center, click thetab > the folder.
Delete the workstation object.
Boot the device, and run the following command:
zac fsg –d
Reboot the device.
Option 2: Perform the following tasks:
Before taking the image of the device that has the ZDM 7.x agent and the ZENworks Agent with Asset Management installed, do the following on the device:
Run the zac fsg –d command.
In the Windows Services window, stop the Novell ZENworks Agent Service and change the service’sto .
Reboot the device.
Take the image of the device that has the ZDM 7.x agent and the ZENworks Agent with Asset Management installed.
After restoring the image on a non-registered device, do the following on the device whose image you have taken:
In the Windows Services window, change theof Novell ZENworks Agent Service to , and start the service.
Reboot the device.
novell-pbserv crashes during multicast imaging to 120 or more devices
Edit the %zenworks_home%\conf\preboot\novell-zenimgweb.conf file to uncomment the following entry, which is beneath the line “#Allow HTTP if HTTPS is not available”:
Restart the Novell ZENworks Preboot Service.
You might encounter an error message prompting you to restart Windows installation when the device boots up after the restoration of the ZENworks or WIM image on a Windows 7 or later
Windows could not complete the installation. To install windows on this computer, restart the installation.
If you restore an image of Windows on a bare machine that has a ZENworks partition, the machine fails to boot the second time after the image restoration
Boot the device in the ZENworks Imaging maintenance mode.
Run sidChange -i.
reboot the device.
Mounting an NFS partition from the Imaging kernel fails on a device that is booted in the ZENworks Imaging Maintenance mode
mount -t nfs IP_address_of_NFS_server:path_of_NFS_share /mnt/destination_directory
The following error messages are displayed:
mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Eihter use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified
mount -t nfs -o nolock IP_address_of_NFS_server:path_of_NFS_share /mnt/destination_directory
The SLES or SLED device with SATA drive fails to boot after the restoration of an image
Unable to take an image of a device if the Imaging Satellite is outside the L4 switch and the Primary Server is behind the L4 switch
Open the novell-zenimgweb.conf file that is located on the Imaging Satellite by using a text editor.
The file is located in the%ZENworks_Home%\conf\preboot\ directory on a Windows Imaging Satellite, and in the /etc/opt/novell/zenworks/preboot/ directory on a Linux Imaging Satellite.
Append the following entry:
Save and close the novell-zenimgweb.conf file.
Restart the Novell ZENworks Preboot Service (novell-pbserv).
Take the image of the managed device.
Dell DTK Configuration bundle fails on a device that does not have operating system installed
No work Assigned.
Create a logical disk:
Boot the device into the Dell DTK maintenance mode.
Execute the following command:
raidcfg -ctrl -c=0 -ac=cvd -ad=0:0:1 -sz=100MB -r=0 //raid 0 configuration with 100 MB size
PXE boot the device.
Unable to create a Dell partition on a Dell device by using the Dell DTK Configuration bundle
Can't Load Kernel File
copy upimg.bin from the latest Dell DTK distro that is integrated with ZENworks to the path relative to the TFTP server home directory.
Reassign the Dell DTK Configuration bundle to the Dell device.
PXE boot the Dell device.
Unable to use chkconfig with the novell-proxydhcp init script on SLES 11 or SLED 11
insserv: Script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
Managed devices are not reconciled to appropriate folders if you restore the image of a different operating system on the devices
In ZENworks Control Center, click.
Click theor folder that contains the device object you want to move.
Select the check box next to the device object you want to move.
The Move Device dialog box is displayed.
Choose the destination folder.
SUSE Linux installation or Red Hat Linux installation by using Preboot bundles fails
Unable to change the preconfigured master Primary Server whose tftp directory changes you want to replicate on all other servers at a specific schedule
Unable to apply the TFTP Replication settings. Remove the circular dependency for the Master Primary Server. For more information, see the Help.
Before changing the master Primary Server for the tftp directory replication, change the TFTP replication schedule for the existing Primary Server to.
Change the master Primary Server, then configure a new TFTP replication schedule.
When you upgrade a SLES operating system to SLES 11 SP2, an error occurs while loading the shared library files
libhd.so.12: cannot open shared object file: No such file or directory
The symbolic link to libhd.so.12.34 breaks when it is upgraded to libhd.so.15.xx
The hwinfo RPM is updated.
Unable to upload the tntfs.ko driver file after modifying or replacing the NTFSDriver.conf file
Login to ZENworks Control Center.
Click> > .
Re-download the tntfs.ko file by using the link provided.
Re-upload the tntfs.ko file.
Error occurs when a local imaging operation is performed on RAM
File name not displayed when an Imaging operation fails
Enable the developer logs by running the export DEVELOPER_LOG=a command in the Imaging distro mode.
The logs are stored in the /imglog file.
Search for the following strings to find the file on which the failure occurs as follows:
For Take Image operation: The last occurrence of the lnxfsTuxeraBaseImageToArchive string. This line and the next line contains the path to the file that has failed.
For Restore Image operation: The last occurrence of the ntfsTuxeraWriteFileFromArchive string. This line contains the path to the file that has failed.
For more information, see TID 7014246.
Screen flickers or gets distorted in a Distro environment
For example, append="mode=5 splash=silent showopts vga=0x0314 nomodeset".
For more information see Modifying Kernel Boot Parameters in Preparing Imaging Boot CDs, DVDs or bootable USB.
Unable to differentiate between WAIK and WADK uploads
File path for Linux: /srv/tftp/boot/WdsConfig.inf
File path for Windows: %ZENWORKS_HOME%\share\tftp\boot\WdsConfig.inf
Product.Name for WAIK32: Windows 7
Product.Version for WAIK32: 6,1,0,0
Product.Name for WADK32: Windows 8
Product.Version for WADK32: 6,2,0,0
Unable to upload 32-bit and 64-bit ImageX files at the same instance
On restarting the server, the pbserv or the novell-zmgprebootpolicy Imaging services are dead
Add the following line in the /etc/sysct1.conf file:
# allow processes to bind to the non-local address net.ipv4.ip_nonlocal_bind =1
Reload the /etc/sysct1.conf file by running the $ sysct1 -p /etc/sysct1.conf command.
ZENworks WADK Imaging works only on hardwares that are supported on Windows 8
Download the coreinfo.exe file from Windows Sysinternal (Download and Usage Information).
Run the tool to determine if the system has support for NX, PAE, and SSE2.
If your system is reported to support NX, PAE, and SSE2, you can use WADK to image the device. Else, use the compatible WIM mode based on WINPE 3.x.
IMPORTANT:In some 64-bit processors like Intel Xeon, there are two boot modes - Enabled and Capable. In both modes SMBIOS indicates that the processor is a 64-bit processor. However, if the mode is set to Capable, the system works as a 32-bit processor, and the 64-bit WADK does not boot. To use ZENworks Imaging on these 64-bit processors, the 64-bit mode should be set to Enabled in BIOS for 64-bit WADK to boot correctly. For more information, see System Management BIOS (SMBIOS) Reference.
NOTE:For VMware Virtual machines, only 32-bit, 64-bit WAIK or 32-bit, 64-bit WADK boot is applicable.
For more information, see TID 7013318.
The bootcd_tntfs.iso file creation fails on RHEL servers
Operating System on UEFI devices loses mount points on image restoration
Windows 8 login screen fails to appear after restoration of Windows 8 images from a Virtual machine on VMwareESX Servers