Page | 6
times end-user like the reassurance of being able to see their security status, as
they would with a conventional AV client that has been installed to the guest
operating system
All the vShield components need 8GB of memory each – that includes the
manger and components like App, Edge and Endpoint. The vShield Manager
needs 8GB of disk space, and each vShield App and Edge requires 5GB and
100MB of disk space respectively. VMware recommend at least two 2Gps VMnics
teamed together provide network redundancy to the appliances themselves.
The current edition of vShield is compatible with vCenter 4.x Update 2 and ESX
4.0 update 2 – however in the context of this book that has been based on
vSphere5, both vShield Endpoint and vShield Data Security require ESXi 5.0
Patch 1. Additionally, both Endpoint and Data Security require the VMs have
hardware version 7 or 8, and that VMware Tools is up to date with on version
8.6.0 or higher which was released with ESXi 5.0 Patch 1.
You can confirm the VM hardware level by adding the “VM Version” column to
the virtual machine tab in vCenter, or by editing the VM’s settings in vCenter. If
you are not using the “Linked Clones” feature you will need to modify you
template that is used as the source for deploying new desktops.
Note: As you can see in our case we discovered the Accounts Desktop pool was running Windows 7 under
version hardware level 7, rather than vSphere5 native hardware level version 8. We decided to upgrade the
“Parent VM”, and the refreshed the linked clone virtual desktop manager.
You can confirm the VMware Tools version the toolbox application that sits in the
virtual desktop icon tray in Windows.
Kommentare zu diesen Handbüchern