foxtrot

exact same error for me going from 13.6.2 to 13.6.4.

uninstalled 13.6.4 and want back to 13.6.2 and everything is fine. I don't think I had anything in my private vault as I never used it (there's nothing there now anyway, i used to have 1 item in there but don't recall if i deleted it since it wasn't used in along time)

edit: using MSSQL datasource and integrated security

Any idea when this will be fixed? I tried the newest 13.5.13 but still doesn't seem fixed

I know what I'm asking is a good use case for Devolutions server but I don't have tons of users to warrant purchasing that but was wondering if I could do something similar with RDM.

I would like to use AD integration with an SQL db as the login method so users don't have to remember another login for SQL.

At the SQL level I'd like to just add one AD group to give all the users the ability to login.

Can I do the same thing at the RDM level if I create the group manually and assign permissions? If yes, I would need a little guidance on this.

If not, is there a way to have RDM create the user for me within the RDM database but not at the SQL level? It seems like it always creates both login and then I need to manually delete the SQL one. I don't mind as much if RDM ends up with a bunch of users in the DB but I'd prefer just to use a simple group at SQL level.

Thanks

I'm looking into potentially using repositories but i don't see the option in RDM. The online help says it's only available with SQL and Devolutions server but when I got to the settings tab on the new datasource i don't see any repository option. Am I looking in the wrong place? I'm using RDM 13.5.8

thanks

I just upgraded to 13.5.8 (from 11.7.6) and when I use quick connect the tab that gets opened doesn't get the focus after I type in my credentials. The focus goes back to the tab I was on instyead of focusing on the newly opened quick connect tab for server I want to connect to.

I don't know if this was changed somewhere along the way but I find it a little confusing. More than a few times I keep thinking the connection failed because I don't get put into the tab that was just opened and I don't see it right away.

ALso noticed that if I type my credentials wrong, the window, instead of being int the middle of the screen like on the first prompt, gets put into the top right corner of the screen. It would be easier if it would appear in the same spot since my cursor is already there so it's slightly faster to click in the user/pass fields and correct my mistake

if it helps, the problem is caused by a slight shift in the pixels on the side. Attached are a couple of screen grabs of the right hand side. With smart sizing off there is what appears to be maybe a 1 pixel black line.

When I turn on smart sizing, the black line is maybe 2 or pixels wide now.

On the left hand side of the screen with ss of it looks like there's a slight black line. With I turn SS on, the black line seems to disappear because the image gets shifted. (I did not provide images of this)

The shift is subtle, I know, but I still can notice the difference as some stuff on the screen will appear a bit out of focus/blurry to me.

Remote desktop size is set to default

Tried RDP 8.0/8.1 but didn't help. I've attached a few screen shots but you might find it hard to see the difference as it's quite subtle. It's almost like the width of the rdp window is maybe off by a pixel or two and it causes a problem.

I tried on a couple other machines with 11.5.4 and 11.6.2 and I didn't see the problem. When I toggle smart sizing for a connection I have open I don't see the screen try and readjust it's dimensions like I do in 11.5.4 and in 11.6.2 it doesn't seem to "resize" as much as in 11.6.5. Kinda of hard to explain, maybe a webex to show the problem might be needed

I upgraded from 11.6.2 to 11.6.5 and the smart sizing option seems to be causing a small problem.

I have it on on by default and when I make a new connection the display is a little blurry (these are embedded connections). If I uncheck smart sizing from the tab on the open connection, the size of the rdp window doesn't seem to change but everything is sharp. It seems like the window adjusts itself on the right hand side ever so slightly but it's hard to tell if the size even changed by a pixel or two. This wasn't an issue in 11.6.2 to the best of my knowledge. I'm on windows 7 and I see the same thing connecting to windows 7/2008 r2/2012 r2 and windows 10 machines.

On an unrelated topic once I'm posting, I have that reconnect issue when I have to switch from default to full in order for it to pass my credentials. Will that be fixed or am I stuck with full reconnect now?

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.

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?

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

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.

I would prefer not to have read/write mode in offline just to keep things simple and avoid and issues with syncing changes.

In offline mode, would be it possible to access the properties of a session in read-only mode? I thought I used to be able to do this but this wasn't the case the other day when I needed it (version 11.0.14, same with 11.1).

My offline mode is set to read-only and intelligent caching.

If there's an issue with SQL not being accessible, I would like to put myself into offline mode so I can still work but may still want access to the IPs/notes/passwords that might be hiding in some of the sessions unfortunately the edit/properties options are grayed out so I can't access any info. My issue was I wanted to access something for which I didn't have a session and getting he login info was RDM was the fastest option in this case but because I was offline and hence couldn't access it.

Thanks

seems to be fixed in 11.0.11 (just like the release notes say).

thanks!

I just downloaded and tried 11.0.10 but it doesn't look like the fix made it. I'll wait for the next update then.

Thanks

Hi David,

Did QA have a chance to look into this and if so, were they able to reproduce?

Hi David,

Following your suggestion, I went back and tried a few things. The problem appears to be caused by my having set a user specific setting on the session.

There are no credentials set for this particular session.

I have a user specific setting saying to override the credentials with my personal credentials. When I choose the option to prompt for credentials, it doesn't seem to pass the password, only user and domain.

If I edit my user specific settings and remove the credentials override, then the open prompt for credentials) seems to work. For fun I tried the option to select credential entry and that worked.

Long story short, the problem seems to happen when I have a user specific setting set to override the credentials with my personal credentials, and I select the option to open (prompt for credentials).

I'm running RDM 11.0.8. When I right click on a session and choose open with parameters > open (prompt for credentials), it only seems to pass the domain and the username, not the password. This is for RDP sessions. I always have to type the password manually on the login screen.

Am I doing something wrong or is this a bug?

Thanks

Just to confirm, is it backward compatible all the way to version 9? I'm looking in global sessions and see a few people who haven't updated in a while (maybe when version 11 is out, might be a good time to force everyone to upgrade )

Went to upgrade from 10.9.9 to 10.9.12 and got prompted for a DB upgrade. Looks like quite a large jump. Is it relatively safe or is it a big change? I assume it's still fully backward to much older versions?

Is there any way to put in the release notes when a DB upgrade is required? Always comes as a surprise to me so in this case I had to go back to 10.9.9 until I can find a little window to update the DB.

I compared an older .rdd file to the one I exported the other day and it seems like putting in the lockuicode tag makes it import as locked. Is this a valid solution or am I asking for trouble?

As for my feature request, the only thing I can think of is maybe adding it to the administrator > data source settings. Maybe having toggles to lock the server settings for non admins, lock the auto refresh and cache modes, etc?

It's been a while since I've setup a new folder for a new department in RDM and an option I used previously seems to be gone (or I'm not remembering how it works)

What I would do is create a data source on my machine (I'm an admin) with the connection settings(server, sql login, cache settings, etc), then lock it with a password and export it. I would distribute that file and users were able to import it and access the RDM.

With version 10.5.4 though, I'm finding I can't export a locked data source. Has something changed? I can see not allowing an admin to export a locked data source but is there any way I can do it?

Ideally, I could lock certain options and only allow users the ability to change the prompt for offline mode on startup, ping online method and auto go offline. Everything else they shouldn't need to change.

Looks like I had the debug level cranked up pretty high (I assume this is under help > profiler > debug tab?). I guess I forgot to change it after testing something.

I assume the normal level is 0?