noc02

For anyone upgrading to 2026 this patch Tuesday. I can confirm that this still does work.

.\Setup.RemoteDesktopManager.win-x64.2026.1.12.0.msi /quiet INSTALL_DOTNET_RUNTIME="1"

@Jacob Lafrenière - We have deployed 2.16 it and tested with two machines now and the issue seems to be resolved. I'll update if we find any that don't work.

Hello,

Thank you all for reaching out on this matter.

We found out there was another related issue with the initial problem.

We were able to reproduce the issue you are all experiencing. It has been reported to the development team, and they will begin working on a fix soon.

I will follow up here as soon as a fix is deployed in a future update.

Best regards,

@Jacob Lafrenière

Has there been any updates on this issue? We are encountering the same issue.

Ok, just to confirm, the installation switches are the same?

What we used for 2024 -

/quiet INSTALL_DOTNET_RUNTIME="1"

Hello,

Can you please add the installer for .net 9 into the installer for RDM 2025 the same way you did with .net 8 and 2024? We reported this to you in 2024 as our users do not have local admin and no way to install .net 9 without IT intervention.

This should be the go forward for all future releases. It worked extremely well with 2024.

Thanks,

Jeff L

Hubert,

They are similar and they do show up under the Virtual Machines section also, but Azure Virtual Desktop is it's own entity (section) and runs pools of VMs and enables scalability. I'm not sure if they are handled differently on the Azure back end or not.

Thanks,

Jeff L

We would like to be able to synchronize our Azure VDI Session Hosts to DVLS / RDM to use as RDP entries. We would also like RDP Shadow features for these entries as well.

Richard,

I just wanted to stop back and thank you for getting this resolved for us. We have now upgraded all of our users and there was not one complaint or issue in doing so via Intune.

Thanks!

Sorry for the delay, but I was finally able to test this.

Via company portal I was able to upgrade successfully to 2024.1.25.0 and .net 8.0.4 did install with it.

I used the switches /quiet INSTALL_DOTNET_RUNTIME="1"

I guess we will have to have users manually update via company portal as we don't have access to command line switches when using ManageEngine Patch Manager Plus (how we normally patch/upgrade RDM). This is ok as we now have a path forward. Thanks!

Richard,

Thank you for the heads up. We will wait until there is a solution directly in the RDM installer it's self. Please keep us posted.

Thanks,

Jeff

Unfortunately we don't run chocolaty so that doesn't help us at the moment. Can I be notified when you have the installer packaged together?

Thanks,

Hello,

Is there a plan to build the .net 8 requirement into the RDM installer and not force a separate install? .net 8 is very difficult to install via Intune due to no .msi installer being available and none of our users have admin rights on their baseline laptops to install it themselves. As of right now we are pretty much stuck on the last 2023 release for RDM and subsequently DVLS as well.

I tried change the credentials on the Login tab to something wrong and I still just get the same error that says the server is not operational.

Kelemvor,

They had me install RSAT AD/DS tools on the DVLS server and then run ldp.exe to connect to the secondary domain to prove that LDAP is working. May want to give that a go on your end as well. Once RSAT AD/DS is installed just search for ldp.exe and run it as admin.

Hello,

We are also having this issue and it has been reported in Support Ticket : 00047950 for tracking. We get "bad username or password" when trying to AD sync from another domain. We have tested with support and LDAP communication is open and functioning to the secondary domain.

Thanks!

Hello,

We would love to see group provisioning from Azure Single Sign On added as a feature. With a hosted Azure DB connected to Azure AD we really shouldn't have to create users accounts one by one in the DB. I see specifically in your Enterprise App under the provisioning tab that it directs us to create users manually. Is this a feature on the road map?

Thanks,

Jeff