Do PowerShell customers need to revert to an older version?
Devolutions Team, I've become increasingly concerned regarding the resolution to the Powershell cmdlet issues:
* Accounts with MFA still cannot connect to RDM datasources.
* Attempting to login with an application password does not work, either.
I opened a ticket (DEVO-37105) that has not been updated for days, even after multiple requests for updates. I have been downloading the module updates in hopes that it would resolve it. I've been watching the thread for "Set-RDMSessionPassword on private session does not update completely" and seeing it still is broken.
For customers who are dependent on the Powershell module, should we revert to an older version? We literally have projects on hold because we thought this would be resolved fairly quickly.
Thanks,
Paul
All Comments (11)
Hello Paul,
Have you tried to use the old version side by side and execute the previous PowerShell? I will talk with the developer and see what can be done. I know that Jonathan is really working hard to improve the situation.
Regards
David Hervieux
Hello,
Thank you for contacting us on that matter!
The agent in charge of your ticket has replied to you yesterday, have you received his reply? Are you currently on the latest version of the Devolutions Server? It is required for the new RDM PowerShell module to be able to connect to it.
Best regards,
James Lafleur
I did not get that reply. My last correspondence from Devolutions was on 10/18.
RDM version: 2021.2.18.0
PS Module version: 2021.2.0.24
DPS version: 2021.2.8.0
Database version: 720
Hello Paul,
Have you tried to use the old version side by side and execute the previous PowerShell? I will talk with the developer and see what can be done. I know that Jonathan is really working hard to improve the situation.
Regards
Thanks David. 2021.1.44.0 with the integrated cmdlets does not have the issue.
Hi Paul,
I would like to know what 2FA solution your a using.
I'll see if we can support it in the PowerShell module and upload a release as soon as possible.
Regards
Jonathan Lafontaine
Hay Jonathan, we are using Google 2FA as our MFA. Thanks for your hard work in getting issues resolved so quickly!
Hi Paul,
Version 2021.2.0.25 should let you enter the required information to complete Google 2FA authentication.
Let me know if this solves your issue or if you experience different ones.
Regards
Jonathan Lafontaine
Hey Jonathan. Unfortunately, I still do not get prompted for MFA.
On a system with RDM installed, either from ISE or from RDM -> Tools -> Powershell (RDM CmdLet) :
PS C:\Windows\System32\WindowsPowerShell\v1.0> import-module RemoteDesktopManager
PS C:\Windows\System32\WindowsPowerShell\v1.0> Get-Module -Name RemoteDesktopManager | select version
Version
-------
2021.2.0.25
PS C:\Windows\System32\WindowsPowerShell\v1.0> get-rdmdatasource
ID : 402d92ac-5db1-47d7-9b94-d5865611bb65
IsConnected : False
IsOffline : False
Name : mydevolutionserver
Type : RDMS
PS C:\Windows\System32\WindowsPowerShell\v1.0> get-rdmsession
get-rdmsession : Connection not found.
At line:1 char:1
+ get-rdmsession
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Get-RDMSession], Exception
+ FullyQualifiedErrorId : 0,RemoteDesktopManager.PowerShellModule.GetRDMSessionCommand
PS C:\Windows\System32\WindowsPowerShell\v1.0>
Would you be open to test a beta build with more logging to try and pin point where the issue might be?
Jonathan Lafontaine
Sorry for the delay. Yes, I have a non-user facing DEV box that is built using the same scripts as production, so functionally identical. We can break that all day long to assist in isolating the issue.
Closing the loop on this, version 2021.2.0.29 has fixed the issue and I am now able to connect to my RDM with an enterprise (DPS) backend without issues. Thanks to Jonathan Lafontaine for doggedly stick with this until it was fixed!