background image

The host UID generation algorithm was changed to be tiered to the host’s hardware and not change 
in time. This was done to avoid problems where duplicated hosts sometimes appeared in Policy 
Manager’s domain tree after the client’s re-installation and also when used in some virtual 
environments. The host UID is now 32 characters long instead of 16 characters long as before. 

4.2.

                              

 Support for Active Directory integration 

To support Active Directory integration in Policy Manager, the client now reports computer’s 
Distinguished Name and GUID AD properties via statistics. 

5.

    

Fixed Issues 

 

Unnecessary Application Control prompts for non-modified applications were shown in some 
cases after computer restart.  

 

The “Virus removed” flyer shown during Real-Time Scanning whenever new virus was found 
caught the focus which might cause inconveniences for the user (CTS 70164). 

 

Firewall rules configure to generate alerts didn’t show pop-ups and sent alerts to Policy 
Manager when triggered for outbound traffic (CTS 62001). 

 

It was not possible to trigger manual scanning from Windows shell extension when connected 
with Remote Desktop session (CTS 70768). 

 

Users were able to modify Quarantine and DeepGuard tables even when changes from local 
GUI were prohibited by the Policy Manager admin. 

 

Hotfixes applied for the previous product version were still shown in Policy Manager after 
upgrade (CTS-71303). 

 

“Scan and remove viruses from e-mails” checkbox display logic was corrected to reflect both 
the inbound and outbound traffic settings. Previously, it was displayed basing on outbound 
setting state only (CTS-72757). 

 

Duplicated entries appeared in Add/Remove programs applet after upgrading Client Security 
using MSI package. 

 

Support of non-standard http-proxy header “Proxy-Connection: close” was added to FSAUA 
for compatibility with i-Filter http-proxy (CTS-64635, CTS-70694). 

6.

    

Known Issues 

6.1.

                              

Installation and Uninstallation 

In some circumstances, the newly installed client does not receive policies 
immediately after reboot. 

The client will usually recover automatically after some time, and receive the new policy. If not, a 
reboot should help. 

Unused databases are still visible for some time after upgrade. 

Reviews: