vBulletin statistics
Deploying PowerShell 2.0 in your environment - Windows Server blog by Kurt Roggen [BE]
maandag 26 juli 2010 14:39 Kurt Roggen

Deploying PowerShell 2.0 in your environment

PowerShell 2.0 brings some great new management functionality such as:

  • Remoting: lets you run commands on one or more remote computers from a single computer that is running Windows PowerShell. PowerShell remoting allows for multiple ways of connecting, including interactive (1:1), fan-out (1:many) and fan-in (many:1 by using the IIS hosting model).
  • New cmdlets: over 100 built-in cmdlets, enabling you to do computer-related tasks, event log and performance counter management task.

PowerShell version 2.0 is bundled into the Windows Management Framework.

The Windows Management Framework makes some updated management functionality of Windows 7 and Windows Server 2008 R2 available to be installed on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.

Windows Management Framework contains 3 components:

  • Windows Remote Management (WinRM) 2.0
  • Windows PowerShell 2.0
  • Background Intelligent Transfer Service (BITS) 4.0.

Using WSUS (part of Windows Server 2008 R2 as a server role), you can import the PowerShell 2.0 package and approve it for installation on your Windows Server 2008, Windows Server 2003, Windows Vista and Windows XP machines.

Import updates directly into WSUS

Add selected updates to download basket

Once the updates are imported into the WSUS infrastructure, you can approve the update on the required computer groups containing your targeted machines.

Approve the imported updates

NOTE: Be aware that the Windows Management Framework is about 30-35 MB in size.  If bandwidth is an issue or if you are dealing with a serious amount of clients, you may want to throttle the bandwidth used by the Background Intelligent Transfer Service (BITS) which is used as transport mechanism by the Windows Update engine.

More about that another timeā€¦

Related reading:

Filed under: ,

# Enable and configure Windows PowerShell Remoting using Group Policy « blog.powershell.no

Pingback from  Enable and configure Windows PowerShell Remoting using Group Policy « blog.powershell.no