Install OfficeScan Server on Carmine, apply Product Keys.
TrendMicro will assist in server configuration, to provision machine groupings for servers, workstations, laptops.
Sysadmin will need to assist in provisioning a SmartScan virtual machine.
Install ScanMail for Exchange.
Coordinate client rollout/conversion with Kelvin, using SCCM to script removal of Symantec products, deploying TrendMicro from MSI package.
Determine attendees for Deep Security 4 hour remote training.
Sysadmin will need to provision Deep Security Manager (requirements below).
Deep Security Virtual Appliance will also need to be provisioned.
All documentation is at \\denim\docs\TrendMicro_Docs.
Required installation files (and updated documentation) is available at downloadcenter.trendmicro.com.
OfficeScan Server will be installed on Carmine (existing provisioned virtual server)
SmartScan server (Linux) will need to be provisioned as a virtual machine (requires 1.5GB of RAM, 20GB disk space, Guest OS is Red Hat Enterprise Linux 5 64-bit, 1 network device, 2 virtual processors)
Deep Security Manager (runs on Windows) will need to be provisioned (requires 4GB of RAM, Windows Server 2008 (32 or 64-bit) or Windows Server 2008 R2 64-bit, recommended 5GB of disk space)
Important: Only install Deep Security Manager on the same ESX server as one that is hosting the VMs you want to protect if that ESX server is part of an ESX cluster. This is because the Deep Security Manager will force the ESX server to go into maintenance mode. If the ESX server is part of a cluster, the VMs, including the Deep Security Manager, will be vMotioned to another ESX server during this process.
DSM can use an embedded database (Apache's Derby), or a SQL Server 2005 SP2 or 2008 SP1 database.
Deep Security Virtual Appliance (memory requirements vary based on number of VMs to be protected. E.g., 10-32 VMs=1GB of RAM. 33-64 VMs=2GB of RAM, 20GB of disk space)
The DSVA should be "pinned" to a specific ESX host, and should not have vmotion enabled. DRS should be set to manual or disabled so that it will not be vMotioned by DRS. Alternatively, DVSA can be deployed onto a local datastore rather than a shared datastore. Install guide recommends using local storage.