Issue:
Client Security for Mac is not connecting to Policy Manager Server after installation. The host does not appear in the pending list.
Resolution:
Why a Client Security for Mac host will not connect to the Policy Manager Server can be a result of several different reasons:
- The Policy Manager Address and ports were misconfigured during the export process
- The .mpkg filename was modified after exporting the installer from the Policy Manager Console
- Certificate issue
Before you start troubleshooting, make sure that you have tried the installation with the latest Client Security for Mac installer. You can find the latest installers on the Downloads page.
1. Make sure that you have used the correct Policy Manager Address when exporting the .mpkg installer.
2. Make sure that you have not modified the .mpkg filename:
When you export the .mpkg installation package from the Policy Manager Server, the Policy Manager address and activation key is embedded in the filename. If the filename is modified, the client will be unable to read the correct Policy Manager address and activation key during installation.
Check these files, if they exist and license is active, product is installed correctly:
- /usr/local/f-secure/fsmac/sysconfig/pm_fingerprint
- /usr/local/f-secure/fsmac/sysconfig/pm_address
3. Check for any certificate issues. We have this KB article that includes instructions how to troubleshoot connectivity issues caused by certificates.
Article no: 000014294