Requirements

1. Use TCacheGen tool to generate scan cache and clean up agent GUID.

   See more details in the following article: Configuring the OfficeScan (OSCE) Virtual Desktop Infrastructure (VDI) client/agent.

2. When the parent Virtual Machine (VM) is launched, make sure it CANNOT communicate with the OfficeScan server.

   This is to avoid the agent GUID being generated once it connects with the OfficeScan server.

3. Before cloning child VMs, make sure that the following two registry keys have the correct value:
   • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc

     “VDIEnabled” =dword:00000001

   • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion

     “GUID” is empty

Known Issue

Depending on the number of child VMs cloned and the period they were kept, the OfficeScan server may have many offline agent entities.

For example: 10,000 Instant-Cloned VMs were created on a daily basis. By default, OfficeScan will purge offline agents per 15 days, which means that there might be a total 150,000 agent entities existing in the Agent Tree. However, most of them are offline and only 10,000 agents are real.

Admins can reduce the auto purge period to 7 days (minimum) to ease this situation.