User manual F-SECURE POLICY MANAGER 9.0 ADMINISTRATOR GUIDE

[. . . ] Managing more than 5000 hosts requires P4 3 GHz processor or faster. Memory: 512 MB of RAM. Managing more than 5000 hosts requires 1 GB of memory. Disk space: Display: 200 MB of free hard disk space. Minimum 16-bit display with resolution of 1024x768 (32-bit color display with 1280x1024 or higher resolution recommended). Managing more than 5000 hosts requires a 100 Mbit network. Network: 10 | F-Secure Policy Manager | Introduction Main components The power of Policy Manager lies in the F-Secure management architecture, which provides high scalability for a distributed, mobile workforce. [. . . ] The Installed version field displays the currently installed product version. Failed Completed (Empty field) · If a domain is selected, the Progress field displays one of the following: <number> hosts left - <number> installations Number of hosts left and number of failed failed installations. Click the button in the Progress field for detailed status information. Completed The installation or uninstallation operation succeeded on all hosts. 46 | F-Secure Policy Manager | Using Policy Manager Console (Empty field) No operations are active. The Installed version field displays all currently installed product versions. 3. The Installation editor launches the Installation wizard, which queries the user for the installation parameters. The Installation editor then prepares a distribution installation package that is customized for the specific installation operation. Note: The Start button is used to start the installation operations selected in the Version to install field. If the Installation editor is closed without first clicking the Start button, then all changes will be discarded. Because the installation operation uses policy-based triggering, you must distribute new policy files. The policy file will contain an entry that tells the host to fetch the installation package and perform the installation. Note that it may take a considerable length of time to carry out an installation operation. This may happen if an affected host is not currently connected to the network, or if the active installation operation requires a user to restart his host before the installation is completed. If the hosts are connected to the network and they send and receive policy files correctly, then there could be a real problem. The host may not be correctly acknowledging the installation operation. In any case, it is possible to remove the installation operation from the policy by clicking Stop all. This will cancel the installation operations defined for the selected policy domain or host. It is possible to stop all installation tasks in the selected domain and all subdomains by selecting the Recursively cancel installation for subdomains and hosts option in the confirmation dialog. The Stop all button is enabled only if the current host or domain has an installation operation defined. If a host has already polled the previous policy file, it may try to carry out the installation operation even though it is no longer visible in the Installation editor. Remote uninstallation: Uninstallation can be performed as easily as an update. A distribution package is created that contains only the software needed to uninstall the product. If the product does not support remote uninstallation, the Installation editor does not display an option for uninstallation. [. . . ] Installation of some products failed. 200 Chapter 10 FSII remote installation error codes Topics: · Error codes This section describes the most common error codes and messages that can occur during the Autodiscover Windows Hosts operation. 96 | F-Secure Policy Manager | FSII remote installation error codes Error codes Here you will find descriptions for the most common error codes and messages appearing in remote installation operations. Windows error codes Error code 1057 5 Description The user account name is invalid or does not exist. If using This Account, it is important that the administrator is logged on to the Policy Manager Console machine with domain administrator privileges. With Domain Trusts, make sure you have logged on to Policy Manager Console using the account from the trusted domain. [. . . ]