Reviewing minimum requirements for VMware environments

This topic describes the minimum requirements for setting up TrueSight Server Automation in VMware environments.

System requirements (VMware)

To employ TrueSight Server Automation in a VMware vSphere virtual environment, your environment must have the following minimum configuration:

VMware vSphere Web Services SDK
VMware tools must be installed on all VMware templates. These tools are used to apply configuration settings to new guest VMs as a part of the provisioning process.
If you are provisioning Windows Server 2003 machines and want to let the Virtual Center perform sysprep activities, copy sysprep to the Virtual Center server. This is not required for Windows 2008, as the Windows 2008 operating system already includes sysprep.
The version of the TrueSight Server Automation RSCD agent installed on the vCenter server or AMO proxy must match the version of the Application Server.

The following VMware versions are supported:

ESX Host - Supports versions 5.0i, 5.1i, 5.5i, 6.0i, 6.5i, 7.0i, 8.0i
vCenter Server - Supports vSphere versions 5.0, 5.1, 5.5, 6.0, 6.5, 7.0, 8.0

Access and privileges (VMware)

The following sections note the access and privilege requirements for implementing TrueSight Server Automation in a VMware environment:

Application Server access

The Application Server requires access to the web service on the target (the vCenter server).

Required agent privileges

The agent requires administrative privileges. Open the c:\windows\rsc\exports file and edit the permissions. Ensure that the permissions in the Exports file follow the permissions guidelines you are using in regards to exports or usersor users.local files.

Required vCenter user privileges

TrueSight Server Automation requires (at a minimum) that the vCenter user has the specific privileges listed in the following table:

Type of privilege	VMware Resource Privilege Name
Datastore	Allocate space Browse datastore
Datastore cluster	Configure a datatstore cluster (required for vCenter version 5.x)
Distributed Virtual Switch	Create distributed virtual switch
dvPort Group	Create Delete Modify Policy Operation
Host Local Operations	Create virtual machine Reconfigure virtual machine
Network	Assign network Configure
Resource	Assign virtual machine to resource pool The following permissions are required for deploying the VM directly on the Cluster and Host Assign virtual machine to Cluster Assign virtual machine to Host
Virtual Machine Configuration	Select all of the privileges for this category. Click here to see the full list. Add existing disk Add new disk Add or remove device Advanced Change CPU count Change resource Configure managedBy Disk change tracking Display connection settings Extend virtual disk Host USB device Memory Modify device settings Query Fault Tolerance compatibility Query unowned files Raw device Reload from path Remove disk Rename Reset guest information Set annotation Settings Swapfile placement Unlock virtual machine Upgrade virtual machine compatibility
Virtual Machine Interaction	Device connection Power Off Power On Reset Suspend
Virtual Machine Inventory	Create from existing Create new Move Remove You can create a virtual machine support in: A destination folder of virtual machines in the datacenter, A folder containing a datacenter, The datacenter, if you do not use folder-based organization. This is crucial for any virtual machine creation.
Virtual Machine Provisioning	Customize Deploy template Read customization specification Clone Virtual Machine Clone template
Virtual Machine State	Create snapshot

Where to go from here

Adding the vCenter server to TrueSight Server Automation