Security Center 4.0 SR1

Transcription

1 Security Center 4.0 SR1 Installation and Upgrade Guide Unified Security Platform September 2010

2 2010 Genetec Inc. All rights reserved. Genetec Inc. distributes this document with software that includes an end user license agreement and is furnished under license and may be used only in accordance with the terms of the license agreement. The contents of this document are protected under copyright law. The contents of this guide are furnished for informational use only and are subject to change without notice. Genetec Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. This publication may not be copied, modified, or reproduced in any form or for any purpose, nor can any derivative works be created therefrom without Genetec Inc. s prior written consent. Genetec Inc. reserves the right to revise and improve its products as it sees fit. This document describes the state of a product at the time of document s last revision, and may not reflect the product at all times in the future. In no event shall Genetec Inc. be liable to any person or entity with respect to any loss or damage that is incidental to or consequential upon the instructions found in this document or the computer software and hardware products described herein. The use of this document is subject to the disclaimer of liability found in the end user license agreement. "Genetec", "Omnicast", "Synergis", "AutoVu", "Federation", the Genetec stylized "G" and the Omnicast, Synergis and AutoVu logos are trademarks of Genetec Inc., either registered or pending registration in several jurisdictions. "Security Center" and the Security Center logo are trademarks of Genetec Inc. Other trade names used in this document may be trademarks or registered trademarks of the manufacturers or vendors of the respective products. All specifications are subject to change without notice. Document title: Security Center 4.0 SR1 Installation and Upgrade Guide Document number: EN V4.0.C1(3) Publication date: June 16,

3 Table of Contents 1. Introduction Installation workflow System requirements Server hardware requirements for AutoVu Server hardware requirements for Synergis Client hardware requirements Software requirements Required and supported software Compatibility with other Genetec security software Preparing to install Installing Omnicast compatibility packs Installing Security Center Installing Security Center Server Manually add a user to manage the SQL 2008 database Installing Microsoft.NET Framework 3.5 SP1 for Windows Server 2008 R Activating Microsoft.NET Framework 3.5 SP1 for Windows Installing ASP.NET for Synergis Web Client Installing Security Center Client Installing Security Center with NEC ExpressCluster X LAN Edition Introduction System Setup Cluster configuration planning Cluster installation requirements and prerequisites How to configure Security Center to run in a cluster configuration Installing NEC ExpressCluster on both servers in the cluster Installing and configuring Security Center on both servers in the cluster Configure NEC ExpressCluster X LAN Edition for Windows Configure the database Configure the Security Center Web Client Start-up Security Center services Upgrading from Security Center Upgrading Security Center Server Upgrading Security Center Client Upgrading from Synergis

4 8.1. Upgrading Synergis Server Upgrading Synergis Client Upgrade issues from Synergis 2.1 to Security Center Limitations Known upgrade issues Manual upgrade of Omnicast external systems Migrating from a previous version of AutoVu Setting up the AutoVu LPR Manager Configuring SQL Server 2008 for AutoVu Changing the location of the LPR Manager database Installing Security Center in Silent Mode About Silent Install Overview About the Silent Install mechanism Limitations Before a Silent Install Performing a Silent Install General syntax Setup arguments Installer arguments Installer options Installer properties Security Center server modules Security Center client modules Sample install commands Sample server installation commands Sample client installation commands Performing a Silent Uninstall Contacting Genetec s Technical Assistance Center

5 1. Introduction This document explains how to install the Security Center 4.0 SR1 software. 2. Installation workflow Use the following checklist to help you install Security Center. 1. Verify that the system requirements are met; see System requirements on page Prepare everything you need before the installation, see Preparing to install on page If Omnicast will be federated (unified) to Security Center, install the required Omnicast compatibility packs before installing any of the following Security Center applications: Integration Service (if it is going to host Omnicast federations) Config Tool (if it is going to be used to configure Omnicast federations) Security Desk (if is going to be used to connect to Omnicast federations) For instructions on how to install Omnicast compatibility packs, see Installing Omnicast compatibility packs on page Do one of the following: If installing Security Center for the first time, see Installing Security Center on page 12. If upgrading from Synergis 2.1, see Upgrading from Synergis 2.1 on page 34. If upgrading from Security Center 3.0, see Upgrading from Security Center 3.0 on page 33. If upgrading from Security Center 4.0 GA, uninstall the Security Center 4.0 GA applications with Windows Add or Remove Programs, then follow the instructions found in Installing Security Center on page 12. If migrating from AutoVu 4.3 Back Office, see Migrating from a previous version of AutoVu on page 40. If you want to install components in silent mode, see Installing Security Center in Silent Mode on page 48. 5

6 3. System requirements For the Security Center to be successfully installed, your equipment must meet certain minimum requirements. The server requirements for AutoVu and Synergis solutions are different, but the client requirements are the same. To determine which server and client configuration best meets your needs, please contact the Genetec Sales Engineering team at 3.1. Server hardware requirements for AutoVu Size Low (20 units 1 or less) Medium (70 units 1 or less) High (70 to 140 units 1 ) Server hardware requirements Intel Core 2 Duo E6850 family or faster 2 GB of RAM or more 80 GB hard drive 2 for OS and Security Center/AutoVu applications Standard SVGA video card 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card DVD ROM drive Intel Core 2 Quad Q6600 family or faster 4 GB of RAM or more 80 GB hard drive 2 for OS and Security Center/ AutoVu applications Dedicated hard drive for SQL database 3 Standard SVGA video card 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card DVD ROM drive Intel Xeon Quad Core X54xx family or faster 6 GB of RAM or more 80 GB hard drive 2 for OS and Security Center/ AutoVu applications Dedicated hard drive for SQL database (4 disk RAID 5 array or better) 4 Standard SVGA video card 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card DVD ROM drive 1 A unit is either a fixed Sharp unit or mobile patrolling unit (AutoVu Patroller with one or two Sharp units). 2 This does not include the storage for LPR data (reads and hits) which are stored in an SQL Server database. 3 Over 20 units, SQL Server 2008 Standard Edition or higher is recommended. 4 Over 70 units, Windows Server x64 R2 and SQL Server 2008 Standard x64 Edition or higher are recommended. 6

7 3.2. Server hardware requirements for Synergis Size Low (64 readers or less) Medium (256 readers or less) High (256 readers or more) Server hardware requirements Intel Core 2 Duo 3.0 GHz or faster 2 GB of RAM or more 80 GB hard drive for OS and Security Center/Synergis applications Standard SVGA video card 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card DVD ROM drive Dual Core Intel Xeon 2.66 GHz or faster 4 GB of RAM or more 80 GB hard drive for OS and Security Center/Synergis applications Standard SVGA video card 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card DVD ROM drive Quad Core Intel Xeon 2.0 GHz or faster 4 GB of RAM or more 80 GB hard drive for OS and Security Center/Synergis applications Standard SVGA video card 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card DVD ROM drive 7

8 3.3. Client hardware requirements Size Low Medium High Client hardware requirements Intel Pentium Dual-Core 2.5 GHz or faster 2 GB of RAM or more 80 GB hard drive for OS and Security Center client applications 3D graphics card required with Direct3D support (128 MB or better) 1024 x 768 or higher screen resolution 10/100/1000 Ethernet network interface card 16x DVD+/- RW drive (recommended for exporting archived video sequences) Sound card Intel Core 2 Duo 3.0 GHz or faster 2 GB of RAM or more 80 GB hard drive for OS and Security Center client applications 3D graphics card required with Direct3D support (256 MB or better, x16 ) 1280 x 1024 or higher screen resolution 10/100/1000 Ethernet network interface card 16x DVD+/- RW drive (recommended for exporting archived video sequences) Sound card Intel Core 2 Duo 3.0 GHz or faster 4 GB of RAM or more 80 GB hard drive for OS and Security Center client applications 3D graphics card required with Direct3D support (512 MB or better, x16 ) 1600 x 1200 or higher screen resolution 10/100/1000 Ethernet network interface card 16x DVD+/- RW drive (recommended for exporting archived video sequences) Sound card 8

9 3.4. Software requirements Required and supported software Software category Operating Systems 5 Database Engines Cluster Manager Virtualization Web Browsers Required/Supported software Microsoft Windows XP Pro SP3 32-bit/64-bit Microsoft Windows Vista SP1 Business and Ultimate 32-bit/64-bit Microsoft Windows 7 Professional and Ultimate 32-bit/64-bit Microsoft Windows Server 2003 Standard Edition SP2/R2 32-bit/64-bit Microsoft Windows Server 2003 Enterprise Edition SP2/R2 32-bit/64-bit Microsoft Windows Server 2008 Standard Edition SP2/R2 32-bit/64-bit Microsoft Windows Server 2008 Enterprise Edition SP2/R2 32-bit/64-bit SQL Server Express/Standard/Enterprise SP2/SP3 SQL Server 2008 Express 7 /Standard/Enterprise (SP1) 8 NEC ExpressCluster X LAN Edition R2.0 for Windows. VMware vsphere 4.1 (client), ESXi 4.0, ESX 4.1 (server) ASP.NET must be enabled on your IIS server. Web Client is installed as part of Security Center Server software. Internet Explorer 7 or 8 (for Synergis Web Client) Compatibility with other Genetec security software Note the following Security Center 4.0 compatibility issues: Security Center 4.0 software cannot be installed on the same machine as earlier versions of Synergis or Security Center. However, Synergis 2.1 and Security Center 3.0 can be upgraded to Security Center 4.0. Security Center 4.0 Client and Omnicast 4.x Client can be installed on the same machine. Security Center 4.0 Server and Omnicast 4.x Server can be installed on the same server, but it is not recommended if Omnicast is managing more than 30 cameras. A different Omnicast Compatibility Pack is required for each version of Omnicast you plan to federate to the Security Center. See Installing Omnicast compatibility packs on page Security Center cannot be installed on a Windows 2003/2008 Server running a Domain Controller. 6 SQL Server 2005 is not supported for AutoVu. 7 SQL Server 2008 Express Edition is part of the installation package. You can choose to install it during the Security Center installation process. 8 SQL Server 2008 Standard/Entrerprise Edition SP1 is required if used with Windows Server

10 4. Preparing to install Before you install, do the following: Administrator privileges are required to install Security Center and its prerequisites. Make sure you have administrator privileges. Make sure you have Internet access. You ll need to connect to the Genetec website in order to submit your validation key and to extract your license (for Directory installation only). Disable all power saving features (hibernation) on computers hosting any Security Center server applications (Directory, Integration Service or Access Manager) or any database used by those server applications. Make sure you have access to the Genetec Security Center 4.0 Installation Package (on a DVD or copied to a folder on your company s LAN). Make sure you have at least 2 GB of free space on your system drive (where the Windows folder is). This is required regardless where you choose to install the Security Center software. Before any upgrade, we strongly recommend that you back up all your system databases as a safety precaution. For information on how to back up your system databases, see the Administrator Guide for that version. 10

11 5. Installing Omnicast compatibility packs If federating Omnicast to Security Center, you ll need to install the required Omnicast compatibility packs before installing Security Center software. The Omnicast compatibility packs will need to be installed on every computer running the following Security Center applications: Security Desk Config Tool Integration Service (if it is hosting an Omnicast federation) Security Center 4.0 is compatible with Omnicast 4.3 and later. You ll need to install a compatibility pack for each version of Omnicast you intend to federate to your Security Center. If you need the compatibility packs for earlier versions of Omnicast, please contact Genetec Technical Assistance. IMPORTANT When installing both Omnicast and Security Center on the same machine, install the compatibility packs after the Omnicast installation. To install an Omnicast compatibility pack: 1. Insert the Security Center installation DVD in your computer s DVD drive. If the InstallShield Wizard does not appear, double-click setup.exe in the product s root folder. 2. Click Compatibility packs. This opens a browser to the CompatibilityPacks folder. 3. In the CompatibilityPacks folder, open the subfolder corresponding to the required compatibility pack. 4. Double-click setup.exe and follow the InstallShield Wizard instructions. 11

12 6. Installing Security Center This section describes how to install the Security Center 4.0 client and server components Installing Security Center Server This section describes how to install Security Center Server on a computer where neither Synergis nor Security Center components are installed. In the procedure that follows, you'll run the InstallShield Wizard, activate the product license from the Genetec license website, and then apply the license in the Security Center Server Admin. Notes If you are using SQL 2008, there are extra installation steps. These steps can be performed before or after the Security Center Server installation, see Manually add a user to manage the SQL 2008 database on page 18. If you are using Windows Server 2008 R2, Microsoft.NET Framework 3.5 SP1 needs to be installed before the Security Center Server installation. For more information, see Installing Microsoft.NET Framework 3.5 SP1 for Windows Server 2008 R2 on page 18. If you are using Windows 7, you must ensure that Microsoft.NET Framework 3.5 SP1 is activated. For more information, see Activating Microsoft.NET Framework 3.5 SP1 for Windows 7 on page 18. If you are planning to install Synergis Web Client, you must ensure that ASP.NET is installed or enabled on your machine. For more information, see Installing ASP.NET for Synergis Web Client on page 19. To install the Security Center server component: 1. Insert the Security Center installation DVD in your computer s DVD drive. If the InstallShield Wizard does not appear, double-click setup.exe in the product s root folder. 12

13 In the Genetec Security Center Installation dialog box, select the language (English or Français) used by the InstallShield Wizard and click Server installation. If the InstallShield Wizard prompts you to install any missing prerequisites, click Install. A reboot might be required. When the InstallShield Wizard is ready to install the server component, the Welcome dialog box appears. 2. Review the Welcome information and click Next. 3. In the License agreement dialog box, read the Genetec Software License Agreement. If you agree with the terms, click I accept the terms in the license agreement and click Next. 4. In the Language selection dialog box, select the language and click Next. 5. In the Destination folder dialog box, specify the location of the installation folder, and click Next. The default is C:\Program Files\Genetec Security Center 4.0\. To choose a different folder, click Change. 6. In the Custom setup dialog box, choose to install all or selected parts of the software, and click Next. From this dialog box, you can perform the following actions: View a feature description and the space it requires by clicking the feature name. Change how a feature is installed by clicking on the button. View the custom setup tips by clicking the Help button. View the disk space requirement summary by clicking the Space button. Go back to the previous step by clicking the Back button. 7. In the Database server selection dialog box, select the database server that is going to manage the database instances required by the Security Center components, and click Next. 13

14 You can choose from the following options: Select Install a new database server to install Microsoft SQL Server 2008 Express Edition on your computer.you must choose a database Instance Name. The default is SQLEXPRESS. The name you enter must follow specific rules: The instance name is not case sensitive The instance name may not match any of the SQL Server reserved keywords, such as DEFAULT, PRIMARY, and so on. For a complete list of all reserved keywords, see The instance name may not be longer than 16 characters. The first letter of the instance name mut be a letter or an underscore (_). Acceptable letters are those defined by the Unicode Standard 2.0, including Latin characters a-z and A-Z, and letter characters from other languages. Subsequent characters can be letters defined by the Unicode Standard 2.0, decimal numbers from Basic Latin or other national scripts, the dollar sign ($), or an underscore (_). Embedded spaces of other special characters are not allowed in instance names, nor are the backslash (\), comma (,), colon (:), semi-colon (;), single quotation mark ('), ampersand (&), number sign (#), and at sign (@). Select Use an existing database server to use an existing SQL Server instance and enter its name in the Database Server field or use the Browse button to find it. Notes concerning AutoVu SQL Server 2005 is not supported for AutoVu (see Software requirements on page 9). As a rule of thumb, if Security Center manages more than five Patrollers or if you intend to keep your LPR data over 30 days, it is recommended to use SQL Server 2008 Standard Edition instead of the Express Edition. For a precise evaluation of your requirements, please contact Genetec Technical Assistance. If you are using an existing SQL Server 2008 instance, there are important configuration settings that you need to follow. See Configuring SQL Server 2008 for AutoVu on page

15 8. In the Services logon parameters dialog box, do one of the following: Select Use default username and password to use the default username (Local System) to run your Security Center services. This option works in most cases. Select Specify the username and password for all services and enter a valid domain username and password. This option is necessary if you intend to run the Integration Service to interface with an Active Directory server. The selected user must be a member of the Administrators group, have Log on as service user right, and Read access to the Active Directory you want it to connect to. Click Next. 9. In the Ready to install dialog box, select Start the Server Admin check box and click Install. The Server Admin window will appear after a few minutes. If you do not choose to install the Directory service, the procedure ends here. Close the Server Admin and click Finish. 15

16 10. In the Server Admin resource tree, select Directory and click the License tab. 11. Click the button next to Validation key to save the validation key to a file on your computer. The validation key is a number sequence generated by the Server Admin. It is used to obtain the license key that unlocks your Security Center software. The default name for that file is Validation.vk. 12. Log on to Genetec Technical Assistance Portal at Use the System ID (as Username) and the Password specified in the Security Center License Information document that was sent to you when you purchased your license, and click Log on. 13. In the System Management tab, click the arrow besides the icon to expand the Directory section. 14. Review the description of your License content and click Activate your license now. 15. In the Activation dialog box, click Browse to open the Validation.vk file saved in Step 11, and click Submit. The message Your license has successfully been activated should appear in the dialog box. 16. Click the hyperlink Download License to save the license key to a file. The default name is your System ID followed by _Directory_License.lic. 16

17 17. In the Server Admin, click the button next to Activate license to import the license key. Browse to the folder where the License.lic file was saved and click Open. The access rights granted by your license are listed in separate tabs. 18. Click in the Server Admin toolbar to save the license information. 19. Close the Server Admin and click Finish to complete the Security Center server software installation. 20. If required by the InstallShield Wizard, restart the computer. 17

18 Manually add a user to manage the SQL 2008 database When installing Security Center Server that uses SQL Server 2008 you must manually add a user to manage the database. SQL Server 2008 protocols prevent the InstallShield from doing this automatically, as it does for other SQL versions. If you are upgrading a SQL database from an earlier version to the 2008 version, you can skip this procedure since the necessary user is already present. To manually add a user to manage the SQL 2008 database: 1. Open Microsoft SQL Server Management Studio and connect to the server Security Cent will use. 2. Expand the Security folder, right-click on Logins and select New Login. 3. In the Login name field, enter the Windows logon user name that is used to start your Security Center services. For example, if you are using the default user name Local System for your Security Center services, you would enter <server name>\local System. 4. Make sure that Windows authentication is selected. 5. Under Select a page, click Server Roles and select the sysadmin option. 6. Click OK. The new user will appear in the Logins folder. 7. Close the Microsoft SQL Server Management Studio and restart all SQL and Security Center services Installing Microsoft.NET Framework 3.5 SP1 for Windows Server 2008 R2 When installing Security Center Server for use with Windows Server 2008 R2, you must manually install Microsoft.NET Framework 3.5 SP1. To manually install Microsoft.NET Framework for Windows Server 2008 R2: 1. Click Start > Control Panel > Administrative Tools > Server Manager. 2. Select Features > Add Features. 3. In the Select Features dialog box, choose.net Framework Features. 4. In the Add Features Wizard dialog box, click the Add Required Role Services button then click Next > Next. 5. From the Role Services list, make sure that.net Extensibility is selected then click Next > Install. 6. When the installation is complete, click Close Activating Microsoft.NET Framework 3.5 SP1 for Windows 7 When installing Security Center Server for use with Windows 7, the Microsoft.NET Framework 3.5 SP1 must be activated (turned on). To activate install Microsoft.NET Framework for Windows 7: 1. Click Start > Control Panel > Programs and Features. 18

19 2. In the Programs and Features dialog box, choose Turn Windows features on or off. 3. Select Features > Add Features. 4. In the Windows Features dialog box, select the Microsoft.NET Framework option and click OK Installing ASP.NET for Synergis Web Client When installing Synergis Web Client module, you must first install ASP.NET. To enable ASP.NET in the IIS Manager on Windows Server 2003 family OS: 1. Click Start > Run. 2. In the Run dialog box, type inetmgr in the Open field and click OK. 3. In IIS Manager, expand the local computer and click Web Service Extensions. 4. In the right pane, right-click ASP.NET and then click Allow. The status of ASP.NET changes to Allowed. To install ASP.NET on Windows Vista or Windows 7 family OS: 1. Follow the instructions found on the following Web page: To install ASP.NET on Windows 2008 family OS: 1. Follow the instructions found on the following Web page: aspx 19

20 6.2. Installing Security Center Client This section describes how to install Security Center Client on a computer where neither Synergis nor Security Center components are installed. For more information about the new Security Desk and Config Tool applications, see the Genetec Security Desk User Guide and the Security Center Administrator Guide respectively. Prerequisite: If you are installing Security Center Client on Windows Server 2008, you must first install the Desktop Experience feature. Failing to do so, the video export feature in Security Desk will not work. 1. Click Start > Administrative Tools > Server Manager. 2. In the Features Summary section, click Add features. 3. Select the Desktop Experience option and click Next. 4. Complete the wizard by clicking Install. To install the Security Center client component: 1. Insert the Security Center installation DVD in your computer s DVD drive. If the InstallShield Wizard does not appear, double-click setup.exe in the product s root folder. In the Genetec Security Center Installation dialog box, select the language (English or Français) used by the InstallShield Wizard and click Client installation. If the InstallShield Wizard prompts you to install any missing prerequisites, click Install. When the InstallShield Wizard is ready to install the client component, the Welcome dialog box appears. 2. Review the Welcome information and click Next. 3. In the License agreement dialog box, read the Genetec Software License Agreement. If you agree with the terms, click I accept the terms in the license agreement and click Next. 4. In the Language selection dialog box, select the language and click Next. 20

21 5. In the Destination folder dialog box, specify the location of the installation folder, and click Next. The default is C:\Program Files\Genetec Security Center 4.0\. To choose a different folder, click Change. 6. In the Custom setup dialog box, choose to install all or selected parts of the software, click Next, and then click Install. From this dialog box, you can perform the following actions: View a feature description and the space it requires by clicking the feature name. Change how a feature is installed by clicking on the button. View the custom setup tips by clicking the Help button. View the disk space requirement summary by clicking the Space button. Go back to the previous step by clicking the Back button. 7. It takes a while for the InstallShield Wizard to install the selected features. When the InstallShield Wizard completed screen appears, click Finish. 21

22 6.3. Installing Security Center with NEC ExpressCluster X LAN Edition Introduction This section describes how to configure Security Center with a NEC ExpressCluster X LAN Edition for Windows configuration. The LAN Edition clustering provides synchronous data mirroring between two servers. Fast application recovery and data protection is ensured in case of a system failure. If the active server fails, the standby server in the cluster will automatically bring Security Center/Synergis online to provide failover. Clustering also minimizes maintenance downtime System Setup The cluster setup should consist of two nodes in a mirrored configuration. 22

23 Cluster configuration planning Before you install, fill-in the following table with the system information you'll need to provide during the installation. Cluster component Description Your system Cluster name Name of the cluster configuration. Failover Group name Name of the failover group. Management Group name Failover Floating IP Address Management Floating IP Address Virtual Computer name Active Node name Active Node public IP address Active Node public Subnet mask Active node public Default Gateway Active Node public Preferred DNS server address Active Node interconnect IP address Active Node Interconnect Subnet mask Standby Node Name Standby Node public IP Address Standby Node public Subnet mask Standby node public Default Gateway Name to be used for identification in the cluster configuration. Static IP address used to access Security Center services within the cluster. Static IP address used to access cluster management services within the cluster. Name to be used to access the actual server (i.e. Active or Standby) hosting the Security Center services. Name to be used for identification in the cluster configuration. Static IP address used in the public IP network. Subnet mask used in the public IP network. Default Gateway used in the public IP network. Static IP address of the Preferred DNS server in the public IP network. Static IP address used in the interconnect IP network. Subnet mask used in the interconnect IP network. Name used for identification in the cluster configuration. Static IP address used in the public IP network. Subnet mask used in the public IP network. Default Gateway used in the public IP network. 23

24 Cluster component Description Your system Standby Node public Preferred DNS server address Standby Node interconnect IP Address Standby Node Interconnect Subnet mask Static IP address of the Preferred DNS server in the public IP network. Static IP address used in the interconnect IP network. Subnet mask used in the interconnect IP network Cluster installation requirements and prerequisites It is assumed that you are familiar with the concept of clustering and how to install and configure the NEC ExpressCluster X LAN Edition for Windows. For more information, see the NEC documentation supplied with the NEC ExpressCluster software. 1. Using Control Panel > Add or Remove Programs, verify that SNMP service is installed on both servers. 2. Each server in the cluster should be equipped with a minimum of 2 network interface cards (NIC): NIC1: is a dedicated connection between the two server nodes used to manage all cluster communications i.e. the transfer of cluster information, synchronous data mirroring messages and heartbeat messages. NIC2: is used to manage all communications over the public IP network i.e. Security Center messages and heartbeat messages. Select Control Panel > Network Connections. NIC 1 should be named appropriately to its function, e.g. Interconnect or private, on both servers. NIC 2 should be named appropriately to its function, e.g. Public, on both servers. 3. NIC1 on both the Active Server and the Standby Server should have its properties configured as detailed in the NEC documentation. 4. NIC2 on both the Active Server and the Standby Server should have its properties configured as detailed in the NEC documentation. 5. Connect the Active Server node and the Standby Server node via their interconnect network and verify a healthy physical link status. 6. Connect the Active Server node and the Standby Server node via their public network and verify a healthy physical link status. 7. The allocation of a separate disk is recommended for data mirroring but it is not mandatory. You may either allocate a separate disk or choose to partition your disk. Partition the disk for each server as follows: By default the software application files reside on the C: drive. 24

25 Create a Cluster partition on the disk, for example the M: drive. The partition should not be formatted (i.e. raw) and should be a minimum of 32 MB. The drive letter and the partition size must be identical on both servers. Create a Data partition on the disk formatted as NTFS, for example the N: drive. The partition should be a minimum of 500MB to a maximum of 100GB. It should be dimensioned appropriately for the database to reside there. The drive letter and the partition size must be identical on both servers How to configure Security Center to run in a cluster configuration Setting up Security Center/Synergis in a cluster configuration requires the following procedures: 1. Installing NEC ExpressCluster on both servers in the cluster. See page Installing and configuring Security Center on both servers in the cluster. See page Configure NEC ExpressCluster X LAN Edition for Windows. See page Configure the database. See page Configure the Security Center Web Client. See page Start-up Security Center services. See page Installing NEC ExpressCluster on both servers in the cluster With nodes representing the servers that are involved in clustering for the failover feature, the following describes the installation procedure for each node. 1. Install NEC ExpressCluster X LAN Edition R2.0 for Windows on drive C: of the Active Server node. Installation requires the application of the appropriate NEC licenses. At the completion of the installation, select the option: NO, I WILL RESTART MY COMPUTER LATER. 2. Install NEC ExpressCluster X LAN Edition software on drive C: of the Standby Server node. The installation path must be exactly the same as that on the Active Server node. Installation requires the application of the appropriate NEC licenses. At the completion of the installation, select the option: NO, I WILL RESTART MY COMPUTER LATER. 3. Restart the Active Server node. 4. Restart the Standby Server node Installing and configuring Security Center on both servers in the cluster The following describes the installation procedure for each server in the cluster. 1. Install Security Center on drive C: of the Active Server node. Security Center Microsoft SQL Express as part of its InstallShield. 25

26 If the same or a different supported database has not already been created, you may install the database service that is provided by the Security Center InstallShield. Otherwise you must specify the path to the already created database. Installation requires the application of the appropriate Genetec licenses using Server Admin. 2. Use Security Center Server Admin to associate the network card of the Synergis - Access Manager with the Active Server node Public NIC. Do not associate the network card of the Directory, Integration Service, and the Watchdog with a NIC. Leave them all blank. 3. At the completion of the Security Center installation on the Active Server node: Navigate to Control Panel > Administrative Tools > Services Right-click on each of the Genetec Security Center services (i.e. Directory, Integration Service, Synergis - Access Manager and Watchdog) to access each service s properties to configure it for manual startup rather than automatic startup. Right-click on the SQL Server (SQLEXPRESS) service to access its properties to configure it for manual startup rather than automatic startup. If you are not using SQL Server Express, you must set all SQL Server related services to manual. 4. In the Services window, right-click on each service and select stop to manually stop each service in the following mandatory order: Genetec - Watchdog Genetec - Integration Service Genetec Synergis - Access Manager 26

27 Genetec - Directory All SQL Server related services 5. Install Security Center on drive C: of the Standby Server node. The installation path must be identical to that on the Active Server node. Security Center provides Microsoft SQL Express as part of its InstallShield. If the same or a different supported database type has not already been created, you may install the database service that is provided by the Security Center InstallShield. Otherwise you must specify the path to the already created database. The database installation path and the database type must be identical to that on the Active Server node. Installation requires the application of the appropriate Genetec licenses using Server Admin. 6. Copy the configuration files (found in the subfolder \ConfigurationFiles of the Security Center installation folder) from the Active Server node to the Standby Server node. The files that must be copied are: Mod.Localization Mod.MailServer Mod.Reporting Mod.WatchdogProxy Srv.AccessManager Srv.Directory Srv.IntegrationService Srv.Watchdog 7. Use Server Admin to associate the network card of the Synergis - Access Manager with the Standby Server node Public NIC. Do not associate the network card of the Directory, the Integration Service or the Watchdog with a NIC. Leave them all blank. 8. At the completion of the Security Center installation on the Standby Server node: Navigate to Control Panel > Administrative Tools > Services Right-click on each of the Genetec Security Center services (i.e. Directory, Integration Service, Synergis - Access Manager and Watchdog) to access each service s properties to configure it for manual startup rather than automatic startup. Right-click on the SQL Server (SQLEXPRESS) service (or the one you chose during installation) to access its properties to configure it for manual startup rather than automatic startup. 9. In the Services window, right-click on each service and select stop to manually stop each service in the following mandatory order: Genetec - Watchdog Genetec - Integration Service 27

28 Genetec Synergis - Access Manager Genetec - Directory All SQL Server related services Configure NEC ExpressCluster X LAN Edition for Windows See the NEC documentation for assistance. 1. Install the NEC ExpressCluster WebManager client software on a laptop or PC connected to the public IP network. 2. Using Internet Explorer on the WebManager, connect to the Cluster Manager on the Active Server. 3. Select Cluster Builder File menu and select Cluster Generation Wizard from the drop down menu. Use the Cluster Generation Wizard window to create a cluster. 4. Use the Cluster Generation Wizard window to create an Active Server and a Standby Server associated with the cluster. 5. Use the Cluster Generation Wizard window to create a Management Group associated with the cluster. 6. Use the Cluster Generation Wizard window to create a Failover Group associated with the cluster. Failover shall be automatic and Failback shall be manual. 7. Use the Cluster Generation Wizard window to create resources for the Failover Group: Create a Floating IP Resource. Create a Mirror Disk Resource. Fast synchronization shall be configured as automatic. Create a Virtual Computer Name Resource. Create a Script Resource. This shall reference two Genetec provided scripts used to start and stop all Security Center services as a group. Optionally, create a Service Resource for each of the individual services installed by Microsoft IIS version 6. These can include: WWW Publishing Service HTTP SSL Service IIS Admin Service FTP Service SMTP Service NNTP Service Create other available Resources if required. The final action to take on detection of an error shall be configured appropriately for each Failover Group resource. The default final action is Stop the cluster service and shutdown OS. Although this may be necessary when a Network Partition is detected, it is too severe for other resource failures. 28

29 If the use of the Script Resource is not considered desirable, individual Service Resources can be created instead for each of the Security Center services, i.e. Directory, Integration Service, Synergis - Access Manager, Watchdog and SQL Server. Whether using a Script Resource or individual Service Resources to start and stop Security Center services, it is mandatory that a specific order be followed. Security Center services should always be started in the following mandatory order: All SQL Server related services Genetec - Directory Genetec Synergis - Access Manager Genetec - Integration Service Genetec - Watchdog Security Center services should always be stopped in the following mandatory order: Genetec - Watchdog Genetec - Integration Service Genetec Synergis - Access Manager Genetec - Directory All SQL Server related services 8. Use the Cluster Generation Wizard window to create resources for the Management Group: Create a Floating IP Resource. 9. Use the Cluster Generation Wizard window to create Heartbeat Resources for both the Active Server and the Standby Server: Create a LAN Heartbeat Resource for the public network. Create a LAN Heartbeat Resource for the interconnect network. 10. Use the Cluster Generation Wizard window to create Network Partition Resolution Resources for both the Active Server and the Standby Server: Create a PING Resource. 11. Use the Cluster Generation Wizard window to create Monitor Resources associated with the cluster. The following lists those appropriate for Security Center others are available and can be created if required: Disk RW Monitor Mirror Disk Monitor (created automatically because of Failover Group Mirror Disk Resource) Mirror Connect Monitor (created automatically because of Failover Group Mirror Disk Resource) IP Monitor Floating IP Monitor Application Monitor 29

30 NIC Link Up/Down Monitor Service Monitor Virtual Computer Name Monitor SQL Server Monitor 12. In the Cluster Builder window, to apply the cluster configuration, click the File menu and select Upload the Configuration File. After the upload is completed, a success message is displayed and OK should be clicked. 13. Close the Cluster Builder. 14. In the Cluster Manager, click the Service menu and select Restart Manager to restart the Cluster Manager. 15. In the Cluster Manager, click the Service menu and select Start Cluster. The Cluster Manager window should update and display details of the configured cluster. 16. In the left pane of the Cluster Manager window, right-click Servers in the tree view and then click Mirror Disks. Mirror disk copying starts immediately but takes some time to complete. After the copy is completed a confirmation dialog is presented. 17. Use the Cluster Manager window to ensure that the cluster has been configured. Please note that all Security Center services and the SQL Server service on the Active Server node are now running Configure the database Enable SQL services on each computer. Bring Security Center to the cluster in the primary node. 1. Using the Cluster Manager, ensure that the cluster is started and that the Active Server is active. Select the Active Server in the Cluster Manager and using the Failover Group Resource Script, stop all the Security Center services and the SQL Server service. Manually start the SQL Server service on the Active Server. 2. Using Microsoft SQL Server Management Studio or Studio Express as appropriate: Connect to the Security Center database on the Active Server. Detach the Security Center database (from its location on the C: drive). Copy the Security Center database to its new location in the data partition of the Active Server. Re-attach to the Security Center database. Disconnect from the Security Center database. 3. Manually stop the SQL Server service again on the Active Server. 4. Using the Cluster Manager, ensure that the cluster is started and that the Standby Server is on standby. 30

31 Select the Standby Server in the Cluster Manager and using the Failover Group Resource Script, stop all the Security Center services and the SQL Server service. Manually start the SQL Server service on the Standby Server Configure the Security Center Web Client Configure Security Center Web Client to use the Virtual Computer Name of the cluster as the name of the server to which it should connect when routing calls to the Directory. This will allow it to always connect to the correct server irrespective of whether the Active Server or the Standby Server is currently the active server. 1. Using the Cluster Manager, ensure that the cluster is started and that the Active Server is active. 2. Navigate to Control Panel > Administrative Tools > Services on the Active Server. Right-click on the IIS Admin service and select Stop. 3. Access the Security Center installation folder on drive C: of the Active Server node. The default path is C:\Program Files \Genetec Security Center Open the WebClient folder. 5. Locate the file Web.Config and open it using Notepad. 6. Locate the following line <add key="accessdatastores" value=""/> in the Web.Config file. 7. Edit the line as follows: <add key="accessdatastores" value="virtual COMPUTER NAME"/> Where VIRTUAL COMPUTER NAME is that configured for the Virtual Computer Name Resource of the cluster Failover Group. 8. Navigate to Control Panel > Administrative Tools > Services on the Active Server. Right-click on the IIS Admin service and select Start. 9. Using the Cluster Manager, ensure that the cluster is started and that the Standby Server is on standby. 10. Navigate to Control Panel > Administrative Tools > Services on the Standby Server. Right-click on the IIS Admin service and select Stop. 11. Access the Security Center installation folder on drive C: of the Standby Server node. The default path is C:\Program Files \Genetec Security Center Open the WebClient folder. 13. Locate the file Web.Config and open it using Notepad. 14. Locate the following line <add key="accessdatastores" value=""/> in the Web.Config file. 15. Edit the line as follows: <add key="accessdatastores" value="virtual COMPUTER NAME"/> Where VIRTUAL COMPUTER NAME is that configured for the Virtual Computer Name Resource of the cluster Failover Group. 16. Navigate to Control Panel > Administrative Tools > Services on the Standby Server. Right-click on the IIS Admin service and select Start. 31

32 Start-up Security Center services Using the Cluster Manager, ensure that the cluster is started and that the Active Server is active. Select the Active Server in the Cluster Manager and using the Failover Group Resource Script, start all the Security Center services and the SQL server service. Security Center is now available. IMPORTANT If you need to change the configuration of the Security Center services with the Server Admin on one of the clustered server node, you must repeat the same changes manually with Server Admin on the other clustered server nodes. 32

33 7. Upgrading from Security Center 3.0 To upgrade from Security Center 3.0 (any version) to 4.0, you must first uninstall the Security Center 3.0 applications and then install the 4.0 applications Upgrading Security Center Server 1. From the Control Panel, click Add or Remove Programs, select Genetec Security Center 3.0 Server and click Remove. 2. Follow the procedure for Installing Security Center Server on page 12 up to the point where the Server Admin window appears. 3. In the Server Admin, select Directory from the resource tree and click the Database tab. The Directory database needs to be upgraded: a. Click Click here to upgrade the database. The upgrade may take a while if the database contains a lot of data. b. Click Close in the Database upgrade dialog when the status shows Completed. The Security Center Directory database is now up to date. Click the button to verify the statistics of the database (number of entities, active alarms, and archived alarms). c. Click the button at the top of Server Admin to save the updated information. 4. Select Synergis Access Manager from the resource tree and click the Database tab. The AccessManager database needs to be upgraded: a. Click Click here to upgrade the database. The upgrade may take a while if the database contains a lot of events. b. Click Close in the Database upgrade dialog when the status shows Completed. The Synergis Access Manager database is now up to date. Click the button to verify the statistics of the database (number of archived events). c. Click the button at the top of Server Admin to save the updated information. 5. Close the Server Admin and click Finish in the InstallShield Wizard to complete the server upgrade. The Security Center services will start by themselves Upgrading Security Center Client 1. From the Control Panel, click Add or Remove Programs, select Genetec Security Center 3.0 Client and click Remove. 2. Follow the procedure for Installing Security Center Client on page

34 8. Upgrading from Synergis 2.1 To upgrade from Synergis 2.1 to Security Center 4.0, you must first remove the Synergis 2.1 applications and then install the 4.0 applications Upgrading Synergis Server To upgrade from Synergis 2.1 Server to Security Center 4.0 Server: 1. From the Control Panel, click Add or Remove Programs, select Genetec Synergis 2.1 Server and click Remove. 2. Follow the procedure for Installing Security Center Server on page 12 up to the point where the Server Admin window appears. 3. In the Server Admin, select Directory from the resource tree and click the Database tab. The AccessDatastore is called the Directory in the Security Center. The previous Synergis AccessDatastore database name is automatically selected. In Security Center, the Directory database is called Directory by default. 34

35 4. A blue hyperlink appears under the Directory database field in the Server Admin, telling you that the database needs to be updated. 5. Click the hyperlink entitled Click here to upgrade the database. If you had an Omnicast external system configured in your Synergis 2.1 system, you ll see a warning message similar to the one below appear during the database upgrade. This warning means additional steps are required to update the Omnicast external system configuration after the InstallShield has completed its work, see Manual upgrade of Omnicast external systems on page

36 During the database upgrade, you may also see the following message appear. This message tells you that a conflict manifest has been generated. The conflict manifest is a list of GUIDs (Globally Unique Identifiers) that need to be converted because their processing has changed from Synergis 2 to Security Center 3. The conflict manifest must be applied to the Synergis Access Manager database as an additional step after the database conversion. Click the hyperlink entitled Locate file ConflictManifest.cm in the message box, save the path to the clipboard, and click OK to close the message box. 6. Click Close in the Database upgrade dialog when the status shows Completed. The Security Center Directory database is now up to date. Click the database (number of entities, number of alarms, etc.) button to verify the statistics of the 7. Click the button at the top of Server Admin to save the updated information. 8. In the Server Admin, select Synergis Access Datastore from the resource tree and click the Database tab. 9. Click the hyperlink entitled Click here to upgrade the database. The upgrade may take a long time (half an hour to one hour) if the database contains a lot of events. 10. Click Close in the Database upgrade dialog when the status shows Completed. If you were told to perform an optional step during the Directory database upgrade, click the next to Database to process the conflict manifest. The Conflict resolution dialog box appears. button Click to open a file browser and paste the path to the ConflictManifest.cm file that you saved in Step 5. The Conflict resolution tool will start processing the conflict manifest. Click OK when the processing ends. 36

37 The Synergis Access Manager database is now up to date. Click the button to verify the statistics of the database (number of archived events). 11. Click the button at the top of Server Admin to save the updated information. 12. Close the Server Admin and click Finish in the InstallShield Wizard to complete the server upgrade. 13. Restart the computer Upgrading Synergis Client 1. From the Control Panel, click Add or Remove Programs, select Genetec Synergis 2.1 Client and click Remove. 2. Follow the procedure for Installing Security Center Client on page Upgrade issues from Synergis 2.1 to Security Center Limitations Certain settings in Synergis 2.1 are not available in the Security Center 4.0 because the concept has changed or is no longer supported. Please read carefully the following list. Certain features may require you to reconfigure part of your system. Issue Description After upgrading from Synergis 2.1 to Security Center 4.0, users who could acknowledge alarms found in Synergis Default partition will no longer be able to do the same in Security Center. To restore their original privileges, you need to add them as Accepted users of the Security Center s Public partition. To learn more about the Security Center s security model, refer to Security partitions in the Security Center 4.0 Administrator Guide The maximum delay for automatic alarm acknowledgement has been reduced from seconds to 5000 seconds in Security Center. Therefore, all values higher than 5000 seconds in Synergis will be set to 5000 in Security Center after the upgrade. No warning will be issued Monitoring and tracking layouts will be lost after an upgrade. The old Synergis layouts have been replaced by tasks in the Security Center. You ll have to create Monitoring tasks in the new Security Desk to replace them Hot actions will be lost after an upgrade. In Security Center, hot actions are no longer associated to users, but to Monitoring tasks, in the Actions tab. Since a user may create multiple monitoring tasks, multiple sets of hot actions can be defined for a same user. To learn more, refer to Hot actions and alarms in Genetec Security Desk User Guide None of the Synergis SecurityDesk options will be preserved after an upgrade since the Security Desk in Security Center is a completely different application. To learn more about the new options, refer to Customizing Security Desk in Genetec Security Desk User Guide All Synergis XAML maps and macros must be modified manually in Security Center after an upgrade. Please contact Genetec Technical Assistance for details The user privilege structure has been completely redesigned in Security Center. It is highly recommended to verify all your user privileges after the upgrade. 37

38 Issue Description Certain standard Visitor fields in Synergis 2.1x are converted into custom fields in Security Center 4.0. They are: Company (Text) Visitor's escort first name (Text) Visitor's escort last name (Text) Escort (Entity) Visit reason (Text) Phone number (Text) You ll have to set the visibility of these custom fields manually in the Config Tool. To learn how to edit a custom field, refer to Adding a custom field in Security Center Administrator Guide Known upgrade issues Certain aspects of Synergis 2.1 configuration are not completely upgraded to Security Center 4.0 by the InstallShield. Issue Description Badge templates are lost during the upgrade to 4.0. You ll need to recreate them The value of Timeout under Report options is not preserved after the upgrade Manual upgrade of Omnicast external systems You need to perform the following extra steps in the Config Tool if you get a warning message such as this during the database upgrade: To complete the Omnicast external system upgrade: 1. Start the Security Center Config Tool. For more information about the new Config Tool user interface, refer to About Config Tool in the Security Center Administrator Guide. 2. In the Config Tool entity selector, select Network view. 3. Expand the entity tree and select an Omnicast external system ( ). 38

39 The external systems are found under the Integration Services ( ). 4. Click the Properties tab. Do the following: a. Assign an Integration Service to the external system. b. Change the Version of Omnicast. Make sure that the required compatibility pack is installed. c. Select the Supported Omnicast events. For more information about this tab, refer to Configure Omnicast ES properties in the Security Center Administrator Guide. 5. Click in the Config Tool toolbar to save your changes. 6. Proceed with the next Omnicast external system if necessary. 39

40 9. Migrating from a previous version of AutoVu Security Center is the unified platform for managing all fixed and mobile Sharp units. The mobile Sharp units are vehicle mounted Sharp units for Law Enforcement and Parking Enforcement. The following changes have been made to AutoVu for Security Center: Back Office is replaced by Security Center. Management of all LPR data (reads, hits, vehicle positions) is handled by the AutoVu LPR Manager module in Security Center. Back Office desktop is replaced by Security Desk. To migrate from earlier versions (4.0 to 4.3) of AutoVu to Security Center 4.0, do the following: 1. Set up an AutoVu LPR Manager in Security Center. The AutoVu LPR Manager will gradually replace the AutoVu Back Office. The migration is likely to take a few days, if not weeks. While you are performing the migration, your old AutoVu system remains fully operational. For instructions, see Setting up the AutoVu LPR Manager on page Upgrade all Sharp units and Patrollers to 4.4. One by one, upgrade the Sharp PlateReaderServer and Patroller applications to 4.4. Once a Sharp unit or Patroller is upgraded to 4.4, it can no longer offload data to the AutoVu Back Office. The new AutoVu LPR Manager of Security Center 4.0 will immediately take charge of these units. For upgrade instructions, see the following guides: AutoVu Hardware Installation Guide for Sharp units upgrade. AutoVu Patroller Administrator Guide for Patrolller application upgrade. For instructions on how to manage upgraded LPR units in Security Center, see the following guides: LPR unit configuration in the Security Center Administrator Guide, for Sharp units. Patroller configuration in the Security Center Administrator Guide, for Patrollers. 3. (Optional) Copy the MapInfo files to the Maps folder. If you are using MapInfo in Security Desk, copy your MapInfo files to a folder named Maps under the Security Center installation folder. For example: C:\Program Files\Genetec Security Center 4.0\Maps\. Repeat this operation on every Security Desk workstation where MapInfo maps will be used. 4. Turn off the old system. Once the upgrade to PlateReaderServer 4.4 and Patroller 4.4 is complete, let both systems run for another three days before turning your old system off. 40

41 This precaution is to give enough time to the old system to finish processing all offloaded data and to the new system to import them before turning the switch off Setting up the AutoVu LPR Manager 1. Install Security Center 4.0 system or upgrade from an earlier version if you were already using Security Center for access control and video surveillance. For instructions on installing Security Center, see Installing Security Center on page Create an AutoVu LPR Manager on your Security Center 4.0 system. AutoVu LPR Manager in Security Center is the module that replaces AutoVu Back Office. For instructions on how to create and configure an AutoVu LPR Manager, see Unification of AutoVu systems in the Security Center Administrator Guide. If you need to move the AutoVu LPR Manager database to a different location than the default one, follow the procedure described in Changing the location of the LPR Manager database on page Configure the LPR data retention periods on the AutoVu LPR Manager. In earlier versions of AutoVu, the following parameters were used to set the LPR data retention period: DBCleaner.FlagDayForCleanup (for reads, unit states and Patroller positions) DBCleaner.FlagDayForCleanupHit (for hits) In Security Center/AutoVu LPR Manager, the following parameters are used to set the LPR retention period: Patroller route retention period Hit retention period Read retention period Event retention period The new retention periods must be equal or longer than the old parameters for all the data to be fully imported into the new system. For example, Read retention period should be greater or equal to FlagDayForCleanup, and Hit retention period should be greater or equal to FlagDayForCleanupHit. These settings are found under General settings in the Options tab of the AutoVu LPR Manager entity in the Config Tool. For more information, see Configure the LPR Manager options in the Security Center Administrator Guide. 4. (Optional: for Parking enforcement only). Import zone definitions from the legacy AutoVu system to the new system. What used to be called zones in the legacy AutoVu system are called Permits, Permit restrictions, and Overtime rules in Security Center. These entities are called LPR rules. For more information about these terms, see the Glossary at the end of the Security Center Administrator Guide. Zone import is only supported for AutoVu 4.1, 4.2 and 4.3 systems. To import the zones: a. Copy the zones.xml file to the Root folder of the AutoVu LPR Manager. 41

42 The Root folder is defined under General settings in the Options tab of the AutoVu LPR Manager in the Config Tool. Once the file is copied, AutoVu LPR Manager automatically creates the corresponding overtime rules, permits, and permit restrictions in Security Center. The only exception is the long term parking zone. It will not be created automatically for you. b. If a long term parking zone was in use in your legacy AutoVu system, you will have to manually create an Overtime rule in Security Center for it. For more information, see Overtime configuration in the Security Center Administrator Guide. c. For every Permit entity (list of permit holders) created by the system, you need to configure the path and the parsing of the permit holder data file. For more instructions, see Permit configuration in the Security Center Administrator Guide. 5. Connect AutoVu LPR Manager to your existing AutoVu Back Office database. a. Select the Options tab of the AutoVu LPR Manager in the Config Tool. b. Select the Data import option, but do not turn it on yet! c. Configure the Data server and the Database name of the existing Back Office database. d. Turn the Data import option ON and click. The data import starts immediately. Notes The first time you run this migration, AutoVu LPR Manager will import everything that is in the existing Back Office database, from the most recent up to the limits of the retention periods defined for the AutoVu LPR Manager. Count approximately one hour for every 2.5 GB of data to transfer. For example, if you have 100 GB of data, the whole process will take approximately 40 hours. 42

43 As data from the legacy system is imported into Security Center, you can see the Patrollers and LPR units (Sharp units) being created under the AutoVu LPR Manager in the Config Tool. All imported units appear as inactive (red) in Security Center. This is normal. Other than the time zone (under the Location tab), there is not much you can configure for an imported AutoVu Patroller unit. A few hours after the import process started, you can start using the data with Security Desk. All legacy data will be associated to the new LPR rules automatically created by LPR Manager. The only exception are hits associated to the long term parking zone. They are associated to the Unknown rule. For instructions on how to use the Security Desk to view the legacy data, see LPR reports in the Genetec Security Desk User Guide. After the first round of data import is complete, the process will repeat itself every 12 hours. In the mean time, the old system can operate as usual. 6. If hotlists were in use in your legacy AutoVu system, corresponding Hotlist entities will be created by the LPR Manager. You need to configure the hotlist data files for each of them. For more instructions, see Hotlist configuration in the Security Center Administrator Guide. 43

44 9.2. Configuring SQL Server 2008 for AutoVu When using your own SQL Server 2008 database instance for AutoVu, do the following: 1. Set the memory usage of the database instance in SQL Management Studio to be lower than the maximum memory available on the computer. Tip Half of the total available memory is usually a good value. 2. Enable FILESTREAM. a. Start Sql Server Configuration Manager. b. Right-click the database instance for AutoVu and select Properties. c. Select the FILESTREAM tab and select the Enable FILESTREAM for Transact-SQL access option. d. Click OK and restart the database instance. 44