After Appliance migration, the ZENworks Server data will be available in the Micro Focus file path. ZENworks Server services will follow the Micro Focus naming convention, that is, Micro Focus will be prefixed with the name of the service. However, the ZENworks agent data will be available in the Novell file path and the related agent services will follow the Novell naming convention, that is, Novell will be prefixed with the name of the service. To view these changed filed paths and service names, see Viewing the Renamed Services and File Locations.
Run ZDC to verify the migrated ZENworks 2020 Update 2 Appliance System.
Ensure that all ZENworks services are running: microfocus-zenworks-configure -c SystemStatus
Ensure that the ZooKeeper service is up and running at all times to enable proper functioning of various ZENworks components. To verify the status of the ZooKeeper service, see the Diagnostics page in ZCC. For more information on the ZooKeeper component, see ZENworks Server in the ZENworks Primary Server and Satellite Reference.
If the Primary Servers in your zone are unable to communicate with the ZooKeeper service due to firewall restrictions, you can run the following configure action to open the ZooKeeper ports. You also need to ensure that the firewall allows client connections from other Primary Servers to the ZooKeeper services on port 6789. If the Primary Servers in your zone are unable to access the ZooKeeper service, then to open the ports, you can run the following Configure action on the server in which ZooKeeper is enabled.
microfocus-zenworks-configure -c ZENServicesFirewallConfigureAction -Doperation=add -Dservice=zookeeper
However, if the Primary Server that is within the DMZ is unable to access the ZooKeeper service within the corporate network, then you need to manually open the port 6789 in the corporate firewall.
For more information on the ZooKeeper ports, see ZENworks 2020 TCP and UDP Ports.
After appliance migration, the ZENworks server configuration will be copied from the old Novell file path to the new Micro Focus file path. However, the ZENworks server binaries and old configuration in the old file path is retained during the upgrade process. After verifying whether the upgraded version of the ZENworks Server is working as expected, you can run the Legacy Cleanup Utility provided with the build after a couple of weeks, to delete the retained server data.
For more information, see Running Cleanup Utility on a Linux or Appliance Server or Running the Cleanup Utility on Windows Server.
(Optional) When you run the cleanup utility, Sybase related files will be retained, which can be removed manually after verifying whether the upgraded ZENworks Server is working as expected.
If you have migrated from the Sybase database to any other database using the database migration tool, the database files, services, and Sybase packages might be retained in the Primary Server. To cleanup the data, run the following scripts on the Primary Server that had the Sybase database.
On Linux/Appliance: Run the script available in: /opt/microfocus/zenworks/install/downloads/tools/cleanupSybase.sh
After migrating to ZENworks 2020 Update 2, you should apply the ZENworks 2020 Update 2 – FTF 998 to mitigate the Log4j vulnerability. For information on downloading the FTFs, see https://portal.microfocus.com/s/article/KM000003058?language=en_US
After a successful upgrade, you can now view the renamed services and file locations introduced in the ZENworks 2020 Update 2 release.
Log Files: The log files will now be available in the new Micro Focus path (/var/opt/microfocus/log/zenworks). However, the log files will also be retained in the old Novell path (/var/opt/novell/log/zenworks).
Conf Files: The configuration files for only the ZENworks Server will now be available in the new Micro Focus path (/etc/opt/microfocus/zenworks). However, the configuration files for both the server and the agent will be retained in the old Novell path (/etc/opt/novell/zenworks).
Libraries: The libraries for only the ZENworks Server will now be available in the new Micro Focus path (/opt/microfocus/zenworks). However, the libraries for both the server and the agent will be retained in the old Novell path (/opt/novell/zenworks).
Configure actions have been renamed from Novell to Micro Focus. For example, the configure action novell-zenworks-configure -c CalibrateMemoryConfigureAction is now renamed to microfocus-zenworks-configure -c CalibrateMemoryConfigureAction. Configure actions that follow the Novell naming convention have been deprecated in this release and will be available along with the Configure actions that follow the Micro Focus naming convention.
ZENworks Server services have been renamed from Novell to Micro Focus. For example, novell-zenserver.service is renamed to microfocus-zenserver.service. Similarly, services such as novell-zenloader.service and novell-zenjoinproxy.service are renamed to microfocus-zenloader.service and microfocus-zenjoinproxy.service, respectively.
Certain services that follow the Novell naming convention, especially those related to the ZENworks agent, will still be applicable.
Therefore, while using the systemctl commands to start or stop services, ensure that you use the renamed services in the command.