VMware credentials The VMware credentials type manages access to vCenter credentials. This credential type is available for Discovery and Orchestration. Discovery and Orchestration require vCenter credentials for any work that it performs on vCenter, such as cloning a virtual machine. For example, the VMware credential type allows Discovery to explore VMware's vCenter running on a Windows machine to discover ESX machines, virtual machines, and resource pools. Setting up VMWare discovery requires credentials and access rights for the VMWare CIM service. This is because during the Identification phase of Discovery, unique serial numbers are required to uniquely identify CI’s. The VMWare discovery and automation API (vCenter API) now provides the globally unique serial number for computer CIs. CIM credentials are no longer needed to allow access to each VMWare host. Note: In versions prior to Geneva patch 6, you need to provide CIM credentials to determine unique serial numbers for VMWare CI’s, a CIM Credential record must be provided that allows access to each VMWare Host. Create a new VMWare user with the CIM Interaction role on each VMWare Host, that can be used as the necessary CIM Credential. Ensure that the credential Type selected is VMware. Note: Do not use VMware Type credentials for Orchestration activities that perform work on the individual virtual machines cloned by vCenter (for example, restarting a Linux VM). For these activities, the credential Type depends on the operating system of the virtual machine (either SSH or Windows). These fields are available in the Credentials form for VMware. Field Description Name Enter a unique and descriptive name for this credential. Active Enable or disable these credentials for use. User name Enter the user name to create in the Credentials table. Avoid leading or trailing spaces in user names. A warning appears if the platform detects leading or trailing spaces in the user name. Password Enter the password. Credential ID Enter the unique key configured for external credentials in the JAR file uploaded to the MID Server for an external credential system. The Credential ID field has a limit of 40 characters.This field is only visible when the External Storage check box is selected. Tag Allow workflow creators to assign individual credentials to any activity in an Orchestration workflow or assign different credentials to each occurrence of the same activity type in an Orchestration workflow. External Storage Select this check box to use an external credential storage system. When you select this option the User name and Password fields are replaced with the Credential ID field. External credential storage is only available when the External Credential Storage plugin in activated. Note: Currently, the only supported external storage system is CyberArk. Applies to Select whether to apply these credentials to All MID servers in your network, or to one or more Specific MID servers. Specify the MID Servers that should use these credentials in the MID servers field. MID servers Select one or more MID Servers from the list of available MID Servers. The credentials configured in this record are available to the MID Servers in this list. This field is available only when you select Specific MID servers from the Applies to field. Order Enter the order (sequence) in which the platform tries this credential as it attempts to log onto devices. The smaller the number, the higher in the list this credential appears. Establish credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number (or none), Discovery or Orchestration tries the credentials in a random order.