The address format must be valid for the hypervisor connection. The rules that are applied are as below: XenServer (HypervisorConnection Type = XenServer)
or http:\\<server Name>
or https:\\<server Name>
Note: To use multiple addresses to the same XenServer pool to provide failover functionality, all XenServers in the pool must have a shared block storage device. If the use of https connections and failover is required, the certificates on the servers must be trusted by all of the controllers (typically this means having a root certificate installed).
VMWare vSphere/ESX (HypervisorConnection Type = vCenter)
http:\\<IP Address>\<sdk path>
http:\\<server Name>\<sdk path>
or https:\\<Server Name>\<sdk path>
* Http requires manual vCenter configuration; https is the only supported default format.
* Default sdk path is 'sdk'
Microsoft SCVMM/Hyper-v (HypervisorConnection Type = SCVMM)
server Name (short or FQDN)
Note: If XenServers are moved to new XenServer pools after being added to a hypervisor connection, unpredictable results can occur. Once a XenServer is assigned to a hypervisor connection, it must not be moved to a new XenServer pool.
In the case of failure the following errors can result.
The path provided is not to an item in a sub directory of a hosting unit item.
The hypervisor connection to which the address is to be added could not be located.
The address could not be used to contact a hypervisor or the validation rules have not been met.
The address specified is already part of the hypervisor connection.
The hypervisor for the connection is in maintenance mode.
An error occurred in the service while attempting a database operation.
The operation could not be completed because the database for the service is not configured.
An error occurred in the service while attempting a database operation - communication with the database failed for
An error occurred while communicating with the service.
The user does not have administrative rights to perform this operation.
An unexpected error occurred. To locate more details, see the Windows event logs on the controller being used or examine the XenDesktop logs.