Security Center Installation and Upgrade Guide 5.1 GA - Genetec

Security Center 

Installation and Upgrade Guide 

5.1 GA 

Click here for the most recent version of this document.

Copyright notice 

© 2011, 2012 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", "Security Center Mobile", "Plan Manager", 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 information 

Document title: Security Center Installation and Upgrade Guide 5.1 GA 

Document number: EN.500.002-V5.1.B(4) 

Document update date: January 19, 2012 

You can send your comments, corrections, and suggestions about this guide to 

documentation@genetec.com. 

Product documentation 

Security Center includes the following documentation: 

• Security Center Release Notes. Describes the release in detail, including new features, resolved issues, 

known issues, and limitations. 

• Security Center Installation and Upgrade Guide. Describes the prerequisites for installing Security 

Center, and provides instructions for installing and upgrading Security Center on your system. 

• Security Center Administrator Guide. Provides all the instructions and conceptual information you’ll 

need to set up, configure, and administer your Security Center system. 

• Getting Started with Security Desk. A task-oriented introduction to Security Desk that uses real-world 

scenarios (viewing a camera, searching/exporting video, and managing alarms) to show new users how 

to use the basic product features. 

ii 

genetec.com | Security Center 5.1 | Installation and Upgrade Guide | Download latest version 

EN.500.002-V5.1.B(4)

• Genetec Security Desk User Guide. Provides the instructions and conceptual information you need to 

get started with Security Desk, to monitor and generate reports for AutoVu LPR, Omnicast video 

surveillance, and Synergis access control systems. 

• Security Center Video Unit Configuration Guide. Provides the pre-configuration instructions for 

integrating video units into Security Center, and any configuration steps required for some video unit 

features to work. 

• Security Center Portable Archive Player User Guide. Explains how to use the Portable Archive Player to 

view exported video files. 

• AutoVu Patroller Release Notes. Describes the AutoVu Patroller release in detail, including new 

features, resolved issues, known issues, and limitations. 

• AutoVu Hardware Release Notes. Describes the AutoVu Hardware for this release in detail, including 

new features, resolved issues, known issues, and limitations. 

• AutoVu Handbook. Provides AutoVu installers and administrators with a single source of information 

about installing and configuring AutoVu hardware and software. 

• AutoVu Patroller User Guides. Quick reference guides to using Patroller, AutoVu’s mobile LPR solution. 

There is a separate user guide for each Patroller installation type (Law Enforcement, City Parking 

Enforcement, City Parking Enforcement with Wheel Imaging, University Parking Enforcement, and 

Mobile License Plate Inventory). 

• AutoVu Connecting the Sharp Camera. Explains how to power up and connect your Sharp. A printed 

version is provided in the Sharp box. 

• AutoVu Connecting the SharpX Camera. Explains how to power up and connect your SharpX. A printed 

version is provided in the SharpX box. 

• Plugin User Guides. Introduces you to the plugin features and describes what’s new in the current 

release. It also explains how to install and configure the plugin in Security Center, and how to use it in 

Security Desk. 

Where can I find the product documentation 

• Product DVD. The documentation is available on the product DVD in the Documentation folder. Release 

notes and installation guides include a direct link to the latest version of the document. 

• Genetec Technical Assistance Portal (GTAP). The latest version of the documentation is available from 

GTAP. Note, you’ll need a username and password to log on to GTAP. 

• Online help. Security Center client applications include online help, which explain how the product 

works and provide instructions on how to use the product features. Patroller and the Sharp portal also 

include context-sensitive help for each screen. To access the online help, click Help, press F1, or tap 

the (question mark) in the different client applications. 


EN.500.002-V5.1.B(4) 

iii

Technical support 

Genetec Technical Assistance Center (GTAC) is committed to providing its worldwide clientele with the best 

technical support services available. As a Genetec customer, you have access to the Genetec Technical 

Assistance Portal (GTAP), where you can find information and search for answers to your product questions. 

• Genetec Technical Assistance Portal (GTAP). GTAP is a support website that provides in-depth support 

information, such as FAQs, knowledge base articles, user guides, supported device lists, training videos, 

product tools, and much more. 

Prior to contacting GTAC or opening a support case, it is important to look at this website for potential 

fixes, workarounds, or known issues. You can log in to GTAP or sign up at https://gtap.genetec.com. 

• Genetec Technical Assistance Center (GTAC). If you cannot find your answers on GTAP, you can open a 

support case online at https://gtap.genetec.com. For GTAC's contact information in your region see the 

Contact page at https://gtap.genetec.com. 

NOTE Before contacting GTAC, please have your System ID (available from the About button in your client 

application) and your SMA contract number (if applicable) ready. 

• Licensing. 

• For license activations or resets, please contact GTAC at https://gtap.genetec.com. 

• For issues with license content or part numbers, or concerns about an order, please contact Genetec 

Customer Service at customerservice@genetec.com, or call 1-866-684-8006 (option #3). 

• If you require a demo license or have questions regarding pricing, please contact Genetec Sales at 

sales@genetec.com, or call 1-866-684-8006 (option #2). 

Additional resources 

If you require additional resources other than the Genetec Technical Assistance Center, the following is 

available to you: 

• GTAP Forum. The Forum is an easy to use message board that allows clients and Genetec staff to communicate 

with each other and discuss a variety of topics, ranging from technical questions to technology 

tips. You can log in or sign up at https://gtapforum.genetec.com. 

• Technical training. In a professional classroom environment or from the convenience of your own office, 

our qualified trainers can guide you through system design, installation, operation, and troubleshooting. 

Technical training services are offered for all products and for customers with a varied level of technical 

experience, and can be customized to meet your specific needs and objectives. For more information, go 

to http://www.genetec.com/English/Support/Training. 

iv 



Contents 

Product documentation . . . . . . . . . . . . . . . . . . ii 

Technical support . . . . . . . . . . . . . . . . . . . iv 

About this guide . . . . . . . . . . . . . . . . . . . . ix 

Chapter 1: Before you install 

Read the Release Notes . . . . . . . . . . . . . . . . . 2 

System requirements . . . . . . . . . . . . . . . . . . 2 

Server hardware requirements . . . . . . . . . . . . . . . 2 

Client hardware requirements . . . . . . . . . . . . . . . 3 

Client and Server software requirements . . . . . . . . . . . . 4 

Preinstallation tasks . . . . . . . . . . . . . . . . . . 5 

Administrator privileges . . . . . . . . . . . . . . . . 5 

Internet access required to extract license . . . . . . . . . . . . 5 

Acquire System ID and password . . . . . . . . . . . . . . 5 

Turn off power saving features . . . . . . . . . . . . . . . 5 

Back up system databases . . . . . . . . . . . . . . . . 6 

Before you install Genetec Server on Windows 7 . . . . . . . . . . 6 

Chapter 2: Installing Security Center 5.1 

About the Security Center installation package . . . . . . . . . . . 8 

Where can I find the installation package . . . . . . . . . . . . 8 

Installation modes . . . . . . . . . . . . . . . . . . 8 

Installer languages . . . . . . . . . . . . . . . . . . 8 

What’s in the installation package . . . . . . . . . . . . . . 8 

Installation overview . . . . . . . . . . . . . . . . . . 10 

Install Security Center on a main server . . . . . . . . . . . . . 11 

Activate your license . . . . . . . . . . . . . . . . . 19 

Web activation . . . . . . . . . . . . . . . . . . 19 

Manual license activation . . . . . . . . . . . . . . . 21 



v

Install an expansion server. . . . . . . . . . . . . . . . . 24 

Connect the expansion server to the main server. . . . . . . . . . . 31 

Install Security Center Client . . . . . . . . . . . . . . . . 33 

Install Omnicast compatibility packs . . . . . . . . . . . . . . 35 

Open ports on your company’s firewalls . . . . . . . . . . . . . 36 

Installing plugins . . . . . . . . . . . . . . . . . . . 38 

Enable Point-of-Sale plugin . . . . . . . . . . . . . . . . 38 

Install Microsoft hotfix . . . . . . . . . . . . . . . . . 39 

Convert a main server to an expansion server . . . . . . . . . . . . 40 

Uninstall Security Center components. . . . . . . . . . . . . . 40 

Chapter 3: Upgrading to Security Center 5.1 

Before you upgrade . . . . . . . . . . . . . . . . . . 42 

Before you upgrade from 5.0 to 5.1 . . . . . . . . . . . . . . 42 

Before you upgrade from 3.0 or 4.0 to 5.1 . . . . . . . . . . . . 42 

Upgrade overview . . . . . . . . . . . . . . . . . . . 44 

Upgrade overview from 5.0 to 5.1 GA . . . . . . . . . . . . . 44 

Upgrade overview from 3.0 or 4.0 to 5.1 GA . . . . . . . . . . . . 45 

Upgrade the main server . . . . . . . . . . . . . . . . . 46 

Upgrade an expansion server . . . . . . . . . . . . . . . . 47 

Upgrade Security Center Client . . . . . . . . . . . . . . . 47 

Enabling inactive roles after you upgrade from 3.0 or 4.0 . . . . . . . . . 48 

Enable the Access Manager . . . . . . . . . . . . . . . . 49 

Enable the Active Directory . . . . . . . . . . . . . . . . 49 

Enable the LPR Manager . . . . . . . . . . . . . . . . 49 

Enable the Omnicast Federation. . . . . . . . . . . . . . . 50 

Enable the Security Center Federation . . . . . . . . . . . . . 50 

Upgrade zone entities . . . . . . . . . . . . . . . . . 50 

Chapter 4: Installing Security Center in Silent Mode 

About Silent Mode . . . . . . . . . . . . . . . . . . . 52 

Limitations . . . . . . . . . . . . . . . . . . . . 52 

Before you install . . . . . . . . . . . . . . . . . . . 53 

vi 



Software prerequisites . . . . . . . . . . . . . . . . . 53 

Preinstallation tasks . . . . . . . . . . . . . . . . . 54 

Installing Security Center in Silent Mode . . . . . . . . . . . . . 55 

Silent install command . . . . . . . . . . . . . . . . . 55 

Installer options . . . . . . . . . . . . . . . . . . 56 

Sample server installation commands . . . . . . . . . . . . . 59 

Sample client installation commands . . . . . . . . . . . . . 59 

Install Security Center in Silent Mode . . . . . . . . . . . . . 60 

Uninstall Security Center in Silent Mode . . . . . . . . . . . . 60 

Chapter 5: Migrating from Omnicast 4.5 and later 

About the migration tool . . . . . . . . . . . . . . . . . 62 

Before you migrate . . . . . . . . . . . . . . . . . . 63 

What’s not migrated from Omnicast to Security Center. . . . . . . . . 64 

What’s included in Directory migration . . . . . . . . . . . . 66 

About Archiver migration . . . . . . . . . . . . . . . . 71 

What’s included in Archiver migration . . . . . . . . . . . . 71 

What’s not included in Archiver migration . . . . . . . . . . . 71 

How Omnicast Archiver setups are migrated . . . . . . . . . . 72 

Migration overview . . . . . . . . . . . . . . . . . . 73 

Run the Migration tool . . . . . . . . . . . . . . . . . 74 

Omnicast to Security Center migration scenarios. . . . . . . . . . . 76 

Scenario #1: Migrate a stand-alone Omnicast system to a Security Center system on the same 

server . . . . . . . . . . . . . . . . . . . . . 76 

Scenario #2: Migrate a stand-alone Omnicast system to a Security Center system on a 

different server . . . . . . . . . . . . . . . . . . . 78 

Scenario #3: Migrate a federated Omnicast system to a federated Security Center system 80 

Scenario #4: Migrate and merge a federated Omnicast system to its federation host on the 

same server . . . . . . . . . . . . . . . . . . . . 82 

Scenario #5: Migrate and merge a federated Omnicast system to its federation host on a 

different server . . . . . . . . . . . . . . . . . . . 84 

Enabling remote connections . . . . . . . . . . . . . . . . 86 

Process overview . . . . . . . . . . . . . . . . . . 86 

Download Microsoft SQL Server 2008 Management Studio . . . . . . . . 86 



vii

Allow remote connections . . . . . . . . . . . . . . . . 87 

Enable remote connections . . . . . . . . . . . . . . . . 88 

Enable remote connections for SQL Server 2008 . . . . . . . . . . 88 

Enable remote connections for SQL Server 2005 . . . . . . . . . . 90 

Run the Migration tool in silent mode . . . . . . . . . . . . . . 92 

Migration tool command syntax . . . . . . . . . . . . . 92 

About the command line options . . . . . . . . . . . . . 92 

Sample commands . . . . . . . . . . . . . . . . . 93 

viii 



About this guide 

This guide explains how to install and upgrade Security Center components. It also explains 

how to migrate from Omnicast 4.x to Security Center. 

This guide assumes you are familiar with the following concepts and systems: 

• Microsoft Windows administration 

• Installation, configuration, and use of Microsoft SQL Server 2008 

This guide is organized into the following chapters: 

• Chapter 1, “Before you install”. Describes the things you should know and do before 

you install or upgrade Security Center. 

• Chapter 2, “Installing Security Center 5.1”. Explains how to install Security Center 

components. 

• Chapter 3, “Upgrading to Security Center 5.1”. Explains how to upgrade an earlier version 

of Security Center to version 5.1. 

• Chapter 4, “Installing Security Center in Silent Mode”. Explains how to automate the 

process of installing Security Center. 

• Chapter 5, “Migrating from Omnicast 4.5 and later”. Explains how to migrate Omnicast 

4.5 and later systems to Security Center 5.1. 



ix

1 

Before you install 

This section describes the things you should know and do before you install or upgrade 

Security Center 5.1 GA. 

This section includes the following topics: 

• "Read the Release Notes" on page 2 

• " System requirements" on page 2 

• "Preinstallation tasks" on page 5 

genetec.com | Security Center 5.1 | Installation and Upgrade Guide | Download latest version 1 


Before you install | Read the Release Notes 

Read the Release Notes 

Before you install and upgrade Security Center, read the Security Center Release Notes for 

any known issues and other information about the release. Click here for the most recent 

version of this document. It is also available for download from the GTAP Product 

Download page, at https://gtap.genetec.com. 

NOTE You will need a username and password to log on to GTAP. 

System requirements 

This section describes the Security Center 5.1 GA hardware and software requirements. 


• "Server hardware requirements" on page 2 

• "Client hardware requirements" on page 3 

• "Client and Server software requirements" on page 4 

Server hardware requirements 

The server hardware requirements depend on the product solutions included in your 

Security Center (AutoVu, Omnicast, Synergis, or a combination thereof). To determine 

which hardware configuration best suits your needs, contact the Genetec Sales Engineering 

team at salesengineering@genetec.com. 

Configuration 

Low 

Medium 

Server hardware requirements a 

Intel® Core® 2 Duo 3.0 GHz or better 

• 2 GB of RAM or more 

• 80 GB hard drive for OS and Security Center applications 

• 4 GB of free disk space to install and run Security Center 

• Standard SVGA video card 

• 1024 x 768 or higher screen resolution 

• 100/1000 Ethernet Network Interface Card 

• DVD ROM drive 

Dual Core® Intel® Xeon® 2.66 GHz or better 


• 80 GB hard drive for OS and Security Center applications 





• DVD ROM Drive 

2 genetec.com | Security Center 5.1 | Installation and Upgrade Guide | Download latest version 


Before you install | System requirements 

Configuration 

High 

Server hardware requirements a 

Windows Server 2008 64-bitIntel® Core®i7 950 or better 


• 80 GB SATA II hard drive for OS and Security Center applications 





• DVD ROM Drive 

a. Archivers may record up to 300 cameras depending on the server's configuration and the 

recording quality settings. To determine which configuration is best suited for you, contact 

Sales Engineering at salesengineering@genetec.com. 

Client hardware requirements 

The Security Center 5.1 GA client requirements are the same for all product solutions. 

Configuration 

Low 

Medium 

High 

Client Hardware requirements 

Intel® Core®2 X6800 @ 2.93 GHz or better 


• 80 GB hard drive for OS and Security Center applications. After the 

installation, you must have at least 8 GB of free disk space to run Security 

Center. 

• 256 MB PCI-Express x16 dual-head video adapter 


• 10/100/1000 Ethernet Network Interface Card 

• 16x DVD+/- RW Drive a 

Intel® Core®i7 870 @2.93 GHzDuo 3.0 GHz or better 

• 8 GB of RAM DDR3 or more 



• 512 MB PCI-Express x16 dual-head video adapter 



• 16x DVD+/- RW Drive b 

Intel® Core®i7 2600 @3.4 GHz or better 

• 8 GB of RAM DDR3 or more 



• NVidia GTX 570 or DirectX VA 2.0 compatible with 1 GB of RAM 



• 16x DVD+/- RW Drive b 

a. A DVD+/- RW drive is recommended in order to export archived video sequences. 



Before you install | System requirements 

Client and Server software requirements 

Security Center client and server components share the same software requirements. 

Category 

Operating 

System a 

Spreadsheet b 

Database Engine 

for Omnicast 

and Synergis 

Database Engine 

for AutoVu 

Required/Supported software 

• Microsoft® Windows 7 Professional SP1 and Ultimate (32-bit/64-bit) 

• Windows XP Pro SP3 (32-bit/64-bit) 

• Windows Server® 2003 Standard Edition SP1/SP2 (32-bit/64-bit) 

• Windows Server® 2003 Standard Edition R2 (32-bit/64-bit) 

• Windows Server® 2003 Enterprise Edition SP1/SP2 (32-bit/64-bit) 

• Windows Server® 2003 Enterprise Edition R2 (32-bit/64-bit) 

• Windows Server® 2008 Standard Edition SP2 (32-bit/64-bit) 

• Windows Server® 2008 Standard Edition R2 SP1 (32-bit/64-bit) 

• Windows Server® 2008 Enterprise Edition SP2 (32-bit/64-bit) 

• Windows Server® 2008 Enterprise Edition R2 SP1 (32-bit/64-bit) 

• Microsoft® Excel 2007 or later 

• SQL Server 2005 Express/Standard c /Enterprise SP2/SP3/SP4 

• SQL Server 2008 Express/Standard c /Enterprise R2 

• SQL Server 2008 Express/Standard c /Enterprise R2 d 

Browsers • Microsoft Internet Explorer (32-bit) 7, 8, 9 

Virtualization • VMware vSphere 4.1 (client) 

• VMware ESx/ESXi 4.0/4.1 (server) 

a. Installation of the Security Center and AutoVu is not supported on a Windows 2003/2008 Server 

running a Domain Controller. 

b. Used to view Security Desk reports in Excel. 

c. SQL Server Standard Edition is required for Directory database mirroring. 

d. If Security Center manages more than five Patrollers, or if you intend to keep your LPR data over 

30 days, use SQL Server 2008 Standard Edition instead of the Express Edition. For a SharpX system 

capturing high resolution context images, the Express Edition can store approximately 

218,000 reads or hits. 



Before you install | Preinstallation tasks 

Preinstallation tasks 

This section describes the things you’ll need to do before you install or upgrade Security 

Center. 


• "Administrator privileges" on page 5 

• "Internet access required to extract license" on page 5 

• "Acquire System ID and password" on page 5 

• "Turn off power saving features" on page 5 

• "Back up system databases" on page 6 

• "Before you install Genetec Server on Windows 7" on page 6 

Administrator privileges 

To install Security Center, you'll need to log on as administrator of the local computer. Make 

sure you have administrator privileges before you install. 

Internet access required to extract license 

You'll need to connect to the Genetec website in order to submit your validation key and to 

extract your license. This applies to the main server (computer hosting the Directory role) 

installation only. 

If the main server does not have Internet access, you can save the validation key to a file, 

and then apply for the license from another computer that has Internet access. 

Acquire System ID and password 

To activate your license on the main server you will need to know your System ID and 

password, found in the Security Center License Information document. Genetec Technical 

Support sends you this document when you purchase the product. 

Turn off power saving features 

Turn off hibernation on computers hosting Genetec Server or any database used by Genetec 

Server. 



Before you install | Preinstallation tasks 

Back up system databases 

Best practice: Before you upgrade, back up all your system databases. For information on 

how to back up your system databases, see the Security Center Administrator Guide of your 

current Security Center version. 

Before you install Genetec Server on Windows 7 

Make sure that Microsoft .NET Framework 3.5 SP1 is activated on Windows 7. 

1 Choose Start > Control Panel > Programs and Features. 

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 3.5.1 

option, and click OK. 



2 

Installing Security Center 5.1 

This section explains how to install Security Center components. It also describes the 

Security Center installation package. 


• "About the Security Center installation package" on page 8 

• "Installation overview" on page 10 

• "Install Security Center on a main server" on page 11 

• "Install an expansion server" on page 24 

• "Install Security Center Client" on page 33 

• "Install Omnicast compatibility packs" on page 35 

• "Open ports on your company’s firewalls" on page 36 

• "Installing plugins" on page 38 

• "Install Microsoft hotfix" on page 39 

• "Convert a main server to an expansion server" on page 40 

• "Uninstall Security Center components" on page 40 



Installing Security Center 5.1 | About the Security Center installation package 

About the Security Center installation package 


• "Where can I find the installation package" on page 8 

• "Installation modes" on page 8 

• "Installer languages" on page 8 

• "What’s in the installation package" on page 8 

Where can I find the installation package 

Installation modes 

Installer languages 

The Security Center installation package is available on DVD or for download from the 

GTAP Product Download page, at https://gtap.genetec.com. 


You can run the Security Center installer in two modes: 

• Wizard mode. The Genetec Security Center InstallShield Wizard appears when you 

insert the Security Center DVD into your DVD drive, or when you double-click 

setup.exe found in the root folder of your installation package. 

• Silent mode. The silent mode is used to run the installer in an automated way without 

user intervention. For more information, see "Installing Security Center in Silent 

Mode" on page 51. 

The Security Center installer is available in English and French. You can select the language 

in the InstallShield Wizard. 

What’s in the installation package 

In Security Center 5.1 GA, the Client and Server InstallShield Wizards have been merged 

into one installer from which you can install all Security Center components. The Security 

Center 5.1 installation package includes the following: 

• setup.exe. The Security Center InstallShield Wizard, from which you can install the following 

applications: 

• Genetec Server. The server component of Security Center. Genetec Server is the 

Windows service that must be installed on every server computer in your Security 

Center system. Once installed on a computer, that computer becomes part of your 

system’s pool of servers. 



Installing Security Center 5.1 | About the Security Center installation package 

• Config Tool. The client application used to configure and administer your Security 

Center system. 

• Security Desk. The task-based, unified user interface of Security Center. 

• Tools. This folder includes the following additional applications and tools: 

• \Access\HID VertX. Discovery tool. A tool that allows you to discover HID units 

connected to your network. Once discovered, the units can be added to your system. 

• \BoschSDK. The Bosch Video SDK application, and online help. 

• \Clustering\NEC Cluster. Scripts for NEC failover purposes, and technical documentation 

on how to configure Security Center with NEC Clustering. 

• \Clustering\Windows Cluster. Technical documentation on how to configure Security 

Center with Windows Clustering. 

• \LPR\MapInfo. MapInfo installation package. 

• \LPR\SecurityDesk. Custom tasks for Security Desk. 

• \LPR\Sharp. Plate Reader Server software. 

• \LPR\XMLTemplatesSamples\XMLExport. XML Export sample template files. 

• \LPR\XMLTemplatesSamples\XMLImport. XML Import sample template files. 

• \Open Source Libraries. Information about the open source libraries used by Security 

Center applications. 

• \Portable Archive Player. Portable Archiver Player.exe and online help. 

• \Video. VideoFileAnalyser.exe used by Technical Support and Field engineers to 

analyze the content of video files (G64). 

• \VisiowaveCodec. Interlogix Visiowave codec drivers setup.exe. 

• \WireShark. Network monitoring freeware useful for gathering diagnosis information 

when contacting Genetec Technical Assistance. 

• Compatibility packs. This folder includes the Omnicast compatibility packs you’ll 

need to install if federating Omnicast to Security Center. It includes compatibility 

packs for Omnicast 4.6, 4.7, and 4.8. If you need the compatibility packs for earlier versions 

of Omnicast, please contact Genetec Technical Assistance. 

• Documentation. This folder contains the PDF versions of Security Center documentation, 

and some documentation on supported third-party hardware. For a list of available 

documentation, see "Product documentation" on page ii. 



Installing Security Center 5.1 | Installation overview 

Installation overview 

The following table summarizes the Security Center installation process: 

Phase Description See 

1 Create a list of the computers that will be part of your new system, and 

decide what Security Center components need to be installed on each: 

Security Center Server (main or expansion server) 

Security Center Client (Config Tool, Security Desk, or both) 

" System requirements" on 

page 2. 

2 Perform any preinstallation tasks. "Preinstallation tasks" on page 5. 

3 Install Security Center components on the main server that will host the 

directory role. 

"Install Security Center on a 

main server" on page 11. 

4 Activate your product license on the main server. "Activate your license" on 

page 19. 

5 Install Security Center components on any expansion servers that will 

connect to the main server to add processing power to your Security 

Center system. 

"Install an expansion server" 

on page 24. 

6 Install Security Center Client (Config Tool, Security Desk, or both). "Install Security Center Client" 

on page 33 

7 If Omnicast systems will be federated to Security Center, install their 

compatibility packs on every computer where Security Center 

components (Server or Client) are installed. You need a different 

compatibility pack for each version of Omnicast you federate. 

8 Make sure that all ports used by Security Center are open and redirected 

for firewall and network address translation purposes. 

"Install Omnicast 

compatibility packs" on 

page 35. 

"Open ports on your company’s 

firewalls" on page 36 

9 Install any Security Center plugins. "Installing plugins" on page 38. 

10 If required, install the Microsoft hotfix. "Install Microsoft hotfix" on 

page 39. 

11 After the installation, connect to the main server with Config Tool and 

configure your entire Security Center system. 

See the Omnicast or Synergis 

“Deployment” chapters in the 

Security Center Administrator 

Guide, or the AutoVu 

deployment chapters in the 

AutoVu Handbook. 



Installing Security Center 5.1 | Install Security Center on a main server 

Install Security Center on a main server 

The main server is the only server in your Security Center system that hosts the Directory 

role. It must be installed first so that other servers can connect to it. You must also activate 

your Security Center license on the main server. 

The main server installation procedure installs the following: 

• The Genetec Server service with the Directory role. When installing the Genetec 

Server, the Directory database, the web-based Server Admin, and the Watchdog service 

are also installed. 

• (Optional) Client applications (Config Tool, Security Desk, or both). 

Before you begin: Read "Before you install" on page 1. 

1 Insert and display the Security Center DVD, or double-click setup.exe in the root folder 

of the Security Center installation package. 

The Security Center Installation dialog box opens. 

2 In the lower-right corner of the dialog box, select the installation language (English or 

French). 

3 Click Security Center installation. 

4 If you are prompted to install any missing prerequisites, click Install. A reboot might 

be required. 

5 In the InstallShield Wizard Welcome page, click Next. 

6 In the License Agreement page, click I accept the terms in the license agreement and 

click Next. 

7 In the Custom Setup page, select the Security Center applications to install. You can 

choose from the following 




• Server. Installs the Genetec Server service, the Directory database, the web-based 

Server Admin, and the Watchdog service. 

• (Optional) Client. Installs the Security Center Client applications: Config Tool, the 

Security Desk, or both. 

NOTE From this page, you can also do the following: 

• Click the application name to view a Feature Description and its space requirements. 

• Click the icon next to the application to change how the feature is installed. 

• Click Help to view the custom setup tips. 

• Click Space to view the disk space requirement summary. 

8 In the Language Selection page, select the user interface language for Security Center 

applications, and click Next. 

NOTE Online help for Security Center applications is not available in all languages. For 

language availability, see “Supported documentation languages” in the Security Center 

Release Notes. 

TIP After the installation, you can change the user interface language any time using the 

Language Tool found in the Tools subfolder of the Genetec Security Center 5.1 program 

group. 

9 In the Destination folder page, change the folder if necessary, and click Next. 




10 In the Installation Type page, select the Main server option, and click Next. 

NOTE If you are installing an expansion server, see "Install an expansion server" on 

page 24. 




11 In the Database Server page, select one of the following options: 

• Install a new database server. Installs Microsoft SQL Server 2008 R2 Express Edition. 

You must choose a database server name. The default is SQLEXPRESS. 

• Use an existing database server. Select an existing Microsoft SQL Server instance to 

install the database on. 

NOTE The database server name must meet the following rules: 

• It is not case sensitive. 

• It cannot match any of the SQL Server reserved keywords, such as DEFAULT, PRI- 

MARY, and so on. For a complete list of all reserved keywords, see http:// 

msdn.microsoft.com/en-us/library/ms143507.aspx. 

• It cannot be longer than 16 characters. 

• The first letter of the instance name must be a letter or an underscore (_). Acceptable 

letters are 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 or other special characters are not allowed: backslash (\), comma 

(,), colon (:), semi-colon (;), single quotation mark ('), ampersand (&), number sign 

(#), and at sign (@). 

12 Click Next. 




13 In the Services logon parameters page, select one of the following options: 

• Use default username and password. Use the default username (Local System) to run 

the Security Center services. This option works in most cases. 

• Specify the username and password for all services. Enter a valid domain username 

and password. 

IMPORTANT If this server is to host the Active Directory role, the specified user must 

be a member of the Administrators group, have Log on as service user rights, and Read 

access to the Active Directory you want it to connect to. 


15 In the Server parameters page, enter the following fields: 

• Web server port. The HTTP port that is used for the web-based Server Admin. If you 

change the default port, then Server Admin address will need to include the port 

number in the URL (for example, “http://computer:port/Genetec” instead of “http:// 

computer/Genetec”). 

• Server port. The TCP port through which the servers in your system communicate. 

• Server password/Confirm password. Leave blank (the default), or type and confirm a 

new password to log on the Server Admin. 

IMPORTANT If you lose the server password, you’ll need to call Genetec Technical 

Support to reset it. See "Technical support" on page iv. 





17 In the Firewall Rules page, select the Allow Genetec Security Center 5.1 to create necessary 

firewall rules for its applications option. 

Select this option to ensure that the internal Windows Firewall security rules are configured 

correctly. 

NOTE You’ll also need to configure the Security Center ports on your company’s Firewall 

after the installation. See "Open ports on your company’s firewalls" on page 36. 




18 In the WinPcap Installation page, select the Install WinPcap 4.1.2 option. This option 

allows you to capture diagnostic data for units and other services in Security Center. 

The WinPcap 4.1.2 Installation Wizard opens. 

a 

b 

In the WinPcap Installation Wizard, follow the installation instructions. 

In the Installation options page, select the Automatically start the WinPcap driver 

at boot time option, and click Install. 

c Click Finish, and continue with the Security Center installation. 

19 In the Ready to Install the Program page, click Install. 

20 When the Installation Wizard Completed page appears, select one the following options: 

• Launch the web-based Server Admin. Opens the Server Admin in a browser for additional 

configuration. You should always leave this option selected. 




• Show the Windows Installer log. Opens the Window Installer log in Notepad. 

21 Click Finish. 

22 If you selected the Launch the web-based Server Admin option in Step 20, the Server 

Admin browser window appears. 

23 In the Server Admin, activate your product license. See "Activate your license" on 

page 19. 

Security Center is now installed on the main server. 

After you are done: If Omnicast systems will be federated, install the required Omnicast 

compatibility packs now (see "Install Omnicast compatibility packs" on page 35). Proceed 

to install Security Center on the expansion servers (see "Install an expansion server" on 

page 24). 




Activate your license 

You must activate your Security Center license on the main server using Server Admin. You 

can activate your license one of two ways: 

• If you have Internet access: See "Web activation" on page 19. (Recommended) 

• If you do not have Internet access: See "Manual license activation" on page 21. 

Before you begin: To activate your license, you’ll need the following: 

• The System ID and password found in the Security Center License Information document. 

Genetec Technical Support sends you this document when you purchase the 

product. 

• The Server password to log on to Server Admin. The password is specified in Step 15 

during the main server installation. 

Web activation 

1 Open the Server Admin web page. 

2 Do one of the following: 

• In the address bar of your Web browser, type http://computer:port/Genetec, where 

computer is the DNS name or the IP address of your server, and port is the Web 

server port specified during Security Center Server installation (see Step 15). 

You may omit the Web server port if you are using the default value (80). 

• If connecting to Server Admin from the local host, double-click the Genetec Server 

Admin icon in the Genetec Security Center 5.1 program folder. 

3 Enter the server password that you set in Step 15 of the main server installation, and 

click Log on. 




4 In the License dialog box that appears, click Modify license. 

The License management dialog box appears. 

5 Click Web activation. 

6 In the Web activation dialog box, enter your System ID and Password as specified in 

the Security Center License Information document. 




7 Click Activate. 

The details of your license appear in the License dialog box. 

8 Click Save to close the License dialog box. 

You are still in the Genetec Security Center Server Admin browser page. 

9 Close the browser window. 

After you are done: Reboot your server. 

NOTE Many more settings can be configured in the Server Admin. For more information, 

see “Server – Server Admin” in the Security Center Administrator Guide. 

Manual license activation 

If you do not have Internet access, you can activate your license manually. 

1 Open the Server Admin web page. 







Admin icon in the Genetec Security Center 5.1 program folder in Windows. 




3 Enter the server password that you set in Step 15 of the main server installation, and 

click Log on. 

4 In the License dialog box that appears, click Modify license. 

5 In the License management dialog box, click Validation key, and choose to save or 

copy the validation key. 

The validation key is a number sequence (in hexadecimal text format) generated by the 

Server Admin. It is used to obtain the license key that unlocks your Security Center 

software. The default name for the file is Validation.vk. 

6 From another computer with Internet access, log on to GTAP at https://gtap.genetec.com. 




7 In the GTAP login page, enter the System ID and the Password specified in the Security 

Center License Information document, and click Login. 

8 Click Activate your license, and navigate to and open the Validation.vk file, and click 

Submit. 

The message Your license has successfully been activated appears. 

9 Click Click here to download your license key, and save the license key to a file. 

The default name is your System ID followed by _Directory_License.lic. 

10 Return to the Security Center main server. 

11 In the Directory tab of the Server Admin web page, click License information. 

12 In the License dialog box, click Modify license. 

13 In the License management dialog box, click Manual activation. 

14 In the Manual activation dialog box, do one of the following: 

• Paste your license information from the License.lic file (open with a text editor). 

• Browse for the License.lic file, and click Open. 

15 Click Activate. 





Installing Security Center 5.1 | Install an expansion server 

Install an expansion server 

This section explains how to install an expansion server. An expansion server adds processing 

power to your Security Center system. You can add expansion servers to your Security 

Center system at any time by connecting them to the main server. 

The expansion server installation procedure installs the following: 

• The Genetec Server service without the Directory role. When installing the Genetec 

Server, the Directory database, the web-based Server Admin, and the Watchdog service 

are also installed. 

• (Optional) Client applications (Config Tool, Security Desk, or both). 

IMPORTANT You cannot install an expansion server until the main server is up and 

running. For more information, see "Install Security Center on a main server" on page 11. 

Before you begin: Read "Before you install" on page 1. 





French). 



be required. 



click Next. 




7 In the Custom Setup page, select the Security Center applications to install. You can 

choose from the following 

• Server. Installs the Genetec Server service, the Directory database, the Web-based 

Server Admin, and the Watchdog service. 

• (Optional) Client. Installs the Security Center Client applications: Config Tool, the 

Security Desk, or both. 













group. 





10 In the Installation Type page, select the Expansion server option, and click Next. 

f 

11 In the Database Server page, select one of the following options: 

• Install a new database server. Installs Microsoft SQL Server 2008 R2 Express Edition. 

You must choose a database server name. The default is SQLEXPRESS. 

• Use an existing database server. Select an existing Microsoft SQL Server instance to 

install the database on. 




NOTE The database server name is not case-sensitive, but it must meet the following 

criteria: 

• It cannot match any of the SQL Server reserved keywords, such as DEFAULT, PRI- 

MARY, and so on. For a complete list of all reserved keywords, see http:// 

msdn.microsoft.com/en-us/library/ms143507.aspx. 

• It cannot be longer than 16 characters. 

• The first letter of the instance name must be a letter or an underscore (_). Acceptable 

character include letters of the Latin alphabet a-z and A-Z, and characters from 

other languagesare as defined in the Unicode Standard 2.0. 

• Subsequent characters can be decimal numbers, letters from basic Latin or other 

national scripts, or symbols such as the dollar sign ($), or an underscore (_), as 

defined in the Unicode Standard 2.0. 

• Embedded spaces and other special characters are not allowed: backslash (\), 

comma (,), colon (:), semi-colon (;), single quotation mark ('), ampersand (&), number 

sign (#), and at sign (@). 


13 In the Services logon parameters page, select one of the following options: 

• Use default username and password. Use the default username (Local System) to run 

the Security Center services. This option works in most cases. 

• Specify the username and password for all services. Enter a valid domain username 

and password. 

IMPORTANT If this server is to host the Active Directory role, the specified user must 

be a member of the Administrators group, have Log on as service user rights, and Read 

access to the Active Directory you want it to connect to. 





15 In the Server parameters page, enter the following fields: 

• Web server port. The HTTP port that is used for the web-based Server Admin. If you 

change the default port, then Server Admin address will need to include the port 

number in the URL (for example, “http://computer:port/Genetec” instead of “http:// 

computer/Genetec”). 

• Server port. The TCP port through which the servers in your system communicate. 

• Server password/Confirm password. Leave blank (the default), or type and confirm a 

new password to open the Server Admin. 

IMPORTANT If you lose the server password, you’ll need to call Genetec Technical 

Support to reset it. See "Technical support" on page iv. 








correctly. 






18 In the WinPcap Installation page, select the Install WinPcap 4.1.2 option. This option 

allows you to capture diagnostic data for units and other services in Security Center. 

The WinPcap 4.1.2 Installation Wizard opens. 

a 

b 

In the WinPcap Installation Wizard, follow the installation instructions. 

In the Installation options page, select the Automatically start the WinPcap driver 

at boot time option, and click Install. 

c Click Finish, and continue with the Security Center installation. 


20 When the Installation Wizard Completed page appears, select one the following options: 

• Launch the web-based Server Admin. Opens the Server Admin in a browser for additional 

configuration. You should always leave this option selected. 




• Show the Windows Installer log. Opens the Window Installer log in Notepad. 


The expansion server is installed. 

After you are done: If Omnicast systems will be federated, install the required Omnicast 

compatibility packs now (see "Install Omnicast compatibility packs" on page 35). Proceed 

to connect the expansion server to the main server. 

Connect the expansion server to the main server 


• If you selected the Launch the web-based Server Admin option in Step 20 of the 

expansion server installation procedure, the Server Admin browser window appears 

automatically. Continue with Step 3. 

• If you did not select the Launch the web-based Server Admin option, open the Server 

Admin Web page in Step 2. 







Admin icon in the Genetec Security Center 5.1 program folder. 




3 Enter the server password that you set in Step 15, and click Log on. 

4 Under Main server connection in the Genetec Server page of the Server Admin, type 

the following information: 

• Security Center Directory. The main server’s DNS name (or IP address). 

• Password. The password to log on to the Server Admin on the main server. This 

password is specified in Step 15 during the main server installation. 

5 Click Apply to save your changes. 

Now your expansion server is connected to the main server. 





Installing Security Center 5.1 | Install Security Center Client 

Install Security Center Client 

The Security Center Client installation option installs Config Tool and Security Desk. By 

default, both client applications are installed. Help is always installed. 





French). 



be required. 



click Next. 

7 In the Custom Setup page, select Security Center Client, and the client applications to 

install. You can choose from the following 

• Config Tool. Allows you to configure all Security Center components. 

• Security Desk. Allows you to efficiently control and monitor multiple security and 

public safety applications. 






Installing Security Center 5.1 | Install Security Center Client 










group. 





correctly. 





After you are done: Install any required compatibility packs and hotfixes, and configure 

the Security Center ports on your company’s Firewall. See "Install Omnicast compatibility 

packs" on page 35, "Install Microsoft hotfix" on page 39, and "Open ports on your company’s 

firewalls" on page 36. 



Installing Security Center 5.1 | Install Omnicast compatibility packs 

Install Omnicast compatibility packs 

The Omnicast compatibility pack is a software component that lets you view video from 

federated Omnicast systems in Security Center. 

IMPORTANT Before you begin please note the following important notes: 

• Security Center components (Server or Client) must be installed first. 

• When installing both Omnicast and Security Center on the same computer, install 

Omnicast before installing the compatibility packs. 

• Close all Security Center applications (Config Tool and Security Desk) and stop all 

Genetec services before installing the compatibility packs. 

• You need to install a different Omnicast compatibility pack for each Omnicast version 

you will federate to your Security Center. 

• If upgrading from an earlier version of Security Center, previously installed compatibility 

packs must be uninstalled and replaced with the ones provided on the Security Center 

5.1 installation package. 

1 Insert and display the Security Center DVD, or open the Security Center installation 

package. 

2 In the CompatibilityPacks folder, open the folder for the required Omnicast version. 

3 Double-click setup.exe, and follow the Installation Wizard instructions. 

4 When the installation is complete, click Finish. 

5 Repeat Step 2 to Step 4 for all Omnicast versions you need. 

6 If you stopped Genetec services prior to this installation, restart them now. 

NOTE The Omnicast compatibility packs are also available for download from the GTAP 

Product Download page, at https://gtap.genetec.com. You will need a username and 

password to log on to GTAP. 



Installing Security Center 5.1 | Open ports on your company’s firewalls 

Open ports on your company’s firewalls 

During the Security Center installation, you were given the option of allowing Security 

Center to create firewall rules for its applications. If you selected this option, all Security 

Center applications were added as exceptions to the internal Windows firewall. However, 

you still need to ensure that all ports used by Security Center are open and redirected for 

firewall and network address translation purposes. 

The following table describes the default ports used by Security Center applications. The 

ones you configure for your installation may be different. 

Computer Inbound Outbound Port usage 

All servers TCP 4502 TCP 4502 Communication between servers 

HTTP 80 

Connection via Server Admin 

Main server TCP 5500 Directory connection requests 

All expansion 

servers 

TCP 5500 

Directory connection requests 

Omnicast 

Federation 

UDP 1024-2048 

Security Desk when viewing video 

from an Omnicast Federation in 


Archiver TCP 555 Live and playback stream requests 

UDP 15000– 

16000 

TCP & UDP 

UDP 15000– 

16000 

Live unicast streams (audio & video) 

Vendor specific ports for events and 

unit discovery 

UDP 47806 UDP 47806 Live multicast video streams 

UDP 47807 UDP 47807 Live multicast audio streams 

TCP 554 or 

HTTP 80 

Typical port used to request video 

from a unit 

Media Router TCP 554 Live and playback stream requests 

Redirector TCP 560 Live and playback stream requests 

UDP 8000– 

12000 

UDP 47806 

Live audio & video unicast streams 

Live audio & video multicast streams 

TCP 555 

Communication with Archiver 



Installing Security Center 5.1 | Open ports on your company’s firewalls 

Computer Inbound Outbound Port usage 

Access Manager UDP/TCP 4070 UDP/TCP 4070 HID VertX controllers 

TCP 20 TCP 21, 23 HID VertX controllers 

TCP 4050 

HID VertX controllers 

LPR Manager UDP 5000 Fixed Sharp unit discovery 

TCP 8731 

TCP 8832 

Fixed Sharp units and Patrollers 

Patroller hotfix requests 

Intrusion 

Manager 

TCP 3001 TCP 3001 Bosch intrusion panels 

Security Desk 

& Config Tool 

UDP 6000–6500 

TCP 5500 

Directory connection requests 

Live audio & video unicast streams 

UDP 47806 

Live multicast video streams 

TCP 554–560 

Live and playback audio/video 

requests 



Installing Security Center 5.1 | Installing plugins 

Installing plugins 

Plugins are installed separately from Security Center. Before installing a plugin, you 

must have a valid certificate for that plugin in your license. The procedures for 

installing plugins are found in the individual Plugin User Guides. For more 

information about using plugins in Security Center, contact your Genetec Sales 

Representative. 

Enable Point-of-Sale plugin 

To view POS reports in Security Desk, do the following after installing the Security 

Center Client: 

1 Open the SecurityDesk.plugins.xml file in C:\Program Files\Genetec Security 

Center 5.1. 

2 Set the Genetec.Synergis.Reporting.PointOfSale parameter to True. 

EXAMPLE 

After you are done: Perform this procedure on each computer hosting a Security 

Center Client. 



Installing Security Center 5.1 | Install Microsoft hotfix 

Install Microsoft hotfix 

After installing Security Center, you may receive the following notification when 

you log on to Config Tool or Security Desk: “A necessary dependency for this 

application has not been found on the system. Video stability and performance are 

not guaranteed without the hotfix KB2494124”. If you receive this message, you must 

install the microsoft hotfix on your computer. 

Before you begin: Close Config Tool and Security Desk. 

1 Insert and display the Security Center DVD, or open the Security Center installation 

package. 

2 Open the Hotfixes/Microsoft/KB2494124 folder. 


• If you are using a 32-bit system, double-click NDP40-KB294124-x86.exe. 

• If you are using a 64-bit system, double-click NDP40-KB294124-x64.exe. 

4 Click Run, and follow the Installation Wizard instructions. 


6 Restart your computer. 



Installing Security Center 5.1 | Convert a main server to an expansion server 

Convert a main server to an expansion server 

When a computer comes pre-installed with Security Center, the Main server configuration 

is always used by default. You might need to convert a main server to an expansion server 

since only one main server is allowed per system. 

Before you begin: Make sure you have another main server to connect to before you 

decommission your current main server. For more information, see "Install Security Center 

on a main server" on page 11. 

1 Log on to Server Admin on your computer using a Web browser (Internet Explorer). 

2 In the Server Admin page, click the Genetec Server tab. 

3 Scroll to the end of the browser page and click Deactivate Directory. 

This operation will restart Genetec Server. 

4 Log on again to Server Admin. 

This time, the Directory tab should not appear. 

5 Scroll to the section labelled Main server connection, and configure the name and 

password of the main server it is supposed to connect to. 


Uninstall Security Center components 

Security Center components are uninstalled from Windows Control Panel. 

To uninstall a component from Windows XP: 

1 Click Start > Control Panel > Add or Remove programs. 

2 In the window that appears, select the component name and click Remove. 

To uninstall a component from Windows 7: 

1 Click Start > Control Panel > Programs and Features. 

2 In the window that appears, right-click the component name and select Uninstall. 



3 

Upgrading to Security Center 5.1 

This section explains how to upgrade an earlier version of Security Center to version 5.1. 


• "Before you upgrade" on page 42 

• "Upgrade overview" on page 44 

• "Upgrade the main server" on page 46 

• "Upgrade an expansion server" on page 47 

• "Upgrade Security Center Client" on page 47 

• "Enabling inactive roles after you upgrade from 3.0 or 4.0" on page 48 



Upgrading to Security Center 5.1 | Before you upgrade 

Before you upgrade 

This section describes the things you need to know and do before upgrading to Security 

Center 5.1 GA. 


• "Before you upgrade from 5.0 to 5.1" on page 42 

• "Before you upgrade from 3.0 or 4.0 to 5.1" on page 42 

Before you upgrade from 5.0 to 5.1 

Before you upgrade your system from Security Center 5.0 to 5.1 GA, read the following: 

• Security Center main server must be upgraded first. 

• Config Tool, Media Router, and LPR Manager must be upgraded to 5.1 GA. 

NOTE Upgrading a role to Security Center 5.1 GA means upgrading the server hosting 

the role. 

• New features introduced in 5.1 GA are only available if the server has been upgraded. 

• When multiple servers are assigned to the same role, they must all be upgraded at the 

same time. 

• New roles introduced in 5.1 GA cannot be hosted on 5.0 servers. They are: 

• Auxiliary Archiver 

• Directory Manager 

• Health Monitor 

• Global Cardholder Synchronizer 

• If you are upgrading an AutoVu LPR system, you must also upgrade the Sharp cameras. 

For more information about upgrading AutoVu systems, see “Upgrading AutoVu” in 

the AutoVu Handbook. Click here for the most recent version of this document. 

Before you upgrade from 3.0 or 4.0 to 5.1 

Before you upgrade your system from Security Center 3.0 or 4.0 to 5.1 GA, read the 

following: 

• The Installation Wizard does not migrate the server and database settings of the services 

and external systems it upgrades. Therefore, before you upgrade, write down the 

server name, extension settings, and database settings of each service and external system 

so you can reapply them after the upgrade. 

• In most cases, SQL Server 2005 is installed. But Security Center AutoVu requires SQL 

Server 2008, so you’ll need to either upgrade SQL Server 2005 to SQL Server 2008, or 

install a separate SQL Server 2008. 



Upgrading to Security Center 5.1 | Before you upgrade 

• If you are upgrading an AutoVu LPR system, you must also upgrade the Sharp cameras. 

For more information about upgrading AutoVu systems, see “Upgrading AutoVu” in 

the AutoVu Handbook. Click here for the most recent version of this document. 

• Zone entities in earlier versions of Security Center are converted to either hardware 

zones ( ) or virtual zones ( ) in Security Center 5.1. A hardware zone is a zone 

based on the inputs of a single access control unit, and it is controlled by the Access 

Manager role. A virtual zone is a zone based on the inputs of more than one unit, and is 

controlled by the Zone Manager role (introduced in Security Center 5.0). 

If you have virtual zones in your system after the upgrade, you’ll have to attach them 

manually to the Zone Manager role. See "Upgrade zone entities" on page 50. 

• The services and external systems from earlier versions of Security Center are converted 

to the following roles in Security Center 5.1: 

Security Center 3.0/4.0 

Service/External System 

Integration Service (service) 

Directory (service) 

Synergis Access Manager (service) 

AutoVu LPR Manager (external system) 

Active Directory (external system) 

Omnicast federation (external system) 

Security Center federation (external system) 

Is converted to 

Genetec Server (service) 

Directory (role) 

Access Manager (role) 

LPR Manager (role) 

Active Directory (role) 

Omnicast Federation (role) 

Security Center Federation (role) 



Upgrading to Security Center 5.1 | Upgrade overview 

Upgrade overview 

This section summarizes the upgrade process to 5.1 GA. 


• "Upgrade overview from 5.0 to 5.1 GA" on page 44 

• "Upgrade overview from 3.0 or 4.0 to 5.1 GA" on page 45 

Upgrade overview from 5.0 to 5.1 GA 

The following table summarizes the upgrade process from 5.0 to 5.1 GA. For supported 

upgrade paths, see the Security Center Release Notes. 


1 If Omnicast systems were federated to your previous 

Security Center system, you must uninstall the previously 

installed compatibility packs and replace them with the ones 

provided on the Security Center 5.1 installation package. 

"Install Omnicast compatibility 

packs" on page 35. 

2 Upgrade the main server. "Upgrade the main server" on 

page 46. 

3 Upgrade Config Tool. "Upgrade Security Center 

Client" on page 47. 

4 Upgrade the Media Router role and the LPR Manager role 

by upgrading the servers hosting those roles. 

5 During this phase, you can roll out the upgrades to the other 

expansion servers and clients in your system according to 

your priorities and schedule. For a list of Security Center 5.0 

roles and features that are backward compatible with 5.1 

GA, see the Security Center Release Notes. 

"Upgrade an expansion server" 

on page 47. 

• "Upgrade an expansion 

server" on page 47. 

• "Upgrade Security Center 




Upgrading to Security Center 5.1 | Upgrade overview 

Upgrade overview from 3.0 or 4.0 to 5.1 GA 

The following table summarizes the upgrade process from 3.0 or 4.0 to 5.1 GA. For supported 

upgrade paths, see the Security Center Release Notes. 


1 If Omnicast systems were federated to your previous 

Security Center system, you must uninstall the previously 

installed compatibility packs and replace them with the ones 

provided on the Security Center 5.1 installation package. 

2 Upgrade the Directory server in your previous system to be 

the main server. 

3 Upgrade all other servers in your previous system as 

expansion servers. 

4 If you upgraded from an earlier major version (3.0 or 4.0), 

enable all inactive roles. 

See "Install Omnicast 

compatibility packs" on page 35. 

See "Upgrade the main 


See "Upgrade an expansion 


See "Enabling inactive roles 

after you upgrade from 3.0 or 

4.0" on page 48. 

5 Upgrade all Security Center client applications. See "Upgrade Security Center 




Upgrading to Security Center 5.1 | Upgrade the main server 

Upgrade the main server 

The main server in your previous Security Center system must be upgraded first. You’ll 

have to apply a new license and upgrade the Directory database. 

Before you begin: 

• Read "Before you upgrade" on page 42. 

• Back up all your previous system’s databases. For information about how to backup 

your databases, see the Security Center Administrator Guide of your previous system. 

IMPORTANT If a reboot warning message displays during the upgrade, accept the message 

and continue with the upgrade procedure. You will have to reboot after completing the 

upgrade. 

1 Install Genetec Server on the previous main server. Use the Main server installation 

type. See "Install Security Center on a main server" on page 11. 

The Installation Wizard automatically detects an earlier version of Security Center, and 

upgrades it to Security Center 5.1. 

2 In the Server Admin, click the Directory tab. 

3 In the Database section, click Upgrade database. 

After the upgrade is complete, the Directory status indicates Directory started, and the 

database status indicates Database connected. 

4 Close the Web browser. 

5 Log on to Config Tool. 

6 Click the Home button > System task > Roles view. 

7 Select the Archiver role, and click the Resources tab. 

8 In the Actions section, click Upgrade database. 

After the upgrade is complete, the Database status indicates Connected. 

9 Repeat Step 7 to Step 8 for every role that requires a database update. 

The roles on your system vary depending on your license options. 



Upgrading to Security Center 5.1 | Upgrade an expansion server 

Upgrade an expansion server 

Before you begin: 

• Read "Before you upgrade" on page 42 

• Back up all your previous system’s databases. For information on how to backup your 

databases, see the Security Center Administrator Guide of your previous system. 

IMPORTANT If a reboot warning message displays during the upgrade, accept the message 

and continue with the upgrade procedure. You will have to reboot after completing the 

upgrade. 

• Install Genetec Server on the expansion server you are upgrading. Use the Expansion 

server installation type. See "Install an expansion server" on page 24 

The Installation Wizard automatically detects an earlier version of Security Center, and 

upgrades it to Security Center 5.1. 

After you are done: Repeat this procedure on all expansion servers in your system. 

To verify that all servers in your system are active, log on to the main server with Config 

Tool. In the Network view task, all the servers in your system should be shown in black. If 

some of the roles are still not active, you may need to upgrade the database. For more 

information, see the Security Center Administrator Guide. 

Upgrade Security Center Client 

Security Center Client upgrades from an earlier major version, such as 3.0, 4.0, or 5.0 are 

not supported. Security Center 5.1 Client is installed side-by-side with previous Security 

Center Client versions. To install Security Center Client, see "Install Security Center Client" 

on page 33. 

NOTE The user workspace configuration is not preserved. In previous versions, the user 

workspace was saved as a workstation configuration. In 5.1, the user workspace is saved as 

part of the user profile in the Directory. 

To uninstall Security Center Client, see "Uninstall Security Center components" on page 40. 



Upgrading to Security Center 5.1 | Enabling inactive roles after you upgrade from 3.0 or 4.0 

Enabling inactive roles after you upgrade from 3.0 or 4.0 

Before you begin: This procedure only applies if you upgraded from an earlier major version 

(3.0 or 4.0) to 5.1 GA. You need the latest Config Tool version to enable the roles. For 

more information, see "Upgrade Security Center Client" on page 47. 

The Installation Wizard does not migrate the server and database settings of the services 

and external systems it upgrades. After the upgrade, you need to manually reassign the 

servers to their respective roles, and in some cases, upgrade their database. 

1 Log on to your upgraded system using Config Tool. 

2 Click the Home button, and click the System task. 

3 In the System task, click the Roles view. 

All roles upgraded from the previous system are shown in red (inactive). 

4 If you have an inactive Access Manager, see "Enable the Access Manager" on page 49. 

5 If you have an inactive Active Directory, see "Enable the Active Directory" on page 49. 

6 If you have an inactive LPR Manager, see "Enable the LPR Manager" on page 49. 

7 If you have an inactive Omnicast Federation, do one of the following: 

• If you are not migrating the federated Omnicast system, see "Enable the Omnicast 

Federation" on page 50. 

• If you are upgrading the federated Omnicast system to an independent Security 

Center 5.1 system, see "Scenario #3: Migrate a federated Omnicast system to a federated 

Security Center system" on page 80. 

• If you are merging the federated Omnicast system to the Security Center system you 

just upgraded, do one of the following: 

If your Omnicast Directory is located on the same computer as your Security 

Center Directory, see "Scenario #4: Migrate and merge a federated Omnicast system 

to its federation host on the same server" on page 82. 

If your Omnicast Directory is located on a different computer than your Security 

Center Directory, see "Scenario #5: Migrate and merge a federated Omnicast system 

to its federation host on a different server" on page 84. 

8 If you had an inactive Security Center Federation, see "Enable the Security Center Federation" 

on page 50. 

All roles in the Role view should now be shown in black (active). 

After you are done: Backup all databases of your new system. For more information, see 

“Database backup and restore” in the Security Center Administrator Guide. 




Enable the Access Manager 

You need to enable the Access Manager role upgraded from a earlier version. 

1 In the System task in the Config Tool, click the Roles view, and select the Access Manager 

role. 

2 Click the Extensions tab, and click to add the hardware extensions that this Access 

Manager used to control. 


4 Click the Resources tab. 

5 In the Servers section of the Resources tab, click . 

6 Select the server that was previously hosting this Access Manager, and click Add. 

7 In the Resources tab, type the Data server and Database names previously used by this 

Access Manager. 

8 (Optional) If upgrading from Security Center 3.0, then in the Actions section, click 

Upgrade database. 


10 (Optional) If you used to have zone entities working in online mode in your previous 

system, follow "Upgrade zone entities" on page 50. 

Enable the Active Directory 

1 In the System task in the Config Tool, click the Roles view, and select the Active Directory 

role. 

2 Click the Directory servers tab. 

3 Click , select the server that was previously hosting this Active Directory, and click 

Add. 


Enable the LPR Manager 

1 In the System task in the Config Tool, click the Roles view, and select the LPR Manager 

role. 

2 Click the Resources tab. 

3 In the Servers section of the Resources tab, click . 

4 Select the server that was previously hosting this LPR Manager, and click Add. 

5 In the Actions section of the Resources tab, click Upgrade database. 


7 Click the Options tab. 

8 On the General settings page, verify that the Root folder is properly set. 




If you used a network drive in the previous version, you will have to reset the path to 

the root folder. 


Enable the Omnicast Federation 

1 In the System task in the Config Tool, click the Roles view, and select the Omnicast 

Federation role. 

2 Select the Resources tab. 

3 In the Servers section, click and select the server that was previously hosting this 

Omnicast Federation and click Add. 


Enable the Security Center Federation 

Upgrade zone entities 

1 From the Role view, select the Security Center Federation role. 

2 Select the Resources tab. 

3 In the Servers section, click and select the server that was previously hosting this 

Security Center Federation and click Add. 


Zone entities based on inputs from more than one unit are converted to virtual zones ( ) 

in Security Center 5.1. If you see virtual zones in the Logical view after the upgrade, you’ll 

have to manually associate them with the Zone Manager role. For more information, see 

“Managing zones” in the Security Center Administrator Guide. 

1 In the Logical view task in the Config Tool, select a virtual zone entity. 

2 Click the Properties tab. 

3 From the Zone Manager drop-down list, assign a Zone Manager role to the virtual 

zone. 


5 Click the Arming tab and change the zone arming properties if necessary. 




4 

Installing Security Center in Silent Mode 

This section explains how to automate the process of installing Security Center. 


• "Before you install" on page 53 

• "Installing Security Center in Silent Mode" on page 55 



Installing Security Center in Silent Mode | About Silent Mode 

About Silent Mode 

A silent installation is an automated way of installing software without user intervention. 

The silent installation is run from the command line using the setup.exe executable, and 

Windows Installer commands. 

You can customize the following options from the command line: 

• Installation language 

• Application language 

• Client or Server installation path 

• Client or Server features to install 

• Server username and password for running the services 

• Server and database name 

Limitations 

Before performing a silent installation, you should note the following limitations: 

• You cannot update your license in silent mode. You’ll need to run the Server Admin 

application after the installation to activate the license. For more information, see 

"Activate your license" on page 19. 

• A command line is limited to a maximum of 850 characters. 

One way to shorten the command line length is to reduce the installation path length. 

This can be achieved by copying the installation files onto a local drive or by mapping a 

network drive to the path of setup.exe. 

• You cannot install WinPcap in silent mode. 



Installing Security Center in Silent Mode | Before you install 

Before you install 

Software prerequisites 

This section describes the things you should know and do before you perform a silent 

installation. 

• "Software prerequisites" on page 53 

• "Preinstallation tasks" on page 54 

During a silent installation the installer will verify and install the software prerequisites on 

your system, but this may cause your system to restart. Therefore, it is best practice to 

manually install the software prerequisites before running the silent installer. 

The following table lists the software prerequisites. If they are not installed, the installation 

packages (.msi or .exe) are available on the Security Center DVD in the folder 

\Full\ISSetupPrerequisites. 

Computer 

32-bit and 64 bit 

operating systems 

Prerequisite software 

• Microsoft® .NET Framework 3.5 SP1 (dotNetFx35.exe) 

• Microsoft® .NET Framework 4.0 (dotNetFx40_x86_x64.exe) 

• Microsoft® Report Viewer 2010 SP1(ReportViewer.exe) 

• Microsoft® CCR and DSS Runtime 2008 R2 

• Microsoft® CCR and DSS Runtime 2008 R3 

• Microsoft® Silverlight 4 (Silverlight.exe) 

• DirectX End-User Runtimes (DXSETUP.exe) – Only for client apps. 

• Visual C++ 2005 SP1 Redistributable (vcredist_x86.exe) 

• Visual C++ 2008 SP1 Redistributable (vcredist_x86.exe) 

• Visual C++ 2010 SP1 Redistributable(x86) (vcredist_x86.exe) 

• Windows Media Format 11 32-bit/64-bit 



Installing Security Center in Silent Mode | Before you install 

Computer 

32-bit operating 

systems 

64-bit operating 

systems 

Prerequisite software 

• Microsoft® SQL Server 2008 Native Client (sqlncli.msi) 

• Microsoft® SQL Server 2008 Management Object Collection 

(SharedManagementObjects.msi) 

• Microsoft® SQL Server CLR Types (SQLSysClrTypes.msi) 

• MSXML 6.0 SP1 (msxml6_x86.msi) 

• One of the following depending on your operating system: 

• Windows Installer 4.5 for Windows Server 2003 SP1 and later (x86) 

• Windows Installer 4.5 for Windows Server 2008 (x86) 

• Windows Installer 4.5 for Windows XP SP2 and later (x86) 

• Windows Media Format 11 (x86) (WMFDist11-WindowsXP-X86- 

ENU.exe) 

• Windows PowerShell 1.0 for Windows 2003 (x86) 

(WindowsServer2003-KB926139-v2-x86-ENU.exe) 

• Windows PowerShell 1.0 for Windows XP (x86) (WindowsXP- 

KB926139-v2-x86-ENU.exe) 

• Microsoft SQL Sever Compact 3.2 SP2 (x86) (SSCERuntime_x86- 

ENU.msi) 

• Microsoft® SQL Server 2008 Native Client (x64) (sqlncli.msi) 

• Microsoft® SQL Server 2008 Management Object Collection (x64) 

(SharedManagementObjects.msi) 

• Microsoft® SQL Server CLR Types (x64) (SQLSysClrTypes.msi) 

• MSXML 6.0 SP1 (x64) (msxml6_x86.msi) 

• One of the following depending on your operating system: 

• Windows Installer 4.5 for Windows Server 2003 and XP (x64) 

• Windows Installer 4.5 for Windows Server 2008 (x64) 

• Microsoft SQL Server Compact 3.2 SP2 (x64) (SSCERuntime_x64- 

ENU.msi) 

• Windows Media Format 11 (x64) (WMFDist11-WindowsXP-X64- 

ENU.exe) 

• Windows PowerShell 1.0 for Windows 2003 and XP (x64) 

(WindowsServer2003.WindowsXP-KB926139-v2-x64-ENU.exe) 

Preinstallation tasks 

Perform the following tasks before performing a silent installation: 

• Security Center Server must connect to a database server. If there is no database server, 

you can install Microsoft® SQL Server 2008 R2 Express Edition on your server computer, 

which is available on the Security Center DVD in the folder \Full\SQLExpress. 

• If you specify a different Windows user than the default (Local System) to run the services, 

then that user must be created before you begin the installation process. The user 

must be a member of the Administrators group and must have the Log on as service 

user privilege. 



Installing Security Center in Silent Mode | Installing Security Center in Silent Mode 

Installing Security Center in Silent Mode 


• "Silent install command" on page 55 

• "Installer options" on page 56 

• "Sample server installation commands" on page 59 

• "Sample client installation commands" on page 59 

• "Install Security Center in Silent Mode" on page 60 

• "Uninstall Security Center in Silent Mode" on page 60 

Silent install command 

Security Center’s Client and Server packages each have their own setup.exe program, but the 

syntax for calling this program in silent mode is the same: 

Setup.exe /L /s /v"/qn " 

The following table lists the setup.exe options. 

Option 

/L 

Description 

Sets the language used by the installation program. Immediately 

precedes the four-digit language code. No space is allowed. 

• /L1033 for English (default) 

• /L3084 for French 

/s Sets the setup.exe executable to run in silent mode with no user 

interaction. 

/v" 

/qn 

" 

Makes sure that the options within the quotation marks are sent 

directly to the msiecxec.exe executable. 

Runs the install in silent mode. 

Sets the installer option list. Each option in the list uses the following 

syntax: 

= 

where is an option name, and is a list of 

comma-seperated values. 

No space is allowed on either side of the equal sign (=). If the value 

list must contain spaces, the entire value list must be included 

between a pair of double quotes preceded by a backslash (\"). The 

individual options and their values are described in "Installer 

options" on page 56. 




Installer options 

The following table lists the installer options. 

Option 

INSTALLDIR 

ADDLOCAL 

GLOBAL_SERVER 

Description 

Specify the path where the software should be installed. 

INSTALLDIR=C:\MyChoiceOfFolder 

INSTALLDIR=\"D:\Program Files\Security Center\" 

Note that in the second example, (\") is required because the value contains spaces. If do 

you not specify a path, it will be installed at C:\Program Files\Genetec Security Center 5.1. 

Specify the features to be installed. 

The Server features are: 

• Server (Genetec Server with Directory) 

• Directory (also Genetec Server with Directory) 

• SimpleServer (Genetec Server without Directory) 

The Client features are: 

• Client (installs Config Tool and Security Desk) 

• SecurityDesk (only Security Desk) 

• ConfigTool (only Config Tool) 

Specify the database server name for the Directory. When omitted, the default value is 

(local)\SQLExpress. 

EXAMPLE GLOBAL_SERVER=BLADE32\SQLServerEnterprise 

DATABASE_SERVER 

DATABASE_INSTANCE 

UPGRADE_DATABASE 

Same as GLOBAL_SERVER option. This parameter maintains backward compatibility with 

previous silent installation scripts. 

Used in conjunction with the BACKUP_DATABASE option. Specify the database instance 

name for the Directory if different from the default. 

Specify that the SQL server database for the Directory is automatically upgraded. If the 

database does not exist, this property is ignored. Possible values are Y or N. When this 

option is omitted, the default value is N. 

EXAMPLE UPGRADE_DATABASE=Y 

BACKUP_DATABASE 

Specify that the SQL server database for the Directory should be backed up prior to the 

installation (and prior to the database upgrade). Configuration Files are also backed up 

in the same destination folder as the database. If the database does not exist, the database 

is not backed up but the configuration files still are. Possible values are Y or N. When this 

property is not set, the default value is N. When set to Y, the 

BACKUP_DATABASE_PATH property must be set to a valid folder. 

EXAMPLE BACKUP_DATABASE=Y 

BACKUP_DATABASE_PATH 

Used in conjunction with the BACKUP_DATABASE option. Specify the folder where the 

database backup must be saved. If the path does not exist, it will be created. 

EXAMPLE UPGRADE_DATABASE_PATH=C:\Backups 




Option 

SERVICEUSERNAME 

Description 

Specify the username to use in the services. 

EXAMPLE SERVICEUSERNAME=.\admin 

SERVICEPASSWORD 

Specify the password to use in the services. 

EXAMPLE SERVICEPASSWORD=anypassword 

User and password need to be created first with the right credentials prior to using those 

properties. 

SERVERADMIN_PORT 

Specify the HTTP port for the Web-based Server Admin. 

EXAMPLE SERVERADMIN_PORT=8080 

SERVERADMIN_PASSWORD 

ALLUSERS=1 

LANGUAGECHOSEN 

Specify the password for the Web-based Server Admin. 

Add this command to install the shortcuts for all users. This parameter specifies whether 

to perform a per-computer or per-user installation on Windows NT-based target 

systems. 

• For a user with administrative privileges, the configuration data for the installation is 

stored in the All Users profile. 

• For a user without administrative privileges, the installation will display an error 

message and then exit. 

Language used by Security Center. The possible code values are: 

• Arabic - 1025 

• Chinese (Simplified) - 2052 

• Chinese (Traditional) - 1028 

• Dutch - 1043 

• English - 1033 

• French - 3084 

• German - 1031 

• Hebrew - 1037 

• Hungarian - 1038 

• Italian - 1040 

• Japanese - 1041 

• Korean - 1042 

• Norwegian - 1044 

• Persian - 1065 

• Polish - 1045 

• Brasilian Portuguese - 2070 

• Spanish - 1034 

• Thai - 1054 

EXAMPLE LANGUAGECHOSEN=1033 

If the code is invalid, English will be used. If this option is omitted, the installation 

language (specified with the /L option) will be used. 

WEBSERVER_PORT 

Specify the HTTP port for the Web-based Server Admin. 




Option 

CREATE_FIREWALL_RULES 

Description 

Add the installed Security Center applications to the Windows Firewall exceptions list. 

Possible values are 0 or 1. When omitted, the default value is 1. 

• 0 = Do not create Firewall rules 

• 1 = Create Firewall rules 

EXAMPLE CREATE_FIREWALL_RULES=1 

REBOOT 

This option allows you to force or suppress a reboot after the Server installation has 

ended. Possible values are: 

• F - To force a reboot when your installation is complete. 

• S - To suppress any reboot except the one caused by the ForceReboot action. 

• R - To suppress any reboot caused by Windows Installer actions. 




Sample server installation commands 

Run the setup.exe program located on the Security Center installation DVD in the Server 

folder. 

EXAMPLE The Genetec Server with Directory will be installed in English with a specific 

Username and Password for the service to run under. The files will be located in a new 

directory, the database server will be specified, and there will be no reboot. Setup will run 

in silent mode without any questions. 

Setup.exe /L1033 /s /v"/qn ADDLOCAL=Directory 

INSTALLDIR=C:\NewServer SERVICEUSERNAME=.\toto 

SERVICEPASSWORD=password DATABASE_SERVER=(local)\Genetec 

DATABASE_INSTANCE=DirectorySecurityCenter REBOOT=S" 

EXAMPLE This is the standard installation of the Genetec Server with Directory in English 

without any questions. Only the installation path is different. 

Setup.exe /L1033 /s /v"/qn INSTALLDIR=c:\GENETEC_PATH ADDLOCAL=Directory" 

EXAMPLE This is equivalent to a Standard Installation in French, in silent mode without 

any questions. 

Setup.exe /L3084 /s /v"/qn" 

EXAMPLE This is equivalent to a Complete Installation in English, in silent mode without 

any questions. The default database server name, (local)\SQLExpress, is used for the 

Directory. 

Setup.exe /L1033 /s /v"/qn ADDLOCAL=ALL" 


any questions. This setup will create a log file located in c: drive. 

Setup.exe /L1033 /s /v"/qn ADDLOCAL=ALL /L*v C:\Server.log" 


any questions. Security Center applications will use Arabic. 

Setup.exe /L1033 /s /v"/qn ADDLOCAL=ALL LANGUAGECHOSEN=1025" 

Sample client installation commands 

Run the setup.exe program located on the Security Center installation DVD in the Client 

folder. 

EXAMPLE The Security Desk will be installed in English, in silent mode without any 

questions. 

Setup.exe /L1033 /s /v"/qn INSTALLDIR=c:\GENETEC_PATH ADDLOCAL=SecurityDesk" 

EXAMPLE The Config Tool and the Security Desk will be installed in French, in silent mode 

without any questions. 




Setup.exe /L3084 /s /v"/qn INSTALLDIR=c:\GENETEC_PATH ADDLOCAL=ConfigTool,SecurityDesk" 

EXAMPLE The Config Tool and the Security Desk will be installed in English, in silent 

mode without any questions. 

Setup.exe /L1033 /s /v"/qn INSTALLDIR=c:\GENETEC_PATH ADDLOCAL=ConfigTool,SecurityDesk" 

EXAMPLE This is equivalent to a Typical Installation in French, in silent mode without any 

questions. 

Setup.exe /L3084 /s /v"/qn" 

EXAMPLE Complete Installation in English, in silent mode without any questions. 

Setup.exe /L1033 /s /v"/qn ADDLOCAL=ALL" 

EXAMPLE Complete Installation in English, in silent mode without any questions. Security 

Center applications will use Arabic. 

Setup.exe /L1033 /s /v"/qn ADDLOCAL=ALL LANGUAGECHOSEN=1025" 

Install Security Center in Silent Mode 

To install Security Center in Silent Mode: 

• Run the setup.exe program located on the Security Center installation DVD in the Full 

folder. 

Uninstall Security Center in Silent Mode 

To uninstall Security Center (Client and Server components) in Silent Mode: 

• Run the following command from the Full folder of the Security Center installation 

DVD: 

setup.exe /s /v"/qn" /x 

To uninstall Security Center Client components (if the Server is also installed): 


DVD: 

setup.exe /s /v"/qn REMOVE=Client" 

To uninstall Security Center Server components (if the Server is also installed): 


DVD: 

setup.exe /s /v"/qn REMOVE=Server" 



5 

Migrating from Omnicast 4.5 and later 

This section explains how to migrate Omnicast 4.5 and later systems (stand-alone or 

federated) to Security Center 5.1. 


• "About the migration tool" on page 62 

• "Before you migrate" on page 63 

• "Migration overview" on page 73 

• "Run the Migration tool" on page 74 

• "Omnicast to Security Center migration scenarios" on page 76 

• "Enabling remote connections" on page 86 

• "Run the Migration tool in silent mode" on page 92 



Migrating from Omnicast 4.5 and later | About the migration tool 

About the migration tool 

The Migration tool is a Security Center application that allows you to migrate your 

Omnicast data to Security Center. It is included in the Security Center 5.1 installation 

package. The executable file MigrationTool.exe is found in the folder C:\Program 

Files\Genetec Security Center 5.1. 

You can migrate the following Omnicast components to Security Center: 

• Directory. For more information, see "Verify your new Security Center system." on 

page 75. 

• Archiver. For more information, see "About Archiver migration" on page 71. 

• Metadata Engine. Only if it is running the Point of Sale (POS) plugin. 



Migrating from Omnicast 4.5 and later | Before you migrate 

Before you migrate 

Before migrating Omnicast to Security Center, please note the following: 

• Not everything is migrated. Due to some conceptual and data model differences, not 

everything is migrated from Omnicast to Security Center. Before you migrate, you 

should understand what components are migrated, the migration limitations, and how 

Omnicast components are converted in Security Center. 

• "What’s not migrated from Omnicast to Security Center" on page 64 

• "What’s included in Directory migration" on page 66 

• "About Archiver migration" on page 71 

• Migrating the Directory to a remote server. If you are migrating the Omnicast directory 

to a Security Center database on a remote server, you need to enable remote connections. 

See "Enabling remote connections" on page 86 

• Migrate the Directory server first. If your Omnicast system is deployed on more than 

one computer, the Omnicast Directory server must be migrated first. 

• Windows 7 and Windows 2008. If you are using a Windows 7 or Windows 2008 system, 

make sure you have full administrative rights on the computer before using the 

Migration tool. 

• Test your migration. If you have more than one Omnicast server to migrate, it is best 

practice to test the entire system after the migration before uninstalling Omnicast. 

• Read the log files. The Migration tool generates log files about the migration (components 

migrated, components not migrated, and any errors that occurred during the 

migration). Read these log files carefully, as they may later provide valuable information 

to fine tune your new system. 




What’s not migrated from Omnicast to Security Center 

The following entities/configurations are not migrated from Omnicast to Security Center: 

Item 

Events 

Actions 

Event-to-action 

Failover 

HTML maps 

Omnicast audit trail 

activity 

What’s not migrated 

Custom events 

Custom actions 

All configurations 

Failover lists 

HTML maps that are bound to the Omnicast SDK (URL will be migrated, but the map 

will not work). 

Directory database log 

Active Directory • All settings 

• Users and user groups 

Multi-site membership 

Cameras 

Camera groups 

Monitor groups 

Analog monitors 

Alarms 

Only the first three partitions will be migrated. 

The following camera properties are not migrated: 

• Video overlays 

• Recorded video sequences from Auxiliary Archivers 

• Current camera blocking priority 

• PTZ motors distinct site security settings. The PTZ motor entity is merged with the 

camera entity in Security Center. 

All camera groups 

All monitor groups 

All analog monitors 

The following alarm properties are not migrated: 

• Alarm display mode (Salvo, Block, Simple) and maximum number of alarms on each 

user 

• Individual Live, Playback, or Still frame display option for each attached camera 

• “Delete after x days” setting for acknowledged alarms 

• Accepted acknowledgement types 

• Metadata overlay configuration 

• For active & acknowledged alarms, the Instance ID is lost 

• Alarm instance description 

• Alarm context (used when alarm is generated from SDK) 

• Alarm history 

• History of alarm priority is lost. Priority history for active and acknowledged alarms. 

In Security Center, the alarm report shows the current priority configuration on the 

alarm. 




Item 

Virtual Matrix 

Plug-ins 

Sites 

Logical IDs 

What’s not migrated 

All settings and dependent entity types: 

• CCTV keyboards 

• Hardware matrices 

• Virtual cameras 

All server and client plug-ins. 

The following site properties are not migrated: 

• Hidden site property is ignored. 

• You can re-create the same effect using the partition hierarchy created by the 

migration. 

• “Inherit parent permission entries” when it is set to false. 

• Multi-site membership 

• Since site hierarchies are migrated as area hierarchies and partition hierarchies, only 

the first three site membership are covered by partitions. 

Logical IDs for all unit devices except for cameras. 

Macros • All macros 

• Hot macro configurations for each user 

Auxiliary Archiver 

Video Tricking 

Failover Directory 

All settings and dependent entity types. 

All settings. 

All settings. Failover is managed by the Directory Manager role in Security Center. 




What’s included in Directory migration 

When migrating the Omnicast Directory service, the following entities/items are included: 

Item 

Camera 

PTZ motors 

Camera sequence 

Sites 

Units 

What’s migrated 

A camera is migrated to Security Center with the following properties: 

• Name 

• Description 

• Logical ID 

• Site membership (see Sites) 

• Video quality/stream usage 

• Recording settings 

• Motion detection (and motion mask) settings 

• Video attributes 

• Network settings 

• Time zone settings 

• Camera specific settings 

A PTZ motor is migrated to Security Center and is merged with the camera it is associated 

with. The following properties are migrated: 

• PTZ protocol 

• PTZ number 

• Serial device 

A camera sequence is migrated with the following properties: 

• Name 


• Camera list, with dwell time and PTZ commands 

NOTE In Security Center 5.1, camera sequences can only be run by the local Security 

Desk. There is no Virtual Matrix that runs camera sequences on a server. Therefore, 

every time you view a camera sequence in Security Desk, it always starts from the 

beginning of the camera list. 

A site is migrated to Security Center as two separate entities: an area and a partition, with 

the following transformations: 

• An area and a partition are created for each site. 

• The site hierarchy is reproduced in the Logical view as an area hierarchy. 

• The site hierarchy is reproduced as a partition hierarchy under a new root partition. 

• The site member entity list is copied to the area member entity list. 

• The site member entity list is copied into the partition member entity list. 

• The site accepted user list is copied into the partition accepted user list. 

NOTE Hidden sites are migrated as regular sites. 

A unit is migrated to Security Center as a video unit with the following properties: 

• Name 



• Username/password 




Item 

Digital Input and 

Output relays 

Serial ports 

Speakers 

Microphones 


Input and output entities are migrated to Security Center as peripherals of the video unit 

they belong to. The following properties are migrated: 

• Name 


A serial port is migrated to Security Center as a peripheral of the video unit it belongs to. 

The following properties are migrated: 

• Name 


• Serial communication settings 

• Line driver 

A speaker is migrated to Security Center as a peripheral of the video unit it belongs to. The 

following properties are migrated: 

• Name 



• Volume gain 

• Camera it is linked to 

A microphone is migrated to Security Center as a peripheral of the video unit it belongs to. 

The following properties are migrated: 

• Name 



• Sensitivity 

• Input type 

• Camera it is linked to 




Item 

Users 

User groups 

Viewer layouts 


A user is migrated with the following properties: 

• Name 


• User group membership 

• Email 

• User status (enabled/disabled) 

• Password 

• Password expiration 

• Number of workstations the user can log on from 

• Logon schedules 

• Supervised logon settings 

• List of viewer layouts (see Viewer layouts) 

• PTZ priority (called User level in Security Center) 

• Archive viewing limitation 

• Privileges 

If an Omnicast user had the same name as a Security Center user, the two will be 

merged, and the privileges granted to the Omnicast user will be granted to the Security 

Center user. 

IMPORTANT Make sure all the privileges have been migrated properly. 

NOTE Users that did not have access to hidden sites will have access after the migration. 

You must manually remove the unwanted users from those partitions. 

A user group is migrated with the following properties: 

• Name 


• Member list 

• Supervised logon settings 

• PTZ priority (called User level in Security Center) 

• Archive viewing limitation 

• Privileges 

If an Omnicast user group had the same name as a Security Center user group, the two 

will be merged, and the privileges granted to the Omnicast user group will be granted 

to the Security Center user group. 

IMPORTANT Make sure all the privileges have been migrated properly. 

A viewer layout is migrated to Security Center as a Public Monitoring task with the 

following properties: 

• Name 


• Tile pattern 

• Tile content (displayed entity) 




Item 

Alarm entities 

Active alarm instances 

Acknowledged alarm 

instances 

Generic schedules 


An alarm entity is migrated with the following properties: 

• Name 


• Logical ID 

• Schedule 

• Priority 

• Dwell time 

• Reactivation threshold 

• Alarm recording duration 

• Protect recorded video for 

• Procedure (URL) 

• Automatic acknowledgement after (seconds) 

• Recipient list 

• Broadcast option 

• For sequential broadcasts, the Time out period is copied to every recipient. 

• Displayed entity (cameras and camera sequences) list 

• Camera list 

The display option of the first camera in the list is applied to all cameras in Security 

Center. If the display option is Still frames, the closest playback options will be used. 

Duplicate cameras are removed and listed in the error log. 

Active alarm instances are migrated with the following properties: 

• GUID 

• Creation time 

• Source entity and event 

• Propagation level 

• When the recipient notification is sequential, the last recipient that has been notified in 

the list is remembered. 

• Dynamic alarm context data 

Acknowledged alarm instances are migrated with the following properties: 

• GUID 

• Creation time 

• Source entity and event 

• Acknowledgement time 

• Acknowledgement type 

• Custom acknowledgements are converted to Default acknowledgements. 

• Acknowledged by 

A generic schedule is migrated to Security Center as a schedule entity with the following 

properties: 

• Name 


• All recurrence settings with time coverage options 




Item 

Archiving schedules 


There are no archiving schedule entities in Security Center 5.1. Instead, each camera has 

the choice to use its own recording settings or follow the default settings of the Archiver 

role. 

The migration is performed as follows: 

• For each archiving schedule in Omnicast, the generic schedule and archiving mode is 

copied to each attached camera. 

• For each Archiver in Omnicast, only the default archiving schedules are copied to the 

corresponding Archiver role. 




About Archiver migration 


• "What’s included in Archiver migration" on page 71 

• "What’s not included in Archiver migration" on page 71 

• "How Omnicast Archiver setups are migrated" on page 72 

What’s included in Archiver migration 

The following table lists the items that are migrated from the Archiver to Security Center. 

Item 

Storage configurations 

Watermarking settings 

Extension configurations 

Archived video 

Ghost cameras 

Archiver events 


All storage configurations (disk configurations, disk groups, camera assignment to each 

disk group, and camera retention periods) are copied to the Archiver role properties. 

Watermarking settings are copied to the Archiver role properties. 

Extension configurations are copied to the Archiver role properties. 

All archived video is preserved by the migration, including video recorded by a 

secondary Archiver during a failover event. 

Ghost cameras are migrated as offline cameras that are not attached to any unit. 

• If after the migration the video unit for the camera is created, then the offline camera 

is automatically attached to the video unit and comes online. 

• Recorded video for ghost cameras is migrated. 

All Archiver events are migrated. 

What’s not included in Archiver migration 

The following items are not migrated from the Archiver to Security Center: 

• Non-default Archiver extension settings. Archiver extensions (called Manufacturer 

extensions in Security Center 5.1) are created automatically as needed in Security Center. 

Therefore, unless you use default settings, the settings will not be migrated. 

Workaround: You’ll have to change settings manually after the migration. 

• Maximum number of simultaneously archived cameras per Archiver. Archiver 

failover works differently in Security Center. Whenever standby Archiver is involved, 

the migration creates a single Archiver role with two servers, one primary and one secondary. 

If multiple Archiver roles end up being assigned to the same server, you’ll need to manually 

assign a priority to each Archiver role after the migration to ensure proper operation 

during failover. 




How Omnicast Archiver setups are migrated 

The following table lists how Omnicast 4.x Archiver scenarios are migrated to Security 

Center 5.1: 

Omnicast scenario 

Single Archiver with no 

standby 

An Archiver with standby/ 

redundant Archiver 

Multiple Archivers with 

one standby Archiver 

One primary Archiver with 

multiple standby Archivers 

Migration solution 

• All video events and files are migrated to the Archiver role. 

• Migrates the primary Archiver first. The Archiver role inherits the settings from the 

first Archiver migrated. 

• All video events and files are migrated to the Archiver role. 

• The Archiver role is assigned the same servers used to host the primary and standby 

Omnicast Archiver services. 

• If all cameras have the same redundant archiving settings, the settings are copied to 

the role. Otherwise, the cameras will keep their individual archiving settings. 

• All video events and files are migrated to the Archiver roles. 

• For every subset of cameras that share the same primary and standby Omnicast 

Archivers, a Security Center Archiver role is created, and assigned to the same 

servers originally hosting the primary and standby Archiver services. 

• Only the video events and files from the primary Archiver and the first standby 

Archiver are migrated to the Archiver role. 

For more information on Archiver priorities, see “Managing Omnicast – Protecting your 

video archives” in the Security Center Administrator Guide. 



Migrating from Omnicast 4.5 and later | Migration overview 

Migration overview 

To migrate an Omnicast system to Security Center, you must perform the same steps on 

every computer where the Omnicast components are installed. The procedure will differ 

based on your migration scenario. 

The following table summarizes the Omnicast to Security Center migration process. 


1 Read the things you need to know and do before you migrate. See "Before you migrate" on 

page 63. 

2 Install Security Center 5.1 Server and Client on the Omnicast server, 

and migrate your Omnicast system. 

This procedure will differ based on your migration scenario. 

NOTE Security Center is installed side-by-side with Omnicast on the 

same computer. Omnicast software remains installed so that you can 

revert back to your old system if anything goes wrong. 

3 Convert Omnicast components to their equivalent Security Center 

components using the Migration tool. 

CAUTION Do not stop Omnicast services manually. They are 

stopped and disabled when you run the Migration tool. 

For a list of Omnicast components that can be migrated, and how 

they are converted in Security Center, see "Before you migrate" on 

page 63. 

4 Test your new Security Center 5.1 system. 

NOTE If needed, you can re-enable Omnicast services and resume 

your operations on your old Omnicast system. 

See "Omnicast to Security 

Center migration 

scenarios" on page 76. 

See "Run the Migration tool" 

on page 74, or "Run the 

Migration tool in silent 

mode" on page 92. 

For information about 

using Security Center 

applications, see the 


Administrator Guide, and 

the Security Desk User 

Guide. 

5 Uninstall your Omnicast software. Same procedure as 

uninstalling Security 

Center components. See 

"Uninstall Security Center 

components" on page 40. 



Migrating from Omnicast 4.5 and later | Run the Migration tool 

Run the Migration tool 

The Migration tool allows you to convert Omnicast components to their equivalent 

Security Center components (for example, Archiver to Archiver role in Security Center). 

For a list of Omnicast components that can be migrated, and how they are converted in 

Security Center, see "Before you migrate" on page 63. 

CAUTION Do not stop Omnicast services manually. They are stopped and disabled when 

you run the Migration tool. 

IMPORTANT If your Omnicast system is deployed on more than one computer, you must 

migrate the Omnicast Directory server first. 

Before you begin: Install Security Center 5.1 Server and Client on the Omnicast server 

computer where you plan to run the Migration Tool. See "Omnicast to Security Center 

migration scenarios" on page 76. 

1 Double-click MigrationTool.exe located in the Security Center 5.1 installation folder 

(typically C:\Program Files\Genetec Security Center 5.1). 

The Migration tool Wizard appears. 

2 Specify the folder where the migration reports should be saved, and click Next. 

For more information about migration reports, see Step 10. 



Migrating from Omnicast 4.5 and later | Run the Migration tool 

3 In the License agreement page, click I accept the terms in the license agreement, and click 

Next. 

4 In the Service selection page, select the Omnicast services you want to migrate, and click 

Next. 

You can choose the following components: 

• Directory 

• Archiver 

• Metadata Engine (only if it is running the Point of Sale plugin) 

Only the services installed on your Omnicast server are listed. 

5 (Only if you are migrating the Directory) In the Omnicast information page, specify the 

Omnicast databases you want to migrate, and click Next. 

If the information is valid, a green confirmation message appears. Click Next. 

6 In the Security Center information page, type the logon and database information of 

your Security Center system, and click Next. 

NOTE If you are migrating the Directory, you must type the database information of 

your target Security Center system. 

CAUTION If your target Security Center system and database is on a remote server, you 

will need to enable remote connections to continue with the Migration. See "Enabling 

remote connections" on page 86. 

If the information is valid, a green confirmation message appears. 

7 Click Next. 

8 (Optional) In the Omnicast Federation page, select the Omnicast Federation role that 

corresponds to the Omnicast system you are migrating, and click Next. 

9 In the Creation summary page, verify the information, and then click Migrate. 

The Migration Progress window appears. 

NOTE During the migration, the Migration tool stops and disables all Omnicast 

services. 

10 When the migration is complete, click Close. 

If you selected the Open the Migration report folder option, the report folder appears, 

displaying the migration log files. The names of the log files are as follows: 

• MigratedEntities.csv. Lists all entities that were migrated. 

• NotMigratedEntities.csv. Lists any entities that were not migrated and the reasons 

why. 

• OtherError.csv. Lists any errors that prevented the migration process. 

After you are done: Verify your new Security Center system. 



Migrating from Omnicast 4.5 and later | Omnicast to Security Center migration scenarios 

Omnicast to Security Center migration scenarios 

This section explains the most common Omnicast to Security Center migration scenarios. 


• "Scenario #1: Migrate a stand-alone Omnicast system to a Security Center system on 

the same server" on page 76. 

• "Scenario #2: Migrate a stand-alone Omnicast system to a Security Center system on a 

different server" on page 78. 

• "Scenario #3: Migrate a federated Omnicast system to a federated Security Center system" 

on page 80. 

• "Scenario #4: Migrate and merge a federated Omnicast system to its federation host on 

the same server" on page 82. 

• "Scenario #5: Migrate and merge a federated Omnicast system to its federation host on 

a different server" on page 84. 

Scenario #1: Migrate a stand-alone Omnicast system to a Security 

Center system on the same server 

This procedure explains how to migrate a stand-alone (not federated) Omnicast system to 

a Security Center 5.1 system hosted on the same server. 

This procedure describes the following migration scenario: 

• Before: Server A runs Omnicast 4.x Directory and Archiver services. 

• After: Server A runs Security Center 5.1 Directory and Archiver roles. 

Server A 

Omnicast 4.x Directory 

and Archiver services 

Server A (main server) 

Security Center 5.1 Directory 

and Archiver roles 

Migration tool 




To migrate a stand-alone Omnicast system to a Security Center system on the same 

server: 

IMPORTANT If your Omnicast system is distributed over several computers, migrate the 

main server first. 

1 On Server A, install Security Center 5.1 Server (main server option) and Client. See 

"Install Security Center on a main server" on page 11. 

2 Delete the Archiver role that was created by default on the main server. 

a Log on to Security Center with Config Tool. 

b Click the Home button, click the System task, and click the Roles view. 

c Delete the Archiver role. 

3 Close all Omnicast and Security Center client applications. 

4 Migrate the system data from Omnicast to Security Center. See "Run the Migration 

tool" on page 74. 

After the migration is complete, the Omnicast system is turned off, its data is migrated to 

the Security Center 5.1 system, and its video units are controlled by the Security Center 

Archiver role. 

After you are done: If your Omnicast system is distributed over several computers, repeat 

this procedure for every expansion server. However, in Step 1, install Security Center 5.1 

Server (expansion server option) and Client. See "Install an expansion server" on page 24. 




Scenario #2: Migrate a stand-alone Omnicast system to a Security 

Center system on a different server 

This procedure explains how to migrate a stand-alone (not federated) Omnicast system to 

a Security Center 5.1 system where the Directory role is hosted on a different server. 


• Before: 

• Server A is a clean new server. 

• Server B runs Omnicast 4.x Directory and Archiver services. 

• After: 

• Server A runs Security Center 5.1 Directory role. 

• Server B runs Security Center 5.1 Archiver role. 

Server A (new server) 

No Genetec software 


Security Center 5.1 with 

Directory role 

Server B 


and Archiver 

Server B (expansion server) 


Archiver role 





To migrate a stand-alone Omnicast system to a Security Center system using a different 

server: 

1 On Server A, install Security Center 5.1 Server (main server option) and Client. See 


Server A is now the main server for Security Center 5.1. 

2 On Server B, install Security Center 5.1 Server (expansion server option) and Client 

software. See "Install an expansion server" on page 24. 





4 On Server B, migrate the Omnicast Directory and Archiver to Security Center 5.1. See 

"Run the Migration tool" on page 74. 

5 Verify that the expansion server (Server B) is created. 

a Log on to Security Center 5.1 on Server A with Config Tool. 

b Click the Home button, and click the Network view task. 

c In the Network view task, verify that the expansion server (Server B) is created. 

6 Verify that the Database server running the Archiver role is on Server B. 

a Click the Home button, click the System task, and click the Roles view. 

b In the Roles view, click the Archiver role, and click the Resources tab. 

c The Database server running the Archiver role should be Local (Server B). 

After the migration, the Omnicast system is turned off, its data is migrated to the Security 

Center 5.1 system, and its video units are controlled by the Security Center Archiver role. 




Scenario #3: Migrate a federated Omnicast system to a federated 

Security Center system 

This procedure explains how to migrate an Omnicast 4.x system federated by a previous 

version of Security Center to a federated Security Center 5.1 system, while upgrading the 

federation host to Security Center 5.1. 


• Before: 

• Server A runs Security Center 4.0 Directory and IS/Omnicast federation external 

system (ES) that is connected to the Omnicast 4.x system on Server B. 


• After: 

• Server A runs Security Center 5.1 Directory and Security Center Federation role 

that is connected to the Security Center 5.1 system on Server B. 

• Server B runs Security Center 5.1 Directory and Archiver roles. 

Server A (federation host) 

Security Center 4.0 Directory and 

IS hosting Omnicast federation ES 

Server A (federation host) 

Security Center 5.1 Directory and 

Security Center Federation roles 

Regular upgrade 

Omnicast federation 

external system 


Federation role 

Server B 



Server B 

Security Center 5.1 

Directory and 

Archiver roles 





To migrate a federated Omnicast system to a federated Security Center system: 

1 On Server B, migrate the Omnicast 4.x system to Security Center 5.1: 

a On Server B, install Security Center 5.1 Server (main server option) and Client. See 


b Log on to Security Center with Config Tool. 

c Click the Home button, click the System task, and click the Roles view. 

d Delete the Archiver role that was created by default on the main server. 

e Close all Omnicast and Security Center client applications. 

f Migrate the system data from Omnicast to Security Center. See "Run the Migration 

tool" on page 74. 

The Omnicast 4.x system becomes a Security Center 5.1 system with an Archiver role. 

2 On Server A, upgrade Security Center 4.0 to Security Center 5.1. See "Upgrade the 

main server" on page 46, and "Upgrade Security Center Client" on page 47. 

NOTE The Integration Server/Omnicast federation expansion server becomes an 

Omnicast Federation role. 

3 Upgrade the Omnicast Federation role to a Security Center Federation role: 

a Log on to Security Center 5.1 with Config Tool. 


c Select the Omnicast Federation role that connects to the Omnicast system on 

Server B. 

It should appear in red (inactive) because the Omnicast services have been disabled 

by the Migration tool in Step 1. 

d Click the Properties tab. 

e From the Version drop-down list, select Upgrade to Security Center. 

f In the warning message that appears, click Continue. 

g The Identity tab is selected, and the entity type shows Security Center Federation. 

h (Optional) Change the entity name and description if necessary, and click Apply. 

i Select again the Properties tab. 

j Enter the server name (Server B), username, and password, and click Apply. 

The Connection status is shown as Connected. 

After the migration, Server A and Server B each hosts a distinct Security Center 5.1 system. 

The Security Center system on Server A is federating the Security Center system on 

Server B. 




Scenario #4: Migrate and merge a federated Omnicast system to its 

federation host on the same server 

This procedure explains how to migrate and merge a federated Omnicast system to its 

Security Center 4.0 federation host, where both systems reside on the same computer. The 

goal is to eliminate the federation and end with one Security Center 5.1 system. 


• Before: 

• Server A runs both Security Center 4.0 Directory and Omnicast 4.x Directory, and 

Security Center is federating Omnicast. 

• Server B runs only Omnicast 4.x Archiver service. 

• After: 

• Server A runs Security Center 5.1 Directory role (main server). 

• Server B runs Security Center 5.1 Archiver role (expansion server). 

Server A 

Security Center 4.0 Directory 

and Omnicast 4.x Directory 






Server B 

Omnicast 4.x with 

Archiver service 



with Archiver role 





To migrate and merge a federated Omnicast system to its federation host when the two 

systems reside on the same computer: 







3 On Server A, run the Migration tool. See "Run the Migration tool" on page 74. 

IMPORTANT Make sure you select the Omnicast Federation role that corresponds to the 

Omnicast system on Server A. 


where Omnicast Archiver is. See "Install an expansion server" on page 24. 

5 On Server B, run the Migration tool. See "Run the Migration tool" on page 74. 





7 Select the Role view, then the Archiver role, and select the Properties tab. 

The server running the Archiver role should be Local (Server B). 

After the migration, a single Security Center 5.1 system remains, deployed on two servers: 

Server A (main server) and Server B (expansion server). 




Scenario #5: Migrate and merge a federated Omnicast system to its 

federation host on a different server 

This procedure explains how to migrate and merge a federated Omnicast system to its 

Security Center 4.0 federation host, where the two systems reside on different computers. 

The goal is to eliminate the federation and end with one Security Center 5.1 system. 


• Before: 

• Server A runs Security Center 4.0 Directory and IS/Omnicast federation external 

system (ES) connected to the Omnicast 4.x system on Server B. 


• After: 

• Server A runs Security Center 5.1 Directory role (main server). 

• Server B runs Security Center 5.1 Archiver role (expansion server). 

Server A 

Security Center 4.0 Directory 

and Omnicast federation ES 





Server B 





with Archiver role 





To migrate and merge a federated Omnicast system to its federation host when the two 

systems reside on different computers: 



2 Delete the Archiver role that was created by default to run on Server A (the main 

server). 





where Omnicast Archiver is. See "Install an expansion server" on page 24. 

4 On Server B, migrate the Omnicast Directory and Archiver to Security Center 5.1. See 

"Run the Migration tool" on page 74. 





6 In the Roles view, click the Archiver role, and click the Resources tab. 

The Database server running the Archiver role should be Local (Server B). 

After the migration, a single Security Center 5.1 system remains, deployed on two servers: 

Server A (main server) and Server B (expansion server). 



Migrating from Omnicast 4.5 and later | Enabling remote connections 

Enabling remote connections 

Process overview 

To migrate your Omnicast Directory to a Security Center 5.1 database that is on a remote 

server, you must enable remote connections between the SQL Servers. 

Before you begin: To be able to access the SQL Server, the same Windows user must exist 

on both computers, and have read and write privileges on both databases. 

The following table summarizes the process of enabling remote connections between your 

Omnicast and Security Center servers. 


1 Download Microsoft SQL Server 2008 Management Studio. 

This application can be downloaded from Microsoft or 

GTAP. 

2 Allow remote connections using the Microsoft SQL Server 

2008 Management Studio. 

3 Enable remote connections on the Omnicast and Security 

Center servers. 

See "Download 

Microsoft SQL Server 

2008 Management 

Studio" on page 86. 

See "Allow remote 

connections" on page 87. 

See "Enable remote 

connections" on page 88. 

Download Microsoft SQL Server 2008 Management Studio 

NOTE The Microsoft SQL Server 2008 Management Studio is available for download from 

the GTAP Product Download page, at https://gtap.genetec.com. 





Allow remote connections 

NOTE Perform this procedure on the Security Center server where you want to migrate the 

Omnicast Directory. 

1 Open the Microsoft SQL Server 2008 Management Studio in Windows. 

2 Connect to the Security Center server where you want to migrate the Omnicast Directory. 

3 Right-click the SQL Server, and click Properties. 

4 In the Server Properties dialog box, select the Connections page. 

5 Select the Allow remote connections to this server option. 

6 Click OK. 

7 Close Microsoft SQL Server 2008 Management Studio. 




Enable remote connections 

The procedure for enabling remote connections differs according to your version of SQL 

Server version. 

• "Enable remote connections for SQL Server 2008" on page 88 

• "Enable remote connections for SQL Server 2005" on page 90 

Enable remote connections for SQL Server 2008 

NOTE Perform this procedure on the Omnicast and Security Center servers. 

1 Open the SQL Server Configuration Manager in Windows. 

2 Click SQL Server Network Configuration, and double-click Protocols for Server 

(where Server is the name of the server). 

3 Under Protocol Name, double-click TCP/IP. 

The TCP/IP Properties dialog box opens. 

4 From the Enabled drop-down list, select Yes. 

5 Click Apply. 

The following warning appears: Any changes made will be saved; however, they will 

not take effect until the server is stopped and restarted. 

6 Click OK. 

7 Click OK to close the TCP/IP Properties dialog box. 




8 (Optional) If you would like to connect the SQL Server by name, do the following: 

a Under Protocol Name, double-click Named Pipes. 

The Named Pipes Properties dialog box opens. 

b From the Enabled drop-down list, select Yes. 

c Click Apply. 

The following warning appears: Any changes made will be saved; however, they 

will not take effect until the server is stopped and restarted. 

d Click OK. 

e Click OK to close the Named Pipes Properties dialog box. 

9 In the SQL Server Configuration Manager, click SQL Server Services. 

10 Right-click the SQL Server service, and click Restart. 

11 Configure the SQL Server Browser to start up automatically in Windows. 

a In the SQL Server Configuration Manager, click SQL Server Services. 

b Right-click the SQL Server Browser service, click Properties, and click the Service 

tab. 

c Set the Start Mode setting to Automatic from the drop-down list. 

d Click the Log On tab, and click the Start button. 

12 Close the SQL Server Configuration Manager. 




Enable remote connections for SQL Server 2005 

NOTE Perform this procedure on the Omnicast and Security Center servers. 

1 Open the SQL Surface Area Configuration page in Windows. 

2 Click Surface Area Configuration for Services and Connections. 

3 On the Surface Area Configuration for Services and Connections page, expand Database 

Engine, and click Remote Connections. 

4 Select the Local and remote connections option, and select the appropriate protocol to 

enable for your environment. 

5 Click Apply. 

The following message appears: Changes to Connection Settings will not take effect 

until you restart the Database Engine service. 

6 Click OK. 

7 In the Surface Area Configuration for Services and Connections page, expand Database 

Engine, and click Service. 

8 Click Stop to stop the SQL Server service. 

9 Wait until the SQL Server service stops, and then click Start to restart the SQL Server 

service. 

10 Configure the SQL Server Browser to start up automatically in Windows. 

a In the SQL Server Configuration Manager, double-click SQL Server Services. 

b Right-click the SQL Server Browser service, click Properties, and click the Service 

tab. 




c 

Set the Start Mode setting to Automatic from the drop-down list. 

d Click the Log On tab, and click the Start button. 

11 Close the SQL Server Configuration Manager. 



Migrating from Omnicast 4.5 and later | Run the Migration tool in silent mode 

Run the Migration tool in silent mode 

IMPORTANT When running the Migration tool in silent mode, never use localhost to specify 

a server. Always use the DNS name or IP address of the computer. 

Migration tool command syntax 

The Migration tool can be executed from the command prompt in silent mode. The general 

syntax is as follows: 

MigrationTool /s /option /option ... 

To list all available command line options: 

1 Open a command console. 

2 Move to the folder where Security Center 5.1 is installed. 

It is typically C:\Program Files\Genetec Security Center 5.1. 

3 Type MigrationTool /help at the command prompt. 

About the command line options 

When calling the Migration tool from the command line, note the following: 

• All options have a long and a short syntax. For example, /help and /h are equivalent. 

• When an option requires an argument (indicated by [arg]), a value must be specified or 

the command is rejected. 

• Options related to a similar topic form a group. Options from the same group must be 

specified together, or else the command is rejected. The option groups are: 

• Compulsory options: /s, /scdir, /scuser, /scpwd 

• Directory options: /dir, /dirdbsvr, /dirdbname, /alarmdbsvr, /alarmdbname 

• Archiver option: /arc 

• Metadata Engine options: /me, /medbsvr, /medbname, /posdbsvr, /posdbname 

• Federation option: /fed (must always be used with the Directory options) 

• The order of appearance of the options in the command line is not important. 

• If an argument value contains spaces, it must be put between double quotes. 




Sample commands 

This section describes some typical commands to help you understand. 

• MigrationTool /s /dir /dirdbsvr (local)\SQLEXPRESS /dirdbname DirectorySQL / 

alarmdbsvr (local)\SQLEXPRESS /alarmdbname AlarmSQL /scdir SERVER_A /scuser 

admin /scpwd: 

This command only migrates the Omnicast Directory component to Security Center 

using the following options: 

• Omnicast Directory database server: (local)SQLEXPRESS 

• Omnicast Directory database name: DirectorySQL 

• Omnicast Alarm database server: (local)SQLEXPRESS 

• Omnicast Alarm database name: AlarmSQL 

• Security Center main server name: SERVER_A 

• Security Center username: admin 

• Security Center password: blank 

NOTE The Directory database is backed up by default and the migration logs are created 

in their default location, which is [currentfolder]\MigrationToolCsvLogs\. 

• MigrationTool /s /arc /me /medbsvr (local)\SQLEXPRESS /medbname OmniPos / 

scdir BLADE65 /scuser admin /scpwd GoHabsGo /posdbsvr (local)\SQLExpress / 

posdbname PointOfSale /csv C:\MigrationLogs 

This command migrates the Archiver and the Metadata Engine to Security Center 

using the following options: 

• Omnicast Metadata Engine database server: (local)SQLEXPRESS 

• Omnicast Metadata Engine database name: OmniPos 

• Security Center main server name: BLADE65 

• Security Center username: admin 

• Security Center password: GoHabsGo 

• Security Center Point of Sale database server: (local)\SQLExpress 

• Security Center Point of Sale database name: PointOfSale 

• Migration log files folder: C:\MigrationLogs 

NOTE The Archiver’s database server and database name are read from the registry and 

do not need to be specified. The Omnicast Directory is not migrated. 

• MigrationTool /s /dir /dirdbsvr (local)\SQLEXPRESS /dirdbname OmnicastConfig 

/alarmdbsvr (local)\SQLEXPRESS /alarmdbname OmnicastAlarms /scdir MAINSERVER 

/scuser JSmith /scpwd Pocahantas /fed “MAINSERVER (Omnicast Federation)” 

This command migrates and merges a federated Omnicast system to its federation host 

that has been previously upgraded to Security Center 5.1, using the following options: 

• Omnicast Directory database server: (local)SQLEXPRESS 




• Omnicast Directory database name: OmnicastConfig 

• Omnicast Alarm database server: (local)SQLEXPRESS 

• Omnicast Alarm database name: OmnicastAlarms 

• Security Center main server name: MAINSERVER 

• Security Center username: JSmith 

• Security Center password: Pocahantas 

• Security Center Omnicast Federation role: MAINSERVER (Omnicast Federation) 

For more information, see "Scenario #4: Migrate and merge a federated Omnicast system 

to its federation host on the same server" on page 82. 



Index 

A 

about 

installation package, 8 

Migration tool, 62 

silent mode, 52 

this guide, ix 

Access Manager, enabling after upgrade, 49 

acquiring 

password, 5 

system ID, 5 

activating 

license, 19 

Microsoft .NET Framework 3.5 SP1, 6 

Active Directory, enabling after upgrade, 49 

administrator privileges, prerequisites, 5 

allowing remote connections, 87 

Archiver 

migrating from Omnicast, 71 

what’s migrated, 71 

what’s not migrated, 71 

B 

backing up databases, 6 

Bosch SDK, tools, 9 

C 

contacting technical support, iv 

converting main server to expansion server, 40 

D 

database, backing up, 6 

demo license, acquiring, iv 

differences between Security Center versions, 43 

Directory database mirroring, requirements, 4 

Directory, migrating from Omnicast, 66 

Discovery tool, locating, 9 

document information, ii 

documentation 

See production documentation 

downloading Microsoft SQL Server 2008 Management 

Studio, 86 

E 

enabling 

inactive roles, 48 

Access Manager, 49 

Active Directory, 49 

LPR Manager, 49 

Omnicast Federation, 50 

Security Center Federation, 50 

Point-ofSale plugin, 38 

remote connections, 86 

overview, 86 

SQL Server 2005, 90 

SQL Server 2008, 88 

expansion server 

about, 24 

converting from main server, 40 

installing, 24 

upgrading, 47 

F 

files 

SETUP.EXE, 8 

VALIDATION.VK, 21 

VIDEOFILEANALYSER.EXE, 9 

firewalls, configuring ports, 36 

G 

Genetec Server, installing in silent mode, 59 



Index | H 

H 

hardware requirements 

client, 3 

server, 2 

hotfix KB2494124, installing, 39 

I 

inactive roles, enabling after upgrade, 48 

installation package 

about, 8 

contents, 8 

locating, 8 

installing 

See also installing options 

expansion server, 24 

Genetec Server in silent mode, 59 

hotfix KB2494124, 39 

Omnicast compatibility packs, 35 

plugins, 38 

prerequisites, 1 



main server, 11 

overview, 10 


silent mode, 55, 60 

Security Center Client, 33 



WinPcap, 17, 30 

installing options 

languages, 8 

modes 


wizard mode, 8 

internet access, prerequisites, 5 

L 

languages, installing options, 8 

license 

activating, 19 

manual activation, 21 

web activation, 19 

license key, about, 21 

limitations 

migrating Omnicast, 64 


locating 

installation package, 8 

LPR Manager, enabling after upgrade, 49 

M 

main server 

about, 11 

converting to expansion server, 40 


upgrading, 46 

manual license activation, 21 

MapInfo, tools, 9 

Microsoft SQL Server 2008 Management Studio, 

downloading, 86 

migrating Omnicast 

Archiver, 71 

Directory, 66 

enabling remote connections, 86 

limitations, 64 

merge to federation host on different server, 84 

merge to federation host on same server, 82 

overview, 73 


running Migration tool, 74 

scenarios, 76 

to a Security Center system on different server, 78 

to a Security Center system on same server, 76 

to federated Security Center system, 80 


about, 62 

running, 74 

running in silent mode, 92 

modes, installation options, 8 

N 

NEC Cluster 

document location, 9 

tools, 9 



Index | O 

O 

Omnicast 

migrating to Security Center, 61 

migration scenarios, 76 

using Migration tool, 62 

Omnicast compatibility pack, installing, 35 

Omnicast Federation, enabling after upgrade, 50 

opening 

ports on company firewalls, 36 

Server Admin, 19, 21 

overviews 

enabling remote connections, 86 



upgrading, 44 

P 

plugins, installing, 38 

Point-of-Sale plugin, enabling, 38 

Portable Archive Player 


tools, 9 

ports, configuring for firewalls, 36 

preinstallation tasks, 5 


prerequisites 

installation, 1 

installing Security Center, 5 

acquiring system ID and password, 5 

administrator privileges, 5 

backing up databases, 6 

for Windows 7, 6 

hibernation options, 5 

internet access, 5 



software requirements, 53 

upgrading, 42 

product documentation 

about, ii 

where to find, iii 

R 

reassigning servers to roles, 48 

Release Notes, where to find, 2 

remote connections 

allowing, 87 

enabling, 86 

requirements. See system requirements 

roles, enabling after upgrade, 48 


S 

scenarios, migrating Omnicast, 76 


installing 

overview, 10 


migrating from Omnicast, 61 


supported 

federations, 5 

migrations, 5 

upgrades, 5 

system requirements, 2 

uninstalling components 

from Windows 7, 40 

from Windows XP, 40 


upgrading, 44 

overview, 44 


version differences, 43 

Security Center Client 

enabling Point-of-Sale plugin, 38 



upgrading, 47 

Security Center Federation, enabling after upgrade, 50 

Security Desk custom tasks, tools, 9 

Server Admin 

creating password, 15, 28 

opening, 19, 21 

server password, creating, 15, 28 

server, reassigning to roles, 48 

SETUP.EXE, file, 8 

silent install command, using, 55 



Index | T 

silent mode 

about, 8, 52 


Genetec Server, 59 

install command, 55 

options, 56 

preinstallation tasks, 54 


Security Center, 60 


limitations, 52 



uninstalling Security Center, 60 

software requirements 



SQL Server 2005, enabling remote connections, 90 

SQL Server 2008, enabling remote connections, 88 

system ID, acquiring, 5 

system password, acquiring, 5 

system requirements 

client hardware, 3 


server hardware, 2 

software, 4 

T 

technical support, contacting, iv 

tools 

Bosch SDK, 9 

Discovery tool, 9 

MapInfo, 9 

NEC Cluster, 9 

Portable Archive Player, 9 

Security Desk custom tasks, 9 

VIDEOFILEANALYSER.EXE, 9 

Visiowave Codec, 9 

Windows Cluster, 9 

Wireshark, 9 

XML templates, 9 

U 

uninstalling 

Security Center components, 40 

Security Center in silent mode, 60 

upgrading 

enabling inactive roles, 48 


main server, 46 

overview, 44 




zone entities, 50 

V 

validation key, about, 21 

VALIDATION.VK, file, 21 

VIDEOFILEANALYSER.EXE, file location, 9 

Visiowave codec, tools, 9 

W 

web license activation, using, 19 

Windows 7, activating Microsoft .NET Framework 3.5 

SP1, 6 

Windows Cluster 


tools, 9 

WinPcap, installing, 17, 30 

Wireshark, tools, 9 

wizard mode, about, 8 

X 

XML templates, tools, 9 

Z 

zone entity, enabling after upgrade, 50

Security Center Installation and Upgrade Guide 5.1 GA - Genetec

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?