本帖最后由 zx900930 于 2011-8-21 10:44 编辑
RELEASE NOTES
4. What’s new
This section describes the new features, enhancements, and most important problems fixed in F-Secure Client Security 9.20 RC.
4.1 New features and enhancements
· Support for Microsoft DirectAccess – the product is now compatible with Microsoft DirectAccess,
a new Windows 7 feature providing seamless secure connectivity from client computers to intranet resources over Internet.
· Support for Microsoft Network Access Protection (NAP) – the product supports integration with Microsoft NAP technology for controlling network access based on the system health of the host. For more information about Microsoft NAP integration and deployment refer to this knowledge-base article.
· Configurable host identity – when deploying the product with F-Secure Policy Manager, it is now possible to specify whether the managed host will be identified using SMBIOS UID or randomly generated GUID.
· Database update check randomization – to mitigate the so-called “AV storm” effect on virtual environments, it is now possible to configure whether to check database updates with a random interval at the system startup.
· New languages – localization to the following languages has been added: Chinese (P.R.C, Taiwan, Hong Kong), Estonian, Canadian French, Latin American Spanish, Romanian, Russian.
· Rebootless installation on Windows Vista/7 platforms – a system reboot is not anymore required when installing the product on Windows Vista and Windows 7 computers (except for MSI installations).
4.2 Fixed issues
The following issues have been fixed in this release since the previous (9.10) release:
· DeepGuard rejects configuration because of DAAS2 failure (CTS-78788)
· fslsp.dll causes crashing applications during Scan Manager update (CTS-78770)
· Firewall alert dialog has odd behavior when clearing individual alerts (CTS-78645)
· Application control is prompting about ping.exe with HIPS 4.0 installed (CTS-77883)
· Client Security 9.10 blocks all browser network traffic (CTS-79154)
· Application Control also blocks other network traffic while asking for permission (CTS-77424)
· AUA cannot resolve host names in DirectAccess tunnel (CTS-78338)
· Dynamic IP or DNS name of the host is not sent with autoregistration request (CTS-79132)
· Same host UID is generated on several computers (CTS-79085, CTS-79102)
· fsmautil tool is not working correctly (CTS-79285)
· FSDiag does not collects AUA logs (CTS-78892)
· Incorrect time zone information in Logfile.log (CTS-79936)
· Not possible to disable participation in Real-time Protection Network from the Advanced GUI
· After resetting host identity a new corresponding host appeared in Policy Manager while status information continued to be updated for host having old identity (CTS-79881)
5. Known issues
5.1 Installation, upgrade and uninstallation
Policies are not received immediately after reboot
In some cases, the installed client may not receive policies immediately after the 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 after upgrade
In case of an upgrade, some databases and engines used by the previous version might not be needed anymore. These are still visible in “Settings – Other settings – Downloads”, marked as “Not Installed”. This is normal, and after 7 days they will be automatically removed.
System might be slow for several minutes after the first reboot while the installation finishes
The system may start up slowly after the initial reboot after installation. This is because the installation is being finalized in the background, by downloading and installing various updates, etc.
The effect is more visible during the first reboot after a fresh installation, where more updates need to be downloaded. The local UI will inform about this if opened by having a blue status indicator, and a “Completing Installation” status text.
Sub-sequent reboots are not affected.
NAP Health Validator is not removed from configured health policies during uninstallation
During uninstallation references to F-Secure System Health Validator are not automatically removed from health policies. Computers having those polices in use start to be considered not compliant with health polices and become quarantined. To correct broken reference to F-Secure SHV please open health policies properties from Network Policy Server console (nps.msc) and confirm the automatic update.
5.2 DeepGuard
DeepGuard does not protect services in Windows 7 (CTS-65247)
When stopping a protected service from the command line or from the Services applet, DeepGuard fails to prompt about it. However, it still protects services from most malicious stop attempts. This problem only exists in the 32-bit version of Windows 7.
5.3 Browsing Protection
Disabling Browser Protection requires open browsers to be closed in order to be affected
If there are open browsers and the Browsing Protection feature is disabled, the change will only affect the open browser once it has been closed and restarted.
5.4 Anti-Virus
Incorrect engine versions are shown in policy settings
Incorrect engine versions are shown in the policy settings (the Plug-ins table, OID=1.3.6.1.4.1.2213.12.2.12) after clean installation. This affects scanning reports. The problem can be fixed by restarting FSGKHS service.
5.5 NAP Support
NAP Health Validator does not support multiple configurations
F-Secure System Health Validator does not support multi-configuration feature introduced in Microsoft Windows Server 2008 R2. |
发表于 2011-8-21 09:43:20
楼主
; 但是DG在32位Win7上出现了无法保护普通服务的BUG
有简中了，中文系列全都有了
修复了一个BUG，又来一个BUG。。。。
发表于 2011-8-21 19:48:16
