{"id":2510,"date":"2013-11-26T00:01:00","date_gmt":"2013-11-26T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/11\/26\/remoting-week-remoting-sessions\/"},"modified":"2013-11-26T00:01:00","modified_gmt":"2013-11-26T00:01:00","slug":"remoting-week-remoting-sessions","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/remoting-week-remoting-sessions\/","title":{"rendered":"Remoting Week: Remoting Sessions"},"content":{"rendered":"

Summary<\/strong>: Richard Siddaway explains how to use WindowsPowerShell remoting sessions.\n\"Hey, Hey, Scripting Guy! I’ve just starting learning Windows PowerShell, and I understand how to use it as a scripting language and shell on the local machine. But how do I work with remote machines?\n—AP\n\"Hey, Hello AP,\nHonorary Scripting Guy, Richard Siddaway, here today filling in for my good friend, The Scripting Guy. This is the second part of a series of five posts about remoting. The series includes:<\/p>\n

    \n
  1. Remoting Recap<\/a><\/li>\n
  2. Remoting Sessions<\/li>\n
  3. Configuring Remoting<\/li>\n
  4. Remoting Security<\/li>\n
  5. Non-Domain Remoting<\/li>\n<\/ol>\n

    In my Remoting Recap post, you saw that you can use Invoke-Command<\/strong> to send a command to a remote machine over a WSMAN connection, and then receive the results back on your local machine, for example:<\/p>\n

    Invoke-Command -ComputerName $computer -ScriptBlock {Get-Service}\nThis great if you want to send only a single command. But if you have a number of commands, it is more efficient to create a remoting session to the target machine and run the commands over that. You only have one set up and tear down instead of one per command.\nYou get several cmdlets for working with Windows PowerShell remoting sessions:<\/p>\n