Install Guide

IndigoVisionControl Center Installation Guide Control Center T HIS MANUAL WAS CREATED ON 09 APRIL 2014. DOCUMENT ID: IU-SMS-MAN001-17 Legal Considerations LAWS THAT CAN VARY FROM COUNTRY TO COUNTRY MAY PROHIBIT CAMERA SURVEILLANCE . P LEASE ENSURE THAT THE RELEVANT LAWS ARE FULLY UNDERSTOOD FOR THE PARTICULAR COUNTRY OR REGION IN WHICH YOU WILL BE OPERATING THIS EQUIPMENT. INDIGO VISION LTD. ACCEPTS NO LIABILITY FOR IMPROPER OR ILLEGAL USE OF THIS PRODUCT. Copyright COPYRIGHT © INDIGO VISION LIMITED. ALL RIGHTS RESERVED. T HIS MANUAL IS PROTECTED BY NATIONAL AND INTERNATIONAL COPYRIGHT AND OTHER LAWS . UNAUTHORIZED STORAGE , REPRODUCTION, TRANSMISSION AND/OR DISTRIBUTION OF THIS MANUAL , OR ANY PART OF IT, MAY RESULT IN CIVIL AND/OR CRIMINAL PROCEEDINGS . INDIGO V ISION IS A TRADEMARK OF I NDIGO V ISION LIMITED AND IS REGISTERED IN CERTAIN COUNTRIES . SMS4, CAMERA G ATEWAY , AND MOBILE CENTER ARE UNREGISTERED TRADEMARKS OF INDIGO VISION LIMITED. ALL OTHER PRODUCT NAMES REFERRED TO IN THIS MANUAL ARE TRADEMARKS OF THEIR RESPECTIVE OWNERS . SAVE AS OTHERWISE AGREED WITH INDIGO VISION LIMITED AND /OR INDIGO VISION , I NC., THIS MANUAL IS PROVIDED WITHOUT EXPRESS T O THE FULLEST EXTENT PERMITTED BY APPLICABLE LAWS , I NDIGO V ISION LIMITED AND INDIGO VISION , I NC. DISCLAIM ALL IMPLIED REPRESENTATIONS , WARRANTIES , CONDITIONS AND/ OR OBLIGATIONS OF EVERY KIND IN RESPECT OF THIS MANUAL . ACCORDINGLY , SAVE AS OTHERWISE AGREED WITH INDIGO V ISION L IMITED AND/OR I NDIGO VISION , INC., THIS MANUAL IS PROVIDED ON AN “ AS IS ”, “ WITH ALL FAULTS ” AND “ AS AVAILABLE ” BASIS . PLEASE CONTACT INDIGO VISION LIMITED ( EITHER BY POST OR BY E - MAIL AT PARTNER. SUPPORT@INDIGOVISION .COM ) WITH ANY SUGGESTED CORRECTIONS AND /OR IMPROVEMENTS TO THIS MANUAL . REPRESENTATION AND /OR WARRANTY OF ANY KIND . SAVE AS OTHERWISE AGREED WITH I NDIGO V ISION LIMITED AND/ OR I NDIGO VISION , I NC ., THE LIABILITY OF I NDIGO VISION LIMITED AND INDIGO VISION, INC. FOR ANY LOSS ( OTHER THAN DEATH OR PERSONAL INJURY ) ARISING AS A RESULT OF ANY NEGLIGENT ACT OR OMISSION BY I NDIGO V ISION L IMITED AND /OR I NDIGO V ISION, I NC . IN CONNECTION WITH THIS MANUAL AND /OR AS A RESULT OF ANY USE OF OR RELIANCE ON THIS MANUAL IS EXCLUDED TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAWS . Contact address IndigoVision Limited Charles Darwin House, The Edinburgh Technopole, Edinburgh, EH26 0PY 2 Installation Guide - v17 TABLE 1 2 OF CONTENTS Legal Considerations Copyright Contact address 2 2 2 About This Guide 7 System configurations IndigoVision documentation Safety notices 7 7 7 NVR-AS Installation 9 System specifications NVR-AS operating system specification Anti-virus software Step 1: Prepare your video library Recording onto a local drive Recording onto a network drive Step 2: Install the NVR-AS Upgrading the NVR-AS 3 4 9 9 10 10 10 10 10 11 Control Center front-end application Installation 13 Control Center front-end application operating system specification Audit logging Installation procedure Control Center front-end application Incident Player Site database overview Use a segmented site database Choosing the location of the site database Partner branding Windows firewall Turning off the firewall Creating firewall exceptions Unattended installation Installer properties Prerequisites Examples 13 13 13 14 18 18 19 19 20 20 20 20 20 21 21 22 Control Center Client front-end application Installation Installation procedure Control Center Client The Control Center Client site database Windows firewall Installation Guide - v17 23 23 23 24 24 3 v17 . Windows Server 2008 R2. 9000. Windows Vista Windows Server 2003 Using a remote site database in a workgroup Configuration Download and configure the Mobile Center app Deregister a device Change the Mobile Center Service url Change the port on Windows 7.Control Center Unattended installation Installer properties Prerequisites Examples 5 24 24 25 26 Camera Gateway Installation 27 Camera Gateway overview Intended use System specifications Installation procedure Prerequisites Installation 6 27 27 27 28 28 28 Mobile Center Service Installation 31 Overview System specifications Compatibility Prerequisites IIS Configuration on Windows Server 2008 R2 IIS Configuration on Windows Vista and Windows 7 IIS Configuration on Windows Server 2003 Installation procedure Windows 7. 11000 Range cameras and encoders Ports required by BX Range cameras Ports required by Ultra Range cameras Ports required by 8000 and 9000 Range receivers Ports required by alarm panels Ports required by an NVR-AS Ports required by an NVR-AS 3000 Ports required by Windows NVR-AS Ports required by Bandwidth Manager 4 37 37 39 Microsoft SQL Server Express 2008 installation fails to complete The IndigoVision Mobile Center Administration page cannot be displayed Upgrading mobile device to iOS 7 Mapped drive is not displayed when browsing for a remote site database Site database cannot be edited A 31 31 31 32 32 32 33 33 33 35 36 36 37 37 37 43 44 44 45 46 46 47 48 48 Installation Guide . and Windows Vista systems Access Mobile Center Service from a public network 7 Troubleshooting IndigoVision Firewall Requirements 39 39 40 40 40 43 Ports required by 8000. Windows Server 2008 R2. v17 48 49 49 50 50 50 53 53 53 54 55 55 55 56 56 56 56 57 57 58 59 61 61 61 61 61 63 63 5 .Control Center Ports required by Control Center front-end application Ports required by Camera Gateway Ports required by Video Stream Manager (VSM) Ports required by Mobile Center Service Ports required by Mobile Center app Video stream configuration port usage B NVR-AS Post-Installation Network Drive Configuration Creating a user account Changing the video library folder Restarting the NVR-AS C Migrating from Control Center 3 Network Video Recorders and Alarm Servers NVR-AS compatibility Migrating from Control Center 3 Upgrade to the latest NVR 3 release Upgrade to the latest Control Center 3 release Upgrade to the latest version of Control Center front-end application Upgrade to NVR-AS 4 Migrate alarm sources Re-configure binary inputs on IndigoVision devices Planning your migration of 3.x installation alarm sources Features not supported in IndigoVision Control Center Manual deletion of alarms from the alarm log Tamper alarms Assign alarms Downgrading an NVR-AS D Installing a Windows NTP server Installation and configuration Installation Guide . v17 .Control Center 6 Installation Guide . 1 ABOUT THIS GUIDE This guide details how to install all components of IndigoVision Control Center. if not avoided. please refer to the Windows NVR Specification Guide ► For information about specifying a system for Control Center. IndigoVision Control Center is a powerful and easy-to-use software solution that enables you to manage all your video surveillance operations and investigate security events quickly and effectively in one integrated platform. you can choose a system configuration to match your requirements: • The Control Center front-end application and the NVR-AS installed on the same computer — for small systems only • The Control Center front-end application installed on one or more computers and an NVR-AS installed on one or more different computers (recommended) ► For information about requirements for Windows NVR-AS. Installation Guide . damage the product. ► For a list of the new features for each Control Center release. or lead to loss of data. see the Control Center Performance Guide IndigoVision documentation IndigoVision product documentation. please refer to the Release Note available from the IndigoVision website Safety notices This guide uses the following formats for safety notices: Indicates a hazardous situation which. could result in moderate injury. System configurations When using the Windows NVR-AS application. The Control Center suite consists of a number of applications that provide a complete end-toend IP security solution. could result in death or serious injury. is available to authorized partners via the IndigoVision website. including hardware guides and configuration guides.v17 7 . Indicates a hazardous situation which. if not avoided. 1 About This Guide Control Center Indicates a hazardous situation which, if not avoided, may seriously impair operations. Additional information relating to the current section. 8 Installation Guide - v17 2 NVR-AS INSTALLATION This chapter details how to install the Windows Network Video Recorder/Alarm Server (NVR-AS). System specifications IndigoVision recommends that you install your NVR-AS on a server-style system, with a server network adaptor and server disk systems. IndigoVision strongly recommends the use of disk redundancy technology such as RAID to provide a single large partition to the NVR-AS. ► For more information about requirements for Windows NVR-AS, please refer to the Windows NVR Specification Guide NVR-AS operating system specification We recommend that you use the following guidelines for the NVR-AS PC or server operating system. Table 1: Supported Operating Systems Operating System Notice Supported Windows Server ® 2012 Y Windows Server ® 2008 R2 x64 Y (recommended) Windows® 8 Y (small systems only - up to 16 streams) Windows® 7 Y (small systems only - up to 16 streams) Other N IndigoVision recommends that you use Windows Server ® 2008 R2 x64 when using the Windows NVR-AS. If your NVR-AS is to be used to record more than 16 streams of video or process alarms from more than 100 devices, we recommend using Windows Server® 2012 or Windows Server® 2008 R2. Installation Guide - v17 9 2 NVR-AS Installation Control Center Anti-virus software It is possible to run anti-virus software on the same machine as the IndigoVision Windows NVR-AS. However, IndigoVision recommends that the VideoLibrary directory (containing .vmf recording files) should not be automatically checked while recordings are being made as this could disrupt disk performance, possibly resulting in recordings with lost frames. Scheduling of automatic scans should also be carefully planned with regard to a possible overload of the server CPU. If the virus checker overloads the CPU then the NVR-AS may again lose frames from recordings. Step 1: Prepare your video library During installation you are asked for a path to the Video Library. This is the folder where the video files are stored. Caution The NVR- AS Video Library should always be on a separate drive from the NVR-AS configuration data directory, and the NVR-AS configuration directory should always be on a local hard disk. Recording onto a local drive If you plan to store your recordings on a local drive, these should be stored on a partition with as much disk space as possible, and preferably not on the system partition. Caution IndigoVision strongly recommends the use of disk redundancy technology such as RAID to provide a single large partition to the NVR-AS. Recording onto a network drive If you plan to store NVR-AS recordings on a network drive, you must first select a temporary location on a local disk. After installation, use the NVR-AS Administrator program to specify a permanent location. ► For more information, see "NVR-AS Post-Installation Network Drive Configuration" on page 53. Step 2: Install the NVR-AS If you have a Windows ® NVR-AS licence, insert the licence dongle into the USB port of the PC or server. If you do not, you can still install the Windows® NVR-AS, however, only one video stream will be available for demonstration purposes. To install the NVR-AS: 1. Insert the licence dongle into the USB port of the PC or server. Notice 10 You can insert a licence dongle after installation. It may take several minutes for the licence to register with the software. Installation Guide - v17 Control Center 2 NVR-AS Installation 2. Specify the path to the video and configuration data.Configure the email settings to enable email actions. 5.exe file in your Windows Explorer window. 13. Notice When alarms are reaped. or use the Run option on the Windows Start menu and enter the path to the Installer. then click Next. The maximum length of a chunk is limited to four hours of footage. Installation Guide . the NVR-AS Administrator application opens. Enter the server (NVR-AS) name and location as required. Select the way you want features to be installed. • Notice If you are recording at a high bit rate.v17 11 . 10. 12. Click Finish to complete the installation.Configure the alarm management settings. Read the agreement and select the check box to accept the agreement. The NVR-AS installation begins. 9. The NVR-AS Installation wizard opens.The IndigoVision NVR-AS Set Up wizard is displayed. 11. Configure the network settings. then click Next. 4. The End-User Licence Agreement dialog opens.0). then click Next. The Custom Set-up dialog opens. then click Next. Enabling this feature will increase CPU usage. Consider the capabilities of your NVR-AS server before enabling this option. you will not be able to upgrade without inserting a valid Windows® NVR-AS licence dongle. These are the name and location that are used in Control Center applications. 3.Configure the disk space management setting. you may want to set the Maximum Chunk Size at a higher value to limit the number of recordings that the NVR-AS and Control Center have to manage. it is useful to define the IP address. then click Next. • Enable video thinning to reduce the storage requirements at the expense of full motion video.exe file on the CD ROM. then click Next. • Enable Tamper protection on recordings to verify that recordings made by the NVR have not been tampered with. Click Next. Click OK to confirm. If the NVR-AS is using IP based storage. any activations that contributed to those alarms are also reaped. Then click Install. 7. After a period. Click Next. and click Next. Insert the IndigoVision Control Center CD into the CD drive of the PC or server on which you are installing the NVR-AS application. Contact IndigoVision if you do not have a Windows® NVR-AS licence dongle. If the install screen does not open automatically. 14. 8. The NVR-AS service starts automatically. Tamper Protection has an impact on performance. Click Install for the NVR-AS component. 6. Upgrading the NVR-AS If you are upgrading an existing NVR or NVR-AS (prior to version 11.Click Finish. double-click the Installer. such as an iSCSI SAN. The IndigoVision Control Center install screen opens. v17 .2 NVR-AS Installation 12 Control Center Installation Guide . Notice Audit logging is required to use the Spot Monitor Export function. ► For information about specifying a system for Control Center. Alternatively. you can configure them at a later stage once you have logged into the Control Center front-end application. Installation Guide . refer to the Audit Log Reference Guide Installation procedure This section describes the installation procedures for the Control Center front-end application and Incident Player. refer to the "Control Center Performance Guide" Control Center front-end application operating system specification We recommend that you use the following guidelines for the Control Center front. Microsoft SQL Server®.3 CONTROL CENTER FRONT-END APPLICATION INSTALLATION This chapter describes how to install the Control Center front-end application and Incident Player application. It also explains how to configure a Windows firewall to allow correct operation of the Control Center front-end application and/or the NVR-AS. ► For information about setting up audit logging. for example.end application PC operating system. You can configure audit log settings when setting up your site database. Table 2: Supported Operating Systems Operating System Supported Windows 8® 64-bit Y Windows 7® 64-bit Y Other N Audit logging The IndigoVision Control Center provides an audit logging function that logs many common user and administrator actions in an ODBC compliant database. You must be logged in as an administrator to change the audit log settings.v17 13 . • you are installing the Control Center front-end application on only one PC. ► For more information about site databases.3 Control Center front-end application Installation Control Center An alternative variant that does not include site setup functionality. you have the option to set up your site database. When installing the Control Center front-end application. • you are installing the Control Center front-end application on an operator’s PC. see "Control Center Client front-end application Installation" on page 23 Control Center front-end application You must be logged into Windows as an administrator to install the Control Center front-end application.exe file on the CD ROM. If you wish to change the existing site database settings. or Microsoft Sync Framework 2. see "Site database overview" on page 18 Notice Your Operating System may require you to authorize this installation. Set up a site database If you cleared the Use existing site database settings check box on the Custom Setup dialog of the Control Center installer.exe file in your Windows Explorer window. Use this variant for installations that should only use the site database provided by an administrator. Go to see "Use an existing Control Center site database" on page 15 • 14 Select Create new site database if: • this is the first time you have installed the Control Center front-end application . double-click the Installer.1 Provider Services installed. ► For more information. Installation Guide . Click Install for the Control Center front-end application. You have the following options to set up a site database: • Select Use existing site database if: • you have already created a Control Center site database which you want to use. Insert the IndigoVision Control Center CD into the CD drive of the PC on which you are installing the Control Center front-end application. the Site Database Setup application opens and you must select the site database settings. If the install screen does not open automatically. Microsoft Sync Framework 2. and you want it to access a central site database.v17 . clear the Use existing site database settings check box to open the Site Database Setup application. the Control Center front-end application will notify you. 2. the Control Center Client front-end application. The IndigoVision Control Center install screen opens. you must set up the site database. 3.NET Framework 4. If you are installing Control Center front-end application on a PC for the first time. and install them for you before continuing.1 Core Components. If you are performing a fresh install of the Control Center front-end application. 1. is also available. Notice If you do not have Microsoft . or use the Run option on the Windows Start menu and enter the path to the Installer. and follow the on-screen instructions to complete the installation. this check box is unavailable. and you want it to access a central site database. Select Create a new site database and click Next.x configuration. Select if you want to create a Segmented or Unsegmented database. Select Specify a backup site database and browse to the folder where the database is located. Your system is not fully operational and does not log alarms until the migration is complete. Click Next. Go to see "Import an existing Control Center 3 site database" on page 17 ► For more information about migrating to IndigoVision Control Center. If you have selected to create a segmented site database. The Finish dialog opens. 4. 2. and alarms generated in 3. 5. The backup site database is used if the requested site database is unavailable. 1.x are not compatible with later versions. migrating from 3. Create a new site database Follow this procedure if this is the first time you have installed the Control Center front-end application. Installation Guide . ensure you read the migration section and develop a comprehensive migration strategy. 5. Therefore. please refer to see "Migrating from Control Center 3" on page 55 Caution The IndigoVision Control Center alarm management configuration is significantly different to the 3. Go to see "Modify the current site database" on page 16 • Select Import an existing Control Center 3 site database if: • you are upgrading from Control Center 3 and wish to create a Control Center compatible site database from your Control Center 3 site database. 1. see "Site database overview" on page 18 4. 3. You can add or remove segments at a later stage. 3. or you are installing the Control Center front-end application on only one PC. To mitigate risks.v17 15 . if required. Click Finish to complete the site database setup. Select Use an existing site database and click Next. Specify a backup site database. The Administrator Details dialog opens.Control Center 3 Control Center front-end application Installation Go to see "Create a new site database" on page 15 • Select Modify current site database if: • you are already using a Control Center site database which you want to modify.x installations is complex. A segmented site database stores information for each sub-site in separate segments of the site database. 2. Click Browse and navigate to where you want to save the database. 6. Use an existing Control Center site database Follow this procedure if you have already created a Control Center site database which you want to use. if required. ► For more information about site database types. specify the number of segments you would like to create. Click Browse and navigate to the folder where the site database is located. Click Next. or you are installing the Control Center front-end application on an operator’s PC. Select the authentication method used to authenticate the administrator. C lick Next. either enter a Windows account or click Browse and select the required account. the Control Center front-end application checks that the current Windows user is the same as the Windows user linked to the administrator account. you may need to select Compatibility Mode. The Software Upgrade Plan dialog opens. refer to the Audit Log Reference Guide Notice • Depending on the database you have selected. Check Enable audit log to allow Control Center to log user actions to a database. enter a username and password. and select the required option from the drop-down list. Click Finish to complete the site database setup. select Use password authentication. Enter a password. follow the connection setup instructions provided by the driver. You set up individual user accounts once you log into the Control Center front-end application. select Yes and enter your SUP contract number.14 alphanumeric characters. Select Modify current site database and click Next. Modify the current site database You can modify a Control Center site database at any time using the Site Database Setup application. 7. If you have a Software Upgrade Plan (SUP). select No. see the Audit Log Reference Guide. This must contain between 8 . • To use password authentication. Click Next. and confirm it. Specify the modifications required: • 16 Select Upgrade PTZ protocols to upgrade to the latest protocols installed with Control Center. The Finish dialog opens. Click Next. Notice If you have chosen to enable audit logging. The Configure Audit Log dialog opens 8.3 Control Center front-end application Installation Notice Control Center • To use Windows authentication. If not. The current site database folder is specified on the top of this dialog. The administrator must enter this password each time they log in to the Control Center front-end application.v17 . Otherwise. The username and password must be identical to those you set up when you configured the database. an error message is displayed and the administrator is not logged on. When the administrator tries to log in. from the Start menu select Programs>IndigoVision>Control Center 11 >Site Database Setup. 2. ► For more information about audit logs. 1. 9. Installation Guide . You may be prompted to enter the username and password again. • If you are using ODBC password authentication to access the database. To open the Site Database Setup application outside of the installation process. For more information about setting up an audit log. Select Import an existing Control Center 3 site databaseand click Next. To mitigate risks. select No. Otherwise. If you have a new Software Upgrade Plan (SUP). Click Finish to complete the site database setup. 4. 1. 5.v17 17 . select Yes and enter your SUP contract number. or would like to modify the existing one. Select an option and click Next. ensure you read the migration section and develop a comprehensive migration strategy. • Select Reuse audit log from imported site database to use the audit log from the imported site database. do not select this option. • Select to Add segments or Delete a segment and specify the number of segments to add or the segment to delete. Select Upgrade PTZ protocols to upgrade to the latest protocols installed with Control Center. The Software Upgrade Plan dialog opens. • Select Configure new audit log to create a new audit log for this site database. 3.x installations is complex. migrating from 3. 3. see "Migrating from Control Center 3" on page 55 Caution The IndigoVision Control Center alarm management configuration is significantly different to the 3. • Select No audit log if you do not want to log actions. select No. and specify where you want to save the new Control Center site database. Caution If you have customized your PTZ protocols. 4.x configuration. Your system is not fully operational and does not log alarms until the migration is complete. The Software Upgrade Plan dialog opens. Click Next. The Configure Audit Log dialog opens. Click Next. ► For more information about audit logs. 2. Therefore. Use the Browse buttons to specify where the existing Control Center 3 site database is located. Click Next. ► For more information about migrating to the latest IndigoVision Control Center. as your changes will be lost. If you have a Software Upgrade Plan (SUP). as your changes will be lost. Import an existing Control Center 3 site database Follow this procedure if you are upgrading from Control Center 3 and wish to create a site database compatible with later versions of Control Center from your existing Control Center 3 site database. select Yes and enter your SUP contract number. The Finish dialog opens. and alarms generated in 3.Control Center Caution 3 Control Center front-end application Installation If you have customized your PTZ protocols. do not select this option. Click Next. Otherwise.x are not compatible with later versions. refer to the Audit Log Reference Guide Installation Guide . or use the Run option on the Windows Start menu and enter the path to the Installer. enter a username and password.v17 . Insert the IndigoVision Control Center CD into the CD drive of the PC on which you are installing Incident Player. The username and password must be identical to those you set up when you configured the database.3 Control Center front-end application Installation Notice Control Center • Depending on the database you have selected. 6.) For more information on setting up an audit log. or centrally on a Windows file server.all site information is stored in a single database. but you can change this at any time using the Site Database Setup application. see "Use a segmented site database" on page 19 For either option. from the Start menu select Programs>IndigoVision>Control Center 11 >Site Database Setup. (You may be prompted to enter the username and password again. see the Audit Log Reference Guide.exe file on the CD ROM. This option is suited to large sites with multiple administrators who are responsible for different sub-sites. you may need to select Compatibility Mode. There are two configuration options for the site database: • Unsegmented Site Database . To open the Site Database Setup application outside of the installation process. follow the connection setup instructions provided by the driver. double-click the Installer. Notice If you have chosen to enable audit logging. see "Choosing the location of the site database" on page 19 18 Installation Guide . If the install screen does not open automatically. ► For more information. • If you are using ODBC password authentication to access the database. You can enter site database information during installation. Click Install for the Incident Player component. the site database can be stored locally on the PC running the Control Center front-end application. • Segmented Site Database . ► For more information. If you have installed Control Center front-end application on several PCs you should use a central site database. Click Finish to complete the site database setup. 2.information for each sub-site is stored in separate segments of the site databases (max. This option is suited to smaller sites. Incident Player The Incident Player application can be used to view incidents you have exported using the Control Center front-end application. 1. Site database overview The Control Center site database stores the site configuration information. and follow the on-screen instructions to complete the installation.exe file in your Windows Explorer window. The IndigoVision Control Center install screen opens. 250). cameras. remote facilities a segmented site database enables each facility to operate independently while providing central oversight. Operators and administrators can view and manage individual segments.v17 19 . such as user accounts. Installation Guide . If you have installed the Control Center front-end application on only one PC you should use a local site database. apply to all segments. • Multiple administrators For installations where areas are managed independently by different administrators. Use a segmented site database A segmented Control Center site database stores information for each site directly under the top site in separate segments of the database.the site database is stored on an individual PC. If you have installed the Control Center front-end application on several PCs you should use a central site database. You should use a segmented site database in the following scenarios: • Large site with many devices (for example. or choose to view all segments for an overview of the whole site. a segmented site database enables the site to be organized into independent segments.the site database is stored on a Windows file server and users access the data across the network. When you use a central site database. • Central . Each segment can be administered independently. the site database can be stored in one of the following options: Notice • a PC where the Control Center front-end application is installed • a Windows file server Ensure that the folder you select for the site database is accessible by all PCs running the Control Center front-end application. Full administrators can grant users access to individual segments. Site wide information. detectors etc. Notice Ensure that the folder you select for the site database is accessible by all PCs running the Control Center front-end application.Control Center Notice 3 Control Center front-end application Installation Only one Control Center front-end application instance should write to the site database or a site database segment at any one time. Choosing the location of the site database There are two ways to use the site database: • Local .) Sites with many thousands of cameras and alarms will benefit from a segmented site database with improved performance and easier management of devices. improving performance and simplifying management. • Multiple facilities requiring central oversight When monitoring multiple. and save it in the folder where the Control Center front-end application is installed. enter the text you want to appear in title bar. Turning off the firewall Turning off the firewall completely leaves your computer unprotected against outside attack. and company name appears in the title bar of the Control Center front-end application. IndigoVision provides a . or • create firewall exceptions. Open a DOS prompt and navigate to the Control Center front-end application installation directory. Windows firewall Firewall protection is automatically enabled on PCs running Windows Vista® . ► IndigoVision port numbers are listed in see "IndigoVision Firewall Requirements" on page 43 Unattended installation Unattended installation enables system administrators to install the front-end applications using group policies. Notice The dimensions of the partnerlogo. This enables system administrators to automate installation to ensure 20 Installation Guide . 1. see the Windows help system.bmp and a . this should not be an issue as long as your network is protected by other means. Edit the partnerlogo. 3. If you have installed a Control Center front-end application on either of these operating systems. otherwise the image may not scale correctly. you can: • turn off the firewall.txt file for you to edit with your company details. Enter the following at the prompt: ccbrand. the firewall may prevent correct operation of the application and/or the NVR-AS.txt file. you can create firewall exceptions for a Control Center front-end application and the NVR-AS service.bmp image must be identical to the Control Center logo on the login page (390 x 65 pixels). or Windows® 7.v17 . Creating firewall exceptions Alternatively. However. navigate to Resources\Partner Branding.bmp file with the image you want to appear in the login screen.exe 4. On the IndigoVision Control Center CD. and save it in the folder where the Control Center front-end application is installed. For more information about creating exceptions. In the partnertext.3 Control Center front-end application Installation Control Center Partner branding You can customize the Control Center front-end application to include your company’s name and logo. To ensure these applications work as expected. 2. Open the Control Center front-end application to check the image is correctly displayed on the login dialog and the text is correctly displayed in the title bar. Your company logo appears on the login screen. Control Center 3 Control Center front-end application Installation the correct version of the Control Center front-end application or Control Center Client frontend application is available to users. • Add a string value called SiteDbPath. • Control Center site database location • This is stored in the registry: 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\IndigoVision\Control Center Client 4. The following sections provide the information a system administrator requires to implement unattended installation within your organization's environment.1 provider services • ProviderServices-v2. Microsoft Sync Framework 2.v17 21 .1-x86-ENU. An example Microsoft Windows Installer Transform file (. Installer properties To perform an unattended installation of the front-end applications. Table 3: New Control Center installation Prerequisite Required Control Center site database location Yes Microsoft . Microsoft Sync Framework 2.msi • Available on the Control Center CD in the Control Center folder.1 provider services Yes Installation Guide .mst) with these settings is available in the Resources folder on the IndigoVision Control Center CD under Unattended Installation.exe • Available on the Control Center CD in the Control Center folder.NET Framework 4 Client Profile • dotNetFx40_Client_x86_x64.1 core components Yes Microsoft Sync Framework 2.1-x86-ENU. the installer properties USEEXISTINGSITEDBSETTINGS and FINALRELEASE must be set to 1. some prerequisites may have been previously installed.msi • Available on the Control Center CD in the Control Center folder.NET Framework 4 Client Profile Yes Microsoft Sync Framework 2. depending on the version. This contains the database location. • • • Microsoft .1 core components • Synchronization-v2. Prerequisites The installers for the front. The following tables illustrate which prerequisites are required for each scenario. C:\IndigoSiteDb. The prerequisites required depend on whether this is the first time the front-end application has been installed on this PC or whether it is being upgraded. If the front-end application has already been installed on the PC. The following applications and registry settings are prerequisites for the Control Center frontend applications installation.end applications have several prerequisites for the target PC before running the front-end application installer. for example. NET Framework 4 Client Profile Yes Microsoft Sync Framework 2.1 provider services Yes Table 5: Upgrading from Control Center 4.1 core components No Microsoft Sync Framework 2. They are editable in a text editor such as Notepad. installed on the PC. Table 4: Upgrading from Control Center 4.3 Prerequisite Required Control Center site database location No Microsoft .3 Control Center front-end application Installation Notice Control Center These prerequisites apply even if Control Center 3 is. 22 Installation Guide .1 core components Yes Microsoft Sync Framework 2.1 provider services Yes Table 6: Upgrading from Control Center 4.4 Prerequisite Required Control Center site database location No Microsoft . The scripts are available in the Resources folder on the Control Center CD under Unattended Installation. or has been.1 provider services No Examples Examples of registry scripts are available on the Control Center CD. The scripts are an example of how to set the site database path in the registry to C:\IndigoSiteDB.2 or 4.NET Framework 4 Client Profile Yes Microsoft Sync Framework 2.v17 .1 core components Yes Microsoft Sync Framework 2.NET Framework 4 Client Profile No Microsoft Sync Framework 2.mst) with the required settings is available in the Resources folder on the Control Center CD under Unattended Installation.1 or earlier Prerequisite Required Control Center site database location No Microsoft . An example Microsoft Windows Installer Transform file (. 1 Provider Services installed.exe file on the CD ROM. Control Center Client will notify you. double-click the Installer. After installing Control Center Client. 2. you can copy the contents of the ControlCenterClient folder on to a CD. To install Control Center Client: 1. 3.1 Core Components. or use the Run option on the Windows Start menu and enter the path to the Installer. see "The Control Center Client site database" on page 24. The IndigoVision Control Center install screen opens. For information about system specifications.NET Framework 4. the Site Database Setup application opens. Installation Guide . Installation procedure Control Center Client is available on the IndigoVision Control Center CD. Insert the IndigoVision Control Center CD or Control Center Client CD into the CD drive of the PC on which you are installing Control Center Client. and install them for you before continuing. Click Browse to select the folder where the database is located. For information on site databases. see the "Control Center Performance Guide".exe file in your Windows Explorer window. Microsoft Sync Framework 2. Notice If you do not have Microsoft . Notice Your Operating System may require you to authorize this installation. or Microsoft Sync Framework 2. and select Upgrade PTZ protocols to upgrade to the latest protocols installed with Control Center. Click Install for the Control Center Client front-end application.v17 23 . and follow the onscreen instructions to complete the installation. Control Center Client You must be logged into Windows as an administrator to install Control Center Client. It also explains how to configure a Windows firewall to allow correct operation of Control Center Client. If the install screen does not open automatically. If you need to distribute Control Center Client.4 CONTROL CENTER CLIENT FRONT-END APPLICATION INSTALLATION This chapter describes how to install the Control Center Client front-end application. the installer properties USEEXISTINGSITEDBSETTINGS and FINALRELEASE must be set to 1. or Windows® 7. 6. The following sections provide the information a system administrator requires to implement unattended installation within your organization's environment. Otherwise. 5.v17 . Click Next. If you have installed a Control Center front-end application on either of these operating systems. or • create firewall exceptions. The Back up Site Database Details opens. If you have a Software Upgrade Plan (SUP). Click Next. but you can change this at any time.4 Control Center Client front-end application Installation Caution Control Center If you have customized your PTZ protocols. you can: • turn off the firewall. To ensure these applications work as expected. Installer properties To perform an unattended installation of the front-end applications.) During installation you are asked to use an existing site database. then click Finish to complete the installation. then click Browse to select the site database.mst) with these settings is available in the Resources folder on the IndigoVision Control Center CD under Unattended Installation. select Yes and enter your SUP contract number. An example Microsoft Windows Installer Transform file (. 24 Installation Guide . Click Next. The Software Upgrade Plan dialog opens. do not select this option. select Programs> IndigoVision> Control Center Client>Site Database Setup. Specify a backup site database. Unattended installation Unattended installation enables system administrators to install the front-end applications using group policies. as your changes will be lost. 4. Windows firewall Firewall protection is automatically enabled on PCs running Windows Vista® . the firewall may prevent correct operation of the application and/or the NVR-AS. Select Specify a backup Site Database. You can enter site database information during installation. The backup site database is used if the requested site database is unavailable. This enables system administrators to automate installation to ensure the correct version of the Control Center front-end application or Control Center Client frontend application is available to users. select No. The Control Center Client site database The Control Center site database stores the site configuration information. if required. (From the Start menu. end applications have several prerequisites for the target PC before running the front-end application installer.1 provider services • ProviderServices-v2.msi • Available on the Control Center CD in the Control Center folder.1 or earlier Prerequisite Required Control Center site database location No Microsoft .msi • Available on the Control Center CD in the Control Center folder.v17 25 .exe • Available on the Control Center CD in the Control Center folder. • Control Center site database location • This is stored in the registry: 64-bit Windows: HKLM\SOFTWARE\Wow6432Node\IndigoVision\Control Center Client 4.1 core components Yes Microsoft Sync Framework 2. or has been. The following tables illustrate which prerequisites are required for each scenario.1-x86-ENU. Microsoft Sync Framework 2. The following applications and registry settings are prerequisites for the Control Center frontend applications installation. for example.1 core components Yes Microsoft Sync Framework 2. • • • Microsoft . This contains the database location.NET Framework 4 Client Profile • dotNetFx40_Client_x86_x64. installed on the PC. Table 7: New Control Center installation Prerequisite Notice Required Control Center site database location Yes Microsoft . Table 8: Upgrading from Control Center 4.1 core components • Synchronization-v2.NET Framework 4 Client Profile Yes Microsoft Sync Framework 2. depending on the version. Microsoft Sync Framework 2.1-x86-ENU. some prerequisites may have been previously installed.1 provider services Yes Installation Guide .1 provider services Yes These prerequisites apply even if Control Center 3 is. The prerequisites required depend on whether this is the first time the front-end application has been installed on this PC or whether it is being upgraded.Control Center 4 Control Center Client front-end application Installation Prerequisites The installers for the front. C:\IndigoSiteDb. If the front-end application has already been installed on the PC.NET Framework 4 Client Profile Yes Microsoft Sync Framework 2. • Add a string value called SiteDbPath. NET Framework 4 Client Profile No Microsoft Sync Framework 2.1 core components No Microsoft Sync Framework 2.1 provider services No Examples Examples of registry scripts are available on the Control Center CD.4 Prerequisite Required Control Center site database location No Microsoft . An example Microsoft Windows Installer Transform file (. The scripts are an example of how to set the site database path in the registry to C:\IndigoSiteDB.2 or 4.4 Control Center Client front-end application Installation Table 9: Control Center Upgrading from Control Center 4. They are editable in a text editor such as Notepad. 26 Installation Guide .1 provider services Yes Table 10: Upgrading from Control Center 4.v17 .NET Framework 4 Client Profile Yes Microsoft Sync Framework 2.mst) with the required settings is available in the Resources folder on the Control Center CD under Unattended Installation.1 core components Yes Microsoft Sync Framework 2.3 Prerequisite Required Control Center site database location No Microsoft . The scripts are available in the Resources folder on the Control Center CD under Unattended Installation. giving customers a wide choice of cameras to choose from. If. the Camera Gateway allows you to do so without having to change the cameras. and the following minimum requirements: • Server class PC • Current generation Intel Xeon processor 3. The Camera Gateway service enables multiple clients to stream video from the same camera. you want to use Control Center to view a location in which third party cameras are already installed. with a server network adaptor. The cameras do not need to support ONVIF in order to connect to the IndigoVision system. The Camera Gateway supports video streams from H.5 CAMERA GATEWAY INSTALLATION This chapter details how to install the Camera Gateway. giving total flexibility. Camera Gateway overview The IndigoVision Camera Gateway enables third party cameras from a range of manufacturers to be connected to IndigoVision Control Center. The Camera Gateway takes video streams from third party cameras using their native protocols and enables users to view the streams in a Control Center front-end application and record them using NVRs.4 cameras. The Camera Gateway is a software service that can be installed on a Windows server. and events. Intended use The Camera Gateway enables third party cameras from a range of manufacturers to be connected to IndigoVision Control Center. System specifications The IndigoVision Camera Gateway can be installed on one of the following Windows operating systems: • MS Windows 7 (32 bit) • MS Windows 7 (64 bit) • MS Windows Server 2008 R2 For systems with more than 16 streams it is recommended to use Windows Server 2008 R2. IndigoVision recommends that you install Camera Gateway on a server-style system. for example.264 and MPEG. PTZ control.10 Ghz • 4GB RAM Installation Guide .v17 27 . whilst only requiring a single stream from the camera to the Camera Gateway. The Camera Gateway Server installation wizard opens. For more information. for demonstration purposes only. or use the Run option on the Windows Start menu and enter the path to the setup. Prerequisites The following prerequisites are required to install and use the Camera Gateway. Select Camera Gateway.NET Framework 4 is not installed. click Start > Administrative Tools > Server Manager > Roles. Follow the on-screen instructions. • Select Use Offline Activation to install the Camera Gateway on a PC without internet access.NET Framework 3.5. • In Windows 7. 4. Verify that the Application Server role is installed. Insert the Control Center CD into the CD drive of the PC or server on which you are installing the Camera Gateway application. before installing the three components of the Camera Gateway. • A valid licence key for the Camera Gateway. and Microsoft SQL Server 2008 Express Edition. click Start > Control Panel > Programs > Turn Windows features on or off. Installation Guide . 2. You may need to restart your computer. The installer then presents the necessary files to allow you to register the Camera Gateway installation on a PC with internet access. Restart the computer. you will be prompted to install it. you can still install the Camera Gateway. If Microsoft SQL Server 2008 Express Edition is not installed. then open the Control Center CD and select Camera Gateway. see "Microsoft SQL Server Express 2008 installation fails to complete " on page 39 3.NET framework is enabled. 28 • Select Use Demo licence to install the Camera Gateway without entering a licence key. If the install screen does not open automatically. 5. During the installation process you will be prompted to select one of the following licence options. however. Installation 1. The demo licence enables four streams for 30 days. Follow the on-screen instructions.1 is selected. navigate to English/CameraGateway and double-click the setup. Verify that Microsoft . you will be prompted to install it.5 Camera Gateway Installation Control Center Installation procedure The Camera Gateway installer first checks the system for the prerequisite components: Microsoft . only four video streams will be available for 30 days after installation for demonstration purposes. The Control Center install screen opens. The installer then installs each prerequisite component required. If you do not have a licence key. If Microsoft .NET Framework 4.exe file on the CD ROM. • In Windows Server.v17 . you must manually remove the components.exe file in your Windows Explorer window. If the Microsoft SQL Server 2008 installation fails to complete. • Microsoft . Follow the on-screen instructions. Control Center 5 Camera Gateway Installation • Select Enter licence Key if you have a Camera Gateway licence key. Once the Camera Gateway Administrator has successfully installed. click Finish. click Finish. click Finish. Once the Camera Gateway Server has successfully installed. Type the licence key and click Check licence to authenticate the license. The Camera Gateway Interface installation wizard opens. Once the Camera Gateway Interface has successfully installed. Installation Guide . 7. 6.v17 29 . Follow the on-screen instructions. 8. Follow the on-screen instructions. The Camera Gateway Administrator installation wizard opens. 5 Camera Gateway Installation 30 Control Center Installation Guide .v17 . System specifications We recommend that you use the following guidelines for the Mobile Center Service PC or server operating system.v17 31 .and Windows Server 2008 R2: IIS 7. To use Mobile Center on a mobile device.0 or later Mobile Center iOS app v1. This enables you to access and control cameras in your site database on the move. The Mobile Center Service provides the interface between the site database and the Mobile Center app installed on the mobile device. you must install the Mobile Center Service on a PC or server.6 MOBILE CENTER SERVICE INSTALLATION This chapter details how to install the Mobile Center Service. video is streamed directly from the camera maintaining IndigoVision's robust.0 or later • Windows Vista. Windows 7. Overview The Mobile Center Service enables you to view video streams from cameras in an IndigoVision Control Center site using a mobile device. distributed architecture.5 or later Installation Guide . and install the Mobile Center app on a suitable mobile device. Table 11: Supported Operating Systems Operating System Supported Windows Server ® 2008 R2 x64 Y (recommended) Windows Server ® 2003 Y Windows® 7 Y (recommended) Windows Vista® Y Windows® XP Professional N Compatibility Mobile Center Service is compatible with the following applications: • IndigoVision Control Center 4 or later • Windows Server 2003: IIS 6.5 or later is compatible with the following applications: • iOS 6 or later • Mobile Center Service v1. However. This will be installed as part of the installation process if it is not already available. The following sections provide information about configuring IIS. • Internet Information Services (IIS) installed and correctly configured. • IndigoVision Control Center installation • A valid licence key for the Mobile Center Service.6 Mobile Center Service Installation Control Center Prerequisites The following prerequisites are required to install and use the Mobile Center Service.5.0. • Microsoft .microsoft. you can still install the Mobile Center Service. The configuration depends on the operating system. please refer to the Microsoft support site (http://support.v17 . you will only be able to register one mobile device for 30 days after installation.NET Framework 4. IIS Configuration on Windows Server 2008 R2 Navigate to Control Panel > Programs and Features > Turn Windows Features On or Off > Roles > Add Role and follow the wizard to ensure the following IIS features are installed and enabled: • Web Server (IIS) • Web Server > Application Development • • • • ASP . If you do not have a licence key.NET • NET extensibility • ISAPI Extensions • ISAPI Filters Web Server > Common HTTP Features • Static Content • Default Document Web Server > Security • Basic Authentication • Request Filtering Management Tools • IIS Management Console Navigate to: Control Panel > Programs and Features > Turn Windows Features On and Off > Features > Add Feature and follow the wizard to ensure the following features are installed and enabled: • .NET Framework 3.1 IIS Configuration on Windows Vista and Windows 7 Navigate to: Control Panel > Programs and Features > Turn Windows Features On or Off > Internet Information Services and ensure the following IIS features are installed and enabled: • Web Management Tools • • 32 IIS Management Console World Wide Web Services > Application Development Features Installation Guide . however. For additional information.com). for demonstration purposes. Windows Vista To install the Mobile Center Service on a PC or server running Windows 7. Assign the SSL certificate Installation Guide . For security reasons it is recommended that you create your own or purchase a certificate from a trusted certificate authority. Windows 7.NET • ISAPI Extensions • ISAPI Filters World Wide Web Services > Common HTTP Features • Default Document • Static Content World Wide Web Services > Security • Basic Authentication • Request Filtering IIS Configuration on Windows Server 2003 Navigate to: Control Panel > Add or Remove Programs > Add/Remove Windows Components > Application Server and ensure the following sub-components are installed and enabled: • Application Server Console • Enable network COM+ access • Internet Information Services (IIS) • Common Files • Internet Information Services Manager • World Wide Web Service Installation procedure The installation procedure for Mobile Center Service depends on the operating system of the PC or server. Install the Mobile Center Service 2. Windows Server 2008 R2. Import the SSL certificate 3. complete the following steps: 1.year certificate. This is a 10.v17 33 . The installation procedure comprises the following steps: • Install an SSL certificate • Insert a valid licence dongle • Install the Mobile Center Service An SSL certificate is required for a secure connection between the Mobile Center app and the Mobile Center Service.Control Center • • 6 Mobile Center Service Installation • NET extensibility • ASP . Windows Server 2008 R2. This section provides details for installing Mobile Center on supported operating systems. ensure you check the expiration date before use. or Windows Vista. An example SSL certificate is provided on the Control Center CD in the Mobile Center Service folder. • If you are using a remote site database. Notice The first time you install Mobile Center Service.exe file in your Windows Explorer window. the user account that you are logged in with must have access to the location of site database.exe file on the CD ROM. and follow the on-screen instructions to complete the installation. Click Start > Control Panel > Administrative Tools > Internet Information Services. Insert the IndigoVision Control Center CD into the CD drive of the PC or server on which you are installing Mobile Center Service. During installation. however. 4. 2. you will only be able to register one mobile device for 30 days after installation. ► For more information. click Cancel to complete the installation. or use the Run option on the Windows Start menu and enter the path to the Installer. your browser will not be able to display the Mobile Center Administration page until you have imported and assigned the SSL certificate. If the install screen does not open automatically. you can still install the Mobile Center Service. • If you do not want to set up the site database at this time. 34 Installation Guide . and click Open. 3. and click OK. see "Using a remote site database in a workgroup" on page 36 To select a remote site database.. double-click the Installer. Type the password in the Password field. Click Install for the Mobile Center Service component. for demonstration purposes. 3. On the Actions pane.. If you do not. After the installation has been completed. 2. enter the user name and password Mobile Center Service will use to access the directory where the site database is located. Import the SSL certificate 1. navigate to the certificate file. click Import. Browse to the location of the site database. the Mobile Center Service Administration page opens in your default web browser. Select the server instance. The IndigoVision Control Center install screen opens. Click . insert the licence dongle into the USB port of the PC or server.6 Mobile Center Service Installation Control Center Install the Mobile Center Service 1. You can select the site database at any time. Once you have completed the subsequent installation steps. If you have a licence key for the Mobile Center Service. refresh your browser page to view the Mobile Center Administration page. the Mobile Center Service Site Database tool opens. and double-click Server Certificates in Features View.v17 . 4. Access the Mobile Center Site Database Setup tool from Start > IndigoVision > Mobile Center Service > Mobile Center Site Database Setup. 5.. Click Start > Control Panel > Administrative Tools > Internet Information Services. Windows Server 2003 To install the Mobile Center Service on a PC or server running Windows Server 2003. 4. Click Open. and click Next. Select the binding created by the Mobile Center Service. and select Properties. The IndigoVision Control Center install screen opens. Type 49200 in the SSL Port field. double-click the Installer. you can still install the Mobile Center Service. Type the password in the Password field. 3. and select Bindings..exe file in your Windows Explorer window. Click Install for the Mobile Center Service component. and click Next..pfx file. Click Start > Control Panel > Administrative Tools > Internet Information Services. 8. and click Next. 3. 6. The password is provided by the creator of the SSL certificate. If the install screen does not open automatically. 5. and navigate to the certificate file.. and follow the on-screen instructions to complete the installation. 2. otherwise you will not be able to assign the certificate. The password is provided by the creator of the SSL certificate. Select the Mobile Center Service certificate from the SSL certificate drop-down.v17 35 . Select the Directory Security tab. Install the Mobile Center Service Import the SSL certificate 1. Install the Mobile Center Service 1. Click Browse. Select the IVMobileCenterService web site. or use the Run option on the Windows Start menu and enter the path to the Installer. insert the licence dongle into the USB port of the PC or server. however. and click Next. 3. 7. 4..exe file on the CD ROM. and click OK. If you do not. for demonstration purposes. Import the SSL certificate 2. and click Edit. on the Actions pane. 2. complete the following steps: 1. Click Finish. If you have a licence key for the Mobile Center Service. 9.. Insert the IndigoVision Control Center CD into the CD drive of the PC or server on which you are installing Mobile Center Service. Right-click Default Web Site. 2. and click Server Certificate. Assign the certificate 1. you will only be able to register one mobile device for 30 days after installation.Control Center 6 Mobile Center Service Installation Note: Ensure Allow this certificate to be exported is selected. Select Import a certificate from a . Installation Guide . • Group membership: Restricted user • Groups: Windows 7 and Server 2008 R2 . 4.v17 . navigate to your Mobile Center Service url. Use this user name and password when selecting a site database in the Mobile Center Site Database Setup tool. 1. The default url is: https://<Server IP>:49200/mobilecenterservice . there may be a problem with your installation. After the installation has been completed. click Cancel to complete the installation. • If you do not want to set up the site database at this time. Using a remote site database in a workgroup When the remote site database used for a Mobile Center Service installation is accessed over a Workgroup. You can select the site database at any time. see "The IndigoVision Mobile Center Administration page cannot be displayed" on page 39 36 Installation Guide . Access the Mobile Center Site Database Setup tool from Start > IndigoVision > Mobile Center Service > Mobile Center Site Database Setup. • If you are using a remote site database. Ensure this user account has Read access to the directory where the site database is located.IIS_USRS 2.6 Mobile Center Service Installation Control Center 4. see "Installation procedure" on page 33 Configuration The IndigoVision Mobile Center Administration page allows you to view all registered mobile devices. To view the configuration page. Create a user account on the PC or server where Mobile Center Service will be installed. ► For more information. see "Using a remote site database in a workgroup" on page 36 To select a remote site database. the user account that you are logged in with must have access to the location of site database. ► For more information. ► For more information about changing the url. where <Server IP> represents the IP address of the server. Setup a user account on the PC or server where the site database is located. 3. you need to ensure the site database is accessible to the service. the Mobile Center Service Administration page opens in your default web browser. ► For more information . Use your Control Center administrator username and password to access the administration page. Use the same user name and password as the user account created in step 1. During installation. enter the user name and password Mobile Center Service will use to access the directory where the site database is located. see "Change the Mobile Center Service url" on page 37 If you cannot view the IndigoVision Mobile Center Administration page. the Mobile Center Service Site Database tool opens. Browse to the location of the site database. Change the port on Windows 7. and Windows Vista systems 1. 2. Mobile Center users can register their device again after it has been removed. Installation Guide . To log on. Type the new port for the Mobile Center Service in the Port field. you can configure the Mobile Center Service installation in the following ways: • Set up VPN access to the network on which the Mobile Center Service and cameras are available. and click OK. • Click Remove to deregister the device. and select Bindings. You can change the default port number and path using IIS Manager.. ► For more information about using the app. see the Mobile Center app help. Windows Server 2008 R2. Access Mobile Center Service from a public network To access Mobile Center Service from a public network. 3. Change the Mobile Center Service url The Mobile Center Service is assigned the following url by default: • https://<Server IP>:49200/mobilecenterservice <Server IP> represents the IP address of the server. • Click Block Device to deregister the device. Deregister a device You can block a device from accessing the Mobile Center Service by deregistering it on the IndigoVision Mobile Center Administration page. ► For more information about accessing the IndigoVision Mobile Center Administration page. Select the binding created by the Mobile Center Service. on the Actions pane. use your Control Center username and password. Click Start > Control Panel > Administrative Tools > Internet Information Services.v17 37 . To use the Mobile Center app. 4. and block it from connecting to the Mobile Center Service. Select the IVMobileCenterService web site. you must first register the device with Mobile Center Service. The procedure depends on the operating system of the PC or server that Mobile Center Service is installed on. and remove it from the list of devices.Control Center 6 Mobile Center Service Installation Download and configure the Mobile Center app The Mobile Center app is available from the app store for your device. see "Configuration" on page 36 Notice This functionality is only available if you have full administrator permissions. Use the Mobile Center Service URL provided by your administrator. and click Edit.. Installation Guide .6 Mobile Center Service Installation Control Center This is the recommended option. • Notice 38 Provide a public IP address behind a Network Address Translation (NAT) firewall for the Mobile Center Service server as well as all the cameras you need to view. Cameras from the BX Range do not support Network Address Translation (NAT).v17 . this may indicate that: • Another application or web page is using the same port number.50727 • ASP . see "Access Mobile Center Service from a public network" on page 37 Installation Guide . you are accessing a private network from the public network.v17 39 . the Mobile Center Administration page will not be displayed until the SSL certificate has been imported and assigned. • Your device does not have access to the network on which the Mobile Center Service is installed. the following web service extensions may be prohibited. ► For more information.NET v2. you must remove the following components using Control Panel > Programs and Features before reinstalling.7 TROUBLESHOOTING This chapter provides troubleshooting information for the installation of Control Center applications. • Microsoft SQL Server 2008 • Microsoft SQL Server Native Client • Microsoft SQL Server Setup Support Files • Microsoft SQL Server VSS Writer • Microsoft SQL Server 2008 Browser The IndigoVision Mobile Center Administration page cannot be displayed If the IndigoVison Mobile Center Administration page cannot be displayed when you use the provided URL. For example. Use the IIS Manager to allow these extension. Microsoft SQL Server Express 2008 installation fails to complete If the Microsoft SQL Server Express 2008 installation fails to complete.0. ► For more information. • ASP . see "Change the Mobile Center Service url" on page 37 • For Windows Server 2003.NET v4.0.30319 • The first time Mobile Center Service is installed on Windows 2008 R2. Use the IIS Manager to change the port number that Mobile Center Service uses. you can disable Enhanced Database Protection for the site database. Read Extended Attributes. Start > Accessories > Command Prompt > Run as administrator net use [mapped drive letter:] [mapped drive path] You will need to repeat this operation each time you reboot the system. due to corporate IT policies. and Change Permissions • If you cannot change the file permissions for mapped drives. Mapped drive is not displayed when browsing for a remote site database When using Mobile Center Site Database Setup on Windows 7.v17 . This increases the risk of data loss or corruption during extreme circumstance such as a power outage or network failure while editing the site database. • Map the network drive from an elevated command window. Installation Guide .5. • Ensure the administrator has the following file permissions to edit the site database: Windows Share Permissions: Full Control (to enable control by the NTFS Security permissions) NTFS Security Permissions: Synchronize. After your device has been de-registered. Read Attributes. Disabling Enhanced Database Protection requires Control Center to use alternative Windows APIs. a mapped network drive may not be displayed when browsing for a remote site database. your administrator must de-register your device before you can use the Mobile Center app. Write Extended Attributes. • Add following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "EnableLinkedConnections"=dword:00000001 Site database cannot be edited Control Center stores site information in the site database. you must re-register when you first open Mobile Center iOS app v1. Read Permissions. If you have already upgraded to iOS 7 before upgrading to Mobile Center iOS app v1. This can occur when the mapped drive was set up by a user without administrator permissions. • 40 The file sharing attributes for the site database are incorrect.7 Troubleshooting Control Center Upgrading mobile device to iOS 7 IndigoVision recommends you upgrade Mobile Centre iOS app to v1. Control Center may not be able to edit the database for the following reasons: • The administrator account may not have permission to edit the database. for example. use one of the following solutions: • Log in as an administrator and reconfigure the mapped network drive.5. To resolve this issue. Delete. Write Attributes.5 before upgrading your device to iOS 7. due to corporate IT policies.Control Center 7 Troubleshooting When Enhanced Database Protection is disabled. • Enable Enhanced Database Protection. the file sharing attributes of a remote site database are changed when the site database is modified on the machine on which it is hosted. ensure the file sharing attributes are correct on the site database. for example. Installation Guide . and that all site database changes are made from a remote Control Center front-end application.v17 41 . • If you cannot enable Enhanced Database Protection. 7 Troubleshooting 42 Control Center Installation Guide .v17 . the following information should be used to configure the firewalls. 49425 IN/OUT UDP Multicast Audio UDP 49410.49509 IN Used to access PTZ cameras and other devices connected to the transmitter serial ports Serial Data 2 TCP 49510 . 11000 Range cameras and encoders Service Prot. 49404. 9000. 49430 OUT UDP Multicast UDP 49411. Firewalls should also support TCP and UDP connection tracking. 49431 IN/OUT Installation Guide . Serial Data TCP 49500 . Ports need not be opened in a firewall if the network protocol is exchanged entirely within a subnet or subnets that do not cross a firewall boundary. TCP Audio TCP 49410 IN UDP Multicast Video UDP 49400. 49403.v17 43 . Comments Control Data UDP 49300 IN Mandatory for communications with other IndigoVision devices including front-end application and NVR-AS. Notice This information applies only if communication occurs between equipment on opposite sides of the firewall. 49405. This is also used for UDP Video. 49420.49519 IN An additional second serial data channel for integration purposes. This service may not be used for PTZ camera control through Control Center. Destination Port Dir.A INDIGOVISION FIREWALL REQUIREMENTS When setting up a network of IndigoVision equipment that includes firewalls. 49422. Ports required by 8000. TCP Video TCP 4940049402. 49424 OUT UDP Multicast Video Control UDP 49401. 49423. 49421. UDP timeouts should be at least 30 seconds.4942049422 IN See separate section for details on ports used for different stream configurations. 49402. Also used for reliable video and audio streams. IN Comments JPEG2000 video streaming from Installation Guide .v17 . 49402. UDP Multicast audio UDP 49410 ‡ OUT Audio streams for multicast transports. Web Configuration TCP 80. Destination Port Control Center Dir. 443 1 IN Web configuration pages on the BX range devices WS-Discovery UDP 3702 IN/OUT Unicast and multicast discovery of ONVIF devices WS-Discovery TCP 3702 IN Unicast discovery of ONVIF devices 1 = This is configurable through the device web page. Destination Port Dir.A IndigoVision Firewall Requirements Service Prot. Best Effort and Multicast transports. Ports required by Ultra Range cameras Service Prot. JPEG2000 video TCP 44 Destination Port 8888 Dir. ‡ = This is configurable through the ONVIF Configuration Utility. Comments Audio Control Bandwidth Management UDP 49600 OUT Used to request a bandwidth allocation from the Bandwidth Manager Web Configuration TCP 80 IN Only required for administration telnet TCP 23 IN Only required for administration FTP cmd TCP 21 IN Used for passive FTP during bulk upgrade FTP data TCP 1024-4999 IN Used for passive FTP data transfer during bulk upgrade NTP UDP 123 OUT Used for NTP time synchronization Syslog UDP 514 OUT External system logging support SNMP UDP 161 IN Used for SNMP monitoring by third party network management tools VBLTM UDP 50000 IN/OUT Used for VBLTM monitor Ports required by BX Range cameras Service Prot. Best effort video and audio streams use ephemeral ports. 49412 ‡ OUT Video streams for Multicast transports. Comments RTSP video and TCP audio 554 1 IN RTSP session control for Reliable. UDP Multicast video UDP 49400. 49424 IN UDP Multicast Video Control 49401. UDP 49405. Destination Port Dir.4942049422 OUT See separate section for details on ports used for different stream configurations. Control Data UDP 49300 OUT Used to initiate live video from transmitters. Web Configuration TCP 80 IN Web configuration pages on the Ultra 5k range device. WS-Discovery TCP 3702 IN Unicast discovery of ONVIF devices. Best Effort video streams use ephemeral ports. UDP 49404. 49422. WS-Discovery UDP 3702 IN/OUT Unicast UDP and multicast discovery of ONVIF devices. 49423. 49430 IN UDP Multicast Audio Control UDP 49411. Serial Data TCP 49500 . 49421. Destination Port Dir. TCP Video TCP 4940049402. 49420. 49403. Comments Ultra 5K Fixed Cameras. RTSP Video TCP 554 IN RTSP session control for Reliable and Best Effort transports. Also used for Reliable video streams. 49425 IN/OUT UDP Multicast Audio UDP 49410. Comments Control Data UDP 49300 IN Mandatory for communications with other IndigoVision devices including front-end application and NVR-AS.v17 45 . 49431 IN/OUT Video Playback TCP 49299 OUT Playback of footage from an NVR-AS Web Configuration TCP 80 IN Only required for administration telnet TCP 23 IN Only required for administration FTP cmd TCP 21 IN Used for passive FTP during bulk upgrade FTP data TCP 1024-4999 IN Used for passive FTP data transfer during bulk upgrade Installation Guide . Ports required by 8000 and 9000 Range receivers Service Prot. TCP Audio TCP 49410 OUT UDP Multicast Video 49400. 49402.Control Center A IndigoVision Firewall Requirements Service Prot. This is also used to receive UDP Video.49509 OUT Used for serial connections between a PTZ keyboard attached to the receiver and a PTZ camera on a remote transmitter. Control Center Destination Port Dir. Receivers and Alarm Panels NVR Control Data TCP 8130 IN Mandatory for communication between the NVR and front-end application NVR Control Data TCP 8130 OUT Used for Alarm Server Record Actions and fault monitoring Alarm Server Control Data TCP 8131 IN Mandatory for communication between the Alarm Server and frontend application Playback TCP 49299 IN Used to playback video in front-end application Installation Guide .v17 .A IndigoVision Firewall Requirements Service Prot. Comments Control Data UDP 49300 IN Mandatory for communications with other IndigoVision devices including front-end application and NVR-AS. Comments NTP UDP 123 OUT Used for NTP time synchronization Syslog UDP 514 OUT External system logging support SNMP UDP 161 IN Used for SNMP monitoring by third party network management tools Ports required by alarm panels Service Prot. Comments IN Mandatory for communications with other IndigoVision devices including front-end application Control Data UDP 49300 OUT Mandatory for the NVR-AS to initiate recording on Transmitters. Also required to receive alarm events from Transmitters. Destination Port Dir. UDP Destination Port 49300 Dir. Web Configuration TCP 80 IN Only required for administration telnet TCP 23 IN Only required for administration FTP cmd TCP 21 IN Used for passive FTP during bulk upgrade FTP data TCP 1024-4999 IN Used for passive FTP data transfer during bulk upgrade NTP UDP 123 OUT Used for NTP time synchronisation Syslog UDP 514 OUT External system logging support SNMP UDP 161 IN Used for SNMP monitoring by third party network management tools Ports required by an NVR-AS Service Control Data 46 Prot. 49405. 49424 IN UDP Multicast Video Control UDP 49401.Control Center A IndigoVision Firewall Requirements Service Prot. 49403.4942049422 OUT See separate section for details on ports used for different stream configurations. 49404. 49402. Ports required by an NVR-AS 3000 Service Prot. 49431 IN/OUT NVR Events UDP 49301 IN Used to receive events from IndigoVision Integrations and custom integration software built using the IndigoVision SDK. Bandwidth Management UDP 49600 OUT Used to request a bandwidth allocation from the Bandwidth Manager Email TCP 25 OUT Used by Alarm Server Email Actions. 49421. Destination Port Dir. Comments TCP Video TCP 4940049402. Comments Web Configuration TCP 80 IN Only required for administration telnet TCP 23 IN Only required for administration FTP cmd TCP 21 IN Used for archiving recordings via FTP FTP data TCP 1024-4999 IN Used for archiving recordings via FTP NTP UDP 123 OUT Used for NTP time synchronisation Syslog UDP 514 OUT External system logging support SNMP UDP 161 IN Used for SNMP monitoring by third party network management tools SNMP UDP 161 OUT Used to monitor UPS status Installation Guide . 49422. Destination Port Dir. 49423. Port is configurable. 49425 IN/OUT UDP Multicast Audio UDP 49410.v17 47 . 49420. TCP Audio TCP 49410 OUT PTZ Control TCP 49500 .49509 OUT Used for Alarm Server PTZ Actions Firewall Friendly transport type TCP ONVIF streams 80 OUT Video and Audio may be tunneled through HTTP for ONVIF devices Reliable transport type ONVIF streams TCP 554 OUT UDP Multicast Video UDP 49400. 49430 IN UDP Multicast Audio Control UDP 49411. NVR Control Data TCP 8130 OUT Mandatory for communication between the NVR-AS and front-end application NVR Control Events UDP 49303 IN Mandatory for NVR event notifications and the front-end application. 49430 IN UDP Multicast Audio Control UDP 49411. 49423. 49424 IN UDP Multicast Video Control UDP 49401.4942049422 OUT See separate section for details on ports used for different stream configurations. Destination Port Dir. 49422.A IndigoVision Firewall Requirements Control Center Ports required by Windows NVR-AS These may include further Windows services such as NTP and Remote Desktop Ports required by Bandwidth Manager Service Bandwidth Management Prot. UDP Destination Port 49600 Dir. Comments Used to issue bandwidth allocations to Transmitters and NVR-ASs IN Ports required by Control Center front-end application Service 48 Prot. 49404. Alarm Server Control Data TCP 8131 OUT Mandatory for communication between the Alarm Server and frontend application Playback TCP 49299 OUT Used to playback video from an NVR TCP Video TCP 4940049402. 49431 IN/OUT Serial Data TCP 49500 . Comments Control Data UDP 49300 OUT Mandatory for communications to all IndigoVision devices. 49425 IN/OUT UDP Multicast Audio UDP 49410. 49402. 49403.49509 OUT Used to access PTZ cameras connected to transmitter serial ports Communication TCP 80 OUT Configuration of devices Firewall Friendly transport type TCP ONVIF streams 80 OUT Communication with ONVIF devices Reliable transport type ONVIF streams 554 OUT TCP Installation Guide . 49420.v17 . TCP Audio TCP 49410 OUT UDP Multicast Video UDP 49400. 49421. 49405. v17 Prot. TCP 49 . Comments FTP cmd TCP 21 OUT Used for passive FTP during bulk upgrade FTP data TCP 1024-4999 OUT Used for passive FTP data transfer during bulk upgrade WS-Discovery UDP 3702 OUT Used for discovery of ONVIF cameras WS-Discovery TCP 3702 OUT Used for discovery of ONVIF cameras Additional ports may be required for Windows services including: • NTP for time synchronisation • Access to network drives for the site database • Access to ODBC database for audit logging • Telnet for administration of IndigoVision devices Ports required by Camera Gateway Service Prot. Comments Control Data TCP 80 IN Camera Gateway Configuration Control Data TCP 25473 IN Camera Gateway Configuration Licence Activation TCP 80 OUT Camera Gateway Licence Activation (only required during installation) Media Streaming TCP 554 IN Camera to Camera Gateway Media Streaming TCP 554 OUT Mandatory for communications from Camera Gateway to NVR or frontend application Control Data TCP 47002 IN Mandatory for communications with front-end application Events TCP 29170 IN Used to listen for events from cameras The ports required for communication between a camera and the Camera Gateway vary depending on the camera. Comments JPEG2000 video TCP 8888 OUT JPEG2000 video streaming from Ultra 5K Fixed Camera Web Services 80 OUT ONVIF web services requests to Ultra 5K Fixed Camera and Firewall Friendly video streaming Installation Guide . Destination Port Dir. Ports required by Video Stream Manager (VSM) Service Destination Port Dir.Control Center A IndigoVision Firewall Requirements Service Prot. Destination Port Dir. If these details are not provided. please contact the camera manufacturer. It should be noted that multiple video streams from the same stream configuration would use the same TCP/IP port. Comments Web Services TCP 8000-8009 IN ONVIF web services for each managed Ultra 5K Fixed Camera RTSP TCP 8554-8563 IN RTSP session control and Reliable transport video streaming for each managed Ultra 5K Fixed Camera WS-Discovery UDP 3702 IN/OUT Unicast UDP and multicast discovery of ONVIF devices WS-Discovery TCP 3702 OUT Unicast TCP discovery of ONVIF devices Ports required by Mobile Center Service Service Destination Port Prot. Video stream configuration port usage Each IndigoVision Transmitter can have 3 separate stream configurations on up to two independent encoders giving a total of 6 stream configurations.A IndigoVision Firewall Requirements Control Center Service Prot. Comments Control Data UDP 49300 OUT Mandatory for communications to all IndigoVision devices.v17 . Mobile Center Control TCP 49200 IN Control requests from Mobile Center app. TCP Video TCP 49400-49402. Destination Port Dir. The table below illustrates how the ports are used by different video transport protocols and stream configurations: Stream Configuration 50 UDP Unicast Video UDP Multicast Video UDP Multicast Video Control TCP Video Encoder 1 Stream 1 49300 49400 49401 49400 Encoder 1 Stream 2 49300 49402 49403 49401 Installation Guide . Comments Control Data UDP 49300 OUT Mandatory for communications to all IndigoVision devices. Dir. Serial Data TCP 49500-49509 OUT Used to access PTZ cameras connected to transmitter serial ports . 49420-49422 OUT See separate section for details on ports used for different stream configurations. Dir. Ports required by Mobile Center app Service Destination Port Prot. For TCP and UDP multicast video the ports used will depend on the stream configurations that have been set up. Mobile Center Control TCP 49200 OUT Control requests to Mobile Center Service. v17 51 .Control Center Stream Configuration A IndigoVision Firewall Requirements UDP Unicast Video UDP Multicast Video UDP Multicast Video Control TCP Video Encoder 1 Stream 3 49300 49404 49405 49402 Encoder 2 Stream 1 49300 49420 49421 49420 Encoder 2 Stream 2 49300 49422 49423 49421 Encoder 2 Stream 3 49300 49424 49425 49422 Installation Guide . v17 .A IndigoVision Firewall Requirements 52 Control Center Installation Guide . enter the required Video Library folder (UNC path). Only video data should be stored on a network share. 2. select Settings>Control Panel>Administrative Tools>Services. From the Start menu. Changing the video library folder You will have set up a temporary Video Library folder during installation. Click Set. To browse to select a network share. From the Start menu. Creating a user account To allow the NVR-AS to record to this folder. In the Video Library field. Take care not to select a mapped network drive as this will not be recognized by the NVR-AS.v17 53 . The user name you enter must have read/write access to the Video Library. Installation Guide . 3. 3. 2. then click OK. To change this to a permanent location: 1. configuration information should be stored on a local drive which is directly attached to the NVR-AS machine.B NVR-AS POST-INSTALLATION NETWORK DRIVE CONFIGURATION If you are recording to a network drive. 4. Enter and confirm the password. Click the Log on tab and select the required account. IndigoVision recommends that you do the following: • Create a special user account for this purpose. select Programs>IndigoVision>NVR-AS>NVRASAdministrator. you must enter the account’s user name (which includes the domain name) and password as follows: 1. click Caution . Right-click Indigovision NVR-AS and select Properties. • Change the temporary Video Library folder that you set up during installation. for example. Right-click Indigovision NVR-AS and select Restart.B NVR-AS Post-Installation Network Drive Configuration Notice Control Center For optimal performance.168. for example. \\NVRTEST\VideoLibrary. the UNC path should be either: • an IP address. \\nvrtest.1. Restarting the NVR-AS 1. 2.v17 .com\VideoLibrary • It should not be a NetBIOS name. select Settings>Control Panel>Administrative Tools>Services. \\192. 54 Installation Guide .indigovision.2\VideoLibrary • a fully qualified domain name. From the Start menu. for example. C MIGRATING FROM CONTROL CENTER 3 This appendix outlines the processes for migrating from Control Center 3 and NVR 3.3 or later. To mitigate risks. This can be in the form of a standalone NVR-AS 3000 running firmware 4. Your system is not fully operational and does not log alarms until the migration is complete. and alarms generated in 3.x installations is complex. Network Video Recorders and Alarm Servers An Alarm Server handles all alarm management for Control Center. Installation Guide . To configure alarms using Control Center. Mismatched front-end application and NVR-AS versions should only occur when migrating between releases. Caution The IndigoVision Control Center alarm management configuration is significantly different to the 3. you must have at least one Alarm Server in your site database. The following table details the features of NVR 3 used with Control Center 4 or later.3 or later.x configuration. Feature NVR 3 Continuous recording job Y Timed recording job Y Record on alarm N Playback Y Alarms N Bookmarks Y ONVIF N The following table details the compatibility of the standalone NVRs and NVR-AS. ensure you read the migration section and develop a comprehensive migration strategy.v17 55 .x are not compatible with later versions. NVR-AS compatibility Caution A system must have the same versions of the NVR-AS and the Control Center frontend application for correct operation. Therefore. During migration all video and user data is copied and migrated to a new Control Center database. migrating from 3. or a Windows based NVR-AS 4. 2.x firmware. Please refer to the relevant Installation Guide for further information.1 firmware or later) NVR-AS 3000 NVR capability with all 3.1 firmware or later) NVR 200 (vp851) Only NVR capability (3. The installer creates a new site database at the location specified. 1. Upgradeable to full NVR-AS with Control Center 4 r2 or later Migrating from Control Center 3 1. This allows you to configure the new version while continuing to use your existing Control Center 3 installation. Log into the Control Center front-end application as an administrator. you must upgrade to the latest NVR 3 release before migrating to NVR-AS 4. Upgrade your NVRs to the latest NVR 3 release 2. you must ensure that your site database is compatible for the migration by upgrading to the latest release of Control Center 3 front-end application. Install the latest release of Control Center 3 front-end application. This forces Control Center to update the site database to the latest format.C Migrating from Control Center 3 Control Center Standalone NVR version Compatibility vp850 Not compatible vp852 Only NVR capability (3. 4. select Import an existing Control Center 3 site database on the Site Database Details dialog. Upgrade your Control Center front-end application to the latest Control Center 3 release 3. Upgrade to the latest Control Center 3 release To successfully migrate to IndigoVision Control Center.15. followed by your Primary NVRs. Make a minor change to the site database. Upgrade to the latest version of Control Center front-end application You can install the latest version of the Control Center front-end application on the same PC as Control Center 3. see "Control Center front-end application Installation" on page 13 During installation. ► For more information about installing Control Center. Reconfigure the binary inputs on IndigoVision devices Upgrade to the latest NVR 3 release To successfully migrate to IndigoVision Control Center. 3.15. Notice Upgrade your Failover NVRs first. Upgrade your Control Center front-end application to the latest release 4. 56 Installation Guide . Please refer to the relevant Installation Guide for further information.v17 . change the top site name. Upgrade your NVRs to the latest NVR-AS release 5.x installation 6. Undo the change and close the front-end application. Migrate the alarm sources from your 3. for example. These tools are provided on the IndigoVision Control Center CD. see "NVR-AS Installation" on page 9. refer to Alarm Server Configuration Tool Administration Guide provided with the tool ► For information about using the Control Center Alarm Source migration tool. 2. leaving the original NVR database available. Should you need to revert to your previous NVR version. After installation. For more information about installing NVR-AS 4. Installation Guide . refer to Control Center Alarm Source Migration Tool online help provided with the tool Before migrating your alarm sources.x installation.v17 57 . see the Audit Log Reference Guide. you need to use the following steps: 1.Control Center C Migrating from Control Center 3 The new site database contains all site information with the exception of the alarm-related information. you can downgrade the NVR-AS installation.x installation. Import the new zones. ► For information about using the Alarm Server Configuration tool. Migrate alarm sources Once you have successfully installed Control Center. Upgrade to NVR-AS 4 Install the latest NVR-AS 4 release. Notice Upgrade your Failover NVRs first. ► For information about planning the migration. This enables you to downgrade to your previous Control Center 3 installation if necessary. see "Planning your migration of 3. ► For more information about downgrading an NVR-AS installation. 3. see "Downgrading an NVR-AS" on page 61 Caution Footage recorded on an NVR-AS 4 cannot be played on an NVR 3. you must upgrade the audit log database to the latest version. Notice The Control Center 3 site database is kept after the new version of the Control Center front-end application is installed. any footage recorded by the NVR-AS 4 will not be accessible after you downgrade to NVR 3.x installation alarm sources" on page 59 To migrate alarm sources from a 3. Export the alarm sources from the 3. Plan your migration to ensure the zones and detectors created behave as expected.x installation. During installation the NVR-AS 4 installer copies the configuration data to new databases. you can migrate the alarm sources from your 3. it is important that you plan how your alarms will be managed in IndigoVision Control Center. detectors and actions into an Alarm Server. For more information. Therefore. To migrate alarm sources you must use the Control Center Alarm Source Migration tool and the Alarm Server Configuration tool. followed by your Primary NVRs. and [Base Name]_Actions. Use the list of migration warnings to identify the additional configuration required in Control Center. The alarm sources are exported as two . 2. for example. and displays a list of warnings on the Migration Warnings dialog. 2. The alarm sources are saved to the export files and the Migration Warnings dialog opens. Export 3. It may be more convenient to make changes prior to importing. Click Save and exit to save the list of warnings as an .C Migrating from Control Center 3 Control Center 4. Click OK.csv files. The majority of the zone. 5. If you intend to use more than one Alarm Server in the new installation. Re-configure binary inputs on IndigoVision devices Before you can use the physical input detectors in your IndigoVision Control Center system. The Alarm Server Configuration tool enables bulk creation of zones. The file names are [Base Name]_Detectors. export the alarm sources destined for each new Alarm Server in different batches. The warnings provide details of alarm sources that cannot be exported. use the options at the top of the list to filter the list. please refer to the Control Center online help. 1. 3.csv. Enter the Base Name for the exported files and choose the Export folder these files are saved to.x installation alarm sources To migrate alarm sources.. you need to export them from the 3.csv files if necessary. detectors and activations in late versions of Control Center. Select the alarm sources that you want to migrate. 1.csv files. Install and open Control Center Alarm Source Migration..x installation. you need to import them into an Alarm Server using the IndigoVision Alarm Server Configuration tool. Import 3. Control Center Alarm Source Migration validates the alarm sources you have selected. During installation you must select the Control Center 3. ► For more information about configuring zones. detector and action settings can be edited in the . After importing the new zones. Edit the detector and action . as well as any additional configuration required in later versions of Control Center. you may need to complete additional configuration using Control Center. ensure the binary inputs of IndigoVision devices are correctly configured. Complete any additional configuration in Control Center as necessary.The Export to SMS4 Format dialog opens.x installation alarm sources. 6.x installation alarm sources To complete the migration of 3..html file that you can refer to when configuring the alarms in later versions of Control Center.csv files into an Alarm Server. 4. The dialog closes. Use the Alarm Server Configuration tool to import the detector and action . 58 Installation Guide . One contains details of the new zones and detectors.v17 . the second the details of the alarm actions. 3. Right-click the selected alarm sources and click Export to SMS4 Format. detectors and actions on an Alarm Server. grouping the detectors by logical zones.x site database that you are migrating. detectors and actions.csv. If your list is large. Caution If the binary input configuration is not updated. For more information about Control Center alarm management.x installation are not directly comparable to the zones and detectors in later versions. • In Control Center after migration. Alternatively. or alarm panel. please refer to the Control Center help.x prior to exporting the alarm sources. You have the following opportunities to edit the alarm source to help simplify the migration: • In Control Center 3. you can reconfigure large numbers of binary inputs using the Alarm Server Configuration Tool. For more information refer to the Alarm Server Configuration Tool Administrator Guide. the physical input detectors may remain in either the triggered or normal state. Ensure that both Low to High and High to Low events are configured for each input . alarm sources created in 3. Before migrating your alarm sources.x installation alarm sources Control Center 4 and later provides a more sophisticated alarm management system than 3. and deactivated on network gain) Installation Guide . • Edit the detector and actions . navigate to the Binary IO page on the device's Configuration pages. For each camera.Control Center C Migrating from Control Center 3 1. Use these sections to help you plan the migration. Planning your migration of 3. For more information refer to the Control Center help. for example grouping detectors into zones. it is important that you plan how your alarms will be managed in Control Center. Detectors are grouped into zones to help manage alarms more effectively.x installations. transmitter. Alarm sources An alarm source maps to a single zone with one detector. • Name: Name of the Zone and the name of the Detector • Priority: Zone priority Alarm source type The alarm source type maps to the detector type. • In the Alarm Source Migration tool prior to exporting the alarm sources. Events are detected by detectors such as a PIR or camera motion detection.csv files prior to importing into your new Control Center installation.x installation alarm source settings are converted during the migration. • Binary input: Physical • External input: External (any non-IndigoVision application that sends events to an alarm server) • Video analysis: Analytics • Video lost: Video Fault (detector is activated on video loss. and deactivated on video gain) • Network lost: Network Fault (detector is activated on network loss. 2.v17 59 . For more information refer to the Control Center help. The following sections detail how 3. receiver. Therefore. Alarm source alarm procedures • Manual acknowledgement: Detector is alarmable with 0 sec dwell time • Latched acknowledgement: Detector is not alarmable with 0 sec dwell time • Timed acknowledgement: Detector is not alarmable with X sec dwell time • Automatic acknowledgement: Detector is not alarmable with 0 sec dwell time Video source The camera associated with the new detector is used as the default video source for that detector. During migration.x installation. Video and Network gain events are used to deactivate Video and Network Fault detectors. The alarm source specified here is used for the detector deactivation event if that alarm source type is supported in Control Center 4 or later. Recording actions on alarm sources Recording actions map to recording actions on detectors. if the activation alarm source is a Network or Video Lost. • Camera: The camera uses the same name. the deactivation event will be the Network or Video gain event regardless of the alarm source defined here. This may be different to the video source used by the original alarm source. warnings are displayed if these are present in the current 3. • On activation. • Stop after: Stop recording after • Protect footage | Pre-alarm duration: Protect footage | Pre-event duration • Record audio: Record audio The connection types use descriptive names: • UDP Unicast: Best effort • TCP: Reliable • UDP Multicast: Multi-cast Relay actions on alarm sources Relay actions on alarm sources map to relay actions on detectors. However. • 60 Default priority is 5 Installation Guide . Ensure the corresponding Video or Network lost alarm source is selected to ensure a fault detector is created.v17 . • Stop on alarm from: The recording action is configured to stop on detector deactivation.C Migrating from Control Center 3 Control Center Tamper alarm source types are not migrated as they are not supported in Control Center 4 and later. set output pin high: Relay is normally open • On activation. set output pin low: Relay is normally closed • Automatically reset output pin X seconds after activation: Activate relay for X seconds • Do not automatically reset output pin: Activate relay Video actions on alarm sources Video action settings to move PTZ cameras to a preset map to PTZ actions on detectors. you will need to reconfigure these settings in Control Center once the zones. This may be useful if you have received a standalone NVR-AS 3000 with NVR-AS 4 pre-installed. • Looped replay on video actions • Armed time • PA actions • Map Links The following settings can be inherited from their parent sites. Assign alarms Assign an alarm to the current user so that several users do not attempt to deal with it at the same time. You will need to reconfigure these settings in Control Center once the zones. • Recipients are migrated • Email subject is updated to the new format Settings not migrated The following settings are not migrated. detectors and actions have been imported. Installation Guide . Tamper alarms The tamper alarms that were associated with Tamper-Proof Alarm Panel inputs are no longer supported. • Alarm sound • Alarm procedure text • User response required when manually acknowledging an alarm • User access • Protection Features not supported in IndigoVision Control Center Certain alarm management features that were available in Control Center 3 and NVR 3 are not supported in IndigoVision Control Center. Downgrading an NVR-AS You can downgrade an NVR-AS 4 installation to an NVR 3 if required. A reaping policy is now available on the Alarm Server to control the deletion of alarms. If they are not configured to be inherited. Manual deletion of alarms from the alarm log Manually edit the alarm log to delete alarms. detectors and actions have been imported.v17 61 .Control Center C Migrating from Control Center 3 Email actions on alarm sources Email actions on alarm sources map to email actions on detectors. You can downgrade a Windows NVR-AS and an NVR-AS 3000. or if you wish to revert an upgrade. Install the version of NVR you require.C Migrating from Control Center 3 Caution Control Center Footage recorded on an NVR-AS 4 cannot be played on an NVR 3. To downgrade a Windows NVR-AS: 1. any footage recorded by the NVR-AS 4 will not be accessible after you downgrade to NVR 3. Uninstall the Windows NVR-AS. Therefore.1 vex file. Navigate to the Firmware upgrade page in the Configuration pages. Select the NVR 3.23. 2.1 or later.v17 .23. 62 Installation Guide . An NVR-AS 3000 can be downgraded to NVR 3. 2. A Windows NVR-AS can be downgraded to any previous NVR 3 version. To downgrade a standalone NVR-AS 3000: 1. Navigate to \English\Resources\NTP Server on the Control Center product CD.D INSTALLING A WINDOWS NTP SERVER Accurate time synchronization is critical for all elements in an IndigoVision security system.exe. default installation folders. This installs the Microsoft Visual C++ 2008 Redistributable Package (x86) C++ runtime required by the NTP software. If adding a new account the password must meet the criteria : a. b. On the Configuration Options dialog specify the time source for the NTP daemon. To synchronize your devices it is recommended that you use the Windows network time protocol (NTP) server software included on the Control Center product CD. Windows-based devices. Accept the license agreement. Caution When the Windows NTP daemon is installed. • If you are installing the NTP daemon on a server (for example.exe. VSM 4000. Be at least six characters in length. 6. 2. Choose whether to create a new account or use an existing one to run the daemon. • If you are installing the NTP daemon on a Control Center PC. 3. 1. Contain characters from three of the following four categories: • English uppercase characters (A through Z) • English lowercase characters (a through z) Installation Guide .2. This installs the Windows NTP daemon. and default settings. 4. IndigoVision cameras and NVR-AS 3000 units have built in network time protocol (NTP) software accessible through the device web page. VSM 4000. use these settings: Do not select the check box Add local clock as a last resort reference. Specify the upstream NTP servers using a comma separated list. Camera Gateway servers and workstations running the Control Center front-end application must be time synchronized. Run ntp-4.6p5@london-o-lpv-win32-setup. 5. 7. NVR-AS 4000.v17 63 . Run vc_redist_x86. Windows NVR-AS. or Camera Gateway) which is to be used as an NTP server for downstream clients: Select the check box Add local clock as a last resort reference. Installation and configuration This procedure tells you how to install and configure the Windows network time protocol (NTP) server software. the standard Windows Time service (W32Time) is disabled and can no longer be used. including the NVR-AS 4000. %) Control Center If the password does not meet the requirements you get the error message ERROR 2245. 8. !.v17 . You can check the current state of time synchronization by running the Quick NTP Status utility.D Installing a Windows NTP server • Base 10 digits (0 through 9) • Non-alphabetic characters (for example. $. 64 Installation Guide . #. Use the default NTP Service Settings. To run the utitlity: Select Start Menu > All Programs > Meinberg > Network Time Protocol > Quick NTP Status. The Windows NTP daemon is now configured to synchronize the system clock with the upstream NTP servers.