Devolution Launcher on Terminal Server

Devolution Launcher on Terminal Server

0 vote

avatar

Hi There,

Current scenario;

We have Devolution Launcher installed a Windows 10 multi-host VM on Azure, all the vendors remote onto this 1 virtual machine to use Devolution Launcher to RDP their sessions.

Is there any way to auto-configure the Data Source for new users when they first login to auto populate the "Host" field and " Username" field with %USERNAME@%DOMAINDNSNAME%

I know there is a method for RDM with custom installer which is available for Launcher.

But is there any work around I can do with Launcher to streamline the process.

All Comments (6)

avatar

Hello,

We received a request very recently on adding the custom installer feature for Launcher: https://forum.devolutions.net/topics/43231/launcher-custom-installer
We will note your interest in this as it would simplify deployments of Launcher.

At the moment you might be able to achieve something like this manually if you install through scripting or SCCM for example and package the configuration files alongside the Launcher installation.

Regards,

Hubert Mireault

avatar

Hello,

The following script can help your users to automatically create the data source or update the existing one.

The script requires PowerShell 7 and the Devolutions.PowerShell module.
https://docs.devolutions.net/powershell/rdm-powershell/rdm-powershell-core-module/

It's important for the script to be executed before loading the Devolutions.PowerShell or running one of its cmdlets.

$override = Get-RDMPowerShellOverride
$override.OptionFilePath = 'C:\my\path\LauncherRDM.cfg'
Set-RDMPowerShellOverride

# Create a new data source
$nds = New-RDMDataSource -Name 'My Data Source Name' -DVLS -Username '%USERNAME@%DOMAINDNSNAME%' -Server '%USERNAME@%DOMAINDNSNAME%' -SetDataSource
#

# Or Update a data source
$nds = Get-RDMDataSource -Name 'Data Source To Modify'
Set-RDMDatasourceProperty -DataSource $nds -Property UserName -Value '%USERNAME@%DOMAINDNSNAME%'
Set-RDMDatasourceProperty -DataSource $nds -Property Server -Value '%USERNAME@%DOMAINDNSNAME%'
Set-RDMDataSource -DataSource $nds
#	

$override = Get-RDMPowerShellOverride
$override.OptionFilePath = ''
Set-RDMPowerShellOverride


Let us know if that works.

Best regards,

Érica Poirier

avatar

Thanks Erica,

The login user won't be able to have the ability to run the script manually. I was thinking to apply a GPO to run the script on login.

Since the script will run everytime they login, if they already have the data source setup, I don't want the script to create another duplicate data source, but to only create a data source if they don't have one. This will make it easier to manager new and existing users

If I use the script above will it achieve that?

avatar

Hello Michael,

Thank you for your feedback.

Here is the script you can use to test whether the data source already exists to avoid creating it multiple times. Please update the data source name 'My Data Source Name' in the script with the one you want to use.

$override = Get-RDMPowerShellOverride
$override.OptionFilePath = 'C:\my\path\LauncherRDM.cfg'
Set-RDMPowerShellOverride

# Test if the data source already exists
$ds = Get-RDMDataSource -Name 'My Data Source Name'

if ([string]::IsNullOrEmpty($ds))
{
    # Create a new data source
    $nds = New-RDMDataSource -Name 'My Data Source Name' -DVLS -Username '%USERNAME@%DOMAINDNSNAME%' -Server '%USERNAME@%DOMAINDNSNAME%' -SetDataSource
    #
}
else 
{
    # Or Update a data source
    Set-RDMDatasourceProperty -DataSource $ds -Property UserName -Value '%USERNAME@%DOMAINDNSNAME%'
    Set-RDMDatasourceProperty -DataSource $ds -Property Server -Value '%USERNAME@%DOMAINDNSNAME%'
    Set-RDMDataSource -DataSource $ds
    #	
}

$override = Get-RDMPowerShellOverride
$override.OptionFilePath = ''
Set-RDMPowerShellOverride


We recommend testing it before deploying it at large.

Let us know if that helps.

Best regards,

Érica Poirier

avatar

Hi Erica,

I get the following error when running the script

Please advise


My Data Source Name.jpg

avatar

Hello Michael,

I forgot to mention that you must adapt 'My Data Source Name' with one of your existing DVLS data source names. From the error message you posted, it's Devolution Server.

Let us know if that helps.

Best regards,

Érica Poirier