Upgrade F-Secure Management Server from 15.21 to 16.0 - troubles.
I have: Debian 9 with F-Secure Management Server and Windows 10 stations with F-secure Business Clients. Mangement Console is on Windows 10.
After upgrade Management Server from 15.21 to 16.00 (and of course management console) i can push installations from Server to Workstations, but:
Installation is complete on station and station can get signatures from server, but installation stucks on server on "In progress" and server still says version 15.21 (dont finish it). Worse: When i change anything in polisy station never get that update.
I was try do test upgrade on few workstations, so it seems its not a problem of workstation/s. Comunnication works fine (download signatures from server to workstations works fine). Of course server is "visible" on LAN by name and ip address.
After that upgrade when i manually export client installation file and install it on workstation, management server did not notice it and cant join "new workstation" to polisy server. "Pending" is still 0.
How to check what is going on after upgrade ?
Best Answer
-
Hi,
thanks for interesting in topi i have found "my bug".
In tree i have root → domain → OU's …
My problem was i put name of Polisy Management Server address in Settings on "domain" level (so OU's) have it becuase are "lower". In my installation that was enough for clients 15.21.
I was put name of server at root level (wich was blank and distribute polisy) and upgrade the server itself again.
That works ! Everything is right now.
I have no idea why stations need this on "root" level in clients 16.00 (clients 15.21 doesnt need it), but this way or another everything works good.
Upgrade stations, information to server after push installations, changes of polisy on server to clients …globally ALL is ok.
So topic to close.
2
Answers
-
I was forget: After that upgrade when i manually export client installation file and install it on workstation, management server did not notice it and cant join "new workstation" to polisy server. "Pending" is still 0.
0 -
Hi @Zibi0802
Sorry to hear that you are having issues distributing policy.
Can the host reach Policy Manager server via HTTP browser ?
Test the connectivity from the host to Policy Manager Server by using the HTTP and HTTPS protocol:
- Open any web browser on the host that has F-Secure Client Security installed.
- Enter the IP address of the Policy Manager and press Enter.
- Repeat the test, only this time by using the HTTPS protocol (for example https://192.168.0.10:443/).
If the HTTP (automatic updates) and HTTPS (management agent) connections are working, a webpage from the Policy Manager Server should be displayed.
If the connection fails, troubleshoot the network connectivity between the host and Policy Manager at your end. Verify whether the host and the server can reach each other (for example through corporate firewall, switches or a proxy).
0 -
Hi,
If i open web browser both sites (http, and https) are reachable. Except on https is warning before connection becuase cert is unthrusted. So seems communications works fine (i dont know why it should change if in 15.21 all is ok).
I was try turn off station firewall, reset_id … but its not works. i will post here after "next tests"
0 -
Hi @Zibi0802
Thank you for the reply.
Kindly ensure certificates are valid on both host and Policy Manager Server. Alternatively, you can run our Connectivity Tool here - https://download.withsecure.com/connectivitytool/ConnectionChecker.exe
If issue persists, please submit a support case with WSDiag logs from Policy Manager Server and affected host, so we can check if there is a missing certificate.
0 -
Ok, next tests:
1 .push installation 16.0 still fails (dont connect to Policy Manager Server)
2. copy exported installation - fails (dont connect to Policy Manager Server)
3. remove client from console - reinstall Client (after uninstall tool) - fails (dont connect to Policy Manager Server)
4. reinstall Client (after uninstall tool) - install back 15.21 works - client visible in server and get updates/policy.
So i think its some problem with client installation
tried on 3 stations with windows 10
… so nothing at this time…
0
Categories
- All Categories
- 4.7K WithSecure Community
- 3.6K Products
- 1 Get Support