Product: PowerShell Studio 2025 (64 Bit)
Build: v5.9.252
OS: Windows 10.0.19045
PS Version(s): 5.1.19041.1, 7.4.2, 7.3.4
Hi,
I find using Remote Consoles very useful - however, if the remote connection (PSSession) is disconnected unexpectedly there's no warning of this and the Console reverts from a "remote" to "local" one. So the potentially dangerous command that was aimed at a remote target can get unintentionally actioned on the local machine.
Other than hitting return and checking the prompt before issuing commands (which is still not an 100% guarantee), is there a practical way to guard against this, either natively in PowerShell or in PowerShell Studio's Remote Consoles?
I guess this is essentially a feature of psSessions (and the ISE's Remote Tabs do the same) but would it be a feasible feature request that the Remote Consoles in PowerShell Studio only work to the psSession and not locally (or something to that effect)?
Build: v5.9.252
OS: Windows 10.0.19045
PS Version(s): 5.1.19041.1, 7.4.2, 7.3.4
Hi,
I find using Remote Consoles very useful - however, if the remote connection (PSSession) is disconnected unexpectedly there's no warning of this and the Console reverts from a "remote" to "local" one. So the potentially dangerous command that was aimed at a remote target can get unintentionally actioned on the local machine.
Other than hitting return and checking the prompt before issuing commands (which is still not an 100% guarantee), is there a practical way to guard against this, either natively in PowerShell or in PowerShell Studio's Remote Consoles?
I guess this is essentially a feature of psSessions (and the ISE's Remote Tabs do the same) but would it be a feasible feature request that the Remote Consoles in PowerShell Studio only work to the psSession and not locally (or something to that effect)?
Statistics: Posted by mark106 — Thu Jan 23, 2025 3:45 am