Installing and Running Windows PowerShell

Installation Requirements

Before you install Windows PowerShell, be sure that your system has the software programs that Windows PowerShell requires. Windows PowerShell requires the following programs:

· Windows XP Service Pack 2, Windows 2003 Service Pack 1, or later versions of Windows

· Microsoft .NET Framework 2.0

If any version of Windows PowerShell is already installed on the computer, use Add or Remove Programs in Control Panel to uninstall it before installing a new version.

Installing Windows PowerShell

To install Windows PowerShell:

1. Download the Windows PowerShell installation file. (The name of the file will differ with the platform, operating system, and language pack.)

2. To start the installation, click Open.

3. Follow the instructions on the installation wizard pages.

You can also save the Windows PowerShell files to a network share for installation on multiple computers.

To perform a silent installation, type:

<PowerShell-exe-file-name> /quiet

For example,

PowerShellSetup_x86_fre.exe /quiet

On 32-bit versions of Windows, Windows PowerShell is installed, by default, in the %SystemRoot%\System32\WindowsPowerShell\v1.0  directory. On 64-bit versions of Windows, a 32-bit version of Windows PowerShell is installed in the %SystemRoot%\SystemWow64\WindowsPowerShell\v1.0 directory and a 64-bit version of Windows PowerShell is installed in the %SystemRoot%\System32\WindowsPowerShell\v1.0 directory.

Running Windows PowerShell

To start Windows PowerShell from the Start Menu, click Start, click All Programs, click Windows PowerShell 1.0, and then click the Windows PowerShell icon.

To start Windows PowerShell from the Run box, click Start, click Run, type powershell, and click OK.

To start Windows PowerShell from a Command Prompt (cmd.exe) window, at the command prompt, type powershell. Because Windows PowerShell runs in a console session, you can use this same technique to run it within a remote telnet or SSH session. To return to your Command Prompt session, type exit.

Deployment Options (Velocity)

Security Considerations

The "Velocity" distributed cache system is designed to be operated in the corporate datacenter within the perimeter of the corporate firewall. The servers described in this topic are the server hosting the cache configuration storage location, the cache servers, the cache-enabled application servers, the development servers, and the primary data source server. All servers should be co-located on the same corporate domain.

Because cached data and the TCP/IP communications between the cache servers is not encrypted, the distributed cache system is vulnerable to malicious "sniffing" and "replay" attacks.

Note

The "Velocity" cache client is meant to reside in the application tier of your application ecosystem. End users inside or outside your corporate domain should not have direct network access to the cache servers.

When decommissioning a cache server, the "Velocity" installation program may not remove all firewall port exceptions. After "Velocity" has been uninstalled, we recommend that you reapply the corporate standard firewall configuration.

Deployment Scenarios

To simplify the discussion of deployment options, this topic will focus on three distinct examples:

• Developer deployment: A single-computer deployment used by to develop cache-enabled applications.

• Mid-sized deployment: A multi-computer installation that does not use SQL Server, with lead hosts performing the cluster management role.

• Enterprise deployment: A multi-computer installation that uses SQL Server for storing cluster configuration settings and performing the cluster management role.