I installed a new ZCM Server into our existing Zenworks 10 zone and during testing this server I found that using the agent package from this newly installed server the casa agent tries to connect to the ZCM server using a wrong port. We have configured our ZCM Zone to use alternate HTTP(s) port(s) for agent to server communication ( 8080/8443 instead of port 80/443).

casaauthtoken.log from a workstation with working casa agent:

[6AC-7DC] [13:34:49] CASA_AuthToken -ObtainAuthTokenFromServer- Start
[6AC-7DC] [13:34:49] CASA_AuthToken -ObtainAuthTokenFromServer- Hostname = wwwwww.xxx.yyy.at
[6AC-7DC] [13:34:49] CASA_AuthToken -ObtainAuthTokenFromServer- port = 8443
[6AC-7DC] [13:34:49] CASA_AuthToken -OpenRpcSession- Start
[6AC-7DC] [13:34:49] CASA_AuthToken -OpenRpcSession- Host = wwwwww.xxx.yyy.at
[6AC-7DC] [13:34:49] CASA_AuthToken -OpenRpcSession- HostPort = 8443

and casaauthtoken.log from a workstation with non-working casa agent:

[610-E8C] [14:01:42] CASA_AuthToken -ObtainAuthTokenFromServer- Start
[610-E8C] [14:01:42] CASA_AuthToken -ObtainAuthTokenFromServer- Hostname = wwwwww.xxx.yyy.at:8443
[610-E8C] [14:01:42] CASA_AuthToken -ObtainAuthTokenFromServer- port = 443
[610-E8C] [14:01:42] CASA_AuthToken -OpenRpcSession- Start
[610-E8C] [14:01:42] CASA_AuthToken -OpenRpcSession- Host = wwwwww.xxx.yyy.at:8443
[610-E8C] [14:01:42] CASA_AuthToken -OpenRpcSession- HostPort = 443

Notice that in the working client log the Host does not contain the port 8443 and the HostPort knows the rhight one and the non working client does contain the port 8443 and the HostPort does not know the right port.
In the ZCC on both servers the configuration is identical, so I think the local configuration on the newly added server has wrong information inside, but where?
Is this a known bug or is there a short way (editing some files) to repair this misconfiguration?

Any help welcome.

Werner Seifert
Senior Systems Engineer
Johannes Kepler University Linz/Austria