Powershell embedded script vairables

Published 10 years ago

Am I wrong or is it not possible to use the RDM Variables in a powershell embedded script?
So for example I'm trying to use the $HOST$ variable but it doesn't work when I use embedded script, but works fine when I use a single line command.
I'm completely new to getting RDM todo powershell type things so it could be that i'm missing something completely obvious.

Any point in the right direction would be greatly aprechiated.

All Comments (9)

Maurice Côté

Published 10 years ago

Hello,

I will ask someone to look into this.

Best regards,

Maurice

Hubert Mireault

Published 10 years ago

Hello,

We are able to reproduce the issue and it should be fixed in the next minor version.

Regards,

Hubert Mireault

scott02

Published 10 years ago

Awesome, thanks heaps for that :)

chanlerone

Published 10 years ago

Hi Hubert,

I have installed the latest version to see if I could leverage the variables in the scripts. However even before using that I face the execution policy issue.
I have set the exec policy to Bypass, but whenever I use the RDM Powershell snapin in always runs in restricted mode. Even if I use RDM as administrator.

Any ideas?

Cheers!

Sjoerd

Olivier Desalliers

Published 10 years ago

Hi,

If you use Set-ExecutionPolicy Unrestricted. Do you have the same problem?

Best regards,

Olivier Désalliers

chanlerone

Published 10 years ago

No in whatever mode I set the ExecPolicy RDM still tells me it's in Restricted mode.

Cheers!

Sjoerd

chanlerone

Published 10 years ago

Olivier, David, you guys have any ideas?

Cheers!

Sjoerd

Olivier Desalliers

Published 10 years ago

Hi,

It could a scope problem. If you use "Get-ExecutionPolicy -List", do you have one of your scope that is still Restricted?

Can you also send us the error you get in your PowerShell Console?

Best regards,

Olivier Désalliers

chanlerone

Published 10 years ago

Hi Olivier,

I have created two Script sessions calling the exact same embedded script. One as a PSRemote session type, that will launch straigth away (an error that is cannot reach the machine I am running the session on, but that's understandable due to firewall and VPN reasons). The other is with the PowerShell (local) session type. The latter is failing on me.

When I run the same command from Powershell this is the result:

Apologies for the HUGE characters, but sometimes my Windows 10 machines explodes.....

Any ideas?

Cheers!

Sjoerd