Remove private & personal settings and more

[Stefka]

We got 3 requirements we do not know how to implement in a multiuser ASGRD environment: 
 
1) How do we identify sessions with admins with older ASG RD Versions?  (how do we block older ASG RD Versions? / enforce a specific version)
 
2)  We've got issues with inherited settings. Not all users share the same settings at the moment. But we don’t want to allow individual inheritance or personal settings of any kind. 
At least we need a way to FORCE the use of some settings. (for example: all connections in this folder use THIS credentials. We would expect to overwrite the individual settings on that folder for all ASG RD Users)
Alternatively: Is there a way to reset the database and remove all and every individual inheritance? 
THIS is a big issue for us.
 
3) when you press the Menu Key (the key right next to the windows key) inside of a windows RDP session the ASGRD Menu appears instead of the right menu inside the RDP session. (This is a minor issue for us)



 - we use ASG RD 12.0.6342.1   mixed x86 and x64 enviroment. 
 - Users connect with integrated login.  (Domain user) 
 - we ve got user permissions enabled.
 - we are a group of 15 admins

[DevOma]

1) This is not possible currently

2) I will check that and provide you some scripts to remove all personal settings like you want

3) This should work like it is configured - in connection properties => RDP => Resources

[DevOma]

Here is a script that removes all personal values in the category "Credentials" of folders and connections - and reset the individual setting of "Use Default/Inherited/Personal"

DELETE FROM ItemProperties WHERE UserId <> '00000000-0000-0000-0000-000000000000' and RolePropertyId = '5B5AA970-E8EA-4162-BECE-6A366E150C92'

DELETE FROM ItemPropertiesUsage WHERE UserId <> '00000000-0000-0000-0000-000000000000' and RolePropertyId = '5B5AA970-E8EA-4162-BECE-6A366E150C92'

With permissions you can ensure that afterwards nobody is allowed to set these values anymore!

Or do you really want to remove all personal settings? That might not really make sense (like Display Options) - if you need some more specific categories please let me know - for all personal values you can remove the "RolePropertyId = …" part of the SQL script

You should do a backup before running such scripts on the database!

[Stefka]

Or do you really want to remove all personal settings? That might not really make sense (like Display Options) - if you need some more specific categories please let me know - for all personal values you can remove the "RolePropertyId = …" part of the SQL script

thank you! we really want to remove inheritance. In our setup the correct settings (especially the correct credentials) always comes from the folder "above" so no connection object got individual / personal settings. 
And we are also totally ok with removing all and every personal setting possible. I'll try the script.

[Stefka]

3) This should work like it is configured - in connection properties => RDP => Resources

This does not work. When i press the menu key inside a ASGRD RDP session the ASGRD Menu appears. always. And i can not close it with "ESC" or something I am forced to i select something from the menu.

[DevOma]

RDP sessions in tab view or window?

[Stefka]

RDP sessions in tab view or window?

RDP in tab view.

[DevOma]

We tested this settings really often - debugged it and so on - for some customers it is not working as expected - but we don't know why… in all our test systems it runs as expected

[Stefka]

We tested this settings really often - debugged it and so on - for some customers it is not working as expected - but we don't know why… in all our test systems it runs as expected

a useful workaround would be:  On Event Control.KeyPress  VK_Esc -> DestroyMenu.  I mean the most annoying part is, that it is impossible to close the conext menu once it opens up. You have to choose the most non-work-interupting menuItem  to get rid of it.


Kind Regards, 
Gregor Stefka

[DevOma]

The event is not fired in this control - we will try to replace the context menu control and check if it works better...