Eric St-Martin

Hello,

I ran some tests on my side and I seem to be getting the same issue you are having.

I have gone ahead and opened a ticket with our engineering team working on the module to investigate.

Once I hear back from them I will update you in this forum.

Best regards,

Hello,

Thank you for letting us know about this issue. I have advised the engineer and there should be a new release in the PSGallery with the fix for this issue shortly.

Once it is posted, I will let you know.

Best regards,

Eric

Hello,

The importer only works with .rdm and .pvm files.

With .json files it would need to be imported via an RDM that is connected to your Password Hub.

Best regards,

Eric

Hello,

It'll come down to where you are importing the vaults and if you plan on moving them to other products.

.rdm files can be imported in all of our products.

Note: Presently Password Hub Business doesn't have this feature implement directly yet but imports can be done when used in conjunction with our Password Hub Importer:

https://devolutions.net/password-hub-importer

.json files are importable by Remote Desktop Manager. ".json" also have a higher chance of being available with other products outside of Devolutions.

Please let me know if you have any questions.

Best regards,

Hello,

We have some example scripts for our RemoteDesktopManager PowerShell module located on our github here: https://github.com/Devolutions/RDMSamples-ps

For the export all entries in all vaults, you could try the following:

#The following script will export all entries from all vaults as one file per vault. Each file is password protected.
	

	Import-Module RemoteDesktopManager
	

	# Adapt the data source name
	$ds = Get-RDMDataSource -Name "NameOfYourDataSourceHere"
	Set-RDMCurrentDataSource $ds
	

	# Adapt the password
	$passwd = ConvertTo-SecureString -AsPlainText -Force 'mypassword'
	

	$repos = Get-RDMRepository
	

	foreach ($repo in $repos)
	{
	    Set-RDMCurrentRepository $repo
	    Update-RDMUI
	

	    $sessions = Get-RDMSession
	    $reponame = $repo.name
	

	    # Adapt the destination path for file(s)
	    Export-RDMSession -Path "C:\temp\Sessions_$reponame.rdm" -Sessions $sessions -IncludeCredentials -XML -Password $passwd
	}

Please let me know if you have questions.

Best regards,

Hi Matthias,

You could use something like the below code. You'll get prompted to add credentials before the creation.

$Credentials = Get-Credential
$Entry = New-RDMSession -Type Credential -Name ' '
$Entry.Credentials.UserName = $Credentials.GetNetworkCredential().UserName
Set-RDMSession $Entry
Update-RDMUI
Set-RDMSessionPassword -ID $Entry.ID -Password $Credentials.Password
Update-RDMUI

Please let me know if you have any questions.

Best regards,

Eric

Hello,

Would it be possible to send the script you are running ?

Which version of the PowerShell module are you using ?

We are now using a PowerShell module that has been separated from RDM so maybe something would need to be changed.

Best regards,

Eric

Hello,

After some testing on our end, we have discovered a bug with the New-RDMUser. I have gone ahead and opened a ticket with the engineer working on the Module.

I will keep you posted once I get news regarding a fix.

Best regards,

Eric

Hello,

Are you connecting to the Server via RDM, at which point you want a script to be run ? Or are you looking for a PowerShell solution to do this all-in-one ?

Best regards,

Hello,

You should be able to do this via File > Options > Types > Remote Desktop > Screen Sizing Mode set to Smart Sizing. This will make the Default option on RDP sessions Smart Sizing.

Another option, if you already have some configured, you could select all your RDP Sessions and under Edit tab > Batch edit > Edit (Session Type Settings). Here you would be able to change on a mass scale all Display information for all sessions selected.

Best regards,

Hi SP,

My pleasure! Glad to hear it's working.

Best regards,

Hi SP,

Ahh that module is only available in Enterprise editions.

In your case, you could use the following on the sessions Events under Properties > Events> Before Open > PowerShell .

$rdp = (get-content "C:\Path\to\file.rdp") -like 'gatewayaccesstoken*' -split 'gatewayaccesstoken:s:' | Select-Object -Skip 1

$RDM.Connection.RDP.GatewayAccessToken = $rdp

Please let me know if this works for you.

Best regards,

Hi SP,

You could use something like this, note this would be run before connecting via Tools > PowerShell (RDM CmdLet)

$rdp = (get-content "C:\Path\to\file.rdp") -like 'gatewayaccesstoken*' -split 'gatewayaccesstoken:s:' | Select-Object -Skip 1
$session = Get-RDMsession -Name 'yoursessionname'
$session.RDP.GatewayAccessToken = $rdp
Set-RDMSession $session
Update-RDMUI

You could also try something like this on the entry itself under Properties > Events> Before Open > PowerShell

$rdp = (get-content "C:\Path\to\file.rdp") -like 'gatewayaccesstoken*' -split 'gatewayaccesstoken:s:' | Select-Object -Skip 1
$RDM.Connection.RDP.GatewayAccessToken = $rdp

This would need to be tested though. You could also point the event to a created Macro for this (note that copy/pasting will result in an error.)

Best regards,

Hello,

Could you please open a new case with us?

Please visit the customer portal for better control over the classification process of your request at https://devolutions.atlassian.net/servicedesk/customer/portal, or send an email at ticket@devolutions.net.

Best regards,

Hello,

I wanted to add that:

1. The Credential entry needs to have the Allow Password variable enabled.

2. The SSH entry needs to have the Allow Password variable enabled.

3. Under Administration > System Settings > Password Policy > Allow Password needs to be enabled.

Then the $PASSWORD$ should work without issue.

Best regards,

Hello,

Thank you for contact the Devolutions Support Team.

This is definitely possible but there are some steps that need to be done firstly.

Under Administration > System Settings > Password Policy > Allow Password in variable needs to be activated.

On both the Password and SSH entry > Security Settings > Allow Password in variable needs to be active.

Then the way to do this is using $PASSWORD$.

Best regards,

Hi Dirk,

Just to make sure I understand, are you searching for a separate script or was it regarding the script above?

Best regards,

Hello,

You could do this with a Foreach statement, small example below

$repo = Get-RDMRepository
 foreach ($repos in $repo) {
   Set-RDMCurrentRepository $repos
    Get-RDMSession | Where-Object { $_.ConnectionType -eq 'RDPConfigured'}
  }

For finding its Original Vault based off the Session ID, you would need to have the ID ahead of time and see if it exists within each Vault.

Best regards,

Hello,

There are 2 ways

• PowerShell > This creates a copy and deletes the original

$session = Get-RDMSession -Name "Session Name" 
Set-RDMCurrentRepository -Repository (Get-RDMRepository -Name "Destination Vault")
Set-RDMSession -Session $session
Set-RDMCurrentRepository -Repository (Get-RDMRepository -Name "Original Vault")
Remove-RDMSession -Session $session

• Via RDM > Edit > Move to Vault

Best regards,

Hello,

Thank you for contacting Devolutions Support.

I just want to confirm I understand fully. You are asking how to copy an entry to another Vault ?

Best regards,

This is really odd.

Could you please create a Portable version of RDM on your system and test again?

To do so, you will need to do the following:

1- Download the .zip file below: https://remotedesktopmanager.com/home/thankyou/rdmbin

2- Create a new folder on your Desktop

3- Extract the content of the .zip file into the folder created at #2

4- Go in this folder once the .zip file has been extracted and run remotedesktopmanager64.exe

5- Enter your current serial

Let me know how it goes.

Best regards,

Can you try removing any trailing spaces to see if it changes anything ?

Your credential entry is using Username/Password type of Entry or something else?

There is an '&' symbol causing the issue for some reason. Could you maybe also create a new one and see if it works.

The command is working on my end exactly as shown on a fresh install and an older install.

Hello,

Can you please remove the ".exe" from the command ? Should work after that.

Best regards,

Hello,

Thank you for contacting Devolutions Support.

Could you please confirm your Remote Desktop Manager version and which Data Source you are using ? (Note: If Devolutions Server, which version?)

Best regards,

Hello,

Thank you for contacting Devolutions support.

We don't have a list of all the information but it can be easily found. To retrieve the exact name of the fields, right-click on your session and select Clipboard – Copy. Note that you would need to have the fields filled in beforehand for it to show. As an example of info that can come out in the Clipboard. In theory, you would need to do MetaInformation\InfoNeedingToBeChanged and so on (case sensitive). Since there are a few datatypes I am not 100% all of them will work.

     <MetaInformation>
      <Architecture>64-bit</Architecture>
      <AssetTag>Test</AssetTag>
      <Blade>test</Blade>
      <BladeDetails>Info</BladeDetails>
      <Cpu>Input here or use dropdown</Cpu>
      <CPUCoreCount>4</CPUCoreCount>
      <CustomField1Value>Ok!</CustomField1Value>
      <Domain>test</Domain>
      <Drives>2</Drives>
      <Hardware>Test info</Hardware>
      <IP>192.168.137.130</IP>
      <IsVirtualMachine>true</IsVirtualMachine>
      <Keywords>ALL Stuff PCs</Keywords>
      <LogicalCPUCount>2</LogicalCPUCount>
      <MAC>Info here</MAC>
      <MachineName>101.1001.1000</MachineName>
      <Manufacturer>Dell</Manufacturer>
      <Memory>31.75 GB</Memory>
      <ModelInformation>Test</ModelInformation>
      <Monitors>2</Monitors>
      <OS>Windows Server 2019</OS>
      <PurchaseDate>2021-06-30T13:15:01.2395177-04:00</PurchaseDate>
      <Rack>Test</Rack>
      <SerialNumber>Test</SerialNumber>
      <ServerFeatureRoles>
        <string>Domain</string>
      </ServerFeatureRoles>
      <ServiceTag>Something</ServiceTag>
      <Site>Montreal</Site>
      <SocketCount>5</SocketCount>
      <SocketType>Test</SocketType>
      <Softwares>RDM, DVLS</Softwares>
      <SupportServiceLevel>Platinum</SupportServiceLevel>
      <Vendor>Dell</Vendor>
      <Version>2021</Version>
      <VirtualMachineName>Windows Server 2019</VirtualMachineName>
      <VirtualMachineType>VMware</VirtualMachineType>
      <Warranty>2029-07-17T00:00:00-04:00</Warranty>
    </MetaInformation>

Out of curiosity have you looked at maybe doing this via PowerShell using our RDM Module ? https://help.remotedesktopmanager.com/psmodule.html

Best regards,