A.0 Troubleshooting

The following sections provides solutions to the problems you might encounter while deploying and Configuring ZENworks Appliance:

ZENworks Appliance disk expansion does not take effect

Explanation: On ZENworks appliance, the function to expand the /vastorage disk on the web administration console does not take effect if the appliance contains any additional disk which is mounted to a directory below /vastorage.

The system does not report any errors and request the administrator to restart the appliance. The size of the /vastorage disk is unchanged after the appliance has been restarted.

Action: On a command line, stop all ZENworks services using the microfocus-zenworks-configure -c Start command and then unmount the additional disk umount /dev/sdc1 before using the web administration console to expand the /vastorage disk.

After appliance migration, the appliance goes into the emergency mode

Source: ZENworks Appliance
Explanation: An appliance with content-repo mounted on a separate disk (3rd disk), after migrating, the appliance goes to the emergency mode.
Action: While in the emergency mode, in /etc/fstab, update the x-systemd.requires=/vastorage parameter to the mounted content-repo, as shown in the below example: 
/dev/sdc1   /var/opt/microfocus/zenworks/content-repo    ext4    acl,user_xaatr,x-systemd.requires=/vastorage     1      2

After making the changes, reboot the appliance for the changes to take effect.

Error is displayed when you try to configure the ZENworks appliance with a.pfx certificate

Source: ZENworks Appliance
Explanation: While configuring the ZENworks appliance for the first Primary Server, if you upload an external CA in the.pfx format, the This certificate chain does not match the Root certificate error is displayed.
Possible Cause: The.pfx file does not contain the self-signed root certificate.
Action: Log in to ZENworks Appliance. On the ZENworks Appliance home page, under ZENworks, click Terminal & File Explorer.

Perform the following steps to upload files to ZENworks Appliance. Alternatively, you can use any WinSCP tool to upload the files.

  1. In the File Explorer, select a folder where you will run the command to create a.pfx file and click Upload.

  2. Select the file to upload and click Open.

  3. Click Start Upload in the File Upload dialog box.

Run the following command to create a.pfx file:

openssl pkcs12 -export -out <name>.pfx -inkey <key> -in <server.cer> -certfile <int+cer.cer>

Specify the following values in the command:

  • name: name of the.pfx file

  • key: key in the.pem format

  • server.cer: Server certificate

  • int+cer.cer: The root certificate and intermediate certificate. Note: It should not contain the server certificate.

Unable to Deploy the Appliance on VMware vSphere

Source: The source of the message.
Explanation: Deploying the ZENworks Appliance on VMware vSphere 6.x fails with a "TypeError: Cannot read property 'keyValue' of undefined" error.
Action: Perform the following steps:

  1. Download the embedded host client available in the following link:

    https://flings.vmware.com/esxi-embedded-host-client

  2. Upload the downloaded VIB file into the datastore, and then install the file using the following command:

    [root@ESXI~] esxcli software vib install -v /vmfs/volumes/<your_datastore> /esxui-signed-12086396.vib

  3. After successfully installing the VIB, restart the appliance deployment.

The ntpd service is disabled even when the NTP Time Source is configured

Explanation: In the ZENworks Appliance, by default, the ntpd service is disabled even when the NTP Time source is configured, and the ntpd service might not run automatically after a device reboot.
Action:

  1. In the ZENworks Appliance terminal, open Yast, select System > Date and Time, and then select Other Settings.

  2. Select Synchronize with NTP Server and then select the Run NTP as daemon option. After accepting the changes, the ntpd service is enabled and the ntpd service runs automatically after the device reboots.

System Update Fails On Windows 10 Devices

Source: ZENworks 2020
Explanation: When you deploy ZENworks 2020 Update 1 on Windows 10 64-bit devices, the system update might fail.
Action: Redeploy the update on the devices on which the update has failed.

Registration of Online Updates fails using the local SMT

Source: ZENworks 2020, ZENworks 2020 Update 1
Explanation: Unable to register for online updates using the local SMT in the appliance console.
Action: In the Appliance terminal, run the zypper pd -i command.

If a product with Internal Name as SLES is displayed along with installed ZENworks product, perform the following actions.

  1. Delete the SLES.prod file available in the following location:

    /etc/products.d/SLES.prod

  2. Run the zypper pd -i command and then verify if the command displays only ZENworks as the installed product.

Now, you will be able to register to the SMT server.

Appliance migration fails due to inadequate disk space

Source: ZENworks 2020
Explanation: The appliance migration from ZENworks 2017 to ZENworks 2020 fails and "No space left on device" message is logged in the zcmMigration.log (/tmp/zcmMigration.log) file.
Action: Before starting the appliance migration, in the ZENworks 2017 Appliance, rename the database folder available in the /vastorage/var/opt/microfocus/zenworks/ location to database.old, deploy a new ZENworks 2020 Appliance and then restart the migration.

NOTE:Ensure that you rename the folder, deploy a new ZENworks 2020 appliance, and then attach the disk to the ZENworks 2020 appliance.

Proxy DHCP service is not listed in ZENworks Appliance

Source: ZENworks 2020
Explanation: When you update ZENworks Appliance from 2017, Update 1, Update 2 to 2017 Update 3, the Proxy DHCP service is not listed in the System Services page on Appliance admin console.
Action: To manage the Proxy DHCP services, perform the following:

To set the service as Automatic or Manual, or to check the status of the service, from the Appliance command prompt, run the related command:

  • Automatic : systemctl enable microfocus-proxydhcp.service

  • Manual : systemctl disable microfocus-proxydhcp.service

  • Status : systemctl status microfocus-proxydhcp.service