Update with .exe compared to .msi

Hello Deas

First, I'm glad that this is working well when you install using the .exe. This has been a long-standing issue with the RDM install so I'm glad our fixes last year have helped.

I'm not familiar with Patch My PC directly, but I have some idea as to why it might not be working. We workaround the issue of the lost taskbar pin by running some custom PowerShell at the end of the installation process. However, one limitation I'm aware of is that this script only fixes the pin for the current user. If Patch My PC is running the install in the context of a different user, for example, the script won't work.

I have some ideas on how to fix this but I'd like to confirm the issue. Is it possible for you test this? After updating RDM with Patch My PC (and losing the taskbar pin), can you open an administrator PowerShell prompt and execute the "OptimizeRDM.ps1" script that's in the RDM install directory (%programfiles%/devolutions/Remote Desktop manager)? Is the taskbar pin restored, or perhaps the script outputs some error information?

Please don't hesitate to post back if something isn't clear or you have further questions

Kind regards,

Hello,

That explains it. SCCM runs the update with System permissions. Patch My PC only does the download and packaging part for SCCM to get the workload for this from the admin away. The deployment is done with native SCCM capabilities.

Do you see any chance to implement a fix for this issue in the .msi installer also?

I don´t know SCCM in deep as this is not my part, but I will talk to my SCCM specialist if it is possible to install the update as System and then start the PowerShell in user context with admin rights to fix the icon.

EDIT: I will try to do the .msi update and manual PowerShell script as requested by you next week! It´s already Friday afternoon here in Austria and the weekend is calling... :)

Brgds Andreas

Hello Andreas

Do you mean the installer is run as SYSTEM? The .msi normally obtains administrator permissions to run, but the post-install script is run with "impersonation" allowing it to interact with the currently logged in user account. So if the user that runs the installer is different to the "actual" user of the machine, this will probably fail. It sounds like this is the issue.

From our side, I believe we can modify our script to run for all users on the machine which is likely a broad improvement over what we have anyway, and I believe it should fix this issue.

I'm opening a ticket on our side to address this. The timing is convenient because I was also planning to make the same fix for the DVLS console installer. I'll add this forum thread to the ticket and we'll post back here once there's an update on this.

I apologize for the inconvenience, and thank you for your patience. If you have further questions or comments please don't hesitate to post back.

Kind regards,

Hello,

Yes - as far as I know and my SCCM colleague told me, SCCM executes this in his own context which is SYSTEM. This has nothing to do with manually starting the .msi installer.

If you could do this for all users it would be great! Do you still need my test?

Nothing to apologize for - this is just a minor issue, even if it is somehow annoying. I have an issue which hurts me more and unfortunately nothing happens. Credential "Linked (User Vaul)" not available for RDP Gateway Credentials (devolutions.net) What must I do to get this implemented as soon as possible?!? Sorry for hijacking this thread...

Brgds Andreas

Hello Andreas

Yes, I believe this is technically possible on our side and I don't think you need to make a test. I know it's a "minor" issue but oftentimes these can be the most annoying.

Regarding your other ticket; I did take a look at that. The latest notes are that this is to be implemented in time for the 2023.2 release, and it's at the top of the backlog for non-PI (i.e. new features) issues. I'm sorry if it's not as soon as you were hoping for but wanted you to know that the RDM Windows team is aware of the issue and does have it prioritized.

Please let me know if you have any further questions or comments, and once again thank you for your patience.

Kind regards,

Hello,

Perfect - if you need a test, just get back to me.

Thanks for taking a look at the other ticket! I got the impression that it will/should be implemented with 2023.1 and that is what I communicated internally to my manager. Hearing now that it will come with 2023.2 makes my life not easier. Do you have an ETA for 2023.2?

To be honest, I think it can´t be that hard to implement this as it is already working this way for all other places I know where I am able to select a secret from Delinea Secret Server to use. And with 2022.x versions and a local SQLite database it is working this way. I really don´t understand why somebody thought it is a good idea to be able to store the Delinea Secret Server secret to use on every place a secret can be used, but for an RDP gateway we prompt the user every time.

Thanks a lot for your help!

Brgds Andreas

Hello Andreas,

Thank you for sharing your concerns, and I apologize for any confusion or inconvenience caused by the change in the release schedule. The 2023.2 release is currently planned for the end of June. We understand that this may not be ideal for you and your team, and we appreciate your patience in this matter.

Though the feature modification may appear simple, it requires coordinated efforts across multiple platforms (Mac, Linux, iOS, Android), which makes it challenging to include in a minor RDM version. Rest assured, we will provide updates as soon as more information about the feature becomes available.

Best regards,

Hello Andreas

RDM Windows 2023.1.22 is now available for download; I added some changes here that I think will retain the taskbar pins for all users on the machine. I'm hoping that this fixes your issue - please don't hesitate to post back if that's still not working right, or you have further questions or comments.

Thanks and kind regards,

Hello,

thanks a lot for your quick support! I just downloaded the version and will try the install on Monday - now I have to leave. I post an update as soon as I know the result.

Brgds Andreas

Hello,

I "simulated" such an update now - started a cmd as system and executed the setup with "/passive" - RDM was updated AND my icon is OK!

Thanks a lot for your help!

Brgds Andreas

Hi Andreas

Good news! Thanks for the update and please don't hesitate to post back with further questions or comments.

Kind regards,