What's New in CTP of PowerShell 2.0

Posted by bink on November 7 2007, 1:27 PM. Posted in Powershell.

1.       PowerShell Remoting<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>

Windows PowerShell 2.0 provides support for executing Cmdlets and Scripts remotely. PowerShell Remoting allows managing a collection of remote machines from a single client. Managing remote computers using PowerShell 2.0, requires that PowerShell 2.0 be installed on all the computers taking part in the operation; that is the client computer and the computer(s) being managed.

For more information:<o:p></o:p>

·         get-help About_Remoting

·         get-help Invoke-Expression


Enable Remoting: PowerShell Remoting feature relies on Windows Remote Management (WS-Man) technology. In order for remoting to work, make sure that the WS-Man Winrm service is installed and started. To verify that Winrm service is running, do the following:<o:p></o:p>                                PS> get-service winrm<o:p></o:p>Setup places a PowerShell script (Configure-Wsman.ps1) in $pshome folder that configures WS-Man settings. To configure WS-Man for PowerShell remoting feature, please run the configure-WSMan.ps1 script from PowerShell folder (run elevated for Windows Server 2008 or Windows Vista SP1). This script does not start or stop WinRM service.<o:p></o:p>                & $pshome\Configure-Wsman.ps1 <o:p></o:p>

Known issue: 

·         To use Remoting Cmdlets and features, PowerShell must be started as administrator/elevated. <o:p></o:p>

      ·         PowerShell 2.0 Remoting features will not work correctly on Windows Vista RTM. Please install Windows Vista Service Pack 1 (SP1) Beta to enable PowerShell Remoting features.

2.       Background Jobs

<o:p>Continue At Source</o:p>