prism installation guide - lenel partner center |...

2.0

Installation Guide

Lenel® Prism® 2.0 Installation Guide. This guide is item number DOC-6001-EN-US, Revision 1.009, December, 2016.© 2016 United Technologies Corporation. All rights reserved.

Lenel®, OnGuard® and Prism® (Registered trademarks of UTC Fire & Security Americas Corporation, Inc.). Lenel is a part of UTC Climate, Controls & Security, a unit of United Technologies Corporation.Interlogix is part of UTC Climate, Controls & Security, a unit of United Technologies Corporation. All rights reserved.The TruVision name and logo are trademarks of United Technologies.All trademarks are the property of their respective owners.Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of UTC Fire & Security Americas Corporation, Inc.Non-English versions of Lenel documents are offered as a service to our global audiences. We have attempted to provide an accurate translation of the text, but the official text is the English text, and any differences in the translation are not binding and have no legal effect.The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that agreement. Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc. OnGuard includes ImageStream® Graphic Filters. © 2002 eBT International, Inc. (f/k/a Inso Corporation). All rights reserved. ImageStream Graphic Filters and ImageStream are registered trademarks of eBT International, Inc. (f/k/a Inso Corporation).Integral and FlashPoint are trademarks of Integral Technologies, Inc. Portions of this product were created using LEADTOOLS ©1991-2011, LEAD Technologies, Inc. ALL RIGHTS RESERVED. Portions of this product are licensed under US patent 5,327,254 and foreign counterparts. Active Directory, Microsoft, SQL Server, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. For technical support, visit http://www.lenel.com.

http://www.lenel.com/


Table of Contents

CHAPTER 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Prism Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Understanding Prism File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

CHAPTER 2 Preparing Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Updating System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Verifying Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Configuring the Computer for the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Configuring the Network Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Checking Computer Accessibility Over the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Setting Windows Power Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Assigning System-Level User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Understanding Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Enabling Microsoft .NET Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Adding a Microsoft SQL Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Configuring the SQL Server for Custom Database Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing Localized Editions of Prism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

CHAPTER 3 Setting Up Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Lenel NVR Device Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Configuring Lenel NVR Failover and Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Using Prism in an Integrated OnGuard Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

UltraView Device Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15TruVision Device Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Prism Installation Guide i

Table of Contents

What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

CHAPTER 4 Installing Prism Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Performing a Basic Prism Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing Prism on a Single Server Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Licensing Prism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installing Prism on Client Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Installing Prism on a Video Matrix Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Customizing a Prism Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Installing Prism on Separate Server Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using Advanced Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Upgrade Prism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

CHAPTER 5 Configuring Prism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Planning a Prism System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Logging into the Prism Common Services Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Adding Additional User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Adding a Prism Operator Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Setting Up a Prism System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Step 1: Set Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Step 2: Add Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Step 3: Add and Configure Recorders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 4: Configure Cameras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 5: Assign Devices to Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 6: Create Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 7: Configure Client Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 8: Configure Permission Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 9: Add Operator Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Step 10: Configure Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Step 11: Configure Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Step 12: Test Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Step 13: Set Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40(Optional) Step 14: Change Passwords for the Administrator Accounts . . . . . . . . . . . . . . . . . . . . . . . . 40

What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

CHAPTER 6 Uninstalling Prism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Uninstalling Prism with the Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Uninstalling Prism Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

CHAPTER 7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Installation Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Resolving Communication Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

ii Prism Installation Guide

Table of Contents

Verifying that the Prism Common Services Database Is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Installation FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Database FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Using the Create Database Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Prism Installation Guide iii

Table of Contents

iv Prism Installation Guide

CHAPTER 1 Introduction

This document describes how to install and configure Prism®, a software-based video surveillance solution that transforms video streams into information that can be quickly viewed, recorded, and searched across an IP network comprised of server and client computers, recorders, and cameras.

The basic steps involved in installing a Prism system include:

1. Prepare computers.2. Install and configure hardware devices according to manufacturer instructions.3. Install Prism software on server computers. 4. License the server computer that contains the Prism Common Services database.5. Install Prism software on client computers.6. Set up Prism by configuring facilities, permissions, operators, alarms, recorders, etc.

Note: Throughout this document, references to the <Prism installation directory> mean C:\Program Files (x86)\Prism.

Prism Installation Guide 1

2

Prism Components OverviewThe primary components of a Prism system include:

• The Prism Client program is the most visible part of Prism, where operators monitor live video, play back recorded video, and perform forensic investigations. Administrators also use this program to manage devices, unlock tracks, and maintain Prism Management Server data.

• The Prism Common Services program is used to manage administrative aspects of Prism (such as permissions and operators), as well as alarms, schedules, maps, audit logs, and diagnostics.

• The Prism Common Services Server is the main server computer that hosts the Prism Common Services database, as well as licensing information. It also contains the Prism Client program and a client version of the Prism Common Services program.

Note: There can be only one Prism Common Services Server in a Prism system.

• Prism Management Server (Peer Server) is a proxy server that manages all devices in the system. It also authenticates client logins, distributes live events, stores system-wide client settings, and gathers health status data from other system components.

• LS Message Broker is an Enterprise Service Bus (ESB) broker that manages system-wide message data.

• Prism CS Host is an event server for Lenel® Network Video Recorders (NVRs).In addition, Prism includes several other software components, including:

• Prism Management Server Database

• Microsoft® SQL Server® Express is installed on the Prism Common Services Server to a supported version of the Prism Common Services database. (A full edition of Microsoft SQL Server can be used if a SQL server instance is added. Refer to the next chapter, Preparing Computers on page 5.)

• Python 2.6.2 is an object-oriented programming language used by the Prism Client program.• Crystal Reports™ modules support Prism’s reporting functionality.• Microsoft .NET Framework supports the exchange of information across web services.

Understanding Prism File Locations

Note: The folders created by the Prism Installation Wizard and the files that are copied to those folders vary according to the type of installation performed. For example, an “All-in-One” installation that includes all Prism components will include all of the folders and files mentioned in this section, but a client installation will not.

During installation, the primary Prism application files are placed in the following folders and are approximately 962 MB in size:

• <Prism installation directory>\Prism• <Prism installation directory>\Prism Common Services• <Prism installation directory>\Prism Server

Note: The default drive for the primary Prism folders is the C: drive, but they may be located on a different drive (for example, D:) if the default destination path is changed during installation.

Prism Installation Guide

What’s Next?

The Prism Installation Wizard creates the following folders in the C:\Program Files (x86)\Common Files folder so that the folder contents can be shared by other programs that follow Windows file storage standards. Files in these folders are approximately 99 MB in size.

• C:\Program Files (x86)\Common Files\Lenel• C:\Program Files (x86)\Common Files\Lenel Shared• C:\Program Files (x86)\Common Files\PrismNote the following details about other folders and files installed by the Prism Installation Wizard, which vary according to the type of installation performed:

• Third-party programs are stored in the C:\Program Files (x86) folder, including Microsoft SQL Server, Microsoft .NET Framework, Bonjour, Open LDAP, and Microsoft Visual C Redistributables.

• Python files are installed in the C:\Python26 folder.• Lenel NVR program files must remain on the C: drive, but Lenel NVR data files can be stored on

any drive.• Additional Prism files and folders are created in the C:\Users folder when the Prism Client

program is used.• If an existing version of a third-party program is installed but Prism requires a later version, the

Installation Wizard will update the program. For example, if Microsoft .NET Framework 3.5.1 is installed, the Installation Wizard will install Microsoft .NET Framework 4.5.2 or later.

• The Prism and Lenel OnGuard® common message broker configuration files are installed in the C:\ProgramData\Lnl folder.

• The AVS Controller Service is installed in the C:\ProgramData\Lenel folder.

What’s Next?Before installing Prism software, prepare server and client computers by downloading the latest software updates, configuring network settings, etc. Proceed to Preparing Computers on page 5.


4

CHAPTER 2 Preparing Computers

This chapter describes how to configure server and client computers for Prism and should be read carefully before installing Prism. Perform the steps in the order given.

To prepare a computer for use with Prism:

1. Ensure that the computer meets the hardware and software requirements listed in the Prism Release Notes included on the Prism Installation disc.

IMPORTANT: Do not install Prism server components on a computer that is also used as a Microsoft Domain Controller. Otherwise, security permissions will not function properly and server connectivity will be broken.

2. Download the latest operating system service pack, Windows updates, and video drivers. See Updating System Software on page 6.

3. Check that display settings are set to at least 1024 by 768 pixels. See Verifying Display Settings on page 6.

4. Configure network settings. Refer to Configuring the Computer for the Network on page 6.5. Adjust power options to avoid sleep modes. See Setting Windows Power Options on page 7.6. Configure system-level user passwords to avoid permission issues with remote client computers.

For more information, refer to Assigning System-Level User Passwords on page 7.

7. If planning to install Prism on a Microsoft Windows Server® 2008 Release 2 SP1 (64-bit) operating system or Server 2012 Release 2 see Enabling Microsoft .NET Framework on page 8.

8. If planning to use a full edition of Microsoft SQL Server with Prism instead of Microsoft SQL Server Express, see Adding a Microsoft SQL Server Instance on page 9.

9. If using a localized edition of Prism, refer to Installing Localized Editions of Prism on page 10.


6

Updating System SoftwareTo update system software on each computer:

• Download the latest operating system service pack from the Microsoft Download Center. • Check for Windows updates at update.microsoft.com. Afterward, disable the Install updates

automatically option for Windows.• Ensure that the KB2919442, KB2919355, and KB2999226 Windows updates are installed by

selecting View installed updates in the Uninstall or change a program window. If these updates are not installed, go to support.microsoft.com, search for each Knowledge Base article, and install the updates.

IMPORTANT: KB2919442 MUST be installed before installing 2919355.

• Download the latest video drivers. The Prism Client program requires video drivers that support the Open Graphics Library (OpenGL) standard for high-resolution graphics on all client computers.

Verifying Display SettingsVerify that the screen resolution on each computer where live and recorded video will be viewed meets the recommended screen resolution: 1024 by 768 pixels.

To access display settings on a computer:

1. Right-click the mouse on the Windows desktop.2. Select Screen resolution from the menu that appears.3. Change the Resolution setting to at least 1024 by 768 pixels.4. Click Apply.5. Click OK.

Configuring the Computer for the NetworkPrism uses a TCP/IP network protocol to allow server and client computers to communicate. When configuring network properties for computers, note these details:

• All computers should exist on the same domain.• Do not use “dots” in the computer name (e.g., MyServer.corporate). Use hyphens or underscore

characters instead.• All computers should be added to the network before installing the Prism software. • All computers should use the same network properties.• Due to Microsoft security rules for running Secure Socket Layer (SSL) from a privileged service,

the SSL host name must be the complete fully qualified domain name (FQDN) of the server computer that will host the Prism Common Services database. If that computer is not on a domain, has a domain name system (DNS) suffix, and the local DNS server is configured to NOT resolve names for computers that are not part of the domain, then SSL will not work unless: – The computer is joined to a domain,


http://www.microsoft.com/downloads/en/default.aspx

http://update.microsoft.com

Setting Windows Power Options

– DNS is reconfigured to resolve names for computers that are not part of the domain, or – The hosts file of the computer is edited to add a line to resolve the FQDN to its IP address.

Configuring the Network CardVerify that the network card uses the same speed as the existing network. (See www.microsoft.com/technet for details.) If a computer has multiple network interface cards, choose the same network profile for each card. When attaching a card to a new network and specifying if the network is Home, Work, or Public, choose the same option for both cards so that the correct ports are opened during installation.

Checking Computer Accessibility Over the NetworkEach Prism installation includes a primary server computer — known as the Prism Common Services Server — that contains the Prism Common Services database and licensing information. All other server and client computers must be able to reach this computer over the network. To test communications with the Prism Common Services Server, use the ping utility.

Setting Windows Power OptionsIf server computers are running, Prism can continue to operate regardless of whether anyone is logged in to Windows or Prism (unless Auto Shutdown is enabled in Prism Common Services). For each server computer, use Control Panel to set power options so that the display screen and hard disks never turn off, and the computer never goes into sleep mode. See www.technet.microsoft.com for details.

Assigning System-Level User Passwords Use the User Accounts option in Control Panel to add users to a computer and then add users to a group. For details, refer to the documentation that came with the Windows operating system.

Note the following recommendations about Windows user accounts:

• Assign a password to all user accounts to avoid permission issues when attempting to access remote client computers. Refer to www.technet.microsoft.com for details.

• To avoid interruptions during installation, consider configuring passwords so they never expire. • To install Prism on a non-English operating system that does not have a local “Administrators”

group created in English by Windows, create an Administrators group with full permissions. See Installing Localized Editions of Prism on page 10.

To install Prism, an administrator must log on to the computer with a Windows user account (local or domain) that is a member of the Administrators group with full access rights, including permission to apply required registry changes (i.e., full permission control).

During installation, the following items are created:

• A Windows user group named SPAdmin. (If user accounts are added after installing Prism software, assign them to this group.)

• A local user account called secure is created in the Users and SPAdmin groups. The default, case-sensitive password for this user account is SecurityMaster08. After Prism is installed,


http://www.microsoft.com/technet

http://technet.microsoft.com




8

the default password for this account should be changed to enhance security, as described later in Setting Up a Prism System on page 37.

Understanding PrerequisitesIf the following components are not already installed, the Prism Installation Wizard will install them:

• Microsoft .NET Framework 4.5.1 Full or later supports the exchange of information across web services.

• Microsoft Visual C++® 2010 SP1 Redistributable package (x86) supports Prism processes.• Microsoft Visual C++ 2015 Redistributable package supports Prism processes.• Lenel NVR Client Software Development Kit (SDK) supports Prism video functionality.• Joystick Controller SDK Installation supports Prism joystick functionality.

Enabling Microsoft .NET Framework

Note: This section only applies to server computers running a Microsoft Windows Server® 2008 Release 2 (64-bit) operating system.

Note: When installing .Net Framework 3.5 on Windows 8 and Windows Server 2012, you need to specify an alternate source path to the \Sources\SxS\ directory on the installation media. For more information, refer to http://msdn.microsoft.com/en-us/library/hh506443.aspx

To enable Microsoft .NET Framework on a Windows Server 2008 R2 SP1 or Server 2012 R2 computer:

1. Click Start > Administrative Tools. 2. Click Server Manager. 3. In the Server Manager interface, click Features and verify that .NET Framework 3.5.1 is listed.4. If .NET Framework 3.5.1 is not listed, follow these steps to install and enable the feature.

Note: Microsoft .NET Framework 3.5.1 features cannot be installed unless the required role services and features are also installed.

a. In the Server Manager interface, select Add Features to display a list of possible features.b. In the Select Features interface, expand .NET Framework 3.5.1 Features.

Two check boxes will appear: one for .NET Framework 3.5.1 and other for WCF Activation. c. Select the .NET Framework 3.5.1 check box and click Next.

Note: If you do not expand .NET Framework 3.5.1 Features and select the .NET Framework 3.5.1 check box, the Add Features Wizard will appear. Click Cancel, expand .NET Framework 3.5.1 Features, select the .NET Framework 3.5.1 check box, and click Next.

5. In the Confirm Installation Selections interface, review the selections and then click Install.6. Allow the installation process to complete and then click Close.When Prism software is installed, the Installation Wizard will automatically update .NET Framework to version 4.5.1 or later, as necessary.


http://msdn.microsoft.com/en-us/library/hh506443.aspx

http://msdn.microsoft.com/en-us/library/hh506443.aspx

Adding a Microsoft SQL Server Instance

Adding a Microsoft SQL Server Instance

Note: This section only applies to the server computer that will be used as the main Prism Common Services Server and will host the Prism Common Services database.

Microsoft SQL Server 2008 and Microsoft SQL Server 2012 are supported. If using SQL Server 2008 Express, it will be installed automatically with Prism. If using the full version of SQL Server 2008 or 2012 it will need to be installed using Microsoft’s installation instructions. SQL Server 2008 Express can be upgrade to SQL Server 2012 Express after the Prism installation is completed.

If planning to use a full edition of Microsoft SQL Server instead of the default Microsoft SQL Server Express program that is included with Prism, make sure to:

• Install SQL Server, if it is not already installed on the computer. The SQL Server 2012 installation may be performed manually, or it may be automated using .bat scripts. To manually install a new instance of SQL Server 2012 Express (32 Bit), run SQLEXPR_x86_ENU.exe located in the Redistributables folder. To manually install a new instance of SQL Server 2012 (64 Bit), run SQLEXPR_x64_ENU.exe.

• To automate the SQL Server installation, use the corresponding .bat files located on the product disc or disc image in the Redistributable folder.

• Update any SQL Server Service packs or feature packs supported by Prism from the Microsoft Download Center.

• Use the SQL Server Installation Wizard included with SQL Server 2008 to create a server instance named “VMSSQL” and enable protocols for the instance, as described next.

To create and configure the VMSSQL server instance for Prism:

1. Use the Instance Configuration page of the SQL Server Installation Wizard to create a server instance called “VMSSQL”.

2. Configure the Server Configuration properties for VMSSQL as follows:a. Click the Use the same account for all SQL Server services button.

• In the Account Name field: Enter Administrator or the domain account name. • In the Password field: Enter the password for the account.

b. For the Startup Type, select Automatic for SQL Server Agent, SQL Server Database Engine, and SQL Server Browser.

3. Configure the Database Engine Configuration properties for VMSSQL as follows:a. For Authentication Mode, click Mixed Mode (SQL Server authentication and Windows

authentication). b. In the Built-in SQL Server system administrator account section, enter the default ‘sa’

password and the case-sensitive, default password: SecurityMaster08. c. In the Specify SQL Server administrators section, click Add. d. In the Enter the object names to select field on the Select Users or Groups window, select

the Administrator object and then click Check Names to verify the name. Click OK to close the window.

e. Click Next.4. When the Error and Usage Reporting window appears, click Next. 5. When the Installation Rules window appears, click Next. 6. When the Ready to Install window appears, click Install. 7. When the setup process is complete, click Next. 8. When the Complete window appears, click Close.


http://www.microsoft.com/downloads/en/default.aspx

10

9. Restart the computer. 10. Start Client Protocols.

• For Microsoft SQL Server 2008: Navigate to Configuration Tools > SQL Server Configuration Manager > SQL Native Client 10.0 Configuration (32bit) > Client Protocols.

• For Microsoft SQL Server 2012: Navigate to Configuration Tools > SQL Server Configuration Manager > SQL Native Client 10.0 Configuration (32bit) > Client Protocols.

11. Right-click on each of the following options and click Enable:• Shared Memory• Named Pipes• TCP/IP

12. Repeat step 11 to enable the same options for SQL Server Network Configuration > Protocols for VMSSQL.

13. Repeat step 11 to enable the same options for SQL Native Client 10.0 Configuration > Client Protocols.

To verify that the VMSSQL server instance is configured properly, start Microsoft SQL Server and confirm that client computers can connect to the SQL database.

Configuring the SQL Server for Custom Database InstancesAn SQL server custom database instance can be configured in one of two ways:

• For a named instance: During Prism 2.0 installation, click Custom System in the System Type Information window, and then type a new SQL instance name in the Enter SQL Instance field in the SQL Account Configuration window.

• For a default instance: During Prism 2.0 installation, click Custom System in the System Type Information window, and then select the Use Default SQL Instance Name check box in the SQL Account Configuration window.

To have the Prism configuration communicate with a specific database instance after creating the original SQL database during installation:

• Launch the Configure Prism program, type a new instance name in the Instance Name field, and apply the configuration.

• To configure the default SQL instance, launch the Configure Prism program, select the Default check box, and apply the configuration.

Installing Localized Editions of PrismPrism supports localization of the user interface. To use a language other than English, you must install the Prism language pack on top of the core Prism product to run a localized version of the Prism software. The language pack is available to authorized Lenel VARs (Value Added Resellers) and customers at http://www.lenel.com.

If installing a localized edition of Prism, note the following details:

• Install the localized Windows operating system for the specific language first. For the version of Windows or Windows Server that is currently supported, refer to the Prism Release Notes.



What’s Next?

• To install Prism on a non-English operating system, install Microsoft .NET Framework 4.0 (or later) in the appropriate language before installing the Prism software and the language pack.

• To install Prism on a non-English operating system that does not have a local “Administrators” group created in English by Windows, create an Administrators group with full permissions first.

IMPORTANT: Use English-language ASCII characters when assigning an FQDN to the server computer that will host the Prism Common Services database, as well as any computer that will host a LS Message Broker.

Refer to the Prism Language Pack User Guide, available at: http://www.lenel.com, for more details.

What’s Next?Before installing Prism software, install and configure hardware devices according to manufacturer instructions. Proceed to Setting Up Devices on page 13.



12

CHAPTER 3 Setting Up Devices

Prism is compatible with Lenel NVR, Lenel OnGuard®, as well as several UltraView™ recorders and encoders. Refer to the Prism Release Notes and visit http://partner.lenel.com for the latest version numbers of compatible software, as well as updated lists of supported devices and device drivers.

Before installing Prism software on server and client computers, install recorders, encoders, and cameras according to manufacturer instructions. Configure compatible UltraView devices in the Video Configuration Manager (VCM) web interface. Lenel NVR devices can be configured in the Prism Client program after Prism software is installed.

When installing and configuring devices, use the notes provided in the following sections, as well as the release notes included on the Prism installation disc, for reference.

Lenel NVR Device NotesWhen setting up Lenel NVR devices, note the following details:

• The Lenel NVR System User Guide is located at http://partner.lenel.com– Select the Downloads icon.– Choose the Product Lenel NVR– Select the Version Lenel NVR7.2– Select User Guides.– Select Lenel NVR System User Guide.

• For optimal performance, do not install Prism server components on computers that are also used as Lenel NVR video servers.

• Do not assign the same camera to multiple Lenel NVRs.• Enable PTZ camera settings according to the Lenel NVR documentation.

• For Axis® cameras connected to Lenel NVRs:– Configure the names of preset positions via the web page of each camera. Use primary

numbers (1, 2, 3, etc.) for each preset position.– Disable the International Security Management Association (ISMA) compliance setting.


http://partner.lenel.com/


14

• If planning to use motion alarms in a Prism-only environment, be sure to configure motion detection settings for Lenel NVR cameras in the Dashboard window before using the Configure Motion ROI window.

Configuring Lenel NVR Failover and RedundancySecondary recorders record and process video when the primary recorder is offline or at the same time if the redundancy feature is configured.

In standard failover scenario, when the primary recorder goes offline, an alarm is generated and the secondary recorder begins recording video. Users can view live and recorded video from the time the alarm was generated on the secondary recorder. The secondary recorder uses the same workstation, algorithms and channel parameters as the primary recorder. When the primary recorder comes back on line, a restored alarm is generated, the primary recorder connects to the IP camera and resumes recording. When both the recorders are on line, users can view uninterrupted recorded video.

The redundancy feature is a full-time failover solution. In a failover configuration, video channels are recorded to the primary recorder unless it goes offline, at which time recording occurs on the secondary recorder. In a redundant configuration, video channels are recorded to both the primary and secondary recorders regardless of the status of the primary recorder.

After Prism software is installed and recorders are added to the system via the Prism Client program’s Dashboard window, failover recorders can be configured in the Dashboard window and then alarms for failover channels can be configured in the Prism Common Services program.

Note the following details when configuring Lenel NVR failover:

• UDP port 5000 must be used.• Be sure to enable monitoring for all failover channels in the Prism Common Services program so

that alarm events are generated.• If a redundant failover system is used, then only alarms for the primary recorder appear when

both recorders are on line.• When failover occurs, expect a brief delay while messages are propagated through the system,

devices go on line or offline, and configurations are synchronized between Lenel NVRs.

Using Prism in an Integrated OnGuard EnvironmentIf Prism will operate in an integrated environment with an existing OnGuard installation, the Prism Migration Tool must be used to configure Lenel NVR data so that it can be shared by both systems. The Prism Migration Tool instructs Prism not to make configuration changes to Lenel NVRs, which will be managed by OnGuard. The tool is available on http://www.lenel.com/support.

Note: An OnGuard integrated mode license is required to activate an integrated OnGuard environment.

After running the Prism Migration Tool, follow these steps to complete the integrated OnGuard environment setup:

1. Using a Prism system with Administrator permission, launch the Configure Prism utility from the Prism installation directory. The default location of the Configure Prism utility is C:\Program Files (x86)\Prism\Prism\ConfigurePrism.exe.

2. Select the Enable radio button in the OnGuard Integration field.3. Click Apply Changes. 4. Wait several minutes until all services restart and are in a running state.5. Launch the Prism Client, enter credentials, and click Login.



UltraView Device Notes

6. Click the Dashboard button ( ) on the Prism Client toolbar. 7. In the Prism Servers pane, the Integrations status for OnGuard appears as “Yes.” Lenel NVR

device options are now read-only on Prism device pages.Note the following details about using Prism in an integrated OnGuard environment:

• Lenel NVR Video Suite 7.1.1027 or later includes a Lenel NVR Recovery tool that can be used to restore system information that may have been lost as a result of upgrading from Lenel NVR 7.0 or earlier, or from removing or reassigning storage media containing Lenel NVR files. Without this system information, the video will not be viewable on a Prism client until the recovery tool is run, but the video will still be viewable on an OnGuard client.

• Configure devices in OnGuard, not the Prism Client program. (Lenel NVR device options are read-only on Prism Device pages in an integrated environment.)

• Adjust device power options to avoid sleep modes. • Configure each device to use the same timezone as its parent Lenel NVR.• Although devices with duplicate names can be added in the Dashboard window of the Prism

Client program, OnGuard does not support identical device names. • Prism schedules (known as “timezones” in OnGuard) are not migrated to OnGuard. In an

integrated environment, Lenel NVRs receive schedule data from OnGuard. All OnGuard timezone entries will be migrated as Always.

• If camera motion detection settings are configured to send alarms on the Event Mode sub-tab of the Camera form in OnGuard, OnGuard will only send that information to Prism if the Timezone is set to Always.

• OnGuard does not support identical device names on a single Lenel NVR.• If a Lenel NVR is deleted from either Prism or OnGuard after running the Prism Migration tool,

the recorder will not be automatically deleted from the other system. Lenel NVRs must be deleted in both Prism and OnGuard, separately.

• If a camera is deleted from a Lenel NVR in OnGuard, the camera will remain visible in the Prism Client program until the user logs out and then logs in again.

• Video from the following cameras cannot be displayed in Prism: Bosch Dinion IP NWC-0495, Bosch VideoJet 8008, Bosch VideoJet V8-X4, and Bosch VideoJet V8-X8.

IMPORTANT: Be sure to back up the OG.db file stored in the C:\Program Files (x86)\Prism\Prism Common Services folder whenever backing up data. This file tracks whether or not the Prism Migration Tool was used and instructs Prism not to make configuration changes to Lenel NVRs, which are managed by OnGuard in an integrated environment.

UltraView Device NotesConfigure UltraView devices in the Video Configuration Manager (VCM) web interface before adding them to Prism. Refer to the Video Operating System (VOS) documentation and VCM Help files for details. For installation instructions, see the UltraView Video Operating System Installation Guide and the UltraView Video Configuration Manager Installation Guide available at http://partner.lenel.com.

Review recommendations for naming devices are provided in Planning a Prism System on page 33.

Note the following details about configuring UltraView devices for Prism:




16

• Update the VOS firmware for each device to version 5.0.0.• Remember to use the Apply button to save changes.• Do not use lowercase letters or hyphens (-) in device names.• Install VCM on the same server where the Prism Management Server will reside.• Do not assign the same camera to multiple recorders.• For PTZ cameras, enable PTZ settings according to the UltraView documentation. • For Axis cameras connected to UltraView devices:

– Configure the names of preset positions via the web page of each camera. Use the text string “Pos” before each primary number (Pos1, Pos2, Pos3, etc.).

– Do not configure Axis cameras to automatically adjust for Daylight Saving Time (DST) changes.

• See “Configure Plugin” in VCM Help for plugin configuration instructions.• Define an Event Manager, using the default settings.• Use the following format to define events:

VIDEO_EQUIPMENT_<Device name>_AD_<Channel number>_AD_ALARM_ON Example: VIDEO_EQUIPMENT_UVN80Z9_AD_1_AD_ALARM_ONNote the following details about events:– If Prism alarms and schedules will be used, the event names defined in the VCM web

interface must match the Prism Common Services alarm names. Also, a video event trigger must be defined for each alarm event in the Prism Common Services program. See Step 11: Configure Alarms and Events on page 39.

– To configure two storages simultaneously for a camera, use a different frames per second (FPS) setting for each storage. Configure one storage for continuous recording and the other for event-based recording.

TruVision Device NotesWhen setting up TruVision devices, note the following details:

• The Prism Driver Pack User Guide is located at http://partner.lenel.com– Select the Downloads icon.– Choose the Product Prism– Select the latest version of the Driver Pack– Select User Guides.– Select Prism Driver Pack User Guide.

• The Prism Video Matrix and Configure Client Settings window provide options for TCP or UDP for Live video transport. For TruVision recorders, the operator should select Use TCP or Enabled TCP.

• Lock/Unlock functionality is supported in Prism for TruVision devices. The Lock operation can be performed in the Archive Group Pages of the Prism Client.

• To ensure configured alarms are propagated to the Prism Client, two actions must be performed: – The alarm must be configured in Prism CS. – The operator must manually enable the appropriate alarms / notifications from the TruVision

recorder browser window.



What’s Next?

• The option for identifying whether the attached camera is PTZ enabled/disabled is not consistent with TruVision recorders. Consequently, the PTZ tab in the Prism client is provided by default for all the cameras connected to a TruVision recorder.

What’s Next?When Prism hardware is ready, proceed to Installing Prism Software on page 19.


18

CHAPTER 4 Installing Prism Software

This chapter describes how to perform a typical Prism installation that includes one main server computer, plus one or more client computers.

In a typical setup, a single server computer known as the Prism Common Services Server hosts all of Prism’s server functionality. This type of server computer is also known as an “All-in-One” or “Complete” system and includes the following components:

• Prism Common Services database• Prism Management Server• LS Message Broker• Prism CS Host event server• Prism Client program (includes the Prism video UI, the Prism Common Services and UI, and the

joystick controller service)• SQL 2008 SP1 VMSSQL instance.This chapter also describes the different ways to customize an installation. For example, one server computer can be used to host the Prism Common Services database, which connects to one or more Prism Management Servers dedicated to video.

IMPORTANT: Do not install Prism server components on a computer that is also used as a Microsoft Domain Controller. Otherwise, security permissions will not function properly and server connectivity will be broken.

IMPORTANT: Installing Prism via a remote desktop session may produce inconsistent results.

Topics in this chapter include:

• Performing a Basic Prism Installation on page 20• Customizing a Prism Installation on page 25• What’s Next? on page 32


20

Performing a Basic Prism InstallationThis section describes how to install Prism on a single server computer with one or more client computers, which involves the following steps:

1. Install all Prism server components on a single server computer.2. License Prism on the server computer. 3. Install Prism client components on the client computers.

IMPORTANT: Before proceeding, ensure that computers are configured properly, as described in Preparing Computers on page 5. If problems occur during installation, see Installation Troubleshooting Tips on page 45.

Prism can also be installed across multiple server computers, as described in Installing Prism on Separate Server Computers on page 25.

Installing Prism on a Single Server ComputerThis section describes how to install all Prism server functionality on a single server computer (i.e., an “All-in-One” or “Complete” Prism system) using the default settings of the Installation Wizard. (To customize an installation by changing the default SQL administrator account password or broker configuration, refer to Customizing an All-in-One Server Computer Installation on page 28.)


To install Prism on a single server computer:

1. Log on to the computer with a Windows user account (local or domain) that is a member of the Administrators group with full access rights, including permission to apply registry changes.

2. Insert the Prism installation disc into the disc drive. If the Installation Wizard does not start automatically, use Windows Explorer to navigate to the \Setup folder on the installation disc, right-click setup.exe, and then click Run as administrator from the shortcut menu.

3. If the Installation Wizard detects that any prerequisites are not installed (see Understanding Prerequisites on page 8), a window will appear to prompt you to install them.

4. When the Installation Wizard appears, review the Software License Agreement and then click Accept & Continue.

5. On the System Type Information window, click Typical System. 6. On the System Type Selection window, click Complete Prism System.

The Destination Folder window displays the default folder for Prism application files.7. (Optional) Click Change to select a different folder.

Note: Although changing the destination folder will impact the location of the primary Prism application files, additional programs and folders will be installed elsewhere on the computer. Refer to Understanding Prism File Locations on page 2 for details.

8. Click Next.9. When the Ready to Install the Program window appears, click Install.10. When a window appears to indicate that Prism was installed successfully, click Finish.

The License Setup window appears.


Performing a Basic Prism Installation

11. (Recommended) Before licensing the server computer that hosts the Prism Common Services database, confirm that the Installation Wizard created the Prism Common Services database. See Verifying that the Prism Common Services Database Is Installed on page 47.

12. Click OK to license the server computer that hosts the Prism Common Services database.The server computer that hosts the Prism Common Services database should be licensed immediately, as described next. Otherwise, skip to Installing Prism on Client Computers on page 22, but note that Prism will operate in demonstration mode with limited functionality until it is licensed.

Licensing PrismThis section describes how to license Prism on the server computer that contains the Prism Common Services database. The license key controls the following details:

• The number of Prism Management Server instances allowed. • The number of video channels allowed.• The expiration date of Prism use.• Integration with OnGuard.• The ability to configure and manage video matrix. Note the following details about Prism licensing:

• Computers used solely to host a Prism Management Server or LS Message Broker do not need to be licensed.

• Client computers do not need to be licensed.• Without a license key, Prism will operate in demonstration mode which allows one recorder and

four video channels. • If the motherboard or network interface card on the server computer that hosts the Prism

Common Services database is replaced, contact Customer Support to obtain a new license key.

Requesting a License KeyBefore licensing Prism, contact Customer Support to request a registered license key. Have the following information ready:

• The bar code from the Prism package,• The specific version number of Prism that is being used.• The Machine Seed Key from the License Setup window,• Company name and address, and• The sales or purchase order number, if upgrading an existing license.Contact Customer Support using the information below:

• Telephone: 585-248-9720, extension 3 • E-mail: [email protected]

IMPORTANT: Store a written copy of the license key in a secure location so that if the license key on the computer is ever destroyed or corrupted, it can be re-installed without having to contact Lenel.

After obtaining a license key, license the server computer that contains the Prism Common Services database, as described next.


22

Licensing the Prism Common Services Server To license the Prism Common Services Server:

1. If the License Setup window is not already open, start the Prism License program. For more information, refer to the OnGuard Installation Guide, Using OnGuard on Supported Operating Systems section.

2. When the Welcome window appears, click OK.3. Type the SQL Password for PrismCS.

Note: The default, case-sensitive password is “SecurityMaster08”. If the password was changed during a custom installation, you may be prompted to type the SQL Password for PrismCS again.

4. (Optional) Select the Warranty Reminder check box and enter the number of days (0—120) before the warranty expires when a reminder should appear.

Note: The Machine Seed Key is a read-only field that changes every time the licensing sequence runs.

5. In the License Key fields, enter the 35-character license key string. (See Requesting a License Key on page 21.)

6. Click Register. A message indicates that licensing was successful and Prism services will stop.

7. Click OK. The license program registers the license key and closes. If the system does not reboot automatically, wait for two minutes and then reboot the system.

After licensing the server computer that hosts the Prism Common Services database, install Prism software on client computers, as described next.

Installing Prism on Client ComputersThis section describes how to install Prism on client computers, which include these components:

• The Prism Client program used to display video.• The client version of the Prism Common Services program.• The LS Message Broker, along with LS Message Broker certficates and the Prism Watchdog

Service.Note the following details about installing Prism on client computers:

• By default, the primary LS Message Broker is installed on the server computer that contains the Prism Common Services database, but a backup broker can be installed on a server or client computer by installing the client version of Prism.

• To install Prism on a computer that will be used as a Video Matrix client, follow the steps in Installing Prism on a Video Matrix Client on page 23 instead.

To install Prism on a client computer:

1. Log on to the computer as a user with local administrator rights. 2. Insert the Prism installation disc into the disc drive.

If the Installation Wizard does not start automatically, use Windows Explorer or File Explorer (depending on the operating system) to navigate to the \Setup folder on the installation disc, right-click setup.exe, and then click Run as administrator from the shortcut menu.


Performing a Basic Prism Installation

3. If the Installation Wizard detects that any prerequisites are not installed (see Understanding Prerequisites on page 8), a window will appear that can be used to install them.


5. On the System Type Information window, click Typical System. 6. On the System Type Selection window, click Prism Client. 7. When the Prism Common Services Server Location window appears:

a. Type the hostname of the Prism Common Services Server (i.e., the computer that hosts the Prism Common Services database).

b. Click Test Connection to ensure that the client can connect to the Prism Common Services Server.

c. If no connection is made, try typing the FQDN for the Prism Common Services Server.d. Click Next.

8. When the Prism Broker Configuration window appears:a. Type the FQDN for the computer that hosts the primary LS Message Broker in the Broker

Server field. (By default, this broker is installed on the server computer that contains the Prism Common Services database, but may be installed on another computer in a custom installation.) Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary.

b. If a backup broker is installed, type the FQDN for the computer that hosts the backup broker in the Backup Broker Server Name field. Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary.

c. Click Next.The Destination Folder window displays the default folder for Prism application files.

9. (Optional) Click Change to select a different folder.



Installing Prism on a Video Matrix ClientThis section describes how to install Prism on a client computer that hosts one or more video matrix (for example, two large monitors with eight tiles each). This type of client computer is known as a Video Matrix client.

Unlike a typical Prism Client that includes the Prism Client program used to display video, as well as the client version of the Prism Common Services program, a Video Matrix client only includes:

• The Prism Client program, and• The Prism Video Matrix service that detects the type of video matrix connected to the Video

Matrix client and reports this information back to the Prism Management Server. For example, a single Video Matrix client can host two video matrix — one matrix with 8 separate video screens and another matrix with only four video screens.


24

After installation, operators with the appropriate permissions can use the Configure Video Matrix window in the Prism Client program to control the layout and content of video matrix, which can include live or recorded video streams, sequences, views, salvos, and web pages.

To install Prism on a computer that will be used as a Video Matrix client:





5. On the System Type Information window, click Custom System. 6. In the selection option, check the option for Prism Video Matrix Client. 7. When the Prism Common Services Server Location window appears:


b. Click Test Connection to ensure that the client can connect to the Prism Common Services Server.


8. When the Prism Broker Configuration window appears:a. Type the FQDN for the computer that hosts the primary LS Message Broker in the Broker

Server field. (By default, this broker is installed on the server computer that contains the Prism Common Services database, but may be installed on another computer in a custom installation.) Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary.

b. If a backup broker is installed, type the FQDN for the computer that hosts the backup broker in the Backup Broker Server Name field. Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary.

c. Click Next.The Destination Folder window displays the default folder for Prism application files.





Customizing a Prism Installation

Customizing a Prism InstallationThis section describes how to customize a Prism configuration by installing Prism on separate server computers, as well as how to use advanced installation options such as changing the default SQL administrator account password, the LS Message Broker configuration, or the location where Prism files are stored. A backup broker can also be installed.


Installing Prism on Separate Server ComputersThis section describes how to install Prism Common Services components (including the Prism Common Services database) on one server computer, and then install Prism Management Server components on one or more server computers.


Installing Prism on a Dedicated Prism Common Services ServerThis section describes how to install Prism on a server computer that will host the Prism Common Services database but will not include Prism Management Server.

This custom installation includes these components:

• The Prism Common Services database.• The Prism Client program used to display video.• The client version of the Prism Common Services program.• The LS Message Broker, along with LS Message Broker certficates and the Prism Watchdog

Service• The Prism CS Host event server for Lenel NVRs.To install Prism on the server computer that will host the Prism Common Services database:

1. Log on to the computer as a user with local administrator rights.2. Insert the Prism installation disc into the disc drive.




5. On the System Type Information window, click Custom System. 6. On the Custom Setup window, click the icon next to Prism Common Services Server. 7. Select the This feature will be installed on the local hard drive option from the drop-down list

that appears.8. Make sure that the This feature is not available option is checked for the Prism Management

Server option. (A red “X” should appear next to that option.) The Prism Client option will be automatically selected because those files are also installed.

9. Click Next.


26

10. When the Prism Management Server Options window appears:a. (Optional) Change the default port numbers for the Prism Management Server. Click Check

Port to determine if the port is available for use.b. (Optional) To receive status messages from the Prism Management Server, select the

Configure e-mail address check box and type values in the E-mail address to receive messages, SMTP Server, and Sent from e-mail address fields.

c. Click Next. 11. When the Prism Broker Configuration window appears:

a. Type the FQDN for the computer that hosts the primary LS Message Broker in the Broker Server field. (By default, the broker is installed on the Prism Common Services Server, but may be installed on another computer in a custom installation.) Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary. Click Check Port to determine if the port is available for use.

b. (Optional) If a backup broker is installed, type the FQDN for the computer that hosts the backup broker in the Backup Broker Server Name field and adjust the default port setting, if necessary. Click Check Port to determine if the port is available for use. Click Test Connection to ensure that the client can connect to the computer.

c. Click Next.12. When the SQL Account Configuration window appears, the password fields contain the default

password for the SQL system administrator (sa) account: “SecurityMaster08”.a. (Optional) To change the default password, type the new password in the fields provided.b. Click Next.

13. When the Change the “Secure” password window appears:a. (Optional) Click Change Password and type the new password in the fields provided.b. Click Next.The Destination Folder window displays the default folder for Prism application files.




The License Setup window appears. 18. (Recommended) Before licensing the server computer that hosts the Prism Common Services

database, confirm that the Installation Wizard created the Prism Common Services database. See Verifying that the Prism Common Services Database Is Installed on page 47.

The server computer that hosts the Prism Common Services database should be licensed immediately, as described in Licensing Prism on page 21. Otherwise, Prism will operate in demonstration mode with limited functionality. When finished, return to this section to install Prism on the server computer that will be used as a Prism Management Server, as described next.

Installing a Prism Management ServerEach Prism system can have only one Prism Common Services Server that hosts the Prism Common Services database, but can have multiple Prism Management Server instances dedicated to video,



depending on the license. Repeat the following steps for each computer that will be used as a Prism Management Server.

To install Prism on a server computer that will be used as a Prism Management Server:





5. On the System Type Information window, click Custom System. 6. On the Custom Setup window, click the icon next to Prism Management Server. 7. Select the This feature will be installed on the local hard drive option from the drop-down list

that appears.8. Make sure that the This feature is not available option is checked for the Prism Client and

Prism Common Services options. A red “X” should appear next to those options.The Prism Management Server Options window appears.

9. (Optional) Change the default port numbers for the Prism Management Server. Click Check Port to determine if the port is available for use.

10. (Optional) Change the default Video Configuration Manager (VCM) server and port number for the Prism Management Server by typing them into the VCM Server and VCM Port fields. Ensure that the VCM server URL is valid for the Prism system.

11. (Optional) To receive status messages from the Prism Management Server, select the Configure E-mail Address check box and enter values in the E-mail address to receive messages, SMTP Server, and Sent from e-mail address fields.

12. Click Next. 13. When the Prism Common Services Server Location window appears:


b. Click Test Connection to ensure that the computer can connect to the Prism Common Services Server.


14. On the Prism Broker Configuration window, enter the FQDN for the computer that hosts the primary LS Message Broker in the Broker Server field. (By default, this broker is installed on the Prism Common Services Server, but may be installed on another computer in a customized installation.) Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary. Click Check Port to determine if the port is available for use.

15. (Optional) If a backup broker is installed, type the FQDN for the computer that hosts the broker in the Backup Broker Server Name field and adjust the default port setting, if necessary. Click Check Port to determine if the port is available for use. Click Test Connection to ensure that the client can connect to the computer.

16. Click Next.


28

The Destination Folder window displays the default folder for Prism application files.17. (Optional) Click Change to select a different folder.



Note: Do not license the Prism Management Server computer. Only the Prism Common Services Server computer that hosts the Prism Common Services database needs to be licensed.

After installing Prism on server computers, install Prism on client computers as described in Installing Prism on Client Computers on page 22.

Using Advanced Installation OptionsThis section describes how to use the advanced options provided in the Installation Wizard to:

• Customize a server computer installation• Customize a client computer installation• Install a backup brokerTo learn about using advanced options to install Prism Management Server on a separate server computer, refer to Installing a Prism Management Server on page 26.


Customizing an All-in-One Server Computer InstallationThis section describes how to customize installation for a server computer that will contain all of Prism’s server functionality. This type of system, also known as an “All-in-One” or “Complete” Prism system, uses a single server computer to host the Prism Common Services database and a Prism Management Server.


The following elements can be customized:

• The default SQL administrator account password.• The broker configuration.• The location where Prism files are stored.• An external Simple Mail Transfer Protocol (SMTP) server through which Prism can send

notification messages about a Prism Management Server to an administrator can be configured.• The Prism Management Server port.The following steps can also be used to re-install Prism program files if the original files were corrupted, or if upgrading to a new version of Prism.

To perform a custom installation on an “All-in-One” server computer:







5. On the System Type Information window, click Custom System. 6. On the Custom Setup window, click the icon next to Prism Management Server and select the

This feature will be installed on the local hard drive option from the drop-down list that appears.

7. Click the icon next to Prism Common Services Server and select the This feature will be installed on the local hard drive option from the drop-down list that appears.The Prism Client option will be automatically selected because those files are also installed on a Prism Common Services Server.

8. Click Next.9. On the Prism Broker Configuration window, enter the FQDN for the computer that hosts the

primary LS Message Broker in the Broker Server field. (By default, this broker is installed on the Prism Common Services Server, but may be installed on another computer in a customized installation.) Adjust the default port setting, if necessary. Click Check Port to determine if the port is available for use.

10. (Optional) If a backup broker will be installed (see Installing Prism on Client Computers on page 22), type the FQDN for the computer that will host the broker in the Backup Broker Server Name field and adjust the default port setting, if necessary. Click Check Port to determine if the port is available for use.

11. Click Next.The Prism Management Server Options window appears.

12. (Optional) Change the default port numbers for the Prism Management Server. Click Check Port to determine if the port is available for use.

13. (Optional) To receive status messages from the Prism Management Server, select the Configure E-mail Address check box and enter values in the E-mail address to receive messages, SMTP Server, and Sent from e-mail address fields.

14. Click Next.15. When the SQL Account Configuration window appears, the Enter SQL Instance field contains

the default instance VMSSQL and the password and the password fields contain the default password for the SQL system administrator (sa) account: “SecurityMaster08”.a. (Optional) To change the default password, type the new password in the fields provided.b. (Optional) Enter a preconfigured SQL instance or select the Use default SQL Instance name

checkbox.c. Click Next.

16. When the Change the “Secure” password window appears:a. (Optional) Click Change Password and type the new password in the fields provided.b. Click Next.The Destination Folder window displays the default folder for Prism application files.



30


18. Click Next.19. When the Ready to Install the Program window appears, click Install.20. When a window appears to indicate that Prism was installed successfully, click Finish.21. When the Welcome to PrismCS License Setup process window appears, click OK.

The License Setup window appears. 22. (Recommended) Before licensing the Prism Common Services Server, confirm that the

Installation Wizard created the Prism Common Services database. See Verifying that the Prism Common Services Database Is Installed on page 47.

The Prism Common Services Server should be licensed immediately, as described in Licensing Prism on page 21. Otherwise, Prism will operate in demonstration mode with limited functionality.

Customizing a Client Computer InstallationThis section describes how to use the Installation Wizard to customize installation on a client computer by changing the broker configuration or the folder where Prism files are stored. These steps can also be used to re-install Prism program files if the original files were corrupted, or if upgrading to a new version of Prism.

Note: This section does not pertain to Video Matrix clients, which cannot be customized.

A Prism Client installation includes these components:

• The Prism Client program used to display video.• The client version of the Prism Common Services program.• The LS Message Broker, along with LS Message Broker certficates and the Prism Watchdog

Service.To perform a custom installation on a client computer:





5. On the System Type Information window, click Custom System. 6. On the Custom Setup window, click the icon next to Prism Client and select the This feature

will be installed on the local hard drive option from the drop-down list that appears.7. For the Prism Management Server and Prism Common Services Server options, select the

This feature will not be available option if it is not already selected. A red “X” should appear next to those options.

8. Click Next.9. On the Prism Common Services Server Location window, type the name of the server computer

that hosts the Prism Common Services database and click Next.


Upgrade Prism

10. On the Prism Broker Configuration window, enter the FQDN for the computer that hosts the primary LS Message Broker in the Broker Server field. (By default, this broker is installed on the Prism Common Services Server, but may be installed on another computer in a customized installation.) Click Test Connection to ensure that the client can connect to the computer. Adjust the default port setting, if necessary.

11. (Optional) If a backup broker is installed, type the FQDN for the computer that hosts the broker in the Backup Broker Server Name field and adjust the default port setting, if necessary. Click Test Connection to ensure that the client can connect to the computer.

12. Click Next.The Destination Folder window displays the default folder for Prism application files.




Upgrade Prism

IMPORTANT: If your system utilizes Prism and Lenel NVR make sure that you first upgrade Lenel NVR before upgrading Prism.

Management Server1. Back up the databases using the Database Maintenance utility (C:\Program Files

(x86)\Prism\Prism Common Services\DatabaseScripts\DatabaseMaintenance.exe).2. Back up the Prism Management server (http://localhost:5000/ or https://<servername>:5001/).3. Disconnect and turn off Prism Services on all installed Prism Clients.4. Review Before You Begin on page 41 and make sure that all Prism programs and services are

stopped and all users are logged out of the system.5. Run the Prism setup.exe. The Prism Installation Wizard starts. Click Next.6. A summary of upgrade components is displayed. To continue, click Install. The status bar

updates as the upgrade progresses. 7. The Prism License Setup window appears. Enter your Prism License and click Register.8. Click Finish to complete the Prism upgrade.9. If necessary, reboot the system after two minutes.

Client1. Review Before You Begin on page 41 and make sure that all Prism programs and services are

stopped on the machine to be upgraded.2. Run the Prism setup.exe. The Prism Installation Wizard starts. Click Next.3. A summary of upgrade components is displayed. To continue, click Install. The status bar

updates as the upgrade progresses.


32

4. The Prism License Setup window appears. Enter your Prism License and click Register.5. Click Finish to complete the Prism upgrade.6. If necessary, reboot the system after two minutes.

What’s Next?

After Prism is installed on all server and client computers, proceed to Configuring Prism on page 33.


CHAPTER 5 Configuring Prism

After setting up devices and then installing and licensing Prism software on server and client computers, configure Prism by:

• Using the Prism Common Services program to set up facilities, clients, permissions, operators, schedules, alarms, events, and maps.

• Using the Prism Client program to add recorders, configure cameras, assign devices to facilities, and configure sequences, salvos, views, and Regions of Interest (ROI) for cameras.


• Planning a Prism System on page 33• Logging into the Prism Common Services Program on page 35• Adding Additional User Accounts on page 36• Setting Up a Prism System on page 37• What’s Next? on page 40

Planning a Prism SystemRegardless of whether Prism is being set up for a single site, or for a more complex, multi-site environment, read this section in its entirety before configuring the Prism software. It provides guidelines regarding how to set up Prism in a logical way that will support future expansion.

A digital map should be created for each facility that includes all camera locations, as discussed later in Step 6: Create Maps on page 38. Maps can be layered and nested to allow easy navigation through satellite maps, multi-story buildings, and very large areas. In addition to serving as a graphic representation of a system, a map can be useful when naming devices, as described next.


34

Naming ConventionsEffective naming conventions are essential for a successful Prism deployment. The use of meaningful and well-structured names to cameras, sequences, views, salvos, and alarms, will help to:

• Identify the location and function of each camera in a network.• Identify cameras and organize them into meaningful camera groups.• Quickly search for cameras, sequences, views, salvos, and events.• Identify alarm events that have common characteristics or triggers.Instead of naming devices according to make, model, and serial number, use pertinent elements in each device name to provide a frame of reference regarding the device’s type, function, location, or another category that is meaningful for an installation. For example, instead of naming a camera UltraViewWDR120546, name it BLDG2_LOBBY_NE_CAM if it is located in the northeast corner of the Building 2 lobby.

Pseudo numbers can be assigned to a group of cameras to identify them by function or location. For example, assign pseudo numbers 101 through 110 for cameras on the first floor of a building, 201 through 210 for second floor cameras, 301 through 310 for third floor cameras, etc.

Naming GuidelinesConsider the following guidelines for naming conventions:

• Names can include alphanumeric characters, spaces, underscores, and hyphens, but no other special characters.

• A camera name should indicate if it is a PTZ camera (for example, BLDG2-PTZ-05).• Avoid unnecessary information in names. For example, do not include “camera” or “cam” as part

of a camera name. The type of device should be clear from the context.• Choose meaningful prefixes, such as a geographic location, function, or time of day.

– Use geographic designations to classify cameras and camera groups, such as buildings at a facility: BLDG1, BLDG2, BLDG3.

– Use camera functions to classify cameras, camera groups, or archives: FIX, PTZ, HIGHRISK, DOOR.

– Use time of day to classify events: MORN, NOON, EVNG.• Use nested prefixes to help locate specific areas, making sure that the order of the prefixes

reflects how groups will be organized. For example, use a grouping such as TX-AU–BLDG1-FL01 to name cameras and set up camera groups for different states (TX), with subgroups for cities (AU), buildings (BLDG), and floors (FL).

• When using numeric identifiers in device name prefixes, be sure that the numbering scheme allows for expansion. For example, use C001, C002, etc., instead of C1, C2, etc. By adding extra digits, Prism can sort devices correctly as the number of devices grows.

For example, if cameras are numbered as 01, 02, and 10, Prism will sort the names correctly.– PTZ01– PTZ02– PTZ10Note that improper numbering will result in incorrect sorting, as shown here:– PTZ1– PTZ10– PTZ2


Logging into the Prism Common Services Program

Logging into the Prism Common Services ProgramInitially, only one operator record exists in the Prism Common Services database: an English language operator named secure with a case-sensitive password, SecurityMaster08. Use this operator and password when logging into the Prism Common Services program for the first time. The secure operator has an administrator permission level.

Two other English language default operators exist after Prism Common Services installation:

• Export–This operator has view and export permission. The Login ID and Password for this operator is export.

• View–This operator has view-only permission. The Login ID and Password for this operator is view.

Also, note the following details:

• If the computer was recently restarted, wait at least four minutes for Prism services to start before trying to log into the Prism Common Services program.

• If User Account Control (UAC) is enabled on the computer, run the Prism Common Services program as an administrator.

• For non-English operating systems, log into the Prism Common Services program for the first time using the English-language operator, secure. Then create a language-specific operator record. See Adding a Prism Operator Record on page 36.

To log into the Prism Common Services program on the Prism Common Services Server:

1. Start the Prism Common Services program. Refer to the OnGuard Installation Guide, Using OnGuard on Supported Operating Systems section for operating system-specific paths.

2. Select the File menu, and then click Login to open the Login window.3. Enter the default login ID and password.

• Login ID: secure• Password: SecurityMaster08 (case-sensitive)

4. Click OK. The main Prism Common Services window appears.

Before adding records in the Prism Common Services program, review the instructions for adding records, as described next.

Adding Records in the Prism Common Services ProgramWhen adding new records in the Prism Common Services program, note the following details:

• Be sure to use either the New Record menu option or icon after opening the form. • The New Record option is available only when a form is open and contains records. • Permission is required to update records. • The New Record icon on the Record toolbar has the same features as the New Record menu

option. For step-by-step instructions about adding records, refer to online help or the Prism User Guide stored in the \Program Files (x86)\Prism\Prism Common Services\Documentation folder.


36

Adding Additional User AccountsWhen Prism was installed on the Prism Common Services Server, a default local user account was created, as detailed here:

• User group: SPAdmin• User name: secure • Password: SecurityMaster08 (case-sensitive)A Windows user account should be added for each Prism administrator to clearly identify each administrator in Windows. (See Assigning System-Level User Passwords on page 7.) Assign each user account to the SPAdmin group created during installation.

The next step is to add an operator record for the person configuring the Prism system, as described next.

Adding a Prism Operator RecordBy default, Prism includes a single operator record, secure. Another initial operator record should be created for the administrator configuring Prism so that the steps performed to set up the system can be tracked.

To add an operator record:

1. Log into the Prism Common Services program using the default login ID, secure.2. Select Administration from the Application Group pane, and then Operator.3. Select New Record from the File menu or click the New Record icon on the Record toolbar. 4. Complete the Operator form. Refer to the Prism online help for details.

Be sure to select System Administrator in the Permission field. This default permission profile provides complete read, write, and delete privileges.

5. Click Save.6. Log out of the Prism Common Services program, and then log back on as the new operator.

Note: If logging back on as a new operator with a language other than English, there is a slight delay while Prism copies localized Help files to the main directory.

After configuring Prism elements such as facilities and permissions, operator records can be created for each person that will use the Prism software. For now, proceed to the next section and follow the instructions for configuring Prism.


Setting Up a Prism System

Setting Up a Prism SystemThis section includes the basic steps for configuring Prism, listed in a sequence that is suitable for a smooth system configuration. For example, facilities should be defined before adding recorders.

Note: This section is intended as an overview only. Use it in conjunction with online help or the Prism User Guide stored in the \Program Files\Prism\Prism Common Services\Documentation folder.

To set up a Prism system, follow these steps:

• Step 1: Set Preferences on page 37• Step 2: Add Facilities on page 37• Step 3: Add and Configure Recorders on page 38• Step 4: Configure Cameras on page 38• Step 5: Assign Devices to Facilities on page 38• Step 6: Create Maps on page 38• Step 7: Configure Client Computers on page 38• Step 8: Configure Permission Profiles on page 38• Step 9: Add Operator Records on page 38• Step 10: Configure Schedules on page 39• Step 11: Configure Alarms and Events on page 39• Step 12: Test Communications on page 39• Step 13: Set Memory Usage on page 40• (Optional) Step 14: Change Passwords for the Administrator Accounts on page 40

Step 1: Set Preferences Use the Preferences form (Prism Common Services program; Administration group) to select a time interval to archive the Prism Common Services database.

Note the following details about the Prism Common Services archiving process:

• If using Microsoft SQL Server Express 2008 R2 or SQL Server 2012 with Prism, the Windows Task Scheduler executes archiving tasks. Keep the startup type for this service set to Automatic.

• If using a full edition of Microsoft SQL Server, the SQL Server Agent server instance (VMSSQL) must be running during the archive process. To learn about adding this instance, see Adding a Microsoft SQL Server Instance on page 9.

Step 2: Add Facilities Use the Facility form (Prism Common Services program; Places & Policies group) to define facilities that represent buildings or locations. Facilities will be used to divide cameras into logical groups on the Device Tree in the Prism Client program, and can also be used to control which operators can access a camera.

2.1 Assign Facilities to the Initial Operator RecordUse the Facilities tab on the Operator form (Prism Common Services program; Administration group) to assign facilities to the default operator record, secure, and the operator record created for the administrator configuring the system (see Adding a Prism Operator Record on page 36).


38

Step 3: Add and Configure RecordersSwitch to the Prism Client program and use the Dashboard window to add and configure recorders (and encoders, if applicable).

IMPORTANT: If using Prism in an integrated environment with OnGuard, use the Prism Migration Tool before adding Lenel NVRs in the Dashboard window. See Using Prism in an Integrated OnGuard Environment on page 14 for details.

To access the Prism Client program from the Prism Common Services program:

• Click the Video Console icon ( ) on the Prism Common Services toolbar, or• Click Launch Administrator in the Video section of the Application Group pane.

Step 4: Configure CamerasUse the Dashboard window in the Prism Client program to configure cameras.

Step 5: Assign Devices to FacilitiesAfter adding and configuring recorders and cameras in the Dashboard window, use the Edit Facility Assignment option on the Tasks menu to assign devices to facilities.

Step 6: Create Maps Return to the Prism Common Services program and create digital maps for facilities to indicate where cameras are located. Consider the various capabilities of each type of device (for example, a PTZ camera vs. a fixed analog camera) when creating maps. Different symbols can be used on a map to denote each type of device, and configure map symbols so that when the condition of a device changes (for example, if a camera detects motion), the related symbol on the map changes its appearance to alert operators.

Step 7: Configure Client Computers Use the Client form (Prism Common Services program; Administration group) to define alarm notification and Auto Shutdown settings for client computers.

Step 8: Configure Permission Profiles Use the Permission form (Prism Common Services program; Administration group) to define permission profiles that control what an operator can and cannot do in Prism Common Services and Prism Client programs. After a permission profile is created, it can be assigned to one or more operators on the Operator form, as described next.

Step 9: Add Operator Records Use the Operator form (Prism Common Services program; Administration group) to create operator records that allow users to access and control Prism. Create an operator record for each person who will use Prism, including administrators, so that Prism can track transaction history appropriately.


Setting Up a Prism System

Step 10: Configure Schedules Use the following Prism Common Services forms to define schedules:

• Use the Time Schedule form (Schedules group) to configure the time intervals when actions will occur, such as turning on alarm monitoring.

• Use the Event Notifier form (Alarms & Events group) to assign alarms and reset conditions for an event that will trigger an e-mail message. This form can also be used to designate which operators receive e-mail about the event, as well as the content of the e-mail.

• Use the Client Group form (Administration group) to assign client computers to logical groups, to which mode schedules can be applied. Client groups can also be used to route and bump alarms.

• Use the Mode Schedule form (Schedules group) to define the date and time when a mode goes into effect. The purpose of a mode is to allow clients to operate differently than defined for Normal mode. Mode schedules appear as schedule options on the Time Schedule form.

• Use the Holiday Schedule form (Schedules group) to define the date and time a holiday schedule starts, and the date and time the holiday schedule ends.

• Use the Holiday Group form (Schedules group) to assign holiday schedules to a holiday group.

Note: Lenel NVR devices controlled by OnGuard are not impacted by Prism schedules.

Step 11: Configure Alarms and Events

Note: In an integrated OnGuard environment where events and alarms are shared, OnGuard Event Proxy must be installed on the OnGuard server. A user specific to Event Proxy needs to be created in OnGuard and assigned the access privileges determined by the administrator. See the OnGuard Event Proxy Administration Guide for further information.

Use the following Prism Common Services forms to define alarms and events:

• Use the Instruction form (Alarms & Events group) to create messages that appear on the Alarm Monitor window whenever the associated alarm occurs.

• Use the Response form (Alarms & Events group) to create a list of frequently used, predefined responses to an alarm, reducing the need for operators to type text on the Alarm Monitor window.

• Use the Alarm form (Alarms & Events group) to modify the default alarm records generated for each camera when recorders are added to Prism in the Dashboard window.

Note: If using Prism alarms and schedules with VOS-based cameras, the Prism Common Services alarm names must match the event names defined in the CCS web interface. See UltraView Device Notes on page 15.

If OnGuard alarms are not visible in the Alarm form, see the OnGuard Event Proxy Administration Guide for configuration instructions.

• Use the Video Event Trigger form (Alarms & Events group) to automate how Prism responds when an alarm occurs.

Step 12: Test CommunicationsUse the following options on the Video Synchronization tab of the Preferences form (Prism Common Services program; Administration group) to test communications.

• Broker Connection Status


40

• Video Servers• Video DevicesIf components are not communicating properly, refer to Resolving Communication Issues on page 46.

Step 13: Set Memory Usage

Note: This step requires Microsoft SQL Server Management Studio Express, available at www.microsoft.com. (If using a full version of SQL Server, SQL Server Management Studio is already installed and should be used instead.)

To prevent slow performance resulting from excess memory usage, limit the size of the Prism Common Services database to 1 GB by following these steps:

1. On the Prism Common Services Server, start Microsoft SQL Server Management Studio. 2. Click Connect.3. Right-click the Prism Common Services database instance on the navigation tree to the right. 4. Select Properties. 5. Select Memory page. 6. Set the minimum server memory to no less than a quarter of the allowable limit. 7. Set the Maximum server memory (MB) option to 1 GB. 8. Click OK.9. Exit SQL Server Management Studio.

(Optional) Step 14: Change Passwords for the Administrator AccountsTo increase security, the passwords for the default administrator accounts that are part of the SPAdmin user group can be changed:

To change the secure account password, use the Operator form in the Prism Common Services program, as described in the Prism online help.

What’s Next?The basic setup is complete. To continue customizing Prism, use the Prism Client program to configure additional Prism elements, such as sequences, views, and salvos. After confirming that Prism is fully functional, back up all Prism data, as described in the Prism online help.

User name Case-sensitive password

secure SecurityMaster08

admin admin


http://www.microsoft.com

CHAPTER 6 Uninstalling Prism

This chapter describes how to remove Prism programs, folders, and files.

Note: To uninstall Lenel NVR programs, refer to the Lenel NVR System User Guide located at http://partner.lenel.com.


• Before You Begin on page 41• Uninstalling Prism with the Installation Wizard on page 42• Uninstalling Prism Manually on page 42

Before You BeginBefore removing Prism from a computer, note the following details:

• For client computers, make sure that:– The Prism Common Services and Prism Client programs are both closed.– All Prism services are stopped. See “Starting and Stopping Prism Services” in Prism online

help for details. • For Video Matrix client computers, make sure that:

– The Prism Client program is closed.– The Prism Video Matrix service is stopped.

• For server computers, make sure that:– All client computers are logged out of the Prism Common Services program.– The Prism Common Services and Prism Client programs are both closed.– All Prism services are stopped. See “Starting and Stopping Prism Services” in Prism online

help for details. – All administrators are logged out of the secure account.

• Determine if any data should be preserved and copy it to another location, if necessary.



42

– For computers where the Prism Client program was used to save evidence files, use Windows Explorer to navigate to the \Users\<Name>\Prism\Evidence Locker folder (where Name is the name of a user account on the computer). Back up any relevant files.

– For server computers, follow the instructions in the Prism User Guide or online help to back up the three Prism Common Services databases (Main, History, and Archive), event data, third-party report data, graphics map data, and Prism Management Server data. If Prism is operating in an integrated environment with OnGuard, be sure to back up the OG.db file stored in the <Prism installation directory>\Prism Common Services folder.

Uninstalling Prism with the Installation WizardTo uninstall Prism using the Installation Wizard:

IMPORTANT: Review Before You Begin on page 41 and make sure that all Prism programs and services are stopped, all users are logged out of the system, and any existing data is backed up. Refer to the Prism User Guide for details about backing up data.

Although the Installation Wizard will create a backup of pertinent files in the \Users\<Name>\AppData\Lenel\Prism folder, users are strongly encouraged to back up data before using the Installation Wizard to uninstall Prism.


2. Run the Prism installation installer. If the Installation Wizard does not start automatically, use Windows Explorer or File Explorer (depending on the operating system) to navigate to the \Setup folder on the installation disc, right-click setup.exe, and then click Run as administrator from the shortcut menu.

3. When the Installation Wizard appears, click Next.4. On the Program Maintenance window, click Remove.5. On the Remove the Program window, click Remove again to confirm your selection.6. When a window appears to indicate that Prism was removed successfully, click Finish.

The Installation Wizard will create a backup of pertinent files to the \Documents and Settings\Application Data\Lenel\Prism folder

To reinstall Prism, refer to Installing Prism Software on page 19.

Uninstalling Prism ManuallyThis section describes how to uninstall Prism using Windows Control Panel. Use this method to remove one or more Prism components from a computer that is part of a Prism system already populated with data.

1. Review Before You Begin on page 41 and make sure that all Prism programs and services are stopped, all users are logged out of the system, and any existing data is backed up. Refer to the Prism User Guide for details about backing up data.



Uninstalling Prism Manually

3. Depending on which program is used to manage Prism Common Services data, use Microsoft SQL Server Express or Microsoft SQL Server to delete the Main, History, and Archive databases on the Prism Common Services Server.

4. Open Control Panel and access the “Uninstall or change a program” page.5. To remove any or all of the programs listed below, select a program, and then click Uninstall.

• Prism x.x (where x.x is the version installed)• Prism Common Services Crystal Reports Runtime • Microsoft SQL Server Express• Microsoft SQL ServerThe uninstallation of Prism does not uninstall the LNVR Client SDK or Lenel Common Components. If OnGuard is not installed and a clean uninstall is required, the following components must also be uninstalled from the Control Panel:

• Lenel AppContext Common Component• LNV Suite Client Runtime Installer• AVS Controller Service

6. Close Control Panel.7. To fully restore a computer to a pre-Prism state, use Windows Explorer to delete these folders:

• <Prism installation directory>\Prism• <Prism installation directory>\Prism Server • <Prism installation directory>\Prism Common Services• \Users\<Name>\Prism\ (where Name is the name of a user account on the computer)

Note: Not all folders will exist on all computers. For example, the \Users\<Name>\Prism\ folder only exists on computers where the Prism Client program was used to save evidence files.

The Prism uninstall will not remove user-created files such as logs and databases. These can be manually removed if no longer necessary. The files will also be backed up in the user directory of the user that uninstalled the program.

To reinstall Prism, refer to Installing Prism Software on page 19.


44

CHAPTER 7 Troubleshooting

This chapter provides information to help diagnose and solve problems that may arise during or after the installation of Prism software. Topics in this chapter include:

• Installation Troubleshooting Tips on page 45• Installation FAQs on page 48• Database FAQs on page 49For additional troubleshooting tips, refer to online help or the Prism User Guide stored in the <Prism installation directory>\Prism Common Services\Documentation folder. The Prism User Guide is also provided on the Prism installation disc.

Installation Troubleshooting TipsIf problems are encountered during installation, consider these tips:

• Review Preparing Computers on page 5 to rule out a problem with a computer’s configuration.• After checking for Windows updates (see Updating System Software on page 6), disable the

Install updates automatically option for Windows so that automatic updates do not disrupt the installation process.

• Ensure that the KB2919442, KB2919355, and KB2999226 Windows updates are installed by selecting View installed updates in the Uninstall or change a program window. If these updates are not installed, go to support.microsoft.com, search for each Knowledge Base article, and install the updates.

IMPORTANT: KB2919442 MUST be installed before installing 2919355.

• Close any open Windows programs before installing the Prism software.• If the Installation Wizard does not launch automatically after inserting the installation disc in the

drive, start the Installation Wizard manually by navigating to the disc in Windows Explorer or File Explorer, depending on the operating system. Right-click the autorun.exe file and select Run as administrator.

• Installation may stall if antivirus software is running. If so, configure the software so that the disc drive is not scanned.


46

• If unexpected reboots occur during installation, log in again to restart the process. This issue may occur if the user is not logged into the computer with a Windows user account (local or domain) that is a member of the Administrators group with full access rights, including permission to apply required registry changes (i.e., full permission control).

• If a Windows Installer Service error message appears while Prism is configuring the SQL database on the Prism Common Services Server, restart the computer and log in as a user with local administrator rights. The installation process should restart on its own.

• If errors occur during the installation of Prism prerequisites, check the following items:– Is Microsoft .NET Framework enabled? For Windows Server 2008 R2 computers, this

feature must be enabled before installing Prism. (See Enabling Microsoft .NET Framework on page 8.) For other supported computers, the Prism Installation Wizard automatically installs and enables Microsoft .NET Framework.

– Are you running the Installation Wizard as an administrator? Log on to the computer with a Windows user account (local or domain) that is a member of the Administrators group with full access rights, including permission to apply registry changes.

– Does the machine have a FQDN? Is it joined to a domain? See Configuring the Computer for the Network on page 6 and Verifying the FQDN in Configuration Files on page 47

– Was a previous Prism version on this machine at any time? Refer to Uninstalling Prism on page 41 to learn about removing Prism components. In extreme cases, the computer may need to be re-imaged.

– Is a full edition of Microsoft SQL Server being used instead of the default Microsoft SQL Server Express program? A server instance named “VMSSQL” must be created and configured. See Adding a Microsoft SQL Server Instance on page 9.

– Are there any Prism-related messages in the Windows error logs? In the Computer Management tool that is part of the Microsoft Management Console (MMC), click Event Viewer and examine errors and warnings in the logs.

– Are the KB2919442, KB2919355, and KB2999226 Windows updates installed? Install these updates before installing Prism to ensure that Microsoft Visual C++ 2015 Redistributable Package installs correctly.

• If the Windows Event viewer displays an error similar to “Faulting module name: WS2_32.dll_unloaded, version: 0.0.0.0, time stamp: 0x4ce7ca25”, then disable the Windows Customer Experience Improvement Program (CEIP) by following the instructions athttps://www.microsoft.com.

• If the “Error installing SQL Express” message appears at the end of a Prism Common Services Server installation, run one of the following programs from the \SQLExpress folder on the installation disc, and then restart the computer:– For 64-bit computers, double-click RunSetup_x64.

• The Prism Installation Wizard creates a Prism_version_Installation.log file in the \Users\<Name>\Prism folder, where version is the current version and Name is the name of the user account on the computer.

Resolving Communication IssuesThis section contains troubleshooting suggestions if client computers that are not communicating properly with other system components.

First, use the Microsoft Management Console to verify that the FQDN in the Prism security certificate on the client computer matches the FQDN of the computer that hosts the primary LS Message Broker. (By default, the primary LS Message Broker is installed on the server computer that hosts the Prism Common Services database, but it can be installed on any Prism computer.)



Installation Troubleshooting Tips

To use MMC to check the FQDN in the security certificate:

1. Log into the Prism Common Services Server as an administrator.2. Open the Microsoft Management Console. 3. On the File menu, click Add/Remove Snap In.

The Add or Remove Snap-in dialog box appears.4. In the list of available snap-ins, select Certificates and click Add.5. When prompted to select an account for the snap-in, click Computer account. 6. Click Next.7. When prompted to select the computer for the snap-in, click Local Computer.8. Click Finish.

The Certificates (Local Computer) snap-in appears in the Add or Remove Snap-in dialog box.9. Click OK to close the dialog box.10. In the Console Root window, open the Certificates (Local Computer)/Trusted Root

Certification Authorities/Certificates folder.11. Verify that the Prism SOA Common Trusted Root certificate exists.12. Open the Certificates (Local Computer)/Personal/Certificates folder.13. Verify that the certificate issued by the Prism SOA Common Trusted Root includes the FQDN of

the computer that hosts the primary LS Message Broker. (By default, the primary broker is installed on the server computer that hosts the Prism Common Services database, but it can be installed on any Prism computer.)

14. If the FQDN does not match, re-install Prism on the client computer to generate a new security certificate. See Installing Prism on Client Computers on page 22.

Verifying the FQDN in Configuration FilesCheck the following configuration files to verify that the FQDN matches the FQDN of the computer that hosts the primary LS Message Broker.

• The Prism Common Services broker configuration file, BrokerConfig.ini, located in the <Prism installation directory>\Prism Common Services folder on the server computer that hosts the Prism Common Services database.

• The Prism Common Services host configuration file, sms_app_prism_cs_host.ini, located in the <Prism installation directory>\Prism Common Services folder on the server computer that hosts the Prism Common Services database.

• The Prism Management Server configuration file, production.ini, located in the <Prism installation directory>\Prism Server folder on each server computer where Prism Management Server is installed.

Verifying that the Prism Common Services Database Is InstalledTo verify that the Installation Wizard created the Prism Common Services database:

1. On the server computer that hosts the Prism Common Services database, open the Windows administrative tool used to manage services for the operating system.

2. Check for SQL Server (VMSSQL), the server instance used by the Prism Common Services program.

If no SQL instance is found and SQL Server Express 2008 is being used with Prism (the default), use the Create Database utility (see Using the Create Database Utility on page 50) and then check for


48

VMSSQL again. If using a full edition of SQL Server, refer to Adding a Microsoft SQL Server Instance on page 9.

Installation FAQsDoes Prism support the use of roaming user profiles?

The Prism Common Services graphics programs (for example, Graphics Map Editor) use a local stored cache so users will not be able to open or save graphics maps. If using roaming profiles on a client computer, follow these steps to change the cache path to a mapped network drive:


2. Map the network drive for the cache on the local computer3. Stop the Prism Common Services program on the local computer.4. Open Registry Editor.5. Back up the registry. (See windows.microsoft.com for details.)

IMPORTANT: Only advanced users should change settings in Registry Editor. Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Lenel cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Backup the current settings before proceeding.

6. Navigate to the following key:HKLM->Software->{Wow6432Node}->UTCFS->PrismCommonServices->Configuration->Paths

7. Change the JVM Working Area key to point to the mapped network drive.8. Restart the Prism Common Services program on the local computer. (8043).What communication ports does Prism use?

Prism uses different ports depending on which type of computer is involved:

• On client computers, Prism opens all ports to support streaming video from URLs. • On the computer that hosts Prism Management Server, Prism uses port 443 to support HTTPS.• On the Prism Common Services Server, Prism opens the following ports:

Ports Used by the Prism Common Services Server

Port Description

135 Client Workstation/Server Communications Port

1433 SQL Client Port

5000* HTTP Port

5001* HTTPS Port

5671* Message Broker SSL Port (Default Configuration)

5672* Message Broker TCP Port

6699 Controller Communications Port


windows.microsoft.com

Database FAQs

The Prism Common Services Server also uses an SQL port whose number varies according to the SQL server configuration.

To identify the specific port number:

1. Start the SQL Server Configuration Manager. 2. When the SQL Server Configuration Manager appears, expand the navigation tree for SQL

Server Network Configuration to display Protocols for VMSSQL. 3. Right-click TCP/IP, select Properties, and then switch to the IP Addresses tab.

The SQL port number appears in the IPAll, TCP Dynamic Ports field. Can the broker port be changed after installation?

The default Prism broker port is 5671 and should not be changed after installation.

Why are recorders and cameras not interacting with the Prism Client program?

Be sure to enable motion detection and configure area settings for each camera at the recorder level, as described in Setting Up Devices on page 13.

Can I use the Installation Wizard for other purposes?

The Installation Wizard can also be used to add other components to an existing Prism installation, and remove Prism from a computer (see Uninstalling Prism with the Installation Wizard on page 42).

Note: A Prism Client workstation cannot be converted directly into a Prism Common Services Server. Instead, use the Installation Wizard to remove the Prism Client components from the computer, and then launch the Installation Wizard again to install the necessary components for a Prism Common Services Server.

Database FAQsThe following message appears when the Prism Common Services program starts: “The Prism Common Services database was created with errors. Please check the error log for details.”

Review the CreateDatabaseLog.txt logfile stored in the <Prism installation directory>\Prism Common Services\Logs folder on the Prism Common Services Server, and correct any installation configuration problems. If the problem continues, recreate the database; see Using the Create Database Utility on page 50.

Prism installed SQL Server Express and the Prism Common Services Server restarted but “hangs” for more than five minutes. How can I complete the installation?

Double-click the following file to continue the installation:

<INSTALL DIR>\\Program Files\Prism\Prism Common Services\SQLExpress\SPMSCRAT.exe

8088 Server Workstation Video Streaming Port

8085 Start Video Communications Port Range (3)

8089 Start Digital Video Viewer Port Range (20)

*Applicable for default configuration only. Port is customizable.

Ports Used by the Prism Common Services Server


50

When using the full version of SQL Server instead of SQL Server Express, the following error message appears when the Prism Common Services program starts:

“Error loading meta-data. Details: Error obtaining a connection from the connection pool.”

Check to see if the Shared Memory, TCP/IP, and Named Pipes protocols are enabled for the VMSSQL server instance. Refer to Adding a Microsoft SQL Server Instance on page 9.

When using the full version of SQL Server on a Windows 2008 Server computer, I am prompted to use the Role Manager to install Microsoft .NET Framework during installation.

Make sure that SQL Server 2008 or later is installed, and then check to see if Microsoft .NET Framework 4.0 or later is enabled.

Microsoft SQL Server Express had to be uninstalled. How should it be reinstalled?

Run one of the following programs from the \SQLExpress folder on the installation disc, and then restart the computer:

– For 64-bit computers, double-click RunSetup_x64.

Using the Create Database UtilityIf the Prism Common Services database was not created during Prism installation, use the Create Database utility to add the database on the Prism Common Services Server, as described next.

IMPORTANT: The Create Database utility should be used only when first installing Prism, before any records are added to the Prism Common Services database. The utility will delete existing records.

To use the Create Database utility:

1. From the Start menu, click the Create Database utility. The Select Product Edition page of the Create Database utility appears.

2. Type the Username and Password for the SQL system administrator account. Click Next.The next page displays the default folders for data and the log file. Browse to select new destinations, if necessary.

3. Click Create Database.A progress bar appears as the utility creates the database, then a message appears to indicate that the database was created successfully.


Index

AAdd

facilities ................................................... 37graphics maps ........................................ 38language packs ....................................... 10Microsoft SQL Server instance ............ 9Prism Common Services records ........ 35recorders ................................................. 38

Alarms ............................................................... 39Assign user passwords ..................................... 7Axis cameras .................................................... 17

Bbackup broker .................................................. 22

CCameras

configuring in Prism ............................. 38naming conventions .............................. 34naming guidelines ................................. 34setting up ................................................ 13

Change passwords .......................................... 40Client computers

advanced installation options .............. 28checking network accessibility ............. 7folder structure ....................................... 32installing Prism software ..................... 22licensing .................................................. 25preparing ................................................... 5Video Wall clients ................................. 23

Client form ....................................................... 38Configure

alarms and events .................................. 39cameras ................................................... 38client computers .................................... 38

computers for Prism ................................ 6devices ..................................................... 13network cards ........................................... 7permission profiles ................................ 38presets for Axis cameras ...................... 17Prism ........................................................ 33recorders ................................................. 38recorders and cameras .......................... 13schedules ................................................. 39

Create Database utility ................................... 50Customize a configuration ............................ 25

DDevices

assigning to facilities ............................ 38configuring cameras in Prism ............. 38configuring recorders in Prism ........... 38setting up ................................................ 13

Display settings ................................................. 6Domains ............................................................. 6

EEvents, configuring ........................................ 39

FFacilities

adding ...................................................... 37assigning devices ................................... 38assigning to operators ........................... 37

Failover ............................................................. 14Firewall settings ................................................ 8FQDN ................................................................. 6

resolving communication errors ......... 46verifying in configuration files ........... 47


Index

52

GGraphics maps

creating .................................................... 38using with roaming profiles ................. 48

HHosts file ............................................................ 7

IInstall

advanced options for client computers 28backup broker ........................................ 22basic installation .................................... 20custom installation ................................ 25localized editions of Prism .................. 10Prism software ....................................... 19recorders and cameras .......................... 13troubleshooting ...................................... 45verifying an installation ....................... 47

Installation FAQs ............................................ 48

LLanguage packs ............................................... 10Lenel NVRs

configuring failover and redundancy . 14device notes ............................................ 13Prism Migration Tool ............................ 14program file locations ............................. 3Recovery tool ......................................... 15uninstalling software ............................ 41

Licensing Prismclient computers .................................... 25generating a license key ....................... 21Prism Common Services Server ......... 21

Localized editions of Prism .......................... 10LS Message Broker ............ 22, 23, 24, 25, 26

MMaps .................................................................. 38Memory usage ................................................. 40Microsoft .NET Framework 8, 10, 11, 22, 50Microsoft SQL Server instance ...................... 9

NNaming conventions ....................................... 34

OOnGuard ........................................................... 14

backing up the OG.db file .................... 42Prism Migration tool ............................. 38using Prism in an integrated OnGuard

environment ..................................... 14Operator form .................................................. 38Operator records

adding ............................................... 36, 38assigning facilities to ............................ 37

PPasswords

assigning to system-level users ............. 7changing for administrator accounts .. 40

Peer Server ......................................................... 2installing ................................................. 26

Permission form .............................................. 38Permission profiles ......................................... 38Preferences form ............................................. 37Preparing computers ......................................... 5

adding an SQL Server instance ............. 9adjusting firewall settings ...................... 8assigning user passwords ....................... 7configuring computers for the network 6configuring the SQL server for custom

database instances ........................... 10enabling Microsoft .NET Framework . 8installing localized editions of Prism . 10setting power options .............................. 7updating system software ...................... 6verifying display settings ....................... 6

Prerequisites ....................................................... 8Presets ............................................................... 17Prism

configuring ............................................. 33file locations ............................................. 2installing software ................................. 19language packs ....................................... 10licensing .................................................. 22planning a configuration ...................... 33uninstalling ............................................. 41upgrading from an earlier version ...... 32using with OnGuard .............................. 14

Prism Common Servicesadding records ........................................ 35initial setup ............................................. 37logging in ................................................ 35operator records ..................................... 36setting preferences ................................ 37

Prism Common Services Server ..................... 2Prism Management Server .............................. 2

installing ................................................. 26Prism Migration Tool ..................................... 14Prism User Guide ............................................ 37

RRecorders

configuring in Prism ............................. 38configuring Lenel NVR failover ........ 14setting up ................................................ 13using Lenel NVRs with OnGuard ...... 14using the Prism Migration Tool .......... 14

Resolve connection issues ............................. 46Roaming user profiles .................................... 48

SSchedules ......................................................... 39Server computers


Index

advanced installation options .............. 28installing Prism software ..................... 19preparing ................................................... 5

SQL Server ........................................................ 9System software, updating .............................. 6

TTest communications ...................................... 39Troubleshooting .............................................. 45

UUltraView

Video Configuration Manager (VCM) 15Video Operating System (VOS) ......... 15

UltraView device notes .................................. 15Uninstall Prism ................................................ 41

backing up data ...................................... 41using Control Panel ............................... 42using the Installation Wizard ............... 42

Update system software ................................... 6Upgrade from an earlier version of Prism .. 32User accounts

adding ...................................................... 36roaming user profiles ............................ 48setting passwords .................................... 7

VVideo Configuration Manager (VCM) ........ 15Video Matrix clients ....................................... 23Video Operating System (VOS) ................... 15

WWindows power options .................................. 7


Index

54

UTC Fire & Security Americas Corporation, Inc.1212 Pittsford-Victor RoadPittsford, New York 14534 USATel 866.788.5095 Fax [email protected]