What you need Windows 7 and Windows Server 2008 R2 has the necessary bits Windows Vista, XP, Server 2003 and Server 2008 you will need the Windows Management Framework Windows PowerShell 2.0, Windows Remote Management (WinRM) 2.0, and Background Intelligent Transfer Service (BITS) 4.0
What version am I using? To check your PowerShell version, use the variable $PSVersionTable
Things to remember beforehand You 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
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.
Enabling PowerShell Remoting Remember to be an Administrator! Open a PowerShell Prompt on the machine and type Enable-PSRemoting.
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.
Running x64? On x64 hardware, a 32-bit listener is installed.