RDM PowerShell module

Hello,

Thank you for reporting this. We will update the Release Notes as well as the the online documentation help and will notify you once completed.

Best regards,

Hello,
I just have updated the release notes with the breaking change and the link.

Regards

Hello,

The RDM online help has been updated.

Best regards,

The RDM online help has been updated.

in the article PowerShell Module (remotedesktopmanager.com), there is still reference to old module name, in the following code example:

Get-Command -Module RemoteDesktopManager.PowerShellModule

Hello,

Thank you for reporting this oversight. We will update it soon.

Best regards,

I'm also having lots of issues after upgrading both my RDM (2021.2.16.0) and PowerShell module (2021.2.0.18) to the latest versions at the time of writing.

Get-RDMCurrentDataSource returns the current data source information but the commands to get credentials out of credential sessions is completely broken!!

Get-RDMSessionDomain -Session $CSession
Get-RDMSessionUserName -Session $CSession
Get-RDMSessionPassword -Session $CSession

all return the following error

Get-RDMSessionPassword : Object reference not set to an instance of an object.
At line:1 char:1
+ Get-RDMSessionPassword -Session $CSession
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-RDMSessionPassword], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,RemoteDesktopManager.PowerShellModule.GetRDMSessionPasswordCommand

This is such a critical issue for us and in all my years using RDM I've never seen a botched release such as this !!

I feel like this should be filed into "feature no one asked for. ever." Was there a change advisory board where the was a discussion that went "you know what we should do, take away a an existing feature... because... reasons."? The release notes are also not very forthcoming. The release changes says "New PowerShell module (multi platform) now available for download in PSGallery". That reads as an addition, not a subtraction. While it is under the heading Breaking Change, it does not say "Removed a component of RDM so integrated into the native product, we include it as a menu option under the Tools menu."

Sorry for the sarcasm, but my request is that you please stick to the changes requested by the customers and not make arbitrary changes that negatively impact the customer experience.

@Paul07

I understand your frustration. We will try to do better the next time. We will publish a blog about it soon. Here are some pros

• Can be execute in a schedule task (requested by many users)
• Cross-platform: it supports now RDM macOS and Linux (requested by many users)
• Compatible with PowerShell Core (requested by many users) including PowerShell 7
• No need to install RDM on the machine, only the PowerShell module (requested by many users)
• Can be updated independently of RDM

Regards

Thanks for responding, David. I shouldn't have vented my frustration. I do believe you and the program managers have the customers' best interests in mind and sometimes those interests require breaking changes. I think these types of changes should have some upfront communications to assist in transitioning before executing the changes. For example, now that I have installed the cmdlet from the PowerShell Gallery, I can't find a way to connect. The old Powershell cmdlet would auto-connect but the new Powershell cmdlet does not and the module does not have a connect-rdm* verb so there must be a new way to connect/authenticate to the RDM.

For me, what was expected to be a routine Sunday upgrade has become a re-learn and recode all of the RDM PowerShell scripts with insufficient documentation. This is not a vent, this is just to let you know the customer impact of at least one customer.

Ideally, a change like this would have an overlap period where the legacy method would have had a warning like "Warning: the Powershell module that comes with RDM is being deprecated, please upgrade to the new cmdlet by running 'Install-RemoteDesktopManager -scope AllUsers'." And when running the new cmdlet, a header like 'Welcome to the new RemoteDesktopManager Powershell cmdlet. To create a new RDM connection, run the following cmdlet: xxxx"

Even with these growing pains, RDM and DPS are still the absolute best administration tools I've ever used and my team will attest that I can't stop talking about how much I love them. Thanks for the great products and for taking a personal interest in the frustrations of this customer.

-Paul

For me, what was expected to be a routine Sunday upgrade has become a re-learn and recode all of the RDM PowerShell scripts with insufficient documentation. This is not a vent, this is just to let you know the customer impact of at least one customer.

Not only one customer. I haven't yet discovered all the scripts that are broken and need changes. But I already had to change required module name...

Module on PowerShell Gallery is good, but then it could also contain help topics which are correct, have examples and online help links. That would help changing all the scripts...