User manual NOD32 ESET REMOTE ADMINISTRATOR SERVER

[. . . ] 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. 2 Configuring the environment for remote installation . 54 Role and purpose of policies in the policy tree structure . [. . . ] On lower servers, the following options are available for policies inherited from upper servers: View Merged – Same as above View Override Part – This button applies for policies with the attribute Override any child policy. This option only shows the forced part of the policy – i. The one which has priority over other settings in child policies. View Non-force part – Has opposite effect of View Override Part – only displays active items, to which Override… is not applied. The policies can furthermore be imported from groups by clicking the Import from Groups. Policy rules can be imported/exported by clicking the Import. Button and, in addition, they can be created using the Policy Rules Wizard. Name conflicts (the existing and the imported policy names are identical) are solved during the import by adding a random string to the name of the imported policy. If a conflict cannot be resolved in this fashion (usually due to the new name being too long) the import finishes with the warning Unresolved policy name conflict. The solution is to delete or rename the conflicting policies or policy rules. 7 Assigning policies to clients There are two main rules for assigning policies to clients: 1. Local (primary) clients can be assigned any local policy or any policy replicated from upper servers. Clients replicated from lower servers can be assigned any local policy with the Down replicable attribute or any policy replicated from upper servers. They cannot be forced to adopt policies from their own primary server (to do so, you must connect to that server with ERAC). An important feature is that each client is assigned some policy (there is no such thing as clients with no policy). Also, you cannot take a policy away from a client. You can only replace it with another 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. For more information see chapter Virtual policies 54 . 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. [. . . ] 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. When the ESET SysRescue CD is created the driver is included in compilation so the user does not need to find it later. 4 Bootable USB device If you have selected USB device as your target medium, you can select one of the available USB media on the Bootable USB device tab (in case there are more USB devices). 5 Burn If you have selected CD/DVD as your target medium, you can specify additional burning parameters on the Burn tab. [. . . ]