User manual ESET REMOTE ADMINISTRATOR 4

[. . . ] ESET Remote Administrator 4 Installation Manual and User Guide ESET Remote Administrator 4 Copyright © 2010 by ESET, spol. No part of this documentation may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise without permission in writing from the author. reserves the right to change any of the described application software without prior notice. Customer Care Worldwide: www. eset. eu/support Customer Care North America: www. eset. com/support REV. [. . . ] Rather, they provide continuous maintenance of certain configuration settings for ESET security products. In other words, a Policy is a configuration that is forced to a client. 5. 3. 1 Basic principles and operation Access the Policy Manager by selecting Tools > Policy Manager. . . The Policy Tree on the left lists the policies that are present on individual servers. The right side is divided into four sections ­ Policy settings, Policy configuration, Policy action and Global policy settings ­ the options in these sections enable an administrator to manage and configure policies. The primary functions of the Policy Manager include creating, editing and removing policies. ERAS can use multiple policies which can inherit settings from each other or from policies from an upper server. The system of adopting policies from an upper server is called inheritance; policies that are created as a result of inheritance are referred to as merged policies. 5. 3. 2 How to create policies The default installation only implements one policy labeled "Server Policy". This name can be changed in the Policy settings > Policy name field. The policy itself is configurable from the ESET Configuration Editor ­ click Edit and define parameters for the selected ESET security product (or client). All parameters are organized into a comprehensive structure and all items in the Editor are assigned an icon. All inactive (greyed out) parameters will remain unchanged on target computers. The same principle applies to inherited and merged policies ­ a child policy will adopt only active parameters from a parent policy. The following options are available for new policies: policy name, linking to a Parent policy and configuration (configuration can be empty, copied from an existing policy, or copied from an . xml configuration file). Policies can only be created on the server you are currently connected to via ERAC. To create a policy on a lower server you need to connect directly to that server. Each policy has two basic attributes ­ Override any child policy and Down replicable policy. These attributes define how active configuration parameters are adopted by child policies. Override any child policy ­ Forces all active parameters to inherited policies. If the child policy differs, the merged policy will contain all active parameters from the parent policy (even though the Override. . . All inactive parameters from the parent policy will adjust to the child policy. [. . . ] If you select less than 512 MB, the recovery CD will be permanently accessed when WinPE will be running. External drivers ­ in this section you can insert drivers for your specific hardware (usually network adapter). Although WinPE is based on Windows Vista SP1 which supports a wide array of hardware, sometimes hardware is not recognized and you need to add the driver manually. There are two ways to introduce the driver into ESET SysRescue compilation manually (the Add button) and automatically (the Aut. [. . . ]