McAfee MOVE AV Solution #83
Labels
Merge Issue
Issue must be merged into next Release
Priority: Medium
Status: Completed
Type: Enhancement
Projects
Milestone
Prepare MCS / PVS Master Image for McAfee MOVE AV Solution
(with installed Agent)
Vendor Best Practices:
Deploy client in a Virtual Desktop Infrastructure environment
When operating in a Virtual Desktop Infrastructure (VDI) environment, follow these steps to create a master
image of a client system and clone the virtual machines.
Before you begin
• The McAfee Agent is installed on the master image.
• The McAfee MOVE AntiVirus client is in the Master Repository.
Task
1 Deploy the McAfee MOVE AntiVirus client to the master image.
2 Configure and apply McAfee MOVE AntiVirus policies to the master image.
Unselect “Enable Selfprotection” on the McAfee Management Server
Unselect “Enable Selfprotection” in the Policy for MOVE AV Common (e.g. 4.8.0)
3 Run the targeted on-demand scan on the master image to build up the cache.
Building up the cache on the master image improves the performance of the VDI when you clone the virtual
machines.
4 In the master image, delete the registry key AgentGUID from the location determined by your Windows
operating system.
• 32-bit — HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent
(32-bit)
• 64-bit — HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Network Associates\ePolicy
Orchestrator\Agent (64-bit)
5 In the master image, under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mvagtdrv
\Parameters, delete the data for ServerAddress1, ServerAddress2, and ODSUniqueId.
Note: ServerAdress1 and ServerAdress2 mus be set to empty value. ODSUniqueID must remove completly
6 Shut down the master image and clone the virtual machines from the master image.
When cloned virtual machines are turned on, new agent GUID values are automatically generated. The virtual
machines are now managed by the McAfee ePO server.
Additional Hints:
McAfee Services on the Master Image do not need to be stopped!
Services Overview:
The text was updated successfully, but these errors were encountered: