This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

Setting up a VMware vSphere environment

To set up a VMware vSphere environment in TrueSight Server Automation, you must perform the following tasks:

When you add the vCenter server to TrueSight Server Automation, you can add it as either an agent-based managed server or as an agentless managed object (AMO) that communicates with some other agent-based proxy server.


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 task is not required for Windows 2008, as the Windows 2008 operating system already includes sysprep.

If you add a new server that contains virtualization management software like vSphere or SCVMM installed on it, TrueSight Server Automation auto-detects that software and treats the server accordingly by populating Virtualization PSIs for them.

Any conflicting use of the servers can result in conflicts, such as deletion of user created Virtualization PSI. The following actions are examples of usage of the servers in a conflicting manner:

  • Using a server that has SCVMM for UCS.
  • Installing conflicting virtualization managers on a server: for example, installing vSphere and SCVMM on the same server.

After you set up the VMware vSphere environment, you are ready to perform various vSphere management tasks, as discussed in Managing a VMware vSphere environment.

Was this page helpful? Yes No Submitting... Thank you