Weird output problem from invoke-command (get-rdmsession)
Hi
I am trying to collect information from one of our rdm servers with use of invoke-command (powershell) from another server.
The rdm server I collect info from run version 12.6.8.0.
The problem is that when I am trying to collect using get-rdmsession I get nothing back. Other cmdlets like Get-RDMCurrentDataSource, Get-RDMInstance or local cmdlets like get-process works fine. If I run get-rdmsession locally on the rdm server with the same credentials I use with invoke-command it works fine..! It happens only when I use invoke-command or even using enter-pssession. Then I don't get any output from get-rdmsession.
I have tried from another rdm server and from that I get expected output from get-rdmsession using invoke-command. I have tried to compare rdm servers and trying to find a difference. But they both are on same OS version, powershell version and rdm version. Very strange... Only differance I can see is that on the rdm server that the output works. Has the rdm sql database installed locally.
Have anyone any idea why I from one of ours rdm server can't get any output from get-rdmsession when using invoke-command??
I have also tried to narrow get-rdmsession query with specific name, but it always returns noting.
Invoke-Command -ComputerName <server> -Credential <credtials> -ScriptBlock {
Import-Module "C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.PowerShellModule.dll"
Get-RDMSession}
\Magnus
All Comments (8)
Hello,
What version of Devolutions Server (rdm server) are you using?
Could you please try to refresh the local cache file with CTRL+F5 when RDM is opened on this machine? Or you can use the Update-RDMUI cmdlet to refresh the local cache file before using Get-RDMSession.
If it doesn't work, please try to disable the Caching mode in the Advanced tab of the DVLS data source configuration (File - Data Sources).
Best regards,
Érica Poirier
Hi
RDM is version 12.6.8.0. The server I have trouble with running invoke-command command aginst only has RDM installed. RDM database is a MS SQL database that is installed on another server. We are not using Devolutions Server.
I tried what you said. Both using Update-RDMUI and tried to turn off caching mode. But there is no difference. No output from Get-RDMSession when using invoke-command.
Invoke-Command -ComputerName <> -Credential <> -ScriptBlock {
Import-Module "C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.PowerShellModule.dll"
Update-RDMUI
Get-RDMSession
}
\Magnus
I did some more testing. We have a couple of servers with rdm installed. They all use same MS SQL server as their database source. I have tried running my invoke-command agains one more of the servers with RDM installed. It is the same issue with that one aswell. get-rdmsession returns no output when using invoke-command. If I run get-rdmsession locally on the server with rdm it works fine.
Seems like I only get this problem when MS SQL database that rdm is using is not installed locally..
\Magnus
Hello,
I am unable to reproduce your issue.
Maybe this could be a local cache file issue. Could you please change the Offline engine mode to SQLite? Please go in File - Options - Advanced and set the Offline engine to SQLite. You would need to restart RDM on this server to apply the modification. Then try again to run the Get-RDMSession from the Invoke-Command.
Best regards,
Érica Poirier
Still no luck. :/ Did what you said, Offline engine = SQLLite. Restarted rdm but still no output. Should it help if I open a support case. Maybe we could run a remote session to troubleshoot?
\Magnus
Hello,
Sure we could do a remote session to see what's happening on your end. Please send us an email at support@devolutions.net and we will send you the information on how to schedule an appointment.
Best regards,
Érica Poirier
hello, we have the same problem in our environment. Did you manage to solve the problem and how?
the get-rdmsession command does not go back and no error. The get-rdmuser command raises a warning: your connection is not ready
Thanks for your feedback
Hi
Yes, got below from support and it worked with different login mode.
Hello,
Maybe we have found something. Are you using Integrated Security option as the Login mode value?
If so, this will not work with the Invoke-Command. It looks like this cmdlet doesn’t transfer the whole Windows user context and in the Event Viewer of the SQL Server, we see that it tries to login as an anonymous account on the SQL Server.
Could you please try with a database account instead? The database account must not be a domain account but a SQL account.
rdm.png