In previous versions of VBR, it was possible to logon directly to a tenant VBR using Remote Access Console (RAC), from within the CloudConnect VBR console, without having to re-authenticate to the CloudConnect server.
With VBR 13, EVERYTIME the RAC is started, we need to select and authenticate to the Cloud Provider Server before being able to select the tenant and tenant server. This is a significant waste of time, compared to VBR12.
This request is to reduce or remove the EXTRA authentication to the CloudConnect server. Suggested options are:
Option 1 (preferred): When starting RAC from within the CloudConnect VBR console (in CloudConnect VBR console, select Cloud Connect > Tenants > [right click selected tenant] > Remote Console), the VBR console should pass the CloudConnect server details and authentication, and tenant, to RAC. The RAC would open on the "Specify tenant's backup server" window, or even on the "Type in tenant credentials" window if a Tenant only has a single VBR server.
Option 2: When starting RAC from the Start Menu or Desktop icon, the RAC should ask for the Cloud Provider Server details and authentication once, and then retain that information while the session is open. Possibly, when the Connect button is pressed on the "Specify tenant's backup server" window, the tenant authentication and session should start in a new process/window, leaving the "Specify tenant's backup server" window open to allow further tenant connections without having to restart RAC.
ALSO, EVERYTIME RAC connects to a server, it shows the "Untrusted server certificate" window, and asks "Trust this server?". Can RAC please be set to remember server certificates that we have previously trusted, both for the Cloud Provider Server and the Tenant VBR servers?
-
TT_rick
- Lurker
- Posts: 2
- Liked: never
- Joined: Mar 06, 2024 3:07 am
- Full Name: Rick Day
- Contact:
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot] and 61 guests