April 2010-intro-to-remoting-part2
Download as PPTX, PDF0 likes1,193 views
This document discusses PowerShell remoting, including reusable sessions, interactive sessions, and running single commands remotely. It covers core remoting commands like New-PSSession and Invoke-Command. The document demonstrates creating reusable sessions to run multiple commands against machines, passing variables to remote hosts, and restricting the commands allowed in an interactive session for security. It provides resources for learning more about PowerShell remoting.
April 2010-intro-to-remoting-part2
- 1. Introduction to PowerShell Remoting, Part 2Matt Johnson, GSEC, MCSEmatt@michiganpowershell.com
- 2. What are we going to cover?Remote CommandsReusable Sessions with PS RemotingInteractive Sessions with PS RemotingTemporary Sessions with PS Remoting
- 3. Remote CommandsNew-PSSessionGet-PSSessionEnter-PSSessionExit-PSSessionRemove-PSSessionInvoke-Command
- 4. PS Remoting HelpGet-Help about_Remotingabout_PSSessionsabout_Remote_Requirementsabout_Remote_FAQabout_Remote_Troubleshooting
- 5. Reusable Sessions with PS RemotingIt is really easy to create a new PS Session$dc = New-PSSession –computerName DC1It is also really easy to enter that sessionEnter-PSSession –Session $dcMore about that later!
- 6. Reusable Sessions with PS Remoting Cont..Less network / CPU cycles used when using Reusable sessions compared to running individual commands.You can run one off commands if you are using Reusable sessionsUse Reusable sessions when you need to run more than one command against a computer.
- 7. Demo
- 8. Running Commands against muliple machines$sessions = New-PSSession pc1, pc2, pc3Invoke-Command { Md HKLM:\Software\mwjcomputing } –Session $sessions
- 9. Passing Variables to Remote HostsYou can pass variables to the Invoke-Command cmdletYour script block must use the param statementUse the –ArgumentList switch
- 10. Demo
- 11. Interactive SessionsRun at a console just like you are sitting there at the machine. Run all normal PowerShell commandsYou can restrict the commands that can be run remotely.
- 12. Demo
- 13. Code to change what is allowed to run# Disable access to all applications$ExecutionContext.SessionState.Applications.Clear()# Disable access to scripts$ExecutionContext.SessionState.Scripts.Clear()# Define a list of allowed commands$RequiredCommands = "Exit-PSSession", "Get-Command", "Get-FormatData", "Get-Help", "Measure-Object", "Out-Default", "Select-Object"$Commands = $RequiredCommands + "Get-Process", "Get-Service", "Where-Object", "ForEach-Object"# Make everything except the allowed commands private (not visible)Get-Command | Where-Object {$Commands -notcontains $_.Name} | ForEach-Object {$_.Visibility="Private"}# Restrict the language elements to a very limited set. The possible values are FullLanguage,RestrictedLanguage, and NoLanguage$ExecutionContext.SessionState.LanguageMode="RestrictedLanguage"
- 14. Code to change what is allowed to run cont.Save as:%windir%\system32\WindowsPowerShell\v1.0\restricted.ps1
- 15. Running single commandsUse Invoke-CommandResults are returned as text, not as objectsAdds some overhead by doing it this way
- 16. DEMo
- 17. Remoting ResourcesTwo very useful resources!Get-HelpPowerShell.com’s Administrators Guide to PowerShell Remoting
- 18. ContactMatt JohnsonPhone: +1 (734) 931-0323Web: http://www.mwjcomputing.com/Blog: http://www.mwjcomputing.com/blog/Twitter: http://twitter.com/mwjcomputingEmail: matt@michiganpowershell.com
- 19. Thanks!