khuizer

It is the private vault tab (the tab next to 'all entries') that is missing.

We are running 11.7.1.0 (and some 11.7.2.0) with DLVS 3.1.0.0

That option is not checked, and it's just a number of users that don't see the private vault, and it seems to be correlated with the machine, if a user starts RDM on his own device he doesn't have the private vault logs into our remoteapp farm and starts RDM, he does get the private vault.

Since the problem with the "translation" of the variable as discussed above we seem to have a number of users that dont see the private vault tab anymore.

Is there a way to 'reset' something so the user will see the/his private vault again??

Since the problem with the 'translation' of the variable as discussed above we seem to have a number of users that don't see the private vault tab anymore.

Is there a way to 'reset' something so the user will see the/his private vault again?

That's good to hear.

Can you also make sure that that version will be made available from the installer package generation option so I can create new installer packages asap.

Export? For creating the installer package you mean? it isn't directly related to the export.

If i just start the application, set the username to 'ITS\%username% and exit the data source settings, i then get asked to login again, and when i then go back to the data source settings the username is set to my username instead of just the variable.

Hi,

I'm using RDM 11.6.1.0 together with a DLVS 3.x.

In my datasource i had set the username name field to 'ITS\%username%' which worked fine in the past, i could create an installer package with this datasource configuration and it would keep the %username% intact.

However, since my upgrade to version 16 it seems that the username field in the datasource settings is set to the account that i logged in. For instance, when i set the config to %ITS\%username%, login as ITS\khuizer and go back to the datasource settings the username field shows 'ITS\khuizer' instead of the 'ITS\%username%'.

Is there a way to have the username field be 'fixed' again, or???

I've checked the information about DVLS and Azure AD, but there are some issues with this i think:

- I need to download some sdk from the azure portal, but we don't use multi-factor auth provider (our MFA is included in our Office 365 licenses).

- It only supports SMS or Phonecalls (who still uses that? :) ) , an azure AD based login should just use the settings the (azure AD) user has already set up (most likely he uses the Azure MFA app).

- allowing 'real' azure ad logins would circumvent the problems above, and would make for a better experience (but i have no clue about programming, so i have no idea if its even possible), integration azure ad login in webapp is (supposed to be) a breeze, but for applications things are probably not so easy.

Is there any word about this feature? Azure AD login (with MFA) would be a nice option.

What also would be nice is the ability to use Azure AD accounts (with MFA) with Devolutions Server.

I know you can use google authenticator etc, but as we are using Office 365 users are already using Azure AD accounts protected with MFA, and it would be nice if they could just use that instead of configuring yet another two-factor solution/app.

Has one of the engineers had a look into this problem already?

I'm using RDM 11.0.1.0

@Maurice,

I'm not trying hijack this thread, but we have Devolutions Server environment with around 6000 items, and everything feels a bit sluggish, saving a sessions properties takes a couple of seconds for example.

As I'm unsure if this sluggishness is caused by our environment or the high number of items, or something else I'm interested in the best practices you speak about?

I'm currently looking into setting up two-factor authentication for all of our users, but I'm a bit uncertain of what is the correct/best way to set this up?

We have RDM with around 50 users and a Devolutions Server 3.0 which is connected to an MS SQL server.

In different locations I'm seeing settings for two-factor, but what is the correct way to set this up? And at what level? On the Devolutions Server, or on the data source?

When I try and setup two-factore on the data source level, and try to select the 'fore data source two-factor authentication' I get an error stating that you need to configure two-factor in the data source before enabling this option, but wasn't that was I was doing? What options do I need to set?

I also tried to configure two-factor on the Devolutions Server, I can configure the two-factor settings, and I guess i need to configure the settings of the users (?), but when I select Manager Users from the Devolutions Server console, the two-factore 'Configure' button of the users doesn't seem to do anything.

When I go to Administration / Users and go to a user and click on 'Configure' I get an 'Object reference not set to an instance of an object' error:

NullReferenceException - Object reference not set to an instance of an object.

at DevExpress.XtraPrinting.Native.IEnumerableExtensions.ForEach[T](IEnumerable`1 en, Action`1 action)

at Devolutions.RemoteDesktopManager.Forms.FrmTwoFactorConfiguration.c69ae3f3c12239a7b16bed0123734a3a2(Object c19f185fd70cefc696ba148af1c4faf54, EventArgs cf1018bb83ec7debd818319fd3cb4844e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at Devolutions.RemoteDesktopManager.Forms.FrmBase.OnLoad(EventArgs e)

at System.Windows.Forms.Form.OnCreateControl()

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hi,

It looks like that modifying the domain setting to just 'ITS' indeed solved the problem.

(although it shouldn't really matter if the domain is 'its.centric.lan' or 'its', both should work in my opinion, it's still the same domain).

What i meant with the select user button is the following.

The users that are domain users have a button behind the login name where you can select a domain account

http://i62.tinypic.com/1w8ea.png

However after the upgrade and then logging in with a (domain) user that is still unknown in RDM a user account is created, but there is no ad account selecting button, so it looks to me like the user account has been created as a non-domain user account.

http://i57.tinypic.com/n2db0l.png

The domain value in DVLS is set to its.centric.lan

Hmm,

It looks look that after the upgrade to 2.5.2 i can logon using a previously unknown account which then is auto created, but it looks like a non AD account as there is no select user button behind the login name.

When i try to login using my regular account (its\khuizer) i now get a unknown user or password eror.

when i login using an unknown account and without the domain prefix (its\) it looks like a user its.centric.lan\khuizer gets created, but this account also doesn't have the 'select user' button behind the login name field.

I have enabled that option (after an upgrade of RDM), and upgraded the server to 2.5.2 again, but unfortunatly i still get the same error.

My username is ITS\khuizer and integrated security (active directory) had been selected when this users (and other users) have been created.

Yes, I can login using my AD credentials when i'm on the 2.2 server version. After i upgrade to version to 2.5 i can't login anymore using the same credentials.

I have not enabled auto creation, but all of the users are already created (and can login when i use the devolutions server 2.2)

I am trying to upgrade our devolutions server 2.2 to version 2.5.2.

The upgrade process runs fine, everything got updated etc.

However when i restart RDM i can't seem to logon anymore (using AD accounts).

The error i get is 'your login is valid but your user does not have any access for this data source'.

When i revert back to the old version everything works fine again.

Any ideas of what is wrong here, or what/where to look for?

I just installed the 10.1.10.0 beta and this seems to have solved the problem.

Hopefully a non beta version will be released soon, we are on the verge of going 'live' with our RDM environment and I need to create a custom installer package for our users with this fix included.

Uhm yes and no.

We had configured a default templates path in the past as we wanted one set of defaults within our teams. However when i just checked the path wasn't in the setting anymore.

Hmm, i just inputted the UNC path to our templates directory again, but when looking back in the setting again it doesnt show a directory, so this might be 'normal' behaviour.

So yes we are using a default template directory.

We are seeing some weird behaviour with the setting of Personal Credentials.

When I (TEST\KH) sets my own personal credentials to TEST\ADMIN_KH) everything looks OK.

However when a collegue logs into RDM using his own PC and his own login naam (TEST\RH) and goes to the personal credentials setting he is seeing MY personal credentials (TEST\ADMIN_KH), and can even view MY password.

I don't think this is suppose to happen? :)

Is there any progress on this?

I'm getting a bit annoyed by the 'difference' between domain\user, fqdndomain\user and user@domain >, they all point to the same AD account, so why doesn't RDM(S) still understand this?

Btw, is it even possible to login using a UPN (user.name@domain) ? When i try this a new user account will be created in the form of its.centric.lan\kees.huizer@centric.eu (instead of just kees.huizer@centric.eu)