Red Hat LINUX VIRTUAL SERVER 4.6 - ADMINISTRATION Guide de l'utilisateur Page 36
- Page / 92
- Table des matières
- DEPANNAGE
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
Install on Windows with login scripts
Using Windows login scripts to install the agent can be an efficient way to make sure all systems in
your network have an agent installed.
Before you begin
• McAfee recommends first creating segments of your System Tree that use either
network domain names or sorting filters that add the expected systems to the desired
groups. If you don’t, all systems are added to the Lost & Found group, and you must move
them manually.
• Consult your operating system documentation for writing login scripts. The details of the
login script depend on your needs. This task uses a basic example.
• Create a batch file (ePO.bat) that contains commands you want to execute on systems
when they log on to the network. The content of the batch file depends on your needs,
but its purpose is to check whether the agent has been installed in the expected location
and, if not, run FramePkg.exe to install the agent. Below is a sample batch file that does
this. This example checks the default installation folder for an agent file and, if not
present, installs the new agent.
IF EXIST “C:\Program Files\McAfee\Common Framework\FRAMEWORKSERVICE.EXE” GOTO END_BATCH
\\MyServer\Agent\UPDATE$\FRAMEPKG.EXE /INSTALL=AGENT
:END_BATCH
FramePkg.exe requires administrator rights to install properly, so we recommend the
version of FramePkg.exe with embedded credentials. The installation folders for your
distribution might be different than in this example, depending on where you have
specified to install the agent.
Task
1
Copy the agent installation package, FramePkg.exe, from your McAfee ePO server to a shared
folder on a network server, where all systems have permissions.
• Systems logging on to the network are automatically directed to this folder to run the
agent installation package and install the agent. The default location for the agent
installation packages for Windows is: C:\Program Files\McAfee\ePolicy
Orchestrator\DB\Software\Current\EPOAGENT3000\Install\0409\FramePkg.exe
• Embedded credential package always runs in silent mode and does not display any
error message when an installation fails.
2
Save the batch file you created, ePO.bat, to the NETLOGON$ folder of your primary domain
controller (PDC) server. The batch file runs from the PDC every time a system logs on to the
network.
3
Add a line to your login script that calls the batch file on your PDC server.
The line would look similar to this example: CALL \\PDC\NETLOGON$\EPO.BAT
Install using Group Policy Object
The agent supports deployment using Window's Group Policy Objects on client systems in their
network. The administrator must copy the agent Group Policy Object files and msi file to a shared path
(UNC path) accessible to each client system on which you want to install the agent.
2
Installing the agent
Install on Windows systems
36
McAfee
®
Agent 4.8.0 Product Guide
- Agent 4.8.0 1
- COPYRIGHT 2
- TRADEMARK ATTRIBUTIONS 2
- LICENSE INFORMATION 2
- License Agreement 2
- Contents 3
- Using the agent 4
- 9 Agent activity logs 87 5
- Index 89 5
- About this guide 7
- Find product documentation 8
- Introducing McAfee Agent 9
- Agent 4.8.0 Product Guide 10
- About the McAfee Agent 11
- SuperAgent 12
- Agent Handler 12
- Installing, upgrading, and 13
- Installing the agent 15
- Supported languages 17
- Installation vs. deployment 18
- Deploying the agent 19
- Default requiretty 21
- PermitRootLogin Yes 21
- Agent installation folder 22
- Orchestrator 24
- Install the help extension 25
- Agent installation package 25
- Manage Agent Deployment URLs 27
- Install on Windows systems 33
- Install on Windows manually 35
- $chmod +x ./installdeb.sh 40
- $sudo ./installdeb.sh ‑i 40
- Correct duplicate agent GUIDs 41
- Upgrading vs. updating 43
- Macintosh systems 46
- Removing the McAfee Agent 51
- Configuring agent policies 57
- Repository policies 58
- Troubleshooting policies 58
- Priority event forwarding 59
- Retrieve system properties 59
- Select a repository 60
- Proxy settings for the agent 61
- Repository Package Management 62
- Wake-up calls and tasks 67
- SuperAgents and how they work 68
- Convert agents to SuperAgents 69
- How the cache works 70
- When the cache is flushed 70
- SuperAgent and its hierarchy 71
- Agent relay capability 73
- Respond to policy events 75
- Run client tasks immediately 76
- Locate inactive agents 77
- Agent properties 78
- Using the system tray icon 81
- Run a manual update 83
- Enforce policies 83
- Update policies and tasks 83
- Agent command-line options 85
- Command‑line options 86
- Agent activity logs 87
Produits connexes et manuels pour Logiciel Red Hat LINUX VIRTUAL SERVER 4.6 - ADMINISTRATION
(29 pages)© 2020, manymanuals.fr. Tous droits réservés | 0.032 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels