Client Installation

The Cisco VPN Unity Client fits perfectly in Cisco's Unified Client Framework. This framework entails a consistent specification that encompasses wireless and desktop clients interaction with VPN Concentrators version 3.0 and up, PIX Firewalls version 6.1 or later, and Cisco routers with IOS version 12.2.8(T) or later. In fact, the Unity Client can be used to initiate VPN sessions to any of these specified devices. This framework also adopts a central management focus by allowing these devices to push configuration parameters to the clients.

To communicate with a VPN Concentrator running software version 3.0 and up, you must be running at least version 3.0 of the Cisco VPN Unity Client. Mind you, as features are added in later revisions of the concentrator's software, Cisco typically mirrors those features in client revisions. If you cannot use certain services or features on the concentrator, ensure that you have a compatible version of the Unity client running.

The Unity Client can be installed on a multitude of operating system platforms. These platforms include the Windows suite of operating systems, including Windows 95 (OSR2), 98, Me, NT 4.0 (SP3), 2000, and XP. In addition, the client can be installed on Linux, Solaris UltraSparc, and Macintosh OSs.

You should know the supported platforms on which the Cisco Unity Client could be installed. In addition, be aware that only the VPN Client for Windows and the VPN Client for Mac OSX (version 3.7 and up) support a graphical user interface (GUI) configuration.

To install the client on the Windows platform, the first step should be to ensure that you meet the minimum requirements as specified in the release notes. Furthermore, it is not a bad idea to uninstall any previous clients (Cisco and other OEM VPN software clients) to ensure you do not have residual icons or files that might cause the program to malfunction. The Cisco uninstallation process typically asks you whether you want to keep any created profiles so you do not have to re-create them. In addition, be sure to disable any virus detection software that is running in the background. After these steps are completed, run the setup executable and install the client in the directory of your choosing. If you are installing an older version of the Unity client on a Windows 2000 or XP station, you may be prompted with a warning that the client's driver is not "signed" by Microsoft; however, it is safe to install the drivers even though they have not been officially certified by Microsoft. After the install is completed, the system requires rebooting to complete the installation.

Client Automatic Silent Installation

It is possible to have the client perform an auto installation without interrupting the user for any input. This type of installation is called silent mode and can be performed if you add a file called oem.ini. A typical oem.ini file might look like Listing 10.1.

Listing 10.1 Sample Output of oem.ini

 [Default] SilentMode = 1 InstallPath = C:\Program Files\Engineering\IPSec Connections DefGroup = IPSec remote users Reboot = 1 

The first line of this file turns the silent mode on so that it will not prompt users when installing the Unity Client. The InstallPath line in the oem.ini file signifies where you want to install that client on the local workstation. After you have chosen the directory, you can also change the folder name in which the client is installed by using the DefGroup variable. The last significant line in this file tells the computer to reboot after the installation.