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.

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/novell/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 novell-proxydhcp.service

  • Manual : systemctl disable novell-proxydhcp.service

  • Status : systemctl status novell-proxydhcp.service

Inconsistency while loading ZCC pages after Appliance upgrade

Explanation: After migrating your appliance from 11.4.x to 2017, or 2017 to 2017 Update 1, you might observe inconsistency while loading ZCC pages.
Action: After appliance migration, perform the following steps to remove duplicate JAR files:

  1. 1. Download the script from the following location:

  2. Copy the script to the migrated ZENworks 2017 Appliance System and Run as a root user.

  3. Assign executable permission for the script file by running the following command:

    chmod +x mvOldJars.sh.

  4. Run the script by running the following command:

    ./mvOldJars.sh

  5. Restart the ZENworks services using the following command:

    novell-zenworks-configure -c Restart