Using Microsoft® Cluster Services

with OnGuard
(For use with Windows Server 2003 Enterprise Edition)
Lenel OnGuard ® 2008 Plus Using Microsoft® Cluster Services with OnGuard
Product version 6.1, item number DOC-903, revision 1.012, June 2008
Copyright © 1992-2008 Lenel Systems International, Inc. Information in this document is subject
to change without notice. No part of this document may be reproduced or transmitted in any form
or by any means, electronic or mechanical, for any purpose, without the express written
permission of Lenel Systems International, Inc.
Non-English versions of Lenel documents are offered as a service to our global audiences. We
have attempted to provide an accurate translation of the text, but the official text is the English
text, and any differences in the translation are not binding and have no legal effect.
The software described in this document is furnished under a license agreement and may only be
used in accordance with the terms of that agreement. Lenel and OnGuard are registered
trademarks and BadgeDesigner™, FormsDesigner™, and MapDesigner™ are trademarks of
Lenel Systems International, Inc.
Windows, Windows Vista, Windows 2003, and Windows XP are trademarks and Microsoft is a
registered trademark of Microsoft Corporation. Integral and FlashPoint are trademarks of Integral
Technologies, Inc. Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc.
Oracle is a registered trademark of Oracle Corporation. Other product names mentioned in this
User Guide may be trademarks or registered trademarks of their respective companies and are
hereby acknowledged.
Portions of this product were created using LEADTOOLS © 1991-2008 LEAD Technologies, Inc.
ALL RIGHTS RESERVED.
OnGuard includes ImageStream® Graphic Filters. Copyright © 1991-2008 Inso Corporation. All
rights reserved. ImageStream Graphic Filters and ImageStream are registered trademarks of Inso
Corporation.
 Using Microsoft® Cluster Services with OnGuard

Table of Contents

Chapter 1: Overview ....................................................................5

What is Clustering? ......................................................................................... 5

How It Works ..................................................................................................................... 6

Important Installation Notes .............................................................................................. 6

Chapter 2: Hardware Configuration ...........................................9

Chapter 3: Install Microsoft Windows 2003 Enterprise Server

and Microsoft Cluster Services ..............................................11
Adding a Node ................................................................................................................ 15

Chapter 4: Install SQL Server 2005 Enterprise Edition ..........17

Chapter 5: OnGuard Installation and Configuration for

Clustering Services .................................................................33
Installing OnGuard Server Software ............................................................................... 33

Installing the OnGuard Software Dongle and License File ............................................. 35

Setting Up the OnGuard Database ................................................................................. 36

OnGuard Service Registry Fix ........................................................................................ 37

Chapter 6: Adding OnGuard Services to the

Cluster Failover .......................................................................39

Index .................................................................................................45

revision 1 — 3
Table of Contents

4 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Chapter 1: Overview

OnGuard® 2008 with Windows 2003 Enterprise Server and Microsoft Cluster
Services provides a clustering solution for access control. This allows OnGuard
to continue running if a server or managed resource on the server fails. The
failure of a server or resource in a cluster is transparent (by not tying resources to
a physical server). Microsoft Cluster Service allows for the creation of a
customized failover process.

What is Clustering?
In order to ensure system availability in the event of a failure, or to enhance
performance, two or more servers can be connected by a high speed interconnect
and reference data on a shared data storage device. This grouping is called a
cluster. In a cluster, resources are connected to a virtual server that can easily be
referenced between servers in the cluster. When a failure is detected, resources
can be redirected and the workload redistributed.

revision 1 — 5
1: Overview

How It Works
A server cluster provides high availability by making application software and
data available on several servers linked together in a cluster configuration. If a
server stops functioning, a process called failover automatically shifts the
workload of the failed server to another server in the cluster. The failover process
is designed to ensure continuous availability for critical applications and data.

Although clusters are designed to handle failure, they are not fault tolerant with
regards to user data. The cluster by itself does not guard against loss of user data
such as the actual SQL 2005 database. The recovery of the lost data would
typically be handled by third party software or by taking advantage of a RAID
configuration for data redundancy.

Important Installation Notes

Operating System Requirements
• Windows 2003 Enterprise Server with Service Pack 1
• Shared Data Storage Device
• Volumes created for both the SQL data and the QUORUM drive
• Network settings and properties are configured for all network cards in each
server
• All servers must be part of a domain or active directory
• MS Cluster Services must be installed and configured (This also requires the
installation of IIS - Internet Information Server)
• “Dynamic” volumes are not supported for any clustered drives

SQL Server Requirements

• SQL Server 2005 Enterprise Edition
• Program Files installation directory must be a local drive on each computer
(Not a shared volume)
• Data Files installation directory must be a shared volume

OnGuard Requirements
• OnGuard 2008 must be installed on both servers. This also requires the
installation of Windows 2003 service pack 1 and DirectX 9.0.

Important: Due to conflicts with service pack 1 for Windows 2003, OnGuard runs a
Lenel Windows Security Utility during installation. Read the release notes
carefully before continuing with the installation.

• Computer specific services are configured within System Administration to

start on the virtual cluster network name (such as LS Linkage Server)
• The LS Services registry fix is applied to both servers and configured. For
more information, refer to OnGuard Service Registry Fix on page 37.

6 — revision 1
 Using Microsoft® Cluster Services with OnGuard

• If the LS Communications Server is going to be running on the clustered

servers as part of the Cluster Failover, all the hardware that is connected to
that LS Communications Server will need to be configured in System
Administration to point to the Virtual Cluster Name.
• OnGuard program files are installed to a local volume on each server
• Each server has a valid license file and dongle attached
• All OnGuard services except for LS Login Driver are set to “Manual” start
• OnGuard 2008 client computers will need to be configured to point to the
Virtual Cluster Name for the License Server location and the Virtual SQL
Name for the database location. For more information, refer to Chapter 5:
OnGuard Installation and Configuration for Clustering Services on page 33.

revision 1 — 7
1: Overview

8 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Chapter 2: Hardware Configuration

1. Install a cluster-enabled PERC controller and two Network Interface Cards

on each server. (Configurations may need to be made in the BIOS of the
PERC card to enable the clustering option.)
2. Connect the cluster-enabled PERC controller on each server from channel
one on each cluster-enabled PERC 3/DC to the 68-pin UHDCI connector on
the shared media device.
The following diagrams illustrate common hardware configurations using
DELL hardware (You are not limited to DELL hardware):

revision 1 — 9
2: Hardware Configuration

3. Assure that the shared media device contains at least two configured
volumes. One configured volume will host the database; the other
configured volume will host the quorum and clustering logs. The DATA and
QUORUM drives must be two different physical volumes.
4. On each server, connect one NIC to your public network. The other NIC is to
be directly connected to the other server using a cross-over Ethernet RJ-45
cable. Configure the NIC’s with the following pretensions:
• Make sure you have reserved six static IP addresses for the NIC and
cluster configuration. These addresses will be used for:
a. Two (2) public static IP addresses for each NIC connected to the
public network.
b. Two (2) private static IP addresses for each NIC connected to the
private network.
c. One (1) public static IP address for the cluster’s virtual IP address.
d. One (1) public static IP address for SQL Server’s virtual IP address.
• Make sure the public network link on each server is the first NIC
connection accessed by the DNS.
To do this:
a. On the desktop, right-click “My Network Places” and click
“Properties.”
b. On the menu bar, click “Advanced” and click “Advanced
Settings…”
c. Under “Connections”, make sure the public network link NIC is the
first connection in the list. If it is not, highlight the connection and
use the arrows to move it first in the list.
• Make sure the private network link on each server maintains an empty
WINS address.
To do this:
a. On the desktop, right-click “My Network Places” and click
“Properties.”
b. Right-click the private network link and click “Properties.”
c. Make sure that “Internet Protocol (TCP/IP)” is the only checked
component.

Note: Network card settings and IP addresses need to be configured prior to the
installation of the Microsoft Cluster Services.

10 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Chapter 3: Install Microsoft Windows 2003 Enterprise

Server and Microsoft Cluster Services

1. On cold boot, configure the PERC controller and update the NVRAM
accordingly.
2. During Microsoft Windows 2003 Enterprise Server installation, select
“Cluster Services” under the “Windows 2003 Components” window. If this
configuration is post-install, you can select “Cluster Services” in “Add/
Remove Programs.”
3. After Windows 2003 Enterprise Server has been installed, prepare the shared
media device hard drives for clustering.
• Revert both drives back to Basic drives; Dynamic drives are not
supported.
• Create primary partitions that are 100% of the drive space, and format
them as NTFS.
4. Run the “Cluster Service Configuration Wizard” on both servers to create a
two-node cluster, starting with the first server.

Note: It is suggested you create a second Administrator account for user validation
during cluster configuration.

revision 1 — 11
3: Install Microsoft Windows 2003 Enterprise Server and Microsoft Cluster Services

Follow these instructions to run the “Cluster Service Configuration Wizard”:

a. From the Start menu, select Control Panel > Administrative Tools >
Cluster Administrator.
b. From the Action drop-down, select “Create new cluster” then click
[OK] to start the New Server Cluster Wizard.

5. When the New Server Cluster Wizard begins, click [Next].

6. On the Cluster Name and Domain window:

a. In the Domain field, type the correct domain.
b. In the Cluster name field type the name of the cluster.
c. Click [Next].

7. On the Select Computer window

a. Type the name of the computer that will be the first node in the cluster.
This computer must be a member of the domain you specified in the
previous step.

12 — revision 1
 Using Microsoft® Cluster Services with OnGuard

b. Click [Next].
c. The wizard will now analyze your configuration. When the analysis is
completed, click [Next].
8. On the IP Address window.
a. Enter the IP address that is used to connect to the cluster.

9. On the Cluster Service Account window:

a. In the User name field, type the user name for the domain account you
want the Cluster service to use.
b. In the Password field, type the password for the domain account you
want the Cluster service to use.
c. In the Domain drop-down list, select the domain.
d. Click [Next].

revision 1 — 13
3: Install Microsoft Windows 2003 Enterprise Server and Microsoft Cluster Services

10. On the Proposed Cluster Configuration window.

a. Review the cluster configuration. If you are happy with it click [Next] to
create the cluster.
11. You have completed the New Server Cluster Wizard.
a. Click [Finish].

14 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Adding a Node
1. Start the Add Nodes Wizard.
a. Click [Next].

2. On the Select Computers window.

a. Type or browse for the computer name that will be added to the cluster.
b. Click [Add]. The computer will be added to the Selected computers
display window.
c. Click [Next].
d. The wizard will now analyze your configuration. When the analysis is
complete click [Next].

3. On the Cluster Service Account window.

a. In the User name field, type the user name for the domain account you
want the Cluster service to use.
b. In the Password field, type the password for the domain account you
want the Cluster service to use.
c. In the Domain drop-down list, select the domain.
d. Click [Next].

revision 1 — 15
3: Install Microsoft Windows 2003 Enterprise Server and Microsoft Cluster Services

16 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Chapter 4: Install SQL Server 2005 Enterprise Edition

1. Insert the SQL Server 2005 Enterprise Edition installation disc into the disc
drive located on node one (the computer running the Windows operating
system).
• If autorun is enabled, the Microsoft SQL Server 2005 Enterprise splash
screen will automatically open. The Enterprise edition of SQL 2005 will
automatically install the necessary program files on both nodes during
installation.
• If the Microsoft SQL Server 2005 splash screen does not automatically
display, click the Start button, then select Run. In the Run window,
browse for splash.hta on the disc drive. Alternatively, you can run

revision 1 — 17
4: Install SQL Server 2005 Enterprise Edition

splash.hta from Explorer. The Microsoft SQL Server 2005 splash

screen is displayed.
2. To begin the installation process, click Server components, tools, Books
Online, and samples.

3. In the End User License Agreement window:

a. If you agree with the license terms, select I accept the licensing terms
and conditions.
b. Click [Next]

4. The Installing Prerequisites step installs any of the listed components that are missing
from your system. Click [Install].

18 — revision 1
 Using Microsoft® Cluster Services with OnGuard

5. When the component installation is complete, click [Next] to begin the

installation wizard. Prior to this, the SQL Server setup will scan your
computer’s configuration.

6. On the Welcome page of the SQL Server Installation Wizard, click [Next] to
continue.

7. Wait for the System Configuration Check to complete and then click

revision 1 — 19
4: Install SQL Server 2005 Enterprise Edition

[Next >].

8. On the Registration Information window:

a. Type your name and company in the Name and Company fields.
b. Type your Product Key (this 25 character number is located on the
yellow sticker in the installation disc liner notes or the sleeve of the
installation disc).
c. To continue, click [Next].

9. On the Components to Install window:

a. Select the SQL Server Database Services check box.
b. Select the Create a SQL Server failover cluster check box.
c. Click [Next].

20 — revision 1
 Using Microsoft® Cluster Services with OnGuard

d. Optionally, click [Advanced] to select program features you want to

install such as Management Tools. The Feature Selection window is
displayed.
10. On the Instance Name window:
a. Ensure the Default instance radio button is selected.
b. Click [Next].
11. On the Virtual SQL Server Name window:
a. Type the desired name of the new or existing virtual SQL Server.

Notes: This is the name used to identify the failover cluster on your network.The
virtual SQL Server name must be unique on your network and different than
the names of the host cluster and cluster nodes.
The Virtual SQL Server Name window only displays if setup detects that
you are running Microsoft Cluster Server. If the Virtual SQL Server Name

revision 1 — 21
4: Install SQL Server 2005 Enterprise Edition

window does not display, cancel setup and configure Microsoft Cluster
Server.

b. To continue, click [Next].

12. On the Virtual Server Configuration window:

a. In the Network to Use drop-down, select “Mixed Cluster Connection”.
b. Type the virtual IP address.

Note: This is the IP address that will be shared between servers and bound to the
virtual SQL server name.

c. Click [Add]. The IP address and the subnet are displayed.

d. Optionally, continue to configure IP addresses for each installed
network until you have populated all desired networks with an IP
address.

22 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Notes: One IP address is added for each network on which the failover cluster
instance is available to clients on a public (or mixed) network. Only one IP
address is allowed on each subnet.
To avoid IP address conflicts, make sure the IP addresses assigned to the
heartbeat and to SQL Server 2005 are not shared by any other application.

e. To continue, click [Next].

13. On the Cluster Group Selection window:

a. Select the group that contains the drive you want to use for SQL Server
from the Available Cluster Groups.

Note: The selected cluster group is where the SQL Server virtual SQL Server
resources are placed. If you select the group containing the cluster Quorum

revision 1 — 23
4: Install SQL Server 2005 Enterprise Edition

resource, a warning is displayed recommending you do not install to the

cluster quorum resource.

b. You can also specify a custom path for data files in the Data Files field.
c. To continue, click [Next].

14. On the Cluster Node Configuration window, specify the nodes to include in
the failover cluster instance:
a. To add a node to the failover cluster instance: Select the computer from
the Available nodes list and click [Add].
b. To remove a node from the failover cluster instance: Select the
computer from the Selected nodes list and click [Remove].

24 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Notes: Any nodes that are unavailable are displayed in the Unavailable nodes list,
as well as the reason the node is unavailable.
To create a one-node failover cluster, only the node that will be installed with
the failover cluster instance should be listed in the Required node list.

c. To continue, click [Next].

15. On the Remote Account Information window, specify the remote login
information by typing a user name (Account) and Password that has
administrator rights on all nodes of the cluster.

Note: This window displays only if you are installing to a remote node. The
credentials you provide are used only during SQL Server setup to configure
SQL Server on each node in the failover cluster instance. This account must
be a valid administrator account on all nodes of the cluster.

revision 1 — 25
4: Install SQL Server 2005 Enterprise Edition

To continue, click [Next >}.

16. On the Service Account window:

a. Type the Username, Password, and Domain name for the SQL Server
service accounts.

26 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Notes: You can use one account for all of the services. All service accounts for a
failover cluster instance must be domain accounts.
The domain name cannot be a full DNS name. For example, if your DNS
name is “lenel_domain.com”, use “lenel_domain” in the Domain field. SQL
Server will not accept “lenel_domain.com” in the Domain field.

b. Select the Customize for each service account check box to specify
the Username, Password, and Domain for specific services, selecting
the service from the Service drop-down.

Important: The account for the SQL Server Agent service must be an administrator for
the cluster node. Do not use the same account assigned to the cluster service.

Optionally, you can specify an individual account for each service:

c. After selecting the Customize for each service account check box. and
a service from the Service drop-down, then provide login credentials for
the service.
d. When you have completed service account setup, to continue, click
[Next].

17. On the Domain Groups for Clustered Services window:

a. Type or browse for the DomainName\GroupName for each clustered
service being installed: the SQL Server service, SQL Server Agent

revision 1 — 27
4: Install SQL Server 2005 Enterprise Edition

service, and Full-Text Search service must run as domain accounts that
are members of the global or local domain group.
b. To continue, click [Next].

18. On the Authentication Mode window:

a. Select the Mixed Mode (Windows Authentication and SQL Server
Authentication) radio button.
b. Type and confirm a strong password for the System Administrator (sa)
login.
c. To continue, click [Next].

19. On the Collation Settings window, click [Next].

For upgrades: This screen will not be displayed.
20. On the Error and Usage Report Settings window, optionally clear the
checkbooks to disable error reporting or feature usage reporting.
To continue, click [Next].

28 — revision 1
 Using Microsoft® Cluster Services with OnGuard

21. On the Ready to Install window:

a. Review the summary of features and components for your SQL Server
installation.
b. To continue, click [Install].

22. On the Setup Progress window:

a. You can monitor installation progress on individual cluster nodes by
selecting a node from the Node drop-down. Setup progress is displayed
for the selected node:

revision 1 — 29
4: Install SQL Server 2005 Enterprise Edition

MSCLUSTER-A

30 — revision 1
 Using Microsoft® Cluster Services with OnGuard

MSCLUSTER-B

b. To view the log file for a component during installation, click the
Product or Status name on the Setup Progress window.
c. When the configuration of SQL Server is done, click [Next] to continue.
23. On the Completing the Microsoft SQL Server 2005 Setup window:
a. View the Setup Summary Log by clicking the link provided on this
window.
b. To exit the SQL Server Installation Wizard, click [Finish].

revision 1 — 31
4: Install SQL Server 2005 Enterprise Edition

Note: Make sure that the SQL program files are directed to either the system drive
or the application drive, and the SQL data files are directed to the SQL data
drive that is part of the cluster.

24. Create a database under the SQL virtual computer name according to the
Lenel requirements on the active server. It will automatically be created on
the other server. (Refer to the Installation Guide for detailed instructions.)
25. After you have completed configuration of Microsoft Cluster Services and
SQL Server 2005 Enterprise Edition, open Cluster Administrator by
selecting the following:
Click the Windows Start button, then select Programs > Administrative Tools >
Cluster Administrator.

The configuration should resemble the following graphic:

32 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Chapter 5: OnGuard Installation and Configuration

for Clustering Services

Follow the steps below to install and configure OnGuard 2008 on both of the
clustering servers.

Note: This is a brief overview of the installation of OnGuard 2008. Please refer to
the Installation Guide for more in-depth installation instructions.

Installing OnGuard Server Software

Important: Due to conflicts with service pack 1 for Windows 2003 OnGuard runs a
Lenel Windows Security Utility during installation. Read the release notes
carefully before continuing with the installation.

1. Insert the OnGuard installation disc into the disc drive.

2. Click the Start button on the taskbar, then select Run. In the Run window,
select setup.exe from the disc drive.
3. When prompted, read the Software License Agreement. If you agree to its
terms:
a. Select the I accept the terms of the license agreement option.
b. Click [Server].
4. Next, you will be prompted to enter the System Type Information.
a. Select the Custom System radio button.

Note: To include or exclude certain features, the Custom System option is

selected. If you select this option a window is displayed allowing you to
select features not included with the Default System option. You must do a
custom install to use the browser-based clients. Before installing browser-
based applications your system must have IIS installed and meet other

revision 1 — 33
5: OnGuard Installation and Configuration for Clustering Services

requirements. Installing the browser-based applications without meeting the

proper requirements could result in major system problems.

b. Select the SQL Server radio button.

c. Click [Next].
5. The System Location Information window will be displayed.
a. Either accept the default installation directory or click [Browse…] to
specify a different destination folder.
b. Change the License Server location to the Cluster computer name.
This is the name that you entered in step 6 on page 12.
c. In the Port field, enter the number of the port to be used for access
control system communication. It is recommended that you accept the
default value of 8189.
d. Change the SQL Database Location to the virtual SQL Server name.
This is the name that you entered in step 11 on page 21.
e. Click [Next].
6. The Custom Setup window is displayed.
a. Expand the Server Applications node and scroll to the Web Application
Server feature.
b. Click the down-arrow to open the pop-up menu for this feature and
select This feature will be installed on local hard drive.
c. Click [Next].
7. Click [Install] to start the OnGuard installation.
• If you chose to custom install the Web Application Server, additional
prompts will be displayed. Follow the on screen instructions and
provide the virtual server name, user name, and password.
• Installation may take several minutes as indicated by the progress bar.
8. A check is performed behind-the-scenes to determine if a language pack is
installed. If an old language pack is installed, you receive a warning
message. Do one of the following:
• If you wish to cancel the installation and remove the language pack by
yourself, click [Cancel].
• If you wish to remove the language pack and continue the installation,
click [Remove & Continue].

Important: Lenel software requires certain security adjustments to operating systems

using Service Pack 2 or later (Windows XP) or Service Pack 1 or later
(Windows Server 2003). For those who have installed the service packs, a
Windows Service Pack Utility which allows OnGuard to function properly,
runs during installation. Please review the Windows Service Pack Utility
release notes provided prior to running this utility, which then makes these
adjustments automatically. Upon agreeing to the disclaimer, the user

34 — revision 1
 Using Microsoft® Cluster Services with OnGuard

assumes responsibility for any security issues that may occur due to these
adjustments.

9. Once the installation is complete, the database installation utility and Lenel
Windows Security Utility run. Follow the on screen instructions to finish the
installation.
10. Click [Finish] upon successful completion of the installation.
11. Depending on the components that you chose to install, you may need to
restart the computer. If you are prompted to do so, reboot the computer.
12. Once the server has restarted, navigate to the Administrative Tools menu
and open Services. Set all of the OnGuard services to “Manual” startup with
the exception of the LS Login Driver. The LS Login Driver should be set
to “Automatic” startup.
13. Repeat steps 1-12 on the second clustered server.

Installing the OnGuard Software Dongle and License File

The license file needs to be installed on the active cluster computer. Once this is
completed on the first server, the cluster must be failed over to the second server
and all the steps below must be repeated. If the license files are not installed
correctly, the applications will not work when the cluster is failed over.

1. Attach the appropriate software dongle to each of the clustered servers.

A hardware security key protects OnGuard software. Please remember to
physically attach the hardware key (“dongle” adapter) directly to the parallel
port on the computer that has License Server installed in order for the
software to run properly.

Note: If you have a USB dongle instead of a parallel port dongle, you must install
the driver for the dongle BEFORE attaching the USB hardware key to the
PC. The driver for the dongle is located in the Rainbow directory on the
Supplemental Materials disc. When you install the driver, make sure both the

revision 1 — 35
5: OnGuard Installation and Configuration for Clustering Services

USB and Parallel drivers are selected for installation. For more information,
refer to “Configure a USB Hardware Key” in the Installation Guide.

A hardware dongle is only needed on the server running License Server.

Each client computer running OnGuard 2008 uses a software license instead
of a hardware dongle.
2. Obtain a new OnGuard license file. License files have the extension (*.xml,
*.lic, or *.lic.xml). Be sure that you know where the license file is saved, as
you will need to know the location to successfully install the license.
3. Manually start the LS License Server service.
4. Start the License Administration application.
5. Log into the License Administration application.
6. Click the Install New License… hyperlink.
7. In the License file field, enter the name and location of the file containing
the license that you want to install. You can use the [Browse…] button to
locate the file.
8. Click [Next].
9. View the license and make sure that the license is the correct license.
10. Scroll down to the bottom of the window and click [Next].
If the license is not the correct license, click [Back] to go back and choose
another license file.
11. Read the terms of the license agreement.
12. Select the Yes radio button if you agree with the terms of the license.
13. Click [Finish].
14. The license will be installed. The entry that is displayed in the Installed
Licenses drop-down list box indicates the name of the product that the
license controls, and will be updated to include the new license.
15. Manually stop the LS License Server service. Make sure that the service is
still configured for “Manual” start.
16. Execute a manual failover of the cluster.
17. Repeat steps 1-16 on the second server.

Setting Up the OnGuard Database

After OnGuard and the database software have been installed and configured,
you must then install the access control-related reports, tables, triggers, and
default data. The Database Setup application will automatically do this for you.

36 — revision 1
 Using Microsoft® Cluster Services with OnGuard

The following steps need to be completed on the active server only. The cluster
shares an instance of SQL so the database only needs to be created once.

1. Make sure the LS License Server service is started.

2. Click the Start button, then select Programs > OnGuard 2008 > Database
Setup.
3. You will be prompted for a valid ‘LENEL’ login to SQL. Enter the password
and click [OK].
4. The Welcome window will be displayed. Click [Continue].
5. In the Database Setup Options window:
a. Select the Create new database radio button if you don’t already have
a database. This option will install the access control-related reports,
tables, triggers, and default data.
b. Click [Continue].
6. Click [Exit] upon successful completion.
7. LS License Server should now be stopped.

OnGuard Service Registry Fix

The following fix must be applied to all servers in the cluster to allow the
OnGuard services, such as LS Linkage Server, LS Communications Server,
and LS Replicator Service, to start under the virtual cluster name. If this fix is
not applied to all of the servers in the cluster, the services will not be able to start
on the virtual cluster computer.

1. Apply patch for the OnGuard services to the registry by running the registry
file named OnGuard_Clustering_Services_Fix.reg from the Supplemental
Materials disc under Database Utilities > Clustering Materials.
2. Repeat the process on the secondary server.

Note: If the virtual computer name is not FAILOVER, the registry keys will need
to be further edited.

3. If the value for the virtual server name needs to be changed:

Note: The registry key will need to be changed if the Cluster name which was
configured in step 6 on page 12 is anything other than ‘FAILOVER’.

a. Using regedit.exe, navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Vinca\CoStandby\ClusterItems\
CLU_IPADDRS\192.168.1.111

revision 1 — 37
5: OnGuard Installation and Configuration for Clustering Services

Note: The directory that is named as the IP address does not have to be changed to
match your virtual cluster IP address, however, it can be if you would like.

b. Right click on the key named “NtsCluGroupRef” and choose modify.

c. Enter the Cluster name that was created in step 6 on page 12.
d. Save the changes and exit out of regedit.exe.

Refer tp the graphic of the Registry Editor that follows:

4. Restart the server.

5. Repeat steps 1-4 on the second cluster server.

38 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Chapter 6: Adding OnGuard Services to the Cluster

Failover

The steps that follow describe how to add the OnGuard services to the Cluster
Failover so that the OnGuard applications and database can run and be accessed
in the event of a server failure.

revision 1 — 39
6: Adding OnGuard Services to the Cluster Failover

In order to have OnGuard incorporated into the failover process, the necessary
OnGuard services need to be added as resources to the cluster. Open Cluster
Administration and follow the steps that follow.

1. Right click on ‘Cluster Group’ and select New > Resource.

2. The New Resource window opens. The first service that needs to be added is
LS License Server.

a. In the Name field, type LS License Server.

b. In the Resource Type drop-down list, select “Generic Service.”
c. In the Group drop-down list, select your Cluster Group (not the SQL
Group).
d. Click [Next].
3. For Possible owners, select both of the cluster servers and click [Add]. Once
both servers are listed as possible owners, click [Next].

4. Select dependencies for the service. You will need to select ”Cluster Name”
as a dependency. This determines the failover order. (The LS License
Server service will not start until the Cluster Name has started). Once the
dependency is selected, click [Next].

40 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Note: If you are configuring a service other than the LS License Service, you will
need to select only the LS License service resource as the dependency. All
OnGuard services need to be started after the LS License Server has started.

5. The Generic Service Parameters window will appear.

a. In the Service Name field, enter the exact name of the service. (This can
be found in Administrative Tools > Services under the properties for
the specific service.
b. In the Startup parameters field, do not enter anything.
c. Click [Next].
6. The Registry Replication window is displayed. Leave the window blank and
click [Finish].

revision 1 — 41
6: Adding OnGuard Services to the Cluster Failover

7. Repeat steps 1-6 for all other required OnGuard services such as LS Linkage
Server, LS Communications Server, and the LS Replicator.
8. Each service added to the Cluster Group needs to be brought online:
a. Right-click the service then select Bring Online.
b. An exception to this is the LS Linkage Server which must first be
configured in OnGuard using System Options to set a Linkage Server
otherwise the Online attempt will fail.

Once all the necessary resources have been created and added to the cluster, your
Cluster Administration window should be similar to what is shown in the
following graphic.

42 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Note: You may not have all the OnGuard services added as resources. You should
see all the necessary services listed as resources that you added.

The last thing that should be done is the execution of a manual failover to test and
verify your cluster configuration. If you have configured everything successfully,
all resources should come online and you should be able to access all OnGuard
applications and monitor configured hardware from the active cluster server no
matter which one it is.

revision 1 — 43
6: Adding OnGuard Services to the Cluster Failover

44 — revision 1
 Using Microsoft® Cluster Services with OnGuard

Index

A R
Adding OnGuard services to the cluster failover 39 Requirements
OnGuard ........................................................ 6
C operating system ............................................ 6
Clustering SQL Server .................................................... 6
description...................................................... 5
how it works .................................................. 6 S
installing and configuring OnGuard for ...... 33 Services
operating system requirements ...................... 6 adding to cluster failover ............................. 39
SQL Server requirements .............................. 6 registry fix.................................................... 37
Configuring Setting up the OnGuard database........................ 36
NICs............................................................. 10 SQL Server requirements...................................... 6
OnGuard for clustering ................................ 33
PERC controller........................................... 11
Configuring hardware ........................................... 9

D
Database
recovery ......................................................... 6
setting up OnGuard...................................... 36
Dongle................................................................. 35

H
Hardware configuration ........................................ 9

I
Installing
dongle .......................................................... 35
license file.................................................... 35
Microsoft Cluster Services .......................... 11
Microsoft Windows 2003 Advanced Server 11
OnGuard ...................................................... 33
OnGuard for clustering ................................ 33
SQL Server 2005 Enterprise Edition ........... 17

L
License file.......................................................... 35

O
OnGuard
adding services to the cluster failover ......... 39
installation and configuration for clustering
services ................................................. 33
requirements .................................................. 6
service registry fix ....................................... 37
setting up the database ................................. 36
Operating system requirements ............................ 6

revision 1 — 45
Lenel Systems International, Inc.
1212 Pittsford-Victor Road
Pittsford, New York 14534 USA
Tel 585.248.9720 Fax 585.248.9185
www.lenel.com
[email protected]

© 2008 Lenel Systems International, Inc.