VMware VSHIELD APP 1.0 - API Manuel d'utilisateur Page 27

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 35
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 26
Page | 27
3. This should pull up the “Security Server Installation Page which
allows you to control how the service is deployed. There’s quite a lot
options in this page, but most of them are common sense we feel:
So “Name” is the VM name of the appliance. I created a folder called
Bitdefender Security Servers” in my “infrastructure” folder so I could
keep things nice and tidy.
VM Settings allows you to control the resources assigned to the appliance
including which datastore to use and if the appliance will use a thin or
thick virtual disk. The controls the amount of memory and CPU allocated
to the security server. The guidance indicates that as you have more
virtual desktops and general VMs you will need resources. The small (i)
icon will give you some ideas on the appropriate settings for your the
scale of your environment. The consolidation, memory and CPUs options
all control the workload the Security Server expects to take, and virtual
resources allocated to deal with them. There are four options under
consolidation (Low, Medium, High and Manual). Each option allocates
more and more resources to the SVA based on the rate of consolidation
you expect in your environment per ESX host. “Low” as assume you have
around 0-24 virtual desktops and 0-2 server-based VMs whereas “High”
assumes you have 50 or more virtual desktops, and 8 or more server-
based VMs. Obliviously “Custom” allows you to manual set your own
preferences. Whereas “Low” allocation 2GB of RAM to the appliance, and
two vCPUs the “high” option allocates 4GB of RAM and 6 vCPUs.
You can also set as password for the security server as well as its time
zone that can be important for logs and reports.
Pay close attention to the network settings. In our case we placed the
appliance on our “management network” and used DHCP to set it up. That
was because we have up to 9 servers to deploy to and we wanted to
reduce the per-server settings. It’s currently not possible to bulk select
many ESX hosts, and just use DHCP. So each host needs to be configured
this way. Once completed just click Save, and move on to the next ESX
host.
Vue de la page 26
1 2 ... 22 23 24 25 26 27 28 29 30 31 32 33 34 35

Commentaires sur ces manuels

Pas de commentaire