{"id":3251,"date":"2009-12-29T14:50:37","date_gmt":"2009-12-29T14:50:37","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2009\/12\/29\/bringing-remote-commands-to-your-local-session\/"},"modified":"2019-02-18T13:06:03","modified_gmt":"2019-02-18T20:06:03","slug":"bringing-remote-commands-to-your-local-session","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/bringing-remote-commands-to-your-local-session\/","title":{"rendered":"Bringing remote commands to your local session"},"content":{"rendered":"

How can you manage multiple technologies installed on separate machines<\/u> that expose their management surface through cmdlets?  One approach would be to open remote desktop connection to each of those machines, another approach would be to send commands using Invoke-Command and PowerShell Remoting.  But remote desktop is not a feasible solution for automation and invoking remote commands using Invoke-Command cmdlet can sometimes get burdensome – tab completion is missing, verbose incantations are needed for passing arguments to remote commands<\/a> and Get-Help -Online doesn’t quite work in a remote session. <\/p>\n

That\u2019s where IMPLICIT REMOTING<\/strong> comes to play \u2013 ability to import remote commands into your local session. One can even store the information about imported commands on disk for later use, details in a later post<\/a>. Implicit remoting is a feature that smoothes out the user experience of invoking remote commands.<\/p>\n

Importing remote commands into local session<\/h3>\n

Let’s see how one can import a remote command into a local session. First \u2013 let\u2019s ask Import-PSSession cmdlet to look in the remote session $s, take all the remote commands matching "*-Process" wildcard, add a "Remote" prefix to their noun, and then present them to me as if they were local commands: <\/p>\n

PS> $s = New-PSSession<\/a> -ComputerName lukasza5 -Credential REDMOND\\lukasza\nPS> Import-PSSession<\/a> -Session $s -CommandName *-Process -Prefix Remote\nModuleType Name                      ExportedCommands\n---------- ----                      ----------------\nScript     tmp_a50e3c88-46f1-4c25... {Stop-Process, Get-Process, Debug-Process, Wait-Process...}<\/pre>\n
Implicit remoting experience<\/h3>\n
The basic promise behind implicit remoting is that you can work with remote commands using local syntax. In particular – after Import-PSSession did its magic I can invoke remote commands as if they were local commands. Let’s see if Get-RemoteProcess really works on a different machine than Get-Process: <\/p>\n
PS> Get-RemoteProcess -Name w*host\nHandles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id ProcessName\n-------  ------    -----      ----- -----   ------     -- -----------\n    313      10    39000      51044   162     2.18   2348 wsmprovhost\nPS> Get-Process -Name w*host\nHandles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id ProcessName\n-------  ------    -----      ----- -----   ------     -- -----------\n    216      11     2056       6132    61     0.09   1208 WUDFHost<\/pre>\n
Below is a list of other things that you can try: <\/p>\n