Align Powershell module version with RDM version
0 vote
The Powershell module versions should match the current RDM versions.
As the Powershell module contains the engine to access the DB and therefore must match the current state or perform an upgrade, it should match the version numbering to be able to align the module with the deployed RDM version. I cannot decipher alone from the names of the modules which version matches which RDM version.
The current list on PSGallery for 2022 is:
Version Downloads Last updated 2022.2.0.0 97 3 days ago 2022.1.3.4 (current version) 193 15 days ago 2022.1.3.3 315 a month ago 2022.1.3.2 8 a month ago 2022.1.3.1 22 a month ago 2022.1.3.0 4 a month ago 2022.1.2.1 493 2 months ago 2022.1.2.0 8 2 months ago 2022.1.1.0 417 3 months ago 2022.1.0.9 82 3 months ago 2022.1.0.8 79 3 months ago 2022.1.0.7 286 3 months ago 2022.1.0.6 572 4 months ago 2022.1.0.5 17 4 months ago 2022.1.0.4 110 4 months ago
The first RDM version listed in the release notes is 2022.1.11.0 on February 14th 2022.
This leads to a total crap shoot for trying to align versions, especially with automation. We have to determine version alignment before updating the version that gets automatically deployed on a host. It would be great to simply specify Min and Max based on the current desktop client and avoid thinking about which PS module needs to be deployed.
All Comments (4)
Hello,
Thank you for your request.
The RDM PowerShell module matches the RDM software major version. So you can base your automation script with the major version number (module 2022.1 matches with all RDM 2022.1.x versions, module 2022.2 matches with all RDM 2022.2.x version, etc).
The PowerShell module is independent from RDM minor versioning as it can be used on different platforms like Linux and Mac OS. And on those platforms, the versioning of the application is different than RDM Windows version. Every new PowerShell module version contains fixes and/or new cmdlets/switches that is not related to the RDM UI fixes or improvements.
I've asked an engineer to have a look on your request and add any additional information that could explain the difference between the versioning.
Let me know if that helps.
Best regards,
Érica Poirier
Hi Erica,
We were behind on an old version. Based on your response, are database upgrades always assigned a new major version in the current semantic numbering?
Hello,
Even if you're behind, you should be able to install the appropriate PowerShell module version with this command. Just replace the version with the one you want to install.Update-Module -Name RemoteDesktopManager -RequiredVersion 2022.1.3.4 -Force
It could happens that a database upgrade is required for minor versions. The following article shows the database versions along DVLS and SQL data sources.
https://kb.devolutions.net/rdm_version_compatibility_dps.html
Best regards,
Érica Poirier
That article is perfect. Thanks Erica!