NOTE:ZENworks no longer supports Windows Server as a Primary Server from version 24.2 onwards. For more information, see End of Support for Windows Primary Server.
ZENworks Primary Server uses ports 443 and 7443 for running ZENworks API Gateway and ZENworks Administration Management Service respectively. If these ports are required for other applications, then these services need to be reconfigured to run on some other port. Using the information in this chapter, you can change the ports. These steps can be performed on both Appliance and Non-appliance Primary Servers to change the port numbers.
IMPORTANT:Before starting this process, ensure that you take a backup of the configuration files, certificates and the database.
Points to Remember: The following points should be considered if agents updates are automated:
If the zone has multiple Primary Servers, the following steps are optional. Because, when the device tries to connect to the server, it will be marked as bad as it is not reachable. Till the next refresh is triggered, it will use another server in the zone based on the configured closest server rules. When the next refresh happens on the agent, it will get the updated server list which will have the updated information and the agent will be updated with the new details.
In the case of a single Primary Server, when the agent comes up, the server will be marked as bad. To avoid this, delay the execution of the zac cc command and the agent restart. After the policy has been applied on the device, the server port has to be changed and then the agent service has to be restarted. A time delay can be added to execute the zac cc command and restart the agent.
Also, the initial-web-service file needs to be modified ONLY on the devices registered to the Primary Server whose port number has been changed. Grep the contents of initial-web-service and make sure whether it has the current server's IP or Hostname in it and then proceed.
During this process, the Primary Server will be down. Therefore, it is recommended to have an alternate Primary Server in the zone so that the managed devices will be able to connect to that server for any activity involving servers.
NOTE:The following actions should be performed in the same order.