I updated to RDM 11.5.4 and had to update to VMRC 8 per the warning and reselect VMRC 8.0 in my session settings. My vCenter server is 6.0u2.
When I double click an entry, I keep getting the error attached. My consoles are sub connections of other sessions but it's the same thing when I created a new test session. I also noticed that when I power off the VM, the console stays open now instead of closing itself like before.
vmrcsettings.png
vmrcerror.png
Hello,
The VMID seems wrong, how did you obtain it? It needs to be what VMware call moref, on our system they are simple numbers. If you hit create in our own VMware console, we will create the session with proper parameters.
I will add the ID to our own grid to make this easier, at least you'll see it immediately.
Best regards,
Maurice
Hi Maurice,
I get the ID like this:
get-vm "myvm" | select *
and look at the ID field (you need to drop the VirtualMachine- in front)
I also confirmed it's the same value as shown using these two methods:
Using the info in VMware KB1017126
Using RVTools and checking the ID column.
All of them give me the same value with the vm- in front of it.
I haven't used the VMRC until after updating vCenter and RDM were updated so I don't know which one may have caused the issue. If I put in my credentials into the error dialog box the console will open just fine, I'm just getting the invalid session box now which is a bit of a pain
If it helps, using the info on this page:
http://www.virtuallyghetto.com/2014/10/standalone-vmrc-vm-remote-console-re-introduced-in-vsphere-5-5-update-2b.html
I tried both methods described at the command prompt with vmrc and they both work however...
If I use the clone ticket method, close the resulting console widow, and then try to use the same call again I get the same error as I get with RDM. In order to get it to work, I need to generate a new ticket. Is it possible RDM is not generating a ticket (or using some old ticket) before calling vmrc?
Hello,
We use the PowerCLI so:$si = Get-View ServiceInstance; $sm = Get-View $si.Content.SessionManager; $ticket = $sm.AcquireCloneTicket(); Start-Process -FilePath \"$($vmrcPath)\" -ArgumentList \"vmrc://clone:$($ticket)@$($vcenter)/?moid=$($vmid)\" -Wait
Maurice
The first time I tried the commands using PowerCLI window, I got the error but I had a mistake in the start-process line. When I tried again I didn't get the error.
I closed the powercli window and opened it again and ran the following and everything worked as expected using this code (where my_vcenter_server was name of my vc)
$si = Get-View ServiceInstance;
$sm = Get-View $si.Content.SessionManager;
$ticket = $sm.AcquireCloneTicket();
Start-Process -FilePath "C:\Program Files (x86)\VMware\VMware Remote Console\vmrc.exe" -ArgumentList "vmrc://clone:$ticket@my_vcenter_server/?moid=vm-2230" -Wait
Is there a minimum version of powercli required? (I have 5.5 Release 2 at the moment).
Is there something I can do in RDM to see what's going on? My only guess is that somehow an old ticket or no ticket is being used and that's why i get getting prompted.