Matt_B1's Accepted Solutions

VMware support was able to figure this out.  For some reason, not all the workflows were available even though I deployed a new 6.0.3 appliance and imported the config from my previous 5.5 instance.  So, we went into the Orchestrator Configuration webpage->Troubleshooting and clicked "Reset Current Version" for plug-ins.  Bounced it and the missing workflows were there.  Then, went back into Orchestrator Configuration webpage->vSphere Configuration under General and input the IP of our vCenter PSC and used administrator@vsphere.local.  The look up data worked, I checked most of the boxes, and was able to see vCenter in vCO afterwards.

Thanks for the info.  I use the "Invoke an external script" workflow to run several PowerShell scripts from my admin host.  It is easier for me to maintain all the .ps1 files in one location and not import them into Orchestrator.  The article prompted me to switch my Powershell host connection from Basic to Kerberos.  In order to do that, I had to update /etc/krb5.conf on the vCO appliance.  I referenced VMware KB2036986 to get around the "Cannot get kdc for realm" issue.  This issue was primarily because we did not need to have krb5 configured earlier. I now got a different error when running the workflow after bouncing vCO. System.NullReferenceException: Object reference not set to an instance of an object. This pointed me back to the need to make the AD connection first.  It did not work previously without Kerberos authentication.  Once I add these lines of code, Get-QADComputer finally worked without error!   Thanks for the help. $pass = ConvertTo-SecureString -AsPlainText -Force -String "password" Connect-QADService -ConnectionAccount "example.com\serviceaccount" -ConnectionPassword $pass $Computer = Get-QADComputer -Identity "server01" | where {$_.name -eq "server01"} Disconnect-QADService

I gave up, uninstalled VUM from the admin server, re-installed it on the vCenter server, used 127.0.0.1 and finally got VUM with valid SSL certs.  As part our design, we did not want to have VUM on the same server as vCenter but I was left with no other option.