We have just released the Beta versions of the new 12 series of Client Security and Policy Manager.
Policy Manager 12 for Windows, and Client Security Premium contain several new added-value features to improve security and productivity.
In addition, the new version includes several smaller improvements to enhance the manageability and control of your IT environment, as well as improved tools for daily tasks.
Contact your reseller partner to join the Beta program to experience the superior power of manageability and control the new version gives you!
I tried FSPM 12.00 beta and FSCS 12.00 beta in a Win7 Enterprise 32-bit VM.
Used port 85 for host, 8085 for console, 8086 for web reporting in FSPM. Comms setting for client was specified as: http://127.0.0.1:85
Problem: After instalation, FSCS 12 Beta reports in the PMC as a new host, but doesn't seem to notice policies sent by PMC.
Changed IE settings to mmadate SSL30 and TLS 1.x, turned off the F-Secure IS/DFW personal firewall, changed comm settings on client to http://localhost:85 and policy reception started to work.
Turned firewall on, reverted comm settings on client to http://127.0.0.1:85 and it still works.
Previously, with FSPM 11.31 or earlier, I have't experienced such hiccups. I don't understand this sequence of events, but maybe someone has an idea?
Thanks in advance, Yours Sincerely: Tamas Feher, 2F 2000, Hungary.
When FSCS 12.00 beta blocks a webpage due to "parental control" categories, the landing page does not say why the page was blocked, the name of category (adult, hate, gambling, etc.) is not provided.
This can be problematic, since the workstation end user will be deprived of information he/she needs in order to complain of a false blocking. (Especially that the landing page provided by FSCS 12 beta doesn't include a submit button for re-categorization.)
Thanks for your kind attention, Sincerely: Tamas Feher, Hungary.
Now I think this issue is related to some tricks M$ implemented in Win7, where 127.0.0.1 resolution to localhost doesn't work without DNS access by default. (Must be edited manually in the "hosts" file.)
Best Regards: Tamas Feher, 2F 2000, Hungary.
Thank you for your feedback. Yes, block page does not provide any information on the category itself. The category information for specific page in the block page will be taken into consideration for future improvements.
We are also considering various reporting possiblitities for example reporting false positives with most easiest way. These are under discussion for future releases. Most likely end user will not have this possibility of "re-categorization" in the blocking page as the enforcement of the categories will be done by IT admin and end-user should not be able to do this.
Is it wise to eliminate Win 2003 support from FSPM 12?
According to Microsoft, extended Support End Date for Windows Server 2003R2 is 7/14/2015.
Usually 3rd party vendors provide 1 or 2 years more, before ditching the platform. (For example WinXP was abandoned by Microsoft in April 2014, but F-Secure still supported it in version 11 and some other antivirus vendors will support WinXP even in those product edition that will appear in mid-2016.)
I think there will be complaints among business F-Secure customers because of the premature Windows 2003 abandonment. For example Hungary is full of ancient W2003 boxes still serving.
Thanks for your kind attention, Sincerely:
Tamas Feher, 2F 2000 Kft., Hungary.
FSAVCS 12.00 RC Release Notes say:
> For this version, Web content control, Connection control and WTS advanced
> protection features work only if the product is connected to the Beta update channel.
For this requirement, the F-Secure support website knowledge base gives guidance:
> How to configure Policy Manager to download updates from beta update server?
> 1. Use Regedit to modify Windows registry: ...
> 2. Restart the "F-Secure Automatic Update Agent" service
The problem is, apparently there is no such service process in F-Secure version 12, anymore?
Best Regards: Tamas Feher, Hungary.
Installation of PM on server OS, alone or with SS/ESS has fsaua service.
Installation of PM on client OS will have it if it is installed alone, and will or will not have it depending on the order of installation of CS/PM if this products are installed together. For the scenario, where FSAUA is missing as a service, restart of FSMA service will do the trick.
BTW, a bit offside question. Do you think/know, that installation of PM on a client OS is a widly used case? As far as i remember it's not recommended scenario, and PM installation is showing a notification about that.
> Do you think/know, that installation of PM on a client OS is a widly used case?
I think many use that scenario, at least for testing purposes.
Yours Sincerely: Tamas Feher, Hungary.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link: