PowerShell Remote Console
This entry type seems to be very poorly documented. I can't find any references to it in either the online help or the PDF user manual on the devolutions website.
Some questions about this entry type.
1) Why when checking Advanced -> Run as Administrator will the window be outside of RDM? I can't dock it inside RDM.
2) When I open the entry if I don't like the font size and I use ctrl + scroll wheel to make the font smaller and exit the session, if I re-enter the session the font size has been reset. Why?
3) When you open an entry initially (non administrator) a powershell window is launched outside of RDM which then gets sucked into RDM after 2 or 3 seconds. Why?
4) Is there a way to set the default directory location when you open the session in? By default it always keeps opening up into C:\users\administrator\documents. Maybe I want it to open into the root of C:\? How do I change this as a default?
5) If you give RDM focus on on other entry types (for example RDP) and you focus your window on another application then focus back to RDM the RDP session still has focus. But when you do this with the PowerShell Remote Console entry type it doesn't. You have to specifically click INSIDE the powershell window to give it focus back. Why?
6) There doesn't seem to be a logoff feature of any kind. I just simply have to close the window. Why?
All Comments (2)
Hello,
Indeed this entry isn't available on our online help documentation as all entry types has been removed from the online documentation.
What RDM version are you using?
About the PowerShell Remote Console entry type, here are the answers to your questions.
1- I can reproduce that behaviour when enabling the Run as Administrator. I will check with the engineering team what can cause this.
2- We will have to look on this feature if it's possible to add properties in the entry to keep the font size.
3- That behaviour is normal as RDM will launch PowerShell and then will grab the session to embed it in the application. That maybe related to point #1.
4- I don't think that is possible to set a default working folder as this session call the Enter-PSsession PowerShell cmdlet and using it, it is not possible to set the default working folder. You could use the After Open - Macro to set the remote default folder like the following.
5- That is a problem according to the embedded PowerShell window that is not part of the RDM application and it's only an external application embedded in the application. About RDP sessions, as they are launch using ActiveX methods, we have full control over these.
6- We will have to look further on this one as indeed, there is no other method than closing the tab to close the session.
Best regards,
Érica Poirier
Hello,
About launching the PowerShell Remote Console as an administrator, because of a Windows limitation, we need to launch RDM as an administrator to get the window embedded in RDM. A lower privileges application cannot send message to another application running with administrative privileges. There nothing else we can do about it.
Best regards,
Érica Poirier