Feb 2010 Intro To Remoteing Part1
Download as PPTX, PDF0 likes1,178 views
This document provides an introduction to PowerShell remoting. It discusses the prerequisites for remoting, including having PowerShell 2.0 and Windows Remote Management installed. It explains how certain cmdlets were updated in PowerShell 2.0 to support the -ComputerName parameter for remote management. The document also demonstrates how to enable PowerShell remoting on a machine using Enable-PSRemoting and describes what tasks this runs to configure the system.
Feb 2010 Intro To Remoteing Part1
- 1. Introduction to PowerShell Remoting, Part 1Matt Johnson, GSEC, [email protected]
- 2. What we are going to cover?An simple intro to remotingRemoting PrerequisitesBasic Remoting using –ComputerNameSetting up Remoting
- 3. A simple intro to remoting
- 4. In Version 1.0In version 1.0, the only command available with –ComputerName was Get-WMIObjectThis made managing a remote PC complicated.
- 5. New in V2!Some cmdlets were updated with the –ComputerName parameter.Get-ProcessGet-ServiceGetWinEventGetEventLogRestart-ComputerStop-ComputerTest-Connection
- 6. New in V2! Cont….Remote console via PS Sessions.Kinda like SSH but much cooler (since it is PowerShell)You can run ANY command on the remote PC.Can run interactively or via jobs
- 8. What you needWindows 7 and Windows Server 2008 R2 has the necessary bitsWindows Vista, XP, Server 2003 and Server 2008 you will need the Windows Management FrameworkWindows PowerShell 2.0, Windows Remote Management (WinRM) 2.0, and Background Intelligent Transfer Service (BITS) 4.0
- 9. What version am I using?To check your PowerShell version, use the variable $PSVersionTable
- 10. Things to remember beforehandYou MUST be in the Administrators group on the remote PC.Both the remote and local computers must be configured to use remoting. You must have PowerShell and the related bits installed on all machines
- 11. Things to remember Cont…On current versions of windows. The network type must be work or home. Public will not work. Any policies, ie group policies, on the remote pc are in effect in remote PowerShell sessions. Keep that in mind if something isn’t working as expected.
- 12. Basic Remoting using –ComputerName
- 16. Enabling PowerShell RemotingRemember to be an Administrator!Open a PowerShell Prompt on the machine and type Enable-PSRemoting.
- 17. What is it doing?Runs the Set-WSManQuickConfigcmdlet, which performs the following tasks: Starts the WinRM service. Sets the startup type on the WinRM service to Automatic. Creates a listener to accept requests on any IP address. Enables a firewall exception for WS-Management communications. Enables all registered Windows PowerShell session configurations to receive instructions from a remote computer. Registers the "Microsoft.PowerShell" session configuration, if it is not already registered. Registers the "Microsoft.PowerShell32" session configuration on 64-bit computers, if it is not already registered. Removes the "Deny Everyone" setting from the security descriptor for all the registered session configurations. Restarts the WinRM service to make the preceding changes effective.
- 18. Running x64?On x64 hardware, a 32-bit listener is installed.
- 20. Remoting is now enabled!What do you do next?Configure PSRemotingRun Scripts / Commands Remotely
- 21. In Two Months!Running Interactively with PS RemotingRunning Jobs with PS RemotingWS-MAN Configuration
- 22. Questions?
- 23. Contact InfoMatt JohnsonPhone: +1 (734) 931-0323Web: http://www.mwjcomputing.com/Blog: http://www.mwjcomputing.com/blog/Twitter: http://twitter.com/mwjcomputingEmail: [email protected]
- 24. Thanks!