Sei sulla pagina 1di 2

Microsoft Windows PowerShell 2.

0 Programming Second Edition Updates As is the case with most popular programming language, Microsoft continues to enhance and improve Windows PowerShell 2.0 with the release of Windows PowerShell V2 CTP3. A number of changes have occurred with Windows PowerShell 2.0 since this book was published. This document provides a summary overview of many of these changes. For a complete review of the changes that have been made to Windows PowerShell 2.0, refer to the Release Notes provides that accompany Windows PowerShell 2.0. Supported Operating Systems Windows XP SP3 Windows Server 2003 SP2 Windows Vista SP1 Windows Server 2008

Note: Windows PowerShell will execute on either the x86 or x64 platforms of all of these operating systems Windows PowerShell 2.0 is included as an option features in Windows 7 (beta). Updated System Requirements Windows PowerShell 2.0 requires .Net Framework version 2.0 Windows Remoting requires WinRM 2.0 CTP3 Graphical Windows PowerShell has been renamed Windows PowerShell Integrated Scripting Environment (ISE) .NET Framework 3.5.1 is required to run ISE and to use the Out-GridView cmdlet Get-WinEvent, Get-Counter and Import-Counter only work on Windows Vista and Windows Server 2008. Get-WinEvent requires .NET Framework 3.5.

Renamed cmdlets Get-Event has been renamed Get-WinEvent Push-Runspace has been renamed Enter-PSSession Pop-Runspace has been renamed Exit-PSSession Add-Module has been renamed Import-Module Register-PSEvent has been renamed Register-EngineEvent *-Runspace cmdlets have been renamed *-PSSession *-PSEvent cmdlets have been renamed *-Event *-PSTransaction cmdlets have been renamed *-Transaction *-PSJob cmdlets have been renamed *-Job *-PSEventSubscriber cmdlets have been renamed to *-EventSubscriber

Windows Remoting Configuration The Config-WSMan.ps1 script located in the $pshome directory has been replaced with Enable-PSRemoting cmdlet. To configure Windows Remoting, you must execute the following command: Enable-PSRemoting -force If upgrading from Windows PowerShell version 2 CTP2 you must execute the following commands: Unregister-PSSessionConfiguration * - force; Register-PSSessionConfiguration Microsoft.PowerShell force; Enable-PSRemoting -force

Windows PowerShell Integrated Scripting Environment (ISE) The executed for ISE is now powershell_ise.exe The term runspace has been replaced with PowereShell tab

Additional Notes To install Windows PowerShell version 2.0 CTP3, you must uninstall any previous version of Windows PowerShell. Windows remoting only works on computers running Window Vista SP1 or Windows Server 2008. Windows background jobs rely on Windows Remoting in order to execute. Windows Remoting must be enabled for background jobs to execute.

Potrebbero piacerti anche