Viewing versions With Secure 16.00

Hello, I installed With Secure Policy Manager 16.01 over a month ago and I started installing With Secure Client Security 16.00 however on the Policy Manager console when the computers are in version 16.00 the version it displays and version 15.30? Is there a way to correct this problem because I cannot have a global vision of the PCs with version 16.00 which remains disturbing
Answers
-
Hi @Neo14000
Thank you for reaching out the WithSecure Community,
Have you upgraded the Policy Manager and Client Security to version 16.x on top of the previous version 15.x? Are you currently using VPN software on your client machine?
We have encountered similar cases in the past where the Client Security in the Policy Manager (PM) console continues to appear as an older version. We suspect that there may be a connection issue when hosts report back to PM through a VPN connection. To troubleshoot this, we can try increasing the FSMA polling interval.
To increase the FSMA polling interval, please follow these steps:
In the Policy Manager console, select "Root" under the domain tree.Click on "Settings" and switch to the Advanced View.Navigate to "F-Secure Management Agent > Settings > Communications > Protocols > HTTP."Increase the value of the "Host Polling Interval" to 1 hour. Click the lock icon to finalize the changes.Distribute the updated policies.
If the problem persists, please follow these steps for additional investigation:
Check the connection issue between the Client and Policy Manager.
a) Open a web browser on the client machine and connect to your Policy Manager using the following format: https://<Policy Manager Server address or IP address>:<443> and http://<Policy Manager Server address or IP address>:<80>
If the client can contact the Policy Manager, the web page should display a message like "If you see this message, WithSecure™ Policy Manager Server is installed and is working fine."
NSlookup.
a) Open a command prompt with elevated mode.
b) Perform a nslookup for your Policy Manager server and check the result.
If the nslookup fails, you'll need to investigate connection issues within your network environment.
Let me know if you need further assistance or have any other questions.Best regards,
Sethu
Community Moderator | Technical Support Engineer
WithSecure™0 Like -
Hello,
I actually migrated my Policy Manager server to version 16.01 and some machines to Security Clients 16.00. To return to your recommendations, I can no longer find the "advanced settings" in version 16.00 of policy manager. Is this normal? When I enter the IP address of my WithSecure server it gives me the message that they communicate well together, the same goes for NSLookup, does this not come from Policy Manager which does not know the difference between 15.30. and 16.00? Have you ever had similar errors?
0 Like -
Hi @Neo14000
»I can no longer find the "advanced settings" in version 16.00 of policy manager. Is this normal?«
Follow these steps to enable the Advanced View in Policy Manager 16 (PMC):
- Open PMC (Policy Manager Console).
- Navigate to the "Tools" menu.
- Choose the "Preferences" option.
- In the "Appearance" tab, locate the option: "Make advanced mode available for Settings and Status pages."
- Enable the Advanced View by checking this option.
By following these steps, you can activate the Advanced View feature in Policy Manager 16.
»does this not come from Policy Manager which does not know the difference between 15.30. and 16.00? Have you ever had similar errors?«
Try the following troubleshoot steps:
a) Delete one of the problematic hosts (shows older ver 15.x) from domain tree.
b) Restart the computer.c) Re-import the host in the PM
You can now check the software version display in Policy Manager console and let us know how it goes.or re-install the CS 16 then import again.
Best regards,
Sethu
Community Moderator | Technical Support Engineer
WithSecure™0 Like -
I'm writing to you because after trying your method, it still doesn't work. Furthermore, as I have a fairly large computer population (over 1900 PCs), doing this by hand on each PC is likely to be a fairly repetitive task.
I've also noticed that if I install a version 16 PC directly, Policy Manager doesn't detect it; the PC remains in the "Unmanaged" category. On the other hand, if I install a version 15.30 and update it to 16.00, it works fine on the PC, even though the Policy Manager still displays the PC as "15.30".
Finally, since the PCs have been updated to version 16.00, Policy Manager displays a red cross in front of the host, which means that it hasn't been contacted for 30 days, and this for all the hosts on which I've performed the update.
0 Like -
Hi @Neo14000
In your particular situation, we kindly request you to collect the Wsdiag (formerly fsdiag) logs and contact our WithSecure Support team for further investigation. By providing us with these logs, we will be able to identify the exact root cause of the issue and offer you an appropriate solution. Thank you for your cooperation.
Best regards,
Sethu
Community Moderator | Technical Support Engineer
WithSecure™0 Like