I'm currently using vRealize Orchestrator 6.0.0. I've been trying to add the extention to my vSphere Web Client but it still does not work.
I configured the SSO Authentication, the network, imported the SSO Certificate. I ran both workflows "Add a vCenter Server instance" and "Register vCetner Orchestrator as a vCenter Server extension" in "Library / vCenter / Configuration".
When I try to restart my vSphere Web Client service, I can see the vCO in it, but it disappear after a minute. And I can the see the error message "
Could not connect to one or more vCenter Server systems:
https://{vCenterIP}:443/sdk"
It seems that this is not a supported combination - vRO 6.0.0 (for vRA 6.2 customers only) + VC 5.5.0. Also in general it is not needed to run the Register extension workflow. The extension should be registered automatically with Add vCenter server workflow. You could wait for vRO 6.0.1and for vSphere 6.0.0 and try with them.
Regards,
Galina
I'm still unable to see the "vCO Servers" section in my vSphere Web client. Here is what I have in my "mob". Is it normal to have a type "HTTPS" ? Because of what I've seen in the forum, people are talking about "REST" in this section.
Data Object Type: Extension Parent Managed Object ID: ExtensionManager Property Path: extensionList["com.vmware.vco"] |
Properties
NAME | TYPE | VALUE |
---|---|---|
client | ExtensionClientInfo[] | client |
company | string | Unset |
description | Description | description |
dynamicProperty | DynamicProperty[] | Unset |
dynamicType | string | Unset |
eventList | ExtensionEventTypeInfo[] | Unset |
extendedProductInfo | ExtExtendedProductInfo | extendedProductInfo |
faultList | ExtensionFaultTypeInfo[] | Unset |
healthInfo | ExtensionHealthInfo | Unset |
key | string | "com.vmware.vco" |
lastHeartbeatTime | dateTime | "2015-03-09T10:27:52.807-04:00" |
managedEntityInfo | ExtManagedEntityInfo[] | Unset |
ovfConsumerInfo | ExtensionOvfConsumerInfo | Unset |
privilegeList | ExtensionPrivilegeInfo[] | Unset |
resourceList | ExtensionResourceInfo[] | Unset |
server | ExtensionServerInfo[] | server |
shownInSolutionManager | boolean | false |
solutionManagerInfo | ExtSolutionManagerInfo | solutionManagerInfo |
subjectName | string | Unset |
taskList | ExtensionTaskTypeInfo[] | Unset |
type | string | Unset |
version | string | "6.0.0" |
Data Object Type: ExtensionServerInfo[] Parent Managed Object ID: ExtensionManager Property Path: extensionList["com.vmware.vco"].server |
Properties
NAME | TYPE | VALUE | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
[0] | ExtensionServerInfo |
|
Hi,
What are the exact versions are you using? For vRO and vSphere web client.. We do not have a vRO 6.0.0 official release, so what are your version?
Regards,
Galina
vSphere web client: Version 5.5.0 Build 1750785
vRealize Orchestrator: Version 6.0.0 2357352
It seems that this is not a supported combination - vRO 6.0.0 (for vRA 6.2 customers only) + VC 5.5.0. Also in general it is not needed to run the Register extension workflow. The extension should be registered automatically with Add vCenter server workflow. You could wait for vRO 6.0.1and for vSphere 6.0.0 and try with them.
Regards,
Galina
I tried with a vCO 5.5.2.1 and it worked. So it was a problem with the 6.0.0...