daphnissov - the first screenshot is from the Flex-based vSphere Web client, and it shows that the vRO plug-in is deployed successfully and can communicate with the vRO server vro72-01...com
kunalkhairnar - if "superadmin" user account has full admin permissions on both vRO and vCenter, then probably the problem is not permission-related. This (Unusable) prefix is automatically added to vCenter connection display name when there is some problem with communication between vRO vCenter plug-in and vCenter server (login problem, certificate problem, etc.).
As a first step to troubleshoot the problem, I'd suggest to check vRO server logs for errors/exceptions logged by vCenter plug-in. The logs can be found in vRO appliance, in /var/log/vco/app-server/ folder; the main log file is named server.log
If you don't have SSH access to vRO appliance, you can export the vRO log bundle as a zip file from vRO Control Center UI.
