User manual NOD32 ESET REMOTE ADMINISTRATOR CONSOLE

[. . . ] 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. 58 Each server is a standalone unit and policies are defined locally . 58 Each server is administered individually - policies are managed locally but the Default Parent Policy is inherited from the upper server . [. . . ] An important feature is that each client is assigned some policy (there is no such thing as clients with no policy). If you do not want to apply a configuration from any policy to a client, create an empty policy. 1 Default Primary Clients Policy One method of assigning policies is automatic application of the Default Primary Clients Policy, a virtual policy that is configurable in Global Policy Settings. 2 Manual assigning There are two ways to manually assign policies: Right-click a client in the Clients pane and select Add Policy from the context menu, or click Add Clients > Add/Remove in the Policy Manager. Clicking Add Clients in the Policy Manager opens the Add/Remove dialog window. If the Down replicable policy is selected, the window will also list clients replicated from lower servers. Select clients to receive the policy by using the drag-and-drop method or clicking >> to move them to Selected items. Newly selected clients will have a yellow asterisk and can still be removed from Selected items by clicking the << or C button. NOTE: After confirming, if you reopen the Add/Remove dialog window, clients cannot be removed from Selected items, you can only replace the policy. Rules are applied immediately after the client connects to the server; they have priority over the Default Primary Clients Policy and over manual assigning. The Default Primary Clients Policy only applies if the client does not fall under any current rules. Likewise, if there is a manually assigned policy to be applied and it is in conflict with the policy rules, the configuration forced by the policy rules will take precedence. Policy rules have a tab within the Policy Manager, where they can be created and managed. The process of creation and application is very similar to that of rule creation and management in email clients: each rule can contain one or more criteria, the higher the rule is in the list, the more important it is (it can be moved up or down). Then enter a Name, Description, Client filter parameter and Policy (a policy that will be applied to any clients matching the specified criteria). The available criteria are: (NOT) FROM Primary Server – if (not) located on primary server IS (NOT) New Client – if it is (not) a new client HAS (NOT) New Flag – applies to clients with/without the New Client flag. Primary Server (NOT) IN (specify) – if name of the primary server contains/does not contain. ERA GROUPS IN (specify) – if client belongs to the group… ERA GROUPS NOT IN (specify) – if client does not belong to the group… DOMAIN/WORKGROUP (NOT) IN (specify) – if client belongs/does not belong to the domain… Computer Name Mask (specify) – if computer name is . HAS IP Mask (specify) – if client belongs to the group defined by the IP address and mask… HAS IP Range (specify) – if client belongs to the group defined by the IP range… HAS (NOT) Defined Policy (specify) – if client does (or does not) adopt the policy… Product Name (NOT) IN - if product name is. Last Connection IS (NOT) older than (specify) - if last connection is older than. IS (NOT) Waiting For Restart - if client is waiting for restart Policy rules can be imported/exported from/to an . Xml file and they can also be created automatically by using the Policy Rules Wizard, which allows you to create a policy structure based on the existing group structure and map created policies to groups by creating correspondent policy rules. [. . . ] There are two ways to introduce the driver into ESET SysRescue compilation manually (the Add button) and automatically (the Aut. In the case of manual introduction, you need to select the path to the corresponding . In the case of automatic introduction, the driver is found automatically in the operating system of the given computer. We recommend using automatic introduction only if ESET SysRescue is used on a computer that has the same network adapter as the computer on which the ESET SysRescue CD was created. [. . . ]