A default installation of the Trend Micro OfficeScan client in a vDisk of a provisioned device is going to get you in trouble…
The Trend Micro management server expects each client to register with a unique GUID.
When you install the Trend Micro OfficeScan client in a vDisk, all provisioned devices using that vDisk will register with the same GUID and the management server becomes clueless.
While figuring out how the client interacts with the management server, I found out that the management server is not really picky with these GUIDs and let’s you make up your own GUID as long as you follow this format:
So what we need to do is make sure each provisioned device has a unique GUID before it registers with the management server.
Start with the following:
- Install the Trend Micro OfficeScan client in the vDisk.
- Unload OfficeScan.
- Set the Trend Micro services to “manual”.
Create a startup script with the following contents:
REG ADD HKLM\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion /v GUID /t REG_SZ /d "0d8ffd52-a5a7-48c5-9313-ecdc%COMPUTERNAME%" /f
(leave out the Wow6432Node if you’re on a 32-bit system).
What this does is change the current GUID to a random value, appended with the name of the provisioned device (which should be unique for each provisioned device !).
In my environment the %COMPUTERNAME% translates to devices with a name made out of 8 characters, so if you follow a naming convention which is not made out of 8 character make sure you add or subtract random characters before the %COMPUTERNAME% variable and follow the format mentioned earlier.
You can now add another line to your script to manually start the Trend Micro Officescan client:
net start tmlisten
net start ntrtscan
The client will now successfully register with the management server and you’re done !