Does anyone know why VMRC console is not starting? The end-user has a possibility to enable/disable and launch the console. Once enabled, when I try to open it I get the message: Resource Not Available. It is UCSD 6.7.4 and vCenter 6.7. VM is up and running. Any clues?
Case solved. UCSD wrongly shows connectivity to vCenter, even if there are some isuues. It's always green, until you perform Check Connectivity, then it updates. If there are any credential issues, the VMRC console will not work.
Greetings, glad the case was resolved. VMRC tunneling/ proxy through the UCS Director instance will be coming soon. This will allow the need for only UCSD to have connectivity to the ESXi hosts and not the client endpoint. Something to check out on the next connector pack update delivered through Intersight.
Since you mentioned Intersight when is it going to be a full-blown orchestrator? Customers are aware that Intersight is to replace UCSD, and they like orchestration which UCSD does, but they do not want to buy it anymore, since UCSD's future is blury. Any news?
Cheers,
Krzysztof
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
