Installing only the Network Shell (Windows)

During Application Server installation on the Microsoft Windows platform, you can choose to install the Network Shell (NSH) in addition to the Application Server. To install only the Network Shell, you can use the Network Shell installation program.

If you have an earlier version of Network Shell installed, see Upgrading-the-Network-Shell-on-Windows.

Note

To use the BLCLI or the blcred utility, you must install the TrueSight Server Automation Console. For information, see Installing-the-TrueSight-Server-Automation-Console-and-Network-Shell-Windows.
If you want to run Network Shell to communicate with a Network Shell Proxy Server and use TrueSight Server Automation single sign-on capabilities, then you must install either the TrueSight Server Automation Console or the Application Server. These installations automatically install Network Shell . For information on installing TrueSight Server Automation, see Installing-the-Application-Server-and-Network-Shell-on-Windows or Installing-the-TrueSight-Server-Automation-Console-and-Network-Shell-Windows.

If the host computer on which you are installing the Network Shell has:

A supported version of Perl installed — The Network Shell installation automatically installs the Network Shell Perl module. (For information about the Perl versions that TrueSight Server Automation supports, see Perl support.)
An unsupported version of Perl installed — The installation copies files that allow you to install the Perl module after you have installed the supported version of Perl.

To perform a silent installation of the Network Shell, see Using-silent-mode-to-install-the-Network-Shell-Windows.

Before you begin

To perform the Network Shell installation, you must have local administrator privileges.
If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on a Windows operating system, use one of the following methods to install:
- Install in Install mode rather than Execute mode. For information, see Using-Install-mode-instead-of-Execute-mode.
- Install using the Windows Add or Remove Programs utility.
On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.

To install only the Network Shell

Navigate to the directory containing installation files and run the installation program for Network Shell. The 32-bit installer can be used for both 32-bit and 64-bit Windows environments. (Installation program names follow the convention: NSHversion-platform.)
The Choose Setup Language window opens.
Select a language to use for the installation and click Next.
The installer extracts the installation files, and the Welcome window opens.
Click Next.
The License Agreement window opens.
(optional) To print the license agreement, click Print.
To accept the license agreement, click Yes.
The Customer Information window opens.
Enter your name and the name of your organization, and then click Next.
The Choose Destination Location window opens.
(optional) Click Browse to select a location other than the default, C:\Program Files\BMC Software\BladeLogic\NSH.
Click Next.
The Selected Components window opens.
Review the current settings to confirm that you have specified the correct installation configuration, and then click Next.
A progress bar indicates the progress of the installation until the InstallShield Wizard Complete window states that the installation is complete.
To complete the installation, click Finish.

Where to go from here

For instructions on starting client tier applications, see Starting-and-stopping-TrueSight-Server-Automation-components.

Installing only the Network Shell (Windows)

Before you begin

To install only the Network Shell

Where to go from here

On this page