bkrontz01

Think maybe I could've been a little better at explaining... consider this unrelated to the screensharing technology in use... just looking for the ability (like Word or Excel) where you'd have a little slider at the bottom to increase/decrease the zoom a tiny bit on an RDP session or any other session. Sounds like RDP is in the works, which is great! Just throwing an idea out there. Thanks David!

Brian

It looks like the ability to zoom a bit into web sessions was added... wondering if the same could be added to other sessions. On a Webex, or something where the folks on the call can't seem to figure out how to adjust their screen, it would be nice if the host (with RDM) could zoom just a little... definitely less than 30%... just a nudge in the direction of making the text bigger.

Nothing super important, but figure while you're at it :)

B

Brian Krontz • 9 days ago

Quick question... zooming into other types of sessions... possible? Could it be? I've been on a bunch of Webex's with colleagues that had a hard time seeing things... would be a cool feature.

• Max Trottier Staff Brian Krontz • 2 days ago

• Thanks for the suggestion Brian! Would you mind posting it on the Devolutions Forum in the Feature request section so we can get more feedback from other users as well? Thanks!

Right on Stefane... Brent Ozar would be unhappy, I'm sure... but I'll defrag the db after the shrink... familiar with all of that stuff, but can't write a query to save my life :)

THANK YOU!

B

Hi Maurice,

Happy Monday! My alerting on SQL has been trying to prevent coffee from happening this morning. I'm still quite low on space and it doesn't appear to be leveling off any time soon. Did ya'll have a chance to work on that SQL Statement?

B

Thanks Maurice! Érica mentioned this the other day and I figured I was alright. I currently run the scripts under my account which should meet your req's. I can change it of course... will do that moving forward because I'm not really testing anymore. Appreciate the lightning fast response!!!

B

Hello Guru's!

With some help, I've created Powershell scripts (Thanks Érica!!) to add/edit users in my RDM MS SQL Data Source automagically and hit a problem... my database has grown to over 500gb. After a little digging, I've found that the UserInfoHistory table is the culprit holding almost a million rows and 536gb of history that I probably shouldn't be keeping... and/or I need to cool my jets with the scripts running every 15 min's... I'd prefer to flush these logs if possible and adjust retention. Thoughts?

Thanks!!

B

Wow... you're really brilliant... you read into my issue perfectly. I'll give this advice a spin and let ya know. Thanks so much Erica!

B

After giving it a shot, I noticed that it was still digging in AD... really only needs to be this... and the first import lines can probably go as well... I did test this way and things were fine.

#Purpose - Config every RDM MS SQL Login User in the database with

# add/edit/whatever perms on the root of their user account.

# This builds a platform so sessions can be config'd for add/edit/etc.

# Otherwise, a user would never be able to do those things.

#Load things

Import-Module 'C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.PowerShellModule.psd1'

Import-Module ActiveDirectory

#Connect to the SQL Data Source

$DS = Set-RDMCurrentDataSource -ID "123123123-1231-1231-1231-123123123123"

#Get all RDM users

$users = Get-RDMUser

#Change perms

foreach ($user in $users) {

$user.CanAdd = $true

$user.CanEdit = $true

$user.CanDelete = $false

Set-RDMUser $user

}

Wondering if this has something to do with my powershell scripts... 5 set to every 5 mins add folks in an OU... paused things and seeing where I end up. My thought is that the scripts are deadlocking things... not the app.

Here's a crash of the application, which is more along the lines of the mystery crashes of the application itself instead of the user add situation I was speaking about above

Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Ent Ed 12.0.8.0, running since 4 hours 21 min 8 sec, mem usage 1038mb, SqlException

SqlException - Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)

at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)

at System.Data.SqlClient.SqlDataReader.Read()

at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)

at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)

at System.Data.Common.DataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)

at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)

at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetData(String sql, IDbDataParameter[] parameters, IDbConnection dbConnection)

at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseSecuritySubDataSource.GetUsers[T](Int32 userType, Nullable`1 userId)

at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseSecuritySubDataSource.GetUsers()

at Devolutions.RemoteDesktopManager.Managers.SecurityManager.GetAllUsers(Boolean useCache)

at Devolutions.RemoteDesktopManager.Managers.CurrentDataSourceSecurityManager.GetAllUsers(Boolean useCache)

at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.c81c347c83082c8f27092d107150085af(Boolean ceb9d2241b042f495f5aa0c7d6093924c)

at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.Initialize(ISecurityManager securityManager)

at Devolutions.RemoteDesktopManager.Managers.MainMenuManager.c708816d1c95767c33a3abe0df3fc19d4(SecurityManagementOpenMode c17de7030565f43077466095dd50c1438)

at Devolutions.RemoteDesktopManager.Managers.MainMenuManager.c395f096672f59ebb8079354f25b9919c(Object c19f185fd70cefc696ba148af1c4faf54, EventArgs cf1018bb83ec7debd818319fd3cb4844e)

at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

at System.Windows.Forms.ToolStripItem.PerformClick()

at Devolutions.RemoteDesktopManager.Decorators.RibbonControlDecorator.c3be681b5eeb4880ff5e27146cfc20794(Object c19f185fd70cefc696ba148af1c4faf54, ItemClickEventArgs cf1018bb83ec7debd818319fd3cb4844e)

at DevExpress.XtraBars.BarItem.OnClick(BarItemLink link)

at DevExpress.XtraBars.BarBaseButtonItem.OnClick(BarItemLink link)

at DevExpress.XtraBars.BarButtonItem.OnClick(BarItemLink link)

at DevExpress.XtraBars.BarItemLink.OnLinkClick()

at DevExpress.XtraBars.BarButtonItemLink.OnLinkClick()

at DevExpress.XtraBars.BarItemLink.OnLinkAction(BarLinkAction action, Object actionArgs)

at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(BarLinkAction action, Object actionArgs)

at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.ClickLink(BarItemLink link)

at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(BarItemLink link)

at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnUnPressItem(DXMouseEventArgs e, RibbonHitInfo hitInfo)

at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnUnPress(DXMouseEventArgs e, RibbonHitInfo hitInfo)

at DevExpress.XtraBars.Ribbon.Handler.RibbonHandler.OnUnPress(DXMouseEventArgs e, RibbonHitInfo hitInfo)

at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnMouseUp(DXMouseEventArgs e)

at DevExpress.XtraBars.Ribbon.Handler.RibbonHandler.OnMouseUp(DXMouseEventArgs e)

at DevExpress.XtraBars.Ribbon.RibbonControl.OnMouseUp(MouseEventArgs e)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

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

at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m)

at DevExpress.XtraBars.Ribbon.RibbonControl.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)

I'm not sure if I'm having the same issue, but there's definitely deadlocking going on with MS SQL. I poked around with the above advice and found this in the roaming directory. Here's a screenshot:

https://goo.gl/photos/N1LZfeCBDCUms7Xx5

It won't let me open the file in Notepad or Notepad++

The behavior up until today was that I'd head back over to the server running RDM after an hour or two and it will have crashed at some point. Today, I was powershelling some user add's and this happened:

Unable to save the user in the database! Transaction (Process ID 64) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

This all seemed to start after I upgraded to 12.0.8.0.

Also of note, I have 5 powershell scripts that kick off every 5 minutes to scour AD for new users in an OU and add them to RDM/SQL.

Thanks! I'll give that a try. Have a great weekend Erica!

Thank you Erica!!

To help me wrap my head around this... Does this seem correct? These perm's live on the user level... and without further perms in sessions, or the like, these perm's in and of themselves do not allow anything. They simply set the baseline for further access.

I'm also not having any luck getting that powershell to work. Is that going to work with a MS SQL backend?

#Load things

Import-Module 'C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.PowerShellModule.psd1'

Import-Module ActiveDirectory

#Get users

$adGroup = "Testgroup"

$users = Get-RDMUser

$domainName = Get-ADDomain -Current LocalComputer

# Connect to the SQL Data Source

$DS = Set-RDMCurrentDataSource -ID "31231231231-1231-1322-1233-1231231231231231"

#Change perms

foreach ($user in $users) {

$user.CanAdd = $true

$user.CanEdit = $true

$user.CanDelete = $false

Set-RDMUser $user

}

Is there a way to do that globally with Powershell? I have quite a few users.

Word doc with images attached. The rdp sessions to be flagged are in the Viewpoint folder and the VPProcess credential is used by RDM to log into those resources.

I take it back... the end user and the backend user both have edit perm's. To be clear, I've created a role for that class of user... that role has the perm's. Outside of the role, the user has no explicit perms.

That was the issue... The AD account used for those session logons didn't have the RDM perm's... The AD accounts of the end users did... need both. Thanks!

This appears to be a permissions issue with my end user, but I'm not sure what's wrong. I've given the User a Role with View and Edit permissions on the RDM folder. What else might be needed? I can't find anything in the forums or manual that speaks to the req'd permissions. Thanks!!

Hmm... un-ticking this box seems to be a good workaround if I close with the X. If I log out of a machine properly, I'm still forced into the dashboard.

I can't roll beta's out in this environment and will need to wait on a permanent fix. No biggie. Just a heads up was all.

B

I'm also having this issue... pretty annoying. Specifically when I close out a tab by hitting the "X", focus shifts back to dashboard even after I've quickly moved on to something else and that tab has become active.

Version: 11.6.2.0

B