Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
Client Security for Mac is not able to connect to the Policy Manager Server after installation - F-Secure Community
<main> <article class="userContent"> <h3 data-version="4" data-article="000014294" data-id="issue">Issue:</h3> <p>Client Security for Mac is not connecting to Policy Manager Server after installation. The host does not appear in the <b>pending </b>list.</p> <h3 data-id="resolution">Resolution:</h3> <p>Why a Client Security for Mac host will not connect to the Policy Manager Server can be a result of several different reasons:<br></p><ul><li>The Policy Manager Address and ports were misconfigured during the export process</li><li>The .mpkg filename was modified after exporting the installer from the Policy Manager Console</li><li>Certificate issue </li></ul> 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 <a rel="nofollow" href="https://www.f-secure.com/en/business/downloads/client-security-for-mac">Downloads page</a>.<br><br>1. Make sure that you have used the correct Policy Manager Address when exporting the .mpkg installer.<br><br>2. Make sure that you have not modified the .mpkg filename:<br><br>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.<br><br>Check these files, if they exist and license is active, product is installed correctly: <ul><li>/usr/local/f-secure/fsmac/sysconfig/pm_fingerprint</li><li>/usr/local/f-secure/fsmac/sysconfig/pm_address</li></ul> 3. Check for any certificate issues. We have this <a rel="nofollow" href="http://community.f-secure.com/business-suite-en/kb/articles/8933-resolving-connectivity-issues-between-client-security-for-mac-and-policy-manager">KB article</a> that includes instructions how to troubleshoot connectivity issues caused by certificates.<br> <p>Article no: 000014294</p> </article> </main>