HI,
In this code :
$RDPSessions = Get-RDMSession | Where-Object {$_.ConnectionType -eq "RDPConfigured"}
foreach ($s in $RDPSessions)
{
# Get Username and password to store in Vault
if ($s.rdp.Domain) {
$username = -join($s.rdp.UserName, '@', $s.rdp.domain)
}
else {
$username = $s.rdp.UserName
}
$password = Get-RDMSessionPassword -Session $s -AsPlainText
}
I get the error :
$password = Get-RDMSessionPassword -Session $s -AsPlainText
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The method or operation is not implemented.
The entry (some datas are obfuscated):
<?xml version="1.0"?>
<RDMExport>
<Connections>
<Connection>
<Url>12.12.12.12</Url>
<AllowPasswordVariable>true</AllowPasswordVariable>
<ConnectionType>RDPConfigured</ConnectionType>
<CreatedBy>MAQ\user</CreatedBy>
<CreationDateTime>2023-07-05T10:18:25</CreationDateTime>
<Description>description 1
Description 2
</Description>
<ID>cef686c9-b80e-4d65-9848-5d5c9237430f</ID>
<Name>MY-HBGT7</Name>
<OpenEmbedded>true</OpenEmbedded>
<PinEmbeddedMode>False</PinEmbeddedMode>
<StatusMessage>MAQ\USER : 01-04-2021
!! DO NOT UPDATE RULES !!</StatusMessage>
<RDP>
<SafePassword>xxxxxxxx==</SafePassword>
<UserName>administrateur</UserName>
</RDP>
</Connection>
</Connections>
<DatabaseID>A9A91957-E24A-41AA-B249-9DD89AFA348D</DatabaseID>
<Version>2</Version>
</RDMExport>
Thanks you
Edit: pwsh 7.2.5 + Devolutions Module 2023.2.0.1 ; RDM 2023.1.26.0
Hello,
Thank you for reporting this issue.
For most of my RDP entries stored in a shared vault, I can get their passwords. But for one RDP entry, I get the same error message.
I will verify with our engineering team and will keep you posted.
Best regards,
Érica Poirier
Hello,
The problem is because of the status message. The module doesn't handle the OK/Cancel buttons from the status message property.
A workaround would be to set the message in Events - Before Open instead of the Status message property.
Otherwise, it's not possible to use the module to get the password of these entries.
Let us know if you have further questions about this.
Best regards,
Érica Poirier
Ok, thanks you. Perhaps I can remove the message, do my stuff and put it back.
And perhaps you can suggest to your engineering team to add a '-AcceptStatus' parameter ;-p
Hello,
Thank you for your suggestion.
The information has been transmitted to the engineering team for further analysis. We will let you know if it's something possible.
Best regards,
Érica Poirier
Any update? I'm delighted I got on your article. Because I want to write an essay assignment about the creation myth, I was seeking this website https://www.grabmyessay.com/samples/category/engineering where I could read essay samples for free. While browsing for it online, I also came across your post.
Hello,
There is no update available at this moment.
Once our engineering team will make any progress on this, we will post it here.
Thank you for your patience.
Best regards,
Érica Poirier
As I said, save the status in a $var, empty the status, do your stuffs and put the message back, works.
Hello,
Thank you again Joffrey for your workaround.
With the latest Devolutions.PowerShell module 2023.2.0.3, it's now possible to use the ForcePromptAnswer switch to answer the Yes/No, Yes/No/Cancel and Ok/Cancel prompts. It will not be possible to use it for any other prompts in RDM than the ones listed above.
Here is a sample for this new switch.
$password = Get-RDMSessionPassword -Session $session -AsPlainText -ForcePromptAnswer Yes
Let us know if you have any questions about it.
Best regards,
Érica Poirier