dmitzman

Thanks for the link. Very helpful! I forgot to post my results but everything worked out as anticpated.

We are preparing to move from straight RDP to utilizing a secure RF gateway. I was able to manually create a session and it worked just fine but we need to migrate all our connections so I was planning to use powershell to script it out.

Problem is, I can't find in the documents how to create that object and add it to the RDMSession. Any thoughts or section of the documentation you can point me to?

@dmitzman

Figured it out. I exported the test entry as xml and saw the settings under the RDP node which translates to the RDP property of the RDMSession so I should be good. I'll test tomorrow and post my results.

We are preparing to move from straight RDP to utilizing a secure RF gateway. I was able to manually create a session and it worked just fine but we need to migrate all our connections so I was planning to use powershell to script it out.

Problem is, I can't find in the documents how to create that object and add it to the RDMSession. Any thoughts or section of the documentation you can point me to?

Perfect. It def slows down but that's not a big deal for this. Thank you very much for all the help.

OK I found something. If I do an Update-RDMUI between each call, it seems to work.

OK I can see the light at the end of the tunnel but here's what I do

New-RDMSession -type Group -Name "Hotel Servers" |Set-RDMSession #great, works and creates at root
New-RDMSession -type Group -Name "Site A" -group "Hotel Servers\Site A" | Set-RDMSession #fails with Connection has invalid group specified

I can see the "Hotel Servers" folder at root when I look in RDM but just not sure why the subfolder creation fails. Seems that it should work based on your post.

Yeah that's what I figured but I'm hitting a weird roadblock. For example

$newfolder = New-RDMSession -type Group -Name "Hotel Servers" 
Set-RDMSession $newfolder #creates a folder at root called "Hotel Servers"
$newfolder = New-RDMSession -type Group -Name "Site A" -Group "Hotel Servers" #i want this to be created under Hotel Servers folder
Set-RDMSession $newfolder #fails with "invalid group specified"

$newfolder = New-RDMSession -type Group -Name "Hotel Servers\Site A" 
Set-RDMSession $newfolder #I want this to be created under Hotel Servers folder and this does it but I end up with a structure "Hotel Servers" -> "Hotel Servers\Site A"

Am I just doing this wrong?

Ok last one, I swear. If I'm doing the Copy-RDMSession and the existing folder is nested (so $oldsession.Group = "Servers\Location A\Services"), If that doesn't exist in the new vault, I get a "Connection has invalid group specified".

I can't manually create it without the folders existing to begin with, correct? I'd have to loop through and create the folders prior to setting the session?

Gotcha. Thank you!

Thank you. In my case, personal credential GUID is actually 9F3C3BCF-068A-4927-B996-CA52154CAE3B.I will leverage that, thank you.

So that's working great. One thing I'm trying to do is if credentials aren't set to "My Personal Credentials", I want to leave the session alone and just straight up copy instead of setting alternate shell, etc.

I can look at $oldsession.credentials but I don't see a way to determine if a credential is my personal credentials or selected from a vault of pre-set credentials. Any ideas?

Thanks Jonathan. How I didn't even see this cmd is beyond me. I'll attribute it to being a Friday lol. I'll give this a go and report back.

I'm working on a POC utilizing CyberArk with alternate shell. What I want to do is create a new vault, clone all our RDP sessions from our default vault to the new one and test. I would do it like this (psuedocode)

Get All RDM Sessions that are RDPConfigured and loop
  - clone the session to a new var i.e. $newsession
  - set $newsession host, alternate shell, and credentials appropriately
  - change to new vault with Set-RDMCurrentVault
  - Set-RDMSession $newsession (copyes it to the new vault)

My problem is that I can't just do this $newsession = Get-RDMSession $oldsession because Get-RDMSession doesn't accept an object as parameter.

If I do $newsession = Get-RDMSession $oldsession.Name I end up with an issue when I have multiple sessions with the same name (it happens, I know it shouldn't but it does) and I'd like to avoid having to loop through in this instance to keep my code clean.

Is there a way to do a Get-RDMSession on just an ID or something that would be unique?

Absolutely. As long as there's a tool tip on the button shows that for users who might not be familiar that should be great.

That's correct. We're using the VMRC integration with PowerCLI. This is what a session looks like:

I checked their site and they have a code repository here https://www.nutanix.dev/code_samples/ and a Github repository here https://github.com/nutanixdev/. I'm not sure if that has everything you would need but if not, I can see if our Infrastructure team can reach out to them and find out.

We have recently begun rolling out Nutanix Prism Central to replace some instances of VMWare Vcenter. Would it be possible to have a session type for Prism Central built within RDM like there is one now for VCenter (PowerCLI / VMRC / etc.)?

We have RDM setup with numerous connections to virtual servers through PowerCLI (due to various firewall rules preventing using RDP). It would be great if we could set a keyboard shortcut for RDM to send ctl-alt-del commands without having to navigate to the actions tab and clicking ctl-alt-del button.

In our environment, we have our PCI compliant servers on their own VLAN with RDP traffic restricted. The only way to access them is via LanDesk remote control. I believe it would be beneficial to have a LanDesk plugin through RDM so we could manage our connections there.