FSPM + Proxy - Question

Hi,

 

 

we got this constellation:

 

FSPM11 running on a Server here

FSPPM2 running on a Server at a different location

Clients runnign on the same localtion as FSPPM.

 

Actually there is 4 Clients that have been pushed client security there.

The Settings on clilent reports that there is a FSPM Server and also there is FSPPM Server.

They do get settings pushed from FSPM Server and they do get automatic updates.

However they report that they use the FSPM Server for updates and not the FSPPM.

We want the Clients to use the FSPPM as Update Server because if all clients drag updates from the FSPM Server this would kill our bandwith here.

 

Can anyone please give some advice?

 

Greets

Sebastian

Answers

  • FedericoFederico Posts: 38

    Hi Sebastian,

     

    Assuming the settings are correct, by default the clients will fallback to the Policy Manager Server if the Policy Manager Proxy is not available. I would suggest to check if the connection from the clients to the Policy Manager Proxy is working. Please check if the Policy Manager Proxy is reachable at the IP address (or hostname, depending on what you have used) and at the correct port.

  • sw2090sw2090 Posts: 14

    hi

     

    Policy-Manager-Proxy is reachable via http. It tells me it is working fine if I open the url in a browser:

    "If you can see this message, FSPMP v 2.00 is installed in working fine."

     

    Though all clients do report that they use the FSPM Server as update server in their settings.

    I want them to use FSPMP.

     

    Greetings

    Sebastian

  • GaryGary Posts: 70

    Hi Sebastian,

     

    If the configurations on the clients are correct and the connection to the Proxy server is fine, the AUA log (F-Secure Client > Settings > Other settings > Downloads > View log file) should have similar entries as the following:

     

    [ 2600]Thu May 1 15:13:35 2014(2): Connecting to http://PMServer.f-secure.com (Proxy.example.com, no HTTP proxy)...
    [ 2600]Thu May 1 15:13:35 2014(2): Update check completed successfully. No updates are available.

     

    * PMServer.f-secure.com = Your Policy Manager Server address
    * Proxy.example.com = Your Proxy Server address

     

    Regards,

    Gary

  • sw2090sw2090 Posts: 14

    344]Mon May 05 02:22:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 02:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 02:32:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 02:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 02:42:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 02:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [ 1120]Mon May 05 02:52:55 2014(3):  Database 'aquawin32' version '1399245516' db_size '369701848', free '8408645632'
    [ 1120]Mon May 05 02:52:56 2014(3):  Downloaded 'F-Secure Aquarius Update 2014-05-04_03' - 'aquawin32' version '1399245516' from <fspm>, 369701848 bytes (117775 bytes downloaded)
    [  344]Mon May 05 02:52:58 2014(2):  Update check completed successfully.
    [ 1544]Mon May 05 02:53:18 2014(3):  Installation of 'F-Secure Aquarius Update 2014-05-04_03' : Success
    [  344]Mon May 05 03:02:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 03:02:47 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 03:12:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 03:12:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 03:22:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 03:22:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 03:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 03:32:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 03:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 03:42:47 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 03:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 03:52:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 04:02:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 04:02:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 04:12:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 04:12:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 04:22:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 04:22:49 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 04:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 04:32:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 04:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 04:42:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 04:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 04:52:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 05:02:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 05:02:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 05:12:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 05:12:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 05:22:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 05:22:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 05:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 05:32:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 05:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 05:42:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 05:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 05:52:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 06:02:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 06:02:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 06:12:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 06:12:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 06:22:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 06:22:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 06:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 06:32:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 06:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 06:42:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 06:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 06:52:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 07:02:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 07:02:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 07:12:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 07:12:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 07:22:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 07:22:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 07:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 07:32:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 07:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 07:42:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 07:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 07:52:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 08:02:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 08:02:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 08:12:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 08:12:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 08:22:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 08:22:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 08:32:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 08:32:47 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 08:42:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 08:42:43 2014(2):  Update check completed successfully. No updates are available.
    [  344]Mon May 05 08:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...
    [  344]Mon May 05 08:52:43 2014(2):  Update check completed successfully. No updates are available.

    fspm iis the  Policy Manager which is here, fspmp is Policy Manager Proxy  at the Site.

    As I see in this log the client does download the updates from fspm and not from proxy. It just uses the Proxy for checking if there are updates?

     

    Gruß

    Sebastian

  • GaryGary Posts: 70

    Hi sw2090,

     

    Perhaps the following examples will give you a clearer picture:

     

    Example of update check via Policy Manager Proxy Server:

    [  344]Mon May 05 02:52:41 2014(2):  Connecting to http://<fspm&gt; (http://<fspmp>:8080, no HTTP proxy)...

     

    Example of update check via Policy Manager:

    [  344]Mon May 05 02:52:41 2014(2):  Connecting to http://<fspm&gt; (no BW proxy, no HTTP proxy)...

     

    Based on the AUA log the update was from the PM Proxy Server.

     

    Best regards,

    Gary

This discussion has been closed.