VMFAQ.com - FAQing about virtualization since 2008
:    
:

Using Trend Micro OfficeScan with VMware View virtual desktops

: 5973
: 1
: 2
Posted: 21 Jan, 2010
by: Troen L.
Updated: 21 Jan, 2010
by: Troen L.

When installing Trend Micro OfficeScan to a desktop it creates a globally unique identifier. This is a problem in environments where you're cloning disks with disk imaging tools (such as Ghost) or in a VMware View environment when you're using an automated desktop pool with a single parent vm.

Trend has a kb article on this topic meant for disk imaging solutions:

http://esupport.trendmicro.com/8/Deploying-OfficeScan-80-clients-using-disk-imaging.aspx

The steps in the above article also works on OfficeScan 10, but after logging on it shows a window telling you that OfficeScan is being reconfigured that is shown for a minute or two. This is probably not so important in a traditional disk cloning environment where you're doing this only once in a clients life time, but things are different when you need to run this everytime a user logins. Note that this solution is only available for 32 bit guests.

The following is from Trend Micro OfficeScan 10's help on this topic:

 

The solution we've found for a VMware View environment is this:

  1. Power on the parent VM
  2. Copy the imgsetup.exe file from the OfficeScan server to the parent VM
  3. Login to the parent VM and run imgsetup.exe /silent
  4. Shutdown the parent VM and create a new snapshot
  5. From Desktops and Pools in View Manager you need to create a new Automated Pool that points to your new snapshot
  6. Entitle it and it's ready for action

You will need to run this command (imgsetup /silent) every time you change the parent VM image.

: 1-2 2  

12 Dec, 2011   |   Lars T
With the latest versions of OfficeScan you don't need to run ImgSetup.exe as it supports VDI environments out of the box: http://esupport.trendmicro.com/solution/en-us/1056210.aspx


09 Dec, 2011   |   Josh Mullen
The problem we're facing with our VMware View environment is that we don't grant our user's admin rights, so the REBOOT / new pooled provisioned VM is a new machine made available to our users, but the imgsetup.exe fails when they log in because it need to FINISH the installation as an admin. I can't have my system admins log into each newly provisioned VM when they're re-composed. Any thoughts on this?



document Placing virtual desktops into the right OU
document Provisioning of desktops fails after adding new host to the cluster
document After upgrading VMware View from 4.6 to 5.0 desktop pools fails with the error message: Diskfault: Selected parent VM is not accessible
document sdd was not found



RSS