Milestone XProtect Corporate 4.1

XProtect ®
Corporate 4.1
Administrator’s
Manual
Target Audience for this Document
This document is aimed at surveillance system administrators installing and/or managing an XProtect Corporate
surveillance System. It is solely aimed at XProtect Corporate administrators, and administrator rights are likely to
be required in order to be able to access the majority of features described in this document.
This document provides detailed descriptions of XProtect Corporate system administration features. It furthermore
provides a large number of targeted ―how-to‖ examples, guiding administrators through completing common
administration tasks in XProtect Corporate.
This document contains very limited information of relevance to end-users. End-users will be able to find
information targeted at their needs in the separate manuals available on the XProtect Corporate software DVD as
well as from www.milestonesys.com.
Administrators requiring information about end-user related applications, such as the Smart Client or the Matrix
Monitor, should refer to the targeted manuals available on the XProtect Corporate software DVD as well as from
www.milestonesys.com.
XPCO41-am-1(a1)-081011
Contents
INTRODUCTIONS ............................................................................................... 7
Product Overview ....................................................................................................................................... 7
SYSTEM REQUIREMENTS ............................................................................... 10
Computer Running Management Server .................................................................................................. 10
Computer Running Recording Server or Failover Server ......................................................................... 10
Computer Running Management Client (Unlicensed and Free) ............................................................... 11
Computer Running Event Server.............................................................................................................. 11
Computer Running Log Server ................................................................................................................. 11
Computer Running Service Channel ........................................................................................................ 12
Computer Running Smart Client (Unlicensed and Free) .......................................................................... 13
Computer Accessing Remote Client (Unlicensed and Free) .................................................................... 13
Active Directory (Recommended)............................................................................................................. 14
ACCESS CLIENTS ............................................................................................ 15
Access Client Overview ............................................................................................................................ 15
Smart Client ............................................................................................................................................. 16
Remote Client........................................................................................................................................... 18
USE THE BUILT-IN HELP SYSTEM ................................................................. 20
Navigating the Built-in Help System ......................................................................................................... 20
Links in Help Topics ................................................................................................................................. 20
Printing Help Topics ................................................................................................................................. 20
Browsers supported ................................................................................................................................. 21
INSTALLATION AND REMOVAL ..................................................................... 22
Installation Overview ................................................................................................................................ 22
Install Management Server ...................................................................................................................... 23
Install System Components ...................................................................................................................... 27
Install Event Server and Log Server (Custom) ......................................................................................... 31
Install Service Channel (Custom) ............................................................................................................. 33
Important Port Numbers ........................................................................................................................... 36
List of Ports Used by XProtect Corporate ................................................................................................. 36
Multiple Management Servers (Clustering) .............................................................................................. 37
Multiple Recording Server Instances ........................................................................................................ 40
Remove System Components .................................................................................................................. 40
Upgrade from Previous Version ............................................................................................................... 42
Installation Troubleshooting ..................................................................................................................... 44
Use Download Manager ........................................................................................................................... 48
www.milestonesys.com
Page 3
MANAGEMENT CLIENT ................................................................................... 53
Management Client Overview .................................................................................................................. 53
Panes Overview ....................................................................................................................................... 56
Get Started ............................................................................................................................................... 57
Log in to the Management Client ............................................................................................................. 59
Management Client Menu Overview ........................................................................................................ 60
Customize the Management Client's Layout ............................................................................................ 61
Activate Licenses ..................................................................................................................................... 64
Manage Licenses ..................................................................................................................................... 67
Manage Software License Codes (SLC) .................................................................................................. 69
Servers ..................................................................................................................................................... 70
Devices .................................................................................................................................................... 96
Client ...................................................................................................................................................... 134
Rules and Events ................................................................................................................................... 140
Security .................................................................................................................................................. 164
System Dashboard ................................................................................................................................. 177
Server Logs ............................................................................................................................................ 178
Alarms .................................................................................................................................................... 182
Enterprise ............................................................................................................................................... 191
Registered Services ............................................................................................................................... 194
Options ................................................................................................................................................... 195
FEDERATED ARCHITECTURE ...................................................................... 201
Federated Architecture Overview ........................................................................................................... 201
Manage Federated Architecture ............................................................................................................. 207
BACK UP, MOVE, RESTORE SYSTEM CONFIGURATION .......................... 213
Prerequisites .......................................................................................................................................... 214
Backing up System Configuration .......................................................................................................... 214
Backing Up Event Server Configuration ................................................................................................. 216
Backing Up Log Server Database .......................................................................................................... 216
Installing New Management Server on New Database .......................................................................... 216
Restoring System Configuration ............................................................................................................. 217
Restoring Event Server Configuration .................................................................................................... 218
DEVICE DRIVERS ........................................................................................... 220
Manage and Remove Video Device Drivers ........................................................................................... 220
FAILOVER SERVERS ..................................................................................... 222
Failover Server Service Administration .................................................................................................. 222
Manage Failover Servers ....................................................................................................................... 223
MAPS ............................................................................................................... 229
www.milestonesys.com
Page 4
DATABASE CORRUPTION ............................................................................ 230
Protect Databases from Corruption ........................................................................................................ 230
SERVICES ADMINISTRATION ....................................................................... 231
About the Service Channel ..................................................................................................................... 231
Management Server Service and Recording Server Service ................................................................. 231
VIRUS SCANNING INFORMATION ................................................................ 235
SNMP ............................................................................................................... 236
Installing the SNMP Service ................................................................................................................... 236
Configuring the SNMP Service ............................................................................................................... 236
DAYLIGHT SAVING TIME ............................................................................... 237
Spring: Switch from Standard Time to DST ............................................................................................ 237
Fall: Switch from DST to Standard Time ................................................................................................ 237
IPV6 ................................................................................................................. 239
Important Information if Using XProtect Corporate with IPv6 ................................................................. 239
How to Write IPv6 Addresses ................................................................................................................. 240
MULTI-DOMAIN ENVIRONMENT WITH ONE-WAY TRUST .......................... 241
INDEX .............................................................................................................. 242
www.milestonesys.com
Page 5
Introductions
Milestone XProtect Corporate 4.1; Administrator's Manual
Disclaimers
Copyright
© 2011 Milestone Systems A/S.
Trademarks
XProtect is a registered trademark of Milestone Systems A/S.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
All other trademarks mentioned in this document are trademarks of their respective owners.
Disclaimer
This document is intended for general information purposes only, and due care has been taken in its preparation.
Any risk arising from the use of this information rests with the recipient, and nothing herein should be construed
as constituting any kind of warranty.
Milestone Systems A/S reserve the right to make adjustments without prior notification.
All names of people and organizations used in this document’s examples are fictitious. Any resemblance to any
actual organization or person, living or dead, is purely coincidental and unintended.
This product may make use of third party software for which specific terms and conditions may apply. When that
is the case, you can find more information in the file 3rd_party_software_terms_and_conditions.txt located in your
Milestone surveillance system installation folder.
www.milestonesys.com
Page 6
Milestone XProtect Corporate 4.1; Administrator's Manual
Introductions
Product Overview
XProtect Corporate is a fully distributed solution, designed for large multi-site and multiple
server installations requiring 24/7 surveillance, with support for devices from different
vendors. The solution offers centralized management of all devices, servers, and users,
and empowers an extremely flexible rule system driven by schedules and events.
XProtect Corporate consists of the following main elements:

The Management Server - the center of your installation

One or more recording servers

One or more management clients, which are unlicensed and can be downloaded and installed for free
(a many times as needed).

A Download Manager

One or more Smart Clients and Remote Clients, which are both unlicensed and can be downloaded
and installed for free (a many times as needed).
You can read more about each of these in the following.
Furthermore, XProtect Corporate includes fully integrated Matrix functionality for distributed viewing of video from
any camera on your surveillance system to any computer with a Smart Client installed.
The system also offers the possibility of including a standalone Viewer application when exporting video evidence
from the Smart Client. The Viewer allows recipients of video evidence (such as police officers, internal or external
investigators, etc.) to browse and play back the exported recordings without having to install any software on their
computers.
Finally, XProtect Corporate handles an unlimited number of cameras, servers, and users— across multiple sites if
required. XProtect Corporate is capable of handling IPv4 as well as IPv6 (see page 239).
An Example of a typical XProtect Corporate setup:
The number of cameras and recording servers, as well as the number of connected access clients, can be as
high as you require.
Legend:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
Management Client(s)
Event Server
Microsoft Cluster
Management Server
Management Failover
Server
SQL Server
Failover Recording
Server
Recording Server(s)
Smart Client
Smart Wall PC
Smart Wall
IP Video Cameras
Video Server
Analog Cameras
PTZ IP Camera
Camera Network
Server Network
www.milestonesys.com
Page 7
Introductions
Milestone XProtect Corporate 4.1; Administrator's Manual
About Updates
Milestone Systems regularly release service updates for our products, offering improved functionality and support
for new devices.
If you are an XProtect Corporate system administrator, it is recommended that you check the Milestone Systems
website www.milestonesys.com for updates at regular intervals in order to make sure you are using the most
recent version of XProtect Corporate.
The Management Server

What? Stores the surveillance system's configuration in a relational database, either on the
management server computer itself or on a separate SQL Server on the network. Also handles user
authentication, user rights, etc. To enhance system performance, several management servers can be
run a as a Milestone Federated HierarchyTM (see page 201).

Where? Runs as a service, and is typically installed on a dedicated server.
What comes along with the Management Server? Furthermore, when installing the Management
Server, you get the following integrated components as well (if you select Typical Management Server
Installation for more information):
o
The Event Server

What? Stores and handles incoming alarm data and events from all XProtect Enterprise and
XProtect Corporate servers in a federated hierarchy, thus enabling powerful monitoring and
instant overview of alarms and possible technical problems within your systems.

o
The Log Server

What? Provides the necessary functionality for logging information from your XProtect
Corporate installation.

o
Where? Usually installed on the same server as the management server and runs as a service.
Where? Usually installed on the same server as the management server and runs as a service.
The Service Channel

What? Enables automatic and transparent configuration communication between servers and
clients in your XProtect Corporate installation.

Where? Usually installed on the same server as the management server and runs as a service.
The Recording Server

What? Used for recording video and for communicating with cameras and other devices. In large
installations, more than one recording server is often used on the surveillance system. Failover servers
can be set up to take over if a recording server becomes temporarily unavailable.

Where? Recording servers as well as failover servers run as services, and are typically installed on
separate servers rather than on the management server itself.
The Management Client

What? Feature-rich administration client for configuration and day-to-day management of the system.
Available in several languages.

Where? Typically installed on the surveillance system administrator's workstation or similar.
www.milestonesys.com
Page 8
Introductions
Milestone XProtect Corporate 4.1; Administrator's Manual
The Download Manager

What? Lets surveillance system administrators manage which XProtect Corporate -related components
(e.g. particular language versions of clients) your organization's users will be able to access from a
targeted web page generated by the management server.

Where? Automatically installed on the management server during XProtect Corporate installation
process.
The Smart Client and Remote Client

What? Clients enabling access to live and recorded video as well as other key surveillance system
features, such as export of recordings for use as evidence.

Where? Depends on type of client. The very feature-rich Smart Client must be installed on users'
computers. The more basic Remote Client is accessed through a browser, and run directly from the
XProtect Corporate management server without the need for any installation.

How? Users connect to the management server for initial authentication, then transparently to the
recording servers for video recordings, etc.
www.milestonesys.com
Page 9
Introductions
Milestone XProtect Corporate 4.1; Administrator's Manual
System Requirements
IMPORTANT: XProtect Corporate no longer supports Microsoft® Windows® XP (however, clients can still be
run/accessed from computers with Windows XP Professional).
It is recommended to have the Microsoft Active Directory® in place before you install XProtect Corporate. If you
add the Management Server to the Active Directory after installing XProtect Corporate, you must re-install the
Management Server, and replace users with new users defined in the Active Directory.
The following are minimum requirements for the computers used in an XProtect Corporate solution:
Computer Running Management Server

CPU: Intel® Xeon® , minimum 2.0 GHz (Dual Core recommended)

RAM: Minimum 1 GB (2 GB or more recommended)

Network: Ethernet (1 Gbit recommended)

Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors

Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)

Hard Disk Space: Minimum 50 GB free (depends on number of servers, cameras, rules, and logging
settings)

Operating System: Microsoft® Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008
(32 or 64 bit), Microsoft® Windows® Server 2003 (32 or 64 bit).
Furthermore, to run clustering/failover servers, a Microsoft® Windows® Server 2003/2008 Enterprise or
Data Center edition is needed.

Software: Microsoft .NET 3.5 SP1 and .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
Computer Running Recording Server or Failover Server

CPU: Dual Core Intel Xeon, minimum 2.0 GHz (Quad Core recommended)

RAM: Minimum 1 GB (2 GB or more recommended) Network: Ethernet (1 Gbit recommended)

Graphics Adapter: Onboard GFX, AGP, or PCI-Express, minimum 1024×768, 16 bit colors

Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)

Hard Disk Space: Minimum 100 GB free (depends on number of cameras and recording settings)

Operating System: Microsoft® Windows® 7 Ultimate (32 bit or 64 bit*), Microsoft® Windows® 7
Enterprise (32 bit or 64 bit*), Microsoft® Windows® 7 Professional (32 bit or 64 bit*), Microsoft®
Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008 (32 or 64 bit*), Microsoft®
Windows® Vista® Business (32 or 64 bit*), Microsoft® Windows® Vista Enterprise (32 or 64 bit*),
Microsoft® Windows® Vista Ultimate (32 or 64 bit*) or Microsoft® Windows® Server 2003 (32 or 64 bit*).
* Note that recording servers will always run 32-bit
Tip: You can run multiple instances of the 32-bit recording server service on servers with 64-bit
operating systems and sufficient RAM; see Multiple Recording Server Instances.
www.milestonesys.com
Page 10
System Requirements
Milestone XProtect Corporate 4.1; Administrator's Manual

Software: Microsoft .NET 4.0 Framework.
IMPORTANT: When formatting the hard disk of a recording/failover server device, it is important to change its
Allocation unit size setting from 4 to 64 kilobytes. This is to significantly improve recording performance of the
hard disk. You can read more about allocating unit sizes and find help at
http://support.microsoft.com/kb/140365/en-us.
Computer Running Management Client (Unlicensed and
Free)

CPU: Intel Core2™ Duo, minimum 2.0 GHz

RAM: Minimum 1 GB

Network: Ethernet (100 Mbit or higher recommended)

Graphics Adapter: AGP or PCI-Express, minimum 1024×768 (1280×1024 recommended), 16 bit colors

Hard Disk Space: Minimum 100 MB free

Operating System: Microsoft® Windows® 7 Professional (32 bit or 64 bit*), Microsoft® Windows® 7
Enterprise (32 bit or 64 bit*), Microsoft® Windows® 7 Ultimate (32 bit or 64 bit*), Microsoft® Windows®
Vista Ultimate (32 bit or 64 bit*), Microsoft® Windows® Vista Enterprise (32 bit or 64 bit*), Microsoft®
Windows® Vista Business (32 bit or 64 bit*), Microsoft® Windows® Server 2008 (32 bit or 64 bit*),
Microsoft® Windows® Server 2008 R2 (64 bit) or Microsoft® Windows® Server 2003 (32 bit or 64 bit*).
*Running as a 32 bit service/application

Software: Microsoft .NET 4.0 Framework, DirectX 9.0 or newer, and Windows Help (WinHlp32.exe)
which you can download from http:// www.microsoft.com/downloads/.
Computer Running Event Server

CPU: Intel® Xeon® , minimum 2.0 GHz (Dual Core recommended)

RAM: Minimum 1 GB (2 GB or more recommended)

Network: Ethernet (1 Gbit recommended)

Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors

Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)

Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging
settings)

Operating System: Microsoft® Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008
(32 or 64 bit), Microsoft® Windows® Server 2003 (32 or 64 bit)

Software: Microsoft .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
Computer Running Log Server

CPU: Intel® Xeon® , minimum 2.0 GHz (Dual Core recommended)
www.milestonesys.com
Page 11
System Requirements
Milestone XProtect Corporate 4.1; Administrator's Manual

RAM: Minimum 1 GB (2 GB or more recommended)

Network: Ethernet (1 Gbit recommended)

Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors

Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)

Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging
settings)

Operating System: Microsoft® Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008
(32 or 64 bit), Microsoft® Windows® Server 2003 (32 or 64 bit)

Software: Microsoft .NET 4.0 and Internet Information Services (IIS) 5.1 or newer.
Computer Running Service Channel

CPU: Intel® Xeon® , minimum 2.0 GHz (Dual Core recommended)

RAM: Minimum 1 GB (2 GB or more recommended)

Network: Ethernet (1 Gbit recommended)

Graphics Adapter: Onboard GFX, AGP or PCI-Express, minimum 1024×768, 16 bit colors

Hard Disk Type: E-IDE, PATA, SATA, SCSI, SAS (7200 RPM or faster)

Hard Disk Space: Minimum 10 GB free (depends on number of servers, cameras, rules, and logging
settings)

Operating System: Microsoft® Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008
(32 or 64 bit)*, Microsoft® Windows® Server 2003 (32 or 64 bit)*
*Limited by Windows operating system to ten concurrent, incomplete outbound TCP connection attempts

Software: Microsoft .NET 4.0 Framework, and Internet Information Services (IIS) 5.1 or newer

If installing on Windows Server 2008, a standard IIS installation must furthermore be customized:
1.
In Windows Start menu, select Control Panel, then select Programs and Features.
2.
In the Programs and Features window, click Turn Windows features on or off. This opens the
Windows Features window (window name may be different depending on which operating
system you are installing the service channel on).
3.
In the Windows Features window, expand Internet Information Services.
4.
Expand and select Web Management Tools, then expand and select IIS 6 Management
Compatibility, then select IIS Metabase and IIS 6 configuration compatibility.
5.
Expand and select World Wide Web Services, then expand and select Application Development
Features, then select the following:

.NET Extensibility

ASP

ASP.NET
www.milestonesys.com
Page 12
System Requirements
Milestone XProtect Corporate 4.1; Administrator's Manual

ISAPI Extensions

ISAPI Filters.
6.
Expand and select Security, then select Windows Authentication.
7.
Click OK.
Computer Running Smart Client (Unlicensed and Free)

CPU: Intel Core2 Duo, minimum 2.0 GHz (Quad Core recommended for larger views)

RAM: Minimum 512 MB (1 GB recommended for larger views, 1 GB recommended on Microsoft
Windows Vista® )

Network: Ethernet (100 Mbit or higher recommended)

Graphics Adapter: AGP or PCI-Express, minimum 1280 × 1024, 16 bit colors

Hard Disk Space: Minimum 500 MB free

Operating System: Microsoft® Windows® 7 Professional (32 bit or 64 bit*), Microsoft® Windows® 7
Enterprise (32 bit or 64 bit*), Microsoft® Windows® 7 Ultimate (32 bit or 64 bit*), Microsoft® Windows®
Server 2008 R2 (64 bit), Microsoft® Windows® Vista Ultimate (32 bit or 64 bit*), Microsoft® Windows®
Vista Enterprise (32 bit or 64 bit*), Microsoft® Windows® Vista Business (32 bit or 64 bit*), Microsoft®
Windows® Server 2008, Microsoft® Windows® Server 2003 (32 bit or 64 bit*), Microsoft® Windows® XP
Professional (32 bit or 64 bit*).
* Running as a 32 bit service/application

Software: Microsoft .NET 4.0 Framework, DirectX 9.0 or newer, and Windows Help (WinHlp32.exe)
which you can download from http:// www.microsoft.com/downloads/.
Computer Accessing Remote Client (Unlicensed and Free)

CPU: Intel Pentium® 4, minimum 2.4 GHz

RAM: Minimum 256 MB (512 MB recommended for larger views, 1 GB recommended on Microsoft
Windows Vista)

Network: Ethernet (100 Mbit or higher recommended)

Graphics Adapter: AGP or PCI-Express, minimum 1024 x 768 (1280 x 1024 recommended), 16 bit
colors

Hard Disk Space: Minimum 10 MB free

Operating System: Microsoft® Windows® 7 Professional (32 bit or 64 bit*), Microsoft® Windows® 7
Enterprise (32 bit or 64 bit*), Microsoft® Windows® 7 Ultimate (32 bit or 64 bit*), Windows Vista Ultimate
(32 bit or 64 bit*), Windows Vista Enterprise (32 bit or 64 bit*), Windows Vista Business (32 bit or 64
bit*), Microsoft® Windows® Server 2008 R2 (64 bit), Microsoft® Windows® Server 2008, Windows
Server 2003 (32 bit or 64 bit*), Microsoft Windows® XP Professional (32 bit or 64 bit*)
*Running as a 32 bit service/application

Software: DirectX 9.0 or newer, and Windows Help (WinHlp32.exe) which you can download from http://
www.microsoft.com/downloads/.
www.milestonesys.com
Page 13
System Requirements
Milestone XProtect Corporate 4.1; Administrator's Manual
Active Directory (Recommended)
XProtect Corporate users are normally added from Active Directory, although users can also be added without
Active Directory.
Active Directory is a distributed directory service included with several Windows Server operating systems; it
identifies resources on a network in order for users or applications to access them.
If wishing to add users through the Active Directory service, a server with Active Directory installed, and acting as
domain controller, must be available on your network.
www.milestonesys.com
Page 14
System Requirements
Milestone XProtect Corporate 4.1; Administrator's Manual
Access Clients
Access Client Overview
Users can access an XProtect Corporate surveillance system with two different clients. Both clients are
unlicensed and can be downloaded and installed (a many times as needed) for free:

The Smart Client is very feature-rich and flexible for future integration of plugins, etc. The Smart Client
must be installed on users' computers.

The Remote Client has a more basic feature set. Its main benefit is that it is accessed through a
browser, and run directly from the XProtect Corporate management server without the need for any
client installation on the user's computer.
Both clients are included in the XProtect Corporate solution.
View Examples of the Two Clients
Examples of user interfaces: Smart Client (left) and Remote Client (right)
Which Client Should I Choose?
Which clients to use in your organization depend on your organization's needs. Note, however, that the two clients
can easily be used alongside each other: There is no problem in some of your users using the Smart Client and
others using the Remote Client.
Both clients provide access (user rights permitting) to key surveillance system features such as live and recorded
video, control of PTZ cameras and export of recordings for use as evidence. But if you want support for multiple
screens, audio, digital zoom, intelligent browsing of recordings, etc., the Smart Client should be your choice.
The following table outlines the main differences between the two clients:
www.milestonesys.com
Page 15
Access Clients
Milestone XProtect Corporate 4.1; Administrator's Manual
Access Clients at a Glance Smart Client
Remote Client
User's Installation
Client must be installed on user's computer.
None; client is accessed from
server through a browser.
User's Feature Set
Very feature-rich.
Basic features.
User's Ease of Use
Very easy to use. Setup of views can be handled locally as well as centrally.
With central views handling, remote users can begin using their client upon first
login.
System Administrator's
Installation
None required, although the administrator
would in most cases install a Smart Client
on his/her workstation.
None.
System Administrator's
Feature Set
Very flexible configuration through the
Management Client; options include
handling of local IP address ranges, NAT,
multicasting, etc.
Configuration through the
Management Client.
System Administrator's
Access Control Options
Users and their access rights are set up as part of roles definition process in the
Management Client.
Flexibility re. Future
Features and Plugins
Offers a high degree of flexibility for
integration of new features, plugins, etc.
Limited.
Recommended Use
Users who require audio. Users who
require access to the latest features. Users
who demand a high degree of flexibility re.
use of plugins.
Users who do not wish to install
client software. Users who find
that a .NET-based client solution
is not desirable.
How Do Client Users Connect to the Surveillance System?
Users connect to the XProtect Corporate management server for initial authentication, then transparently to the
recording servers for access to for video recordings, etc.
How Do I Set Up Users and their Rights?
You set up your surveillance system's users, and their access rights, as part of the roles definition process (see
page 164) in the XProtect Corporate Management Client.
Where Can I Find More Information?
See Smart Client Introduction (on page 16) and Remote Client Introduction (on page 18) respectively.
Smart Client
The Smart Client provides remote users with extremely
feature-rich access to the surveillance system.
Example of the Smart Client, in this case displaying live video
from 64 cameras
Tip: Like XProtect Corporate, the Smart Client supports IPv6
(see page 239).
www.milestonesys.com
Page 16
Access Clients
Milestone XProtect Corporate 4.1; Administrator's Manual
The Smart Client must be installed locally on the remote user's computer, which can be done in three different
ways. Naturally it can also subsequently be removed:
Where can I find more information about the Smart Client?
Once installed, the Smart Client has its own built-in help system. Alternatively, refer to the Smart Client User's
Manual, available on the XProtect Corporate software CD as well as from www.milestonesys.com. For Smart
Client system requirements, see System Requirements on page 10.
Installing the Smart Client from Server or CD
1.
Verify that your computer meets the Smart Client’s minimum system requirements, see page 10.
Downloading and Installing from the Surveillance System Server (Typical Method)
a.
Open an Internet Explorer browser (version 6.0 or later), and connect to surveillance system server
at the URL or IP address specified by your system administrator. The address is typically:
http://[management server address]:[port]/installation/
where [management server address] is the IP address or host name of the management
server, and [port] is the port number which IIS has been set up to use on the management
server.
When you are connected to the surveillance system server, you will see a welcome page.
b.
On the welcome page, click the required language link for the Smart Client.
Installing from the XProtect Corporate software CD (Alternative Method)
a.
Insert the surveillance system software CD, wait for a short while, select required language, then
click the Install Milestone XProtect Smart Client link.
Tip: Depending on your security settings, you may receive one or more security warnings (Do you
want to run or save this file?, Do you want to run this software? or similar; exact wording depends
on your browser version). When this is the case, accept the security warnings (by clicking Run or
similar; exact button names depend on your browser version).
b.
The Smart Client setup wizard begins. In the wizard, click Next, and follow the installation
instructions.
Installing the Smart Client silently (Surveillance System
Administrators Only)
For surveillance system administrators, it is possible to deploy the Smart Client to users’ computers using tools
such as Microsoft Systems Management Server (SMS). Such tools let administrators build up databases of
hardware and software on local networks. The databases can then— among other things— be used for
distributing and installing software applications, such as the Smart Client, over local networks.
In order to be able to deploy the Smart Client this way, it is necessary to make an installation package for a socalled silent installation, i.e. an installation which does not require end users to be actively involved. To make the
installation package, do the following:
You cannot complete the following procedure if you already have a Smart Client installed; in that case, remove
your existing Smart Client before completing this step.
1.
Locate the self-extracting Smart Client installation file MilestoneXProtectSmartClient.exe .
You find the file in a folder located under the Milestone surveillance software installation folder (typically
C:\Program Files\Milestone\XProtect Corporate Management Server\Clients\Binary\Client).
2.
With an extraction tool, such as WinZip® or similar, extract the files contained in
MilestoneXProtectSmartClient.exe to a folder of your choice.
3.
Make a response file for the silent installation:
www.milestonesys.com
Page 17
Access Clients
Milestone XProtect Corporate 4.1; Administrator's Manual
a.
Open a command prompt.
b.
With the command prompt, call the file setup.exe (located in the folder to which you extracted
MilestoneXProtectSmartClient.exe ) with the parameter /r.
This will start the Smart Client installation and record your subsequent actions in a response
file, which you will later use when deploying the Smart Client to end users.
c.
Go through the entire Smart Client installation.
d.
Exit the command prompt.
4.
The response file, called Setup.iss will be stored in your computer’s Windows folder (example:
C:\WINDOWS (or C:\WINNT if running Windows NT)). Copy the response file to the folder to which you
extracted MilestoneXProtectSmartClient.exe .
5.
Based on the content of the folder to which you extracted MilestoneXProtectSmartClient.exe (i.e. all the
original files as well as the newly created response file Setup.iss), create a new self-extracting file.
The new self-extracting file should use the following command after unzip: Setup.exe /s
6.
Use the new self-extracting file when deploying the Smart Client through your systems management tool
Removing the Smart Client
To remove a Smart Client, do the following on the computer on which the Smart Client is installed:
1.
In Windows' Start menu, select Control Panel, and select Add or Remove Programs. This will open the
Add or Remove Programs window.
2.
In the Add or Remove Programs window's list of currently installed programs, select Milestone XProtect
Smart Client x.x (where x.x refers to the version number).
3.
Click the Remove button, and follow the removal instructions.
Remote Client
The Remote Client provides users with basic access to the surveillance system. The Remote Client does not offer
nearly as many features as the Smart Client (see
page 16). The main benefit of the Remote Client is
that it is accessed through a browser and run directly
from the XProtect Corporate management server.
This eliminates the need for installing any client
software on the user's computer.
Example of the Remote Client, in this case displaying video
from 16 cameras
Tip: See system requirements for the Remote Client
under System Requirements on page 10.
Where can I find more information about the
Remote Client? Refer to the Remote Client User's
Manual, available on the XProtect Corporate software
CD as well as from www.milestonesys.com .
Accessing the Remote Client
1.
Open an Internet Explorer browser (version 6.0 or later), and connect to the surveillance system server
at the URL or IP address specified by your system administrator. The address is typically:
www.milestonesys.com
Page 18
Access Clients
Milestone XProtect Corporate 4.1; Administrator's Manual
http://[management server address]:[port]/installation/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
When you connect to the management server, you will see a welcome page. On the welcome page, click
the Remote Client link in order to view the Remote Client login dialog.
2.
3.
To log in, specify information in the following fields:

Previous Logins: Only available if you have logged in
before. Lets you reuse previously specified login details
(except any password, which you must always type
yourself). This can greatly speed up the login process.

Address: Type the URL or IP address of the
management server, as specified by your system
administrator.

Port: Internet connections may use different ports for different purposes. Specify the port number to
use when logging in to the Remote Client. In most circumstances, port 80 is used.

Authentication: Select required authentication method.
o
Windows (current user), with which you will be authenticated through your current Windows
login, and do not have to specify any user name or password. This is the default
authentication method, i.e. the method which is automatically used unless you select
another method.
o
Windows, with which you will be authenticated through your Windows login, but you will
need to type your Windows user name and password.
o
Basic, not used when connecting to an XProtect Corporate surveillance system.

Username: Type your user name. The user name is case-sensitive, i.e. there is a difference
between typing, for example, amanda and Amanda.

Password: Type your password. The password is case-sensitive.
Click the Login link. After a short wait, you get access to the Remote Client. Content in the Remote
Client is grouped on three tabs: Live, Browse and Setup.
The Live tab is used for viewing live video from cameras, the
Browse tab is used for finding and playing back recorded video, and the Setup tab is used for configuring
the Remote Client.
www.milestonesys.com
Page 19
Access Clients
Milestone XProtect Corporate 4.1; Administrator's Manual
Use the Built-in Help System
The XProtect Corporate Management Client features a comprehensive built-in help system. To use
the built-in help system, simply press the F1 key on your keyboard. When you press F1, the built-in
help system will open in a separate browser window, allowing you to easily switch between help and
the Management Client itself.
As an alternative to pressing the F1 key, click the toolbar's (see page 55) Help... button:
The built-in help system is context sensitive. This means that when you press F1 or click the Help... button while
working in a particular part of the Management Client, the help system automatically displays a help topic
describing that part, or a task related to that part.
Navigating the Built-in Help System
You are always able to freely navigate between the help system's contents. To
do this, simply use the help window's three tabs: Contents, Search, and
Glossary, or use the links inside the help topics.

Contents Tab: Lets you navigate the help system based on a tree structure. Many users will be familiar
with this type of navigation from, for example, Windows Explorer. To go straight to the help system's
Contents tab, click Contents... button in the Management Client's toolbar (see page 55).

Search Tab: Lets you search for help topics containing particular terms of interest. For example, you
can search for the term zoom and every help topic containing the term zoom will be listed in the search
results. Clicking a help topic title in the search results list will open the required topic. To go straight to
the help system's Search tab, click the Search... button in the Management Client's toolbar (see page
55).

Glossary Tab: What is a video encoder? What does PTZ mean? The Glossary tab provides a glossary
of common surveillance and network-related terms. Simply select a term to view a corresponding
definition in the small window below the list of terms.
Links in Help Topics
The actual content of each help topic is displayed in the right pane of the help window. Help topic texts may
contain various types of links, notably so-called expanding drop-down links.
Clicking an expanding drop-down link will display detailed information. The detailed information will be displayed
immediately below the link itself; the content on the page simply expands. Expanding drop-down links thus help
save space.
Tip: If you wish to quickly collapse all texts from expanding drop-down links in a help topic, simply click the title of
the topic on the help system's Contents tab.
Printing Help Topics
To print a help topic, navigate to the required topic and click the browser's Print button.
Tip: When printing a selected help topic, the topic will be printed as you see it on your screen. Therefore, if a topic
contains expanding drop-down links, click each required drop-down link to display the text in order for it to be
included in your printout. This allows you to create targeted printouts, containing exactly the amount of information
you require.
www.milestonesys.com
Page 20
Use the Built-in Help System
Milestone XProtect Corporate 4.1; Administrator's Manual
Browsers supported
The following browsers support the built-in help system (recent versions only):

Internet Explorer

Mozilla Firefox

Safari.
www.milestonesys.com
Page 21
Use the Built-in Help System
Installation and Removal
Installation and Removal
Installation Overview
If upgrading from a previous version of XProtect Corporate, make sure you read the upgrade information.
If you plan to run Milestone Federated Architecture, make sure to read about important prerequisites for running
Federated Architecture.
Your XProtect Corporate installation process begins with the installation of the management server software.

The Management Server is the center of your XProtect Corporate installation. It is typically installed on a
dedicated server. See Management Server Installation on page 23 for further information.
Once the management server is installed, you are able to install key components required by the management
server:

The Recording Server, which is used for recording video feeds, and for communicating with cameras and
other devices. The recording server is typically installed on one or more separate computers, rather than on
the management server itself. See Install System Components on page 27 for further information.

The Management Client, which is used for configuration and day-to-day management of the system. The
Management Client is typically installed on the system administrator's workstation or similar. See
Management Client Installation for further information.
Finally, you are able to install client software for access to the XProtect Corporate system:

The Smart Client is the feature-rich client used for access to live and recorded video and other features from
the surveillance system. The Smart Client software must be installed on users' computers. See Install and
Remove Smart Client on page 17 for more information.
Alternatively, the Remote Client lets you avoid installing access client software, as the Remote Client is run
straight from the XProtect Corporate system through a browser. It does, however, have significantly fewer
features than the Smart Client. See Remote Client on page18 for more information.
Tip: Video device drivers are small programs used for controlling/communicating with the cameras connected to a
recording server. You get the drivers automatically during the initial installation of your XProtect Corporate
system. However, new versions of the drivers are released from time to time; see Video Device Drivers on page
44.
Installing XProtect Corporate on Virtual Servers
As well on traditional servers, installation can also take place on virtualized servers. Thus, it is possible to run all
®
®
XProtect Corporate components on virtualized Windows servers, such as—for example—VMware and
®
Microsoft Hyper-V . Contact your IT department for more information.
Tip: Virtualization is often preferred to better utilize hardware resources. Normally, virtual servers running on the
hardware host server do not load the virtual server to a great extent, and often not at the same time. However,
XProtect Corporate Recording Server service records all cameras and streaming video. This puts high load on
CPU, memory, network, and storage system. Thus when run on a virtual server, the normal gain of virtualization
disappears to a large extent, since—in many cases—it will use all available resources.
If run in a virtual environment, it is important that the hardware host has the same amount of physical memory as
allocated for the virtual servers and that the virtual server running the recording server is allocated enough CPU
and memory—which it is not by default. Typically, the recording server needs 2-4 GB depending on configuration.
Another bottleneck is network adaptor allocation and hard disk performance. Consider allocating a physical
network adaptor on the host server of the virtual server running the recording server. This makes it easier to
ensure that the network adaptor is not overloaded with traffic to other virtual servers. If the network adaptor is
used for several virtual servers, the network traffic might result in the recording server not retrieving and recording
the configured amount of images.
www.milestonesys.com
Page 22
Installation and Removal
Installation and Removal
Install Management Server
If upgrading from a previous version of XProtect Corporate, make sure you read the upgrade information on
page 42.
If you plan to run Milestone Federated Architecture, make sure to read about important prerequisites for
running Federated Architecture on page 201.
Read the EULA on the Product License Sheet (enclosed with the software CD) before installing any part of
XProtect Corporate.
Your Milestone XProtect Corporate installation process begins with the installation of the Milestone XProtect
Corporate management server software. The management server is the center of your XProtect Corporate
installation.
Prerequisites

Windows Installer 4.5 - only on Windows Server 2003
Before installing Milestone XProtect Corporate, it is important that you install Windows Installer 4.5. You
can download the Windows Installer 4.5 from this link: http://www.microsoft.com/downloads.

SQL Server
The management server requires access to a relational database. Later in this installation process you
must choose between using an existing SQL Server on the network (Administrator rights on the SQL
Server are required) or setting up a SQL Server Express Edition (a lightweight, yet powerful, version of
a full SQL server) on the management server computer itself.
Whatever SQL solution you choose, make sure to have Microsoft .NET Framework 3.5 Service Pack 1
installed on the management server computer running the SQL Server Express Edition (even though
Microsoft .NET Framework 4.0 is already installed) or the separate server running the existing SQL
Server. See also System Requirements on page 10.
Which SQL Server type is right for our organization? The SQL Server Express Edition is easy to
install and prepare for use, and will often suffice for systems with less than 500 cameras. However, if
you plan to perform frequent/regular backups of your database, using an existing SQL Server on the
network is recommended (Administrator rights on the SQL Server are required). For large
installations, such as installations with 500 cameras or more, using an existing SQL Server on the
network is always recommended.

Windows Server 2003 Fix
If you use Windows Server 2003 it is recommended to install this supported fix for Windows Server
2003 before starting: http://support.microsoft.com/kb/925336.
Otherwise, the installation of your management server might fail due to Microsoft Windows Installer
process having insufficient contiguous virtual memory to verify that the .msi package or the .msp
package is correctly signed.
Installing
1.
Shut down any Milestone software running. If upgrading, it is highly recommended that you remove any
previous versions of the management server before upgrading. Note, however, that you may not want
to remove the management server database, as it contains your Milestone XProtect Corporate
configuration.
2.
Insert the Milestone XProtect Corporate software CD. If the Milestone XProtect Corporate Management
Server Installation window does not open automatically upon inserting the CD, run the following file
from the CD:
setup.exe
Tip: Alternatively, if you are installing a version downloaded from the internet, run the setup.exe file
from the location you have saved it to.
www.milestonesys.com
Page 23
Installation and Removal
Installation and Removal
3.
The Milestone XProtect Corporate Management
Server Installation window will open, listing the
steps involved in the installation:
4.
Complete the steps outlined in the Milestone
XProtect Corporate Management Server
Installation window.
Tip: Depending on what is already installed on
the computer which is going to act as
management server, you may not need to
complete all of the window's three steps. The step
that currently requires your attention will be
highlighted.
Tip: When the management server software is
installed, you are able to check the state of the management server by looking at the management
server icon in the management server computer's notification area. See Management Server Service
and Recording Server Service on page 231 for more information.
Step 1: Internet Information Services
Milestone XProtect Corporate Management Server Installation automatically detects if Internet Information
Services (IIS) is already installed. If this step is not available, it is simply because IIS is already installed.
Internet Information Services includes a range of administrative features for managing web servers and web
applications, and is required in order to run a
Milestone XProtect Corporate management
server.
If installing on a server running Windows
2008 Server, IIS is automatically installed
once you click the Internet Information
Services step (should the automatic
installation fail, see Installation
Troubleshooting on page 44).
1.
On Windows Server 2003, clicking the
Internet Information Services step
opens Windows' built-in Windows
Components wizard:
2.
In the wizard's Components list, select
Application Server.
3.
Click the Details... button, and select
Internet Information Services (IIS).
4.
Click the Details... button and verify
that all IIS subcomponents are selected.
Click OK to return to the Windows
Components wizard.
5.
In the Windows Components wizard, click
Next and follow the wizard.
Tip: It is a good idea to have your Windows
installation CD ready; it may be required
during the process.
When IIS is installed, you will be returned to
the Milestone XProtect Corporate
Management Server Installation window for
the next step of the installation.
www.milestonesys.com
Page 24
Installation and Removal
Installation and Removal
Step 2: XProtect Corporate Management Server Database
Before completing this step, click the View Microsoft SQL Server 2008 Express End-user License Agreement link
to read the license agreement for the software.
This step opens the Database Setup wizard, which will guide you through the process of preparing a database for
use with the management server.
In the Database Setup wizard you will get the choice of using an existing SQL Server on the network or setting up
a SQL Server Express Edition (a lightweight, yet powerful, version of a full SQL server) on the management
server computer itself.
Follow the wizard's steps by clicking the Next button.
IMPORTANT: We recommend that you install the database on a dedicated hard disk drive that is not used for
anything else but the database. Installing the database on its own drive will prevent low disk performance.
IMPORTANT: During the database preparation process, you will be asked whether you want to create a new
database, use an existing database, or overwrite an existing database. For a new installation, you would typically
select the default option Create new database. However, if you are installing the database as part of upgrading to
a newer version of Milestone XProtect Corporate, and you want to use your existing database, make sure you
select Use existing database.
When you have prepared the database, you will be returned to the XProtect Corporate Management Server
Installation window for the last step in the management server installation.
Step 3: XProtect Corporate Management Server
This step opens a wizard, which will guide you through the process of installing the management server software
itself.
Opening page in Management Server Setup wizard
Follow the wizard's steps by clicking the Next button.
Tip: The wizard will ask you to specify the location of your
temporary license (.lic) file. The system will verify your license
file before you are able to continue. Therefore, have your
license file ready.
On one of the wizard's steps, you will be asked to select
between two installation options:

Typical
If you select Typical installation, the wizard will install all
the management server components at their default
location and with other default settings. A Typical
installation is recommended for most users.
-or-

Custom
If you select Custom installation, you get the option to select where to install each individual Management
Server component. A Custom installation is recommended for advanced users.
Only relevant if selecting Custom installation:
On one of the wizard's steps you will be asked to select
an IIS (Internet Information Services) web site for the
management server service:
Select one of the listed web sites, and make sure the
selected web site is started, then click Next. If the
selected web site is not started, the Next button is
disabled.
Tip: You may find that only a single IIS web site— the
Default Web Site— is listed. In that case simply make
sure that the web site is started, then click Next.
Towards the end of the wizard, in the Service Log On
www.milestonesys.com
Page 25
Installation and Removal
Installation and Removal
Setup window, you will be asked to select a user account under which the
management server service will run:
You will be able to select either a:
o
predefined Network Service account (in which case the service will
run whenever the computer acting as management server is
running).
or -
o
particular user account (in which case the service will use the
specified user account to log in to the computer acting as
management server).
See Select a Predefined Network Service Account and Select a Particular
User Account in the following.
Tip: If the computer acting as management server is a member of a domain, you should either select
Network Service, or make sure that you specify a user account which belongs to the domain in question.
You install the XProtect service channel, XProtect event server and XProtect log server as part of the
management server installation. But if required you can just as well install these on another server in your
surveillance system:
o
The XProtect service channel enables automatic and transparent configuration communication
between servers and clients in your Milestone XProtect Corporate installation. See Service Channel
Installation on page 34.
o
The XProtect event server is used for handling alarms and maps. Maps provide a physical overview
of your surveillance system: Which cameras are placed where, and in what direction are they
pointing? As mentioned it does not necessarily have to be installed on the Management Server—in
fact, you can often achieve better performance by installing the event server on another server. See
Install Event Server and Log Server (Custom) on page 31.
o
The XProtect log server provides the necessary functionality for logging information from your
XProtect Corporate installation. See Install Event Server and Log Server (Custom) on page 31.
What's Next?
Upon installation of the management server software, the management server's built-in web page automatically
opens in a browser. The web page lets you install key components required by the management server, among
these:

One or more Recording Servers (for recording video feeds and for communicating with cameras and
other devices)

A Management Client (for configuration and day-to-day management of the system)
Even though the web page opens automatically on the management server computer, you will in most cases want
to install the key components on other computers than the management server itself. This is no problem since
installation takes place through the web page, which can easily be accessed from other computers. See Install
System Components on page 27for further information.
How to Select a Predefined Account “Network Service”
1.
Select This predefined account.
2.
Select Network Service.
3.
Click OK.
How to Select a Particular User Account
1.
Select This account.
www.milestonesys.com
Page 26
Installation and Removal
Installation and Removal
2.
Click the Browse... button. This will open the Select User window.
3.
In the Select User window, verify that the required domain is specified in the From this location field. If
not, click the Locations... button to browse for the required domain.
4.
In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you
have entered is recognized.
5.
Click OK.
6.
Specify the password for the user account in the Password field, and confirm the password in the
Confirm password field.
The password fields must not be empty; the password for the account must contain one or more
characters and/or digits.
7.
Click OK.
Install System Components
If upgrading from a previous version of XProtect Corporate, make sure you read the upgrade information on
page 42.
Installation of the following components is not covered in this section: XProtect event server and XProtect log
server (see page31), Management Server (see page 23) and XProtect service channel (see page 33).
Read the EULA on the Product License Sheet (enclosed with the software CD) before installing any part of
Milestone XProtect Corporate.

Learn more about recording servers on page 70.

Learn more about the Management Client 53.

Learn more about failover servers on page 222.
IMPORTANT: As a prerequisite make sure of the following. During the installation process you will be asked to
specify a user account under which the Failover Server service will run. For the failover solution to work, the
failover server has to use the same user account as the recording server. Furthermore, the user account you
specify must have access to your XProtect Corporate system with administrator rights. To verify this, do the
following:
a.
In the Management Client's Site Navigation pane (see page 56), expand Security and select Roles. In the
Overview pane's (see page 56) roles list, select the Administrators role.
b.
In the Properties pane (see page 56)'s role settings list, verify that the required user is listed.
c.
If the user is not listed, add the required user to the Administrators role by clicking the Add... button below
the role settings list. For more information, see Assign and Remove Users and Groups to/from Roles on
page 165.
Part I—Downloading the Installer
The following describes the removal process. The process is more or less similar for the component types
mentioned, so in the following replace the component with the XProtect Corporate recording server, the failover
server or the Management Client, depending on your needs.
1.
On the computer on which you will install the component, shut down any Milestone software running. If
upgrading, it is highly recommended that you remove any previous versions of the component before
upgrading (see page 40).
2.
With an Internet Explorer browser, connect to the XProtect Corporate management server at the following
address:
www.milestonesys.com
Page 27
Installation and Removal
Installation and Removal
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
This will open the management server's built-in web page. If not accessing the web page on the
management server itself, log in with an account which has administrator rights on the Management Server.
3.
The web page is available in a
number of different languages. In
this example, we assume that you
view the web page in English, and
that you want to install English
versions of the Milestone XProtect
Corporate components.
On the web page find the relevant
component's installer section, and
then click the English link under
the required recording server
version (often, only one version
will be available).
Depending on your security
settings, one or more Windows
security warnings may appear
after you click the link. If such
security warnings appear, accept security warnings by clicking Run or similar (exact button text depends on
your browser version).
Part II—Installing the Component
Select the relevant component for a description of the process (if required, repeat the process on other computers
where the component should be installed):
Recording Servers
This will open the Milestone XProtect Corporate Recording Server Setup wizard, which will guide you through the
installation.
1.
On the first step of the wizard, click Next.
2.
Select installation method:

Typical
The Typical option installs the XProtect Corporate recording server with default settings. A Typical
installation is recommended for most users.
a.
Specify recording server setup parameters, see Tell Me How to Specify Recording Server
Setup Parameters... later in this topic.
b.
Click Next.
- or -

Custom
The Custom option lets you select where to install
the XProtect Corporate recording server
components. A Custom installation is recommended
for advanced users.
a.
Select required installation folder, then click
Next.
www.milestonesys.com
Page 28
Installation and Removal
Installation and Removal
b.
When asked which type of server to install, click the Standard recording server... icon. This lets you
install a regular recording server.
c.
Specify recording server setup parameters.
Click Next.
d.
The wizard will ask you to select a user account under which the XProtect Corporate Recording
Server service will run.
You must select between:

a predefined system account
- or -

a particular user account (in which case the service will use the specified user account to
log in to the computer acting as recording server).
See Select a Predefined System Account... and Select a Particular User Account... in the
following.
Tip: If the computer acting as recording server is a member of a domain, select the
predefined account Local System or make sure you specify a user account which belongs to
the domain in question.
If using network drives, you should always specify a particular user account (which has
access to the network drives in question), as the Recording Server service will not be able
handle the network drives otherwise.
Click Next.
e.
In some cases it can be advantageous to install more than one instance of the recording server on
the same physical server (see Multiple Recording Server Instances on page 40). Specify the
required number of instances (default is 1), then click Next.
f.
Only relevant if installing more than one instance of the recording server on the same physical
server: For each instance, specify the IP address to use for the instance in question.
IMPORTANT: Note that the IP addresses you specify must be assigned to the physical server in
question. Furthermore, even though your organization will not use IPv6 addresses, make sure to
assign both IPv6 and IPv4 on the server as these are needed by the software (see page 239).
Tip: Provided enough IP addresses are assigned to the server, the fields will be pre-filled.
Click Next.
3. Click Install.
4. On the last step of the wizard, click Finish. The recording server is now installed. The recording server has no
user interface as such; it is accessed and managed through the Management Client.
Tip: When the recording server software is installed, you are able to check its state. See Management Server
Service and Recording Server Service on page 231 for more information.
Failover Servers
1. This will open the XProtect Corporate Recording Server
Setup wizard, which will guide you through the installation.
On the first step of the wizard, click Next.
2. Select installation method Custom.
3. Select required installation folder, and then click Next.
4. When asked which type of server to install, click the
Failover recording server for temporary... icon.
5. Specify failover server setup parameters, see Specify
Recording Server Setup Parameters... in the following.
www.milestonesys.com
Page 29
Installation and Removal
Installation and Removal
Click Next.
6. A failover server has two services:

A Failover Server service, which handles the
processes of taking over from the regular
recording server.

A Recording Server service, which enables the
failover server to act as a recording server while
the regular recording server is unavailable.
The wizard will ask you to select a particular user account
under which the services will run. Make your selection.
See Select a Particular User Account... later in this topic for
how to select.
For the failover solution to work, the user account you specify must have access to your XProtect Corporate
system with administrator rights. If the computer acting as failover server is a member of a domain, make
sure you specify a user account which belongs to the domain in question. If using network drives, always
specify a user account which has access to the network drives in question.
7. Click Install.
8. On the last step of the wizard, click Finish. The failover server is now installed. The failover server has no
user interface as such; it is accessed and managed through the Management Client.
Tip: When the failover server software is installed, you are able to check its state. See Management Server
Service and Recording Server Service on page 231 for more information.
Management Client
1. In the Select installer language drop down box, select language to use during the installation. In this example,
we assume that you prefer English.
2. Next to appear is the XProtect Corporate Management Client Setup wizard, which will guide you through the
installation process.
On the first step of the wizard, click Next.
3. Select required installation folder, then click Next.
4. Click Install to begin installation; wait while the required components are installed.
5. When ready, click Finish. If wanted, select Launch XProtect Corporate Management Client to launch the
Management Client right away.
Tip: For an introduction to the Management Client, see Management Client Overview on page 53.
How to Specify Recording Server Setup Parameters

Name: A name for the server in question. If required, you can later change the name through the XProtect
Corporate Management Client.

Milestone XProtect Corporate management server: The IP address (example: 123.123.123.123) or host
name (example: ourserver) of the management server to which the server in question should be connected. If
required, you can later change the management server IP address/host name as part of the basic
administration on the Recording or Failover Server service.

MediaDB: The path to the server in question's media database. The media database is the recording
server's default storage area, i.e. the default location in which recordings from connected cameras are stored
in individual camera databases. If required, you can later change the path, and/or add paths to more storage
area locations, from the XProtect Corporate Management Client.
www.milestonesys.com
Page 30
Installation and Removal
Installation and Removal
When should I choose a particular user account instead of a predefined? If using network drives you should
always specify a particular user account (with access to the network drives in question). Otherwise the service in
question is unable to handle the required network drives.
How to Select a Predefined System Account
1.
Select This predefined account.
2.
Select Local System, Local Service, or Network Service as applicable.
3.
Click OK.
How to Select a Particular User Account
1. Select This account.
2. Click the Browse... button. This will open the Select User window.
3. In the Select User window, verify that the required domain is specified in the From this location field. If not,
click the Locations... button to browse for the required domain.
4. In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you have
entered is recognized.
5. Click OK.
6. Specify the password for the user account in the Password field, and confirm the password in the Confirm
password field.
The password must contain one or more characters and/or digits.
7. Click OK.
Install Event Server and Log Server (Custom)
If upgrading from a previous version of XProtect Corporate, make sure you read the upgrade information.
Installation of the following components are not covered in this section: recording servers, failover servers,
Management Client, Management Server and XProtect service channel . See installation details for each.
Read the EULA on the Product License Sheet (enclosed with the software CD) before installing any part of
Milestone XProtect Corporate.
Learn more about the event server and the log server on page 7.
Normally, the Milestone XProtect event server and Milestone XProtect log server are both installed as part of the
Management Server installation (see page 23), when installed with the Typical option. The following describes
how to make a custom installation of the XProtect event server and/or the XProtect log server , when these are
not installed as part of the Typical management server installation.
The XProtect event server and the XProtect log server can be installed either on the management server or on
any other computer.
Make sure that user rights are set up correctly in the operating system. You can read about user rights in the
operating system on Microsoft's web site:
(http://technet.microsoft.com/en-us/library/cc794944(WS.10).aspx.
www.milestonesys.com
Page 31
Installation and Removal
Installation and Removal
Installing Event Server and Log Server
The following describes the installation process (custom Installation). The process is more or less similar for the
two server types, so in the following replace the server with XProtect event server or XProtect log server
depending on your needs.
1. On the computer on which you will install the server, shut down any Milestone software running. If
upgrading, it is highly recommended that you remove any previous versions of the server (see page 40)
before upgrading.
2. Download the relevant server's installer from the management server's built-in web page at the address
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server, and
[port] is the port number which IIS has been set up to use on the management server.
On the web page find the servers' installer section, and then click the English link. Note that
depending on your security settings, one or more Windows security warnings may appear after you
click the link. If such security warnings appear, accept security warnings by clicking Run or similar
(exact button text depends on your browser version).
3. Run the installation file, either directly or from the location you saved it to. Follow the on-screen
installation guide.
4. Verify/specify the required installation path and click Next.
5. Select the relevant server type:


6.
Event Server
a.
Specify the URL address of the XProtect Corporate management server (example:
http://123.123.123.123). If installing the server on the management server itself, simply specify
localhost and click Next.
b.
Select the database to be used and click Next.
c.
Select the web site on which you want to install and click Next.
Log Server
a.
Select the database to be used by the Log server and click Next.
b.
Select the web site on which you want to install and click Next.
c.
Specify the URL address of the XProtect Corporate management server (example:
http://123.123.123.123). If installing the server on the management server itself, simply specify
localhost and click Next.
Specify a user account under which the server's service will run. The specified user is automatically
granted administrator rights in XProtect Corporate, see Specify the Rights of a Role on page 171.
You must select between:

a predefined Network Service account (in which case the service will run whenever the
computer acting as management server is running).
-or -

a particular user account (in which case the service will use the specified user account to log in
to the computer acting as recording server).
See Select a Predefined Network Service Account... and Select a Particular User Account... in the
following.
www.milestonesys.com
Page 32
Installation and Removal
Installation and Removal
When should I choose a particular user account instead of a predefined? If using network drives
you should always specify a particular user account (with access to the network drives in question).
Otherwise the service in question is unable to handle the required network drives.
7.
Click Install. When installation is complete, click Finish.
When to Select a Predefined Network Service Account
1.
The Network Service account is selected by default.
2.
Click OK.
The Network Service account must be added as a Windows user on the relevant recording server computers
in your surveillance system in order to retrieve status information from these recording servers.
When to Select a Particular User Account
1.
Select This account.
2.
Click the Browse... button. This will open the Select User window.
3.
In the Select User window, verify that the required domain is specified in the From this location field. If
not, click the Locations... button to browse for the required domain.
4.
In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you
have entered is recognized.
5.
Click OK.
6.
Specify the password for the user account in the Password field, and confirm the password in the
Confirm password field.
The password must contain one or more characters and/or digits.
7.
Click OK.
Install Service Channel (Custom)
If upgrading from a previous version of XProtect Corporate, make sure you read the upgrade information on
page 42.
Read the EULA on the Product License Sheet (enclosed with the software CD) before installing any part of
XProtect Corporate.
The Milestone XProtect service channel is installed as part of the Management Server installation (see page 23),
when the management server is installed with the Typical option. The following describes how to make a custom
installation of the service channel, when the service channel is not installed as part of the management server
installation. This allows you to install the service channel on another server in your surveillance system, if
required.
Manually Installing the IIS
When you install the service channel on another computer, you must first manually install the IIS, using the
following procedure:
1.
On the computer you want to install the service channel on, select Server Manager from Windows' Start
menu.
www.milestonesys.com
Page 33
Installation and Removal
Installation and Removal
2.
In the left side of the Server Manager window, select Roles, then the Roles Summary.
3.
Now select Add Roles to start a wizard.
4.
In the wizard, click Next, select Web Server (IIS), and follow the wizard's steps.
5.
When you reach the wizard's Select Role Services step, you will see that some role services are
selected by default. However you should select some additional role services:

Under Security, select Basic Authentication and Windows authentication.

Under
Management
Tools, select IIS
Management
Console, expand
it, and select IIS 6
Metabase
Compatibility, IIS
6 WMI
Compatibility, IIS
6 Scripting Tools,
and IIS 6
Management
Console.
When ready, the
relevant part of the
Role services tree
should look like this:
6.
Complete the wizard
by following the
remaining steps.
Installing the Service Channel
1.
On the computer on which you will install the service channel, shut down any Milestone software
running. If upgrading, it is highly recommended that you remove any previous versions of the service
channel (see page 40) before upgrading.
2.
If you want to install the service channel elsewhere, download the service channel installer from the
management server's built-in web page at the address
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has
been set up to use on the management
server. On the web page find the Service
Channel Installer section, and then click the
English link. Note that depending on your
security settings, one or more Windows
security warnings may appear after you click
the link. If such security warnings appear,
accept security warnings by clicking Run or
similar (exact button text depends on your
browser version).
When installing the service channel, you must be
logged on to the computer with a user that has
administrator rights in XProtect Corporate for the
www.milestonesys.com
Page 34
Installation and Removal
Installation and Removal
installation to be successful.
When the Service Channel Setup wizard opens:
3.
Click Next on the wizard's opening page.
4.
Select installation method:

Typical
The Typical option installs the service channel with default settings. A Typical installation is
recommended for most users.
o
Choose Management Server; specify the URL address of the management server
(including the http:// prefix, example: http://123.123.123.123), or host name including
domain name of the Management Server computer, example:
http://myhost.mydomain.com, then click Next.
-or-

Custom
The Custom option lets you select where to install the service channel components. A Custom
installation is recommended for advanced users.
a.
Verify/specify the required installation path, and click Next.
b.
Verify/specify web site, and click Next.
c.
Choose Management Server; specify the URL address of the management server
(including the http:// prefix, example: http://123.123.123.123), or host name including
domain name of the Management Server computer, example:
http://myhost.mydomain.com, then click Next.
d.
Specify a user account under which the
service channel will run. The specified
user is automatically granted
administrator rights in XProtect
Corporate, see Specifying the Rights of a
Role on page 171.
You are able to select either a particular
user account or Network Service.
Tip: If the computer acting as
management server is a member of a
domain, you should either select Network
Service, or make sure that you specify a
user account which belongs to the
domain in question.
You must select between:
o
a predefined Network Service account.
- or -
o
a particular user account (in which case the service will use the
specified user account to log in to the computer acting as management
server).
See Select a Predefined Network Service Account... and Select a Particular User
Account... in the following.
e.
Click Next.
When should I choose a particular user account instead of a predefined? If using network
drives you should always specify a particular user account (with access to the network drives in
question). Otherwise the service in question is unable to handle the required network drives.
www.milestonesys.com
Page 35
Installation and Removal
Installation and Removal
5.
Click Install. When installation is complete, click Finish to exit wizard.
How to Select a Predefined Network Service Account
a.
Select This predefined account.
b.
Select Network Service account.
c.
Click OK.
How to Select a Particular User Account
a.
Select This account.
b.
Click the Browse... button. This will open the Select User window.
c.
In the Select User window, verify that the required domain is specified in the From this location field. If
not, click the Locations... button to browse for the required domain.
d.
In the Enter the object names to select box, type the required user name.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the name you
have entered is recognized.
e.
Click OK.
f.
Specify the password for the user account in the Password field, and confirm the password in the
Confirm password field.
The password must contain one or more characters and/or digits.
g.
Click OK.
Important Port Numbers
XProtect Corporate uses particular ports when communicating with other computers, cameras, etc.
What is a port? A port is a logical endpoint for data traffic. Networks use different ports for different types of data
traffic. Therefore it is sometimes, but not always, necessary to specify which port to use for particular data
communication. Most ports are used automatically based on the types of data included in the communication. On
TCP/IP networks, port numbers range from 0 to 65536, but only ports 0 to 1024 are reserved for particular
purposes. For example, port 80 is used for HTTP traffic which is used when viewing web pages.
When using XProtect Corporate, you must therefore make sure that certain ports are open for data traffic on your
network.
The port numbers can be changed. Different port numbers may therefore be used in your organization. See
Management and Recording Server Service Administration on page 231 for information about changing the
recording server-related port numbers.
Tip: Consult the administrator of your organization's firewall if in doubt about how to open ports for traffic.
List of Ports Used by XProtect Corporate

Port 20 and 21 (inbound and outbound): Used by recording servers to listen for FTP information;
some devices use FTP for sending event messages. FTP (File Transfer Protocol) is a standard for
exchanging files across networks.
www.milestonesys.com
Page 36
Installation and Removal
Installation and Removal

Port 25 (inbound and outbound): Used by recording servers to listen for SMTP information. Also,
some devices use SMTP (e-mail) for sending event messages and /or for sending images to the
surveillance system server via e-mail. SMTP (Simple Mail Transfer Protocol) is a standard for sending email messages between servers.

Port 80 (inbound and outbound): While not directly used by XProtect Corporate, but by management
servers, port 80 is typically used by the IIS (Internet Information Services) Default Web Site for running
the XProtect Corporate Management Server service.

Port 554 (inbound and outbound): Used by recording servers for RTSP traffic in connection with
H.264 video streaming.

Port 1024 and above (outbound only (except ports listed in the following)): Used by recording
servers for HTTP traffic between cameras and servers.

Port 1249 (inbound and outbound): Used for communication between event server and Management
Client.

Port 5210 (inbound and outbound): Used for communication between recording servers and failover
servers when databases are merged after a failover server has been running.

Port 5432 (inbound and outbound): Used by recording servers to listen for TCP information; some
devices use TCP for sending event messages.

Port 7563 (inbound and outbound): Used by recording servers and Smart Client for handling PTZ
camera control commands and for communicating.

Port 8080 (inbound and outbound): Used for internal system communication.

Port 8844 (inbound and outbound): Used for communication between failover servers.

Port 9000 (inbound and outbound): Used by management servers for communication between
XProtect Corporate and XProtect Transact.

Port 9993 (inbound and outbound): Used for communication between recording servers and
management servers.

Port 11000 (inbound and outbound): Used by failover servers for polling (i.e. regularly checking) the
state of recording servers.

Port 12345 (inbound and outbound): Used by management servers and Smart Client for
communicating between XProtect Corporate and Matrix recipients.

Port 22331 (inbound and outbound): Used for communication between event server and Smart Client.

Port 65101 (inbound and outbound): Used by recording servers for communication between
recording servers and drivers (internally, used for example when SMTP events are received).

Any other port numbers you may have selected to use. Examples: If you have changed the IIS
Default Web Site port from its default port number (80) to another port number, or if you have integrated
XProtect Enterprise servers into your XProtect Corporate solution, in which case a port must be
allocated for use by XProtect Enterprise's Image Server service.
Multiple Management Servers (Clustering)
The XProtect Corporate management server can be installed on multiple servers within a cluster of servers. This
ensures that XProtect Corporate has very little down-time: if a server in the cluster fails, another server in the
cluster will automatically take over the failed server's job running the XProtect Corporate management server. The
automatic process of switching over the XProtect Corporate server service to run on another server in the cluster
only takes a very short time (up to 30 seconds).
www.milestonesys.com
Page 37
Installation and Removal
Installation and Removal
Note that the allowed number of failovers is limited to two within a six hour period. If exceeded, Management
Server services are not automatically started by the clustering service. The number of allowed failovers can be
changed to better fit your needs. See Microsoft's homepage:
http://technet.microsoft.com/en-us/library/cc787861%28WS.10%29.aspx for details on how to do this.
Is clustering the same as federated architecture? No, clustering is not the same as federated architecture.
Clustering is a method to obtain failover support for a management server on a site. With clustering, it is only
possible to have one active management server per surveillance setup, but other management servers may be
set up to take over in case of failure. On the other hand, federated architecture is a method to combine multiple
independent corporate sites into one large setup, offering flexibility and unlimited possibilities.
Prerequisites for Installing XProtect Corporate in a Cluster

Two or more servers installed in a cluster.
Tip: You can find information about failover clusters on Microsoft's web site.
-Regarding clusters in Windows 2003, see Deploying Exchange Server 2003 in a Cluster.
(http://technet.microsoft.com/en-us/library/bb123612(EXCHG.65).aspx)
-Regarding clusters in Windows 2008, see Failover Clusters.
(http://technet.microsoft.com/en-us/library/cc732488(WS.10).aspx)

Either an external SQL database installed outside the server cluster or an internal SQL service within
the server cluster.

A Microsoft® Windows® Server 2003/2008 Enterprise or Data Center edition.
Installing XProtect Corporate in a Cluster
The section is based on Windows 2008. So, if you are using Windows 2003, descriptions and illustrations might
differ from what your see on your screen.
1.
Install the XProtect Corporate management server and all its subcomponents on the first server in the
cluster by following the procedures described in Install Management Server (see page 23).
The management server must be installed with a specific user and not as a Network Service. This
requires that you use the Custom install option, see Install Management Server, step 3, for details.
Furthermore, the specific user must have access to the shared network drive and preferably a nonexpiry
password.
The service channel and the IIS should both be installed normally with the exact same user, and not as
cluster services.
IMPORTANT: The event server must be installed outside the cluster.
2.
After you have installed the management server and the Management Client on the first server in the
cluster, open the Management Client, then from the Tools menu select Registered Services...
a.
In the Add/Remove Registered Services window, select the Log Service in the list, then
click Edit...
b.
In the Edit Registered Service
window, change the URL address
of the log service to the URL
address of the cluster.
c.
Repeat steps a and b for all services listed in the Add/Remove Registered Services
window.
d.
In the Add/Remove Registered Services window, click Network...
www.milestonesys.com
Page 38
Installation and Removal
Installation and Removal
e.
In the Network
Configuration
window, change the
URL address of the
server to the URL
address of the
cluster. (This step
only applies to the
first server in the
cluster.) Click OK.
3. Click Close in the Add/Remove Registered Services window, then exit the Management Client.
4. Stop the management server service (see page 231) and the Internet Information Service (IIS). You
can read about how to stop the IIS at Microsoft's homepage:
http://technet.microsoft.com/en-us/library/cc732317(WS.10).aspx.
5. Repeat steps 1-4 for all subsequent servers in the cluster, this time pointing to the existing SQL
database, but for the last server in the cluster you install the management server on, do not stop the
management server service.
The management server service must be configured as a generic service in the failover cluster in order to
take effect:
1.
On the last server you have installed the Management Server on, open Windows' Failover Cluster
Management, found under Administrative Tools in the Start menu.
2.
In the Failover Cluster Management window, expand your cluster, right-click Services and
Applications, then select Configure a Service or Application...
3.
On the first page of the High Availability
wizard click Next, then on the second page
of the wizard select Generic Service in the
list, and click Next.
4.
Do not specify anything on the third page
of the wizard, click Next.
5.
Select the Milestone XProtect Corporate
management server service from the list,
then click Next.
6.
Specify the name (host name of the
cluster), that clients will use when
accessing the service, then click Next.
7.
No storage is required for the service, click Next.
8.
No registry settings should be replicated, click Next.
9.
Verify that the cluster service is configured according to your needs, then click Next.
10. The XProtect Corporate management server has now been configured as a generic service in the
failover cluster. Click Finish to exit the wizard.
Upgrading XProtect Corporate in a Cluster
Prerequisite
Make sure to have a backup of the database in question before updating the cluster.
www.milestonesys.com
Page 39
Installation and Removal
Installation and Removal
How to Update
1.
Stop Management Server services (see page 231) on all management servers in the cluster.
2.
Uninstall the management server on all servers in the cluster. See Remove System Components on page 40.
3.
Use the procedure for installing multiple management servers in a cluster as described earlier in Installing
XProtect Corporate in a Cluster.
IMPORTANT: When installing, make sure to reuse the existing SQL configuration database (which will
automatically be upgraded from the old existing database version to the new one).
Multiple Recording Server Instances
32-bit programs, such as the Recording Server service, can use up to 2 GB of virtual memory. On 32-bit operating
systems, this is fine: the operating system kernel reserves 2 GB for itself, and each individual running process is
allowed to address up to another 2 GB.
However, if you have a 64-bit operating system and plenty of virtual memory, say 16 GB of RAM, on a server
running a single Recording Server service, you will be under-utilizing the server's resources, since the single 32bit service will still only be able to use up to 4 GB of RAM.
To facilitate better use of virtual memory on servers with 64-bit operating systems and large amounts of RAM, it is
therefore possible to install more than one instance of the Recording Server service on the same server.
During the recording server installation (see page 28), you simply select the required number of instances. By
installing several instances of the Recording Server service on a single server, you will be able to make better use
of the server's virtual memory—provided that the server runs a 64-bit operating system and that the server is rich
on RAM.
Example: On a server with 16 GB of RAM, you would, in theory, provided that all the hardware on the
server has the necessary capacity, be able to run up to three instances of the Recording Server service.
Of the 16 GB, two GB would be used by the operating system itself, leaving 14 GB for three instances of
the Recording Server service, each instance using 4 GB, a total of 12 GB.
Note, however, that other processes may also run on the server, in practice leaving less RAM for Recording
Server service instances. The number of Recording Server service instances you will be able to run in practice
may therefore be lower than the theoretical maximum.
A maximum of 99 recording server instances is allowed on a single server.
Using multiple recording server instances does not require additional licenses.
When using multiple instances of recording servers, you will note a few differences in the Management Client and
when managing basic properties of the Recording Server service on the server itself:

In the Management Client, each recording server instance will be displayed separately, allowing you to
configure each instance separately
 When managing the Recording Server service (see page 231) by right-clicking its icon in the notification
area on the server itself, you can:
o
Stop and start each instance individually
o
View status messages for each instance individually, grouped on tabs
Remove System Components
If you are not an XProtect Corporate system administrator, do not attempt to remove the management software.
www.milestonesys.com
Page 40
Installation and Removal
Installation and Removal
The following procedure describes standard system component removal in recent Windows versions; the
procedure may be slightly different in older Windows versions:
1.
2.
In Windows' Start menu, select Control Panel, and then...

If using Category view, find the Programs category, and click Uninstall a program.

If using Small icons or Large icons view, select Programs and Features.
In the list of currently installed programs, right-click the required program or service, select Uninstall, and
follow the removal instructions.
Removing Management Server
XProtect Corporate Management Servers is most likely installed on a dedicated server.
To remove, follow the removal procedure described in the beginning.
Removing Download Manager, Event Server and Log Server
The Download Manager, XProtect event server and XProtect log server which are all installed on the
management server, are removed separately from the management server software.
To remove, follow the removal procedure described in the beginning.
Removing XProtect Corporate Management Client or XProtect
service channel
XProtect Corporate Management Client and XProtect service channel are all removed at the computer on
which the program or service is installed.
To remove, follow the removal procedure described in the beginning.
Removing XProtect Corporate Recording Server
To remove an XProtect Corporate recording server, use the following procedure on the computer on which the
recording server is installed:
What happens to the recording server's recordings? During the removal process, you will be asked whether
you want to keep the recording server's recordings.
1.
Stop the recording server service by right-clicking the recording server
icon in the computer's notification area (also known as the system tray),
then selecting Stop Recording Server Service.
Example: recording server notification area icon
2.
Follow the removal procedure described in the beginning. Right-click the XProtect Corporate Recording
Server in step 2 of the process.
Removing Non-Required Components from Management Server
Upon installation, your management server by default contains installation files for a number of components, such
as additional language versions of the Smart Client. The installation files lets you install the components on the
management server, and make them available to your organization's users through the Download Manager.
You can remove installation files for non-required features from the Management Server. This can help you save
disk space on the server if you know that your organization is not going to use certain features, for example nonrelevant language versions.
www.milestonesys.com
Page 41
Installation and Removal
Installation and Removal
1.
Open the Installers folder located in the management server software installation folder, typically at
C:\Program Files\Milestone\XProtect Corporate Management Server\Installers.
2.
You may—depending on the type of
component—need to select the
required language sub-folder. Then
you delete the unwanted installation
(.exe) file. In the following example,
we are about to delete a French
Smart Client language pack installation file from the management server:
Upgrade from Previous Version
This information is only relevant if you are upgrading a previous installation of XProtect Corporate.
IMPORTANT: XProtect Corporate no longer supports Microsoft® Windows® XP. See System Requirements on
page 10.
The process of upgrading XProtect Corporate involves removing all of its components except the Database
Server. The Database Server is one of the management server's components, it contains the entire system
configuration (recording server configurations, camera configurations, rules, etc.). As long as you do not remove
the Database Server, you will not need to reconfigure your surveillance system configuration in any way (although
you may of course want to configure some of the new features in the new version).
Backward compatibility with recording servers from XProtect Corporate versions older than 3.0 is limited. You can
still access recordings on such older recording servers; but in order for you to be able to change their
configuration, they must be of version 3.0 or later. It is thus highly recommended that you upgrade all recording
servers in your XProtect Corporate system.
When doing an update which includes updating your recording servers, you automatically update your Video
Device Drivers as well. In this case, after restarting your system, it might take several minutes for your hardware
devices to make contact with the new Video Device Drivers, so have patience. This is due to several internal
checks being performed on the newly installed drivers.
Prerequisites

Have your temporary license (.lic) file ready. The license file will change when your SLC changes, so
you are likely to have received a new license file when purchasing the new version. When you install the
management server installation, the wizard will ask you to specify the location of your license (.lic) file,
and the system will verify both before you will be able to continue.
If you do not have your license file, contact your Milestone vendor.

Have your new Milestone XProtect Corporate version ready. If you have not purchased the software
on a CD/DVD, you can download it from www.milestonesys.com. Note that although you can download
any version, you will only be able to install a version for which your license file is valid.

The management server stores your XProtect Corporate system's configuration in a database. The
system configuration database can be stored in two different ways: 1) In a SQL Server Express Edition
database on the management server itself, or 2) in a database on an existing SQL Server on your
network. If using 2), Administrator rights on the SQL Server are required whenever you need to
create, move or upgrade the management server's system configuration database on the SQL Server.
Once you are done creating, moving or updating, being database owner of the management server's
system configuration database on the SQL Server will suffice.
Upgrading the Management Server
The management server has several components. In the following, we will walk through the process of removing
the old components—except the Database Server—and installing the new ones:
www.milestonesys.com
Page 42
Installation and Removal
Installation and Removal
1.
First remove the management server itself. See Remove System Components on page 40.
2.
Next, remove the XProtect Corporate Windows components.
3.
If the XProtect Corporate Management Client (in earlier versions called the Manager) is installed on the
management server itself, remove the Management Client/Manager too. See Remove System
Components on page 40.
4.
If the XProtect Corporate Management Client (in earlier versions called the Manager) is installed on the
management server itself, remove the Management Client/Manager too. See Remove System
Components on page 40.
5.
Run the installation file for the new version of XProtect Corporate. After a short while, the installation
window will open. Out of the three installation steps for the management server, you will be asked to
address step 3 (XProtect Corporate management server).
6.
Click the installation window's step 3, and complete the XProtect Corporate management server
installation. During this process you will be asked to specify the path to your license (.lic) file.
7.
When the management server is installed, the management server's web page will appear in a browser.
If you want to install the Management Client software (in earlier versions called the Manager) on the
management server itself, you can do if from the management server's web page.
Upgrading Recording Servers
Once the new management server is installed, you can remove the old recording server version, and install the
new one:
What happens to the recording server's recordings? During the removal process, you will be asked whether
you want to keep the recording server's recordings.
1.
See Remove System Components on page 40 for how to remove a recording server.
2.
When the recording server has been removed, open a browser and connect to the management server's
web page at the following address:
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
If not accessing the web page on the management server itself, log in with an account which
has administrator rights on the management server.
3.
From the web page, install the new version of the recording server software.
4.
Repeat for each recording server on your XProtect Corporate system.
When updating your recording servers, you automatically update your Video Device Drivers as well. After
restarting your recording servers, it might take several minutes for your hardware devices to make contact with
the new Video Device Drivers, so have patience. This is due to several internal checks being performed on the
newly installed drivers.
Upgrading a Manager/Management Client
If the Management Client (in earlier versions called the Manager) is installed on separate computers, such as the
surveillance system administrator's workstation or similar, you should now remove the old version and install the
new one:
1.
See Remove System Components on page 40 for details on removing a Management Client.
2.
When the Management Client has been removed, open a browser and connect to the management
server's web page at the following address:
www.milestonesys.com
Page 43
Installation and Removal
Installation and Removal
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
If not accessing the web page on the management server itself, log in with an account which has
administrator rights on the management server.
3.
From the web page, install the new version of the Management Client.
Upgrading the Smart Client
Smart Client users should now remove their old Smart Client versions and install the new one:
1.
See Smart Client on page 16 for how to remove a Smart Client.
2.
When the Smart Client has been removed, open a browser and connect to the management server's
web page at the following address:
http://[management server address]:[port]/installation/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
3.
From the web page, install the new version of the Smart Client.
Upgrading Video Device Drivers
Before upgrading Video Device Drivers, you must remove old Video Device Drives.
For information on how to remove/upgrade/install Video Device Drivers, see Manage and Remove Video Device
Drivers on page 44.
Installation Troubleshooting
The following issues may occasionally occur during or upon installation of the XProtect Corporate management
server or recording servers. For each issue, one or more solutions are available.
Issue: Automatic IIS Installation for Management Server or Event
Server Fails
If installing the management server or the Event server (custom installation) (see page 31) on a server running
Windows 2008 Server, Internet Information Services (IIS) is under normal circumstances automatically installed.

For the management server, this happens when you click the Internet Information Services step in the
XProtect Corporate Management Server Installation window.

For the Event server, this is only a problem if the Event server is installed on a different server than the
management server.
If the automatic installation fails, you can install IIS manually.

Solution: Install IIS Manually
1.
If automatic IIS installation fails, you will see an error message asking you to install IIS
manually. In the error message box, click the Install IIS Manually button.
www.milestonesys.com
Page 44
Installation and Removal
Installation and Removal
2.
You will now see the Server Manager window. In the left side of the window, select Roles, then
the Roles Summary.
3.
Now select Add Roles to start a wizard.
4.
In the wizard, click Next, select Web Server (IIS), and follow the wizard's steps.
5.
When you reach the wizard's Select Role Services step, you will see that some role services
are selected by default. However, you should select some additional role services:
o
Under Security, select Basic Authentication and Windows authentication.
o
Under Management Tools, select IIS 6 Management Console, expand it, and select IIS
6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, and IIS 6
Management Console.
When ready, the relevant part of the Role services tree should look like this:
6.
Complete the wizard by following the remaining steps.
Issue: Recording Server Startup Fails due to Port Conflict
This is an issue if either the Simple Mail Transfer Protocol (SMTP) Service or an existing installation of XProtect
Enterprise is running.
Both use port 25. If port 25 is already in use, it may not be possible to start the Milestone XProtect Corporate
Recording Server service. It is important that port number 25 is available for the recording server's SMTP service
since many cameras are only capable of communicating via this port.
SMTP Service: Verification and Solutions
To verify whether SMTP Service is installed, do the following:
1.
From Windows' Start menu, select Control Panel.
2.
In the Control Panel, double-click Add or Remove Programs.
3.
In the left side of the Add or Remove Programs window, click Add/Remove Windows Components.
www.milestonesys.com
Page 45
Installation and Removal
Installation and Removal
4.
In the Windows Components wizard, select the Internet Information Services (IIS) item, and click the
Details… button.
5.
In the Internet Information Services (IIS) window, verify whether the SMTP Service check box is
selected. If it is, SMTP Service is installed.
If SMTP Service is installed, select one of the following solutions:
o
Solution 1: Disable SMTP Service, or set it to manual startup
This solution lets you start the recording server without having to stop the SMTP Service every
time:
1.
From Windows' Start menu, select Control Panel.
2.
In the Control Panel, double-click Administrative Tools.
3.
In the Administrative Tools window, double-click Services.
4.
In the Services window, double-click the Simple Mail Transfer Protocol (SMTP) item.
5.
In the Simple Mail Transfer Protocol (SMTP) Properties window, click Stop, and then set
Startup type to either Manual or Disabled.
Tip: When set to Manual, the SMTP Service can be started manually from the Services
window, or from a command prompt using the command “ net start SMTPSVC”.
6.
o
Click OK.
Solution 2: Remove SMTP Service
Note that removing the SMTP Service may affect other applications using the SMTP service.
1.
From Windows' Start menu, select Control Panel.
2.
In the Control Panel, double-click Add or Remove Programs.
3.
In the left side of the Add or Remove Programs window, click Add/Remove Windows
Components.
4.
In the Windows Components wizard, select the Internet Information Services (IIS) item,
and click the Details… button.
5.
In the Internet Information Services (IIS) window, clear the SMTP Service check box.
6.
Click OK, Next, and Finish.
XProtect Enterprise: Verification and Solutions
To verify whether XProtect Enterprise is installed, do the following:
1.
From Windows' Start menu, select Control Panel.
2.
In the Control Panel, double-click Add or Remove Programs.
3.
In the Add or Remove Programs window, verify whether XProtect Enterprise appears in the list. If it
does, XProtect Enterprise is installed.
www.milestonesys.com
Page 46
Installation and Removal
Installation and Removal
If XProtect Enterprise is installed, select one of the following solutions:
o
o
Solution 1: Remove XProtect Enterprise
1.
From Windows' Start menu, select Control Panel.
2.
In the Control Panel, double-click Add or Remove Programs.
3.
In the Add or Remove Programs window, select XProtect Enterprise, click the
Change/Remove button, and then OK.
Solution 2: Set XProtect Enterprise services to manual startup
This solution lets you start the recording server without having to stop the XProtect Enterprise
services every time:
1.
From Windows' Start menu, select Control Panel.
2.
In the Control Panel, double-click Administrative Tools.
3.
In the Administrative Tools window, double-click Services.
4.
In the Services window, repeat steps a-c in the following for these items:
- Milestone ImageImportService
- Milestone ImageServer
- Milestone LogCheckService
- Milestone Recording Server
a.
Double-click the item.
b.
In the <item> Properties window, click Stop, and then set Startup type to Manual.
c.
Click Close to close the window.
Tip: With the startup type Manual, you can start and stop the XProtect Enterprise
services from a command file:
To start the XProtect Enterprise services from a command file, create a file named
e.g. startx.cmd with the following content:
net start "Milestone ImageImportService"
net start "Milestone ImageServer"
net start "Milestone LogCheckService"
net start "RecordingServer"
To stop the XProtect Enterprise services from a command file create a file named
e.g. stopx.cmd with the following content:
net stop "Milestone ImageImportService"
net stop "Milestone ImageServer"
net stop "Milestone LogCheckService"
net stop "RecordingServer"
Issue: Changes to SQL Server Location Prevents Database Access
This is an issue if using an MS SQL Server database as the XProtect Corporate management server database: If
the location of the SQL Server is changed, for example by changing the host name of the computer running the
SQL Server, access to the database will be lost.
www.milestonesys.com
Page 47
Installation and Removal
Installation and Removal

Solution: Run Management Server Database Installation Step Again
See management server Installation on page 23. When running the database installation, you will—
during the database preparation process— be asked whether you want to create a new database, use
an existing database, or overwrite an existing database: Pointing to the new location of the SQL Server,
select to use an existing database. This will update the SQL connection string used by the management
server, and it will again be possible to access the database.
Issue: Installation Fails Due to Insufficient Continuous Virtual
Memory
The following is only relevant if you use Windows Server 2003.
If you try to install a large Windows Installer package or patch package in Windows Server 2003, this problem
might occur if the Windows Installer process has insufficient continuous virtual memory to verify that the .msi
package or the .msp package is correctly signed.

Solution: A supported fix is available for Windows Server 2003.
See http://support.microsoft.com/kb/925336.
Issue: Multi-domain Environments with One-way Trusts not
Working
See Multi-domain Environments, One-way Trust on page 241.
Use Download Manager
The management server has a built-in web page. The web page enables
administrators and end users to download and install required surveillance
system components from any location, locally or remotely.
The web page is capable of displaying two sets of content:

One targeted at system administrators, enabling them to
download and install key XProtect Corporate components,
such as recording servers (see page 28) and the
Management Client (see page 30). This is the content you see during the XProtect Corporate
installation process.

One targeted at end users, providing them with access to client applications, such as the Smart
Client and Remote Client, as well as various drivers, plugins, language packs, etc.
The example to the right shows the web page displaying content targeted at system administrators. The web
page automatically has some content; this is why you can use it straight away during the XProtect Corporate
installation process. However, as a system administrator, you can customize what should be displayed on the
web page, for example if particular language versions of the Smart Client are required in your organization. For
this purpose you use the Download Manager.
Working with Download Manager
Access Download Manager
You access the Download Manager on the server running the Management Server software: In Windows' Start
menu, select All Programs > Download Manager > Download Manager.
www.milestonesys.com
Page 48
Installation and Removal
Installation and Removal
Make New Components Available
Making new components—including new language versions—available to your organization's users involves two
procedures: First you install the required components on the management server. You then use the Download
Manager to fine-tune which components
should be available in the various language
versions of the web page.
Installing New Components on
Management Server
If the Download Manager is open, close it
before installing new components on the
management server.
Installation files for additional components, for example Smart Client language versions, language packs, etc., are
by default available on your management server in a folder called Installers. The Installers folder is located in the
management server software installation folder, typically at C:\Program Files\Milestone\XProtect Corporate
Management Server\Installers.
To install a component from the Installers folder you may—depending on the type of component—need to select
the required language sub-folder. Then you double-click the required installation (.exe) file. In the following
example, we are about to install a French Smart Client language pack on the management server:
Tip: You can find more language versions of the Smart Client installer—and additional language packs—on the
XProtect Corporate software DVD as well as on www.milestonesys.com.
When a new component has been installed on the management server, you will see a confirmation dialog. If
required, you can open the Download Manager from the dialog:
Making New Components Available through the Download
Manager
When you have installed new components—such as Smart Client
language versions, language packs, etc.—they will by default be
selected in the Download Manager, and thus immediately be
available to users via the web page.
You can always show or hide features on the web page by
selecting or clearing check boxes in
the Download Manager's tree
structure.
In the following example, we have specified that users who select the Spanishlanguage version of the Default web page version should have access to a Spanish
version of the Smart Client, English and Spanish versions of the Remote Client, and a
French language pack for the Smart Client:
Tip: You can change the sequence in which components are displayed on the web
page: In the Download manager's tree structure, simply drag component items and
drop them at the required position.
Move Components between Web Page Versions
You are able to move components between the two versions of the web page, i.e. between the one targeted at
system administrators and the one targeted at end users.
To move a component, simply right-click it, and select the web page version you want to move the component to.
In the following example we want to move the
Remote Client, which is by default displayed on
the end-user (Default ) version of the web
page, to the administrator version ( Admin ):
Hide and Remove Components
You have three options:
www.milestonesys.com
Page 49
Installation and Removal
Installation and Removal

You can hide components from the web page by clearing check boxes in the Download Manager's tree
structure. In that case, the components will still be installed on the management server, and by selecting
check boxes in the Download Manager's tree structure you can quickly make the components available
again.

You can remove components which have previously been made available through the Download
Manager. This will remove the installation of the components on the management server. The
components will disappear from the Download Manager, but installation files for the components will be
kept in the Managements Server's Installers folder, so you can re-install them later if required.

1.
In the Download Manager, click the Remove features... button.
2.
In the Remove Features window, select the features you
want to remove. In the following example, we have
selected to remove a Spanish Smart Client installer and
a Spanish Remote Client
3.
Click OK. You will be asked to confirm that you want to
remove the selected features. If you are sure, click the
Yes button.
You can remove installation files for non-required features
from the Management Server. This can help you save disk space
on the server if you know that your organization is not going to
use certain features—typically non-relevant language versions. See Remove System Components on
page 40 for more information.
More Info about Download Manager
Download Manager Is Not User Rights Management Tool
The Download Manager lets you control which components users are able to download and install (or—in the
case of the Remote Client —run straight from the web page). However, it is important to know that the Download
Manager cannot be used for managing users' rights to use the components. Such rights are determined by roles
(see page 164); you define roles in the Management Client.
Default Configuration of Download Manager and Web Page
The Download Manager has a default configuration. This ensures that your organization's users can access
standard features without you having to set up anything.

The default configuration provides administrators with access to downloading recording servers (see
page 28), the Management Client (see page 30), the Event Server service (see page 32), as well as
video device drivers (see page 44). This content is displayed when the web page is automatically loaded
at the end of the management server installation as well as when the web page is accessed by entering
the URL.
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server. If not
accessing the web page on the management server itself, log in with an account which has
administrator rights on the management server.

The default configuration provides end users with access to downloading a Smart Client as well as to
running a Remote Client (which does not need to be downloaded). Both applications will by default be
available in a language version matching the language version of your XProtect Corporate installation.
This content is displayed when the web page is accessed by entering the URL.
http://[management server address]:[port]/installation/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
www.milestonesys.com
Page 50
Installation and Removal
Installation and Removal
The Download Manager's configuration is represented in a tree structure. Example: With an English
version of XProtect Corporate, the Download Manager's default configuration would be represented in a
tree structure like this:
Download Manager's Tree
Structure Explained
The first level of the tree structure (• in
the example illustration) simply
indicates that you are working with
XProtect Corporate.
The second level (••) refers to the two
targeted versions of the web page.
Default refers to the web page version
viewed by end users. Admin refers to
the web page version viewed by
surveillance system administrators.
The third level (•••) refers to the
languages in which the web page is
available. In the example, the
welcome page is available in a dozen
languages (English, Arabic, Chinese,
Czech, Danish, etc.).
The fourth level (••••) refers to the
components which are—or can be
made—available to users. In the
example, these components include
the Smart Client and Remote Client
for end users. For system
administrators, the components
include recording server and
Management Client.
The fifth level (•••••) refers to particular
versions of each component, which
are—or can be made—available to
users. Example: version 3.5d of the
Remote Client.
The sixth level (••••••) refers to the
language versions of the components which are—or can be made—available to users.
In the example, XProtect Corporate has been installed in an English-language version. If we expand one of the
other languages in the tree structure's third level, for example Arabic, we will see that users who select the Arabic
version of the web page will initially also only have access to English versions of the Smart Client and, potentially,
the Remote Client.
The fact that only standard components are initially available—and only in the same language version as the
surveillance system itself—helps reduce installation time and save space on the server. There is no need to have
a component or language version available on the server if nobody is going to use it.
You can, however, make more components and/or languages available as required. See Make New Components
Available earlier. Likewise, you can hide or remove unwanted components and/or languages; see Hide and
Remove Components earlier.
Examples of Components You Can Control Through the Download Manager

Recording servers (including failover servers; failover servers are initially downloaded and installed as
recording servers, during the installation process you specify that you want a failover server)

Management Client
www.milestonesys.com
Page 51
Installation and Removal
Installation and Removal

Video device drivers (for use on recording servers)

Smart Client

Remote Client

Language packs for Smart Clients (allowing users to add additional languages to their Smart Clients)

Event Server the service used in connection with map functionality (see page 229) in Smart Clients

Various plugins (downloading such plugins can be relevant if your organization uses add-on products
(such as video analytics or transaction management solutions) with XProtect Corporate.

More options may be available in your organization.
Virus Scanning Information
If you are using virus scanning software on the management server, it is likely that the virus scanning will use a
considerable amount of system resources on scanning data from the Download Manager. If allowed in your
organization, disable virus scanning on the management server. For more information see Virus Scanning
Information on page 235.
www.milestonesys.com
Page 52
Installation and Removal
Management Client
Management Client
Management Client Overview
The Management Client is the feature-rich administration client used for configuration and day-to-day
administration of your XProtect Corporate system. The Management Client software is typically installed (see
page 30) on the surveillance system administrator's workstation or similar.
Management Client's Elements
The Management Client window is divided into a number of panes. The number of panes will change depending
on your task:
The following illustrations outline the Management Client window's default layout; the window layout can be
customized (see page 61), and may therefore be different on your computer.

When working with recording servers and devices (cameras, inputs, outputs), the Management Client
window contains a menu bar and four panes:

When working with rules, time and notification profiles, users, roles, etc., the Management Client window
typically contains a menu bar and three panes:

When viewing logs, the Management Client window typically contains only the menu bar, the Site
Navigation and Federated Sites Hierarchy Pane and an overview area (marked in gray):
www.milestonesys.com
Page 53
Management Client
Management Client
Site Navigation Pane and Federated Site Hierarchy Pane
This area of the Management Client consists of two different panes/tab's, the Site Navigation pane and the
Federated Site Hierarchy pane. Per default, the Site Navigation pane is located on top.

Site Navigation pane
The main navigation element in the Management Client. Name, settings and configurations of the site
you are logged in (see page 201) to is reflected here (site-name is visible at the top of the pane). The
Management Client's features are grouped into the following categories:
o
Basics: General information, for example about licenses in your XProtect Corporate system
o
Servers: Management of recording servers and failover servers (spare recording servers)
connected to your XProtect Corporate system
o
Devices: Management of cameras, microphones, speakers, inputs, and outputs
o
Client: Management of view groups, Smart Client profiles and Matrix recipients
o
Rules and Events: Management of rules, time profiles, notification profiles, and events
o
Security: Management of roles, users, and groups.
o
System Dashboard: Overview of recording servers' databases and archives
o
Server Logs: Access to the various logs of your XProtect Corporate system
o
Alarms: Management of alarm definitions, alarm's time profiles and alarm-related settings and
logs.
Tip: Right-clicking items in the Site Navigation pane gives quick access to management features.

Federated Site Hierarchy pane
Navigation element dedicated to displaying Milestone Federated Architecture sites and their parent/child
links.
The parent server you are logged in to, a.k.a your home-site, will always be at top, and adopting its point
of view, you can view all its linked children and downwards in the parent/child hierarchy.
What if I only have one server and don't run Milestone Federated Architecture? Your user interface
looks the same, but you will only see the one server in your setup.
www.milestonesys.com
Page 54
Management Client
Management Client
Menu Bar
The Management Client's menu bar features the following menus (see page 60):
File Menu, Edit Menu, View Menu, Action Menu, Tools Menu and Help Menu.
Toolbar
The Management Client's toolbar features the following options:
Save: Save changes to your settings.
Undo: Undo your latest change.
Help...: Access a help topic relevant to your task.
Contents...: Access the help system's table of contents.
Search...: Access the help system's search feature.
Tip: Read more about the Management Client's built-in help system in Use the Built-in Help System on page 20.
Memory Indicator
The memory indicator located in the lower left corner of the Management Client
states how much memory is available for working with the Management Client.
When you expand items in the Site Navigation pane (see page 56) the Management Client uses memory to treat
data stored in the individual items. Expanded items keep processing even when you expand other items in the
Site Navigation pane, thus letting you access already-expanded items faster.
When available memory drops to 300 MB the memory indicator numbers turn red:
When the memory indicator drops to 0 MB, meaning there is no more memory available for the Management
Client, you cannot expand any more items and you will see the following dialog.
To free up memory, refresh the Management
Client: Click OK to exit the dialog, then press
F5 on your keyboard or select Refresh from
the Action menu.
www.milestonesys.com
Page 55
Management Client
Management Client
Panes Overview
The Management Client window may contain up to four panes:
1.
Site Navigation Pane
and Federated Sites
Hierarchy Pane
2.
Overview Pane
3.
Properties Pane
4.
Preview Pane
The illustration outlines the
Management Client window's
default layout; the window layout
can be customized (see page 61),
and may therefore be different on
your computer.
Menu and Tool Bars
Provide quick access to oftenused features.
Navigation Pane
Your main navigation element in the Management Client. Name, settings and configurations of the site you are
logged into (see page 201) are reflected here (site-name is visible at the top of the pane). The Management
Client's features are grouped into the following categories:

Basics: General information, for example about licenses in your XProtect Corporate system

Servers: Management of recording servers and failover servers (spare recording servers) connected to
your XProtect Corporate system

Devices: Management of cameras, microphones, speakers, input, and output

Client: Management of view groups, Smart Client profiles and Matrix recipients

Rules and Events: Management of rules, time profiles, notification profiles, and events

Security: Management of users, groups, and roles

System Dashboard: Overview of recording servers' databases and archives

Server Logs: Access to the various logs of your XProtect Corporate system

Alarms: Management of alarm definitions, alarm's time profiles and alarm-related settings and logs.
Tip: Right-clicking items in the Site Navigation pane gives you quick access to management features.
Federated Site Hierarchy Pane
Your navigation element dedicated to displaying Milestone Federated Architecture sites (see page 201) and their
parent/child links.
The parent server you are logged in to, a.k.a your home site, will always be at top, and adopting its point of view,
you can view all its linked children and downwards in the parent/child hierarchy.
Right-clicking in the Federated Site Hierarchy Pane is not selecting! Since you must be able to delete a site
without being connected to it, right-clicking a site does not select it, but offers a context menu.
www.milestonesys.com
Page 56
Management Client
Management Client
Overview Pane
Provides an overview of the item you have selected in the navigation pane, typically in the form of a detailed list.
Selecting a particular item in the Overview pane will typically display the item's properties in the properties pane.
Right-clicking items in the Overview pane gives you access to management features.
Properties Pane
Displays properties of the item selected in the Overview pane. In many cases,
properties are displayed across a number of tabs:
Example of properties displayed on tabs
Preview Pane
Displays preview images from selected cameras or state information from selected
microphones, speakers, inputs and outputs. The example to the left shows a camera preview
image with information about the resolution and data rate of the camera's live stream.
Tip: By default, information shown with camera preview images will concern live streams
(shown in green text). If you want recording stream information instead (shown in red text),
select View > Show Recording Streams from the Management Client's menu.
You will see the preview pane when you deal with recording servers and devices. You can toggle the preview
pane on and off in the View menu. To resize the preview pane, drag its borders. The larger the preview pane, the
larger preview images and state information will appear.
Tip: Performance can be affected if the preview pane displays preview images from many cameras at a high
frame rate. To control the number of preview images, and their frame rate, select Options > General from the
Tools menu.
Get Started
In the following, the tasks typically involved in setting up an XProtect Corporate system are listed.
Note that although information is presented as a checklist, a completed checklist does not in itself guarantee that
the XProtect Corporate system will match the exact requirements of your organization. To make the system
match the needs of your organization, it is highly recommended that you monitor and adjust the system once it is
running.
For example, it is often a good idea to spend time on testing and adjusting the motion detection sensitivity settings
of individual cameras under different physical conditions (day/night, windy calm weather, etc.) once the system is
running. The setup of rules, which determine most of the actions performed by the XProtect Corporate system
(including when to record video), is another example of configuration which to a very large extent depends on
your organization's needs.
Install the various components of your XProtect Corporate system. See Installation Overview on page
22.
Log in to the Management Client. See Log in to the Management Client on page 59.
Authorize use of your XProtect Corporate system's recording servers. See Manage Recording Servers
on page 87.
Why must I authorize recording servers? By authorizing recording servers before they can be used,
surveillance system administrators have full control over which recording servers are able to send
information to their XProtect Corporate management server.
www.milestonesys.com
Page 57
Management Client
Management Client
Detect the hardware devices (i.e. cameras and video encoders) which should be added to each
recording server. See the wizard Detect Hardware on page 75.
What is the Detect Hardware wizard? Detect Hardware helps you detect IP hardware devices, such as
cameras and video encoders, on your network and add them to your XProtect Corporate system. The
wizard offers you two ways of detecting and adding hardware devices: With automatic hardware
detection, XProtect Corporate automatically scans for available hardware within one or more specified IP
address ranges. With assisted hardware detection, you manually specify the IP address of each required
device. Both options offer the possibility of automatically detecting the correct hardware drivers.
Verify that each recording server's storage areas will meet your needs. See About Storage and Archiving
on page 70.
What is a storage area? A storage area is a directory in which the databases containing recordings
from the cameras connected to the recording server are stored — each individual camera database by
default has a maximum size of 5 GB. A default storage area is automatically created for each recording
server when the recording server is installed on the system. Connected cameras’ databases are stored
in the recording server's default storage area unless you specifically define that another storage area
should be used for storing the databases of particular cameras. If required, a wizard lets you add further
storage areas (on the recording server computer itself, or at another location, for example on a network
drive), edit which storage area should be the default area, etc.
Verify that each recording server's archiving settings will meet your needs. See About Storage and
Archiving on page 70.
What is archiving? Archiving is the automatic transfer of recordings from a camera's default database
to another location. This way, the amount of recordings you are able to store will not be limited by the
size of the camera's default database. Archiving also makes it possible to back up your recordings on
backup media of your choice. Archiving is configured on a per-recording server basis. Once you have
configured the archiving settings for a recording server (where to store archives, how often to transfer
recordings to the archives, etc.), you can enable archiving for individual cameras. When archiving is
enabled for a camera, the contents of the camera's database will automatically be moved to an archive
at regular intervals.
Configure any required failover servers. A failover server is a spare recording server which can take over if
a regular recording server becomes unavailable. See About Failover Servers on page 222.
Configure each recording server's individual cameras. See Manage Cameras on page 106.
Tip: You are able to group cameras, and configure common properties for all cameras within a group in
one go.
Tip: Motion detection, a vital setting on most IP surveillance systems, is enabled by default. However,
you may want to fine-tune motion detection settings, or disable motion detection for particular cameras.
Enable and configure microphones — if any. See Manage Microphones on page 110.
Enable and configure speakers — if any. See Manage Speakers on page 115.
Enable and configure input — if any. See Manage Inputs on page 107.
Enable and configure output — if any. See Manage Outputs on page 113.
Create rules. See Manage Rules on page 155.
What is a rule? Rules are a central element in XProtect Corporate. The behavior of an XProtect
Corporate system is to a very large extent determined by rules. Rules determine highly important
settings, such as when cameras should record, when PTZ (Pan/Tilt/Zoom) cameras should patrol, when
notifications should be sent, etc.
Tip: When creating rules, you may also want to use time profiles (see page 161) (for quickly making
rules apply within or outside predefined periods of time) or notification profiles (see page 152) (for quickly
making rules send pre-configured e-mails — with video clips, if required — to selected recipients).
Add roles. See About Roles on page 164.
www.milestonesys.com
Page 58
Management Client
Management Client
What is a role? Roles determine which XProtect Corporate features users and groups are able to use.
In other words, roles determine rights.
Add users and/or groups of users. See About Users and Groups on page 168.
Tip: If you have a server with Active Directory installed, and acting as domain controller on your
network, XProtect Corporate lets you quickly add users and/or groups from Active Directory.
Activate licenses. See About Licensing on page 67.
Why must licenses be activated? When installing the system, you used a single temporary license.
The temporary license is only valid for a certain number of days. After this initial period ends, all
recording servers and cameras on your system will require activation of their individual licenses. You
must therefore activate your licenses before the initial period ends, since all recording servers and
cameras for which no licenses have been activated will otherwise stop sending data to the surveillance
system.
Use the Download Manager to make additional components available to users—if required. See Use
the Download Manager on page 48.
What is the Download Manager? An application which lets surveillance system administrators
manage which system-related components (e.g. particular language versions of clients) surveillance
system users will be able to access from a targeted web page generated by the management server.
Tip: The default configuration of the Download Manager ensures that end users have access to the
Smart Client and Remote Client in language versions matching the language of your XProtect
Corporate system. Basically, you only have to use the Download Manager if you want to make
additional language versions, plug-ins or similar available to your organization's users.
Log in to the Management Client
Access to the XProtect Corporate Management Client requires certain user rights. Consult your surveillance
system administrator if in doubt.
Management Client login window
1.
Click the XProtect Corporate
Management Client desktop icon or—in
Windows' Start menu—select All
Programs > XProtect Corporate >
Management Client. This will make the
login window appear:
2.
The login window's Server type field will
in many cases appear dimmed and prefilled with the required information. If
not, select XProtect Corporate.
3.
In the Server address field, type the IP
address or host name of the computer running the XProtect Corporate management server.
Tip: If you have logged in before, you can select previously used server IP addresses or host names
from the list.
4.
By default, you will log in to the management server with your active Windows account. This means that
if you are currently logged in as, for example, JohnSmith, you will by default log in to the management
server as JohnSmith as well.

If you wish to log in to the management server with your active Windows account (this is the
default login option), select Windows Authentication (current user) in the Authentication field.

If you wish to log in to the management server with a different Windows account, select
Windows Authentication in the Authentication field, then type the required user name and
password in the User name and Password fields respectively.
www.milestonesys.com
Page 59
Management Client
Management Client
Tip: If you have logged in with Windows Authentication before, you can select previously
entered user names from the list.
Tip: When using Windows Authentication, you have the option of selecting Remember
password, in which case you will not have to type the password at subsequent logins.
5.
Click the Connect button to open Management Client.
Management Client Menu Overview
Example only; some menus changes depending on context.
Action Menu Items
(Depending on context)

Refresh is always available and reloads the requested information from the management server.

Expand (or Collapse) is available when working with Federated architecture, Servers, Devices, Client,
Rules and Events and System Dashboard.

A number of context specific items.
Be aware of the following when working with the Action menu concerning federated architecture (see page 201):
To be able to delete a site without being connected to it, right-clicking a site does not select it, but offers a
context menu. Because of this, some context menu items may be disabled if you are not connected to the site
and some are only available on the home-site, i.e. the site you are logged in to. For more details see Manage
Federated Architecture on page 207.
Edit Menu Items

Undo lets you cancel your latest action.
Tip: As an alternative to selecting Edit > Undo, press CTRL+Z on your keyboard.
File Menu Items

Save: Lets you save your current configuration.
Tip: As an alternative to selecting File > Save, press CTRL+S on your keyboard.

Logoff...: Lets you log out of the Management Client, and log in with another user account if necessary.

Exit: Lets you close down and exit the Management Client.
www.milestonesys.com
Page 60
Management Client
Management Client
Help Menu Items

Help... lets you access a help topic relevant to your task.

Contents... lets you access the help system's table of contents.

Search... lets you access the help system's search feature.

About... opens a dialog displaying information about the version of your Management Client.
Tools Menu Items

Registered Services... lets you add trusted servers. See Manage Trusted Servers on page 194 for
details.

Enterprise Servers... lets you add XProtect Enterprise servers specifically. See Manage XProtect
Enterprise Servers on page 191 for details.

Effective Roles... lets you view all roles of a selected user or group (see page 168). For more
information, see Manage Roles on page 166.

Options... opens the Options dialog (see page 195), which lets you define and edit several global
XProtect Corporate settings.
View Menu Items
(Depending on context)

Reset Application Layout: Lets you reset the layout of the different panes in the Management Client to
their default settings. See Customize the Management Client's Layout on page 61 for details.

Preview Window: Lets you toggle the preview pane on and off when working with recording servers and
devices.
Tip: If the preview pane displays images from many cameras at a high frame rate, it may slow down
performance. To specify the number of preview images you want in your preview pane, as well as their
frame rate, select Options > General from the Tools menu.

Show Recording Streams: By default, the information shown with preview images in the preview pane
will concern cameras' live streams (shown in green text). If you want information about recording
streams instead, select Show Recording Streams. Recording stream information will be shown in red
text.

Federated Site Hierarchy: By default, the Federated Sites Hierarchy pane is enabled, and this
command lets you toggle it on and off.

Site Navigation: By default, the Site Navigation pane (see page 56) is enabled, and this command lets
you toggle it on and off.
You can rearrange panes in the Management Client, and thus customize its look to suit your needs. If you
rearrange the panes, you can always reset the entire layout to the Management Client's default layout.
Customize the Management Client's Layout
Resizing Panes
You can resize panes by dragging the borders of the panes:
www.milestonesys.com
Page 61
Management Client
Management Client
1.
Place your mouse pointer over a border.
2.
When the pointer becomes a doubleheaded arrow, drag the border in the
required direction.
The size of the content inside the panes stays the
same regardless of the size of the panes, with one
exception: the larger the preview pane is, the larger preview images and state information will appear.
Moving Panes
You can move a pane to a different position either as a floating
pane or to a docked position, by clicking on a pane's title bar and
dragging it with the mouse.
The position and whether the pane becomes a floating pane or
docked depend on where you release the mouse button. See the
following topics for more information.
The Management Client offers some layout elements
that help you control the new position of the pane. The
layout elements are available when you drag a pane.
Outer lay elements illustrated with green
Inner layout elements illustrated with blue
Center layout element illustrated with red
For more information about how you use the layout elements when moving panes see these topics:
Floating Panes
To move a pane
to a floating
pane, drag the
pane to its new
position without
using one of the
layout elements.
< Dragging a pane
to a position
without using a
layout element…
Result: A floating
pane >
Moving a Pane to a Docked Outer Position
If you move a pane to a docked outer position, it fills the area with a horizontal or vertical split that goes from top
to bottom or left to right.
1.
Drag the pane to one of the outer layout elements.
Tip: Before you release the mouse, the pane's new position is indicated by a gray area.
2.
Release the mouse to dock the pane at its current position.
www.milestonesys.com
Page 62
Management Client
Management Client
< Dragging
a pane to
the right
outer layout
element.
Result: The
pane is
docked to
the right >
Moving a Pane to a Docked Inner Position
If you drag the pane to one of the inner layout elements, the pane will be positioned along one side of one of the
other panes.
1.
Drag the pane to one of the inner layout elements.
Tip: Before you release the mouse, the pane's new position is indicated by a gray area.
2.
Release the mouse to dock the pane at its current position.
< The pane
is docked to
the right of
the
Overview
pane
Result:
Dragging a
pane to the
right inner
layout
element of
the
Overview
pane >
Moving a Pane to a Shared Position
You can move a pane into another pane's position so two or more panes share the same position:
1.
Drag the pane to the center layout element of the pane which position you want to share.
Tip: Before you release the mouse, the pane's new position is indicated by a gray area.
The center layout element
2.
Release the mouse to dock the pane at its current position.
Tip: To view the content of the panes, click the tabs on the bottom of the shared position.
< Dragging a
pane to the
inner center
layout element
of another
pane
Result: The
pane shares
the same
position as the
other pane >
www.milestonesys.com
Page 63
Management Client
Management Client
Splitting Shared Positions
If you do not want a pane to share a position with another pane, do this:
1.
Click the tab of the relevant pane and drag it to a new position.
The pane's new position can be a docked position or a floating pane.
2.
Release the mouse to place the pane at its current position.
Using Auto-Hide
You can auto-hide panes. An auto-hidden pane is available as a tab to the right or left of the previous position of
the pane. When you place your mouse pointer over the tab, the content of the pane slides out. As soon the cursor
is positioned outside the pane, it slides back.
To auto-hide a pane click the Auto Hide pushpin in the title bar of the pane you want to auto-hide.
< Default appearance and position of the
Overview pane.
The Overview pane is hidden and available
through a tab to the left.>
Do the following to show and open an
auto-hidden pane again:
1.
Place your mouse pointer over the tab of the auto-hidden pane to
show the pane.
2.
Click the Auto Hide pushpin in the title bar of the pane to dock the
pane.
Resetting to Default Layout
If you have moved, resized and auto-hidden panes and now want to reset the entire layout of the panes in the
Management Client to their default settings, do the following:
1.
From the Management Client's View menu, select Reset Application Layout.
2.
Restart the application.
Toggling Preview Pane On and Off
You can close the preview pane when working with recorders and devices by clicking the Close button in the right
side of the preview pane's title bar.
To reopen the preview pane select Preview Window from the Management Client's View menu.
Tip: If the preview pane displays images from many cameras at a high frame rate, it may slow down performance.
To specify the number of preview images you want in your preview pane, as well as their frame rate, select
Options > General from the Tools menu.
Tip: When the preview pane is closed, it uses no resources and improves therefore the computer's performance.
Activate Licenses
You can activate your licenses in two ways: online or offline.
Tip: If the computer running the Management Client has internet access, use online activation for a quick and
convenient activation procedure.
www.milestonesys.com
Page 64
Management Client
Management Client
You cannot activate more licenses than you have bought. To view your total number of licenses, expand Basics in
the Management Client's Site Navigation pane (see page 56), and select License Information. If you have added
more cameras than you have licenses for, you must get additional licenses before you can activate them.
Activate Licenses Online
In the Management Client’s Site Navigation pane (see page 56), expand Basics, right-click License Information,
and select Activate License Online.
1.
Activate Licenses Online opens. On the wizard’s first step, select either:

Existing User to use an existing user account on the online licensing system.
- or -

New User to set up a new user account on the online licensing system.
2.
Click Next.
3.
Then specify user name and password.
4.
If you select Save password, the password will be saved on the computer, and can be accessed by other
users of the computer.
5.
Click Next, and follow the wizard's remaining steps to activate your licenses. When your licenses have
been activated, you will see a confirmation.
6.
Click Finish to end the activation.
If You Receive an Online Activation Error Message
Under rare circumstances you may receive an error message during online activation. Often, such error
messages will simply inform you that you forgot to include certain required information.
Should you receive an error message which refers to a slightly more complicated problem, the following list of
selected error messages will help you identify the problem and find out what to do:




The new user could not be created.
The new user could not be created. An error occurred on the server.
The new user could not be created. Access was denied.
The new user could not be created. Unable to communicate with the activation server.
o Problem: It was not possible to register you as a new user, either due to a problem on the
online activation server itself, due to a problem with your connection to the online activation
server, or due to a problem with the specified information.
o What to do: Contact Milestone Support ( support@milestonesys.com ), who will investigate the
issue for you.

The new user could not be created. The specified user name is already registered.
o Problem: The e-mail address you specified as user name on Activate Licenses Online's Enter
new user information step, is already registered on the system.
o What to do: Since you have already registered your e-mail address, you should be able to
activate as an existing user (selectable on Activate Licenses Online's first step). If you have
forgotten your password, use the password reminder feature on the Milestone website: Go to
www.milestonesys.com , click Software Registration in the menu, then the Forgot my password!
link. When you have received a password reminder e-mail, proceed with online activation
through the Management Client's Activate Licenses Online.

Could not acquire a new license.
www.milestonesys.com
Page 65
Management Client
Management Client





Could not acquire a new license. An error occurred on the activation server. Please try later.
Could not acquire a new license. Access was denied.
Could not acquire a new license. The format of the activation request was invalid.
Could not acquire a new license. The requested license could not be granted. Please contact the
software support to correct this problem.
Could not acquire a new license. Unable to communicate with the license activation server.
o Problem: Online activation was not possible, either due to a problem on the online activation
server itself, due to a problem with your connection to the online activation server, or due to a
problem with the specified information.
o What to do: Contact Milestone Support ( support@milestonesys.com ), who will investigate the
issue for you.

Could not acquire a new license. The license has already been activated on another system.
o Problem: License activation has already taken place on another XProtect Corporate system;
you cannot activate licenses on more than one system.
o What to do: Activation should not be necessary, as another system already runs with your
licenses activated. If you believe that this is wrong, contact Milestone Support (
support@milestonesys.com ), who will investigate the issue for you.

Could not acquire a new license. The SLC was not registered.
o Problem: Activation cannot take place before the SLC (Software License Code) for your
XProtect Corporate system has not been registered.
o What to do: Register the SLC (see Manage Software License Codes (SLC), Registering Your
Software License Code (SLC) on page 69, for a step-by-step description of the brief and easy
registration process). When the SLC is registered, use XProtect Corporate’s Activate Licenses
Online again, remembering to log in with the same user name and password as you used when
registering the SLC.

Could not acquire a new license. The specified user is not allowed to activate this system.
o Problem: The SLC (Software License Code) for your system has been registered by another
user name than the user name (e-mail address) you have specified on Activate Licenses
Online's Enter new user information step. Online activation must take place with the user name
under which the SLC was registered.
o What to do: Find out under which user name the SLC was registered, then activate as an
existing user (selectable on Activate Licenses Online's first step). If in doubt about which user
name was used for registering the SLC, contact Milestone Support (
support@milestonesys.com ), quoting your SLC.

Could not acquire a new license. The specified user name or password was not correct.
o Problem: License activation was not possible to due to a problem with the user name or
password you have specified on Activate Licenses Online's Enter new user information step.
o What to do: Verify that you have typed user name and password exactly as they were
specified when you registered the SLC (Software License Code) for your XProtect Corporate
system. If in doubt about which user name was used for registering the SLC, contact Milestone
Support ( support@milestonesys.com ), quoting your SLC.

Could not acquire a new license. Too many licenses for camera feeds requested.
o Problem: If you have added more camera feeds to your XProtect Corporate system than you
currently have licenses for, you must purchase additional licenses for these feeds before you
will be able to activate them.
o What to do: To obtain additional licenses, contact your XProtect Corporate vendor, or visit
www.milestonesys.com to log into the software registration service center. When you have
received an updated license file (.lic) with the new licenses, you can activate your licenses
online. See also Getting Additional Licenses.
www.milestonesys.com
Page 66
Management Client
Management Client

Could not acquire a new license. Too many recording server licenses requested.
o Problem: If you have added more recording servers to your XProtect Corporate system than
you currently have licenses for, you must purchase additional licenses for these recording
servers before you will be able to activate them.
o What to do: To obtain additional licenses, contact your XProtect Corporate vendor, or visit
www.milestonesys.com to log into the software registration service center. When you have
received an updated license file (.lic) with the new licenses, you can activate your licenses
online. See also Getting Additional Licenses.
Activate Licenses Offline
1.
In the Management Client's Site Navigation pane (see page 56), expand Basics, right-click License
Information, and select Activate License Offline > Export License For Activation to export a file with your
currently added recording servers and cameras.
2.
Specify a file name and a location for the license request (.lrq) file.
3.
Open an internet browser and go to Milestone's web site at http://www.milestonesys.com, then select
Software Registration from the top menu. Log in with your e-mail and password, if you have used the
software registration system before, otherwise, click New to the System? to create a new user account.
a.
Select the SLC under Current SLCs.
b.
In the menu for SLC properties, use the Upload LRQ function to upload the generated .lrq file.
How long will this process take? You will immediately after uploading the LRQ file receive an e-mail
with the updated license file.
4.
When you have received the updated license file (.lic), save it at a location accessible from the
Management Client.
5.
In the Management Client's Site Navigation pane (see page 56), expand Basics, right-click License
Information, select Activate License Offline > Import Activated License, and select the .lic file to import it.
6.
Click Finish to end the activation process.
Activating Licenses after the Grace Day Period
If the grace day period is exceeded before activation, all cameras which are not activated within the given period
will become unavailable, and will not be able to send data to the surveillance system.
If you exceed the grace day period before you activate a license, the license is not lost. You can activate the
license as usual.
Configuration, added cameras, defined recording servers, and other settings will not be removed from the
Management Client if a license is activated too late.
Manage Licenses
When you purchase XProtect Corporate, you also purchase a certain number of licenses for device channels.
Device channels are typically cameras but could also be dedicated input/output boxes.
At first, when you have installed the various XProtect Corporate components, configured the system, and added
recording servers and cameras through the Management Client, the surveillance system runs on temporary
licenses which need to be activated before a certain period ends. This is the so-called grace day period.
When the new surveillance system is working, we recommend that you activate your licenses (see page 64)
before you make the final adjustments. The reason is that you must activate your licenses before the grace day
www.milestonesys.com
Page 67
Management Client
Management Client
period expires, since all recording servers and cameras for which no licenses have been activated will not be able
to send data to the surveillance system if the grace day period is expired.
See also What to Know about Licenses and Milestone Federated Architecture on page 203.
Which Devices Require a License?
You need licenses for the number of device channels—typically cameras but it could also be dedicated input/out
boxes—you want to run on the XProtect Corporate system. One device channel license enables you to run one
camera or one dedicated input/output box. You can use and define an unlimited number of recording servers,
microphones, speakers, inputs and outputs.
You can always get more licenses as your surveillance system grows. See Getting Additional Licenses later in
this topic.
What to Know When Replacing Cameras?
You can replace a camera licensed in the XProtect Corporate system with a new camera, and have the new
camera activated and licensed instead.
The total number of purchased device channels corresponds to the total number of cameras that are able to run
on the surveillance system simultaneously. If you remove a camera from a recording server, you also free a
license.
If you replace a camera with a similar camera (manufacturer, brand, and model), and give the new camera the
same IP address as the old one, you will maintain full access to all the camera's databases. In this case, you
simply move the network cable from the old camera to the new one without changing any settings in the
Management Client, and then activate the license.
If replacing a camera with a different model, you must use the Management Client's Replace Hardware wizard to
map all relevant databases of cameras, microphones, inputs, outputs, etc. When done, remember to activate the
license. For details on the Replace Hardware wizard, see Manage Hardware (on page 79) and expand the
Replacing Hardware section.
There is no limit to the number of cameras you can replace.
Viewing Your License Information
You get an excellent overview of the licenses in your XProtect Corporate system if you expand Basics in the
Management Client's Site Navigation pane (see page 56), and then select License Information. This will bring up
the License Information page, on which you can see:

Your software license code

The total number of available device channels (typically cameras but it could also be dedicated
input/output boxes) you are licensed to run

How many licenses you have used, both the number of activated licenses and the number of temporary
(not activated) licenses

Whether you need to get additional licenses in order to have enough licenses for all of your cameras

Any other installed products used with XProtect Corporate, and—if applicable—their Software License
Code.
Any expiry dates listed on the page are in the management server's local time. Since you are not necessarily
located in the same time zone as the management server, the management server's current local time is
displayed in the bottom right corner of the page.
You can activate licenses (see page 64) online or offline, by expanding Basics in the Site Navigation pane (see
page 56), and right-clicking License Information.
www.milestonesys.com
Page 68
Management Client
Management Client
Example only; numbers
and dates may be
different on your system
The cameras (or dedicated
input/output boxes) for
which you do not have a
license will not send data
to the surveillance system.
Cameras added after all
available licenses are used are unavailable. Cameras without licenses will be identified by an exclamation mark
symbol when listed in the Management Client's Overview pane (see page 56).
Tip: In the short period until you have obtained additional licenses, you can disable some less important cameras
to allow some of the new cameras to run instead. See Manage Hardware (see page 79) for more information.
Where I Can See How Many Grace Days I Have Left?
This information is also available from the License Information page where you can see if you need to get more
licenses so all added cameras can deliver data to XProtect Corporate.
When you add a new camera for which you have a license, you are granted a new full grace day period for the
camera in question from the date you added the camera. Therefore the end date of the grace day period
displayed on the License information page is for the first added but not activated camera.
Getting Additional Licenses
What if you want to add—or if you already have added—more device channels (cameras or dedicated
input/output boxes) than you currently have licenses for? In that case, you must buy additional licenses before the
cameras will be able to send data to your XProtect Corporate system.
To get additional licenses for your XProtect Corporate system, contact your XProtect Corporate vendor, or visit
www.milestonesys.com to log into the software registration service center.
When you have received an updated license file (.lic) with the new licenses, you can activate your licenses. See
Activate Licenses (see page 64) for more information.
Tip: In the short period until you get the additional licenses, you can disable some less important cameras to
allow some of the new cameras to run instead. To disable or enable a camera, expand Recording Servers in
Management Client's Site Navigation pane (see page 56), then select the required recording server, right-click the
required camera, and select Enable.
Manage Software License Codes (SLC)
When you purchase XProtect Corporate, you receive a Software License Code (SLC), which is used when
installing your system.
Registering Your Software License Code (SLC)
The SLC is printed on the product license sheet enclosed with the software CD as well as on your order
confirmation. You should also register your SLC before activating your XProtect Corporate system's licenses (see
page 64).
The SLC registration process is brief and easy:
1.
Go to the Milestone Systems website at www.milestonesys.com, and click the Software registration link
in the menu.
2.
Log in to the Software Registration Service Center with your user name (e-mail address) and password.
www.milestonesys.com
Page 69
Management Client
Management Client
Tip: If you have not used the Software Registration Service Center before, click the New to the system?
link, and follow the instructions for registering yourself as a user; then log in to the Software Registration
Service Center using your registered user name and password.
3.
In the Software Registration Service Center, click the Add SLC link.
4.
Type your SLC. When asked whether you want to add the SLC to your account, click OK.
5.
Once your SLC has been added, click the main menu link.
6.
Click the Logout link to log out of the Software Registration Service Center.
Tip: If you plan to use online activation when activating your licenses, make sure you use the same user
name (e-mail address) and password for the activation as you did when registering the SLC.
Changing Your Software License Code (SLC)
Often you run your installation on a trial SLC during the first period. When the trial period is over, and it is time to
change the trial SLC to the permanent SLC, you can do this without any un- or reinstall action.
IMPORTANT: This must be done locally on the management server in question; you cannot do this from the
Management Client.
1.
On the management server, go to the notification area of the taskbar (a.k.a. Systray).
2.
Right-click the XProtect
Corporate Management
Server icon, select Change
License....
3.
The Change XProtect Corporate
License dialog appears. Click Import
License....
4.
Next, select the SLC license file saved
for this purpose. When done, the
selected license file location will be
added.
5.
Click OK. You are now ready to
perform SLC registration.
Servers
About Storage and Archiving
When a camera or device records video and/or audio, all specified recordings are per default stored in the storage
area defined for the device. More precisely in the storage areas default recording database named Recording. A
storage area has no default archive(s), but these can easily be created.
Depending on recording settings, the storage areas recording database will most likely run full at some point and
its contents need to be archived in order to be saved. It is therefore possible to create archives within the default
storage area and start an archiving process. Furthermore, it is possible to create alternative storage(s) and
configure that selected video/audio recordings must be stored/archived here.
Archiving is the automatic transfer of recordings from a camera's or device's default database to another location.
This way, the amount of recordings you are able to store will not be limited by the size of the device's recording
database. Archiving also makes it possible to back up your recordings on backup media of your choice.
Storage and archiving is configured on a per-recording server basis.
www.milestonesys.com
Page 70
Management Client
Management Client
To ease explanations, the following mostly mentions cameras and video, but al is true about speakers and
microphones and audio and sound as well.
IMPORTANT: We recommend that you use a dedicated hard disk drive for the recording server database. Using
a dedicated hard disk drive for the database will prevent low disk performance. Furthermore, when formatting the
hard disk, it is important to change its Allocation unit size setting from 4 to 64 kilobytes. This is to significantly
improve recording performance of the hard disk. You can read more about allocating unit sizes and find help at
http://support.microsoft.com/kb/140365/en-us.
IMPORTANT: The oldest data in a database will always be auto-archived (or deleted if no next archive is defined)
when less than 5GB of space is free. If less than 1GB space is free, data will be deleted. A database always
requires 250MB of free space; if this limit is reached (if data is not deleted fast enough), no more data will be
written to the database until enough space has been freed. The actual maximum size of your database will thus
be the amount of gigabytes you specify, minus 5GB.
Attaching Devices to a Recording Server
Once you have configured the storage areas and archiving settings for a recording server (where to store
recordings, archives, how often to transfer recordings to archives, etc.), you can enable storage and archiving for
individual cameras or a group of cameras. This is done from the individual devices or from the device group, see
Attaching Individual Devices or a Group of Devices to a Storage Area section later in this topic.
Effective Archiving
When archiving is enabled for a camera or a group of cameras, the contents of the camera(s)' database will
automatically be moved to an archive at regular intervals.
Depending on your requirements, you are able to configure one or more archives for each of your databases.
Archives can be located either on the recording server computer itself, or at another location which can be
reached by XProtect Corporate, for example on a network drive.
By setting up your archiving in an effective way, you can prune and groom your database storage usage
significantly if needed. Often, it is desired to make archived recordings take up as little space as possible—
especially on a long-term basis, where it is perhaps even possible to slacken image and sound quality a bit.
Effective pruning and grooming can help ensure this and can be handled from the Storage tab (see page 91) of a
recording server by adjusting several interdependent settings such as:

Recording database retention

Recording database size

Archive retention

Archive size

Archive schedule

Encryption

Frames Per Second (FPS).
The size fields define the size of the camera's database,
exemplified by the cylinder in the following, and its archive(s)
respectively:
Recordings' way from recording database to archive to deletion
By means of retention time and size setting for the recording
database, exemplified by the white area in the cylinder, you
define how old recordings must be before they are archived. In
our illustrated example, recordings are archived when they
have "sifted" down into the green area of the database
cylinder, or in other words: when they are old enough to be
archived.
The retention time and size setting for archives define how long the recordings remain in the archive; recordings
remain in the archive for the time specified, or until the archive has reached the specified size limit. When these
www.milestonesys.com
Page 71
Management Client
Management Client
settings are met, XProtect Corporate begins to overwrite old recordings in the archive.
The archiving schedule defines how often and at what times archiving takes place.
Encryption and FPS determine the size of the data in the databases.
To have recordings archived, all these parameters must be set up in accordance with each other. This means that
the retention period of a next coming archive must always be longer than the retention period of a current archive
or recording database. This is due to the fact that the number of retention days stated for an archive includes all
retention stated earlier in the process. Furthermore, archiving must always take place more frequently than the
retention period is set to, otherwise you risk losing data. If you have a retention time of 24 hours, any data older
than 24 hours will be deleted. Therefore, to get your data safely moved to the next archive, it is important to run
archiving more often than every 24 hours.
Example: These storage areas (image to the left) has a retention time of 4 days and the following
archive (image to the right) a retention time of 10 days. Furthermore, archiving is set to occur every day
at 10:30, ensuring a much more frequent archiving than retention time is set to.
Tip: You can also control archiving by use of
rules and events. See About Rules and
Events on page 140 and Events Overview on
page 148.
Attaching Individual Devices or a Group of Devices to a Storage Area
Once a storage area is configured for a recording server, you can enable it for individual devices (cameras,
microphones or speakers) or a group of devices. You can also select which of a recording server's storage areas
should be used for the individual device or the group.
1.
In the Site Navigation pane (see page 56), expand Devices and select either Cameras, Microphones or
Speakers as required.
2.
In the Overview pane (see page 56), select the required device or a device group.
3.
In the Properties pane (see page 56), select the Record tab.
4.
In the Storage area, select Select...
5.
In the dialog that appears, select the wanted database, click OK.
6.
In the toolbar (see page 55), click Save.
Viewing Archived Recordings
You view archived recordings in the Smart Client. As long as the archived recordings are stored locally or on
accessible network drives, you can use the Smart Client’s many features (timeline browser, smart search,
www.milestonesys.com
Page 72
Management Client
Management Client
evidence export, etc.) when browsing archived recordings; just like you would with recordings stored in a
cameras' regular databases. The fact that you are viewing archived recordings will be completely transparent.
Remember that individual user rights may prevent particular users from viewing recordings from particular
cameras— just as is the case when browsing recordings from cameras' regular databases.
Backing up Archived Recordings
Many organizations want to back up their recordings, using tape drives or similar. Exactly how you do this is
highly individual, depending on the backup media used in your organization. However, the following is worth
bearing in mind:
Back Up Archives Rather than Camera Databases
Always create backups based on the content of archives, not based on individual camera databases. Creating
backups based on the content of individual camera databases may cause sharing violations or other
malfunctions.
When scheduling a backup, make sure the backup job does not overlap with your specified archiving times.
Tip: You are able to view each recording server's archiving schedule in each of a recording server's archives, on
the Storage tab.
Knowing Archive Structure Lets You Target Backups
When recordings are archived, they are stored in a certain sub-directory structure within the archive.
During all regular use of your XProtect Corporate system, the sub-directory structure will be completely
transparent to the system's users, as they browse all recordings with the Smart Client regardless of whether the
recordings are archived or not. Knowing the sub-directory structure is thus primarily interesting if you want to back
up your archived recordings. See Archive Structure later in this topic.
Archive Structure
When recordings are archived, they are stored in a certain sub-directory structure within the archive.
During all regular use of your XProtect Corporate system, the sub-directory structure will be completely
transparent to the system's users, as they browse all recordings with the Smart Client regardless of whether the
recordings are archived or not. Knowing the sub-directory structure is thus primarily interesting if you want to back
up your archived recordings.
In each of the recording server's archive directories, separate sub-directories are automatically created. These
sub-directories are named after the GUID of the recording server.
What is a GUID? A GUID is a Globally Unique IDentifier; a unique 128-bit number used to identify components
on a Windows system. Example of a GUID: 469c37e4-28ad-487b-bcb7-e5fd7e5a609a.
Since you are able to store recordings from different cameras in the same archive, and since archiving for each
camera is likely to be performed at regular intervals, further sub-directories are also automatically added.
These sub-directories each represent approximately an hour's worth of recordings. The one-hour split makes it
possible to remove only relatively small parts of an archive's data if the maximum allowed size of the archive is
reached.
The sub-directories are named after the GUID of each camera plus the date and time of the most recent database
record contained in the sub-directory.
Naming structure:
...[Archive Name]\[Recording Server GUID]\[Camera GUID plus date and time of
most recent recording]\
Real life example:
...OurArchive\b82e691f-67cf-4177-a0b9-e69077d4d75a\469c37e4-28ad-487b-bcb7e5fd7e5a609a_2007-04-30_14-30-20\
In the example, the latest recording contained in the sub-directory is from 20 seconds past half past 2 in the
afternoon on April 30th 2007.
www.milestonesys.com
Page 73
Management Client
Management Client
Even further sub-directories are automatically added. The amount and nature of these sub-directories depend on
the nature of the actual recordings. For example, several different such sub-directories will be added if the
recordings are technically divided into sequences; something which is often the case if motion detection has been
used to trigger recordings.
If you want to back up your archives, knowing the basics of the sub-directory structure enables you to target your
backups. Examples:

If wishing to back up the content of an entire archive, back up the required archive directory and all of its
content; for example everything under:
...OurArchive\

If wishing to only back up the recordings from a particular camera from a particular period of time, back
up the contents of the relevant sub-directories only; for example everything under:
...OurArchive\b82e691f-67cf-4177-a0b9-e69077d4d75a\469c37e4-28ad-487bbcb7-e5fd7e5a609a_2007-04-30_14-30-20\
Archiving and Virus Scanning
If you are using virus scanning software on the computer on which the camera databases you want to archive are
located, or on a computer to which data is archived, it is likely that the virus scanning will use a considerable
amount of system resources on scanning all the data which is being archived.
This may affect system performance negatively. Also, virus scanning software may temporarily lock each file it
scans, which may further impact system performance negatively.
If possible, you should therefore disable any virus scanning of camera databases and archiving locations.
Frequently Asked Questions about Archiving
What happens if a storage area becomes unavailable?
If a storage area becomes unavailable— for example if the storage area is located on a network drive, and the
connection to the drive is lost— it will not be possible to store recordings in the storage area. XProtect Corporate
registers the availability of its recording servers' storage areas. This means that when a storage area becomes
available again, it will again be possible to save recordings in the storage area. However, any recordings from the
period in which the storage area was unavailable will be lost. When creating rules (see page 157), you can use
the events Database Storage Area Unavailable and Database Storage Area Available to trigger actions, such as
the automatic sending of e-mail to relevant people in your organization (see Events Overview on page 148 for
more information). Furthermore, information about a storage area becoming unavailable/available will be logged
(see page 178).
How do I ensure that archiving is set up correctly?
Archives are set up by adjusting several interdependent parameters correctly as described previously.
Can I create an archive on a network drive?
Archives can be located either on the recording server computer itself, or at another location which can be
reached by XProtect Corporate, for example on a network drive.
What happens when the maximum size of an archive is reached?
When you create archives from the Storage tab (see page 91), you specify a maximum size limit for the archive,
in days and gigabytes. When either of the two maximum limits is reached, recordings in excess of the specified
number of days/gigabytes will be removed. However, in order not to remove more recordings than necessary,
excess recordings will be removed in chunks of approximately one hour's worth of recordings.
What happens if a scheduled archiving fails?
If a scheduled archiving fails, for example because the archive is located on a network drive which is temporarily
unavailable, XProtect Corporate will retry archiving after an hour. If that fails, another retry will take place after yet
another hour, and so forth.
If the time of the next scheduled archiving is reached between two retries, an archiving attempt will be made at
the scheduled time; if that attempt fails, XProtect Corporate will retry archiving after an hour, and so forth.
What happens if archiving is not finished before the next scheduled archiving?
Your XProtect Corporate system inserts a compulsory period of archiving-free time after each finished archiving
job. This ensures that archiving jobs do not overlap in time.
www.milestonesys.com
Page 74
Management Client
Management Client
Detect Hardware
The Detect Hardware wizard helps you detect IP hardware devices, such as cameras and video encoders, on
your network and add them to recording servers on your XProtect Corporate system.
To access Detect Hardware, expand the Servers folder in the Management Client's Site Navigation pane (see
page 56) and select the Recording Server node, then in the Overview pane (see page 56), right-click the required
recording server and select Detect Hardware...
Detect Hardware opening page
The wizard offers you two ways of detecting
and adding hardware devices: With automatic
hardware detection, XProtect Corporate
automatically scans for available hardware
within one or more specified IP address
ranges. With assisted hardware detection, you
manually specify the IP address of each
required device. Both options offer the
possibility of automatically detecting the
correct hardware drivers.
Tip: If you are new to XProtect Corporate, use
automatic hardware detection; it will guide you through each of the steps involved in detecting and adding your IP
devices.
It is strongly advised that you only add a physical hardware device to one recording server at the time.
Automatic Hardware Detection
1.
On the first step of the Detect Hardware, select Automatic Hardware Detection and click Next.
2.
The wizard will then suggest one or more IP address ranges on which to detect devices. The number of
suggested ranges will depend on the number of network interface cards on the recording server. By
default, XProtect Corporate will scan the IP address range(s) for devices on port 80.
If the suggested IP address ranges are acceptable, simply go to step 3. Occasionally, you may want to
remove or edit the suggested IP address ranges, change the default port number, or add further IP
address ranges:

Adding or Editing an IP Address Range
To add or edit an IP address range, select the required range and click the Add button.
This will open the Add IP Range to Scan dialog, which
lets you edit the IP address range by changing the
beginning and end of the IP address range as required.
Tip: The beginning and end IP address may be
identical, allowing you to only scan for a single device, if
required.
If scanning for devices which support TCP/HTTP—most
devices do—keep the Use TCP port scanning box
selected.
You are also able to change the port number to scan
(default is port 80).
When XProtect Corporate detects a device, it will
automatically access the device with the device's factory
default user name and password. If one or more devices
within the specified IP address range require a nonfactory default user name and/or password, specify such
user names and passwords one at a time by clicking the Add... button.
Example: IP address range and additional user name and password defined
Click OK to return to the wizard.
www.milestonesys.com
Page 75
Management Client
Management Client
Note that you cannot add more than 100 devices to a recording server at a time. If you need to add
more than 100 devices, simply scan several times.
3.
When ready, the wizard lists all the IP address ranges you want to scan.
Example: A single IP
address range has been
defined
Click Next.
4.
The wizard searches
for devices within the
defined IP address
ranges. Depending on
the size of the IP
address ranges, and
whether they are on
the local network or
not, this may take a
while. While
searching, the wizard
generates a list of the
cameras it detects.
Example: Arrow indicates
list generated while wizard
searches IP ranges
Tip: Detection may
take a while, especially
if large IP ranges must
be searched. You can
interrupt the search at
any time by clicking the
Stop Scan button. Any
cameras detected up to
this point will be
remembered by the
wizard.
5.
When the wizard has finished searching, it will list detected devices. Initially, the list will only contain
known hardware, i.e. devices for which the wizard is automatically able to detect a hardware driver.
The wizard is able to
automatically detect
hardware drives for a
very large number of
devices.
Example: Wizard has
automatically detected
hardware drivers for a
number of cameras
Tip: For a preview
image from camera
devices in the list, click
the browser button
to access the camera's
default web page. You
may be asked to provide the user name and password for the device when accessing it this way.
www.milestonesys.com
Page 76
Management Client
Management Client
6.
Optional: To see any devices for which the wizard has not automatically been able to detect a
hardware driver, select the Show unknown hardware check box.
This will include any unknown hardware in the list. Such unknown devices will be indicated by question
mark icon: . For such devices, you are able to manually specify user name, password and hardware
driver.
Example: Manually
specifying hardware driver
for a device in the defined
IP address range. This will
seldom be necessary, as
the wizard can
automatically detect
drivers for many devices.
Note the green pencil icon
indicating the device being
manually specified.
Remember to select the
Include check box for
each manually
specified device. Click
Next.
7.
On the last step of the wizard, wait for camera setup information to be collected and the Status fields to
update to either Success or Failed, then click Finish.
8.
The devices are added to the recording server, and will appear in the Management Client's lists:
Example of added devices listed in Overview pane
Assisted Hardware Detection
1.
On the first step of Detect Hardware, select Assisted Hardware Detection and click Next.
2.
The wizard will then ask
you to enter information
about the required
hardware. For each
required device, specify
IP address, port number
(if other than the default
port 80), user name,
password, and hardware
driver.
Example: Manually selecting
hardware driver for a device.
Often, the wizard can automatically detect the driver.
www.milestonesys.com
Page 77
Management Client
Management Client
Tip: If you do not specify a user name and password, the factory default user name and password for
the device will automatically be added when you make your selection in the Hardware Driver column.
3.
Remember to select the Include check box for each required device.
Tip: Provided you have specified a valid user name and password, hardware drivers can often be
automatically detected: Simply click the Auto Detect button. If the driver is detected, a check mark will
appear in the second column. If the driver cannot be detected, a question mark
will appear, in which
case you should manually select the required driver.
Example: For the first device, a driver could automatically be detected; for
the second device, a driver could not be automatically detected, and must
be selected manually
Tip: For a preview image from a camera device in the list, click the browser button
to access the
camera's default web page. You may be asked to provide user name and password for the device when
accessing it this way.
4.
Repeat for each required device. Click Next.
5.
On the last step of the wizard, wait for camera setup information to be collected and the Status fields to
update to either Success or Failed, then click Finish.
6.
The required devices are added to the recording server, and will appear in the Management Client's lists.
Failover Tab (Recording Server Properties)
A failover server is a spare recording server which can take over if a
regular recording server becomes unavailable; see also About
Failover Servers on page 222.
If your organization uses failover servers, use the Failover tab to
select which groups of failover servers should take over from a
regular recording server if the recording server in question becomes
unavailable.
To access the Failover tab, select the required recording server in the
Overview pane (see page 56), then select the Failover tab in the
Properties pane (see page 56).
Selecting Required Failover Groups
Failover servers are always grouped; a group can contain one or
more failover servers.

Benefits of Using Failover Groups
Grouping has a clear benefit: When you specify which failover servers should be able to take over from a
recording server, you do not select a particular failover server; rather you select a failover group. If the
selected group contains more than one failover server, this gives you the security of being able to have
more than just one failover server ready to take over if the recording server becomes unavailable. For
information about configuring failover groups, see Manage Failover Servers on page 223.

Primary and Secondary Failover Group
For each recording server, you are able to select a primary and an optional secondary failover group. If
the recording server becomes unavailable, a failover server from the primary failover group will take
over. If you have also selected a secondary failover group, a failover server from the secondary group
will take over in case all failover servers in the primary failover group are busy. This way, you only risk
not having a failover solution in the rare case when all failover servers in the primary as well as in the
secondary failover group are busy.

How to Select Required Failover Groups
1. Select the required failover group from the Primary failover group list.
www.milestonesys.com
Page 78
Management Client
Management Client
2.
If you also want a secondary failover group for the recording server, repeat the process in the
Secondary failover group list.
You cannot select the same failover group for use as both primary and secondary failover
group.
Failover Service Communication Port
By default, TCP port 11000 is used for communication between recording servers and failover servers. Such
communication is primarily about the configuration of the recording server from which the failover server should
take over.
If required, you can change the port number. Note that if you change the port number, you must restart the
Recording Server service (see page 232) on the recording server in question.
Info Tab (Recording Server Properties)
You are able to verify or edit the name and description of a selected
recording server on the Info tab. To access the Info tab, select the
required recording server in the Overview pane (see page 56), then
select the Info tab in the Properties pane (see page 56).
Info tab, displaying information about a recording server
Info Tab's Fields

Name: Name of the recording server. The name will be
used whenever the recording server is listed in XProtect
Corporate and access clients. A name is not compulsory,
but highly recommended. The name does not have to be
unique.
To change the name, simply overwrite the existing name
and click Save in the toolbar (see page 55).
Tip: If you change the name, it will be updated throughout
XProtect Corporate. This means that if the name is used in, for example, a rule, the name will
automatically change in the rule as well.

Description: Description of the recording server. The description will appear in a number of listings
within XProtect Corporate. For example, the description will appear when pausing the mouse pointer
over the recording server's name in the Overview pane (see page 56). A description is not compulsory.
To specify a description, simply type the description and click Save in the toolbar (see page 55).

Host name: Non-editable field, displaying the recording server's host name.

Web server URL: Non-editable field, displaying the URL of the recording server's web server. The web
server is used, for example, for handling PTZ camera control commands, and for handling browse and
live requests from Smart Clients. The URL will include the port number used for web server
communication (typically port 7563).

Time zone: Non-editable field, displaying the time zone in which the recording server is located.
Manage Hardware
For each recording server on your system, you have several options for managing added IP hardware.
Most configuration and management of individual camera settings (such as a camera's recording settings), input
settings, and output settings takes place on a more detailed level; see Manage Cameras on page 106, Manage
Inputs on page 107, and Manage Outputs on page 113.
www.milestonesys.com
Page 79
Management Client
Management Client
Editing Basic Hardware Settings (IP, etc.)
You are able to edit basic settings, such as IP address/host name, for added hardware:
1.
In the Overview pane (see page 56), expand the required recording server, right-click the hardware
device you wish to edit.
2.
From the menu that appears, select Edit IP Hardware...:
This opens the Edit Hardware window, in which
you can edit the following:

Name: The name of the hardware in the
Management Client's lists, etc.
Tip: You can also quickly change the
name of a hardware device by selecting
Rename IP Hardware... from the menu.
3.

Description: (Optional) A description or
other information about the hardware
device. It will, among other places,
appear when you pause your mouse
pointer over the hardware device in the Overview pane (see page 56).

Hardware URL: URL, IP address, or
host name of the hardware device.

User name: Required to access and
use the hardware device.

Password: Required to access and use the hardware device.

Type: Non-editable field indicating the hardware driver used for the hardware device.
Click OK.
Deleting Individual Hardware
IMPORTANT: When deleting a hardware device, all its recordings are deleted permanently.
1.
In the Overview pane (see page 56), expand the required recording server, right-click the no longer
needed hardware device.
2.
From the menu that appears, select Delete IP Hardware.
Tip: As an alternative, press DELETE on your keyboard.
3.
Confirm that you want to delete the hardware device.
4.
The hardware device is removed from the recording server's listings in the Management Client.
Tip: If you ever need to add the hardware device to a recording server again, select the required recording server
and Detect Hardware.
Replacing Hardware
When you replace a physical camera (hardware device) on your network with another hardware device, you must
know the IP address, port, user name and password of the new hardware device.
Furthermore, when replacing hardware devices, note that your system might be affected by license limitations
(see page 67). Using the Activate Online wizard (see page 65), you must reactivate your licenses after replacing
hardware devices. Also note, that if the new number of cameras, microphones, inputs, outputs, etc. exceeds the
old number of cameras, microphones, inputs, outputs, etc. you might also have to buy new licenses. See
regarding your License Information on page 67.
www.milestonesys.com
Page 80
Management Client
Management Client
1.
In the Overview pane (see page 56), expand the required recording server, right-click the hardware
device you wish to replace.
2.
From the menu that appears, select Replace Hardware.
3.
The Replace Hardware wizard appears. Click Next.
4.
In the wizard, in the Address field (marked by red arrow in the image) , enter the IP address of the new
hardware. If known, select relevant hardware device driver from the Hardware Driver drop-down list
(marked by red arrow in the image) . Otherwise select (Auto Detect). If port, user name or/and password
data is different for the new device, also correct this before starting the auto detect process (if
needed).
Tip: The wizard is
pre-filled with
data from the
existing hardware
device. If you
replace it with a
similar hardware
device, you can
reuse some of
this data—for
example, port and
driver information.
5.
6.
Do one of the
following:

If you
selected the
required
hardware device driver directly from the list, click Next.

If you selected (Auto Detect) in the list, click the Auto Detect button, wait for this process to be
successful (marked by a to the far left), click Next.
This step is designed to help you map devices and their databases, depending on the number of
individual cameras, microphones, inputs, outputs, etc., attached to the old hardware device and the new
respectively.
It is important to consider how to map databases from the old hardware device to databases of the new
hardware device. You do the actual mapping of individual cameras, microphones, inputs, outputs, etc. by
selecting a corresponding camera, microphone, input, output or None in the right-side column.
IMPORTANT: Make sure to map all cameras, microphones, inputs, outputs, etc. Contents stored in
databases
belonging to
cameras,
microphones,
inputs,
outputs, etc.
mapped to
None, will be
lost.
Example of the
old hardware
device having
more individual
cameras,
microphones,
inputs, outputs,
etc,
than the new
one.
www.milestonesys.com
Page 81
Management Client
Management Client
Example of the
new hardware
device having
more individual
cameras,
microphones,
inputs, outputs,
etc, than the
old one.
Click Next.
7.
You are presented with a list of hardware to be added, replaced or removed. Click Confirm.
8.
Final step is a summary of added, replaced and inherited devices and their settings. Click Copy to
Clipboard to copy contents to an external source (for, for example, reporting purposes) or/and Close to
end the wizard.
Renaming Hardware
1.
In the Overview pane (see page 56), expand the required recording server, right-click the hardware
device you wish to rename.
2.
From the menu that appears, select Rename IP Hardware.
Tip: As an alternative, press F2 on your keyboard.
3.
Overwrite the name of the hardware.
Disabling/Enabling Hardware
Added hardware is by default enabled.
In the Overview pane (see page 56), under the required
recording server, enabled/disabled hardware devices are
indicated in the following way:
Enabled
Disabled
Disabling
Disable added hardware, for example, for licensing or
performance purposes:
1.
In the Overview pane (see page 56), expand the
required recording server, right-click the hardware
device you wish to disable.
www.milestonesys.com
Page 82
Management Client
Management Client
2.
From the menu that appears, select Enabled to clear it:
Deleting All Hardware on a Recording Server
IMPORTANT: When deleting hardware devices, all
recordings from the hardware devices in question
will be deleted permanently.
1.
In the Overview pane (see page 56), rightclick the required recording server where
you want to delete all hardware.
2.
From the menu that appears, select Delete
All Hardware:
3.
Confirm that you want to delete all
hardware on the selected recording server.
Renaming Individual Devices
1.
In the Overview pane (see page 56), expand the required
recording server and the required hardware device. Rightclick the camera, input, or output you wish to rename.
2.
From the menu that appears, select Rename Device:
Tip: As an alternative, press F2 on your keyboard.
3.
Overwrite the name of the selected device.
Enabling/Disabling Individual Devices
Cameras are by default enabled. Microphones, speakers, inputs and outputs are by default disabled.
This means that microphones, speakers, inputs and outputs must be individually enabled before they can be used
on the XProtect Corporate system. The reason for this is that surveillance systems inherently rely on cameras,
whereas the use of microphones, etc. is highly individual depending on organizations' needs.
In the Overview pane (see page 56), under the required server, enabled/disabled devices are indicated the
following way (examples show indications for an output):
Disabled
Enabled
The same method for enabling/disabling is used for cameras,
microphones, speakers, inputs, and outputs.
Enabling
1.
In the Overview pane (see page 56), expand the required
recording server and the required hardware device. Right-click the camera, input, or output you wish to
enable.
2.
From the menu that appears, select Enabled:
Manage Multicasting
XProtect Corporate supports multicasting of live streams from recording servers. In cases when many Smart
Client (see page 16) users want to view live video from the same camera, multicasting can help save
considerable system resources. Multicasting is thus particularly useful if using Smart Clients' Matrix functionality,
where multiple Smart Clients often require live video from the same camera.
Multicasting is only possible for live streams; not for recorded video/audio.
www.milestonesys.com
Page 83
Management Client
Management Client
If a recording server has more than one network interface card, it is only possible to multicast on one of them.
Through the Management Client you are able to specify which one to use.
The successful implementation of multicasting also
requires that your network equipment (switches, etc.) has
been set up to relay multicast data packets to the
required group of recipients only. If not; multicasting may
not be different from broadcasting, which can significantly
slow down network communication.
What Is Multicasting?
In regular network communication, each data packet is sent from a single sender to a single recipient—a process
known as unicasting. With multicasting, however, it is possible to send a single data packet (from a server) to
multiple recipients (clients) within a group. Multicasting can thus help save bandwidth.

When using unicasting, the source must transmit one data stream for each recipient.

When using multicasting, only a single data stream is required on each network segment.
Multicasting is therefore an interesting option for streaming live video from recording servers to Smart Clients
since video streams will not be duplicated on each network segment.
Multicasting as described here is not streaming of video from camera to servers.
With multicasting, you work with a clearly defined group of recipients, based on options such as IP address
ranges, the ability to enable/disable multicast for individual cameras, the ability to define largest acceptable data
packet size (MTU), the maximum number of routers a data packet must be forwarded between (TTL), etc. Thus,
multicasting should not be confused with the much more primitive method broadcasting, which would send data to
everyone connected to the network, even if the data is perhaps not relevant for everyone:

Unicasting sends data from a single source to a single recipient

Multicasting sends data from a single source to multiple recipients within a clearly defined group

Broadcasting sends data from a single source to everyone on a network; broadcasting can thus
significantly slow down network communication.
What Are the Requirements?
In order to use multicasting, your network infrastructure must support IGMP (Internet Group Management
Protocol, an IP multicasting standard).
Furthermore, multicasting must be configured through the Management Client as described in the following.
www.milestonesys.com
Page 84
Management Client
Management Client
Enabling Multicasting
On the Multicast tab, select the Live multicast check box.
If the entire IP address range for multicast (see the following) is already in use on one or more other recording
servers, you cannot enable multicasting on further recording servers without freeing up some multicasting IP
addresses first.
Assigning IP Address Range
In this section you specify the range from which you want to assign addresses for multicast streams from the
selected recording server. Access clients will connect to these addresses when viewing multicast video from the
recording server in question.
You specify this information in the following fields:

IP address: In the Start field, specify the first IP address in the required range. Then specify the last IP
address in the range in the End field. For more info, see the following.

Port: In the Start field, specify the first port number in the required range. Then specify the last port
number in the range in the End field.

Source IP address for all multicast streams: If a recording server has more than one network
interface card, it is only possible to multicast on one of them. This field is therefore relevant if your
recording server has more than one network interface card—or if it has a network interface card with
more than one IP address.
To use the recording server's default interface, leave the value 0.0.0.0 (IPv4) or :: (IPv6) in the field. If
you want to use another network interface card, or a different IP address on the same network interface
card, specify the IP address of the required interface.
Specifying Datagram Options
In this section you specify settings for data packets (datagrams) transmitted through multicasting.

MTU: Maximum Transmission Unit, the largest allowed physical data packet size (measured in bytes).
Messages larger than the specified MTU will be split into smaller packets before being sent. Default
value is 1500, which is also the default on most Windows computers and Ethernet networks.

TTL: Time To Live, the largest allowed number of hops a data packet should be able to travel before it is
discarded or returned. A hop is a point between two network devices, typically a router. Default value is
128.
Enabling Multicasting for Individual Cameras
Even when you have specified multicasting settings for the selected recording server, multicasting will not work
until you enable it for required cameras:
Select the required recording server in the Management Client's Site Navigation pane (see page 56), select the
required camera in the Overview pane (see page 56), then select Live multicast on the Client tab (see page 99) in
the Properties pane (see page 56). Repeat for all required cameras under the recording server in question.
How to Specify IP Address Range
To specify the range from which you want to assign addresses for multicast streams from the selected recording
server do the following:
For each multicast camera feed, the IP address/port combination (IPv4 example: 232.0.1.0:6000) must be unique.
You can thus either use one IP address and many ports, or many IP addresses and fewer ports. By default,
XProtect Corporate suggests a single IP address and a range of 1000 ports, but you can change this as required.
Example: If you want multicast for 1000 cameras, you would need either:
www.milestonesys.com
Page 85
Management Client
Management Client

1 IP address and a range of 1000 different ports, OR

a range of two IP addresses and a range of 500 different ports (or any matching combination), OR

a range of 1000 IP addresses and a single port.
When specifying the IP address, in the Start field, specify the first IP address in the required range. Then specify
the last IP address in the range in the End field.
Tip: If required, a range may include only one IP address (IPv4 example: 232.0.1.0-232.0.1.0)
Tip: IP addresses for multicasting must be within a special range set aside for dynamic host allocation by IANA
(the authority overseeing global IP address allocation). If using IPv4, you can read more about the range, which
goes from 232.0.1.0 to 232.255.255.255, at www.iana.org/assignments/multicast-addresses. If using IPv6, the
range is different; see www.iana.org/assignments/ipv6-multicast-addresses.
Manage Public Addresses
You define a recording server's public IP address on the Network tab. To access the Network tab, select the
required recording server in the Overview pane (see page 56), then select the Network tab in the Properties pane
(see page 56).
This description is also valid for failover servers, see page 222.
Why Use a Public Address?
When an access client, such as a Smart Client, connects to a surveillance system, an amount of initial data
communication, including the exchange of contact addresses goes on in the background. This happens
automatically, and is completely transparent to users.
Access clients may connect from the local network as well as from the internet, and in each case the surveillance
system should be able to provide suitable addresses so the clients can get access to live and recorded video from
the recording servers:

When access clients connect locally, the surveillance system should reply with local addresses and port
numbers. See also Manage Local IP Address Ranges on page 199.

When access clients connect from the internet, the surveillance system should reply with the recording
server's public address, i.e. the address of the firewall or NAT (Network Address Translation) router, and
often also a different port number (which is then forwarded to recording servers).
To provide access to the surveillance system from outside a NAT (Network Address Translation) firewall,
XProtect Corporate lets you use public addresses and port forwarding. This will allow access clients from
outside the firewall to connect to recording servers without using VPN (Virtual Private Network). Each
recording server (and failover server) can be mapped to a specific port and the port can be forwarded
through the firewall to the server's internal address.
See more about defining the public address in the following.
Enabling Public Access
To enable public access, select the Network tab's Enable public access box.
Defining Public Address and Port
When public access is enabled, you are able to define the recording server's public address and public port
number in the Public address and Public port fields respectively.
As public address, use the address of the firewall or NAT router which clients accessing the surveillance system
from the internet must go through in order to reach recording servers.
www.milestonesys.com
Page 86
Management Client
Management Client
Specifying a public port number is compulsory; it is always a good idea that port numbers used on the firewall or
NAT router are different from the ones used locally.
When using public access, the firewall or NAT router used must be configured so requests sent to the public
address and port are forwarded to the local address and port of relevant recording servers.
Local IP Ranges
There are cases when the recording server's public address should not be used: When access clients connect
from the local network, the surveillance system should reply with local addresses and port numbers. The
surveillance system must therefore be able to determine whether an access client belongs on a local IP range or
on the internet.
For this purpose, you are able to define a list of IP ranges which the surveillance system should recognize as
coming from a local network. You do this by clicking the Network tab's Configure... button. See Manage Local IP
Address Ranges (see page 199) for more information.
Manage Recording Servers
XProtect Corporate recording servers are used for recording video feeds, and for communicating with cameras
and other devices. An XProtect Corporate surveillance system will typically contain several recording servers,
although only a single recording server is required for the system to work.
Recording servers on your system— i.e. computers with the XProtect Corporate recording server software
installed, and configured to communicate with an XProtect Corporate management server— will be listed in the
Management Client's Overview pane (see page 56) when you expand the Servers folder in the Site Navigation
pane (see page 56) and then select the Recording Servers node. Site Navigation pane (see page 56)
Recording server listed in Overview pane
Backward compatibility with recording servers from
XProtect Corporate versions older than 3.0 is limited. You
can still access recordings on such older recording
servers; but in order for you to be able to change their
configuration, they must be of version 3.0 or later. It is thus
highly recommended that all recording servers in your
XProtect Corporate system are upgraded (see page 42) to
the latest possible version.
IMPORTANT: When the Recording Server service is running, it is very important that neither Windows Explorer
nor other programs are accessing Media Database files or folders associated with your XProtect Corporate
surveillance setup. Otherwise, the recording server might not be able to rename or move relevant media files.
Unfortunately, this might bring the recording server to a halt. If this situation has already occurred, stop the
Recording Server service, close the program accessing the media file(s) or folder(s) in question, and simply
restart the Recording Server service.
Authorizing a Recording Server
When first using the system, or when new recording servers have been added to the system, you must authorize
the new recording servers.
Why must I authorize recording servers? In an XProtect Corporate system, recording servers point to
management servers, not the other way round. In theory, recording servers which you do not want to include in
your surveillance system could thus be configured to connect to your management servers. By authorizing
recording servers before they can be used, surveillance system administrators have full control over which
recording servers are able to send information to which
management servers.
1.
Expand the Servers folder in the Management Client's Site
Navigation pane (see page 56) and select the Recording
Servers node.
www.milestonesys.com
Page 87
Management Client
Management Client
2.
Right-click the required recording server in the Overview pane (see page 56).
3.
From the menu that appears, select Authorize Recording Server:
After a short moment, the recording server will be authorized and ready for further configuration.
Viewing/Editing a Recording Server's Properties
When a recording server is authorized, you are able to view/edit the recording server's properties, including its
database storage area settings:
When you select the required recording server in the Management
Client's Overview pane (see page 56), the recording server's
properties are displayed in the Properties pane (see page 56).
Expand the required recording server to see which devices are
connected to the recording server. While the Management Client loads information about the recording server, the
text (... expanding) is displayed next to that recording server.
Adding Hardware (Cameras, etc.) to a Recording Server
You add IP hardware, such as cameras, video encoders, etc., to recording servers on your XProtect Corporate
system through the Detect Hardware wizard. The wizard helps you scan your network for relevant hardware. See
Detect Hardware on page 75 for more information.
Managing Hardware on a Recording Server
You have several options for managing IP hardware, such as cameras, video encoders, etc., on recording servers
on your XProtect Corporate system. See Manage IP Hardware on page 79.
Renaming a Recording Server
1.
Expand the Servers folder in the Management Client's Site Navigation pane (see page 56) and select the
Recording Servers node.
2.
Right-click the required recording server listed in the Overview pane (see page 56).
3.
From the menu that appears, select Rename Recording Server.
Tip: As an alternative to using the menu, press the F2 key on your keyboard.
4.
You are now able to overwrite the name of the recording server in the Overview pane (see page 56).
Removing a Recording Server
IMPORTANT: Removing a recording server will remove all configuration specified for the recording server
through the Management Client, including all of the recording server's associated hardware (cameras, input
devices, etc.).
1.
Expand the Servers folder in the Management Client's Site Navigation pane (see page 56) and select the
Recording Servers node.
2.
Right-click the no longer required recording server in the Overview pane (see page 56).
3.
From the menu that appears, select Remove Recording Server.
4.
You will be asked to confirm that you want to remove the recording server and all of its associated
hardware from the XProtect Corporate system. If you are sure, click Yes.
5.
The recording server and all of its associated hardware will be removed.
Replacing a Recording Server
If a recording server is malfunctioning and you want to replace it with a new server, while letting the new server
inherit the settings of the old, malfunctioning recording server, do the following:
www.milestonesys.com
Page 88
Management Client
Management Client
1.
2.
Retrieve the Recording Server ID from the old recording server;
a.
Open the Management Client.
b.
In the Management Client's Site Navigation pane (see page 56) select Recording Servers, then
in the Overview Pane (see page 56) select the required, old recording server.
c.
In the Management Client's Properties pane (see page 56), select the Storage tab.
d.
Press and hold down the CTRL key on your keyboard while selecting the Info tab.
e.
Copy the recording server ID found
in the lower part of the Info tab. Do
not copy ID = but only the ID itself.
f.
IMPORTANT: Stop the Recording
Server service (see page 232) on the old recording server, then in Windows' Services set the
service's Startup type to Disabled.
Replace recording server ID on the new recording server:
a.
Make sure that the Recording Server service is stopped (see page 232) and disabled on the old
recording server.
It is very important that you do not start two recording servers with identical IDs at the same
time.
b.
On the new recording server, open an explorer and go to C:\ProgramData\Milestone\XProtect
Corporate Recording Server or the path where your recording server is located.
c.
Open the file RecorderConfig.xml.
d.
Delete the ID stated in between the tags <id> and </id>.
e.
Paste the copied recording
server ID in between the tags
<id> and </id>. Save the
RecorderConfig.xml file.
f.
Restart the recording server service. When the new recording server service starts up, the
recording server has inherited all settings on the old recording server.
Tip: This procedure also applies if you re-install Windows on the computer running the recording server, even if
you do not replace the computer running the recording server.
Troubleshooting: Missing Recording Servers
If you have installed several recording servers on your surveillance system, the recording servers should
automatically be listed in the Management Client.
If your Management Client does not list all the recording
servers you have installed, the most likely reason is that the
missing recording servers have not been correctly configured to
connect to a management server (in an XProtect Corporate
system, recording servers point to management servers, not
the other way round).
The configuration normally takes place during one of the steps
in the recording server installation process.
Example from recording server installation: the XProtect Corporate
Management Server field specifies which management server the
recording server should connect to.
Show me which step...
During installation of the recording server, you specified
www.milestonesys.com
Page 89
Management Client
Management Client
recording server setup parameters, among these the IP address or host name of the management server to which
the recording server should be connected:
Fortunately, you do not have to re-install recording servers in order to specify which management servers they
should connect to. Once a recording server is installed, you can verify/change its basic configuration the following
way:
How to Verify/Change which Management Server a Recording Server Connects to
In order to verify/change a recording server's basic configuration, the recording server service must be stopped.
This means that recording and live viewing will not be possible while you verify/change the recording server's
basic configuration.
1.
On the computer running the recording server, right-click the recording
server icon in the notification area:
Tip: The notification area is occasionally also known as the system tray,
it is located at the far right of the recording server computer's Windows
taskbar.
2.
From the menu that appears, select Stop Recording Server Service:
3.
Right-click the notification area's recording server icon again.
4.
From the menu that appears, select Change Settings...:
The Recording Server Settings window appears. Verify/change
the following settings:

Management server hostname/IP address: Lets you
specify the IP address (example: 123.123.123.123) or
host name (example: ourserver) of the management
server to which the recording server should be connected. This information is necessary in
order for the recording server to be able to communicate with the management server.

Management server port: Lets you specify the port number to be used when communicating
with the management server. Default is port 9993, although you are able to change this if
required.
5.
Click OK.
6.
To start the recording server service again, right-click the notification
area's recording server icon, and select Start Recording Server
Service:
How to Read the Recording Server Icons
The following icons are used in the Management Client to indicate the state of individual recording servers:
Recording server is running
Recording server is communicating
Recording server requires attention: This icon will typically appear because the recording server
service has been stopped.
Tip: You can verify whether the recording server is stopped by looking at the recording server icon in the
notification area of the computer running the recording server. Right-clicking the recording server icon in
the notification area opens a menu with which you can start/stop the recording server service, view
recording server status messages, etc. See Recording Server Service Administration on page 231 for
more information.
Recording server must be authorized: Appears when the recording server is loaded for the first time.
When first using a recording server, you must authorize it:
1. Right-click the required recording server icon.
www.milestonesys.com
Page 90
Management Client
Management Client
2.
From the menu that appears, select Authorize Recording Server. After a short moment, the
recording server will be authorized and ready for further configuration.
Ongoing database repair: Appears when databases have become corrupted, and the recording server
is repairing them. The repair process may take considerable time if the databases are large.
IMPORTANT: During the database repair it is not possible to record video from cameras connected to
the recording server in question. Live video viewing will still be possible.
How can databases become corrupted? Databases typically become corrupted if the recording server
is shut down abruptly, for example due to a power failure or similar. See Protect Databases from
Corruption for useful information about how to avoid corrupt databases.
Storage Tab (Recording Server Properties)
On the Storage tab, you are able to setup, manage and
view storage areas for selected recording servers. For a
more general introduction to storing and archiving, see
About Storage and Archiving on page 70.
What is a storage area? A storage area is a directory in
which database content— primarily recordings from the
cameras connected to the recording server— is stored in
at least a recording database and possibly archived in a
number of archiving databases. A default storage area
with a default recording database is automatically
created for each recording server when the recording
server is installed on the system. Unless you specifically
define that another storage area should be used for
particular cameras, recordings from connected cameras
are stored in individual camera databases in the
recording server's default storage area. Archives can be
added to a storage area at any time convenient.
To access the Storage tab, select the required recording
server on the Overview pane (see page 56), then select
the Storage tab in the Properties pane (see page 56).
It is not possible to add databases or edit a storage area
if the recording server is offline.
Example of the contents of a Storage tab
Storage Tab's Elements
Storage configuration list contents:

Name: Indicates the name of the storage area. Click it to edit
it.

Device Usage: Indicates how many devises use the storage
area. Click the number link to see device details:

Default: Indicates the default storage area, i.e. the storage
area in which database content is automatically stored unless
you specifically define other storage areas for particular
cameras. Only one storage area at the time can be default.
Recording and archiving configuration list content:
Database name:
1.
Maximum size of the database (and usage;
also represented graphically by a proportional
filling of the database)
www.milestonesys.com
Page 91
Management Client
Management Client
2.
Database location
3.
Archiving schedule for archiving to the next archive in the list. Note that the number of retention days
stated for an archive includes all retention stated earlier in the process.
Tip: Pausing the mouse pointer over a database will show detailed database information.
Creating a New Storage
A storage area is always created with at predefined recording database named Recording, which cannot be
renamed. Besides a recording database, a storage area can contain a number of archives, see Creating an
Archive within an Existing Storage section later in this topic.
1.
To add an extra storage area to a selected recording server, click the
Storage area configuration list.
button located below the
2.
This opens the Storage and Recording Settings dialog where you must specify the following:

Name: Rename the storage area if needed; use a descriptive and unique name.

Path: Type or use the browser link next to the field to specify the path to the directory in which
to save the storage area. The storage area does not necessarily have to be located on the
recording server computer itself.
Tip: If the directory you plan to use does not already exist, you can create it using the browser
dialog. Network drives must be specified using UNC (Universal Naming Convention) format,
example: \\server\volume\directory\.

Retention time: Select a number of units and select either Days or Hours to specify how long
recordings should stay in the recording database before being deleted or archived (depending
on archive settings). This is useful if you do not want your most recent recordings to be
archived (or deleted) straight away even though archiving may be scheduled to take place
before the specified number of hours.
Who determines the schedule? You do. You must specify the intervals with which the
archiving process will start.
Example: If you specify 24 hours, recordings must be at least a day old before they
will be archived. If archiving is scheduled to take place before the 24 hours have
passed, only recordings older than 24 hours will be archived. Bear in mind that the
archive's scheduling may mean that recordings will be older than the specified number
of hours before they are archived. This may especially be the case if you specify an
archiving schedule with long time spans between archiving.
Archiving is set up by adjusting several interdependent settings, see About Storage and
Archiving on page 70 for more information.
3.
Maximum size: Select the maximum number of gigabytes of recording data to save in the
recording database.
Example: If you want to store up to 100 gigabytes of recording data in the database,
select 100. Recording data in excess of the specified number of gigabytes will be automoved to the first archive in the list—if any is specified—or deleted.
IMPORTANT: This is one of two maximum size settings for the recording database. The
Retention Time setting specified earlier may mean that recordings are removed from the
recording database before the specified number of gigabytes is reached.
IMPORTANT: The oldest data in a database will always be auto-archived (or deleted if no next
archive is defined) when less than 5GB of space is free. If less than 1GB space is free, data will
be deleted. A database always requires 250MB of free space. If this limit is reached (if data is
not deleted fast enough), no more data will be written to the database until enough space has
been freed. The actual maximum size of your database will thus be the amount of gigabytes
you specify, minus 5GB.
4.
Encryption: Select the appropriate level of encryption for the recording database by selecting
either None, Light or Strong.
www.milestonesys.com
Page 92
Management Client
Management Client
Note that the stronger the encryption, the more CPU usage it will cause.
5.
6.
Password (mandatory only if you selected Light or Strong in the Encryption field mentioned
earlier): Click Set... to set a password.
Click OK.
If needed, you are now ready to create archive(s) within your new storage, see Creating an Archive within an
Existing Storage next.
Creating an Archive within an Existing Storage
A storage area has no default archive when it is created.
1.
To create an archive, select the wanted storage by clicking it in the Recording and archiving
configuration list.
2.
Next, click the
3.
This opens the Archive Settings dialog where you must specify the following:
button located below the Recording and archiving configuration list.

Name: Rename if needed; use a descriptive and unique name.

Path: Type or use the browser link next to the field to specify the path to the directory in which
to save the archive. The archive does not necessarily have to be located on the recording
server computer itself.
Tip: If the directory you plan to use does not already exist, you can create it using the browser
dialog. Network drives must be specified using UNC (Universal Naming Convention) format,
example: \\server\volume\directory\.

Retention time: Select a number of units and select either Days or Hours to specify how long
recordings should stay in the archive before being moved to another archive or deleted
(depending on archive settings). The retention time must always be longer than the retention
time of the last archive or the recording database. This is due to the fact that the number of
retention days stated for an archive includes all retention stated earlier in the process.
Who determines the schedule? You do. You must specify the intervals with which the
archiving process will start.
Example: If you specify 24 hours, recordings must be at least a day old before they
will be archived. If archiving is scheduled to take place before the 24 hours have
passed, only recordings older than 24 hours will be archived. Bear in mind that the
archive's scheduling may mean that recordings will be older than the specified number
of hours before they are archived. This may especially be the case if you specify an
archiving schedule with long time spans between archiving.
Archiving is set up by adjusting several interdependent settings, see About Storage and
Archiving on page 70 for more information.

Maximum size: Select the maximum number of gigabytes of recording data to save in the
archive.
Example: If you want to store up to 100 gigabytes of recording data in the archive,
select 100. Recording data in excess of the specified number of gigabytes will be automoved to the next archive in the list—if any is specified—or deleted.
IMPORTANT: This is one of two maximum size settings for the storage area. The Retention
Time setting specified earlier may mean that recordings are removed from the archive before
the specified number of gigabytes is reached.
IMPORTANT: The oldest data in a database will always be auto-archived (or deleted if no next
archive is defined) when less than 5GB of space is free. If less than 1GB space is free, data will
be deleted. A database always requires 250MB of free space. If this limit is reached (if data is
not deleted fast enough), no more data will be written to the database until enough space has
been freed. The actual maximum size of your database will thus be the amount of gigabytes
you specify, minus 5GB.
www.milestonesys.com
Page 93
Management Client
Management Client

Schedule: Click the schedule icon next to the Schedule field to specify an archiving schedule,
i.e. the intervals with which the archiving process should start. If required you are able to make
archiving take place very frequently (in principle every minute all year round), or very
infrequently (for example, every first Monday of every 36 months).
What is the ideal interval? The ideal interval to use between each archiving process depends
entirely upon your organization's needs. Consider your system's recording settings, make an
estimate of the amount of data you expect to record within, for example, a day, a week, or a
month, then decide on a suitable interval. Bear in mind that your organization's needs may
change over time; it is thus a good idea to regularly monitor your archiving settings, and adjust
them if required.
In the following example, we have selected that archiving should take place twice every week:
at three o'clock in the morning on Wednesdays and Sundays. Note that regional settings on
your computer may mean that dates and times appear differently in your version of XProtect
Corporate.
Tip: The effect of your
selections is summed up in
the lower part of the dialog.
Use the summary to verify
that your selections reflect
your intentions.
Tip: If required, you can
always adjust the archive's
settings—including its
scheduling—once the
archive has been created.

Reduce frame rate: Select
the Reduce frame rate
check box and set a frame
per second (FPS) in order to
reduce FPS when archiving.
Reducing frame rates by a
selected number of FPS's
will make your recordings take up less space in the archive. On the other hand, it also reduces
quality since a number of frames are erased, leaving only FPS corresponding to the number of
FPS selected in the dialog. MPEG/H.264 will be reduced to minimum key-frames.
Tip: It is possible to reduce frame rates to less than 1 FPS, for example as low as 0.1 FPS
which means 1 frame every 10 seconds.
4. Click OK.
Deleting an Archive from within an Existing Storage
1. To delete an archive, select the wanted archive from the Recording and archiving configuration list by
clicking it. A selected archive is marked by a dark frame.
It is only possible to delete the last archive in the list. The archive does not have to empty.
2. Click the
button located below the Recording and archiving configuration list.
3. Click Yes.
Deleting an Entire Storage
Prerequisites
The storage area you want to delete must not be set as default storage area. Furthermore, it cannot be used by
any devices to hold recordings. This means that you must possibly move devices and their not yet archived
recordings to another storage area before you are allowed to delete the storage area, see Moving Non-archived
Recordings from One Storage Area to Another section later in this topic.
www.milestonesys.com
Page 94
Management Client
Management Client
To Delete an Entire Storage
1. To delete a storage area, select the wanted
storage by clicking it.
2. Click the
button located below the
Storage configuration list.
3. Click Yes.
Editing Settings for a Selected Storage or Archive
1. In the Recording and archiving configuration list, to edit a storage area, select its recording database. To
edit an archive, select the archive database.
Tip: A selected database is marked by a dark frame.
2. Click the
button located below the Recording and archiving configuration list.
3. For editing a recording database, see Creating a New Storage section and for editing an archive, see
Creating a New Archive within an Existing Storage section—both described earlier in this topic.
If you change the maximum size of a database, recordings that exceed the new limit are auto-archived to the next
archive or deleted—depending on archiving settings.
Moving Non-archived Recordings from One Storage Area to Another
Moving of contents from one recording database to another is done from the Record tab of the device in question.
1. In the Management Client's Site Navigation pane (see page 56), expand Devices, select the wanted
device type. In the Overview pane (see page 56), select the wanted device.
2. In the Properties pane (see page 56), click the Record tab. In the upper part of the Storage area, click
Select....
3. In the Select Storage dialog that follows, select the wanted database.
4. Click OK.
5. In the Recordings Action dialog that follows, select whether already existing—but non-archived—
recordings should be moved along to the new storage or deleted.
6. After selecting, click OK.
See also Record Tab Overview on page 128.
About Upgrading
If your system is upgraded to XProtect Corporate 4.0 (or future versions), you might experience that you end up
with a lot more storages than before upgrade. This is due to the fact that from XProtect Corporate 4.0 and
forwards, database structure is somewhat different than it used to be and during the update process, the system
creates a number of extra databases. However, since your original naming-convention is respected, you are able
to reconstruct your former database structure with only little moving about of devices and deletion of obsolete
storages or databases.
Servers and Clients Require Time-Synchronization
Part of the security surrounding the use of remote access clients with XProtect Corporate is based on so-called
time-based tokens.
www.milestonesys.com
Page 95
Management Client
Management Client
Why Servers Require Time-Synchronization
When a client logs in to the surveillance system, the client receives a token from the management server. The
token contains important security-related time information.
The management server also sends a similar token to the required recording server(s). This is partly due to the
fact that recording servers may be located all around the world; each recording server thus uses the token to
validate the client's token against the local time in the recording server's own time zone.
The validity of a token expires after a while. It is therefore important that time on your management server and all
of your organization's recording servers is synchronized (minute and second-wise; hours may of course be
different in different locations around the world). If time on the servers is not synchronized, you may experience
that a recording server is ahead of the management server's time.
When a recording server is ahead of the management server's time, it may result in a client's token expiring on
the recording server earlier than intended by the management server. Under unfortunate circumstances you might
even experience that a recording server claims that a client's token has already expired when it receives it;
effectively preventing the client from viewing recordings from the recording server.
How to synchronize time on your organization's servers depends on your network configuration, internet access,
use of domain controllers, etc. Often, servers on a domain are already time-synchronized against the domain
controller. If so, you should be fine as long as all required servers belong to the domain in question.
If your servers are not already time-synchronized, it will be necessary to synchronize the servers' time against a
time server, preferably the same time server.
The following articles from Microsoft describe what to do in different situations:

How to configure an authoritative time server in Windows Server 2003:
http://support.microsoft.com/kb/816042/en-us

Registry entries for the W32Time service:
http://support.microsoft.com/kb/223184/en-us
If these links do not work for you, try searching www.microsoft.com for time server, time service, synchronize
servers or similar.
It is also very important that Smart Clients are time-synchronized with the management server (see the following
section).
Why Clients Require Time-synchronization
Because configuration communication is facilitated by the service channel (see page 231), it is advantageous that
Smart Clients are also time-synchronized with the management server and the computer running the Service
Channel service. A time difference of five minutes between Smart Client and servers is tolerated.
If a Smart Client is not time-synchronized with the management server and the computer running the Service
Channel service, the Smart Client is not updated with information about configuration changes made by other
users in the Smart Client’s Setup tab. This means that users risk overwriting each other’s configuration changes.
Devices
360 Degree Lens Tab
Use of 360° technology requires a
dedicated ImmerVision 360° lens
mounted.
In this way, 360° technology
enables a.o.t. panomorph
technology through an advanced
www.milestonesys.com
Page 96
Management Client
Management Client
lens.
The 360° Lens tab lets you enable and configure panomorph support for the selected camera.
Enabling and Disabling Panomorph Support
The panomorph feature is disabled by default. To enable/disable it, select/clear the 360° Lens tab's Enable
panomorph support check box.
Panomorph Settings
When enabling the panomorph support functionality, you must also select a Registered Panomorph Lens (RPL)
number from the ImmerVision Enables® panomorph RPL number list. This is to ensure identification and correct
configuration of the lens used with the camera in question. The LPR number is usually found on the lens itself or
on the box it came in. For details of ImmerVison, panomorph lenses, and RPLs, see
http://www.immervision.com/en/home/index.php.
You must also indicate the physical position/orientation of the camera in question. This is done by selecting its
position from the Camera position/orientation list.
About Device Groups
You are able to group different types of devices (cameras, microphones, speakers, inputs, outputs) on your
XProtect Corporate system by using device groups. The use of device groups has several benefits:

Device groups help you maintain an intuitive overview of devices on your system

You are able to specify common properties for all devices within a device group in one go

When dealing with roles (see page 164), you are able to specify common security settings for all devices
within a device group in one go

When dealing with rules (see page 155), you are able to apply a rule for all devices within a device group
in one go
You can add as many device groups as required; you are completely free to decide which devices to include. The
only restriction is that you cannot mix different types of devices (for example cameras and speakers) in a device
group.
Example: cameras grouped into device groups
If a device group contains 400 devices or more, the Settings tab is
unavailable for viewing and editing. For camera groups, the Streams
tab is also unavailable for editing and viewing if the group contains
400 cameras or more. When you click the plus sign next to the device
folder, your XProtect Corporate system will load the contents of the
device folder, which may take a few seconds. While expanding, the
text (expanding...) is displayed next to the folder name.
The following examples are based on grouping cameras into device groups, but the principle applies for
microphones, speakers, inputs and outputs as well.
Adding a Device Group
1.
In the Overview pane (see page 56), right-click the
item under which you wish to create the new device
group.
2.
Select Add Device Group:
Tip: You may also simply press CTRL+N on your
keyboard.
www.milestonesys.com
Page 97
Management Client
Management Client
The Add Device Group dialog will appear.
3.
In the Add Device Group dialog, specify a name and description of the new device group:
The description will later appear when pausing the mouse pointer over the device group in the device
list.
4.
Click OK. A folder representing the new device group is added
to the list. You are now able to specify which devices should
belong in the device group.
Tip: If required, you are able to add
device groups as subgroups under
other device groups, as illustrated in the following example:
Specifying Which Devices to Include in a Device Group
1.
In the Overview pane's (see page 56) device list, right-click the required device group folder.
2.
Select Edit Device Group Members. The Select Group Members window will appear.
3.
In the Select Group Members window, select either ...:

The Device Groups tab, which lists devices based on existing device groups.
Tip: A device can be a member of more than one device group.

4.
The Recording Servers tab, which lists devices based on which recording servers the devices
belong on.
Select the devices you wish to
include, and click the Add
button. This will copy the
selected devices to the
Selected box:
Tip: You may also double-click
a device to copy it from one
box to the other, or you may
simply drag devices between
the two boxes.
Tip: To select several devices
in one go, press the CTRL key
on your keyboard while
selecting.
5.
Click OK. The selected devices
will be added to your device
group on the device list.
Specifying Common Settings for All Devices in a Device Group
When using device groups, you are able to quickly specify common properties for all devices within a given
device group:
1.
In the Overview pane's (see page 56) device list, click the required device group.
In the Properties pane (see page 56), all properties which are available on all of the device group's
devices will be listed, grouped on tabs.
2.
Specify the required common properties.
www.milestonesys.com
Page 98
Management Client
Management Client
Properties not available on all of the devices in the device group will not be listed; such properties must
still be configured individually for each device.
If the device group contains 400 or more devices the Settings tab is unavailable for viewing and editing.
For camera groups the Streams tab is also unavailable for viewing and editing if the group contains 400
cameras or more.
Tip: The Settings tab has convenient functionality for quickly switching between settings for the device
group and settings for individual devices.
Deleting a Device Group
1.
In the Overview pane's (see page 56) device list, right-click the unwanted device group folder.
2.
Select Delete Group.
Tip: You may also simply press DELETE on your keyboard.
3.
You will be asked to confirm that you want to delete the device group. Verify that you are deleting the
correct device group, then click Yes.
Remember that you have only deleted the device group itself. If you wish to delete IP hardware—such as a
camera—from your XProtect Corporate system, do so on a recording server level (see Managing Hardware on
page 79).
About Devices
In the Management Client's Site Navigation pane (see page 56), you are able to work with the following under
Devices:

Cameras: Lets you handle the majority of camera configuration and management. See Manage
Cameras on page 106 for more information.

Microphones: On many devices you are able to attach external microphones; some devices even have
built-in microphones. See Manage Microphones on page 110 for more information.

Speakers: On many devices you are able to attach external loudspeakers; some devices even have
built-in speakers. See Manage Speakers on page 115 for more information.

Inputs: On many devices you are able to attach external units, typically external sensors, to input ports
on the device. Input from such external input units can be used for many purposes in XProtect
Corporate. See Manage Inputs on page 107 for more information.

Outputs: On many devices you are able to attach external units to output ports on the device. This
allows you to activate/deactivate lights, sirens, etc. through XProtect Corporate. See Manage Outputs on
page 113 for more information.
Client Tab (Camera
Properties)
The Client tab lets you specify information
which will affect access clients' use of the
selected camera. To access the Client tab,
select the required camera in the Overview
pane (see page 56), then select the Client tab
in the Properties pane (see page 56).
Due to the limited feature set of the Remote
Client (see page18), settings on the Client tab
will only affect Smart Client’s (see page 16)
use.
www.milestonesys.com
Page 99
Management Client
Management Client
Client Settings

Live multicast: XProtect Corporate supports multicasting (sending of single data packets to multiple
recipients within a group, thereby saving bandwidth and system resources, see page 84) of live streams
from recording servers to Smart Clients (see page 16). To enable multicasting of live streams from the
selected camera, select the check box.
Remember that for the feature to work, multicasting must also be configured for the recording server;
see Manage Multicasting on page 83. If multicasting is not possible, for example due to restrictions on
the network or on individual clients, XProtect Corporate will revert to unicasting (sending of separate
data packets to separates recipients).

Default microphone: By defining a default microphone, you can determine from which microphone
Smart Client users should by default hear recordings when they select the camera in question in their
Smart Clients. The users can subsequently select another microphone if they require so.
Bear in mind that although you have defined a default microphone for a camera, it cannot be guaranteed
that all Smart Client users will hear audio from the microphone in question: Some users may not have
speakers attached, some users may not have the rights required to listen to audio, etc.

Default Speaker: By defining a default speaker, you can determine through which microphone Smart
Client users should by default be able to speak when they select the camera in question in their Smart
Clients. The users can subsequently select another speaker if they require so.
Bear in mind that although you have defined a default speaker for a camera, it cannot be guaranteed
that all Smart Client users will be able to talk through the speaker in question: Some users may not have
a microphone attached, some users may not have the rights required to talk through speakers, etc.

Shortcut: Users of the Smart Client can take advantage of a range of keyboard shortcuts, some of
which let the users toggle between viewing different cameras. Such shortcuts include numbers, which
are used to identify each camera. In the Management Client, each camera's shortcut number is specified
in the Shortcut field.
A camera shortcut number must not contain any letters or special characters, and cannot be longer than
four digits. Examples of correct camera shortcut numbers: 3, 1234. Examples of incorrect camera
shortcut numbers: A*3, 12345. Always use a unique camera shortcut number for each camera.
Tip: Find more information about audio and keyboard shortcuts from a Smart Client user's perspective in the
separate Smart Client documentation available on the XProtect Corporate software CD as well as from
www.milestonesys.com .
Define Input- and Output-Related Rules
To be able to automatically

activate an output or trigger an event activated by an output, you must, after you have enabled an
output,

trigger an action activated by an input, you must, after you have enabled the input and created an event
based on the input,
include it in a rule.
See Manage Output on page 113 or Manage Input on page 107 for more information.
For example, you may create a rule specifying that:

a siren should sound if motion is detected on a particular camera, or you may create a rule specifying
that a camera should start recording if a siren sounds (output).

a camera should record if a particular input is activated (input).
For the following examples to be useful you should have general knowledge about rules (see page 155). See also
Create Typical Rules on page 147 for other step-by-step descriptions of how to create rules.
www.milestonesys.com
Page 100
Management Client
Management Client
Tip: When you create a rule based on an in- or output event, the actions you specify in the rule do not have to
relate to the device on which the external in- or output was activated; you can easily specify that the actions
should take place on one or more different devices— even across recording servers.
Defining a Rule that Activates/Deactivates an Output
1.
Start the Manage Rule and in step 1 select a rule type and, if necessary, a condition in step 2.
2.
In Manage Rule's step 3 (Step 3: Actions) select the Set device output to <state> action.
3.
If you like the output to be activated/deactivated immediately, skip this step. If you do not want to activate
or deactivate the output immediately after the event, click the immediately link in the initial rule
description, and select an interval between the event and the activation/deactivation of the output. Click
OK to confirm your selection.
4.
Click the state link in the initial rule description, and select whether you want to activate or deactivate the
output. Click OK to confirm your selection.
5.
Click the devices link in the initial rule description, and select which output you want to activate or
deactivate. Click OK to confirm your selection.
6.
If wanted you can select more actions in the Manage Rule's step 3 (Step 3: Actions). Do so or simply
click Next to continue to the next step.
7.
In Manage Rule's step 4 (Step 4: Stop criteria) select one of the stop actions, for instance to deactivate
the output after a certain time or event.
8.
Click Finish to save the rule.
Defining a Rule where an Output Triggers an Action
In the Rules feature, all registered external output (activation, deactivation or change) is treated as an event.
Based on an event, you are able to specify a wide variety of actions to take.
To define a rule where an output activates an action, do the following:
1.
Start the Manage Rule.
2.
In Manage Rule's step 1 (Step 1: Type of rule) select the Perform an action on <event > option.
3.
Click the event link in the initial rule description.
4.
In the Select an Event dialog's Built-in group, select the appropriate option for your rule: Output
Activated, Output Changed or Output Deactivated. Click OK to confirm your selection.
5.
Click the devices/recorders/servers link in the initial rule description.
6.
In the Select Devices and Groups dialog select the required output. Click OK to confirm your selection.
7.
Click Next to continue to the Manage Rule's step 2 (Step 2: Conditions) and select, if necessary, a
condition.
8.
Continue to step 3 (Step 3: Actions) and select one or more actions.
9.
If you do not want to define a stop action, skip this step. If you want to define a stop action— for instance
to deactivate the output again— click Next to continue to step 4 (Step 4: Stop criteria), and select a stop
action.
10. Click Finish to save the rule.
www.milestonesys.com
Page 101
Management Client
Management Client
Defining a Rule where an Input Triggers an Action
In the Rules feature, all registered external input (activation, deactivation, or change) is treated as an event.
Based on an event, you are able to specify a wide variety of actions to take.
To define a rule specifying that an input should result in one or more actions (for example the starting of recording
on a certain camera), do the following:
1.
Start Managing Rules.
2.
In Managing Rules' step 1 (Step 1: Type of rule) select the Perform an action on <event > option.
3.
Click the event link in the initial rule description.
4.
In the Select an Event dialog's Hardware Configurable group, select the appropriate option for your rule:
Input Activated, Input Changed, or Input Deactivated. Click OK to confirm your selection.
5.
Click the devices/recording servers/management servers’ link in the initial rule description.
6.
In the Select Devices and Groups dialog select the required input. Click OK to confirm your selection.
7.
Click Next to continue to Managing Rules' step 2 (Step 2: Conditions) and select, if necessary, a
condition.
8.
Continue to step 3 (Step 3: Actions) and select one or more actions.
9.
Click Next to continue to step 4 (Step 4: Stop criteria), and select a stop criteria. Click Next to continue to
step 5 (Step 5: Stop actions), and select a stop action.
10. Click Finish to save the rule.
Events Tab Overview
For items (cameras or microphones) supporting
events, you are able to manage the hardware
configurable events on the Events tab. To access the
Events tab, select the required item in the Overview
pane (see page 56), then select the Events tab in the
Properties pane (see page 56).
The Events tab will only be available if the selected
item supports hardware configurable events.
Event tab, example from camera
Even when an item supports hardware configurable
events, it is always your decision whether you want to
use such events on your XProtect Corporate system.
Therefore, you simply add each hardware
configurable event you want to be able to use on each
item.
About the Event Tab for:
Camera
In addition to XProtect Corporate’s motion detection, some cameras can themselves be configured to detect
motion. If a camera is capable of such detection, the camera's detections can be used as events. Such events
can in turn be used when creating event-based rules (see page 148). Events from cameras are called hardware
configurable events as they technically occur on the actual camera hardware rather than on the surveillance
system.
www.milestonesys.com
Page 102
Management Client
Management Client
Even though events based on signals from input and/or output units connected to camera devices are technically
also hardware configurable events, they are managed elsewhere. See Manage Inputs on page 107 and Manage
Output on page 113.
Microphone
Some devices are capable of creating events themselves. Such events can in be used when creating eventbased rules (see page 148) in XProtect Corporate. Events from such devices are called hardware configurable
events, as they technically occur on the actual camera hardware rather than on the surveillance system.
Adding a Hardware Configurable Event
1.
On the Events Tab, click Add.... This opens the Select Driver Event window.
2.
Select the required hardware configurable event:
You can only select one hardware configurable event at a time.
3.
Click OK. The selected event will be added to the Events tab's list of
configured events.
4.
In the toolbar (see page 55), click Save.
Using Several Instances of a Hardware Configurable Event
To be able to specify different properties for different instances of an event, you are able to add a hardware
configurable event more than once (see also Specifying Hardware Configurable Event Properties described
earlier).
The following example is specific to cameras.
Example: The camera in question has been configured with two motion windows, called A1, and A2.
You have added two instances of the Motion Started (HW) event. In the properties of one instance, you
have specified use of motion window A1; in the properties of the other instance, you have specified use
of motion window A2.
When you use the hardware configurable event in a rule, you
are able to specify that the event should be based on motion
detected in a specific motion window in order for the rule to be
triggered:
Example: Specifying specific motion window as part of a rule's conditions
Deleting a Hardware Configurable Event
Bear in mind that deleting a hardware configurable event will affect any rules in which the event is used.

In the Events tab's Configured Events list, select the no longer required event.
Tip: If there are several instances of the same event, use the properties list in the right side of the tab to
verify that you have selected the correct event.

Click Delete.
The selected event will be deleted without further warning.

In the toolbar (see page 55), click Save.
How to Specify Hardware Configurable Event Properties
For each hardware configurable event you have added, you are able to specify properties. The number of
properties depends on the item in question. In order to work as intended, some or all of the properties must be
specified identically on the item as well as on XProtect Corporate.
Even though the following list is not exhaustive, you may often be able to specify the following properties:
www.milestonesys.com
Page 103
Management Client
Management Client

Enabled: Determines whether use of the hardware configurable event is enabled. Select True to enable;
select False to disable.
Enabled is the only property you will always see for microphones.

Include Images: Determines whether video should be sent from the camera to XProtect Corporate
when the event occurs. Select True if video is required; select False if video is not required.

Motion Window: Many cameras capable of detecting motion can be configured with different motion
detection settings for different parts the camera's images. For example, if a camera covers a 2-lane road,
different motion detection settings may have been defined for the right lane and left lane area of the
camera's images. Such areas are generally known as motion windows.
Provided one or more motion windows have been defined on the camera device, the Motion Window
setting lets you specify which motion window to use for the event. When the camera detects motion
within the specified motion window, the event will occur.
When specifying use of a motion window, make sure you type the name of the motion window, exactly
as it has been specified on the camera.
You can only specify one motion window in the field. However, you are able to add more than one
instance of an event; see Using Several Instances in the following for more information.
Fisheye Tab (Camera Properties)
Use of the fisheye technology requires a dedicated fisheye camera.
The Fisheye tab lets you configure the fisheye functionality of a
camera. Fisheye is a technology that allows viewing of 360°
panoramic images through an advanced lens.
Configuration
If the camera is mounted on a ceiling, you can adjust the behavior
of the navigation buttons to reflect this by selecting the Ceiling
mount check box.
The camera's fisheye functionality is configured by adjusting its fisheye view field, indicated by a green ellipse in
the preview image, so it encloses the actual image area of the fisheye lens. Press the Auto Calculate button to do
this automatically.
It is also possible to adjust the fisheye view manually. You do this by specifying a number of values which will be
used by the fisheye technology for converting the elliptic image into an ordinary rectangular image.
You can set the ellipse's X-radius, Y-radius, X-center, and Y-center by using the arrow buttons to adjust the
ellipse.
Preview
In the preview section of the Fisheye tab you can set a particular position in the fisheye-rendered view as the
camera's home position: Navigate to the required position, using the navigation buttons, then click the Set as
Home Position button.
www.milestonesys.com
Page 104
Management Client
Management Client
The navigation buttons let you move the camera as follows:
up and to the left
up
up and to the right
to the left
Moves the view
to its default position
to the right
down and to the left
down
down and to the right
Zooms in (one zoom level per click)
Zooms out (one zoom level per click)
Info Tab Overview
The Info tab lets you view and edit basic information about a
selected item in a number of fields. The following items have
an Info tab:

Cameras (see page 106)

Hardware (see page 79)

Microphones (see page 110)

Speakers (see page 115).
Example of Info tab from a camera...
Description of Info Tab's Fields

Name: Name of the item. Not compulsory, but highly recommended. Used whenever the item is listed in
XProtect Corporate and access clients. Does not have to be unique.
To change the name, overwrite the existing name and click Save in the toolbar (see page 55).
Tip: If you change the name, it will be updated throughout XProtect Corporate. This means that if the
name is used in, for example, a rule, the name will automatically change in the rule as well.

Description: Description of the item. Not compulsory. Will appear in a number of listings within XProtect
Corporate. For example, the description will appear when pausing the mouse pointer over the item's
name in the Overview pane (see page 56):
Example from a camera...
To specify a description, type the description and click
Save in the toolbar (see page 55).

Hardware name: (only relevant for Camera, Microphone and Speaker) Name of the hardware, with
which the item is connected. The field is non-editable from here, but can be changed by clicking the Go
To button next to it. This will take you to hardware information, where the name is editable.
www.milestonesys.com
Page 105
Management Client
Management Client

Unit number: (only relevant for Camera, Microphone and Speaker) Non-editable field displaying the unit
on which the item is attached on the hardware.
For single-device hardware, the unit number will typically be 1. For multi-device hardware, such as video
servers with several channels, the unit number will typically indicate the channel on which the item is
attached, e.g. 3.

Shortcut: (only relevant for Camera) Users of the Smart Client can take advantage of a range of
keyboard shortcuts, some of which let the user toggle between viewing different cameras. Such
shortcuts include numbers used to identify each camera. In the Management Client, each camera's
shortcut number is specified in the Shortcut field.
A camera shortcut number cannot contain letters or special characters, and must be no longer than four
digits.
Examples of correct camera shortcut numbers: 3, 1234.
Examples of incorrect camera shortcut numbers: A*3, 12345.
It is highly recommended that you use a unique camera shortcut number for each camera.
Tip: Find more information about keyboard shortcuts from a Smart Client user's perspective in the
separate Smart Client documentation available on the XProtect Corporate software CD as well as from
www.milestonesys.com

Serial Number: (only relevant for Hardware) Hardware serial number as specified by the manufacturer.
The serial number is often, but not always, identical to the MAC address.

Firmware version: (only relevant for Hardware) Firmware version as specified by the manufacturer.

MAC address: (only relevant for Hardware) Hardware MAC address. A MAC (Media Access Control)
address is a 12-character hexadecimal number uniquely identifying each device on a network.

Product ID: (only relevant for Hardware) Product identifier.

Hardware host name: (only relevant for Hardware) Host name or IP address of the hardware.
Tip: By clicking the
button next to the field, you are able to connect to the hardware's own
configuration page. The page opens in a separate window.
Manage Cameras
Enabling/disabling as well as renaming of individual cameras
takes place on the recording server hardware management level;
see Managing Hardware on page 79.
For all other configuration and management of cameras, expand
Devices in the Management Client's Site Navigation pane (see
page 56), then select Cameras. In the Overview pane (see page
56), you group your cameras for an easy overview of your
cameras. Grouping also lets you specify common properties for
all cameras within a group in one go. See Using Device Groups
on page 97 for information about creating groups as well as
adding cameras to your groups.
Device groups are used for grouping cameras
Once you have placed your cameras in groups, configuration can
begin:
www.milestonesys.com
Page 106
Management Client
Management Client
Configuring Individual Cameras
You configure individual cameras by selecting the required camera in the list, then specifying the camera's
required settings on the tabs in the Properties pane (see page 56):

The Info tab (see page 105) for managing the selected camera's name, etc.

The Settings tab (see page 131) for managing the selected camera's general settings.

The Streams tab (see page 112) for managing the selected camera's video streams.

The Record tab (see page 128105) for managing the selected camera's recording, database and
archiving storage settings.

The Presets tab (see page 124) for managing the selected camera's preset positions (only available if
the selected camera is a PTZ camera).

The Patrolling tab (see page 122) for managing the selected camera's patrolling profiles (only available if
the selected camera is a PTZ camera).

The Events tab (see page 102) for managing hardware configurable events.

The Client tab (see page 99) lets you specify information which will affect access client's use of the
selected camera.

The Privacy Mask tab (see page 120) lets you enable and configure privacy masking for the selected
camera.

The Motion tab (see page 116) for managing the selected camera's motion detection settings.
Read the Camera List's Status Icons on page 133
Manage Input
On many devices you are able to attach external units to input ports on the device. Input units are typically
external sensors. Such external sensors may, for example, be used for detecting if doors, windows, or gates are
opened. Input from such external input units is treated as events by XProtect Corporate.
Such events can be used in rules (see page 155). For example, you could create a rule specifying that a camera
should begin recording when an input is activated, and stop recording 30 seconds after the input is deactivated.
Devices' input ports are automatically detected when you add the devices to your XProtect Corporate system
through the Management Client's Detect Hardware wizard (see page 75), regardless of which of the wizard's
detection options you use.
You have two entry points for managing input:

In the Management Client's Site Navigation pane (see page 56), expand Devices, select Inputs, expand
the required device group, and select the required input. If no device groups are available, you must first
group your input: See About Device Groups on page 97 for information about creating groups as well as
adding input to your groups.

In the Management Client's Site Navigation pane (see page 56), expand Servers and select the
Recording Server node, then expand the required recording server in the Overview pane (see page 56)
and select the required input.
Before you specify use of external input and output units on a device, verify that sensor operation is recognized
by the device. Most devices are capable of showing this in their configuration interfaces, or via CGI script
commands. Also check the XProtect Corporate release notes to verify that input- and output-controlled operations
are supported for the devices and firmware used.
www.milestonesys.com
Page 107
Management Client
Management Client
Enabling Input
When inputs are detected with the Detect Hardware process (see page 75) process, they are by default disabled.
You can activate inputs when needed. If a device has several inputs you can enable one, some, or all of them as
required.
1.
In the Site Navigation pane (see page 56), expand Servers and select Recording Servers.
2.
In the Overview pane (see page 56) expand the relevant recording server, and find the device on which
the input is placed.
3.
Right-click the required input, and select Enabled.
Specifying Input Properties
Each input typically has several properties. You can access these properties in two ways:

In the Management Client's Site Navigation pane (see page 56), expand Devices, and select Inputs. In
the Overview pane (see page 56) expand the required inputs folder and select the required input.
- or -

In the Overview pane (see page 56), select a device group to define settings for all inputs in the group,
or expand a device group, and select the required input.
The properties of the selected input, or the common properties for all inputs in a selected device group, will be
displayed on the following tabs: Settings, Info, and Events.
See How to... in the following to learn more about the properties of the selected input, or the common properties
for all inputs in a selected device group.
Viewing the Current State of an Input
The change of an input's state is regarded as an event by XProtect Corporate. Events can be used in rules and
hereby trigger actions when the state of an input is changed.
See Define Input- and Output-Related Rules on page 100 for more information about how to include an input
event in a rule.
To view the current state of an input in the Management Client, do the following:
1.
In the Site Navigation pane (see page 56), expand Devices, and select Inputs.
2.
In the Overview pane (see page 56), expand the required inputs folder and select the required input.
Tip: You may select a group of inputs to view the current status of all inputs in the group.
3.
Information about the current status of the selected input is presented in the preview pane.
When an
input is
deactivated, it
is shown by a
gray indicator:
When the input
is activated, the
indicator lights
up green:
How to Fill in Properties on the Info Tab
Lets you view and edit basic information about an input. Contains the following fields:

Name: Name of the input. Not compulsory, but highly recommended. Used whenever the input is listed
in XProtect Corporate and access clients. Does not have to be unique.
To change the name, overwrite the existing name and click Save in the toolbar (see page 55).
www.milestonesys.com
Page 108
Management Client
Management Client
Tip: If you change the name, it will be updated throughout XProtect Corporate. This means that if the
name is used in, for example, a rule, the name will automatically change in the rule as well.

Description: Description of the input. Not compulsory. Will appear in a number of listings within XProtect
Corporate. For example, the description will appear when pausing the mouse pointer over the item's
name in the Overview pane (see page 56):
To specify a description, type the description and click Save in the
toolbar (see page 55).

Hardware name: Name of the hardware with which the input unit is connected. The field is non-editable
from here, but can be changed by clicking the Go To button next to it. This takes you to hardware
information, where the name is editable.

Unit number: Non-editable field, displaying the unit on which the input can be found on the hardware.
For hardware capable of having more than one input unit attached, the unit number will typically indicate
the number of the input port to which the input is attached. For hardware with, for example, four input
ports, the numbers will typically range from 0 to 3.
How to Fill in Properties on the Settings Tab
Lets you verify or edit key input settings, for a selected input, or for all inputs within a selected device group. If the
selected device group contains 400 or more inputs, the Settings tab will be unavailable for viewing and editing
because changing settings for so many devices in one go takes too long time.
The content of the Settings tab is determined entirely by the devices in question, and is thus likely to vary
depending on the input selected.
Content may vary, but you will typically see the following property:
Input rises on: Lets you define whether the input signal should be considered rising on Circuit closed or Circuit
open. The value of this setting is used on the input's Events tab, where you define properties for input events:
Input Rising event, Input Falling event, and Input Changed event. See the description of the Events tab in the
following.
The content of the Settings tab is displayed in a table, in which the first column lists the available settings, and the
second column lists the value of each setting.
You are typically able to change the values:
1.
Select the row with the property you want to change
2.
Click the
3.
Change the value of the property.
4.
In the toolbar (see page 55), click Save.
button to the right of the properties column.
When you have changed a setting to a non-default value, the value will appear in bold. When a value must be
within a certain range, for example between 0 and 100, the allowed range will be displayed in the grey information
box below the settings table.
How to Fill in Properties on the Events Tab
Lets you define events based on changes of the input's state, from circuit opened to circuit closed or the reverse
order. The events you define can subsequently be used in rules.
You can define events for a selected input, but not for all inputs in a device group.
1.
In the Site Navigation pane (see page 56), expand Devices, and select Inputs.
www.milestonesys.com
Page 109
Management Client
Management Client
2.
In the Overview pane (see page
56), select the required input.
3.
Select the Events tab, and click the
Add... button.
4.
In the Select Driver Event dialog,
select the appropriate option (Input
Rising event, Input Falling event, or
Input Changed event).
5.
Click OK. Your selected type of
input event will now appear in the
Events tab's Configured events list.
To the right of the list, settings for the
selected input event are displayed in a table.
The table's first column lists available
settings, the second column lists the value of
each setting.
The settings on the Events tab is determined entirely by the devices in question, and is thus likely to vary
depending on the input selected.
Content may vary, but you will typically see the following property:

Enabled: Select between True (enabled), or False (disabled).
You are typically able to change the values:
1.
Select the row with the property you want to change.
2.
Click the
3.
Change the value of the property.
4.
In the toolbar (see page 55), click Save.
button to the right of the properties column.
When you have changed a setting to a non-default value, the value will appear in bold. When a value must be
within a certain range, for example between 0 and 100, the allowed range will be displayed in the grey information
box below the settings table.
Read the Input List's Status Icons on page 133.
Manage Microphones
On many devices you are able to attach external microphones; some devices even have built-in microphones.
Devices' microphones are automatically detected when you add the devices to your XProtect Corporate system
through the Management Client's Detect Hardware wizard (see page 75) wizard, regardless of which of the
wizard's detection options you use.
Microphones do not require separate licenses; you can use as many microphones as required on your system.
You can use microphones completely independently of cameras.
Who is able to listen to audio recorded by microphones? Users of the Smart Client (see page 16) can—
provided microphones are available, and the users have the rights to use them—listen to audio from
microphones. Roles (see page 164) determine users' right to listen to microphones. You cannot listen to
microphones from the Management Client.
Tip: XProtect Corporate comes with a default rule (see page 155) which ensures that audio feeds from all
connected microphones and speakers are automatically fed to the XProtect Corporate system. Like other rules,
the default rule can be deactivated and/or modified as required.
You have two entry points for managing microphones:
www.milestonesys.com
Page 110
Management Client
Management Client

In the Management Client's Site Navigation pane (see page 56), expand Devices, select Microphones,
expand the required device group, and select the required microphone. If no device groups are available,
you must first group your microphones: See Using Device Groups on page 97 for information about
creating groups as well as adding microphones to your groups.

In the Management Client's Site Navigation pane (see page 56), expand Servers and select Recording
Servers, then in the Overview pane (see page 56) expand the required recording server, expand the
required device and select the required microphone.
Check the XProtect Corporate release notes to verify that microphones are supported for the devices and
firmware used.
Enabling Microphones
When microphones are detected with the Detect Hardware (see page 75) they are by default disabled. You can
enable microphones when needed. If a device has several microphones you can enable one, some, or all of them
as required.
1.
In the Site Navigation pane (see page 56), expand Servers and select Recording Servers.
2.
In the Overview pane (see page 56), expand the relevant recording server, and find the device on which
the microphone is placed.
3.
Right-click the required microphone, and select Enabled.
On some devices, a microphone can also be enabled/disabled on the device itself, typically through the
device's own configuration web page. If a microphone does not work after enabling it in the Management
Client, you should thus verify whether the problem may be due to the microphone being disabled on the
device itself.
Configuring Individual Microphones
You configure individual microphones by selecting the required microphone in the list, then specifying the
microphone's required settings on the tabs in the Properties pane (see page 56):

The Info tab (see page 105) for managing the selected microphone's name, etc.

The Settings tab (see page 131) for managing the selected microphone's general settings.

The Record tab (see page 128) for managing the selected microphone's recording, database and
archiving storage settings.

The Events tab (see page 102) for managing hardware configurable events.
Viewing Current State of a Microphone
When you have selected a microphone in the Management Client, information about the current status of the
selected microphone is presented in the preview pane.
When a
microphone is
not active, it
is shown as:
When the
microphone is
active, it is
shown as:
Read the Microphone List's Status Icons on page 133.
www.milestonesys.com
Page 111
Management Client
Management Client
Manage Multi-streaming
Viewing of live video and playing back of recorded video does not necessarily require the same settings in order
to achieve the best result.
Example:

For viewing live video, your organization may
prefer MPEG4 at a high frame rate.

For playing back recorded video, your
organization may prefer MJPEG at a lower
frame rate because this will help preserve disk
space.
To handle this, some cameras support multi-streaming,
with which you can establish two independent streams
to the recording server—a stream for live viewing and
another stream for playback purposes, with different
resolution, encoding, and frame rate. XProtect
Corporate supports multi-streaming so cameras can
establish two such independent streams to the
recording server.
Even when cameras support multi-streaming, individual
multi-streaming capabilities may vary considerably
between different cameras. Refer to the documentation
for your cameras for exact information. To see if a camera offers different types of streams, you can also view the
Settings tab (see page 131).
You manage multi-streaming on the Streams tab. The tab is only available when the selected camera or device
group supports multi-streaming. However, if you select a device group with 400 or more cameras, the Streams
tab will not be available for viewing and editing because changing settings for so many devices in one go takes
too long time. To access the Streams tab, expand Devices in the Management Client's Site Navigation pane (see
page 56), expand the relevant camera folder in the Overview pane (see page 56), select the required camera and
then select the Streams tab in the Properties pane (see page 56).
The tab will by default list a single stream—the selected camera's default stream, used for live video as well as for
video which is being recorded for playback purposes.
Adding a New Stream
1.
On the Streams tab, click the Add button. This will add a second stream to the list (you cannot have
more than two streams).
2.
In the Stream column, select the required type of stream.
3.
If you want to use the stream for live video, select the check box in the Live column. Leave the check
box cleared if you only want to use the stream for video which will be recorded.
You can use the same stream for both live and recorded video if required. You cannot use two different
streams for the same purpose, for example for live video.
4.
If you want to use the stream for recorded video, select the check box in the Record column. Leave the
check box cleared if you only want to use the stream for live video.
Note how the selection in the Plug-ins column always follows the stream you have selected for recorded
video. This is because the integrated plug-in which XProtect Corporate uses for motion detection is
always applied on the video stream which will be recorded.
The Edge Recording column indicates whether the selected stream supports edge recording (see page
131) or not.
5.
Click Save.
www.milestonesys.com
Page 112
Management Client
Management Client
Manage Output
On many devices you are able to attach external units to output ports on the device. This allows you to
activate/deactivate lights, sirens, etc. through XProtect Corporate.
Output may be used when creating rules (see page 155). You can create rules that automatically activate or
deactivate outputs, and rules that trigger actions when the state of an output is changed.
Output can also be triggered manually from the Management Client and the Smart Client.
Devices' output ports are automatically detected when you add the devices to XProtect Corporate through the
Management Client's Detect Hardware wizard (see page 75), regardless of which of the wizard's detection
options you use. By default, output are disabled. You can enable output when needed.
You have two entry points for managing outputs:

In the Management Client's Site Navigation pane (see page 56), expand Devices, select Outputs,
expand the required device group, and select the required output. If no device groups are available, you
must first group your output: See About Device Groups on page 97 for information about creating groups
as well as adding output to your groups.

In the Management Client's Site Navigation pane (see page 56), expand Servers and select Recording
Servers, then in the Overview pane (see page 56) expand the required recording server and select the
required output.
Before you specify use of external input and output units on a device, verify that sensor operation is recognized
by the device. Most devices are capable of showing this in their configuration interfaces, or via CGI script
commands. Also check the XProtect Corporate release notes to verify that input- and output-controlled operations
are supported for the devices and firmware used.
Enabling Output
When outputs are detected with the Detect Hardware (see page 75) process, they are by default disabled. You
can activate outputs when needed.
If a device has several outputs you can enable one, some, or all of them as required.
1.
In the Site Navigation pane (see page 56), expand Servers and select Recording Servers.
2.
In the Overview pane (see page 56) select the relevant recording server, and find the device on which
the output is placed.
3.
Right-click the required output, and select Enabled.
Specifying Output Properties
Each output has several properties which can be found on the output's Settings and Info tabs. You can access
these tabs in two ways:

In the Site Navigation pane (see page 56), expand Devices and select Outputs, then in the Overview
pane (see page 56) expand the required outputs folder and select the required output.
- or -

In the Overview pane (see page 56), select a device group to change the settings for all outputs in this
group, or expand a device group and select the required output.
The properties of the selected output, or the common properties for all outputs in a selected device group, will be
displayed on the following tabs: Settings and Info.
See How to... in the following to learn more about the properties of the selected output, or the common properties
for all outputs in a selected device group.
www.milestonesys.com
Page 113
Management Client
Management Client
Automatic and Manual Activation of Output
Output can be activated automatically or manually:

Automatic Activation of Output
With the Management Client's rules (see page 155) feature, you are able to create rules that
automatically activate or deactivate output, and rules that trigger actions when the state of an output is
changed.
For example, you may create a rule specifying that a siren should sound if motion is detected on a
particular camera, or you may create a rule specifying that a camera should start recording if a siren
sounds. See Define Input- and Output-Related Rules on page 100 for more information.

Manual Activation of Output
Output may be activated manually from the Management Client and the Smart Client:
1. In the Site Navigation pane (see page 56), expand Devices and select Outputs.
2. In the Overview pane (see page 56), expand the required outputs folder
and select the required output.
Tip: You may select a group of outputs, for example All Outputs, to
manually activate all outputs in the group.
The availability of features for manually activating an output depends
entirely on the device in question, and may thus vary.
Typically, the following elements are shown for each output in the preview
pane:
3. Select/clear the check box
to activate/deactivate the selected output.
When an output is activated, the indicator lights up green:
Alternatively, click the rectangular button
to activate the output for
the duration defined in the Output Trigger Time setting on the Settings tab
(this feature/setting may not be available for all outputs). After the defined duration, the output is
automatically deactivated.
How to Fill in Properties on the Info Tab
Lets you view and edit basic information about an output:

Name: Name of the output. Not compulsory, but highly recommended. Used whenever the output is
listed in XProtect Corporate and access clients. Does not have to be unique.
To change the name, overwrite the existing name and click Save in the toolbar (see page 55).
Tip: If you change the name, it will be updated throughout XProtect Corporate. This means that if the
name is used in, for example, a rule, the name will automatically change in the rule as well.

Description: Description of the output. Not compulsory. Will appear in a number of listings within
XProtect Corporate. For example, the description will appear when pausing the mouse pointer over the
item's name in the Overview pane (see page 56):
To specify a description, type the description and click
Save in the toolbar (see page 55).

Hardware name: Name of the hardware with which the
output unit is connected. The field is non-editable from here, but can be changed by clicking the Go To
button next to it. This takes you to hardware information, where the name is editable.

Unit number: Non-editable field, displaying the unit on which the output can be found on the hardware.
For hardware capable of having more than one output unit attached, the unit number will typically
indicate the number of the output port to which the output is attached. For hardware with, for example,
four output ports, the numbers will typically range from 0 to 3.
www.milestonesys.com
Page 114
Management Client
Management Client
How to Fill in Properties on the Settings Tab
Lets you verify or edit key output settings, such as active output state, output trigger time, etc., for a selected
output, or for all outputs within a selected device group. However, if the device group contains 400 cameras or
more the Settings tab will not be available for viewing and editing because changing settings for so many devices
in one go takes too long time.
The content of the Settings tab is determined entirely by the drivers for the cameras in question, and is thus likely
to vary depending on the output selected.
Some devices are only able to apply outputs for a relatively short time, for example max. 5 seconds. Refer to the
documentation for the device in question for exact information.
Content is displayed in a table, in which the first column lists the available settings, and the second column lists
the value of each setting.
You are typically able to change the values:
1. Select the row with the property you want to change
2. Click the
button to the right of the properties column.
3. Change the value of the property.
4. In the toolbar (see page 55), click Save.
When you have changed a setting to a non-default value, the value will appear in bold. When a value must be
within a certain range, for example between 0 and 100, the allowed range will be displayed in the grey information
box below the settings table.
Read the Output List's Status Icons on page 133.
Manage Speakers
On many devices you are able to attach external loudspeakers; some devices even have built-in speakers.
Devices' speakers are automatically detected when you add the devices to your XProtect Corporate system
through the Management Client's Detect Hardware wizard (see page 75), regardless of which of the wizard's
detection options you use. Speakers do not require separate licenses; you can use as many speakers as required
on your system.
You can use speakers completely independently of cameras.
Who is able to talk through speakers? Users of the Smart Client (see page 16) can—provided speakers are
available, and the users have the rights to use them—click a button to talk through speakers. Roles (see page
164) determine users' right to talk through speakers. You cannot talk through speakers from the Management
Client.
What happens if two users want to speak at the same time? Roles determine users' right to talk through
speakers. As part of the roles definition, you are able to specify a speaker priority from very high to very low. If
two users want to speak at the same time, the user whose role has the highest priority will win the ability to speak.
If two users with the same role want to speak at the same time, the first-come first-served principle applies.
Tip: XProtect Corporate comes with a default rule (see page 155) which ensures that audio feeds from all
connected microphones and speakers are automatically fed to the XProtect Corporate system. Like other rules,
the default rule can be deactivated and/or modified as required.
You have two entry points for managing speakers:

In the Management Client's Site Navigation pane (see page 56), expand Devices, select Speakers,
expand the required device group, and select the required speaker. If no device groups are available,
you must first group your speakers: See About Device Groups on page 97 for information about creating
groups as well as adding speakers to your groups.
www.milestonesys.com
Page 115
Management Client
Management Client

In the Management Client's Site Navigation pane (see page 56), expand Servers and select Recording
Servers. In the Overview pane (see page 56), expand the required recording server and select the
required speaker.
Check the XProtect Corporate release notes to verify that speakers are supported for the devices and firmware
used.
Enabling Speakers
When speakers are detected with the Detect Hardware, they are by default disabled. You can enable speakers
when needed. If a device has several speakers you can enable one, some, or all of them as required.
1.
In the Site Navigation pane (see page 56), expand Servers and select Recording Servers.
2.
In the Overview pane (see page 56), expand the relevant recording server, and find the device on which
the speaker is placed.
3.
Right-click the required speaker, and select Enabled.
On some devices, a speaker can also be enabled/disabled on the device itself, typically through the device's own
configuration web page. If a speaker does not work after enabling it in the Management Client, you should thus
verify whether the problem may be due to the speaker being disabled on the device itself.
Configuring a Speakers
You configure individual speakers by selecting the required speaker in the list, then specifying the speaker's
required settings on the tabs in the Properties pane (see page 56):

The Info tab (see page 105) for managing the selected speaker's name, etc.

The Settings tab (see page 131) for managing the selected speaker's general settings.

The Record tab (see page 128) for managing the selected speaker's recording, database and archiving
storage settings.
Viewing Current State of a Speaker
When you have selected a speaker in the Management Client, information about the current status of the selected
speaker is presented in the preview pane.
When a
speaker is not
active, it is
shown as:
When the
speaker
active, it is
shown as:
Read the Speaker List's Status Icons on page 133.
Motion Tab (Camera Properties)
The Motion tab lets you enable and configure motion detection for the selected camera. Motion detection
configuration is a key element in your XProtect Corporate surveillance solution: Your motion detection
configuration may determine when video is recorded, when events are generated, when external output (such as
lights or sirens) is triggered, etc.
Time spent on finding the best possible motion detection configuration for each camera may therefore help you
later avoid unnecessary alarms, etc. Depending on the physical location of the camera, it may be a very good
idea to test motion detection settings under different physical conditions (day/night, windy/calm weather, etc.).
www.milestonesys.com
Page 116
Management Client
Management Client
Before you configure motion detection for a camera, it is highly
recommended that you have configured the camera's image quality
settings, such as resolution, compression, etc., on the Settings tab
(see page 131). If you later change image quality settings, you should
always test any motion detection configuration afterwards.
Camera properties: Motion tab with red deflection on the motion indication bar
Tip: You can configure motion detection for all cameras in a device
group (see Manage Cameras on page 106) in one go. Note, however,
that some motion detection settings must be configured individually for
each camera. This is the case with exclude regions (areas in which not
to use motion detection), as these are very likely to vary from camera to
camera.
Enabling and Disabling Motion Detection
Motion detection is enabled by default. To enable/disable motion
detection for a camera, select/clear the Motion tab's Motion detection
check box.
When motion detection is disabled for a camera, any motion detectionrelated rules (see page 155) for the camera will not work.
Motion Detection Settings
You are able to specify settings relating to the amount of change
required in a camera's video in order for the change to be regarded as
motion. You are also able to specify intervals between motion detection analyses, any areas of an image in which
motion should be ignored, etc.

Sensitivity Slider:
The Sensitivity slider determines how much each pixel in the camera's images must change before it is
regarded as motion.
Drag the slider to the left for a higher sensitivity level, and to the right for a lower sensitivity level.
The higher the sensitivity level, the less change will be allowed in each pixel before it is regarded as
motion.
The lower the sensitivity level, the more change in each pixel will be allowed before it is regarded as
motion. This way you are able to allow insignificant changes, which should not be regarded as motion.
Pixels in which motion is detected are highlighted in green in the preview image. Select a slider position
in which only detections you consider motion are highlighted.
Highlighted motion in the preview image
Tip: Your exact sensitivity slider setting is indicated by a
number from 0-300 in the right side of the slider. This way you
are able to compare the exact sensitivity slider setting between
cameras.
Tip: If you find the concept of motion detection sensitivity
difficult to grasp, try dragging the slider to the left towards the
highest possible sensitivity (0) position: The more you drag the
slider towards the highest possible sensitivity position, the
more of the preview image becomes highlighted in green. This
is because with a very high sensitivity level even the slightest
change in each pixel will be regarded as motion.

Motion Slider
The Motion slider determines how many pixels in the camera's images image must change before it is
regarded as motion.
The selected motion level is indicated by the black vertical line in the motion indication bar above the
sliders.
www.milestonesys.com
Page 117
Management Client
Management Client
The black vertical line in the motion indication serves as a threshold: When detected motion is above the
selected sensitivity level, the bar changes color from green to red, indicating a positive detection.
Motion indication bar deflection changes color from green to red when above the threshold, indicating a positive
motion detection
Tip: Your exact motion slider setting is indicated by a number from 0-10.000 in the right side of the
slider. This way you are able to compare the exact motion slider setting between cameras.

Keyframes Settings
A keyframe is a single frame stored at specified intervals. The keyframe contains the entire view of the
camera, whereas the following frames contain only the pixels that change. This helps greatly reduce the
size of files.
If the check box is not available, or not selected, every frame will contain the entire view of the camera.

Image Processing Interval
You are able to select how often motion detection analysis should be carried out on video from the
camera.
From the Process image every (msec): list, select the required interval: every 100 milliseconds (i.e. once
every tenth of a second), every 250 milliseconds, every 500 milliseconds, every 750 milliseconds, or
every 1000 milliseconds (i.e. once every second). Default is every 500 milliseconds.
The interval is applied regardless of the camera's frame rate settings.

Detection Method
You are able to optimize motion detection performance by analyzing only a selected percentage of the
image, for example 25%. By analyzing 25%, only every fourth pixel in the image is analyzed instead of
all pixels.
Using optimized detection will reduce the amount of processing power used to carry out the analysis, but
will also mean a less accurate motion detection.
In the Detection method drop down-box, select the wanted detection method.

Ignoring Motion Detection in Parts of Images
The Exclude Regions settings in the lower part of the Motion tab lets you disable motion detection in
specific areas of a camera's images. Parts of images in which motion should be ignored this way are
called exclude regions.
Disabling motion detection in specific areas may help you avoid detection of irrelevant motion, for
example if the camera covers an area where a tree is swaying in the wind or where cars regularly pass
by in the background.
When exclude regions are used with PTZ cameras and you pan/tilt/zoom the camera, the excluded area
will not move accordingly. This might mean that objects originally excluded will be included. This is due
to the fact that the exclude region is locked according to the camera's view, not the excluded region.
Consequently, it is not recommended to use exclude regions
with PTZ cameras.
To use exclude regions, select the Use exclude regions
check box.
Defining Exclude Regions:
When you select the Use Exclude regions check box, the
preview image will be divided into selectable sections by a
grid.
To define exclude regions, drag the mouse pointer over the
www.milestonesys.com
Page 118
Management Client
Management Client
required areas in the preview image. Pressing down the left mouse button selects a grid section; right
mouse button clears a grid section.
You are able to define as many exclude regions as you require. Excluded regions are shown in blue.
Three exclude regions defined in the preview window. In this case, the grid is visible.
The blue exclude area indications will only appear in the preview image on the Motion tab, not in any
other preview images in the Management Client or access clients.
o
Grid Size
The value selected in the Grid size list determines the density of the grid, regardless whether
the grid is shown or not.
Select between the values 8×8 (i.e. a grid dividing the image into eight sections along the Xaxis and eight sections along the Y-axis), 16×16, 32×32 or 64×64.
With a grid of 8×8, the image will be divided into relatively few sections for you to select for
exclude regions. Each section will be relatively large; you will not be able to define very detailed
exclude regions. With a grid size of 64×64, the image will be divided into relatively many
sections for you to select for exclude regions. Each section will be relatively small, enabling you
to define more detailed exclude regions.
Examples of 8×8, 16×16, 32×32 and 64×64 grids respectively:
The four different grid sizes.
o
Show Grid
The grid may be visible or hidden, depending on whether the Show grid check box is selected
or not.
When the Show grid check box is selected (default), the preview image will feature a grid
indicating the division of the preview image into selectable sections. The grid may help you
when selecting exclude regions in the preview image.
The density of the grid is determined by the value selected in the Grid size list.
Showing the grid is not a requirement for selecting exclude regions; even without the grid you
are able to select exclude regions as described earlier. Hiding the grid may provide a less
obscured view of the preview image.
o
Show Regions
When the Show regions check box is selected (default), exclude regions will be highlighted in
blue in the preview image.
Hiding exclude regions may provide a less obscured view of the preview image. However,
www.milestonesys.com
Page 119
Management Client
Management Client
under normal circumstances it is highly recommended that you keep the Show regions box
selected; otherwise exclude regions may exist without you or your colleagues being aware of it.
The blue exclude area indications will only appear in the preview image on the Motion tab, not
in any other preview images in the Management Client or access clients.
o
Pen size
Use the Pen size slider to indicate the size of the selections you wish to make when clicking
and dragging the grid to select regions for privacy masking. Default is set to small, which is
equivalent to one square in the grid.
Privacy Mask Tab (Camera Properties)
The Privacy Mask tab lets you enable and configure
privacy masking for the selected camera. Among
other things, you can define if and how selected areas
of a camera's view should be masked before
distribution. For example, if a surveillance camera
films a street, in order to protect residents privacy, you
can mask certain areas of a building (could be
windows and doors) with privacy masking. This is
even needed in some countries to comply with
national legislation.
As Administrator you are also able to see through
privacy masked areas, and can turn showing of
privacy masked areas on and off. When viewed via
Smart Client, Remote Client, or any other media,
privacy masked areas will be represented as black
areas and it is impossible to see behind the privacy
masking or in any way remove it.
Red areas indicate the areas masked for privacy.
When privacy masks are used with PTZ cameras and
you pan/tilt/zoom the camera, the selected area
masked for privacy will not move accordingly. This
might mean that objects masked for privacy become
visible. This is due to the fact that the masked area is
locked according to the camera's view, not the
masked object. Consequently, it is not recommended
to use privacy masking with PTZ cameras.
Enabling and Disabling Privacy Masking
The privacy masking feature is enabled by default. To enable/disable the privacy masking feature for a camera,
select/clear the Privacy Mask tab's Privacy masking check box.
Privacy Masking Settings
When you enable privacy masking, the preview image is
divided into selectable sections by a grid.
To define privacy mask regions, drag the mouse pointer over
the required areas in the preview image. Pressing down left
mouse button selects a grid section; right mouse button
clears a grid section.
You are able to define as many privacy mask regions as you
require. Privacy mask regions are shown in red.
Three privacy mask regions defined in the preview window. In this
case, the grid is visible.
The red privacy mask indications will also appear in the
www.milestonesys.com
Page 120
Management Client
Management Client
preview image on the Motion tab.

Grid Size
The value selected in the Grid size list determines the density of the grid, regardless whether the grid is
shown or not.
Select between the values 8×8 (i.e. a grid dividing the image into eight sections along the X-axis and
eight sections along the Y-axis), 16×16, 32×32 or 64×64.
With a grid of 8×8, the image will be divided into relatively few sections for you to select for privacy mask
regions. Each section will be relatively large; you will not be able to define very detailed privacy mask
regions. With a grid size of 64×64, the image will be divided into relatively many sections for you to
select for privacy mask regions. Each section will be relatively small, enabling you to define more
detailed privacy mask regions.
Examples of 8×8, 16×16, 32×32 and 64×64 grids respectively:
The four different grid sizes.

Show Grid
The grid may be visible or hidden, depending on whether the Show grid check box is selected or not.
When the Show grid check box is selected (default), the preview image will feature a grid indicating the
division of the preview image into selectable sections. The grid may help you when selecting privacy
mask regions in the preview image.
Showing the grid is not a requirement for selecting privacy mask regions; even without the grid you are
able to select privacy mask regions as described above. Hiding the grid may provide a less obscured
view of the preview image.

Show Privacy Masks
When the Show privacy masks check box is selected (default), privacy mask regions will be highlighted
in red in the preview image.
Hiding privacy mask regions may provide a less obscured view of the preview image.
However, under normal circumstances it is highly recommended that you keep the Show privacy masks
box selected; otherwise exclude privacy mask regions may exist without you or your colleagues being
aware of it.

Pen size
Use the Pen size slider to indicate the size of the selections you wish to make when clicking and
dragging the grid to select regions for privacy masking. Default is set to small, which is equivalent to one
square in the grid.
www.milestonesys.com
Page 121
Management Client
Management Client
PTZ Patrolling Tab (Camera Properties)
The Patrolling tab lets you create patrolling profiles, the automatic movement of a PTZ (Pan/Tilt/Zoom) camera
between a number of preset positions (see page 124). Before you are able to work with patrolling, you must have
specified at least two preset positions for the camera.
You manage patrolling on the Patrolling tab, which is available only when the selected camera is a PTZ camera.
Patrolling profiles are the definitions of how patrolling should take place. This includes the order in which the
camera should move between preset positions, how long it should remain at each position for, etc. You are able
to create an unlimited number of such patrolling profiles and use them in your rules (see page 155). For example,
you may create a rule specifying that one patrolling profile should
be used during daytime opening hours, and another during
nights.
In order to use PTZ cameras' features, including the ability to pan,
tilt, and zoom, operators must have a role which gives them the
necessary rights. See About Roles on page 164 for more
information, including step-by-step descriptions of how to assign
users to roles and how to specify the rights of roles.
Patrolling tab, displaying a patrolling profile with customized transitions
Adding a New Patrolling Profile
1.
Click the New button. This will open the Add Profile
dialog.
2.
In the Add Profile dialog, specify a name for the
patrolling profile:
Tip: Use a descriptive name; the name of the patrolling profile may later be used in situations where you
will not have access to details about the patrolling profile, e.g. when using the patrolling profile in a rule
(see page 155).
3.
Click OK. The new patrolling profile will be added to the Patrolling tab's Profile list. You are now able to
specify required preset positions and other settings for the patrolling profile.
Specifying Preset Positions for Use in a Patrolling Profile
1.
Select the required patrolling profile in the
Profile list:
2.
Click the Add button. This will open the Select
Preset dialog.
3.
In the Select Preset dialog, select
the preset positions required for your
patrolling profile:
4.
Click OK. The selected preset positions are
added to the list of preset positions for the
patrolling profile:
5.
The preset position at the top of the list will be used as the first stop when
the camera patrols according to the patrolling profile, the preset position in
second position from the top will be the second stop, and so forth.
If required, change the sequence by selecting the required preset position
and using the up/down buttons:
Tip: If required, you can easily add more preset positions to
the list by clicking the Add button, or remove unwanted preset positions from the list by
selecting the unwanted preset position, then clicking the Remove button.
www.milestonesys.com
Page 122
Management Client
Management Client
Specifying How Long to Stay at Each Preset Position for
When patrolling, the PTZ camera will by default remain for 5 seconds at each preset position specified in the
patrolling profile before it moves on to the next preset position. To change the
number of seconds for which the PTZ camera will remain at a specific preset
position, do the following:
1.
Select the required patrolling profile in the Profile list.
2.
In the list of preset positions for the selected patrolling profile, select the
preset position for which you want to change the time:
3.
Specify the required time (in number of seconds) in the Wait time
(secs.) field:
4.
If required, repeat for other preset positions.
Customizing Transitions
By default, the time required for moving the camera from one preset position to another, known as transition, is
estimated to be 3 seconds. During this time, motion detection is by default disabled on the camera, as irrelevant
motion is otherwise likely to be detected while the camera moves between the preset positions. Transitions are
also known as PTZ scanning.
Customizing speed for transitions is only supported if your camera supports PTZ scanning and is of the type
where preset positions are configured and stored on the XProtect Corporate server (type 1 PTZ camera).
Otherwise the Speed slider is grayed out.
You can customize the transitions between each of the preset positions in a patrolling profile. You are able to
customize the following:

The estimated transition time

The speed with which the camera will move during a transition

Which plug-ins to disable during transition.
To customize transitions between preset positions in a patrolling profile, do the following:
1.
Select the required patrolling profile in the Profile list.
2.
Select the Customize transitions check box:
This will add transition indications to the list of preset positions for the
selected patrolling profile.
3.
In the list, select the required transition:
4.
Specify the estimated transition time (in number of seconds) in the
Expected time (secs.) field:
5.
Use the Speed slider to specify the required transition speed. When the slider is in its rightmost position,
the camera will move with its default speed. The more you move the slider to the left, the slower the
camera will move during the selected transition.
Tip: A number indicating the exact speed is displayed near the top right corner of the slider. When
required, the number (from 0.0001 (very slow) to 1.0000 (default speed)) allows you to define exactly the
same custom speed across transitions.
6.
In the Plug-ins to disable list, specify any plug-ins you want to disable during the selected transition. By
default, the plug-in used for motion detection on the camera (MotionDetectionPlugin) is disabled in order
to avoid irrelevant motion being detected during transition.
To add a plug-in to the list, click the Add... button, and select the required plug-in. This requires that one
or more other plug-ins are available, and that they can be disabled.
To remove a plug-in from the list, for example if you do not want motion detection to be disabled during
www.milestonesys.com
Page 123
Management Client
Management Client
the transition, select the plug-in and click the remove button.
7.
Repeat as required for other transitions.
Specifying an End Position
You are able to specify that the camera should move to a specific preset position when patrolling according to the
selected patrolling profile ends.
1.
Select the required patrolling profile in the Profile list.
2.
Select the Go to specific preset on finish check box:
This will open the Select Preset dialog.
3.
In the Select Preset dialog, select the required end position, and click OK.
Tip: You can select any of the camera's preset positions as the end position, you are not limited to the
preset positions used in the patrolling profile.
4.
The selected end position is added to the list of preset positions for the selected patrolling profile. When
patrolling according to the selected patrolling profile ends, the camera will go to the specified end
position.
Renaming an Existing Patrolling Profile
1.
Select the required patrolling profile in the Profile list.
2.
Click the Rename button. This will open the Rename Profile dialog.
3.
In the Rename Profile dialog, type a new name for the patrolling profile.
Tip: Use a descriptive name; the name of the patrolling profile may later be used in situations where you
will not have access to details about the patrolling profile, e.g. when using the patrolling profile in a rule
(see page 155).
4.
Click OK.
Specifying Manual PTZ Session Timeout
Patrolling of PTZ cameras may be interrupted manually by Smart Client (see page 16) users with the necessary
user rights.
You are able to specify how much time should pass before regular patrolling is resumed after a manual
interruption:
1.
In the Management Client's menu bar, select Tools > Options. This will open the Options window.
2.
On the Options window's General tab, select the
required amount of time in the PTZ manual session
timeout list (default is 15 seconds).
The setting will apply for all PTZ cameras on your XProtect
Corporate system.
PTZ Presets Tab (Camera Properties)
The Presets tab lets you create preset positions to be used, for
example, in rules (see page 155) for making a PTZ
(Pan/Tilt/Zoom) camera move to a specific preset position when
an event occurs, as well as in patrolling (see page 122), the
automatic movement of a PTZ camera between a number of
preset positions.
Presets tab, with eight preset positions defined
www.milestonesys.com
Page 124
Management Client
Management Client
You manage preset positions on the Presets tab, which is available only when the selected camera is a PTZ
(Pan/Tilt/Zoom) camera. The Presets tab will not be available if the selected PTZ camera does not support preset
positions.
In order to use PTZ cameras' features, including the ability to pan, tilt, and zoom, operators must have a role
which gives them the necessary rights. See About Roles on page 164 for more information, including step-by-step
descriptions of how to assign users to roles and how to specify the rights of roles.
Adding a Preset Position
As an alternative to defining preset positions in XProtect Corporate, preset positions may for some PTZ cameras
also be defined on the camera device itself (typically by accessing a device-specific configuration web page) and
imported into XProtect Corporate by selecting Use presets from device.
To add a preset position for the camera in XProtect Corporate, do the following:
1.
Click the Add... button. This will open the Add Preset
window:
2.
The Add Preset window displays a preview image from the
camera; use the navigation buttons and/or sliders to move
the camera to the required preset position. While you do this,
you are able to verify the position of the camera through the
preview image.
Tip: Use of the navigation buttons and sliders is described in
the following.
3.
Specify a name or number for the preset position in the
Name field.
Tip: If typing a name, use a descriptive name; the name of
the preset position may later be used in situations where you
will not have access to a preview image from the preset
position, e.g. when using the preset in a rule (see page 155).
4.
Optionally, type a description of the preset position in the
Description field.
5.
Click OK. This will close the Add Preset window, and add the preset position to the Presets tab's list of
available preset positions for the camera.

How to Use the Navigation Buttons
The navigation buttons let you move the camera as follows:
www.milestonesys.com
Page 125
Management Client
Management Client
up and to the left
up
up and to the right
to the left
Moves the view
to its default position
to the right
down and to the left
down
down and to the right
Zooms in (one zoom level per click)
Zooms out (one zoom level per click)

How to Use the Axes Navigation Sliders
The navigation sliders let you to move the camera along each of its axes. Click inside the sliders to
move the sliders' red handles to the required positions.
The slider for the X-axis (allowing you to pan left/right) is located immediately below the preview
image.
The slider for the Y-axis (allowing you to tilt the camera up/down) is located immediately to the left
of the preview image.
The slider for the Z-axis (allowing you to zoom in and out) is located immediately above the preview
image. The camera will zoom in when you move the slider towards Tele, and zoom out when you
move the slider towards Wide.
Example: Add Preset window's X-axis slider

How to Use the Iris Slider
Iris settings are only available for some cameras.
Iris settings control the amount of light in images. The higher the iris setting, the lighter images will
appear.
Click inside the slider to move the slider's red handle to the required position.

How to Use the Focus Slider
Focus settings are only available for some cameras.
Click inside the slider to move the slider's red handle to the required position.
Using Preset Positions from Device
As an alternative to specifying preset positions in XProtect Corporate, preset positions may for some PTZ
cameras also be defined on the camera device itself (typically by accessing a device-specific configuration web
page.
Such device-defined presets can subsequently be imported into XProtect Corporate by selecting Use presets
from device.
www.milestonesys.com
Page 126
Management Client
Management Client
If importing presets from the camera device, any presets you have previously defined for the camera in XProtect
Corporate will be removed; this will affect any patrolling profiles in which these presets are used, as well as any
rules in which the affected patrolling profiles are used.
If you later wish to edit such device-defined presets, editing should take place on the camera device.
Assigning a Default Preset Position
If required, you are able to assign one of a PTZ camera's preset positions at the camera's default preset position.
Having a default preset position can be useful because it allows you to define rules (see page 155) specifying that
the PTZ camera should go to the default preset position under particular circumstances, for example after the
PTZ camera has been operated manually.
To assign a preset position as the default, select the required preset in your list of defined preset positions, then
select the default preset box below the list.
Only one preset position can be the default preset position.
Editing a Preset Position
To edit an existing preset position defined in XProtect Corporate (presets imported from a device should be edited
on the device itself), do the following:
1.
Select the required preset position in the Presets tab's list of available preset positions for the camera.
2.
Click the Edit... button. This will open the Edit Preset window:
3.
The Edit Preset window displays a preview image from the
preset position in question; use the navigation buttons and/or
sliders to change the preset position as required.
Example only; features are camera-dependent
4.
Change the name/number and description of the preset
position as required.
Tip: If using a name, make sure it is descriptive; the name of
the preset position may later be used in situations where you
will not have access to a preview image from the preset
position, e.g. when using the preset in a rule (see page 155).
5.
Click OK.
Testing a Preset Position
1.
Select the required preset position in the Presets tab's list of
available preset positions for the camera.
2.
Click the Test button.
3.
The Presets tab's preview image will move to the selected preset position.
Tip: If the preview image does not appear to move to the selected preset position when you click the
Test button, verify that preview image does not already show the selected preset position. In that case,
try testing another preset position first.
PTZ Tab (Hardware Properties)
The PTZ tab lets your enable PTZ (Pan/Tilt/Zoom) for video encoders. It is only available if the selected hardware
is a video encoder.
What is a video encoder? A video encoder, also known as video server, is a piece of hardware which is able to
stream video from a number of connected cameras. Video encoders contain image digitizers, making it possible
to connect analog cameras to a network.
www.milestonesys.com
Page 127
Management Client
Management Client
For video encoders, the use of PTZ must be enabled on the
hardware level before you can use the PTZ features of PTZ
cameras attached to the video encoder. The Settings tab lets you
enable the use of PTZ separately for each of the video encoder's
channels.
To access the PTZ tab, select the required hardware in the
Overview pane (see page 56), then select the PTZ tab in the
Properties pane (see page 56).
Not all video encoders support the use of PTZ cameras. Even
video encoders which support the use of PTZ cameras may
require configuration, such as installation of additional drivers
(typically through accessing a browser-based configuration
interface on the device's IP address) before PTZ cameras can be
used.
PTZ tab, with PTZ enabled for two of a video encoder's channels
Enabling PTZ on a Video Encoder
To enable the use of PTZ cameras on a video encoder, do the following on the PTZ tab:
1.
In the list of devices connected to the video encoder, select the Enable PTZ box for the camera(s) on
which you want to use PTZ:
2.
In the PTZ Device ID column, verify the ID of the PTZ camera(s) in
question.
3.
In the COM Port column, select which of the video encoder's COM (serial communications)
ports should be used for controlling PTZ functionality on each required PTZ camera:
4.
In the PTZ Protocol column, select which positioning scheme to use for each required PTZ
camera:

Absolute: When operators use Pan/Tilt/Zoom controls for the camera, the
camera is adjusted relative to a fixed position, often referred to as the camera's
home position

Relative: When operators use Pan/Tilt/Zoom controls for the camera, the camera
is adjusted relative to its current position
Refer to the camera's documentation if in doubt.
5.
In the toolbar (see page 55), click Save.
You are now able to configure preset positions (see
page 124) and patrolling (see page 122) for the PTZ
camera(s) in question.
Record Tab Overview
Recordings from an item (camera, microphone or speaker) will
only be saved in the items's database when recording is
enabled and recording-related rule (see page 155) criteria are
met.
Record tab, example from camera
About the Record Tab for:
Camera
Lets you specify recording and storage settings for the selected
www.milestonesys.com
Page 128
Management Client
Management Client
camera.
What does recording mean? In IP video surveillance systems, the term recording means saving video from a
camera in the camera's database on the surveillance system. In many IP video surveillance systems, all of the
video received from cameras is not necessarily saved. Instead, saving of video in a camera's database, i.e.
recording, is started only when there is a reason to do so: For example when motion is detected, when an event
occurs, or when a specific period of time begins. Recording is then stopped after a specified amount of time,
when motion is no longer detected, when an event occurs, when a time period ends, or similar. The term
recording originates from the analog video era, when video was taped only when the record button was pressed.
Microphone
Lets you specify recording and storage settings for the selected microphone. Microphones' recording and storage
settings are completely independent of cameras and speakers.
Speaker
Lets you specify recording and storage settings for the selected speaker.
Enabling and Disabling Recording
Recording is by default enabled.
To enable/disable recording for the selected item, select/clear the Record tab's Recording check box.
Recording must be enabled for the item before you are able to record (i.e. save) video or audio from the camera.
A rule (see page 155) specifying that an item should record under particular circumstances will not work if
recording is disabled for the item in question.
Setting Recording Frame Rate—Camera Only
Specifying recording frame rate is only possible for MJPEG, a video codec (technology for compressing and
decompressing data) with which each frame is separately compressed into a JPEG image.
1.
Select or type the required recording frame rate (in FPS, Frames Per Second) in the Recording frame
rate box.
2.
Clicking the Recording frame rate box' up/down arrows will increase/reduce the value in increments of 1
FPS.
Tip: If you click inside the Recording frame rate box, two decimals will be added to the value. By selecting the
number before or after the separator, you are able to increase/reduce the numbers in increments of 1 unit. This
way you are able to specify a very specific recording frame rate
average over time, for example of 20.15 FPS:
Specifying a specific recording frame rate
Working with Prebuffering
Prebuffering is essentially the ability to save video and audio in the camera's or microphone's database before the
initial boundaries of a recording.
Use of prebuffering can be highly advantageous: It allows you to save video and audio from before the events or
times used to start recordings.
 How Prebuffering Works for Cameras and Microphones...
If, for example, you have created a rule specifying that recording should start when a door is opened,
being able to see what happened immediately prior to the door being opened may be useful. Such
prebuffering is possible since XProtect Corporate continuously receives streams of video and audio from
connected cameras and microphones (unless the transfer of video or audio from cameras or microphones
has in some way been disabled). Storing video and audio from before the initial boundaries of a recording
is therefore not a problem: video and audio passes through XProtect Corporate anyway.
When prebuffering is enabled for a camera or a microphone, XProtect Corporate continuously records
www.milestonesys.com
Page 129
Management Client
Management Client
video or audio from the camera's or microphones stream and provisionally stores it in the database for a
specified number of seconds before automatically deleting it— unless the provisionally stored video or
audio turns out to be required for a recording, in which case it is automatically added to the recording.
 How Prebuffering Works for Speakers...
Unlike video and incoming audio, which XProtect Corporate continuously receives from connected
cameras and microphones, outgoing audio is only transmitted when Smart Client users press a button to
talk through speakers. This can, depending on which events or times are used to start recordings, mean
that there will be very little or no outgoing audio available for prebuffering.
The following example illustrates how prebuffered video or audio is added to a recording:
This is the stream received by XProtect Corporate:
These are the initial boundaries of a recording, as defined, for example, by start and stop events:
However, a rule specifies that recording should start 5 seconds prior to the start event, so 5 seconds of
prebuffered video or audio is added:
This is what is actually recorded:
Enabling and Disabling Prebuffering
Prebuffering is by default enabled; with a prebuffer size of 3 seconds. To enable/disable prebuffering, select/clear
the Enable prebuffering check box. When enabling, remember to specify a prebuffer size.
Specifying Prebuffer Size
Select or type the required prebuffer size (in seconds) in the Prebuffer size box. Clicking the Prebuffer size box'
up/down arrows will increase/reduce the value in increments of one second.
The number of seconds you specify in the Prebuffer size box must be sufficiently large to accommodate your
requirements. Example: If, like in the following rule example, you plan to be able to save video from five seconds
prior to detected motion, the prebuffer size must be at least five seconds.
Using Prebuffering in Rules
The use of prebuffering enables you to create rules (see page 155) specifying that recording should begin prior to
the event or time triggering the rule.
Example: Your ability to use this example rule— specifying that recording should start on a camera 5
seconds before motion is detected on
the camera— depends on prebuffering
being enabled for the camera in
question.
Detail from a rule relying on prebuffering
Working with Storage Area
In the Storage area you can monitor and edit database settings for the selected item.
At the top of the Storage area, the
selected database for the item in
question and its status is stated. In
this example, the selected database
is Local Default and its status is
Active.
www.milestonesys.com
Page 130
Management Client
Management Client
Possible Statuses for Selected Database:

Active - database is active and running.

Archives also located in old storage - database is active and running and has archives located in
other storage areas as well.

Data for some of the devices chosen is currently moving to another location - database is active
and running and moving data from one or more selected devices from one location to another.

Data for the device is currently moving to another location - database is active and running and
moving data from the selected device is currently moving from one location to another.

Information unavailable in failover mode - status information about the database cannot be collected
when database is in failover mode. See Manage Failover Servers on page 222.
Further down in the Storage area it is also possible to see which archive(s) are associated with the selected
database, their individual status (OK or Old Storage), location and how much space they each use.
In the Total used space field, the total spaced used for the entire storage is indicated.
Selecting a Different Storage:
1.
In the upper part of the Storage area, click the Select... button to change database for the item in
question.
2.
In the Select Storage dialog that follows, select the wanted database.
3.
Click OK.
4.
Next, in the Recordings Action dialog, select whether already existing—non-archived—recordings
should be moved along to the new storage or deleted.
5.
After selecting, click OK.
Deleting All Recordings:
1.
To delete all recordings for the selected item, click the Delete All Recordings button at the bottom of the
Storage area.
2.
Click Yes.
Enabling and Disabling Edge Recording—Camera Only
The Edge recording area will only be enabled if the selected camera supports edge recording.
If disabled, select the Enable edge recording check box to enable edge recording.
IMPORTANT: Edge recording cannot coexist with pre-alarm image functionality (see page 141, action Send
notification to <profile>). So if a camera is setup to do edge recording, it is not possible to export pre-alarm
images from that camera, and vice versa.
What is edge recording? Some cameras are capable of edge recording. This means, that to minimize loss in
case connection between the camera and the recording server is lost or broken unexpectedly, they are able to
use their own local storage to store recorded video and audio. In that case, cameras with edge recording
capabilities can record on their own storage and when communication is re-established, recordings are
transferred from the camera to the surveillance system.
Settings Tab Overview
If you select a device group with 400 or more items the Settings tab will not be available for editing because
changing settings for so many devices in one go takes too long time.
www.milestonesys.com
Page 131
Management Client
Management Client
The content of the Settings tab is displayed in a table, in
which the first column lists the available settings, and the
second column lists the value of each setting. You are
typically able to change values; when you have changed
a setting to a non-default value, the value will appear in
bold. When a value must be within a certain range, for
example between 0 and 100, the allowed range will be
displayed in the information box below the settings table:
Settings tab, example from camera. Red arrow indicates
allowed range; in this example the value used to specify
compression must be a number between 0 and 100. Content of
Settings tab varies depending on selected device type and
selected device.
About the Settings Tab for:
Camera
Lets you verify or edit settings, such as default frame rate, resolution, compression, on-screen date/time/text
display, etc., for a selected camera, or for all cameras within a selected device group.
The content of the Settings tab is determined entirely by the drivers for the cameras in question, and is thus likely
to vary depending on the types of cameras selected.
Tip: Some cameras may support more than one type of stream, for example MPEG4 and MJPEG. In that case,
you can use multi-streaming (see page 112).
Tip: If you change a camera's settings, you can quickly verify the effect of your change if you have the preview
pane enabled. Note, however, that you cannot use the preview pane to judge the effect of frame rate changes, as
a special frame rate for the preview pane's thumbnail images is used (defined in the Options dialog (see page
195)).
Microphone and Speaker
Lets you verify or edit settings for a selected microphone or speaker, or for all microphones or speakers within a
selected device group.
Content of the Settings tab may vary depending on the types of microphones or speakers selected.
Hardware
Lets you verify or edit settings for the hardware selected under a recording server.
The content of the Settings tab is determined entirely by the hardware in question, and may thus vary depending
on the type of hardware selected. For some types of hardware, the Settings tab may display no content at all.
Specify Common Settings for Camera, Microphone, Speaker in Device Group
If using Device Groups (see page 97) , you are able to quickly specify common settings for all devices within a
given device group:
1.
In the list of device in the Management Client's Overview pane (see page 56), right-click the required
device group. On the Settings tab, all settings which are common to all of the device group's items (i.e.
cameras, microphones or speakers) will be listed.
2.
You are now able to verify or change both common settings and settings for individual item types within
the device group.
From the menu above the settings list, select the required type of item:
Make changes as needed.
www.milestonesys.com
Page 132
Management Client
Management Client
3.
In the toolbar (see page 55), click Save.
All three examples are from camera.
Specify Common Settings for All Items in a Device Group—Hardware
1.
In the Management Client's Overview pane (see page
56), right-click the required recording server to see its
device groups. Select the relevant hardware under the
wanted device group. On the Settings tab, all settings
which are common to all of the device group's
hardware will be listed.
Selecting hardware under a recording server
2.
You are now able to verify or change both common settings and settings for the individual hardware
types within the device group.
From the menu above the settings list, select the required type of hardware.
3.
Make changes as needed
4.
In the toolbar (see page 55), click Save.
Status Icons Overview
The following icons are used to indicate status of cameras (see page 106), microphones (see page 110),
speakers (see page 115), input (see page 107) and output (see page 113) events in item lists:
Camera
Microphone
Speaker
Input
Output
Description
Item enabled: Can communicate with the recording
server, and can if required be started/stopped
automatically through a rule.
Item recording.
Speaker being recorded: Note that what is being
said through the speaker can be recorded, but cannot
subsequently be played back or exported (for
example to prove that a warning was given).
Item temporarily stopped or has no feed: Often
shown when an item is communicating with XProtect
Corporate while it is being disabled or enabled. Also
shown if the Default Start Audio Feed Rule is not
active; see Managing Rules on page 155. When
stopped, no information is transferred to XProtect
www.milestonesys.com
Page 133
Management Client
Management Client
Corporate. In which case—if it is a camera—neither
live viewing nor recording will be possible. However,
a stopped item will still be able to communicate with
the recording server, as opposed to when an item is
disabled.
Item disabled: Cannot be started automatically
through a rule and will not be able to communicate
with the recording server. In the case of a camera,
when a camera is disabled, neither live viewing nor
recording will be possible.
Item database being repaired.
Item requires attention.
Status unknown.
Note that some icons may be combined, as in this
example where Item is enabled is combined with
Item is recording (since a recording item is also an
enabled item).
Client
Manage View Groups
The way in which video from one or more cameras is presented in the access clients (Smart Client (see page 16)
and Remote Client (see page18) is called a view. A view group is
basically a container for one or more logical groups of such views.
In the access clients a view group is presented as an expandable folder
from which users can select the group, and subsequently the view they
want to see:
Example from Smart Client: Arrow indicates a view group, which contains
a logical group (called Amenities), which in turn contains 3 views.
More about View Groups
By default, each role you define in the Management Client is
also created as a view group: when you add a role in the
XProtect Corporate Management Client, the role will by
default appear as a view group for use in the access clients.
Example of Smart Client displaying a view with video from six
different cameras (the view is highlighted in red frame) >:
< Example of a
role added in the
XProtect
Corporate
Management
Client:

A view group based on a role will by default only be available to users/groups who have been assigned
to the role in question. You are able to change this; see View Group Rights on page 175.
www.milestonesys.com
Page 134
Management Client
Management Client

A view group based on a role will by default carry the role's
name. Example: If you create a role with the name Building A
Security Staff, it will by default appear in the Smart Client as a
view group called Building A Security Staff. You are able to
change the name; see the following for more information.
Example of the role appearing as a view group in the Smart Client

In addition to the view groups you get when you add roles, you
are able to create as many other view groups as you require.
You can also delete view groups which you do not want to use,
including those automatically created when adding roles. See
the following for more information.

Even though a view group is by default created each time you add a role (see page 164), view groups do
not have to correspond to roles. You are therefore able to add any number of view groups—if required—
and rename or remove each of your view groups if required. This is no matter whether the view groups
were created automatically when adding a role or whether you added them manually.
View Groups from an Access Client User's Perspective
For more information about views from an access client user's perspective, see the separate Smart Client and
Remote Client documentation available on the XProtect Corporate software CD as well as from
www.milestonesys.com.
Adding a View Group

In the Management Client's Site Navigation pane (see page 56), expand the Clients node, right-click
View Groups, and select Add View Group. This opens the Add View Group dialog.

Type the name of the new view group, then click OK.

Optionally; in the Management Client's Overview pane (see page 56), select the added view group, then
in the Properties pane (see page 56) add a description of the view group.
No roles will have the right to use the newly added view group until you have specified such rights; see View
Group Rights on page 175 for more information.
Also, even when you have specified which roles should be able to use the newly added view group, already
connected access client users with the relevant roles must log out and log in again before they will be able to see
the view group.
Renaming a View Group
1.
In the Management Client's Site Navigation pane (see page 56), expand Clients and select View Groups.
2.
In the Management Client's Overview pane (see page 56), right-click the required view group and select
Rename View Group.
3.
Change the view group's name as required, then press the return key on your keyboard.
Access client users already connected must log out and log in again before the name change will be visible.
Removing a View Group
1.
In the Management Client's Site Navigation pane (see page 56), expand Clients and select View Groups.
2.
In the Management Client's Overview pane (see page 56), right-click the required view group and select
Delete View Group.
3.
Click Yes.
www.milestonesys.com
Page 135
Management Client
Management Client
Manage Smart Client Profiles
With Smart Client profiles, XProtect Corporate administrators can control exactly how the Smart Clients should
look and behave and exactly what features/panes Smart Client users are able to work with, and which not.
Controllable user right settings are, for example, panes and options, minimize/maximize options, inactivity timecontrol, remember password or not, view shown after log in, layout of print reports, export path, and much, much
more.
To manage Smart Client profiles in XProtect Corporate, expand the Client folder in the Management Client's Site
Navigation pane (see page 56), and select Smart Client Profiles.
To learn about the relationship between Smart Client profiles, roles and time profiles and how to use these in
connection, see Working with Smart Client Profiles, Roles and Time Profiles later for details.
When configuring a Smart Client profile, the following scenarios are relevant:
Adding and Configuring a Smart Client Profile
You must complete the creation of a Smart Client profile before you can configure it. In other words, the
configuration process is done after the creation of the profile.
1.
In the Management Client's Site Navigation pane (see page 56), expand Client, right-click Smart Client
Profiles.
2.
Select Add Smart Client Profile.... This will open the Add Smart Client Profile dialog.
Tip: As an alternative to using the menu, press the CTRL+N keys on your keyboard.
3.
In the Add Smart Client Profile dialog, type a name and description of the new profile.
4.
Click OK.
5.
In the Overview pane (see page 56), click the profile you just created to configure it. This is done by
adjusting settings on one, more or all of the following tabs: Info, General, Live, Playback, Setup and View
Layouts. See how to later on.
6.
Click OK.
Copying a Smart Client Profile
If you have a Smart Client profile with complicated settings and/or rights and need a similar—or almost similar—
profile, it might be easier to copy an already existing profile and make minor adjustments to the copy than to
creating a new profile from scratch.
1.
In the Management Client's Site Navigation pane (see page 56), expand Client, click Smart Client
Profiles, right-click the required profile in the Overview pane (see page 56), select Copy Smart Client
Profile...
2.
In the dialog that opens, give the copied profile a new unique name and description.
3.
Click OK.
4.
In the Overview pane (see page 56), click the profile you just created to configure it. Adjust settings on
one, more or all of the following tabs: Info, General, Live, Playback, Setup and View Layouts. See
Adding and Configuring a Smart Client Profile section earlier for how to work with each tab.
5.
Click OK.
Deleting a Smart Client Profile
1.
In the Management Client's Site Navigation pane (see page 56), expand Client and right-click Smart
Client Profiles.
www.milestonesys.com
Page 136
Management Client
Management Client
2.
Right-click the unwanted profile in the Overview pane (see page 56), and select Delete Smart Client
Profile.
Tip: Alternatively, press DELETE on your keyboard.
3.
Click Yes.
Renaming a Smart Client Profile
1.
In the Management Client's Site Navigation pane (see page 56), expand Client, and right-click Smart
Client Profiles.
2.
Right-click required role in the Overview pane (see page 56), and select Rename Smart Client Profiles...
Tip: Alternatively, press F2 on your keyboard.
3.
In the dialog that opens, change the name of the profile.
Tip: You are also able to edit the name and description of the profile by simply typing in the Name and
Description fields on the Info tab.
4.
Click OK.
Working with Smart Client Profiles, Roles and Time Profiles
When working with Smart Client profiles, it is important to understand the interaction between Smart Client
profiles, roles (see page 164) and time profiles (see page 161).

Smart Client profiles deal with user right settings in Smart Client

Roles deal with security settings in Smart Client

Time profiles deal with time aspects of the two profiles-types
Together these three features provide unique control and customizing possibilities with regards to Smart Client
user rights.
Note, that the time profiles mentioned here are general time profiles (see page 161). To learn about the time
profiles used in Alarms, see Manage Alarms, on page 182.
Example: Let's say you need a user in your Smart Client setup who should only be allowed to view live
video (no playback) from selected cameras, and only during normal working hours (8.00 to 16.00). One
way of setting this up could be as follows:
1.
Create a Smart Client profile (or use an existing if you have a suitable one). Let's call it Live only.
2.
Specify the needed live/playback settings on Live only.
3.
Create a time profile (or use an existing if you have a suitable one). Lets call it Daytime only. See
Manage Time Profiles on page 161.
4.
Specify the needed time period on Daytime only.
5.
Create a new role (or use an existing if you have a suitable one), see Adding a Role and Manage its
Smart Client and Time Profiles on page 166. Let's call it Guard (Selected cameras).
6.
Specify which cameras Guard (Selected cameras) is allowed to work with. See Specify the Rights of a
Role on page 171.
7.
Finally, assign the Live only Smart Client profile and the Daytime only time profile to the Guard (Selected
cameras) role to connect the three elements.
You now have a mix of the three features creating the wanted result and allowing you room for easy fine-tuning
and adjustments.
Note also that it is possible to do the setup in a different order, for example, creating the role first and then the
Smart Client and the time profile, or any other order preferred.
www.milestonesys.com
Page 137
Management Client
Management Client
How to Adjust Settings on a Smart Client Profil
Setting lets you...

Info ...view and edit the name and description of the selected Smart Client profile, edit priority order of
existing profiles and get an overview of which roles use the profile.
Info tab of Smart Client profiles:
1.
2.
3.
Name and description of profile
(editable)
Arrow-buttons to move profiles up and
down and sorted profile overview
List of roles using the profile

General ...work with general settings for the
selected Smart Client profile; show/hide, miniand maximize, login/-out, startup, timeout, info
and messaging options and much more.

Live ...work with live settings for the selected
Smart Client profile; which live tabs/panes
should be available, should camera playback
and overlay buttons be available, bookmark and
live-related MIP plug-in availability.

Playback ...work with playback settings for the
selected Smart Client profile; which playback tabs/panes should be available, layout of print reports,
export paths, should independent playback be available and bookmark and playback-related MIP plug-in
availability.

Setup ...work with setup settings for the selected Smart Client profile; which general setup
tabs/panes/buttons should be available, setup-related MIP plug-in availability and should it be possible to
edit live video buffering.

View Layouts ...work with view settings for the selected Smart Client profile and which type(s) of views
should be available. Expand the Layouts folder and, if relevant, use the Select All or Select None buttons
as shortcuts when making your selections.
Note that in the Settings column of the General, Live, Playback and Setup tabs, most settings are
selectable as drop downs, however a few should be filled in as a text-fields. In the Locked column, many
selections can be locked so that choices made here cannot be changed by users in the Smart Client.
Manage Matrix Recipients
With Matrix — XProtect Corporate’s integrated solution for distributed viewing of video— you can send video from
any camera on a network operating XProtect Corporate to Matrix recipients.
A Matrix recipient is basically a computer capable of displaying Matrix -triggered video. There are two kinds of
Matrix recipients: computers running a dedicated Matrix Monitor application and computers running the Smart
Client, see page 16.
To see a list of Matrix recipients configured in the Management Client, expand the Client node in the Management
Client's Site Navigation pane (see page 56), then select Matrix. A list of Matrix configurations is displayed in the
Properties pane (see page 56).
Each Matrix recipient, regardless whether it is a computer with the Matrix Monitor or the Smart Client, must be
configured to receive Matrix -triggered video. See the Matrix Monitor and Smart Client documentation for more
information.
Adding Matrix Recipients
To add an existing Matrix recipient— i.e. an existing Matrix Monitor or Smart Client installation— through the
Management Client, do the following:
www.milestonesys.com
Page 138
Management Client
Management Client
1.
In the Management Client's Site Navigation pane (see page 56), expand the Clients node, then select
Matrix.
2.
In the Management Client's Overview pane (see page 56), right-click Matrix Configurations and select
Add Matrix... This opens the Add Matrix dialog.
3.
In the Name field, enter a descriptive name for the Matrix
recipient.
4.
In the Description field, enter a description of the Matrix
recipient.
5.
In the Address field enter the IP address or the host name of the
required Matrix recipient
6.
In the Port field enter the port number used by the Matrix
recipient installation.
7.
In the Password field enter the Matrix recipient's password. Remember that passwords are case
sensitive, i.e. there is a difference between typing amanda and Amanda.
Tip: If in doubt, you can find the port number (default 12345) and password this way: For a Matrix
Monitor application, go to the Matrix Monitor’s Configuration dialog. For a Smart Client, go to the Smart
Client’s Setup tab. See the separate Matrix Monitor or Smart Client documentation for more information.
8.
In the Type field select the type of Matrix recipient you are adding—a Matrix Monitor or a Smart Client.
XProtect Corporate does not verify that the specified port number or password is correct or that the
specified port number, password, or type corresponds with the actual Matrix recipient. Therefore, make
sure that you enter the information correctly.
9.
Click OK to save the settings.
You are now able to use the Matrix recipient in rules. See Defining Rules Sending Video to Matrix
Recipients next for more information.
Defining Rules Sending Video to Matrix Recipients
To be able to send video to Matrix recipients you must— after you have configured a Matrix recipient— include
the Matrix recipient in a rule that triggers the video transmission to the requested Matrix recipient.
1.
Start the Manage Rule and in step 1 select a rule type and, if necessary, a condition in step 2. See
Manage Rules on page 155 for more information.
2.
In Manage Rule's step 3 (Step 3: Actions) select the Set Matrix to view <devices> action.
3.
Click the Matrix link in the initial rule description.
4.
In the Select Matrix Configuration dialog, select the required Matrix recipient, and click OK.
5.
Click the devices link in the initial rule description, and select from which cameras you would like to send
video to the Matrix recipient, then click OK to confirm your selection.
6.
Click Finish if the rule is complete or define— if required— additional actions and/or a stop action.
If you delete a Matrix recipient, any rule that includes the Matrix recipient will stop working.
Advanced Tips for Smart Client Matrix Recipients
If the Matrix recipient is a Smart Client, you can send the same video to Matrix positions in several of the Smart
Client’s views, provided the views' Matrix positions share the same port number and password. Do the following:
1.
In the Smart Client, create the required views, and Matrix positions that share the same port number and
password.
www.milestonesys.com
Page 139
Management Client
Management Client
2.
In the Management Client, add the Smart Client in question as a Matrix recipient.
3.
Include the Matrix recipient in a rule, see Defining Rules Sending Video to Matrix Recipients earlier for
more information.
Rules and Events
About Rules and Events
Events are a central element in XProtect Corporate, primarily used for triggering actions. Actions are configurable
through rules (see page 155).
Example: You create a rule which specifies that in the event of detected motion, the surveillance system
should take the action of starting recording of video from a particular camera.
In the Management Client's Site Navigation pane (see page 56), you are able to work with the following under
Rules and Events:

Rules: Rules are a central element in XProtect Corporate. The behavior of an XProtect Corporate
surveillance system is to a very large extent determined by rules. See Manage Rules on page 155 for
more information.

Time profiles: Time profiles are periods of time defined in the Management Client. Time profiles can be
used when creating rules in the Management Client; for example, you can create a rule which specifies
that a certain action should take place within a certain time profile. See Manage Time Profiles on page
161 for more information.

Notification Profiles: With notification profiles you can set up ready-made e-mail notifications, which
can automatically be triggered by a rule, for example when a particular event occurs. See Manage
Notification Profiles on page 152 for more information.

User-defined Events: User-defined events are custom made events making it possible for users to
manually trigger events in the system or react to inputs from the system.
For a list of events, see the Events Overview on page 148.
User-defined Events
If the event you require is not on Events Overview list, you can create your own user-defined events (see page
163). Such user-defined events can be useful if you want to integrate other systems with your surveillance
system.
Example: With user-defined events, you can use data received from a third-party access control system
as events in XProtect Corporate; the events can subsequently trigger actions. This way, you can, for
example, begin recording video from relevant cameras when somebody enters a building.
User-defined events can also be used for manually triggering events while viewing live video in the Smart Client,
see page 16.
Hardware Configurable Events
Some hardware is capable of creating events themselves. For example, some cameras are themselves able to
detect motion or static/moving objects, and their detections can be used as events in XProtect Corporate. Such
events must obviously be configured on the hardware before they can be used in XProtect Corporate, therefore
they are called hardware configurable events. Read more about hardware configurable events for cameras (see
page 106), inputs (see page 107) and microphones (see page 110) respectively.
www.milestonesys.com
Page 140
Management Client
Management Client
Actions and Stop Actions Overview
When creating rules in the Manage Rule wizard (see Manage Rules on page 155), you are able to select between
a number of different actions:
Example: Selecting actions
Some of these actions will require a subsequent stop action.
Example: If you select the action Start recording, recording will start and potentially continue
indefinitely. Therefore, the action Start recording has a compulsory stop action called Stop recording.
Manage Rule makes sure you specify such stop actions when necessary;
stop actions are typically specified on one of the last steps of the wizard:
Selecting stop actions. In the example, note the compulsory stop action
(selected, dimmed), the non-relevant stop actions (dimmed) and the
optional stop actions (selectable).
Each type of action is described in the following (additional actions may,
however, be available if your XProtect Corporate installation uses add-on
products, special plug-ins, etc.). For each type of action, stop action
information is listed as well:
Action
Description
Start recording
Begin recording, i.e. begin saving video in the database of the selected camera.
When selecting this type of action, Manage Rule will prompt you to specify when
recording should start (either immediately or a number of seconds before the triggering
event/beginning of the triggering time interval) as well as on which devices the action
should take place.
This type of action requires that recording has been enabled on the cameras to which
the action will be linked. Being able to save video from before an event or time interval
is only possible if prebuffering is enabled for the cameras in question. You enable
recording and specify prebuffering settings for a camera on the Record tab (see page
128).
Stop action required: This type of action requires one or more stop actions.
Depending on how the action was triggered, the stop action may be performed either
on an event or after a period of time. In one of the subsequent steps of Manage Rule,
the wizard will automatically prompt you to specify the stop action:
Stop recording. Without this stop action, recording would potentially continue
indefinitely. You will also have the option of specifying further stop actions.
Start feed on
<devices>
Begin video feed from camera devices to XProtect Corporate. When the feed from a
device is started, video will be transferred from the device to XProtect Corporate, in
which case live viewing and recording of video will be possible.
IMPORTANT: While this type of action enables access to selected cameras' video
feeds, it does not guarantee that video will be recorded, as cameras' recording settings
must be specified separately.
When selecting this type of action, Manage Rule will prompt you to specify on which
devices feeds should be started.
Tip: XProtect Corporate has a default rule ensuring that feeds are always started on all
cameras. Note however, that the default rule may have been manually deactivated or
modified. See Manage Rules on page 155 for more information.
Stop action required: This type of action requires one or more stop actions.
Depending on how the action was triggered, the stop action may be performed either
www.milestonesys.com
Page 141
Management Client
Management Client
on an event or after a period of time. In one of the subsequent steps of Manage Rule,
the wizard will automatically prompt you to specify the stop action:
Stop feed. You will also have the option of specifying further stop actions.
Note that using the compulsory stop action Stop feed to stop the feed from a device
means that video will no longer be transferred from the device to XProtect Corporate,
in which case live viewing and recording of video will no longer be possible. However,
a device on which the feed has been stopped will still be able to communicate with the
recording server, and the feed can be started again automatically through a rule, as
opposed to when the device has been manually disabled in the Management Client.
Set live frame rate on
<devices>
Sets a particular frame rate to be used when displaying live video from the selected
cameras, instead of the cameras' default frame rate.
Tip: The default live frame rate of a camera is specified on the Settings tab (see page
131).
When selecting this type of action, Manage Rule will prompt you to specify which frame
rate to set, and on which devices.
Always verify that the frame rate (number of frames per second) you specify is
available on the cameras in question.
Stop action required: This type of action requires one or more stop actions.
Depending on how the action was triggered, the stop action may be performed either
on an event or after a period of time. In one of the subsequent steps of Manage Rule,
the wizard will automatically prompt you to specify the stop action:
Restore default live frame rate. Without this stop action, the default frame rate would
potentially never be restored. You will also have the option of specifying further stop
actions.
Set recording frame
rate on <devices>
Sets a particular frame rate to be used when saving recorded video from the selected
cameras in the database, instead of the cameras' default recording frame rate. When
selecting this type of action, Manage Rule will prompt you to specify which recording
frame rate to set, and on which cameras.
Specifying recording frame rate is only possible for MJPEG, a video codec (technology
for compressing and decompressing data) with which each frame is separately
compressed into a JPEG image. This type of action also requires that recording has
been enabled on the cameras to which the action will be linked. You enable recording
for a camera on the Record tab (see page 128). The maximum frame rate you will be
able to specify will depend on the camera types in question, and on their selected
image resolution.
Stop action required: This type of action requires one or more stop actions.
Depending on how the action was triggered, the stop action may be performed either
on an event or after a period of time. In one of the subsequent steps of Manage Rule,
the wizard will automatically prompt you to specify the stop action:
Restore default recording frame rate. Without this stop action, the default recording
frame rate would potentially never be restored. You will also have the option of
specifying further stop actions.
Start patrolling on
<device> using
<profile> with PTZ
priority <priority>
www.milestonesys.com
Begins PTZ patrolling (the continuous moving of a camera between a number of preset
positions) according to a particular patrolling profile (the exact definition of how
patrolling should be carried out, including the sequence of preset positions, timing
settings, etc.) for a particular PTZ camera with a particular priority.
Page 142
Management Client
Management Client
What is Priority? When several users on a surveillance system wish to control the
same PTZ camera at the same time, conflicts may occur. PTZ priority lets you alleviate
the problem by specifying a priority for use of the selected PTZ camera(s) by
users/groups with the selected role. Specify a priority from 1 to 32.000, where 1 is the
lowest priority. Default PTZ priority is 3000.
If your system is upgraded from an older version of XProtect Corporate, the old values
(Very Low, Low, Medium, High and Very High) have been translated as follows:

Very Low = 1000

Low = 2000

Medium = 3000

High = 4000

Very High = 5000
If your system is upgraded to XProtect Corporate 4.0 (or future versions), rule priority
settings is a new feature. Existing rules (created without priority) automatically get
priority 1. It is strongly recommended to reconsider this lowest possible priority for all
affected rules.
When selecting this type of action, Manage Rule will prompt you to select a patrolling
profile. Only one patrolling profile on one device can be selected; it is not possible to
select several patrolling profiles.
This type of action requires that the device to which the action will be linked is a PTZ
(Pan/Tilt/Zoom) device, and that at least one patrolling profile has been defined for the
device. You define patrolling profiles for a PTZ camera on the Patrolling tab (see page
122).
Stop action required: This type of action requires one or more stop actions.
Depending on how the action was triggered, the stop action may be performed either
on an event or after a period of time. In one of the subsequent steps of Manage Rule,
the wizard will automatically prompt you to specify the stop action:
Stop patrolling. Without this stop action, patrolling would potentially never stop. You will
also have the option of specifying further stop actions.
Pause patrolling on
<devices>
Pauses PTZ patrolling (the continuous moving of a camera between a number of
preset positions). When selecting this type of action, Manage Rule will prompt you to
specify the devices on which patrolling should be paused.
This type of action requires that the devices to which the action will be linked are PTZ
(Pan/Tilt/Zoom) devices, and that at least one patrolling profile has been defined for
those devices. You define patrolling profiles for a PTZ camera on the Patrolling tab
(see page 122).
Stop action required: This type of action requires one or more stop actions.
Depending on how the action was triggered, the stop action may be performed either
on an event or after a period of time. In one of the subsequent steps of Manage Rule,
the wizard will automatically prompt you to specify the stop action:
Resume patrolling. Without this stop action, patrolling would potentially pause
indefinitely. You will also have the option of specifying further stop actions.
Move <device> to
<preset> position with
PTZ priority <priority>
www.milestonesys.com
Moves a particular camera to a particular preset position - however always according to
priority (see earlier tip for a definition of rules). When selecting this type of action,
Manage Rule will prompt you to select a preset position. Only one preset position on
one camera can be selected; it is not possible to select several preset positions.
Page 143
Management Client
Management Client
If your system is upgraded to XProtect Corporate 4.0 (or future versions), rule priority
settings is a new feature. Existing rules (created without priority) automatically get
priority 1. It is strongly recommended to reconsider this lowest possible priority for all
affected rules.
This type of action requires that the devices to which the action will be linked are PTZ
(Pan/Tilt/Zoom) devices, and that at least one preset position has been defined for
those devices. You define preset positions for a PTZ camera on the Presets tab (see
page 124).
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Move to default preset
on <devices> with
PTZ priority <priority>
Moves one or more particular cameras to their respective default preset positions however always according to priority (see tip above for a definition of rules). When
selecting this type of action, Manage Rule will prompt you to select which devices the
action should apply for.
If your system is upgraded to XProtect Corporate 4.0 (or future versions), rule priority
settings is a new feature. Existing rules (created without priority) automatically get
priority 1. It is strongly recommended to reconsider this lowest possible priority for all
affected rules.
This type of action requires that the devices to which the action will be linked are PTZ
(Pan/Tilt/Zoom) devices, and that default preset positions have been defined for those
devices. You define default preset positions for a PTZ camera on the Presets tab (see
page 124).
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Set device output to
<state>
Sets an output on a device to a particular state (activated or deactivated). When
selecting this type of action, Manage Rule will prompt you to specify which state to set,
and on which devices.
This type of action requires that the devices to which the action will be linked each
have at least one external output unit connected to an output port.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Create bookmark on
<device>
Creates a bookmark on live streaming or recordings from a selected device. A
bookmark makes it easy to retrace a certain event or period in time. Bookmark settings
are controlled from the Options dialog (see page 195). When selecting this type of
action, Manage Rule will prompt you to specify bookmark details and select device.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Send notification to
<profile>
www.milestonesys.com
Sends a notification, using a particular notification profile. When selecting this type of
action, Manage Rule will prompt you to select a notification profile, and which devices
to include pre-alarm images from. Only one notification profile can be selected; it is not
possible to select several notification profiles.
Page 144
Management Client
Management Client
Tip: Even though you are only able to select a single notification profile, bear in mind
that a single notification profile may contain several recipients.
This type of action requires that at least one notification profile (see page 152) has
been set up. Pre-alarm images will only be included if e-mail notification is used and
the Include images option has been enabled for the notification profile in question.
IMPORTANT: Pre-alarm images functionality cannot coexist with edge recording (see
page 131). So if a camera is setup to export pre-alarm images it is not possible to
enable edge recording on that camera, and vice versa.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Make new <log entry>
Generates an entry in the rule log (see page 178). When selecting this type of action,
Manage Rule will prompt you to specify a text for the log entry.
Tip: When specifying the log text, you will be able to quickly insert variables, such as
$DeviceName$, $EventName$, etc. into the log message wording.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Start plug-in on
<devices>
Starts one or more plug-ins. When selecting this type of action, Manage Rule will
prompt you to select required plug-ins, and on which devices to start the plug-ins.
This type of action requires that at one or more plug-ins are available on your system.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Stop plug-in on
<devices>
Stops one or more plug-ins. When selecting this type of action, Manage Rule will
prompt you to select required plug-ins, and on which devices to stop the plug-ins.
This type of action requires that at one or more plug-ins are available on your system.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Apply new settings on
<devices>
Changes device settings. When you select this type of action, Manage Rule will prompt
you to select required devices, and you will be able to define required settings on the
devices you have specified.
If defining settings for more than one device, you will only be able to change settings
that are available for all of the specified devices. Example: You specify that the action
should be linked to Device 1 and Device 2. Device 1 has the settings A, B and C, and
Device 2 has the settings B, C and D. In this case, you will only be able to change the
settings that are available for both devices, namely settings B and C.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
www.milestonesys.com
Page 145
Management Client
Management Client
Set Matrix to view
<devices>
Makes video from the selected cameras appear on a computer capable of displaying
Matrix-triggered video (see page 138), i.e. a computer on which either a Smart Client
or a Matrix Monitor application is installed. When you select this type of action, Manage
Rule will prompt you to select a Matrix recipient (see page 138), and one or more
devices from which to display video on the selected Matrix recipient.
This type of action lets you select only a single Matrix recipient at a time. If you want to
make video from the selected devices appear on more than one Matrix recipient, you
should create a rule for each required Matrix recipient.
Tip: By right-clicking a rule in the Rules list you are able to copy and re-use the content
of rules. This way you can avoid having to create near-identical rules from scratch.
As part of the configuration on the Matrix recipients themselves, users must specify the
port number and password required for the Matrix communication. Make sure that the
users have access to this information. The users must typically also define the IP
addresses of allowed hosts, i.e. hosts from which commands regarding display of
Matrix -triggered video will be accepted. In that case the users must also know the IP
address of the XProtect Corporate management server (or any router or firewall used).
Send SNMP trap
Generates a small message which logs events on selected devices. The text of SNMP
traps are auto-generated and cannot be customized. It will typically contain the source
type and name of the device on which the event occurred. To configure who receives
SNMP trap messages, see SNMP Support on page 236.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Save attached image
Ensures that when an image is received from the Images Received event (sent via
SMTP e-mail from a camera) (see page 148, Events Dependent on Hardware
Configuration) it is saved for future usage. In future, other events might also be able to
trigger this action.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
Activate archiving on
<archives>
Starts archiving on one or more archives. When you select this type of action, Manage
Rule will prompt you to select required archives.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
On <site> trigger
<user-defined event>
Relevant mostly within Milestone Federated Architecture (see page 201), but can also
be used in a single server setup. Used for triggering a user defined event on a site normally a remote site within a federated hierarchy.
No compulsory stop action: This type of action does not require a stop action;
although it will be possible to specify optional stop actions to be performed on either an
event or after a period of time.
The following is a brief introduction to examples of typical rules, what you can do with them and how they can be
constructed.
www.milestonesys.com
Page 146
Management Client
Management Client
Create Typical Rules
The following is a brief introduction to examples of typical rules, what you can do with them and how they can be
constructed.

Basic Rules:
o Use Higher Live Frame Rate on Motion: Ensures that when motion is detected on a specific
camera, XProtect Corporate will use a higher than default live frame rate for the camera, and
return to using the camera's default live frame rate when motion is no longer detected. The
effect is higher quality live video whenever there is motion. When the specified part of the day
ends, the PTZ camera will stop patrolling.

PTZ-Related Rules:
o Use Specific PTZ Patrolling Profile during Specific Part of Day: Ensures that during a
specific part of the day, a PTZ (Pan/Tilt/Zoom) camera will patrol according to a specific
patrolling profile (i.e. the exact definition of how patrolling should be carried out, including the
sequence for moving between preset positions, timing settings, etc.). When the specified part of
the day ends, the PTZ camera will stop patrolling.
o
Use Different PTZ Patrolling Profiles for Day/Night: Ensures that during daytime, a PTZ
camera will patrol according to a specific patrolling profile. And during nights, according to
another patrolling profile.
o
Pause PTZ Patrolling and Go to PTZ Preset on Input: Ensures that a specific external input
is activated, a PTZ camera will pause its patrolling, move to a specific preset position, and
remain at the preset position for a specific period of time, after which it will resume patrolling.
Default Rules
XProtect Corporate comes with a number of default rules, ensuring that basic features work without any user
intervention being required.
IMPORTANT: Like other rules, default rules can be deactivated and/or modified as required. The fact that default
rules are present does therefore not in itself guarantee that your XProtect Corporate system will work. Nor does it
guarantee that video feeds or audio feeds will automatically be fed to the XProtect Corporate system, as the
default rules may subsequently have been deactivated or modified.
Default Start Feed Rule
Ensures that video feeds from all connected cameras are automatically fed to the XProtect Corporate system.
IMPORTANT: While the default rule enables access to connected cameras' video feeds immediately upon
installing the system, it does not guarantee that video will be recorded, as cameras' recording settings must be
specified separately.
In case you accidentally delete the default start feed rule, you can recreate it with the following content:
Perform an action in a time interval always start feed on All Cameras
Perform an action when time interval ends stop feed immediately
Default Start Audio Feed Rule
Ensures that audio feeds from all connected microphones and speakers are automatically fed to the XProtect
Corporate system.
IMPORTANT: While the default rule enables access to connected microphones' and speakers' audio feeds
immediately upon installing the system, it does not guarantee that audio will be recorded (see page 128), as
recording settings must be specified separately.
In case you accidentally delete the default start audio feed rule, you can recreate it with the following content:
Perform an action in a time interval always start feed on All Microphones, All
Speakers
Perform an action when time interval ends stop feed immediately
www.milestonesys.com
Page 147
Management Client
Management Client
Default Record on Motion Rule
Ensures that as long as motion is detected in video from cameras, the video will be recorded, provided recording
is enabled (see page 128) for the cameras in question (recording is by default enabled).
IMPORTANT: While the default rule specifies recording based on detected motion, it does not guarantee that
video will be recorded, as individual cameras' recording may have been disabled for one or more cameras. Even
when recording is enabled, bear in mind that the quality of recordings may be affected by individual camera's
recording settings.
In case you accidentally delete the default record on motion rule, you can recreate it with the following content:
Perform an action on Motion Started from All Cameras start recording 3 seconds
before on the device on which event occurred
Perform stop action on Motion Stopped from All Cameras stop recording 3 seconds
after
Default Goto Preset when PTZ Is Done Rule
Ensures that PTZ (Pan/Tilt/zoom) cameras will go to their respective default preset positions after they have been
operated manually.
IMPORTANT: This rule is by default not enabled. Even when the rule is enabled, you must have defined default
preset positions for the required PTZ cameras in order for the rule to work; you do this on the Presets tab (see
page 124).
In case you accidentally delete the default goto preset when PTZ is done rule, you can recreate it with the
following content:
Perform an action on PTZ Manual Session Stopped from All Cameras
Move immediately to default preset on the device on which event occurred
Events Overview
When creating an event-based rule in the Manage Rule wizard (see Manage Rules on page 155), you are able to
select between a number of different events.
Select an Event dialog from Manage Rule
In order for you to get a good overview, selectable events are listed in
groups according to whether they are:

Related to plug-ins:

Dependent on hardware configuration:

Built into XProtect Corporate itself:

Related to recording servers:

User-defined events (see page 163):
Each type of event is described in the following:
Event
Description
Events Related to Plug-ins
Motion
Started
Occurs when XProtect Corporate detects motion in video received from cameras.
This type of event requires that XProtect Corporate’s motion detection is enabled for the cameras
to which the event will be linked. Exactly what constitutes motion depends on the motion detection
settings specified for individual cameras in XProtect Corporate.
In addition to XProtect Corporate’s motion detection, some cameras are— depending on
configuration of the camera hardware— themselves able to detect motion. Such camera-detected
www.milestonesys.com
Page 148
Management Client
Management Client
motion detection can also be used in XProtect Corporate rules. Such events are called Hardware
Configurable, as they do not work until configured on the camera hardware itself. See Events
dependent on hardware configuration in the following.
Motion
Stopped
Occurs when motion is no longer detected in received video. See also the description of the Motion
Started event.
Events Dependent on Hardware Configuration
The configuration on which these events depend may only be possible on some hardware. For example,
only selected cameras may be able to detect tampering or temperature changes.
Audio
Falling
Occurs when the audio signal on an audio-enabled device is falling. For exact information about
what constitutes a falling and a rising signal respectively, refer to documentation for the device in
question.
This type of event requires that at least one device on your system has an audio unit connected.
The event will not work until configured on the hardware itself.
Audio
Passing
Occurs when the state of an audio-enabled device is changed, regardless of which state the device
is changed to.
This type of event requires that at least one device on your system has an audio unit connected.
The event will not work until configured on the hardware itself.
Audio
Rising
Occurs when the audio signal on an audio-enabled device is rising. For exact information about
what constitutes a falling and a rising signal respectively, refer to documentation for the device in
question.
This type of event requires that at least one device on your system has an audio unit connected.
The event will not work until configured on the hardware itself.
Images
Received
Occurs when pre-alarm images are received from a camera (using the Include Images option in
Send notification to <profile> action (see page 141)). Pre-alarm images are available for selected
cameras only; such cameras are capable of sending of one or more single still images from
immediately before an event took place to the surveillance system via SMTP e-mail.
This type of event requires that at least one camera on your system supports pre-alarm images.
The event will not work until configured on the hardware itself.
IMPORTANT: Pre-alarm images functionality cannot coexist with edge recording (see page 131).
So if a camera is setup to export pre-alarm images it is not possible to enable edge recording on
that camera, and vice versa.
Tip: Consider using prebuffering, defined on the Record tab (see page 128), as an alternative to
pre-alarm images.
Input
Activated
Occurs when an external input unit connected to an input port on a device is activated.
This type of event requires that at least one device on your system has an external input unit
connected to an input port. The event will not work until configured on the hardware itself.
Input
Changed
Occurs when the state of an external input unit connected to an input port on a device is changed,
regardless of which state the external input unit is changed to.
This type of event requires that at least one device on your system has an external input unit
connected to an input port. The event will not work until configured on the hardware itself.
Input
Occurs when an external input unit connected to an input port on a device is deactivated.
Deactivated
This type of event requires that at least one device on your system has an external input unit
connected to an input port. The event will not work until configured on the hardware itself.
Motion
Started
(HW)
Occurs when a camera detects motion in its video stream. In addition to XProtect Corporate’s
motion detection, some cameras are— depending on configuration of the camera hardware—
themselves able to detect motion. Such camera-detected motion detection can also be used in
XProtect Corporate rules.
The event will not work until configured on the camera hardware itself. Exact use of camera-based
www.milestonesys.com
Page 149
Management Client
Management Client
motion detection depends on the configuration of the cameras in question.
Motion
Stopped
(HW)
Occurs when a camera no longer detects motion in its video stream. See also the description of
the Motion Started event earlier.
The event will not work until configured on the camera hardware itself. Exact use of camera-based
motion detection depends on the configuration of the cameras in question.
Tampering
Occurs when a device detects that it is being tampered with.
The event will not work until configured on the hardware itself. Exact use of tampering detection
depends on the configuration of the devices in question.
Temperatur Occurs when a device detects a temperature change, that a certain temperature is exceeded, or
e
similar.
The event will not work until configured on the hardware itself. Exact use of temperature detection
depends on the configuration of the devices in question.
Video Lost
Occurs when a device detects that a video signal is lost.
The event will not work until configured on the hardware itself. Exact use of this type of detection
depends on the configuration of the devices in question.
Events Built into XProtect Corporate Itself
Communic
ation Error
Occurs when a connection to a device is lost; or when an attempt is made to communicate with a
device, and the attempt is unsuccessful.
Communic
ation
Started
Occurs when communication with a device is successfully established.
Communic
ation
Stopped
Occurs when communication with a device is successfully stopped.
Feed
Overflow
Started
Feed overflow (a.k.a. Media overflow) occurs when a recording server is unable to process
received video as quickly as specified in the configuration and therefore is forced to discard some
images. If the server is healthy, feed overflow usually happens because of slow disk writes. It can
be resolved either by reducing the amount of data written, or by improving the storage system's
performance. Reduce the amount of written data by reducing frame rates, resolution or image
quality on your cameras. This will in general degrade recording quality. If you are not interested in
that, instead improve your storage system's performance by installing extra drives to share the load
or by installing faster disks or controllers.
Tip: This rare event can be used for triggering actions that will help you avoid the problem, e.g. for
lowering the recording frame rate.
Feed
Overflow
Stopped
Occurs when feed overflow (see description of the Feed Overflow Started event) ends.
Live Client
Feed
Requested
Occurs when a user of the Smart Client or Remote Client requests a live stream from a device.
Output
Activated
Occurs when an external output unit connected to an output port on a device is activated.
The event occurs upon the request— even if the client user's request subsequently turns out to be
unsuccessful, for example because the client user does not have the rights required for viewing the
requested live feed or because the feed is for some reason stopped.
This type of event requires that at least one device on your system has an external input unit
connected to an output port.
Output
Changed
Occurs when the state of an external output unit connected to an output port on a device is
changed, regardless of which state the external input unit is changed to.
This type of event requires that at least one device on your system has an external input unit
www.milestonesys.com
Page 150
Management Client
Management Client
connected to an output port.
Output
Occurs when an external output unit connected to an output port on a device is deactivated.
Deactivated
This type of event requires that at least one device on your system has an external input unit
connected to an output port.
Live Client Occurs when a user of the Smart Client or Remote Client no longer requests a live stream from a
Feed
device.
Terminated
Manual PTZ Occurs when a manually operated PTZ session (as opposed to a PTZ session based on scheduled
Session
patrolling or automatically triggered by an event) is started on a camera.
Started
This type of event requires that the cameras to which the event will be linked are PTZ
(Pan/Tilt/Zoom) cameras.
Manual PTZ Occurs when a manually operated PTZ session (as opposed to a PTZ session based on scheduled
Session
patrolling or automatically triggered by an event) is stopped on a camera.
Stopped
This type of event requires that the cameras to which the event will be linked are PTZ
(Pan/Tilt/Zoom) cameras.
Recording
Started
Occurs when recording is started.
Recording
Stopped
Occurs when recording is stopped.
Settings
Changed
Occurs when settings on a device are successfully changed.
Settings
Changed
Error
Occurs when an attempt is made to change settings on a device, and the attempt is unsuccessful.
Events Related to Recording Servers
Archive
Available
Occurs when an archive (see page 70) for a recording server becomes available after having been
unavailable (see Archive Unavailable next).
Archive
Occurs when an archive (see page 70) for a recording server becomes unavailable, for example if
Unavailable the connection to an archive located on a network drive is lost. When this is the case, it will not be
possible to archive recordings.
You can use the event to, for example, trigger a notification profile so an e-mail notification is
automatically sent to relevant people in your organization.
Archive Not Occurs when an archive (see page 70) for a recording server is not finished with the last archiving
Finished
round when the next is scheduled to start.
Database
Disk Full
Occurs when a database disk is full. A database disk is considered to be full when there is less
than 500 MB of space is left on the disk:
In order to prevent operating system failures due to insufficient disk space, the oldest records in
the database will automatically be deleted for all cameras recording on the disk in question when
less than 500 MB of space is left on the disk containing the database, regardless of any time or
size limits specified for the database. This will help ensure that at least 500 MB of disk space will
be available for operating system use.
Database
Full - Auto
Archive
Occurs when an archive (see page 70) for a recording server is full and needs to auto-archive to
an archive in the hierarchy.
www.milestonesys.com
Page 151
Management Client
Management Client
Database
Repair
Occurs if a database becomes corrupted, in which case XProtect Corporate will automatically
attempt two different database repair methods: a fast repair and a thorough repair.
Database
Storage
Area
Available
Occurs when a storage area (see page 70) for a recording server becomes available after having
been unavailable (see Database Storage Area Unavailable next).
You can, for example, use the event to start recording if it has been stopped by a Database
Storage Area Unavailable event (see next).
Database
Occurs when a storage area (see page 70) for a recording server becomes unavailable, for
Storage
example if the connection to a storage area located on a network drive is lost. When this is the
Area
case, it will not be possible to store recordings.
Unavailable
You can use the event to, for example, stop recording and trigger a notification profile (see page
152) so an e-mail notification is automatically sent to relevant people in your organization.
Failover
Started
Occurs when a failover server (see page 222) takes over from a recording server. A failover server
is a spare recording server which can take over if a regular recording server becomes unavailable.
Failover
Stopped
Occurs when a recording server becomes available again, and is able to take over from a failover
server (see page 222).
User-defined Events
A number of events custom made to suit your system may also be selectable. Such user-defined events
can be used for:
Making it possible for end users to manually trigger events while viewing live video in the Smart Client.
Countless other purposes. For example, you may create user-defined events which will occur if a
particular type of data is received from a device.
For information about how to define user-defined events in the Management Client, see Managing userdefined events (see page 163).
Manage Notification Profiles
With notification profiles you can set up ready-made e-mail notifications, which can automatically be triggered by
a rule (see page 155), for example when a particular event occurs. You are even able to include still images and
AVI video clips in the e-mail notifications.
Note that when using the SMTP Service with .NET 4.0, it is not possible to send attachments over 3 MB. However
two hotfixes (must be run in the listed order) from Microsoft can be found at:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=30226
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31723
TLS (Transport Layer Security) and its predecessor SSL (Secure Socket Layer) is not supported; if the sender
belongs on a server that requires TLS or SSL, e-mail notifications will not work properly. Also, you may be
required to disable any e-mail scanners that could prevent the application sending the e-mail notifications.
Prerequisites
Before you can create notification profiles, you must specify settings for the outgoing SMTP mail server you are
going to use for the e-mail notifications.
Optionally, if you want the notification profile's e-mail notifications to be able to contain AVI video clips, the
compression settings for use when generating the AVI files must also be specified.

Go to the Management Client's menu bar, and select Tools > Options... This will open the Options
window.
a.
For outgoing SMTP Mail Server: Specify settings for the outgoing SMTP mail server on the Mail
Server tab. For more information, see Outgoing SMTP Mail Server Settings on page199 .
www.milestonesys.com
Page 152
Management Client
Management Client
b.
For AVI Compression: Specify compression
settings the AVI Generation tab. For more
information, see AVI Compression Settings on
page 198.
Adding New Notification Profiles
1.
In the Management Client's Site Navigation pane
(see page 56), expand Rules and Events, right-click
Notification Profiles, and select Add Notification
Profile... This will open the Add Notification Profile
wizard.
2.
On the wizard's first step, specify name and
description.
Click Next.
3.
On the wizard's second step, verify that Email is
selected, click Next.
4.
On the wizard's third step, specify recipient, subject,
message text and time between e-mails:
5.
If you want send a test e-mail notification to the
specified recipients, click the Test E-mail button.
6.
If you want to include pre-alarm still images in e-mail notifications under the notification profile, select
Include images, and specify number of images, time between images and whether images should be
embedded in e-mail or not.
7.
If you want to include AVI video clips in e-mail notifications under the notification profile, select Include
images, and specify time before and after event and frame rate.
8.
Click Finish.
IMPORTANT: Pre-alarm images functionality cannot coexist with edge recording (see page 131). So if a
camera is setup to export pre-alarm images it is not possible to enable edge recording on that camera,
and vice versa.
Using Rules to Trigger E-mail Notifications
You use the Manage Rule for creating rules. The wizard takes you through all required steps. You specify the use
of a notification profile during the step on which you specify the rule's
actions:
When selecting the action Send notification to <profile>, you get the option
of selecting the required notification profile. You also get the option of
selecting which cameras any recordings to be included in the notification
profile's e-mail notifications should come from:
< Example only; in Manage Rule, you click the
links to make your selections
Bear in mind that recordings cannot be included in the notification profile's e-mail notifications unless something is
actually being recorded.
If still images or AVI video clips are required in the
notification profile's e-mail notifications, you should therefore
verify that the rule you are creating— or another existing
rule— specifies that recording should take place. The
following example is from a rule which includes both a Start
recording action and a Send notification to ... action:
www.milestonesys.com
Page 153
Management Client
Management Client
For more information about rules in general, see Manage Rules on page 155.
How to Fill in Notification Profile Details

Name: (Compulsory) Type a descriptive name for the notification profile. The name will later appear
whenever you select the notification profile during the process of creating a rule.

Description: (Optional) Type a description of the notification profile. The description will, among other
places, appear when you pause your mouse pointer over the notification profile in the Overview pane's
(see page 56) Notification Profiles list:

Recipients: Type the e-mail addresses to which the
notification profile's e-mail notifications should be sent.
If typing more than one e-mail address, separate addresses with a semicolon. Example:
aa@aaaa.aa;bb@bbbb.bb;cc@cccc.cc

Subject: Type the text you want to appear as the subject of the e-mail notifications.
Tip: You can insert system variables, such as Device name, in the subject and message text field. To
insert variables, click the required variable links in the box below the field.


Message text: Type the text you want to appear in the body of the e-mail notifications. In addition to the
message text, the body of each e-mail notification will automatically contain this information:
o
What triggered the e-mail notification.
o
The source of any attached still images or AVI video clips
Time btw. e-mail: Specify required minimum time (in seconds) to pass between the sending of each email notification. Examples:
o
If specifying a value of 120, a minimum of 2 minutes will pass between the sending of each email notification, even if the notification profile is triggered again by a rule before the 2 minutes
have passed.
o
If specifying a value of 0, e-mail notifications will be sent each time the notification profile is
triggered by a rule. This can potentially result in a very large number of e-mail notifications
being sent. If using the value 0, you should therefore carefully consider whether you want to
use the notification profile in rules
which are likely to be triggered
frequently.

Number of images: Specify the maximum
number of still images you want to include in
each of the notification profile's e-mail
notifications. Default is five images.

Time btw. images (ms): Specify the number
of milliseconds you want between the
recordings presented on the included
images. Example: With the default value of
500 milliseconds, the included images will
show recordings with half a second between
them.

Embed images in e-mail: If selected
(default), images will be inserted in the body
of e-mail notifications. If not, images will be
included in e-mail notifications as attached
files.
Example of e-mail notification with embedded
images. Note that the size of the embedded
images will depend on individual camera settings.
www.milestonesys.com
Page 154
Management Client
Management Client

Time before event (secs.): This setting is used to specify the start of the AVI file. By default the AVI file
will contain recordings from 2 seconds before the notification profile is triggered; you are able to change
this to the number of seconds you require.

Time after event (secs.): This setting is used to specify the end of the AVI file. By default the AVI file
will end 4 seconds after the notification profile is triggered; you are able to change this to the number of
seconds you require.

Frame rate: Specify the number of frames per second you want the AVI file to contain. Default is five
frames per second. The higher the frame rate, the higher the image quality and AVI file size.
Manage Rules
Rules are a central element in XProtect Corporate.
The behavior of an XProtect Corporate surveillance
system is to a very large extent determined by rules.
Rules determine highly important settings, such as
when cameras should record, when PTZ
(Pan/Tilt/Zoom) cameras should patrol, when
notifications should be sent, etc.
Example: A rule specifying that a particular camera should begin recording when it detects motion
You create and manage rules in the Management Client: In the Management Client's Navigation pane, expand
the Rules and Events folder, then select Rules. A Rules list will appear in the Overview pane (see page 56).
The Rules list provides an overview of all existing rules on your system. From the Rules list, you are able to
create rules, edit rules, copy rules, validate rules, etc.
Tip: To view step-by-step descriptions of how to create typically required rules, see Create Typical Rules (see
147).
What You Can Do with Rules
In short, rules specify actions which should be carried out under particular conditions. Example: When motion is
detected (condition), a camera should begin recording (action).
The following are examples of what you can do with rules:

Start and stop recording

Set non-default live frame rate

Set non-default recording frame rate

Start and stop PTZ patrolling

Pause and resume PTZ patrolling

Move PTZ cameras to specific positions

Set output to activated/deactivated state

Send notifications via e-mail

Generate log entries

Generate events

Apply new device settings, for example a different resolution on a camera
www.milestonesys.com
Page 155
Management Client
Management Client

Make video appear in Matrix recipients (Matrix is an integrated system for viewing of video from any
camera on any monitor on a network operating with XProtect Corporate, see page 138)

Start and stop plug-ins

Start and stop feeds from devices
How is stopping the feed from a device different from manually disabling the device? Stopping a
device means that video will no longer be transferred from the device to XProtect Corporate, in which
case neither live viewing nor recording will be possible. However, a device on which the feed has been
stopped will still be able to communicate with the recording server, and the feed from device can be
started automatically through a rule, as opposed to when the device is manually disabled in the
Management Client.
IMPORTANT: Some rule content may require that certain features are enabled for the devices in question. For
example, a rule specifying that a camera should record will not work as intended if recording is not enabled for the
camera in question. Before creating a rule it is therefore highly recommended that you verify that the devices
involved will be able to perform as intended. For a number of typically required rules, such prerequisites are
described in Create Typical Rules (see 147).
How a Rule Is Triggered
Rules can be triggered by two types of conditions:

Events: When events occur on the surveillance system (for example when motion is detected, when the
system receives input from external sensors, etc.)

Time: When specific periods of time are entered (for example Thursday 16th August 2007 from 07.00 to
07.59, or every Saturday and Sunday)
What You Can Cover in a Rule
Your exact number of options depends on the type of rule you want to create, and on the number of devices
available on your system.
Rules, however, provide a high degree of flexibility: You are able to combine event and time conditions, you are
able to specify several actions in a single rule, and very often you are able to create rules covering several or all
of the devices on your system.
You can make your rules as simple or complex as required. For example, you can create very simple time-based
rules:
Example
Very Simple Time-Based Rule: On Mondays between 08.30 and 11.30 (time
condition), Camera 1 and Camera 2 should start recording (action) when the time period begins and
stop recording (stop action) when the time period ends.
And you can create very simple event-based rules, involving events on one device only:
Example
Very Simple Event-Based Rule: When motion is detected (event condition) on Camera
1, Camera 1 should start recording (action) immediately, then stop recording (stop action) after 10
seconds.
However, even though an event-based rule is activated by an event on one device, you can specify that actions
should take place on one or more other devices.
Example
Rule Involving Several Devices: When motion is detected (event condition) on Camera
1, Camera 2 should start recording (action) immediately, and the siren connected to Output 3 should
sound (action) immediately; then, after 60 seconds, Camera 2 should stop recording (stop action), and
the siren connected to Output 3 should stop sounding (stop action).
You can of course also combine events and scheduled times in a rule:
Example
Rule Combining Time, Events, and Devices: When motion is detected (event
condition) on Camera 1, and the day of the week is Saturday or Sunday (time condition), Camera 1 and
Camera 2 should start recording (action) immediately, and a notification should be sent to the security
www.milestonesys.com
Page 156
Management Client
Management Client
manager (action); then, 5 seconds after motion is no longer detected on Camera 1 or Camera 2, the 2
cameras should stop recording (stop action).
The required complexity of rules will vary from organization to organization: Some may require only a number of
simple rules; some may require a mix of simple and complex rules.
Create Many Simple or a Few Complex Rules?
Depending on your organization's requirements, it is often a good idea to create many simple rules rather than a
few complex rules.
Even though this will lead to you having more rules, it will generally make it much easier for you to maintain an
overview of what your rules do.
Keeping your rules simple also means that you will have much more flexibility when it comes to
deactivating/activating individual rule elements— with simple rules, you can deactivate/activate entire rules when
required.
Default Rules
XProtect Corporate comes with a number of default rules, ensuring that basic features work without any user
intervention being required. See Default Rules on page 157.
Creating a New Rule
When you create rules, you will be guided by the wizard Manage Rule
which provides a highly intuitive approach. It helps you stay focused by
listing only relevant options. It ensures that a rule will not contain missing
elements. And finally, based on your rule's content, it automatically
suggests suitable stop actions (i.e. what should take place when the rule
no longer applies), ensuring that you will not unintentionally create a neverending rule.
1.
In the Overview pane (see page 56), right-click the Rules item,
and select Add Rule...:
Tip: Instead of right-clicking to select Add Rule, you can press
CTRL+N on your keyboard.
This will open the wizard Manage
Rule:
The wizard will guide you through
the process of specifying the
content of your rule. The wizard
makes the process interactive, yet
intuitive: based on your main
selections, it will ask you to specify
your exact requirements for the rule.
2.
Begin by specifying a name
(compulsory) and a description
(optional) of the new rule in the
Name and Description fields
respectively.
Tip: Always use a descriptive name
for the rule. Once you have several
rules, you will find that descriptive
names are a great help when
identifying individual rules.
3.
Then select the required type of condition for the rule: either a rule which performs one or more actions
when a particular event occurs, or a rule which performs one or more actions when a specific period of
www.milestonesys.com
Page 157
Management Client
Management Client
time is entered:

Perform an action on <event>
If you select an event-based rule, the lower part of the
wizard window will display an initial rule description:
Click the underlined items in the rule description in order to specify its exact content:
o
Event: Clicking
the event link lets
you select the
event which must
occur in order for
the rule to apply
(for example
Motion Started).
o
Devices/
recording
server/managem
ent server: When
you have selected
the required
event, clicking the
devices/recording
server/manageme
nt server link lets
you specify the
devices on which the event should occur in order for the rule to apply. Depending on your
event specification, you may be able to select from a list of cameras, inputs, outputs, etc. In
the following example illustration, the selectable devices are all cameras:
You specify the required devices by moving them from the Available devices list to the
Selected devices list.
To move a device from the Available devices list to the Selected devices list, either select
the device and click the Add button, double-click the device, or simply drag the device from
one list to the other.
Tip: When devices are grouped into so-called device groups, you can quickly move all
devices in a group simply by moving the group folder.
When the required devices are listed in the Selected devices list, click OK.
You have now specified the exact content of the first
part of the rule description:
Example only; your selections may be different

Perform an action in a time interval
If you select a time-based rule, no more information is required on the wizard's first step.
4.
Click the wizard's Next button to go to the wizard's second step. On the wizard's second step you are
able to define further conditions for the rule.
5.
Select one or more conditions, for example Day of week is
<day>:
Example only; your selections may be different
Depending on your selections, the lower part of the wizard window lets you edit the rule description:
Example only; your selections may be different
Click the underlined items in bold italics to specify their
exact content. For example, clicking the days link in our
example would let you select one or more days of the
week on which the rule should apply.
www.milestonesys.com
Page 158
Management Client
Management Client
6.
Having specified your exact conditions, click the wizard's Next button to move to the next step of the
wizard and select which actions should be covered by the rule.
Depending on the content and complexity of your rule, further wizard steps may let you define further
information, such as stop events and stop actions. For example, if a rule specifies that a device should
perform a particular action during a time interval (for example Thursday between 08.00 and 10.30), the
wizard may ask you to specify what should happen when that time interval ends.
7.
Your rule is by default active, meaning that once you have created it, it will be applied as soon as the
rule's conditions are met.
If you do not want the rule to be active straight away, clear the
Active check box:
Tip: You can always activate/deactivate the rule later.
8.
Click the wizard's Finish button.
Tip: To view step-by-step descriptions of how to create typically required rules, see Create Typical Rules
on page 147.
Editing, Copying and Renaming a Rule
1.
In the Overview pane (see page 56), right-click the required rule.
2.
Select either:

Edit Rule...
—or—

Copy Rule...
—or—

Rename Rule...
depending on your needs.
Example when selecting Edit Rule...
The wizard Manage Rule opens.
3.
In the wizard, rename and/or change the rule as required. If
you selected Copy Rule..., the wizard opens, displaying a
copy of the selected rule.
4.
Click the wizard's Finish button.
Deleting a Rule
Tip: You do not necessarily have to delete
an unwanted rule; you may also just
temporarily deactivate the rule by clearing
the Active check box in the Rule
Information pane for the rule in question,
then saving the setting by selecting the
Management Client's File menu:
If you wish to delete an existing rule, do
the following:
1.
In the Overview pane (see page
56), right-click the rule you wish
to delete, and select Delete
Rule...
Arrow indicates Active check box
www.milestonesys.com
Page 159
Management Client
Management Client
Tip: Instead of right-clicking to select Delete Rule, you may simply press the DELETE key on your
keyboard.
2.
You will be asked to confirm that you wish to delete the rule. If you are sure that you wish to delete the
rule, click the Yes button.
3.
The rule will be removed from the Overview pane's (see page 56) Rules list.
Deactivating and Activating a Rule
A rule is by default active, meaning that XProtect Corporate will apply the rule as soon as the rule's conditions
apply. If you do not want a rule to be active, you can deactivate the rule. When the rule is deactivated, XProtect
Corporate will not apply the rule, even if the rule's conditions apply. A deactivated rule can easily be activated
later.
Deactivating a Rule:
1.
In the Overview pane (see page 56), select the required rule.
2.
Clear the Active check box (see illustration above) in the
properties pane (see page 56):
3.
Save the setting by clicking the Save button in the
Management Client's toolbar (see page 55).
4.
The deactivated rule will be indicated by a
different icon in the Rules list:
Example: Different icon indicates that third rule is deactivated
Activating a Rule
When you want to activate the rule again, simply select the required rule, select the Activate check box, and save
the setting.
Validating Rule(s)
You are able to validate the content of an individual rule or all rules in one go.
Why would I need to validate the content of rules? When you create a rule, the Manage Rule ensures that all
of the rule's elements make sense. However, when a rule has existed for some time, one or more of the rule's
elements may have been affected by other configuration, and the rule may no longer work. For example, if a rule
is triggered by a particular time profile, the rule will not work if the time profile in question has subsequently been
deleted. Such unintended effects of configuration may be hard to keep an overview of; rule validation helps you
keep track of which rules have been affected.
IMPORTANT: Validation takes place on a per-rule basis; each rule is validated in isolation. It is currently not
possible to validate rules against each other (for example in order to see whether one rule conflicts with another
rule), not even if using the Validate All Rules feature.
Furthermore, it is not possible to validate whether configuration of prerequisites outside the rule itself may prevent
the rule from working. For example, a rule specifying that recording should take place when motion is detected by
a particular camera will validate OK if the elements in the rule itself are correct, even though motion detection
(which is enabled on a camera level, not through rules) has not been enabled for the camera in question.
To validate an individual rule or all rules in one go, do the following in the Management Client:
1.
In the Overview pane (see page 56), right-click the rule you wish to validate, and select Validate Rule or
Validate All Rules (depending on your needs):
2.
A simple dialog will inform you whether the rule(s) validated successfully or not. If you chose to validated
more than one rule and one or more rules did not succeed, the dialog will list the names of the affected
rules:
www.milestonesys.com
Page 160
Management Client
Management Client
Manage Time Profiles
These time profiles are general time profiles. To learn about the time profiles used in Alarms, see Manage Alarms
on page 182.
Time profiles are periods of time defined by the administrator. Time profiles can be used when creating rules (see
page 155), for example, a rule specifying that a certain action should take place within a certain time period.
Time profiles are also assigned to roles (see page 164), along with Smart Client profiles (see page 136). Per
default, all roles are assigned the default time profile Always. This means that members of roles with this default
time profile attached has no time-based limits to their user rights in the XProtect Corporate system. An alternative
time profile can easily be assigned to a role, see Adding a Role and Manage its Smart Client and Time Profiles on
page 166. See also Working with Smart Client Profiles, Roles and Time Profiles on page 137, to learn more about
their relationship.
Time profiles are highly flexible: they can be based on one or more single periods of time, on one or more
recurring periods of time, or a combination of single and recurring times. Many users will be familiar with the
concepts of single and recurring time periods from calendar applications, such as the one in Microsoft Outlook.
Time profiles always apply in local time. This means that if your system has recording servers placed in different
time zones, any actions (e.g. recording on cameras) associated with time profiles will be carried out in each
recording server's local time. Example: If you have a time profile covering the period 08.30 to 09.30, any
associated actions on a recording server placed in New York will be carried out when the local time is 08.30 to
09.30 in New York, while the same actions on a recording server placed in Los Angeles will be carried out some
hours later, when the local time is 08.30 to 09.30 in Los Angeles.
Are these time profiles the same as the time profiles (see page 161) found in Alarms (see page 182)? No,
Alarms' Time Profiles are used for defining new alarms or editing existing alarm definitions only.
Can I create a time profile which is identical to an existing Alarm Time Profile (give it the same name,
same description, etc.)? Yes, you can do that.
You create and manage time profiles in the Management Client by expanding the Site Navigation pane (see page
56)'s Rules and Events folder, then selecting Time Profiles. A Time Profiles list will appear in the Overview pane
(see page 56):
Example only
Specifying a Time Profile
1.
In the Time Profiles list, right-click Time
Profiles, and select Add Time Profile...:
Tip: Instead of right-clicking to select Add
Time Profile..., you can press CTRL+N on
your keyboard.
This will open the Time Profile window:
Time and date format may be different on your
system
2.
In the Time Profile window, type a name
for the new time profile in the Name field.
Optionally, type a description of the new
time profile in the Description field.
3.
In the Time Profile window's calendar,
select either Day View, Week View or
Month View, then right-click inside the
www.milestonesys.com
Page 161
Management Client
Management Client
calendar and select either Add Single Time... or Add Recurrence Time...
Tip: If you select a time period by dragging in the calendar before right-clicking, the selected period will
automatically be used in the dialog that appears when you select Add Single Time... or Add Recurring
Time...

Specifying a Single Time
When you select Add Single Time..., the Select Time window appears:
Time and date format may be different on your system
In the Select Time window, specify Start time and End
time. If the time is to cover whole days, select the All day
event box. Then click OK.
Tip: A time profile is able to contain several periods of
time. If you want your time profile to contain further periods
o
f
time, add more single times or
recurring times.

Specifying a Recurring Time
When you select Add Recurring
Time..., the Select Recurring
Time window appears:
Time and date format may be
different on your system
In the Select Time window,
specify time range, recurrence
pattern and range of
recurrence.
Click OK.
Tip: A time profile is able to
contain several periods of time.
If you want your time profile to contain further periods of time, add more single times or
recurring times.
4.
When you have specified the required time periods for your time profile, click the Time Profile window's
OK button. Your new time profile is added to the Time Profiles list in the
Overview pane (see page 56):
New time profile appearing in Time Profiles list
If at a later stage you wish to edit or delete the time profile, you can do that from the Time Profiles list.
Editing a Time Profile
1.
In the Overview pane's (see page 56) Time Profiles
list, right-click the required time profile, and select
Edit Time Profile...:
Tip: Instead of right-clicking to select Edit Time
Profile, you can select the required time profile and
press F2 on your keyboard.
This will open the Time Profile window.
2.
In the Time Profile window, edit the time profile as
required. Remember that a time profile may contain
more than one time period, and that time periods
www.milestonesys.com
Page 162
Management Client
Management Client
may be recurring.
Tip: The small month overview in the top right corner of the Time Profile window
can help you get a quick overview of the time periods covered by the time
profile, as dates containing specified times are highlighted in bold. In the
following example, the bold dates indicate that time periods have been specified
on a number of days, and that a recurring time may have been specified on
Mondays:
Bold dates in month overview indicate that times have been specified on those
dates. You browse months by clicking the small back/forward buttons.
3.
When you have made the required changes to the time profile, click the Time Profile window's OK
button. You will be returned to the Overview pane's (see page 56) Time Profiles list.
Manage User-defined Events
User-defined events are events which are custom made to suit your system. Like other events, user-defined
events can be used in rules (see page 155) in order to trigger actions. Thus, when a user-defined event occurs, a
rule can trigger that one or more actions should take place on the XProtect Corporate system.
Example: When user-defined event 37 occurs, PTZ camera 224 should stop patrolling and go to preset
position 18.
Through roles (see page 164), you define which of your users should be able to trigger the user-defined events;
see Specify Rights of a Role on page 171 for more information.
User-defined events can be used in two ways, simultaneously if required:
 For Providing the Ability to Manually Trigger Events in the Smart Client
In this case, user-defined events make it possible for end users to manually trigger events while viewing
live video in the Smart Client. Thus, when a user-defined event occurs because it is manually triggered
by a Smart Client user, a rule can trigger that one or more actions should take place on the XProtect
Corporate system.

For Providing the Ability to Trigger Events through API
In this case, user-defined events can be triggered from outside the surveillance system. Using userdefined events this way requires that a separate API (Application Program Interface; a set of building
blocks for creating or customizing software applications) is used when triggering the user-defined event.
Authentication through Active Directory is required for using user-defined events this way. This ensures
that even though the user-defined events can be triggered from outside the surveillance system, only
authorized users will be able to do it.
Also, user-defined events can via API be associated with meta-data, defining certain devices or device
groups. This is highly usable when using user-defined events to trigger rules: you avoid having a rule for
each device, basically doing the same thing. Example: A company uses access control, having 35
entrances, each with an access control device. When an access control device is activated, a userdefined event is triggered in XProtect Corporate. This user-defined event is used in a rule to start
recording on a camera associated with the activated access control device. It is defined in the meta-data
which camera is associated with what rule. This way the company does not need to have 35 userdefined events and 35 rules triggered by the user-defined events; a single user-defined event and a
single rule are enough.
When user-defined events are used this way, you may not always want them to be available for manual
triggering in the Smart Client. You can use roles to define which user-defined events should be visible in
the Smart Client; see Specify the Rights of a Role for more information.
Whichever way you choose to use user-defined events, each user-defined event must first be added through the
Management Client:
www.milestonesys.com
Page 163
Management Client
Management Client
Adding a New User-defined Event
1.
In the Management Client's Site Navigation pane (see page 56), expand Rules and Events, and select
User-defined Events.
2.
In the Overview pane (see page 56), right click Events and select Add User-defined Event...
3.
Type a name for the new user-defined event, and click OK. The newly added user-defined event will now
appear in the list in the Overview pane (see page 56).
User rights permitting (see roles on page 164), the user-defined event can now be manually triggered
from Smart Clients. Already connected Smart Client users must log out and log in again before the userdefined event will be visible.
Remember to create one or more rules (see page 155) specifying what should take place when the
custom event occurs.
Editing the Name of an Existing User-defined Event
1.
In the Management Client's Site Navigation pane (see page 56), expand Rules and Events, and select
User-defined Events.
2.
In the Overview pane (see page 56), select the required user-defined event.
3.
In the Properties pane (see page 56), overwrite the existing name.
4.
In the toolbar (see page 55), click Save.
Already connected Smart Client users must log out and log in again before the name change will be
visible.
Deleting an Existing User-defined Event
Bear in mind that deleting a user-defined event will affect any rules in which the user-defined event is used.
A deleted user-defined event will not disappear from Smart Clients immediately; only after Smart Client users log
out.
1.
In the Management Client's Site Navigation pane (see page 56), expand Rules and Events, and select
User-defined Events.
2.
In the Overview pane (see page 56), right click the unwanted user-defined event, and select Delete New
User-defined Event...
3.
You will be asked to confirm that you want to delete the user-defined event; if you are sure, click Yes.
Security
About Roles
Roles determine which of your XProtect Corporate solution's features Users and Groups (see page 168) are able
to use. In other words, roles determine rights and handles security within the application.
You define roles first, then you add users/groups and a Smart Client profile (see page 136) and a time profile (see
page 161) to each role.
One role is predefined in XProtect Corporate, and cannot be deleted: the Administrators role. In addition to the
Administrators role, you are able to add as many roles as required in your organization.
To manage roles in XProtect Corporate, expand the Security folder in the Management Client's Site Navigation
www.milestonesys.com
Page 164
Management Client
Management Client
pane (see page 56), and select Roles.
For more information see:

Manage Users and Groups (see page 168)

Assign and Remove Users and Groups to/from Roles (see page 165)

Manage Roles (see page 166)

Specify Rights of a Role (see page 171).
Note that roles may also determine access to views in access clients; see Manage View Groups on page 134.
About Security
In the Management Client's Site Navigation pane (see page 56), you are able to work with the following under
Security:

Roles: Roles determine which of your XProtect Corporate solution's features Users and Groups (see
page 168) are able to use. In other words, roles determine rights. You create roles first, then you add
users and groups and associate a Smart Client profile (see page 136) and a time profile (see page 161)
to the roles. See About Roles on page 164 for more information.
Assign and Remove Users and Groups to/from Roles
To assign or remove users or groups to/from a role, do the following:
1.
In the Management Client's Site Navigation pane (see page
56), expand Security, and select Roles. Then select the
required role in the Overview pane (see page 56):
2.
In the Properties pane (see page 56),
select the Users & Groups tab:
Assigning Users and Groups to a Role
a.
On the Users & Groups tab, click the Add... button. This will open the Select Users, Computers and
Groups dialog:
b.
Verify that the required object type is
specified. If, for example, you need to add
a computer, click Object Types and mark
Computer. Furthermore, verify that the
required domain is specified in the From
this location field. If not, click the
Locations... button to browse for the
required domain.
c.
In the Enter the object names to select
box, type the required user names, initials,
or other types of identifier which Active Directory will be able to recognize.
Tip: Typing part of a name is often enough. Use the Check Names feature to verify that the names,
initials, etc. you have typed are recognized by Active
Directory.
d.
Click OK. The selected users/groups are now added to
the Users & Groups tab's list of users who have been
assigned the selected role:
www.milestonesys.com
Page 165
Management Client
Management Client
Removing Users and Groups from a Role
Tip: To find out which roles user, groups, or individual group members have, use the Effective Roles feature (see
page 166).
Bear in mind that a user may also have roles through group memberships. When that is the case, you cannot
remove the individual user from the role. Furthermore group members may also hold roles as individuals.
a.
On the Users & Groups tab, select the user or group you want to remove, then click the Remove button
in the lower part of the tab.
Tip: You can select more than one user or group, or a combination of groups and individual users, if
required.
b.
Confirm that you want to remove the selected user(s) or and group(s). Click Yes.
Manage Roles
Roles determine which of your XProtect Corporate solution's features Users and Groups (see page 168) are able
to use. In other words, roles determine rights and handles security within the application.
You define roles first, then you add users/groups and a Smart Client profile and a time profile to each role. Added
roles automatically also become view groups (see page 170).
One role is predefined in XProtect Corporate, and cannot be deleted: the Administrators Role.
In addition to the Administrators role, you are able to add as many roles as required in your organization.
To manage roles in XProtect Corporate, expand the Security folder in the Management Client's Site Navigation
pane (see page 56), and select Roles.
For more information see also Assign and Remove Users and Groups to/from Roles on page 165 and Specify
Rights of a Role on page 171.
Note that roles may also determine access to views in access clients; see Manage View Groups on page 134.
More About Administrators role
The Administrators role is predefined, and cannot be deleted. Users and groups with the Administrators role have
complete and unrestricted access to the entire XProtect Corporate system. For this reason it is not necessary to
specify role settings for the Administrators role. Because the Administrators role has complete and unrestricted
access, it is associated with the Default Smart Client Profile profile and does not have a time profile (see page
161).
You add users and groups to the Administrators role just as with any other role; see Assign and Remove Users
and Groups to/from Roles on page 165.
Role settings tabs are not available for Administrators
role as users and groups with this role have
unrestricted access to the system
IMPORTANT: Users with local machine administrator rights on the computer running the management server will
automatically have administrator rights on the management server. It is therefore important that you verify which
users have local machine administrator rights on the computer running the management server: Only users whom
you trust as administrators of your XProtect Corporate system should have local machine administrator rights on
the computer running the management server.
Adding a Role and Manage its Smart Client and Time Profiles
1.
In the Management Client's Site Navigation pane (see page 56), expand Security, and right-click Roles.
2.
Select Add Role. This will open the Add Role dialog.
3.
In the Add Role dialog, type a name and description of the new role:
www.milestonesys.com
Page 166
Management Client
Management Client
Then click OK.
4.
The new role is added to the Roles list in the Overview
pane (see page 56). By default, a new role does not
have any users/groups associated with it, but it does
have the default profile Default Smart Client Profile and
the default time profile Always associated.
5.
To change the default Smart Client or time profiles, in
the Properties pane (see page 56), click the wanted
drop down dialog.
6.
You are now able to assign users/groups to the role, and
to specify which of XProtect Corporate’s features they
should be able to access. See Assign and Remove
Users & Groups to/from a Role on page 165 and Specify
Rights of a Role (see page 171) for more information.
Copying a Role
If you have a role with complicated settings and/or rights and
need a similar—or almost similar—role, it might be easier to copy
the already existing role and make minor adjustments to the copy
than to creating a new role from scratch.
1.
In the Management Client's Site Navigation pane (see
page 56), expand Security, click Roles, right-click the required role in the Overview pane (see page 56),
select Copy Role...
2.
In the dialog that opens, give the copied role a new unique name and description.
3.
Click OK.
Deleting a Role
Before deleting a role (see page 164), bear in mind that you are able to delete a role even when users and/or
groups have been assigned to the role. It is therefore often a good idea to verify if any users/groups are assigned
to the role before deleting it.

Verifying if Any Users/Groups Are Assigned to a Role
1. In the Management Client's Site Navigation pane (see page 56), expand Security, and rightclick Roles.
2.

Select the required role in the Overview pane (see page 56), then select the Users and Groups
tab in the Properties pane (see page 56). Any users and/or groups assigned to the role will be
listed on the Users and Groups tab.
How to Delete a Role
Deleting a role will not delete a view group based upon the role. For information about deleting view
groups, see Manage View Groups on page 134.
1.
In the Management Client's Site Navigation pane (see page 56), expand Security, and rightclick Roles.
2.
Right-click the unwanted role in the Overview pane (see page 56), and select Delete Role.
Tip: Alternatively, press DELETE on your keyboard.
3.
Click Yes.
Renaming a Role
Renaming a role will not change the name of a view group based upon the role. For information about renaming
view groups, see Manage View Groups on page 134.
www.milestonesys.com
Page 167
Management Client
Management Client
1.
In the Management Client's Site Navigation pane (see page 56), expand Security, and right-click Roles.
2.
Right-click required role in the Overview pane (see page 56), and select Rename Role...
Tip: Alternatively, press F2 on your keyboard.
3.
In the dialog that opens, change the name of the role.
Tip: You are also able to change the description of the role.
4.
Click OK.
Viewing Effective Roles
With the Effective Roles feature, you are able to view all
roles (see page 164) of a selected user or group (see page
168). This ability is especially convenient if you are using
groups; in fact it is the only way of viewing the roles of
individual group members.
1.
2.
Open the Effective Roles window. There are three
ways in which you can open the Effective Roles
window:

From the Management Client's menu bar,
by selecting Tools > Effective Roles...

From the Overview pane (see page 56)
(when working with roles), by right-clicking
anywhere inside the pane, then selecting
Effective Roles...

From the Site Navigation pane (see page 56), by expanding Security, then right-clicking Roles,
then selecting Effective Roles...
In the Effective Roles window's User name field, type the user name of the required user.
Tip: By clicking the browse button to the right of the field, you are able to browse for the user in question,
using Active Directory.
3.
If you typed the user name directly into the User name, click the Refresh button in the lower part of the
window to display the roles of the user.
If you used Active Directory to browse for the user, the user's roles will be displayed automatically.
Manage Users and Groups
In XProtect Corporate, you define roles (see page 164) first, then you add users/groups to the roles.
Roles determine which of XProtect Corporate’s features users and groups are able to use. In other words, roles
determine rights.
Once you have defined roles, you can add users and groups; see Assign and Remove Users & Groups to/from a
Role on page 165.
Prerequisites
In order to be able to add users and groups through the Active Directory service, a server with Active Directory
installed, and acting as domain controller, must be available on your network. Consult your network administrator
if in doubt.
Adding Users and Groups through Active Directory (Normal Way)
Users and groups are normally added from Active Directory, although users can also be added without Active
Directory.
www.milestonesys.com
Page 168
Management Client
Management Client
What is Active Directory? Active Directory is a distributed directory service included with several Windows
Server operating systems; it identifies resources on a network in order for users or applications to access them.
Users as well as groups are specified centrally in Active Directory.
Using Active Directory for adding existing user and group information to XProtect Corporate has several benefits:
The fact that users as well as groups are specified centrally in Active Directory means that you will not have to
create any user accounts from scratch in XProtect Corporate. It also means that you will not have to configure any
authentication of users on XProtect Corporate; authentication is handled by Active Directory.
Active Directory User and Group Concepts
Active Directory uses the concepts of users and groups.

Users
Users are Active Directory objects representing individuals with a user account.
Example:

Groups
Groups are Active Directory objects capable of containing several users. In
this example, the Management Group has three members (i.e. it contains
three users):
Groups can contain any number of users. By adding a group to XProtect
Corporate, you add all of its members in one go. Once the group has been
added to XProtect Corporate, any changes subsequently made to the group
in Active Directory (such as new members added or old members removed)
will immediately be reflected in XProtect Corporate.
Note that a user can be a member of more than one group at a time.
Adding Users Not Using Active Directory
While you primarily add XProtect Corporate users and groups to roles (see page 164) through Active Directory, it
is also possible to add individual users—but not groups—without Active Directory. If not using Active Directory,
note the following:

When installing the management server, the user under which the management server service runs
must be a local PC user on the server. See also Management Server Installation on page .

On the computer running the management server, simple file sharing must be disabled the following
way:
1. On the computer running management server, right-click the Start button, and select Explore.

2.
In the window that opens, select the Tools menu, then select Folder Options...
3.
Select the View tab.
4.
Scroll to the bottom of the
Advanced settings list, and
make sure that the Use
simple file sharing
(Recommended) check
box is cleared.
5.
Click OK, and close the
window.
You add users to roles through the
Management Client almost as when
adding users from Active Directory
(see Assign and Remove Users &
Groups to/from a Role on page 165). However, when adding users, you must refer to particular users on
particular computers, as in the following example where the user USER001 on the computer PC001 is
added:
www.milestonesys.com
Page 169
Management Client
Management Client

When users added this way log in to XProtect Corporate, the user must not specify any server name, PC
name, or IP address as part of their user names. Example of a correctly specified user name: USER001.
Example of an incorrectly specified user name: PC001/USER001. The users should of course still
specify their passwords, etc.
Manage View Groups
The way in which video from one or more cameras is presented in the
access clients (Smart Client (see page 16) and Remote Client (see
page18)) is called a view. A view group is basically a container for one or
more logical groups of such views.
In the access clients a view group is presented as an expandable folder
from which users can select the group, and subsequently the view they
want to see:
Example from Smart Client: Arrow indicates a view group, which contains a logical group
(called Amenities), which in turn contains 3 views.
More about View Groups
By default, each role you define in the Management Client is also created as a view group: when you add a role in
the XProtect Corporate Management Client, the role will by default appear as a view group for use in the access
clients.
Example of Smart Client
displaying a view with video
from six different cameras
(the view is highlighted in
red frame) >
< Example of a role added
in the XProtect Corporate
Management Client

A view group based on a role will by default only be available
to users/groups who have been assigned to the role in
question. You are able to change this; see View Group
Rights on page 175.
Example of the role appearing as a view group in the Smart Client >

A view group based on a role will by default carry the role's
name. Example: If you create a role with the name Building A
Security Staff, it will by default appear in the Smart Client as
a view group called Building A Security Staff. You are able to
change the name; see the following for more information.

In addition to the view groups you get when you add roles,
you are able to create as many other view groups as you
require. You can also delete view groups which you do not
want to use, including those automatically created when
adding roles. See the following for more information.

Even though a view group is by default created each time you add a role (see page 164), view groups do
not have to correspond to roles. You are therefore able to add any number of view groups—if required—
and rename or remove each of your view groups if required. This is no matter whether the view groups
were created automatically when adding a role or whether you added them manually.
View Groups from an Access Client User's Perspective
For more information about views from an access client user's perspective, see the separate Smart Client and
Remote Client documentation available on the XProtect Corporate software CD as well as from
www.milestonesys.com.
www.milestonesys.com
Page 170
Management Client
Management Client
Adding a View Group
1.
In the Management Client's Site Navigation pane (see page 56), expand the Clients node, right-click
View Groups, and select Add View Group. This opens the Add View Group dialog.
2.
Type the name of the new view group, then click OK.
3.
Optionally; in the Management Client's Overview pane (see page 56), select the added view group, then
in the Properties pane (see page 56) add a description of the view group.
No roles will have the right to use the newly added view group until you have specified such rights; see View
Group Rights on page in 175 for more information.
Also, even when you have specified which roles should be able to use the newly added view group, already
connected access client users with the relevant roles must log out and log in again before they will be able to
see the view group.
Renaming a View Group
1.
In the Management Client's Site Navigation pane (see page 56), expand Clients and select View Groups.
2.
In the Management Client's Overview pane (see page 56), right-click the required view group and select
Rename View Group.
3.
Change the view group's name as required, then press the return key on your keyboard.
Access client users already connected must log out and log in again before the name change will be visible.
Removing a View Group
1.
In the Management Client's Site Navigation pane (see page 56), expand Clients and select View Groups.
2.
In the Management Client's Overview pane (see page 56), right-click the required view group and select
Delete View Group.
3.
Click Yes.
Specify Rights of a Role
1.
In the Management Client's Site Navigation pane (see
page 56), expand Security, and select Roles. Then select
the required role in the Overview pane (see page 56):
2.
In the Properties pane (see page 56), specify required
rights for the role on the relevant tabs:
Device Rights
The Device tab lets you specify which features users/groups with the selected role should be able to use for each
device (e.g. a camera) or device group.
The tab is divided into two halves: In the upper half you select the device or device group for which you want to
specify role rights. In the lower half you then specify which of the selected device's or device group's features
users/groups with the selected role should have the right to access.
Remember to repeat for each required device/device group.

Camera-Related Rights
Setting determines whether...
www.milestonesys.com
Page 171
Management Client
Management Client
o
AUX Commands: ...it will be possible to use auxiliary
commands from the Smart Client.
Device tab, with role rights for a selected device, in this case a camera. Note
that you can also select a device group, and specify role rights for the entire
device group in one go.
What are AUX Commands? AUX is short for
Auxiliary. Such commands offer the user control of, for
example, wipers on a camera connected via a video
server. Camera-associated devices connected via
auxiliary connections are controlled from the Smart
Client.
o
(Bookmark) Add: ...it will be possible to add
bookmarks in recorded video from the Smart Client.
o
(Bookmark) Delete: ...it will be possible to delete
bookmarks in recorded video from the Smart Client.
o
(Bookmark) Edit: ...it will be possible to edit
bookmarks in recorded video from the Smart Client.
o
(Bookmark) View: ...it will be possible to view
bookmarks in recorded video from the Smart Client.
o
View live within time profile: ...live viewing of video
from the selected camera(s) will be possible in access clients.
o
Export video as AVI/JPEG: ...the AVI and JPEG export feature can be used when browsing
recorded video from the selected camera(s) in access clients.
o
Export video in database format: ...the database export feature can be used when browsing
recorded video from the selected camera(s) in the Smart Client.
o
Get sequences: ...the Sequences feature can be used when browsing recorded video from the
selected camera(s) in access clients.
o
Playback Video: ...playing back of recorded video from the selected camera(s) will be possible
in access clients.
o
Smart Search: ...the Smart Search feature can be used when browsing recorded video from
the selected camera(s) in the Smart Client.
o
Visible: ...the selected camera(s) will be visible in access clients.
The View live right also requires that the role has been granted the right to view the access clients'
Live tab. This right is granted as part of the application rights.
The Browse video, Export video as AVI/JPEG, Export video in database format, Get sequences,
and Smartsearch rights also require that the role has been granted the right to view the access
clients' Browse tab. This right is granted as part of the application rights.

Microphone-Related Rights
Setting determines whether...
o
Visible: ...the selected microphone(s) will be visible in the Smart Client.
o
Listen to live audio: ...listening to live audio from the selected microphone(s) will be possible
in the Smart Client.
o
Browse audio: ...browsing of recorded audio from the selected microphone(s) will be possible
in the Smart Client.
www.milestonesys.com
Page 172
Management Client
Management Client

o
Export audio: ...the export feature can be used when browsing recorded audio from the
selected microphone(s) in the Smart Client.
o
Get sequences: This feature is currently not supported ...the Sequences feature can be
used when browsing recorded audio from the selected microphone(s) in the Smart Client.
Speaker-Related Rights
Setting determines whether...
o
Visible: ...the selected speaker(s) will be visible in the Smart Client.
o
Listen to live audio: ...listening to live audio from the selected speaker(s) will be possible in
the Smart Client.
o
Browse audio: ...browsing of recorded audio from the selected speaker(s) will be possible in
the Smart Client.
o
Export audio: ...the export feature can be used when browsing recorded audio from the
selected speaker(s) in the Smart Client.
o
Get sequences: This feature is currently not supported ...the Sequences feature can be
used when browsing recorded audio from the selected speaker(s) in the Smart Client.
IMPORTANT: Although what is being said through a speaker can be archive (see page 70), there is
currently no way of playing back or exporting such recorded outgoing audio. Therefore, some of the
speaker-related rights currently have no effect. Features for playing back and exporting recorded
outgoing audio, etc. will be available in subsequent releases as soon as possible.

Input-Related Rights
o

Visible: Determines whether information about the selected input(s) will be visible to users of
the Smart Client as well as users of XProtect Central, an add-on product for providing complete
overview of surveillance system status and alarms.
Output-Related Rights
Setting determines whether...
o
Visible: ...the selected output(s) will be visible in the Smart Client. If visible, the output will be
selectable on a list in the Smart Client.
o
Activate output: ...the selected output(s) can be activated from the Smart Client.
Outputs are selected and activated on the Smart Client’s Live tab. Both rights thus require that the role
has been granted the right to view the Smart Client’s Live tab; this right is granted as part of the
application security rights.
Why are some check boxes filled with squares? Square-filled check boxes can only appear if
you are specifying role rights for a device group, in which case they indicate that the right in
question currently applies for some, but not all, devices within the device group.
Square-filled check boxes indicate that settings currently apply for some,
but not all, devices within a device group
You can still select or clear such square-filled check boxes, but note that your choice will in that case apply for all
devices within the device group. Alternatively, select the individual devices in the device group to verify exactly
which devices the right in question applies for.
PTZ Rights
Relevant only if PTZ (Pan/Tilt/Zoom) cameras are available on your XProtect Corporate system, the PTZ tab lets
you specify which features users/groups with the selected role should be able to use.
The PTZ tab is divided into two halves: In the upper half you select the PTZ camera or device group for which you
want to specify settings— note that only PTZ cameras and device groups containing PTZ cameras are available
for selection. In the lower half you then specify what users/groups with the selected role should be able to do
when operating the selected PTZ cameras in the Smart Client.
www.milestonesys.com
Page 173
Management Client
Management Client
Setting determines whether users/groups...


Allow PTZ Control: ...with the selected role are able to use the pan, tilt and zoom features of the
selected PTZ camera(s).
o
False: Users/groups with the selected role will not be able to use the pan, tilt and zoom features
of the selected PTZ camera(s)
o
True: Users/groups with the selected role will be able to use the pan, tilt and zoom features of
the selected PTZ camera(s)
PTZ Priority: ...have priority for PTZ cameras and how. When several users on a surveillance system
wish to control the same PTZ camera at the same time, conflicts may occur. This setting lets you
alleviate the problem by specifying a priority for use of the selected PTZ camera(s) by users/groups with
the selected role. Specify a priority from 1 to 32.000, where 1 is the lowest priority.
Default PTZ priority is 3000.
Example: You specify that the role Security Manager should have very high priority when using
a PTZ camera, whereas the role Security Assistant should have low priority when using the
PTZ camera. Now, if a user with the role Security Manager and a user with the role Security
Assistant want to control the PTZ camera at the same time, the user with the role Security
Manager will win the ability to control the camera.
If your system is upgraded from an older version of XProtect Corporate, the old values (Very
Low, Low, Medium, High and Very High) have been translated as follows:
o
o
o
o
o
Very Low = 1000
Low = 2000
Medium = 3000
High = 4000
Very High = 5000
Users of the Smart Client are able to stop/resume a patrolling PTZ camera's patrolling through a context
menu in the Smart Client view. This PTZ feature is not regulated by PTZ priority.

Allow activation of PTZ presets: ...with the selected role are able to move the selected PTZ camera(s)
to preset positions.
o
False: Users/groups with the selected role will not be able to move the selected PTZ camera(s)
to preset positions
o
True: Users/groups with the selected role will be able to move the selected PTZ camera(s) to
preset positions
For the rights to work, the role must also be granted the right to view the Smart Client’s Live tab. This
right is granted as part of the application rights. Furthermore, the PTZ camera(s) must be visible in Smart
Clients; you determine as part of the device rights.
Speech Rights
Relevant only if loudspeakers are available on your XProtect Corporate system.
The Speech tab is divided into two halves: In the upper half you select the speaker or device group for which you
want to specify settings. In the lower half you then specify what users/groups with the selected role should be able
to do when operating the selected speaker(s) in the Smart Client.
The following rights are available:

Speak live: Determines whether users with the selected role will be able talk through the selected
speaker(s).

Speak priority: When several Smart Client users want to talk through the same speaker at the same
time, conflicts may occur. This setting lets you alleviate the problem by specifying a priority for use of the
selected speaker(s) by users/groups with the selected role. Specify a priority from Very low to Very high.
www.milestonesys.com
Page 174
Management Client
Management Client
Example: You specify that the role Security Manager should have very high priority when
talking through a speaker, whereas the role Security Assistant should have low priority when
talking through the speaker. Now, if a user with the role Security Manager and a user with the
role Security Assistant want to talk through the speaker at the same time, the user with the role
Security Manager will win the ability to talk.
If two users with the same role want to speak at the same time, the first-come first-served
principle applies.
For the right to work, the role must also be granted the right to view the Smart Client’s Live tab. This right is
granted as part of the application rights. Furthermore, the speaker(s) must be visible in Smart Clients; you
determine as part of the device rights.
Application Rights
The Application tab lets you specify which applications in your XProtect Corporate system users/groups with the
selected role should be able to use. Users must be a member of the Administrator role to have access to the
Management Client. Simply select the required applications:
Setting determines whether users/groups with the selected role are able to use the...

Browse: ...Browse tab in the Smart Client and Remote Client.

Live: ...Live tab in the Smart Client and Remote Client.

Setup: ...selected role Setup tab in the Smart Client and Remote Client.

Status API: ...Status API (Application Program Interface). The Status API is used in connection with
XProtect Central, an add-on product that provides complete overview of surveillance system status and
alarms.

Service Registration API: ...Service Registration API. The Service Registration API is used in
connection with the service channel, a service that enables automatic and transparent configuration
communication between servers and clients in your XProtect Corporate.
User-defined Event Rights
Relevant only if user-defined events (see page 163) are available on your XProtect Corporate system, the Userdefined Events tab is divided into two halves:
In the upper half you select the user-defined event for which you want to specify settings. In the lower half you
then specify what users/groups with the selected role should be able to do with the selected user-defined event in
the Smart Client.

Trigger user-defined event: On the Smart Client’s Live tab it is possible to manually trigger your
surveillance system's user-defined events. This right determines whether users with the selected role
should be able to trigger the selected user-defined event in their Smart Clients.
For the right to work, the role must also be granted the right to view the Smart Client’s Live tab. This right is
granted as part of the application rights.
View Group Rights
The View Group tab lets you specify which view groups (i.e. groups of views in access clients; see Manage View
Groups on page 134 for more information) users/groups with the selected role should be able to use.
The tab is divided into two halves: In the upper half you select the view group for which you want to specify role
rights. In the lower half you then specify how users/groups with the selected role should be able to access the
selected view group.
Setting determines whether users/groups with the selected role are able to...

Visible: ...see the selected view group (and any views contained in the view group) in access clients.
www.milestonesys.com
Page 175
Management Client
Management Client

Modify: ...make changes to the selected view group (and any views contained in the view group) in
access clients.

Delete: ...to delete the selected view group (and any views contained in the view group) in access
clients.

Create subgroups and views: ...create subgroups and views in the selected view group.
Enterprise Server Rights
Specifying role rights on the Enterprise Servers tab is only relevant if you have integrated XProtect Enterprise
servers into your XProtect Corporate solution; see Manage XProtect Enterprise Servers on page 191 for more
information.
The tab is divided into two halves: In the upper half you select the XProtect Enterprise server for which you want
to specify role rights. In the lower half you then specify which authentication settings should apply for
users/groups with the selected role. The process is described in detail in Defining Access Roles for XProtect
Enterprise Servers on page 191.
Matrix Rights
Specifying role rights on the Matrix tab is only relevant if you have configured Matrix recipients (see page 138) on
your XProtect Corporate system.
From the Smart Client it is possible to send video to selected Matrix recipients. The Matrix tab lets you specify
which Matrix recipients should be selectable for this purpose in the Smart Client.
The tab is divided into two halves: In the upper half you select the Matrix recipient for which you want to specify
role rights. In the lower half you then specify if users/groups with the selected role should be able to select the
Matrix recipient in the Smart Client.

Visible: Determines whether users/groups with the selected role will be able to select and send video to
the Matrix recipient from the Smart Client.
Alarms
Specifying role rights on the Alarms tab is only relevant if your use alarms in your system setup to provide central
overview and control of your federated XProtect Enterprise and XProtect Corporate installation. See About Alarms
on page 182.
The Alarms tab lets you specify which alarm rights (i.e. how alarms can be handled in the Smart Client, see
Alarms on page 182 for more information) users/groups with the selected role should have.
The tab is divided into two halves: In the upper half you select the alarm role for which you want to specify alarm
role rights. In the lower half you then specify how users/groups with the selected role should be able to handle the
selected alarms.
Determines whether users/groups with the selected role will be able to do the following in the Smart Client:


Manage:
o
Manage alarms (for example change priorities of alarms and re-delegate alarms to other users)
o
Acknowledge alarms
o
Change state (for example from New to Assigned) of several alarms simultaneously (otherwise
state must be changed on a per-alarm basis)
View:
o
View alarms
o
Print alarms reports.
www.milestonesys.com
Page 176
Management Client
Management Client
MIP
Through the Milestone Integration Software Development Kit (MIP SDK) a third party vendor can develop custom
plug-ins (for example, integration to external Access Control Systems or similar) to XProtect Corporate.
Custom settings for these plug-ins—if any—can be found on the MIP-tab.
System Dashboard
About Storage Overview
To view detailed storage (database and archiving) information about recording servers (see page 70), cameras
(see page 106), speakers (see page 115) and microphones (see page 110), do the following. From the Site
Navigation pane (see page 56), expand System Dashboard, click Storage Overview.
In general, all information showed in Storage Overview are snapshots and are refreshed by clicking on the refresh
button in the lower right corner of the Properties pane (see page 56).
Expand the wanted recording server node in the Overview pane (see page 56) and select the wanted entity as
listed in the following:
Recording Server Database
An overview of the selected databases. Each database is represented by a pie chart and a legend with the actual
numbers. The pie chart shows:

Video recordings and archives
(blue)

Other data, including video
archives from other recording
server (network drives with
archives) (red)

Free space (green)
Under each legend, the disk size is noted:
Example of pie-charts showing database usage for a recording server.
Current Tasks
An overview of the tasks of the selected database, their begin time, estimated end time and progress.
Storage Database
An overview of the selected storage and the database(s) in it. Basically works as on the Storage tab (see page
91) on a recording server. However, it only displays database and archive information, device usage and if the
selected storage is the default storage area.
Camera Group/Microphone Group/Speaker Group Database
A table containing all devices in the selected group, showing their names, storage, the space used in the storage
area and the database status.
Camera/Microphone/Speaker Database
A table containing the selected device, showing its name, storage, the space used in the storage area and the
database status.
www.milestonesys.com
Page 177
Management Client
Management Client
About System Dashboard
This works like the dashboard of a car. Here you get detailed and up-to-date information about current recording
servers, cameras, microphones and their storage areas in your XProtect Corporate system. If needed, you can
get the information on a very detailed level, and for some of the data, it is even possible to get graphical
representation.
See About Storage Overview on page 177 for more information.
Server Logs
Manage Logs
In the Management Client, you are able to view different logs related to the management server. The different
logs have different purposes:

Audit Log records remote user activity.

Event Log records event-related information (see page 140).

Rule Log records rules (see page 155) in which the Make new <log entry> action (see page 141) has
been specified.

System Log records system-related information.
XProtect Corporate has a number of default settings related to the different logs, see Handling Log Settings in the
following. Furthermore, you are able to view logs in a number of different languages, export them, and save the
exported logs as tab delimited text (.txt) files at a location of your choice; see Export a Log in the following.
Viewing Log
To view a log, expand the Management Server Logs item in the Management Client's Site Navigation pane (see
page 56), then select appropriate the log.
Reading Log Content
Each row in a log represents a log entry. A log entry contains a number of information fields, listed and briefly
explained here:

Level
o All logs: Display an icon indicating the level of the log entry:
indicates info
indicates error
indicates warning.

UTC Time
o All logs: Timestamp in coordinated universal time (UTC), an international high-precision time
standard.

Local Time
o All logs: Timestamp in the local time of the XProtect Corporate server.

Description
o All logs: Description of the logged incident.

Source Type
o Rule Log only: Type of equipment on which the logged incident occurred. Since log entries are
administrator-defined and relate to incidents on the XProtect Corporate system, source type will
www.milestonesys.com
Page 178
Management Client
Management Client
normally be System.

Event and System Logs only: Type of equipment on which the logged incident occurred, for example
Management Server or Device.
o Audit Log only: Type of equipment on which the logged incident occurred. Since remote user
access is handled by the XProtect Corporate management server, source type will typically be
Server.

ID

o
All logs: Identification number of the logged incident.
Event Type
o All logs, except Audit Log: Type of event represented by the logged incident.
Tip: For more information about event types, see also the list of events in the events overview.

Source Name
o All logs: Name of the management server, device, etc. on which the logged incident occurred.

Service Name
o Event and Rule Logs only: Name of service on which the logged incident occurred.

Audit Type
o Audit Log only: Type of logged incident.

Granted

o
Audit Log only: Information about whether the remote user action was allowed (granted) or
not.
User
o
Audit Log only: User name of the remote user causing the logged incident.

Location
o Audit Log only: IP address or host name of the computer from which the remote user caused
the logged incident.

Rule Name
o Rule Log only: Name of the rule triggering the log entry.

Generator Type
o Rule Log only: Type of equipment on which the logged incident was generated. Since the log
entries are administrator-defined and relate to incidents on the XProtect Corporate system,
generator type will normally be System.

Generator Name
o Rule Log only: Name (if any) of the equipment on which the logged incident was generated.
Navigating Log
If a log contains more than one page of information, you are
able to navigate between the log's pages by clicking the
buttons in the bottom right corner of the log pane:
lets you move one step towards the log page containing
the most recent log entries.
indicates which page you are currently viewing (e.g.
page 1 of 171). By clicking the button, you are able specify a
page number and go straight to that page.
lets you move one step towards the log page containing the oldest log entries.
www.milestonesys.com
Page 179
Management Client
Management Client
Furthermore,
in the lower left corner lets you jump to a specific date and time in the log.
Changing Log Language
1.
In the bottom part of the log pane, in the Show log in drop down-box, select the wanted language.
You can choose from the following log languages:
2.

Danish

English

French

German

Italian

Japanese

Portuguese

Russian

Simplified Chinese

Spanish

Traditional Chinese.
The log is displayed in the selected language.
Next time your open the log, it is reset to the default language.
Searching Log
To search a log, use the Search criteria box in the top part of the log pane:
1.
Specify your search criteria by selecting the required user name, location, etc. from the lists.
Tip: You can combine selections, or make no selection in certain lists, as required. The more search
criteria you combine, the less search results you will typically get.
2.
Click the Refresh button to make the log page reflect your search criteria.
Tip: To clear your search criteria, and return to viewing all of the log's content, click the Clear button.
Exporting Log
You are able to export logs, and
save the exported logs as tab
delimited text (.txt) files at a
location of your choice.
Example of an exported log .txt file
viewed in Notepad.
You are able to target the exported log content by specifying which log, which log elements, and which time range
to include in the export. For example, you are able to specify that only the System Log's error-related log
messages from between January 2nd 2007 08:00:00 and January 4th 2007 07:59:59 should be included in your
export.
To export a log, do the following:
www.milestonesys.com
Page 180
Management Client
Management Client
1.
Expand the Management Server Logs item in the Management Client's Site Navigation pane (see page
56), and select the required log.
2.
If you want to target the exported log's content, select
the required criteria in the Search criteria section above
the log. For example, you may select that your export
should only contain log messages at a particular level,
such as errors or warnings.
Remember to click the Refresh button to make the log
page reflect your selected criteria.
3.
In the Management Client's menu bar, select Action >
Export Log... This will open the Export Log window:
4.
In the Export Log window's Filename field, specify a
name for the exported log file.
By default, exported log files will be saved in your My
Documents folder. However, you are able to specify a
different location by clicking the browse button
next to the field.
5.
Any criteria you have selected in order to target the content of the exported
log will be listed in the Filters field. The field is non-editable; if you find that you
need to change your criteria, close the window, and repeat steps 2-4.
6.
Specify the time period you want the export to cover. You do this by specifying
the required boundaries in the Start date and time and End date and time
fields respectively. By clicking the arrow, you are able to select the required
date from a calendar:
To specify an exact time, overwrite the required time elements
(hours:minutes:seconds) with the required values. In the following example, the
hours element is being overwritten:
Tip: When you have selected time elements in order to overwrite them, you are also able to use your
keyboard's UP ARROW and DOWN ARROW keys to increase/reduce the numbers in increments of one
unit.
7.
Click the Export button to export the required log content to the required location.
Handling Log Settings
XProtect Corporate has a number of default settings related to its logs. To verify or change these settings, do the
following:
1.
Go to the Management Client's menu bar, and select Tools > Options...
2.
In the Options window, select the General tab.
One of the tab's settings applies for all types of
logs:

3.
Number of log rows to retrieve per page:
Lets you specify the number of log rows you
want to view on a single log page. If a log
contains more than the specified number of
rows, you will be able view the remaining
rows on subsequent log pages.
Go to the Options window's Management Server
Logs tab:
In the tab's left box, select the required log. The
selected log's settings are displayed in the tab's
right box:
www.milestonesys.com
Page 181
Management Client
Management Client

Log enabled: Lets you enable/disable the selected log. By default, all logs are enabled.
The System Log and Audit Log cannot be disabled by clearing the box.

Days to keep log entries: Lets you specify how many days the log's information should be kept for.
Default is 365 days.
Excess log content will be deleted if the log reaches its maximum allowed size (see Maximum
number of entries) before the specified number of days is reached.

Maximum number of entries: Lets you specify the maximum size of the log. Default is one million
entries.
Excess log content will be deleted if it reaches its maximum allowed age (see Days to keep log
entries) before the specified number of entries is reached.
For the Audit Log, you will furthermore see:
4.

Enable user access logging: Lets you include detailed information about specific user actions in
the audit log, e.g. about users' viewing of live video (and associated audio), PTZ actions, activation
of output and events, export, playback of video and audio, use of playback features, any denied
access to features, etc.

Playback sequence logging length: Lets you specify the number of seconds to pass for viewed
images to be considered to be within the same sequence. Specifying a high number of seconds may
help limit the number of viewed sequences logged, and thus reduce the size of the audit log.

Records seen before logging: Lets you specify the number of records to be viewed before logging
the sequence.
Click OK.
Alarms
Manage Alarms
Based on functionality handled in the XProtect event server, the Alarms feature provides central overview, control
and scalability of alarms in any number of federated XProtect Enterprise and XProtect Corporate installations
throughout your organization. It can be configured to generate alarms based on either:

Internal system related events;
For example, motion, server responding/not responding, archiving problems, lack of disk space, etc.

External integrated events;
This group can consist of several types of external events:
o
Analytics events;
Typically data received from an external third-party video content analysis (VCA) providers.
o
Milestone Integration Platform plug-in events;
Through the Milestone Integration Software Development Kit (MIP SDK) a third party vendor
can develop custom plug-ins (for example, integration to external Access Control Systems or
similar) to XProtect Corporate.
To ease overview, delegation and handling of alarms, these will appear in the Smart Client’s alarm list and can, if
relevant, be integrated with map functionality. Alarms is thus a powerful monitoring tool, providing instant
overview of alarms and possible technical problems.
Are these time profiles the same as the general Time Profiles feature found under Rules and Events? No,
Alarms' time profiles are used for defining new alarms or editing existing alarm definitions only.
More About Alarms...
Alarm configuration includes among other things:
www.milestonesys.com
Page 182
Management Client
Management Client

Dynamic role-based setup of alarm handling

Central technical overview of all components: servers, cameras, and external units

Setup of central logging of all incoming alarms and system information

Handling of plug-ins, allowing customized integration of other systems, for example external access
control or VCA-based systems.
What is a VCA-based system? VCA-based systems provide third-party video content analysis, spanning from
face recognition, over advanced motion detection, to complex behavioral analysis, where various types of
abnormal behavior, both of humans and vehicles, can be detected. VCA systems and their output can seamlessly
be integrated with—and hook into—XProtect Corporate and be used for, for example, triggering alarms. Within
XProtect Corporate, the events resulting from VCA systems are called analytics events.
In general, alarms are controlled by the visibility of the object causing the alarm! This means that four possible
aspects can play a role with regards to alarms and who can control/manage them and to what degree.

Source/device visibility. If the device causing the alarm is not set to be visible to the user's role, the
user will not be able to see the alarm in the alarm list in the Smart Client. See Device Rights on page
171.

If user-defined events (see page 163) are available in your XProtect Corporate system, right to trigger
user-defined events might be an issue. This right determines if the user's role can trigger selected userdefined events in the Smart Client. See Specify Rights of a Role on page 171, User-defined Events
Rights.

External plug-ins. If any external plug-ins are set up in you system, these might control users rights to
handle alarms.

General role rights determine whether the user is allowed to only view or also to manage alarms. What
a user of Alarms can do with alarms depends—like much else—on the user's role and on settings
configured for that particular role. See Specify Rights of a Role on page 171, Alarms.
Illustration: How do the Alarms Feature and the Event Server work?
Legend:
1.
Surveillance System
2.
XProtect Corporate
Management Client
3.
Smart Client
4.
Alarm Configuration
5.
Alarm Data Flow
FAQs: XProtect Central and Alarms - Same Thing?
Does Alarms cover the same functionality as XProtect Central? Yes, to a large extend, since configuration of
former XProtect Central functionality is now located in Alarms. XProtect Central was an independent product
consisting of two parts; a dedicated server and a number of dedicated clients. Alarms, on the other hand, is an
integrated part of XProtect Corporate. Thus, Alarms configuration uses the Management Client's users, groups
and roles functionality. This means that much configuration needed in XProtect Central is redundant with Alarms.
Client-wise Alarms uses the Smart Client—among other things its view and map feature.
www.milestonesys.com
Page 183
Management Client
Management Client
However, Alarm Definitions, Time Profiles and Log Settings must still be configured in the Management Client
(under Alarms) and are more or less unchanged from XProtect Central. Finally, under Roles, alarm security
settings must be set.
Can I reuse old alarm and map definitions from XProtect Central? No, you will have to redefine your alarms
and maps in Alarms.
Can I reuse old map definitions from XProtect map server? Yes, your old map definitions will be available in
Alarms.
Does Alarms cover the same functionality as XProtect Analytics Generic VA? Yes, to a large extend, since
what was before a plugin to XProtect Analytics is now an integrated part of the event server and covers the same
functionality. See also Does Alarms cover the same functionality as XProtect Central? FAQ earlier.
Managing Alarms
IMPORTANT: Alarms can register and handle events from both XProtect Corporate and XProtect Enterprise
system servers, but they must all be run as federated sites (see page 201) for Alarms to work.
When a particular event (for example Motion Detected) is registered on your surveillance system, Alarms can be
configured to cause this alarm to appear in the Smart Client. You must define alarms before you can use them
and they are defined based on events registered on your XProtect Corporate (and possibly XProtect Enterprise )
system(s) servers.
Tip: You can even use user-defined events for triggering alarms and if required, the same event can be used to
trigger several different alarms.

Creating a New Alarm
1.
In the Management Client's Site Navigation pane (see page 56), expand Alarms, right-click Alarm
Definitions. Select Add New.... The Alarm Definitions Information window appears.
2.
Fill in the following properties:

Enable: Lets you enable the Alarms feature.

Name: Lets you type a name for the alarm. The alarm's name will appear whenever the alarm
is listed.
Tip: Alarm names do not have to be unique, but using unique and descriptive alarm names are
advantageous in many situations.

Description: Lets you type a description text (optional).

Triggering event: This list offers both system-related events andplug-ins. It lets you select the
(event) message which should be used when the alarm is
triggered:
List of selectable triggering events; the highlighted one is
created and customized using analytics events.

3.
Sources: Lets you select which cameras and/or other devices,
including plug-in defined sources (VCA, MIP, etc), the event
should originate from in order to trigger the alarm. Your options
depend upon which type of event you have selected.
Next, for alarm activation, choose between Time profile and Event
based.

Time profile: If you select Time profile, you must select when the alarm should be enabled for
triggering. If you have not defined alarm time profiles (see later in this topic), you will only be
able to select Always. If you have defined one or more time profiles, they will be selectable from
this list.

Event based: If you select Event based, you must select which events should start and stop
the alarm. Events available for selection are hardware events defined on cameras, video
www.milestonesys.com
Page 184
Management Client
Management Client
servers and input (see page 148). Also global/manual event definitions (see page 140) can be
used.
Note that when selecting Event based it is not possible to define alarms based on outputs—
only on inputs.

Related cameras: Lets you select (a maximum of 15) cameras for inclusion in the alarm
definition even though they are not themselves triggering the alarm. This can be relevant, for
example, if you have selected an external event message (such as a door being opened) as the
source of your alarm. By defining one or more cameras near the door, you could attach the
cameras' recordings of the incident to the alarm.

Initial alarm owner: Lets you select a default user responsible for the alarm. You can only
select from users allowed to view all cameras and/or other devices selected as source(s) for
the event causing the alarm.

Initial alarm priority: Lets you select a priority (High, Medium or Low) for the alarm. Priorities
can be used for sorting purposes and workflow control in the Smart Client.

Event triggered by alarm: Lets you define an event to be triggered by the alarm in the Smart
Client (if needed).

Auto-close alarm: Lets you select if the alarm should automatically be closed upon a particular
event. This is possible for alarms triggered by some (but not all) events.
Tip: If you want to disable the new alarm from the beginning, clear the Enable check box in the upper
right corner before saving.
4.

In the toolbar (see page 55), click Save.
Editing Existing Alarms
1.
Click an existing alarm to edit it.
Managing Alarms' Time Profile
These time profiles only apply when working with Alarms. To learn about general Time Profiles, see Manage Time
Profiles on page 161.
Time profiles are periods of time used when creating new alarms or editing existing alarm definitions. They are
defined in Alarms. Once defined, you can, for example, create a time profile which covers the period from 2.30
PM til 3.30 PM on Mondays, and then use the time profile
to make sure that certain alarm definitions are only
enabled within the period of time covered by the time
profile.
Time profiles are highly flexible. They can be based on one
or more single periods of time, on one or more recurring
periods of time, or a combination of single and recurring
times. Many users will be familiar with the concepts of
single and recurring time periods from calendar
applications, such as the one in Microsoft Outlook®.
Time profiles always apply in the XProtect Corporate
Server's local time.
Can I create a time profile which is identical to an
existing time profile under Rules and Events (give it
the same name, same description, etc.)? Yes, you can
do that.
Time and date format may be different on
your system

Creating a New Alarms Time Profile
1. In the Management Client's Site Navigation
pane (see page 56), expand Alarms, rightclick Time Profiles.
www.milestonesys.com
Page 185
Management Client
Management Client
2.
In the Time Profile Information window, type a name for the new time profile in the Name field.
Optionally, type a description of the new time profile in the Description field.
3.
In the Time Profile Information window's calendar, select the Day View, Week View, or Month View
tab, then right-click inside the calendar and select either Add Single Time... or Add Recurring Time...
a.
If you select Add Single Time..., the Add Single Time dialog appears:
Time and date format may be different on your system
b.
Specify Start time and End time. If the time is to cover whole days, select the All day event
box. When ready, click OK.
—or—
a.
If you select Add Recurring Time..., the Add Recurring Time dialog appears:
Time and date format may be different on your system
b.
Specify time range, recurrence pattern, and range of recurrence. When ready, click OK.
Tip: A time profile is able to contain several periods of time. If you want your time profile to
contain further periods of time, simply add more single times or recurring times.
Tip: If you select a time period by dragging in the calendar before right-clicking, the selected
period will automatically be used in the dialog that appears when you select Add Single Time...
or Add Recurring Time...
4.
When you have specified the required time periods for your time profile, click Save. You can now
use the time profile when defining
new alarms or editing existing
alarm definitions. When
defining/editing the alarm, simply
select the required time profile in
the Alarm Definition dialog's
Enabled list:
Time and date format may be different on your system
www.milestonesys.com
Page 186
Management Client
Management Client

Editing Existing Alarms Time Profiles
Click an existing time profile to edit it.
Tip: In the Time Profile Information window, edit the time profile as required. Remember that a time profile
may contain more than one time period, and that time periods may be recurring.
Tip: The small month overview in the top right corner of the Time Profile Information
window can help you get a quick overview of the time periods covered by the time
profile, as dates containing specified times are highlighted in bold. In the following
example, the bold dates indicate that time periods have been specified on several
days, and that a recurring time may have been specified on Mondays:
Editing Alarm, Event and Log Settings
With Alarms you can edit settings for alarms, events, and alarm logs.
1. In the Management Client's Site Navigation pane (see page 56), expand Alarms, General Settings
andedit the following settings:

Keep closed alarms for: Lets you select the number of days to keep closed alarms, i.e. alarms in
the states Closed, Ignore, and Reject.

Keep all other alarms for: Lets you select the number of days for which to keep all other alarms,
i.e. alarms not in the states Closed, Ignore, and Reject.
IMPORTANT: Alarms always have associated timestamps. Furthermore, if the alarm is camerabased, the timestamp has an image from the relevant video recording attached. While the alarm
information itself is stored on the XProtect event server, the video recordings corresponding to the
attached image are fetched from the relevant surveillance system server when users wish to view
them. Therefore, if it is vital to have access to video recordings from all your alarms, make sure that
video recordings from relevant cameras are stored on relevant surveillance system servers for at
least as long as you intend to keep alarms on the event server.

Keep events for: Lets you specify the number of days for which to keep events.

Keep logs for: Lets you specify the number of days for which to keep the Alarms log.
On all the above, default setting is 30 days, but you can define any number up to 99.999 days,
server space permitting. The value 0 can be used to indicate keep closed alarms indefinitely, server
space permitting

Log server communication: Select check box if you want to save a separate log of server
communication in addition to the regular log, for the number of days specified.
2. In the toolbar (see page 55), click Save.
Managing Analytics Events
Analytics events are typically data received from an external third-party video content analysis (VCA) providers.
Using analytics events as basis for alarms is basically a three step process:
1. Part one, enabling the analytics events feature and setting up its security. A list of allowed addresses
can be used to control who can send event data to the system and which port the server listens on.
2. Part two, creating the analytics event, possibly with a description of the event, and test it.
3. Part three, using the analytics event as the source of an alarm definition.
Furthermore, to use VCA-based events, a third-party VCA tool is required for supplying data to XProtect
Corporate. Which VCA tool to use is entirely up to you, as long as the data supplied by the tool adheres to the
applied formatting rules set out in the Milestone Analytics Events; Developers Manual. Contact Milestone for more
details.
www.milestonesys.com
Page 187
Management Client
Management Client
Third-party VCA tools are developed by independent partners delivering solutions based on a Milestone open
platform. These solutions can impact performance on XProtect Corporate.

Creating a New Analytics Event
1. In the Management Client's Site Navigation pane (see page 56), expand Alarms, right-click Analytics
Events. Select Add New.... The Analytics Events Information window appears.
2. Type a name for the event in the Name field.
3. Optionally, type a description text in the Description field.
Tip: Description texts can, for example, be used to give more background info on the event and how it is
used. The description is not visible to users of the Smart Client.
4. In the toolbar (see page 55), click Save.
5. Optionally, you can test the validity of the event by clicking the Test Event button. See Testing an
Analytics Event in the following.
Tip: You can continually correct errors indicated in the test and run the test as many times as you wish
and from anywhere in the process.

Editing an Existing Analytics Event
1. To edit an existing analytics event, click it. This opens the Analytics Event Information window where you
can edit relevant fields.
2. Optionally, you can test the validity of the event by clicking the Test Event button. See Testing an
Analytics Event in the following.
Tip: You can continually correct errors indicated in the test and run the test as many times as you wish and
from anywhere in the process.

Testing an Analytics Event
Optionally, you can test the validity of an event by clicking the Test Event button.
Tip: You can carry out this test at any step of the analytics event creation/editing process and as many times
as you wish.
1. To test an analytics event you must first create one, see Creating a New Analytics Event earlier.
2. Click on an existing analytics event. This opens the Analytics Event Information window.
3. In the Analytics Event Information window, click the Test Event button.
This opens the Test Analytics Event
window which goes through a number
of conditions that must be successful
for analytics events to work. The
window consists of two tabs:
Example of the Test Analytics Event
window. May look different in different
contexts.
The first tab, the Task tab, lists these
conditions in the order they are tested:
Step 1:
Changes saved: If the event is new, is
it saved? Or if there are changes to the event name, are these changes saved?
Step 2:
Analytics Events enabled: Is the Analytics Event feature enabled?
Step 3:
Address allowed: Is the IP address/hostname of the machine sending the event(s) allowed (listed on
the address list)?
www.milestonesys.com
Page 188
Management Client
Management Client
Step 4:
Analytics event used in alarm definition: Is the analytics event used actively in any alarm definitions?
Step 5:
Send analytics event: Did sending a test event to the event server succeed?
Each step is marked by either failed:
or successful:
.
The second tab, the Errors tab, shows a list of errors corresponding to any possibly failed conditions.
Possible errors are:
Error corresponding to step 1:
Save changes before testing analytics event. Solution/Explanation: Save changes.
Error corresponding to step 2
Analytics events have not been enabled. Solution/Explanation: Enable the Analytics Event feature.
Errors corresponding to step 3:
The local host name must be added as allowed address for the Analytics Event service.
Solution/Explanation: Add your machine to the list of allowed IP addresses/hostnames.
Error resolving the local host name. Solution/Explanation: The IP address/hostname of the
machine cannot be found or is invalid.
Error corresponding to step 4:
Analytics event is not used in any alarm definition. Solution/Explanation: Use the analytics event in
an alarm definition.
Errors corresponding to step 5:
Event Server not found. Solution/Explanation: Unable to find event server on the list of registered
services.
Error connecting to event server. Solution/Explanation: Unable to connect to event server on the
stated port (most likely due to network problems, event server being stopped or similar).
Error sending analytics event. Solution/Explanation: Connection to event server established but
event cannot be sent (most likely due to network problems, for example time out).
Error receiving response from event server. Solution/Explanation: Event sent to event server but
no reply received (most likely due tonetwork problems or port being busy (see the event server log,
typically located at ProgramData\Milestone\XProtect Event Server\logs\—can be opened in
Microsoft Notepad or similar tool)).
Analytics event unknown by event server. Solution/Explanation: event server does not know the
event (most likely due to the event—or changes to the event—not having been saved).
Invalid analytics event received by event server. Solution/Explanation: Event format is somehow
incorrect.
Sender unauthorized by event server. Solution/Explanation: Most likely because your machine is
not on the list of allowed IP addresses/hostnames.
Internal error in event server. Solution/Explanation: Event Server error, see the event server log,
typically located at ProgramData\Milestone\XProtect Event Server\logs\—can be opened in
Microsoft Notepad or similar tool).
Invalid response received from event server. Solution/Explanation: Response is invalid (possibly
due to port being busy or network problems (see the event server log, typically located at
ProgramData\Milestone\XProtect Event Server\logs\—can be opened in Microsoft Notepad or
similar tool)).
Unknown response from event server. Solution/Explanation: Response is valid but not understood
(possibly due to port being busy or network problems (see the event server log, typically located at
ProgramData\Milestone\XProtect Event Server\logs\—can be opened in Microsoft Notepad or
similar tool)).
Unexpected error. Solution/Explanation: Not likely to occur. If the accompanying text in the error
does not provide enough information and problem continues, please contact your system provider
Milestone Support (support@milestonesys.com) for help.
www.milestonesys.com
Page 189
Management Client
Management Client
4. Remember to save any changes made during the test.
In the toolbar (see page 55), click Save.
5. When done, check the presence of your test event in the Smart Client's Alarm list. Sort by type: Test
Alarm. See Smart Client documentation for more details.

Editing Analytics Events Settings
1. In the Management Client's Site Navigation pane (see page 56), expand Alarms, select Analytics Events
Settings. The Configurationwindow appears.
2. You are now able to edit the following settings:

Enable: Lets you specify whether this feature should be enabled or not. As default, the service is
disabled.

Port: Lets you specify the port used by this service. Default port is 9090.
Make sure that relevant VCA tool providers also use this port number. If you change the port
number, remember to make sure that these providers also change their port number!

All network addresses or Specified network addresses: Lets you specify whether—in principle—
events from all IP addresses/hostnames are accepted, or only events from IP addresses/hostnames
specified in a list (see the following) are allowed.

Address list: Lets you specify a list of trusted IP addresses/hostnames that you want this service to
recognize. The list is used to filter and allow incoming data so that only events from certain IP
addresses/hostnames are allowed. Both Domain Name System (DNS), IPV4 and IPv6 (see page
239) address formats can be used in the list.
You have two ways of adding addresses to your list: Either by manually entering each IP address or
hostname, or by importing an external list of addresses.
o
Manual entering: Type the required IP address/hostname in the address list. Repeat for
each required address.
o
Import: Click the Import... button to browse for the required external list of addresses. To
be able to import an external list, the external list must have been saved in a .txt file format
and each IP address or hostname must appear on a separate line in the .txt file. Windows’
simple text editor Microsoft® Notepad is an excellent tool for creating such .txt files.
3. In the toolbar (see page 55), click Save.
How to Set Up Alarms Using Enterprise Slaves


User name and password
If your surveillance setup includes one or more XProtect Enterprise slaves and you wish to include one or more of
these in your Alarms, setup, it is important that the login name and password specified when adding the slave, is
the same as used in the XProtect Central add-on in the XProtect Enterprise Server.
Otherwise, the XProtect event server is unable to login to the XProtect Central add-on in XProtect Enterprise and
collect status information.
Port number
Furthermore, if at some point you have changed port number settings in the XProtect Central add-on in the
XProtect Enterprise Server, you must update port number information in the XML file containing configurations for
the event server in the same way.
This is done directly in the affected configuration file.
1. On the server running the XProtect event server, click Start > Control Panel > Administrative Tools >
Services.
www.milestonesys.com
Page 190
Management Client
Management Client
2. Right-click the Milestone XProtect event server, click Stop.
3. Open C:\Program Files\Milestone \XProtect event server \config\XPconfig.xml in Microsoft® Notepad or
another editing tool of your choice.
4. In the XML file, edit the port number information so
it matches the port number(s) specified in XProtect
Central add-on in the XProtect Enterprise Server.
5. Save the changes you have made to the XML file.
6. Restart the XProtect event server by repeating
steps 1 & 2. Instead of Stop, click Restart.
Enterprise
Manage XProtect Enterprise Servers
If your organization has XProtect Enterprise installations, you can integrate XProtect Enterprise servers into your
XProtect Corporate solution. You do this by adding the XProtect Enterprise servers through the XProtect
Corporate Management Client.
Integration only works with XProtect Enterprise servers running XProtect Enterprise version 6.0 or later.
Integration is not possible if your XProtect Corporate system uses IPv6 (see page 239).
When added, XProtect Enterprise servers can send data and video to the XProtect Corporate surveillance
system. You can compare added XProtect Enterprise servers with recording servers and these will likewise be
available for viewing in access clients.
Note that roles defined in XProtect Corporate’s Management Client can be given access to data from XProtect
Enterprise servers. This is done by coupling XProtect Corporate roles with XProtect Enterprise user rights, see
details in the following.
Furthermore, XProtect Enterprise servers added in the XProtect Corporate Management Client will be listed in the
Add/Remove XProtect Enterprise Servers dialog which you can open by selecting XProtect Enterprise Servers...
from the Tools menu.
XProtect Enterprise’s Recording Server Service must be running for XProtect Corporate to receive data from the
XProtect Enterprise installation. See the XProtect Enterprise documentation for more information.
Limitations when Adding XProtect Enterprise Servers
There are a few limitations to how XProtect Enterprise servers will work when added as slaves to the XProtect
Corporate surveillance system. They will provide operational status and status details on cameras and XProtect
Enterprise servers but not on any other device types.
Also, you cannot define cameras, user rights, scheduling, or other settings for the XProtect Enterprise installation,
or see previews of the cameras in XProtect Corporate. All necessary XProtect Enterprise settings must be made
in XProtect Enterprise’s Administrator application or other relevant XProtect Enterprise applications. See the
XProtect Enterprise documentation for more information.
For access client users, it will be completely transparent whether feeds come from an XProtect Enterprise server
or from an XProtect Corporate recording server. The users have access to cameras depending on their roles
defined in the XProtect Corporate Management Client. If a role has borrowed user rights from an added XProtect
Enterprise server, users with that role have access to data from the XProtect Enterprise server according to the
borrowed user rights. See About Roles on page 164 and Defining Roles with Access to XProtect Enterprise
Servers in the following for more information.
www.milestonesys.com
Page 191
Management Client
Management Client
Prerequisites for Access Roles for XProtect Enterprise Servers
On the XProtect Enterprise server, open the Image Server Administrator window to see if one of the XProtect
Enterprise users has user rights that can be used in connection with an XProtect Corporate role.
Write the XProtect Enterprise user's user name and password or Windows account down. You will need this
information when you use XProtect Corporate’s Management Client to define roles with access to XProtect
Enterprise servers. Note that user names and passwords are case sensitive.
You can also create a new user in XProtect Enterprise, and assign the required user rights in XProtect Enterprise,
so they match the XProtect Corporate role. See the XProtect Enterprise documentation for more information
about creating new users in XProtect Enterprise.
Before you are able to give roles access to XProtect Enterprise servers, the servers must be added through
XProtect Corporate’s Management Client. See Managing XProtect Enterprise Servers in the following for more
information.
Defining Access Roles for XProtect
Enterprise Servers
To give access to data from XProtect Enterprise servers, do the
following in the XProtect Corporate Management Client:
1. In the Management Client's Site Navigation pane (see
page 56), expand Security, and select Roles.
2. Select the required role from the list. If you want to
define a new role, see About Roles on page 164 for
more information.
3. At the bottom of the Role Settings pane select the
Enterprise Servers tab.
4. Select the XProtect Enterprise server to which you
want to assign the role.
5. Select a user with the XProtect Enterprise user rights that represent the correct user rights for the
XProtect Corporate role you are assigning it to. You can do this in two ways:


In the Basic Authentication section, enter the user name and password for a user which is
defined as basic authenticated user in XProtect Enterprise.
or In the Windows Authentication section, enter the Windows account name for a user which
is defined as a Windows authenticated user in XProtect Enterprise.
Tip: If in doubt whether a user is defined as a Basic or Windows authenticated user in XProtect
Enterprise, open the Image Server Administrator window on the XProtect Enterprise server, and
click the User Setup... button. See the XProtect Enterprise documentation for more information
The selected XProtect Enterprise user has not automatically been assigned to the role in
question through XProtect Corporate’s Management Client. The user's XProtect Enterprise user
rights have just been borrowed by the role, but the actual user has not been assigned to the
role.
XProtect Corporate does not verify that the specified user name or password is correct or that
the specified user name, password or Windows account name correspond to a defined user in
XProtect Enterprise. Therefore, make sure that you enter the information correctly. Note also
that user names and passwords are case sensitive.
6. In the toolbar (see page 55), click Save.
Adding XProtect Enterprise Servers
To add an existing XProtect Enterprise installation to your XProtect Corporate system, do the following:
www.milestonesys.com
Page 192
Management Client
Management Client
1. From the XProtect Corporate Management Client's Tools menu select XProtect Enterprise Servers...
2. In the Add/Remove XProtect Enterprise Servers dialog click the Add... button.
3. Enter the IP address or the host name of the required XProtect Enterprise server in the XProtect
Enterprise server IP / Host name field.
4. Enter the port number used by the XProtect Enterprise
server's Image Server in the Port number field.
Tip: The default port number is 80; if in doubt, you can
find the port number in the Image Server Administrator
window on the XProtect Enterprise server.
5. Now enter information about the administrator of the
XProtect Enterprise server. You can do this in two ways:

Select Windows and click the browse button to
the right of the Username field to use the
Windows authentication method which authenticates the administrator through the
administrator's Windows login.
- or -

Select Basic and enter the XProtect Enterprise administrator's user name and password in the
Username and Password fields.
The reason why it is important that you enter the XProtect Enterprise administrator information, is that
you as administrator then will have unlimited rights to data from both XProtect Corporate and the
XProtect Enterprise installation.
The connection to the XProtect Enterprise server is now established, but no roles in the XProtect Corporate
Management Client—except the Administrator role—have been given access to data from the XProtect Enterprise
server. See Defining Roles with Access to XProtect Enterprise Servers earlier for more information about giving
users access to data from added XProtect Enterprise servers.
Remember to define the network configuration settings, so the XProtect Corporate management server will be
able to handle the token authentication of clients for added XProtect Enterprise servers.
In the XProtect Corporate Management Client, you must add all XProtect Enterprise servers you would like to
receive data from. The XProtect Enterprise system's internal master/slave setup cannot be reused by XProtect
Corporate.
XProtect Enterprise Server Network Configuration
With the network configuration settings you specify the XProtect Corporate management server's server address
so that the XProtect Corporate management server can handle the token authentication of clients for added
XProtect Enterprise servers.
1. From the XProtect Corporate Management Client's Tools menu select XProtect Enterprise Servers...
2. See Manage Network Configuration on page 194
Editing XProtect Enterprise Servers
1. From the XProtect Corporate Management Client's Tools menu select XProtect Enterprise Servers...
2. Select an XProtect Enterprise server from the list, and click the Edit... button in the Add/Remove
XProtect Enterprise Servers dialog.
3. Edit the relevant settings and click OK.
www.milestonesys.com
Page 193
Management Client
Management Client
Registered Services
Manage Network Configuration
1. In the Add/Remove Registered Services window, click Network...
2. Specify the LAN and/or WAN IP address of the XProtect Corporate management server.
If all involved servers (both the XProtect Corporate
management server and the trusted servers or the
required XProtect Enterprise servers) are on your
local network, you can simply specify the LAN
address. If one or more involved servers access
the system through an internet connection, you
must also specify the WAN address.
3. Click OK.
For more details, see Manage Registered Services on page 231 and Manage XProtect Enterprise Servers on
page 191.
Manage Registered Services
Occasionally, you have servers and/or services which should be able to communicate with XProtect Corporate
even though they are not directly part of the XProtect Corporate surveillance system. A typical example is an
XProtect Transact server with which you want to use video from the XProtect Corporate system (XProtect
Transact is a transaction management system, typically used for loss prevention through video evidence
combined with time-linked POS or ATM transaction data).
Some services, but not all, can register themselves automatically in XProtect Corporate. Services that can
automatically be registered are:

Event Server service, see What comes along with the Management Server? on page 8.

Log Service, see What comes along with the Management Server? on page 8.

Service Channel service (see page 231).
Automatically registered services are displayed in the list of registered services.
You can manually specify servers/services as registered services in the Management Client:
Accessing Registered Services Configuration
1. In the Management
Client's menu bar,
select Tools >
Registered Services...
2. The Add/Remove
Registered Services
window opens. From
this window you can
manage registered
services.
www.milestonesys.com
Page 194
Management Client
Management Client
Adding and Editing Registered Services
1. In the Add/Remove Registered Services window, click the Add... or Edit... button, depending on your
needs.
2. In the Add Registered Service or Edit Registered Service window (depending on your earlier selection),
specify or edit the following:

Service type: Pre-filled field.

Name: Name of the registered service; the name is only used for display purposes in the
Management Client.

Description: Description of the registered service; the description is only used for display
purposes in the Management Client.

URLs: Click the Add button to add the IP address or hostname of the registered service in
question. If specifying a hostname as part of a URL, the host in question must exist and be
available on the network. URLs must begin with http:// or https:// and must not contain any of
the following characters: < > & ' " * ? | [ ] ".
Example of a typical URL format: http://ipaddress:port/directory (where port and
directory are optional).
Note that you can add more than one URL if required.

External: Select if the registered service connects to the management server with a public IP
address.

Trusted: Select if the registered service should be trusted immediately (this is often the case,
but the option gives you the flexibility to add the registered service and then mark it as trusted
by editing the registered service later).
Note that changing the trusted state will also change the state of other registered services
sharing one or more of the URLs defined for the registered service in question.

Click OK.
Network Configuration
With the network configuration settings you specify the XProtect Corporate management server's server LAN and
WAN addresses in order for the XProtect Corporate management server and the trusted servers to be able to
communicate.
1. See Manage Network Configuration on page 194
Options
The Management Client's Options dialog lets you specify a number of settings related to the appearance of the
application, to logging, to mail server configuration, etc.
You access the Options dialog from the Management Client's menu bar (see page 55), by selecting Tools >
Options.
The Options dialog features the following tabs:
General
The General tab lets you specify the following:
www.milestonesys.com
Page 195
Management Client
Management Client

Number of log rows to retrieve per page: Lets you select the number of log rows you want to view on
a single log page. Default is 50 rows. If a log contains more than the specified number of rows, you will
be able view the remaining rows on subsequent log pages.

Default preview frame rate: Lets you select which frame rate to use for the thumbnail camera images
displayed in the preview pane. Default is 1 frame per second.
Refreshing the Management Client' layout (by pressing F5 on your keyboard or selecting Action >
Refresh from the menu bar) is required for a change to take effect.
Note that a high frame rate (i.e. a high image quality) in combination with a large number of thumbnail
images in the preview pane may slow the system down. You are able to limit the number of thumbnail
images with the Max. number of previews setting.

Max. number of previews: Lets you select the maximum number of thumbnail images displayed in the
preview pane. Default is 64 thumbnail images.
Refreshing the Management Client' layout (by pressing F5 on your keyboard or selecting Action >
Refresh from the menu bar) is required for a change to take effect.
Note that a large number of thumbnail images in combination with a high frame rate (i.e. a high image
quality) may slow the system down. You are able to limit the frame rate used for the thumbnail images
with the Default preview frame rate setting.

Motion detection 'on' when adding camera devices: Lets you select whether motion detection should
be enabled while cameras are being added to a recording server through the Detect Hardware wizard
(see page 75).
Select check box to enable motion detection while using the wizard (default).
Note that this setting only applies while Detect Hardware is in use. When the wizard is not in use, motion
detection will be active for all cameras for which it has been enabled, regardless of this setting.
Why would I want to disable motion detection while using Detect Hardware? Motion detection is a
key element in the surveillance system, and is thus by default enabled for all cameras on the system.
However, motion detection uses a relatively large amount of computing resources. If your system
features a very large number of cameras, and motion detection is enabled on all cameras, the system
may thus be slowed down slightly, and adding of new cameras may take longer than usual. In order to
be able to add new cameras as quickly as possible, you therefore have the option or disabling motion
detection while Detect Hardware is used.

Enable multicast live when adding camera devices: Lets you select whether multicast (see page 83)
should be enabled while cameras are being added to a recording server through Detect Hardware.
Select check box to enable multicast while using the wizard (default).
Note that this setting only applies while Detect Hardware is in use. When the wizard is not in use,
multicast will be active for all cameras for which it has been enabled, regardless of this setting.

Language: Lets you select which language your Management Client system should run. You can chose
from the following languages:
o
Danish
o
English
o
French
o
German
o
Italian
o
Japanese
www.milestonesys.com
Page 196
Management Client
Management Client
o
Portuguese
o
Russian
o
Simplified Chinese
o
Spanish
o
Traditional Chinese.
IMPORTANT: A restart of the Management Client is required for language changes to take effect.

Timeout for PTZ sessions: Handling of PTZ cameras may be interrupted manually by Smart Client
users with the necessary user rights. This setting lets you select how much time should pass before
regular patrolling is resumed after a manual interruption. The setting will apply for all PTZ cameras on
your XProtect Corporate system.

Ignore device communication errors if communication reestablished before: Lets you select how
long a communication error may last without being logged by the system log—or in other words, when it
is brief enough to be ignored.
Management Server Logs
The Management Server Log tab lets you specify settings for XProtect Corporate’s five different management
server logs.
See Manage Logs on page 178 for more information.
Mail Server
The Mail Server tab lets you specify settings for the outgoing SMTP mail server you are going to use with your
XProtect Corporate system.
See Outgoing SMTP Mail Server Settings on page199 for more information.
AVI Generation
The AVI Generation tab lets you specify compression settings for the generation of AVI video clip files. Specifying
these settings is a prerequisite if you want to include AVI files in e-mail notifications sent out by rule-triggered
notification profiles (see page 152). See AVI Compression Settings on page 198 for more information.
Network
The Network tab lets you specify local IP address ranges. See Manage Local IP Address Ranges on page 199 for
more information.
Bookmarks
The Bookmarks tab lets you specify settings for how bookmarks should be ID'ed and function in the Smart Client.
See Device Rights on page 171 and Smart Client documentation.
User Settings
The User Settings tab lets you specify settings for user preference, such as whether a message should be shown
when edge recording is enabled.
www.milestonesys.com
Page 197
Management Client
Management Client
See Record tab Overview (see page 128) for more information.
AVI Compression Settings
You are able to specify compression settings for the generation of
AVI video clip files. Specifying these settings is a prerequisite if you
want to include AVI files in e-mail notifications sent out by ruletriggered notification profiles (see page 152).
To specify compression settings for AVI file generation, do the
following:
1.
Go to Management Client's menu bar, and select Tools >
Options...
2.
In the Options window, select the AVI Generation tab:
3.
Specify the following:

Compressor: Select the required codec
(compression/decompression technology).
Tip: If in doubt about which codec to select, try using
Indeo ® 5.10 (if available). This codec generally
provides a good compromise between quality and file
size.
Tip: For some but not all codecs you are able to configure them by clicking the Configure... button.
Configuration options are entirely codec-specific. And also view detailed information about version
number etc. by clicking the About... button.

Compression quality: (Not available for all codecs). Use the slider to select the required degree of
compression (0-100) to be performed by the codec.
0 means no compression, generally resulting in high image quality and large file size. 100 means
maximum compression, generally resulting in low image quality and small file size.
If the slider is not available, compression quality will be determined entirely by the selected codec.

Key frame every: (Not available for all codecs). If you want to use key frames, select the check box
and specify the required number of seconds between keyframes in the neighboring field.
A keyframe is a single frame stored at specified intervals. The keyframe contains the entire view of
the camera, whereas the following frames contain only the pixels that change. This helps greatly
reduce the size of files.
If the check box is not available, or not selected, every frame will contain the entire view of the
camera.

Data rate: (Not available for all codecs). If you want to use a particular data rate, select the check
box and specify the required number of kilobytes per second in the neighboring field.
If the check box is not available, or not selected, date rate will be determined entirely by the selected
codec.
4.
Click OK.
www.milestonesys.com
Page 198
Management Client
Management Client
Outgoing SMTP Mail Server Settings
You are able to specify settings for the outgoing SMTP mail server you are going to use with your XProtect
Corporate system. Specifying these settings is a prerequisite for using rule-triggered notification profiles (see
page 152) to send out e-mail notifications on events, etc.
Note that when using the SMTP Service with .NET 4.0, it is not possible to send attachments over 3 MB. However
two hotfixes (must be run in the listed order) from Microsoft can be found at:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=30226
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31723
1.
Go to the Management Client's menu bar, and select Tools > Options...
2.
In the Options window, select the Mail Server tab:
3.
Specify the following:

Sender e-mail address: Type the e-mail address you
want to appear as the sender of e-mail notifications for
all notification profiles. Example:
sender@organization.org.

Outgoing mail (SMTP) server name: Type the name
of the SMTP mail server which will be used for sending
e-mail notifications for all notification profiles. Example:
mailserver.organization.org.
Furthermore, if the SMTP mail server requires login, select
Server requires login, and type the required user name and
password.
4.
Click OK.
TLS (Transport Layer Security) and its predecessor SSL (Secure Socket Layer) is not supported; if the sender
belongs on a server that requires TLS or SSL, e-mail notifications will not work properly. Also, you may be
required to disable any e-mail scanners that could prevent the application sending the e-mail notifications.
Tip: When you add new notification profiles, you will be able to send test e-mails and thus verify that your SMTP
mail server settings are correct.
Manage Local IP Address Ranges
When an access client, such as a Smart Client (see page 16), connects to a surveillance system, an amount of
initial data communication, including the exchange of contact addresses goes on in the background. This
happens automatically, and is completely transparent to users.
Access clients may connect from the local network as well as from the internet, and in each case the surveillance
system should be able to provide suitable addresses so the clients can get access to live and recorded video from
the recording servers:

When access clients connect locally, the surveillance system should reply with local addresses and port
numbers.

When access clients connect from the internet, the surveillance system should reply with the recording
servers' public addresses (see page 86), i.e. the address of the firewall or NAT (Network Address
Translation) router, and often also a different port number (which is then forwarded to recording servers).
The surveillance system must therefore be able to determine whether an access client belongs on a local IP
range or on the internet. For this purpose, you are able to define a list of IP ranges which the surveillance system
should recognize as coming from a local network.
Working with Local IP Address ranges
1.
In the Management Client's menu bar, select Tools > Options. This will open the Options dialog (see
page 195).
www.milestonesys.com
Page 199
Management Client
Management Client
Tip: You can also access the Options dialog from the Network tab; this can be handy if you are also
configuring the public IP address of a recording server.
2.
In the Options dialog, select the Network tab.
Defining Local IP Address Ranges
a.
On the Network tab, click the Add button.
b.
In the Range Start column, specify the first IP address in the required range. Then specify the last IP
address in the range in the Range End column.
Tip: If required, a range may include only one IP address (example: 192.168.10.1-192.168.10.1).
c.
If more ranges are required, repeat steps a - b.
d.
Click OK.
Editing Local IP Address Ranges
a.
Overwrite the existing information in the Range Start and Range End columns as required.
b.
Click OK.
www.milestonesys.com
Page 200
Management Client
Federated Architecture
Federated Architecture
Federated Architecture Overview
Milestone Federated Architecture™ (MFA) allows multiple individual standard XProtect Corporate systems (also
known as sites) to interconnect in a parent/child hierarchy of sites.
IMPORTANT: Federated hierarchy is only possible with XProtect Corporate 4.0 or newer. Before installing
XProtect Corporate, see Important Prerequisites When Running Federated Sites in the following.
In this text, the term parent refers to a parent site and child to a child site.
Through MFA, client users—based on their user rights—have seamless access to video, audio and other
resources across individual XProtect Corporate sites. In addition, through a single login, administrators can
centrally manage all sites within the federated hierarchy—again based on administration rights for the individual
sites.
As it provides unlimited scalability, flexibility and accessibility to video surveillance across multiple sites and has
no limit to the number of sites you can add, MFA is well suited for large installations covering multiple buildings,
campuses, or entire city areas.
Each site in a federated hierarchy is installed and configured as a normal stand-alone system with standard
system components, settings, rules, schedules, administrators, users, and user rights. Once each site has been
installed, these can be connected by requesting an MFA link from one site (the parent) to another (the child).
When the link is established, the two sites automatically create an MFA hierarchy to which more sites can be
added to grow the federated hierarchy.
The idea behind federated
architecture; parent and children
linked as needed.
The contents of a federated site:
1.
Management Server
and Failover Server
2.
SQL Server Recording
Servers
3.
Failover Recording
Servers
4.
Cameras
The principle of parent/child
setup:
1.
A Federated Site
2.
Another Federated
Site
3.
Yet another Federated
Site
Etc.
In the above example, an
MFA hierarchy consists of six
sites. As illustrated, each site
can be both a parent and a
child at the same time thus
making it possible to create a
hierarchy with as many levels as needed. It is also evident that a site can link to several child sites on the same
level in a hierarchy.
Once an MFA hierarchy is created, it allows users and administrators logged in to a site, to access that site and
www.milestonesys.com
Page 201
Federated Architecture
Federated Architecture
any child or sub-child sites it may have. Access to child and sub-child sites in the hierarchy is not gained
automatically, but dependent on appropriate user and administrator rights.
It is only relevant to speak of a parent/child setup for management servers—not for recording servers (see page
8). However, due to their relations to management servers, recording servers will automatically become part of
the parent/child setup.
See Manage Federated Architecture on page 207 for details on how to work with MFA.
Important Prerequisites When Running Federated Sites
The easiest way to make MFA work correctly is to prepare your XProtect Corporate system for this feature during
installation. There are certain important prerequisites that you must ensure already at the time of installing your
management server. This can be done in different ways—choose between the procedures in alternative 1-3 in the
following:

Alternative 1: Connect Sites from the same Domain (w. Common Domain User) and Customize
the Installation of the Management Server to MFA
Before installation of the management server, a common domain user should be created and used as
the administrator on all computers involved in the MFA. Depending on whether you select Custom or
Typical during installation of the management server, make sure to select the appropriate procedure in
the following. Note that a typical installation requires more configuration on all sites before MFA will work
properly.

Custom installation:
1.
Start the management server installation (see page 23) and select Custom.
2.
Select to install the Management Server service using a user account.
The selected user account must be the administrator on all management servers and must also
be used when installing the other management servers in the MFA setup.

3.
Finish the installation.
4.
Repeat steps 1-3 to install any other XProtect Corporate systems you want to connect in the
MFA.
5.
See Adding a Site to the Hierarchy on page 208 for details on how to proceed with the MFA.
Typical Installation—set up Network Service on all servers:
1.
Start the management server installation (see page 23) and select Typical, let it run till it
finishes.
This will install the management server as a Network Service.
2.
Repeat step 1 to install any other XProtect Corporate systems you want to connect with the
MFA.
3.
Using a Management Client, connect to the management server you want to have as your
parent site.
4.
In the Management Client's Site Navigation pane (see page 56), expand Security, click Roles,
and in the Overview pane (see page 56), click Administrator.
5.
Add the child computer to this parent server’s Administrator role. See Assign and Remove
Users and Groups to/from Roles on page 165 for details.
6.
Log out of the parent management server and connect to the management server that you just
added as a child.
7.
Once again, in the Overview pane (see page 56), click Administrator.
www.milestonesys.com
Page 202
Federated Architecture
Federated Architecture

8.
Add the parent computer to this servers Administrator role. See Assign and Remove Users and
Groups to/from Roles on page 165 for details.
9.
Log out of the management server, connect to the parent management server, and see
Manage Federated Architecture on page 207 for details on how to proceed with MFA.
Alternative 2: Connect Sites from Different Domains
To make it possible to connect sites across domains, it is very important that these domains are trusted
by each other. Setting up domains to trust each other has nothing to do with MFA but is entirely a matter
of Microsoft Windows Domain configuration.
For further information on how to set up trusted domains, see Microsoft website:
http://technet.microsoft.com/en-us/library/cc961481.aspx.
1.

When the domains, on which the sites you want to connect to each other in an MFA, are trusted
correctly, follow the same instructions as if only one domain was present (see Alternative 1 earlier).
Alternative 3: Connect Sites in Workgroup(s)
When you connect sites inside workgroups, it is an important prerequisite for MFA to work correctly that
the same administrator account is present on all computers you want connected in the MFA. This must
be in place before installing XProtect Corporate.
1.
Log in to Windows using a common administrator account.
2.
Start the management server installation (see page 23) and click Custom.
3.
Select to install the Management Server service using a common administrator account.
4.
Finish the installation.
5.
Repeat steps 1-4 to install any other XProtect Corporate systems you want to connect. They must
all be installed using a common administrator account.
6.
See Adding a Site to the Hierarchy on page 208 for details on how to proceed.
It is not possible to mix domain(s) and workgroup(s), i.e. connect sites from a domain to sites from a
workgroup and vice versa.
Licensing of Federated Architecture
To learn about licensing in general, see Manage Licenses on page 67.
MFA can be used—freely—within the same legal entity as many times as needed. In an MFA setup, all sites
share the same Software License Code (SLC) (see page 69) and device licenses are shared between all sites.
In the case of different legal entities running MFA, each system requires a valid set of base and device licenses.
Furthermore, in order for a device to be accessible across a federated setup, one Milestone Federated
Architecture Device License is required per device accessed in the federated site.
To get additional licenses for your XProtect Corporate system, contact your XProtect Corporate vendor, or visit
www.milestonesys.com to log into the software registration service center.
Basic Rules of Federated Sites
One Parent—Many Children
A child can only have one parent, but a parent can have an unlimited number of children.
Parent Requests Child, Not the Other Way Around
A new parent/child link is always requested by the parent, and if necessary, authorized by the child. See
Accepting Inclusion in the Hierarchy see page 209.
One Level at the Time
www.milestonesys.com
Page 203
Federated Architecture
Federated Architecture
A parent knows about all its children, children's children, etc., but only controls them one level down. Furthermore
a child only knows about and answers to its parent one level up.
Synchronization of Hierarchy
A parent always contains an updated list of all its currently attached children, children's children, etc. But when
distant communication is needed, it takes place level by level, each level forwarding and returning
communication, until it reaches the server requesting the information. Depending on the number of levels that
must be updated, changes to a hierarchy might take a little time to become visible in the Federated Sites
Hierarchy pane, see Refreshing the Site Hierarchy on page 211. The federated hierarchy has a regularly
scheduled synchronization between sites, as well as management-triggered synchronization every time a site is
added or removed. This synchronization only contains site configuration data and each time will send less than
1MB. In addition to the data sent during synchronization, video or configuration data will be sent when a user or
administrator views live or recorded video or configures the system. The amount of data in this case depends on
what and how much is being viewed. It is not possible to schedule your own synchronizations.
Principles for Setting up Federated Sites
When working with MFA, the link between management servers is established from the management server
wanting to become parent to another management server. Theoretically, establishment of a parent/child
relationship happens as follows:
1.
The parent sends a link request to the potential child.
2.
Depending on administrator settings, the child might have to authorize the link request. For more details,
see Administrator Role and Federated Sites section, described later in this topic.
3.
If necessary, the child authorizes the link request.
4.
Relevant info is exchanged.
5.
The new parent/child link is established.
The Administrator Role and Federated Sites
Administrator vs. Non-administrator
In general, you must be an administrator to work with federated architecture. However, by requesting the adding
of children to a top-site (to which you have administrator rights), you can (without administrator rights to the other
sites) create the overall initial infrastructure of a federation. But, as described in Manage Federated Architecture
on page 207, the administrator of each individual child must later authorize the connection before it can take
effect.


Becoming an Administrator Using Active Directory—Two Possible Scenarios
How to become administrator of a federated architecture setup using Active Directory depends on how
the management server is installed. If it is installed as described in either of the following two scenarios,
you gain administrator rights of the entire setup. Otherwise not.

If the management server is installed as a Network Service: Both/All computers involved must be
added as users to each other's XProtect Corporate administrator role before a parent/child link can
be established without acceptance from the administrator of the child. See Assign and Remove
Users and Groups to/from Roles on page 165 for details. This type of setup is primarily
recommended if all sites in the hierarchy are not a member of the same Domain. See also Important
Prerequisites When Running Federated Sites earlier in this topic.

If the management server is installed as a user account: This user account must be a member of
the administrator group of the server being linked to before one or more parent/child link(s) can be
established without acceptance from the administrator of the child. This type of user right setup is
primarily recommended if the number of sites in a hierarchy is large. See also Important
Prerequisites When Running Federated Sites earlier in this topic.
Becoming an Administrator Using Work Groups
How to become administrator of a federated architecture setup using work groups depends on how
accounts are created. If they are set up correctly, you gain administrator rights of the entire setup.
www.milestonesys.com
Page 204
Federated Architecture
Federated Architecture
Otherwise not. See Important Prerequisites When Running Federated Sites earlier in this topic for details
on how to do this.
If the previous criteria are not met, the administrator of a child must accept requests for inclusion in the hierarchy
(see page 209) manually before links can be established.
One or More Administrators?
A federated architecture setup can have many administrators working on it at the same time. Furthermore, the
Site Navigation pane (see page 56) is dynamic and reflects changes to the federated site made both by you and
possibly other administrators. This means that you might see changes here caused by other users. You might
also experience that a site you are connected to is removed from the federated site by another user. In this case,
your site will be removed from the Federated Site Hierarchy pane, but nothing will change in the Site Navigation
pane (see page 56) or elsewhere, allowing you to continue working.
Possibilities and Constrains of Federated Sites
In principle, there is no limit to the number of sites you can add to MFA and how these can be linked, offering you
unlimited scaling, flexibility and accessibility.
There are, however, a few issues to be aware of when working with a federated hierarchy:

Maps: Can only contain cameras from the federated site to which the map is attached—not from other
sites in the hierarchy.

Alarms: Can only be viewed per site. In other words, it is not possible to see all alarms for all sites in the
hierarchy at the same time.
Frequently Asked Questions to Federated Sites
What is a federated site?
A federated site is basically just an individual XProtect Corporate system, complete with management server,
SQL server, one or more recording server(s), failover server(s) and cameras. To make use of federated
architecture, you must connect at least two individual XProtect Corporate systems. The Management Client (see
page 8) is used to configure federated hierarchies. In principle, it lets you connect to any site in the federated
hierarchy at any given time (if user rights permit) using the log in credentials for your home-site. This offers you a
central overview, and, at the same time, lets you zoom in on selected sites by connecting to a specific site to have
a closer look, make configurations, or carry out maintenance. Note however, that the Management Client is only
able to see other sites from the level of the site you are logged into and downwards in the hierarchy.
What is a top-site?
Your top-site is the top level management server of your entire federated architecture setup.
An example an organization could have a top-level server called MyCorp. Second level servers called
MyCorp/RegionalServers. Third level servers called MyCorp/ReginalServers/CityNames. And so on. In this case,
MyCorp is your top-level server. There can only be one top-level server.
Tip: In a federated hierarchy, it is always a good idea to name your servers in a recognizable way, for example,
using regional names or names implying where/in what context the server is located. Using, for example,
consecutive numbers only, might be confusing if you have many servers.
What is a home-site?
Your home-site is the site to which you are logged in. Since you may be logged in far down in the hierarchy, this is
not necessarily the same as your top-site—but it may be. You are only able to see children from the point at
which you are logged in and downwards.
Can a site be both a parent and a child at the same time?
Yes, a parent with children attached, can easily be child to another site, and vice versa. This is because the
parent/child concept is relative and used only in respect to other specified servers. So when looking at the
federated architecture illustration (see earlier link), site 7 is the parent of site 8, but the child of site 6.
What is the difference between logging into and connecting to a site?
To work with federated architecture you must always be logged in to a site via the Management Client. You can
log in to any site if you have administrator rights to that particular site. This is called your home-site. When logged
in to your home-site, you can see all its children (if user rights permit). From your home-site you can also connect
www.milestonesys.com
Page 205
Federated Architecture
Federated Architecture
to its children (if user rights permit). Embedded in the connection process is an automated and seamless log-in,
using the same credentials as your home-site log in. Connecting to a child allows you to see and work with that
site (if user rights permit). However, even though technically you log out of your home-site when connecting to
another site, you will still see the site structure as your (former) home-site sees it. This means, that any changes
you make to a child might not be visible until such changes reaches your home-site via scheduled
synchronization. So changes you make in your hierarchy might not be reflected in the Federated Site Hierarchy
pane until later. For more details, see Basic Rules of Federated Sites, Synchronization of Hierarchy described
earlier in this topic.
You cannot refresh via a connection to a child, this but must take place directly from the home-site.
When do I need to accept link requests?
Whether as the administrator of a child you must accept a link request or not (or the link request is accepted
automatically) depends on your administrator settings. See Administrator Role and Federated Sites section
described later in this topic.
Where is federated architecture configured and managed?
Setting up and configuring Milestone Federated Architecture takes place in the Management Client (see page 8).
Do I need more than one Smart Client to work with federated architecture?
When working with Milestone Federated Architecture, all work in the Smart Client can be handled from one Smart
Client installation, i.e. there is no need for a one-to-one relationship between sites and Smart Clients.
How do I view video from federated sites
You can view video from federated sites in any Smart Client, i.e. there is no need for a one-to-one relationship
between sites and Smart Clients. You will always get the view, i.e. see the site structure as the parent you are
currently logged in to.
Can I include XProtect Enterprise slave(s) in my federated hierarchy?
Yes, that is possible, but only as slave(s) to an XProtect Corporate management server. In this case, the
relationship with the XProtect Enterprise server will work as described in Manage XProtect Enterprise Servers on
page 191. See also About Alarms on page 182 for information on working with alarms in a federated setup.
Is federated architecture the same as multiple management servers, a.k.a. clustering?
No, federated architecture is not the same as clustering. Clustering is a method of obtaining failover support for a
management server on a site. With clustering, it is only possible to have one active management server per
surveillance setup, but other management servers may be set up to take over in case of failure. On the other
hand, federated architecture is a method of combining multiple independent corporate sites into one large setup,
offering flexibility and unlimited possibilities.
See Manage Federated Architecture on page 207 for more details.
Federated Sites Example Scenario—Limestone City.
The following is an example of how
several XProtect Corporate systems can
be integrated into an MFA—in this case
in a City Surveillance scenario.
Many surveillance integrators want to
integrate several independent
surveillance entities into a large scale
system, where each site can still be
used and managed locally and users
and administrators can be given access
to the entire large scale installation.
In this example, several governmental
and business installations must be tied
together in a large scale system offering
the different entities local access and
management of the system, as well as
www.milestonesys.com
Page 206
Federated Architecture
Federated Architecture
governmental (police etc.) access in case of crimes and emergencies.
1.
Downtown Residential
2.
City Hall - public places
3.
Residential area shops
4.
A.C.M.E Industries Inc & branch offices
5.
Limestone Transportation Ltd.
6.
MB Industries
7.
Police Headquarters
8.
Limestone Centre Shopping Mall
All entities must be connected to the city’s video surveillance so that City Hall officials and police officers can
access video from their business or residential area to monitor live video or investigate recorded video in case of
break-ins, thefts, vandalism, emergencies, terror etc.
In addition to being connected to the city’s video surveillance, A.C.M.E Industries Inc, Downtown Residential and
Limestone Centre Shopping Mall also want to segment their installation in several sites as they have several
physical locations that they want to monitor. The segmented architecture offers them greater flexibility during
installation and daily usage.
The city uses MFA, allowing the entities independent video surveillance while being tied into the city wide
surveillance system at the same time.
Because the police have installations that City Hall should not have access to, the Police Headquarters is
selected as the top-site in the city’s federated surveillance hierarchy.
Each site is then tied into Limestone city’s federated hierarchy as follows:

Level 1: Police Headquarters.
o
Level 2: Limestone City.

Level 3: City Hall and MB Industries as one group.
o

Level 4: Central Station, Streets & Intersections and Parks as one group under
City Hall.
Level 3: Limestone Center Shopping, Downtown Residential, Limestone Transportation
Ltd and A.C.M.E Industries Inc. as one group.
o Level 4: Shops, Branch Malls and Residential area shops as one group under
Limestone Center Shopping.
o Level 4: Branch Office 1 and Branch Office 2 as one group under A.C.M.E
Industries Inc.
Manage Federated Architecture
The XProtect Corporate Management Client has a Federated Sites Hierarchy
pane dedicated to displaying federated sites and their parent/child links. From
the View Menu (see page 61), you can show or hide the Federated Sites
Hierarchy pane. The pane is located on the left side of the Management Client
window, under the Site Navigation pane (see page 56).
The parent server you are logged in to (your home-site), is always at the top of
the site hierarchy. You can view all its linked children and downwards through
the parent/child hierarchy. Settings and configurations of your home-site is
always reflected in the Overview and Properties pane (see page 56) and its sitename visible at the top of the Site Navigation pane (see page 56).
To connect to another site in the hierarchy, click the wanted site in the Federated
Sites Hierarchy pane, see Connecting to Another Site in the Hierarchy in the
following.
www.milestonesys.com
Page 207
Federated Architecture
Federated Architecture
What if I only have one server and don't run MFA?
Your user interface looks the same, but when you view the Federated Sites Hierarchy pane you will only see the
one server in your setup.
Navigating Site Hierarchy
Federated Icons
There are a number of icons in MFA, each representing the different states a site can be in:

Top-site in the entire hierarchy:

Normal site (not top-site) which is operational:

Site awaiting acceptance of inclusion in the hierarchy:

Site being attaching, but not yet operating:
Expand/Collapse
You can expand and collapse a site in the Site Navigation pane (see page 56),
to see its children, if any.
Site Navigation Pane
The name, settings and configurations of the highlighted site (red arrow) are
reflected in the Site Navigation pane.
Right-clicking is not Selecting!
Because you must be able to delete a site without being connected to it, right-clicking a site does not select it,
but offers a context menu, which differs depending on where in the hierarchy you are. See Action Menu on page
60.
Context Menu
From the Federated Site Hierarchy pane, a context menu lets you add sites to a hierarchy, accept inclusion in a
hierarchy, rename sites in a hierarchy, detach sites from hierarchy, work with site properties and refresh site
hierarchy. See also Working with Federated Hierarchy... in the following section and Action Menu on page 60.
Due to the nature of federated sites, when the context menu is activated from a parent, you cannot accept
inclusion in the hierarchy. And when it is activated from a child, it is not possible to refresh the site hierarchy.
Working with Federated Hierarchy
Adding a Site to the Hierarchy
You can add children to both your home-site and to its children (when connected to them).

Prerequisites
To add a child to a parent in your hierarchy, one of the following two scenarios must be true:
o
The management server is installed as a Network Service: Before a parent/child link can be
established without the acceptance from the administrator of the child, both computers involved
(parent and child) must be added as a user to the other's XProtect Corporate administrator role.
See Assign and Remove Users and Groups to/from Roles on page 165.
o
The management server is installed as a user account: This user account must be a member
of the administrator group of the server being linked to before a parent/child link can be
established without the acceptance from the administrator of the child.
www.milestonesys.com
Page 208
Federated Architecture
Federated Architecture
If neither of these criteria are met, the administrator of the child needs to accept the request for inclusion
in the hierarchy before the link can be established. See Accept Site in Hierarchy in the following section.
See Federated Architecture Overview on page 201 for more details.

To Add a Site to Hierarchy
1. In the Management Client window, in the Federated Sites Hierarchy pane, select the relevant
site, right-click, and click Add Site to Hierarchy.
Tip: As an alternative to using the menu, press the
CTRL+N keys on your keyboard.
2.
Insert the URL of the requested child in the Add Site to
Hierarchy window.
3.
Click OK.
4.
A link to the new child site is added to the Federated
Sites Hierarchy pane.
5.
If you can establish the new child link without requesting acceptance from the administrator
(see Prerequisites described earlier), skip to step 7.
If not, the new child has the awaiting acceptance
icon and its administrator must authorize
the request. See Accept Inclusion in Hierarchy in the following section.
6.
Make sure the child's administrator authorizes the link request (this is done from the child site).
7.
The new parent/child link is established and the Federated Sites Hierarchy pane is updated with
the
icon for the new child.
Due to synchronization issues, any changes made to children located far from your home-site might take
some time to be reflected in the Federated Sites Hierarchy pane. See Basic Rules of Federated Sites on
page 203, Synchronization of Hierarchy.
Accepting Inclusion in the Hierarchy
You must accept a child link request manually if your administrator settings require this.

If the management server is installed as a Network Service: Computers involved must not be added as
users to each other's XProtect Corporate administrator role, but should be added as another XProtect
Corporate non-administrator role. See Assign and Remove Users and Groups to/from Roles on page
165.

If the management server is installed as a user account: This user account must not be a member of
the administrator role of the server being linked to.
Otherwise inclusion will take place automatically.
See also Administrator Role and Federated Sites on page 204.

Prerequisites
The potential child must have received a link request from the potential parent. As a result, the child has
the awaiting acceptance

icon.
To Accept Inclusion in a Hierarchy
1. In the Management Client window (of the potential child), in the Federated Sites Hierarchy
pane, select the relevant site, right-click, and click Accept Inclusion in Hierarchy.
2.
Click Yes.
3.
The new parent/child link is established and the Federated Sites Hierarchy pane is updated with
the normal site
www.milestonesys.com
icon for the selected site.
Page 209
Federated Architecture
Federated Architecture
Due to synchronization issues, any changes made to children located far from your home-site might take
some time to be reflected in the Federated Sites Hierarchy pane. See Basic Rules of Federated Sites
see page 203, Synchronization of Hierarchy.
Connecting to another Site in the Hierarchy
You can connect to all sites in your MFA if your administrator settings are correct.

Prerequisites
To connect from one site in your hierarchy to another, one of the following two scenarios must be true:
o
The management server is installed as a Network Service: Both computers involved must be
added as users to each other's XProtect Corporate administrator role. See Assign and Remove
Users and Groups to/from Roles on page 165.
o
The management server is installed as a user account: This user account must be a member
of the administrator group of the server being linked to.
See Administrator Role and Federated Sites on page 204.

To Connect to Another Site in Hierarchy
Simply click the wanted site in the Federated Site Hierarchy pane (see page 56). A brief dialog informs
you that you are being connected to the new site. When connection is complete, your view in the
Federated Sites Hierarchy pane will change to reflect that you are connected to a different site.
In the following example, the user was logged into the home-site Rome Server and next connects to the
child Paris Server:
Do I log out of my home-site when I connect to
another site in the hierarchy?
Both yes and no. Embedded in your home-site log-in
is an automated and seamless log-in to its children
as well, using the same credentials as your homesite log-in. However, even though you technically log out of your home-site when connecting to one of its
children, you still see the world as your (former) home-site sees it.
Detaching a Site from the Hierarchy
Detaching/Removing a site from its hierarchy involves two different results depending on where in the MFA you
are located.
If you are within your hierarchy—except your home-site—this will detach the selected site from the rest of the
hierarchy. You will no longer be able to see the detached site.
If, on the other hand, you are located at your home-site, your home site will be detached from the rest of the
hierarchy including any sites located under your home-site. Your home-site becomes the new top-site.

Detach Child from Hierarchy (Location: Any site)
o
Prerequisites
The site you are detaching is any site, except your home-site.
o
To Detach Child from a Hierarchy
1.
2.
In the Management Client window, in the Federated Sites Hierarchy pane (see page
56), right-click the site you want to detach—except the home-site—select Detach Site
from Hierarchy.
Click Yes.
3.
The detached site is removed and the Federated Sites Hierarchy pane is updated.
Tip: You do not have to connect to a site to detach it. Just point your mouse to the relevant site
and right click, select Detach Site from Hierarchy.

Detach Home-site from Parent Hierarchy (Location: Home-site, which has a parent)
www.milestonesys.com
Page 210
Federated Architecture
Federated Architecture
o
Prerequisites
Your home-site must be the child of another site, i.e. have a parent.
o
To Detach Home-site from a Parent Hierarchy
1.
In the Management Client window, in the Federated Sites Hierarchy pane (see page
56), right-click the home-site, and click Detach Site from Hierarchy.
2.
Click Yes.
3.
The Federated Sites Hierarchy pane is updated, your home-site becomes the new topsite, and the normal site icon
4.
changes to a top-site
icon.
Click OK.
Due to synchronization issues, changes might take a little time to be reflected in the Federated Sites Hierarchy
pane. See Basic Rules of Federated Sites on page 203, Synchronization of Hierarchy section.
Tip: As an alternative to using the menu to detach from hierarchy, press the DELETE key on your keyboard.
Refreshing the Site Hierarchy
Automatic synchronizations happen regularly through all steps of your parent/child setup. But if you want a current
overview of things, and do not want to wait for the next automatic synchronization, you can refresh.
When refreshing, the home-site will display a current overview of the state of things from the home-site's point-ofview.
Note that only changes saved by the home-site since the last synchronization will be reflected—changes further
down in the hierarchy will not be reflected. For this, a full scheduled synchronization is needed.
1.
In the Management Client window, in the Federated Sites Hierarchy pane, right-click the home-site, and
click select Refresh Site Hierarchy.
2.
The Federated Sites Hierarchy pane is refreshed, reflecting any changes.
It is not possible to schedule your own synchronizations.
Renaming a Site
You can rename both your home-site and its children when connected to them.
1.
In the Management Client, in the Federated Sites Hierarchy pane, select the relevant site, right-click, and
click Rename Site.
Tip: As an alternative to using the menu, press the F2 key on your keyboard.
2.
You can now overwrite the name of the site.
3.
The Federated Sites Hierarchy pane is updated, reflecting the name-change.
Due to synchronization issues, any changes to remote children might take some time to be reflected in the
Federated Sites Hierarchy pane. See Basic Rules of Federated Sites on page 203, Synchronization of Hierarchy
section.
Setting the Site Properties
You can set properties both on your home-site and its children when you are connected to them.
1.
In the Management Client, in the Federated Sites Hierarchy pane (see page 56), select the relevant site,
right-click, and select Properties.
2.
If needed, change the following:
www.milestonesys.com
Page 211
Federated Architecture
Federated Architecture

General Tab
Information related to the site you are currently
connected to:
o Name: Enter the name of the site displayed in
the Federated Sites Hierarchy pane (see page
56) and the Site Navigation pane (see page
56).
o Description: Enter a description of the site.
o URLs: Use the list to add and remove URL(s)
for this site and indicate whether they are
external or not.
Click OK to save changes.

Parent Site Tab (available on child sites only—
marked in red)
Non-editable information regarding the parent of the
child you are currently connected to:
o Name: Shows the name of the parent to be displayed in the Federated Sites Hierarchy pane
(see page 56) and Site Navigation pane (see page 56).
o Description: Shows a description of the parent.
o URLs: Lists URL(s) for this parent and indicates whether they are external or not.
Due to synchronization issues, any changes made to remote children might take some time to be reflected in the
Site Navigation pane (see page 56). See Basic Rules of Federated Sites on page 203, Synchronization of
Hierarchy section.
www.milestonesys.com
Page 212
Federated Architecture
Backup and Restore
Back Up, Move, Restore System Configuration
It can sometimes be necessary to move the XProtect Corporate management server installation from one
physical server to another. The management server stores your XProtect Corporate system's configuration in a
database. If moving the management server from one physical server to another, it is vital that you make sure that
your new management server also gets access to this database. The system configuration database can be
stored in two different ways:

Network SQL Server: If you are storing your XProtect Corporate system's configuration in a database
on an existing SQL 2005 or 2008 Server on your network, you can simply point to the database's
location on that SQL Server when installing the management server software on your new management
server. In that case, you can skip much of the information in the following.

SQL Server Express Edition: If you are storing your XProtect Corporate system's configuration in a
SQL Server Express Edition database on the management server itself, it is important that you back up
the existing management server's system configuration database before the move. By backing up the
database, and subsequently restoring it on the new server, you will not have to reconfigure your
cameras, rules, time profiles, etc. after the move.
Furthermore, regularly backing up your XProtect Corporate database is always recommended: Having a backup
gives you the ability to restore your XProtect Corporate data in a disaster recovery scenario. However, backing up
also has the added benefit that it flushes the SQL Server’s transaction log.
Some of the prerequisite information in the following—and all of the information about backing up and restoring
your system configuration—is only relevant for users of SQL Server Express Edition. If you use any other SQL
setup, ask your IT department for backup details.
What is the SQL Server Transaction Log and Why Does It Need to Be Flushed?
Each time a change in the XProtect Corporate data occurs, the SQL Server will log the change in its transaction
log—regardless whether it is a SQL Server on your network or a SQL Server Express edition. The transaction log
is essentially a security feature that makes it possible to roll back and undo changes to the SQL Server database.
The SQL Server by default stores its transaction log indefinitely, and therefore the transaction log will over time
build up more and more entries.
The SQL Server’s transaction log is by default located on the system drive, and if the transaction log just grows
and grows, it may in the end prevent Windows from running properly. Flushing the SQL Server’s transaction log
from time to time is thus a good idea; flushing it does not in itself make the transaction log file smaller, but it
prevents it from growing out of control. XProtect Corporate does not, however, automatically flush the SQL
Server’s transaction log at specific intervals. This is because users have different needs. Some want to be able to
undo changes for a very long time, others do not care; what would suit one organization’s needs could be
problematic for others.
You can do several things on the SQL Server itself to keep the size of the transaction log down, including
truncating and/or shrinking the transaction log (for numerous articles on this topic, go to support.microsoft.com
and search for SQL Server transaction log). However, backing up XProtect Corporate’s database is generally a
better option since it flushes the SQL Server’s transaction log and gives you the security of being able to restore
your XProtect Corporate data in case something unexpected happens.
What Happens while the Management Server Is Unavailable?
Recording servers will still be able to record: Any currently working recording servers will have received a
copy of their configuration from the management server, so they will be able to work and store recordings on their
own while the management server is down. Scheduled and motion-triggered recording will therefore work, and
event-triggered recording will also work unless based on events related to the Management Server.
Recording servers will store log data locally: They will automatically send log data to the management server
when the management server becomes available again.

Access clients will not be able to log in: Client access is authorized through the management server.
Without the management server, clients will not be able to log in.

Already logged in access clients can remain logged in for up to an hour: When clients log in, they
are authorized by the management server. Technically, the management server gives each client a
token, which allows the clients to communicate with recording servers for up to one hour. Should the
www.milestonesys.com
Page 213
Back Up, Move, Restore System Configuration
Backup and Restore
clients need to communicate with recording servers for longer than one hour, the management server
automatically renews the tokens. When the management server is down, however, tokens cannot be
renewed, and the clients will lose their connections to recording servers when their tokens expire. If you
can get the new management server up and running within an hour, there is a good chance that many of
your users will not be affected.

No ability to configure the system: Without the management server, you will not be able to change
system configuration through the Management Client.
We recommend that you inform your users about the possibility of losing contact with the surveillance system
while the management server is down, even though some users might not experience loss of contact at all.
Prerequisites

Your XProtect Corporate software installation file for installation on the new management server.

Your initial license (.lic) file, i.e. the one you used when initially installing XProtect Corporate, not the
.lic file which is the result of your license activation (see page 64). License activation is, among other
things, based on the specific hardware on which the activation took place; therefore an activated .lic file
cannot be reused when moving to a new server. Note that if you are also upgrading your XProtect
Corporate software in connection with the move, you will have received a new initial .lic file together with
your new Software License Code (SLC).

If you activated XProtect Corporate on the old server, and you are installing the same software
version on the new server: Contact Milestone support; notify us that the software is being moved,
and ask for your computer information to be reset. Why? An already activated license (.lic) file cannot be
reused on a new server. How? Send an e-mail to support@milestonesys.com ; including your Software
License Code (SLC). You should preferably send the e-mail from the e-mail address with which you
previously registered your SLC.

Network SQL Server users only: Administrator rights on the SQL Server are required whenever you
need to create, move or upgrade the management server's system configuration database on the SQL
Server. Once you are done creating, moving or updating, being database owner of the management
server's system configuration database on the SQL Server will suffice.

SQL Server Express Edition users only: Microsoft SQL Server Management Studio Express, a
tool downloadable for free from www.microsoft.com/downloads. Among its many features for managing
SQL Server Express databases are some easy-to-use backup and restoration features. Download and
install the tool on your existing management server and on the server which will be your future
management server (you will need it for backup as well as restoration).

Management server hostname and IP address: When you move the management server from one
physical server to another physical server, it is very important that you give the new server the same
hostname and IP address as the old one. This is due to the fact that the recording server will connect to
the hostname and IP address of the old management server. In case the new management server has
been given a new hostname and/or IP address, the recording server will not be able to find the
management server and you will have to manually stop each recording server in your system. The
solution is to simply change the management server URL, and restart the recording server.
®
Backing up System Configuration
The following only applies if you are storing your XProtect Corporate system's configuration in a SQL Server
Express Edition database on the management server itself.
Prerequisite: Stop the Management Server Service (see page 232) to prevent configuration changes being
made. This is important since any changes made to the XProtect Corporate configuration between the time you
create a backup and the time you restore it on your new management server will be lost. If changes are made
after the backup, you will have to make a new backup.
Note that XProtect Corporate basically will not work while the Management Server service (see page 231) is
www.milestonesys.com
Page 214
Back Up, Move, Restore System Configuration
Backup and Restore
stopped; it is thus important to remember to start the service again once you have finished backing up the
database.
1.
Open Microsoft SQL Server Management Studio Express from Windows' Start menu by selecting All
Programs > Microsoft SQL Server 2008 > SQL Server Management Studio Express.
Tip: If you do not have SQL Server Management Studio Express, it can be downloaded for free from
www.microsoft.com/downloads.
When you open the tool, you are prompted to connect
to a server. Specify the name of the required SQL
Server (in the example, the server is called MM01232),
and connect with the user account under which the
database was created:
Tip: You do not have to type the name of the SQL
server: If you click inside the Server name field and
select <Browse for more...>, you can select the
required SQL Server from a list instead.
2.
Once connected, you will see a tree structure in the
Object Explorer in the left part of the window. Expand
the SQL Server item,
then the Databases item. We are primarily interested in the Surveillance
database:
The Surveillance database contains your entire XProtect Corporate
system configuration, including recording servers, cameras, inputs,
outputs, users, rules, patrolling profiles, etc.
N
o
No Surveillance database?
Surveillance is the default name
of the database containing the
system configuration. If you can
find the database, but it is not
called Surveillance, it could be
because you gave the database
another name during the
management server installation.
Example: During management server installation it is possible to change the database name from
default name Surveillance to another name
In the following, we will assume that the database
uses the default name.
3.
Right-click the Surveillance database, and select
Tasks > Back Up...
4.
On the Back Up Database dialog's General page,
do the following:
5.

Under Source: Verify that the selected
database is Surveillance and that the
backup type is Full.

Under Destination: A destination path
for the backup is automatically suggested. Verify that the path is satisfactory. If not, remove the
suggested path, and add another path of your choice.
On the Back Up Database dialog's Options page, do the following:
www.milestonesys.com
Page 215
Back Up, Move, Restore System Configuration
Backup and Restore

6.
Under Reliability: Select Verify
backup when finished and Perform
checksum before writing to media.
Click OK to begin the backup. When
backup is finished, you will see a
confirmation:
Then exit Microsoft SQL Server
Management Studio Express.
During the backup process, the Management
Server service was stopped to prevent database
changes being made until you were done.
Remember to start the Management Server service
(see page 232) again.
Tip: Also consider backing up the SurveillanceLog
database, using the same method. The
SurveillanceLog database (name may be different
if you renamed the system configuration
database) contains all your XProtect Corporate
system logs, including errors reported by
recording servers and cameras. Backing up this
database is not vital since it does not contain any
system configuration, but you may later
appreciate having access to system logs from
before the management server move.
Backing Up Event Server Configuration
Make a backup copy of the XProtect event server folder with all its subfolders and contents;

on Windows 2008 Server the XProtect event server folder is located in C:\ProgramData\Milestone

on Windows Server 2003 the XProtect event server folder is located in C:\Documents and Settings\All
Users\Application Data\Milestone
Backing Up Log Server Database
Back up the SurveillanceLogServer database using the same method as when backing up system configuration
described earlier in this topic. The SurveillanceLogServer database (name may be different if you renamed the
system configuration database) contains all your XProtect Corporate system logs, including errors reported by
recording servers and cameras. The database is located where the XProtect log server service is installed,
typically the same place as your management server.
Installing New Management Server on New Database
The following only applies if you are storing your XProtect Corporate system's configuration in a SQL Server
Express Edition database on the management server itself.
Management server installation (see page 23) is divided into three steps. During step 2 of the installation on your
new management server, make sure you select Create a new database for the system configuration database,
even though you have a backup of the database from your old management server.
In the following, we will overwrite the new and empty database by restoring the backup we just created.
www.milestonesys.com
Page 216
Back Up, Move, Restore System Configuration
Backup and Restore
Since we are going to overwrite the new and empty database, it is important that it has the same name as the
backed-up database (if your backed-up database has the default name Surveillance, just use the default name
Surveillance when creating the new database too).
The password for the database is not significant in this backup/restore context, but we recommend that you just
use the default setting Allow server to control password.
Restoring System Configuration
The following only applies if you are storing your XProtect Corporate system's configuration in a SQL Server
Express Edition database on the management server itself.
Luckily, most users never need to restore their backed-up XProtect Corporate configuration database, but if you
ever have the need, use the following process:
Prerequisite: Stop the Management Server Service (see page 232) on the new management server to prevent
configuration changes being made until you have restored the system configuration database.
Note that XProtect Corporate basically will not work while the Management Server service (see page 231) is
stopped; it is thus important to remember to start the service again once you have finished restoring the database.
1.
Open Microsoft SQL Server Management Studio Express from Windows' Start menu by selecting All
Programs > Microsoft SQL Server 2008 > SQL Server Management Studio Express.
Tip: If you do not have SQL Server Management Studio Express, it can be downloaded for free from
www.microsoft.com/downloads.
When you open the tool, you are prompted to connect to a server. Specify the name of the required SQL
Server (in the example, the server is called MM01232), and connect with the user account under which
the database was created.
Tip: You do not have to type the name of the SQL server: If you click inside the Server name field and
select <Browse for more...>, you can select the required SQL Server from a list instead.
2.
Once connected, you will see a tree structure in the Object Explorer in the left part of the window.
Expand the SQL Server item, then the Databases
item.
3.
Right-click the Surveillance database, and select
Tasks > Restore > Database...
No Surveillance database? See Backing up
System Configuration on page 214 for details.
4.
The Restore Database dialog's General page, do
the following:

Under Source for restore: Select From
device and click the
button to the right of
the field.
5.
In the Specify Backup dialog, make sure that File is
selected in the Backup media list. Then click the Add
button:
6.
In the Locate Backup File dialog, locate and select
your backup file Surveillance.bak. Then click OK:
7.
Back in the Specify Backup dialog, the path to your
backup file is now listed. Click OK.
www.milestonesys.com
Page 217
Back Up, Move, Restore System Configuration
Backup and Restore
8.
Back on the Restore
Database dialog's
General page, your
backup is now listed
under Select the
backup sets to restore.
Make sure you select
the backup by
selecting the check
box in the Restore
column:
9.
Now go to the Restore
Database dialog's
Options page, and
select Overwrite the
existing database.
Leave the other
options as they are.
10. Click OK to begin the
restoration. When the
restore is finished, you
will see a confirmation:
Tip: If you get an error message telling
you that the database is in use, try exiting
Microsoft SQL Server Management Studio
Express completely, then repeat steps 110.
Then exit Microsoft SQL Server Management Studio Express.
If you also backed up the SurveillanceLog database from the old management server, restore it on the new
Management Server using the same method.
During the restore process, the Management Server service was stopped to prevent configuration changes
being made until you were done. Remember to start the Management Server service (see page 232) again.
Restoring Event Server Configuration
Prerequisite:
Make sure to have a copy of the XProtect event server folder with all its subfolders and contents.

On Windows 2008 Server, the event server folder is located in C:\ProgramData\Milestone

On Windows Server 2003, the event server folder is located in C:\Documents and Settings\All
Users\Application Data\Milestone
How to Restore the event server Configuration:
1. Install XProtect Corporate and the event server on a new server:
2. On the new server running the event server, click Start > Control Panel > Administrative Tools >
Services.
3.
Right-click the Milestone XProtect event server, click Stop.
4.
Paste the event server folder with all it subfolders and contents into:
www.milestonesys.com
Page 218
Back Up, Move, Restore System Configuration
Backup and Restore
5.

C:\ProgramData\Milestone on Windows 2008 Server

C:\Documents and Settings\All Users\Application Data\Milestone on Windows Server 2003.
Restart the event server Service by repeating steps 2 & 3. Instead of Stop, click Restart.
www.milestonesys.com
Page 219
Back Up, Move, Restore System Configuration
Device Drivers
Device Drivers
Manage and Remove Video Device Drivers
Video device drivers are small programs used for controlling/communicating with the camera devices connected
to a recording server. The video device drivers should therefore be installed on each recording server on your
XProtect Corporate system.
Video device drivers are installed automatically during the initial installation of your XProtect Corporate system.
However, new versions of video device drivers are released and made available on www.milestonesys.com from
time to time.
Making New Video Device Driver Versions Available for Installation
The latest version of video device drivers is available for download from www.milestonesys.com or from your
XProtect Corporate vendor.
Once you have downloaded the latest version of video device drivers, you are able to make the latest version
available for download to recording servers through the Download Manager (see page 48).
Once the video device drivers have been made available for download, administrators of recording servers are
able to connect to the management server's web page, and download the drivers from there.
Installing Video Device Drivers
IMPORTANT: During the installation process, the recording server service must be stopped (see Management
Server Service and Recording Server Service on page 231).
1.
On the computer running the recording server, shut down any Milestone software, including the
recording server service.
2.
With an Internet Explorer browser, connect to the XProtect Corporate management server at the
following address:
http://[management server address]:[port]/installation/admin/
where [management server address] is the IP address or host name of the management server,
and [port] is the port number which IIS has been set up to use on the management server.
This will open the management server's web page. If not accessing the web page on the
management server itself, log in with an account which has administrator rights on the
management server.
3.
On the web page, click the required video device drivers link.
Depending on your security settings, one or more Windows security warnings may appear after you click
the link. If such security warnings appear, accept security warnings by clicking Run or similar (exact
button text depends on your browser version).
4.
Select required language, and click OK. This will open the Video Device Driver Setup wizard, which will
guide you through the installation.
5.
On the wizard's first step, click the Next button.
6.
On the wizard's second step, an installation path is automatically suggested. Click Next.
7.
On the wizard's third step, select Device drivers for XProtect Corporate systems from the menu, and
click Next.
www.milestonesys.com
Page 220
Device Drivers
Device Drivers
8.
The wizard is now ready to install the video device drivers. Click the Install button to complete the
installation of the video device drivers.
9.
When ready, start the Recording Server service again.
After restarting the Recording Server service, it might take several minutes for your hardware devices to make
contact with the new drivers, so have patience. This is due to several internal checks being performed on the
newly installed drivers.
Removing Video Device Drivers
Video device drivers are small programs used for controlling/communicating with the camera devices connected
to a recording server. When the video device drivers are removed, communication between the recording server
and the camera devices will no longer be possible.
To remove video device drivers — typically prior to installing a later version of the drivers — use the following
procedure on the recording server computer on which the video device drivers are installed:
1.
Open Windows' Control Panel, and select Add or Remove Programs. This will open the Add or Remove
Programs window.
2.
In the Add or Remove Programs window, select the Video Device Driver Vx.x entry (where x.x indicates
the relevant version number), and click the Remove button.
3.
You will be asked to confirm that you want to remove the video device drivers. Click OK to remove them.
www.milestonesys.com
Page 221
Device Drivers
Failover Servers
Failover Servers
Failover Server Service Administration
When you have installed a failover server, you are able to check the state of the Milestone Failover Server
Service by looking at the Milestone Failover Server Service icon in the notification area of the computer running
the failover server. The notification area icon also lets you start and stop the Failover Server Service, view status
messages, etc.
Tip: The notification area is occasionally also known as the system tray, it is
located at the far right of the management server computer's Windows
taskbar.
Example: Failover Server Service icon in notification area; note that failover servers also have a Recording Server Service
(other icon)
While the Failover Server Service is stopped, the failover server will not be able to take over from regular
recording servers.
Starting and Stopping the Failover Server Service
The Failover Server Service starts automatically. If you have stopped the service manually, you can start and stop
it the following way:
1.
Right-click the notification area's failover server icon.
2.
From the menu that appears, select Start Failover Server Service or Stop Failover Server Service,
depending on your needs.
Changing the Management Server Address
The failover server must be able to communicate with your XProtect Corporate system's management server. You
therefore specify the IP address/hostname of the management server during the installation of the failover server.
Should you later need to change the address of the management server, you do it the following way:
In order to be able to change the management server address, the Failover Server Service must be stopped.
1.
Stop the Failover Server Service (see Starting and Stopping the Failover Server Service earlier).
2.
Right-click the notification area's Milestone Failover Server Service icon again.
3.
From the menu that appears, select Change Settings... The Failover Recording Server Settings window
appears. You are able to change the following setting:

Management server hostname / IP address: Lets you specify the IP address (example:
123.123.123.123) or host name (example: ourserver) of the XProtect Corporate management server with
which the failover server should be able to communicate.
Viewing Status Messages
1.
Right-click the notification area's Milestone Failover Server Service icon.
2.
From the menu that appears, select Show Status Messages. The Failover Recording Server Status
Messages window appears, listing time-stamped status messages.
www.milestonesys.com
Page 222
Failover Servers
Failover Servers
Viewing Version Information
Knowing the exact version of your Failover Server Service is an advantage if you need to contact product support.
1.
Right-click the notification area's Milestone Failover Server Service icon.
2.
From the menu that appears, select About...
3.
A small dialog opens. The dialog will show the exact version of your Failover Server Service.
How to Read Failover Server Service State Icons
The following icons represent the states of the Failover Server Service:
Failover Server is enabled and started. The failover server is running and able to take over
from regular recording servers.
Failover Server is stopped. The failover server is stopped and no longer taking over from
regular recording servers.
Failover Server is starting. The Failover Server Service is in the process of starting. Under
normal circumstances, the icon will after a short while change to Failover Server Service is
enabled and started.
Failover Server is disabled or running offline. Typically appears if:
 the failover server is not enabled through the Management Client; see Manage
Failover Servers on page 223.

the Failover Server Service is running but the Management Server Service is not.

the failover server's information about the management server address is incorrect
(see Changing the Management Server Address later for more information).

the user account under which the Failover Server Service runs has no access to your
XProtect Corporate system. Troubleshoot as follows:
During installation of the failover server, you specified a user account under
which the Failover Server Service should run. For the failover server to work, it is
important that the user account in question has access to your XProtect
Corporate system with administrator rights.
To verify whether the user account has access to your XProtect Corporate
system, do the following:
o In the Management Client's Site Navigation pane (see page 56), expand
Security and select Roles.
o
In the Overview pane's (see page 56) roles list, select the Administrators
role.
o
In the Properties pane’s (see page 56) role settings list, verify that the
required user is listed.
If the user is not listed, add the required user to the Administrators role by
clicking the Add... button below the role settings list. For more information,
see Assign Users & Groups to/from Roles on page 165.
Manage Failover Servers
A failover server is a spare recording server which can take over if a regular recording server becomes
unavailable. It should therefore always be installed on a separate computer. A failover server has two services:
www.milestonesys.com
Page 223
Failover Servers
Failover Servers

A Failover Server service, which handles the processes of taking over from the regular recording server.
By default, this service is always running since it constantly checks the state of relevant recording
servers.

A Recording Server service, which enables the failover server to act as a recording server while the
regular recording server is unavailable. This service is only started when required, i.e. when the failover
server should take over from the regular recording server. Starting this service typically takes a couple of
seconds, but may take longer depending on local security settings, etc.
A failover server must be able to communicate with all cameras of the recording server(s) from which it should be
able to take over.
Illustration: Failover Process in Details
The following diagram illustrates how the
failover setup works:
Involved Servers:
1.
Recording server
2.
Failover server
3.
Management server
Failover Steps:
1.
To check whether it is running or not,
failover server has non-stop TCP
connection to recording server
2.
Connection between failover server
and recording server is interrupted, i.e.
recording server is not running
3.
From management server, failover
server requests configuration of
recording server
4.
Management server sends requested
configuration and failover server starts recording instead if recording server
5.
Failover server and camera(s) exchange video data
6.
Failover server continually tries to re-establish connection to recording server
7.
When connection to recording server is reestablished, failover server shuts down and recording server fetches video
data (if any) recorded during its down-time.
Installing Failover Servers
For information about installing failover servers, see Recording Servers on page 28.
Adding and Grouping Failover Servers
Failover servers are installed through an installation wizard, just like regular recording servers; see Install Failover
Servers section earlier for more information.
Overview of Failover Servers in Management Client
Once failover servers are installed, they become visible in the Management Client: In the Site Navigation pane
(see page 56), select Servers, then Failover Servers and view a list of installed failover servers in the Overview
pane (see page 56).
Tip: If a failover server does not become visible in the Management Client, verify that the failover server has been
configured with the correct IP address/hostname of the management server. Also verify that the user account
under which the Failover Server service runs has access to your XProtect Corporate system with administrator
rights.
www.milestonesys.com
Page 224
Failover Servers
Failover Servers
Failover Servers Are Grouped
Failover servers are always grouped; a group can contain one or more failover servers. Grouping has a clear
benefit: When you later specify which failover servers should be able to take over from a recording server, you do
not select a particular failover server; rather you select a group of failover servers. If the selected group contains
more than one failover server, this gives you the security of being able to have more than just one failover server
ready to take over if the recording server becomes unavailable.
Initially, your failover servers will all
appear in the group Unused Failover
Servers .
A red x on a failover server icon
indicates that the failover server in
question is currently not in use.
Creating Failover Groups
You can create as many new failover groups as required: In the Overview pane (see page 56), right-click Failover
Groups and select Add Group from the menu that appears:
Specify a name and a description (optional) of your new group, then click OK.
Adding Failover Servers to a Group
In the Overview pane (see page 56),
right-click the group to which you want to
add one or more failover servers, then
select Edit Group Members from the
menu that appears. This will open the
Select Group Members window. From
the Available box in window's left side,
select the required failover servers(s),
then click the Add button to move the
selected failover server(s) to the
Selected box in the right side of the
window:
Tip: Alternatively, drag and drop failover
servers between the two boxes.
When ready, click OK. The required failover servers now belong to the group:
A failover server can only be a member of one group at a time.
Editing Failover Group Properties
Select the required failover group in the Overview pane (see page 56).

On the Info tab, you can edit the name and description of the selected failover group.

On the Sequence tab, you can edit the sequence in which failover servers within the group should take
over from unavailable recording servers.
Enabling Failover Servers
A failover server must be enabled before it will be able to take over from regular
recording servers:
1.
In the Overview pane (see page 56), select the required failover server.
2.
In the Properties pane (see page 56), select Enable this failover server.
www.milestonesys.com
Page 225
Failover Servers
Failover Servers
Editing Failover Server Properties
1.
In the Overview pane (see page 56), select the required failover server.
2.
On the Info tab in the Properties pane (see page 56), you are able to edit
the following:

Name: Name of the failover server, as it will
appear in the Management Client, in logs,
etc.

Description: Optional description of the
failover server, for example a description of
the server's physical location.

Host name: Non-editable field displaying the
network address of the failover server.

UDP port: The port number used for
communication between failover servers. By
default, port 8844 is used.
Tip: The port used by the failover server for
polling (i.e. regularly checking) the state of
relevant recording servers is by default port
number 11000. If required, you can change
that port number on the recording server's
Failover tab (see page 78).

Database location: This field specifies the
path to the database which the failover server should use for storing recordings while taking
over from a regular recording server. When the regular recording server becomes available
again, recordings stored by the failover server will be transferred to the regular recording
server, and merged with recordings there.
The database path cannot be changed while the failover server is taking over from a regular
recording server. Changes you make will be applied when the failover server is no longer taking
over from a regular recording server.

Enable this failover server: A failover server must be enabled before it will be able to take
over from regular recording servers. Select box to enable the failover server, clear box to
disable it.
IMPORTANT: A disabled failover server will not be able to take over from regular recording
servers.
3.
On the Network tab, you are able to define the failover server's public IP address, etc. This is relevant
especially if using NAT (Network Address Translation) and port forwarding. See the description of a
regular recording server's Network tab (see page 86) for more information.
4.
In the toolbar (see page 55), click Save.
Assigning Failover Servers to Recording Servers
In the Management Client, you select a recording server, then use the Failover tab (see page 78) to specify
which failover group(s) should take over from the recording server in question. On the Failover tab, you even have
the flexibility of being able to assign a primary and a secondary failover group to each recording server.
Frequently Asked Questions
How does a failover server know when to take over? It polls (i.e. regularly check the state of) relevant
recording servers every 0.5 seconds. If a recording server does not reply within 5 seconds after it was polled, the
recording server is considered unavailable and the failover server takes over.
www.milestonesys.com
Page 226
Failover Servers
Failover Servers
How long does it take for a failover server to take over? It takes 5 seconds plus the time it takes for the
failover server's Recording Server service to start. During this period it will not be possible to store recordings,
neither will it be possible to view live video from affected cameras.
What happens when a recording server becomes available again? When it becomes available again, it will
automatically take over from the failover server, and recordings stored by the failover server will automatically be
merged into the regular recording server's databases.
How long the merging process takes will depend on the amount of recordings to merge, on network capacity, etc.
During the merging process, it will not be possible to browse recordings from the period during which the failover
server took over.
What if the failover server must take over from another recording server during the merging process? In
that case, it will postpone the merging process with recording server A, and take over from recording server B.
When recording server B becomes available again, the failover server will take up the merging process with
recording server A, after which it will begin merging with recording server B.
Will I lose recordings? A failover solution does not provide complete redundancy. It is, however, a very reliable
way of minimizing downtime.
When the regular recording server becomes available again, the Failover Server service will make sure that the
recording server is ready to store recordings again. Only then is the responsibility for storing recordings handed
back to the regular recording server. Thus, loss of recordings at this stage of the process is negligible.
How will clients experience failover? Clients should hardly notice that a failover server is taking over, although
there will be a short period—usually only some seconds—with no access to video from the affected recording
server while the failover server is taking over.
Clients will be able to view live video as soon as the failover server has taken over.
Clients will be able to play back recent recordings, i.e. recordings from after the failover server took over, since
those recordings will be stored on the failover server. Clients will not be able to play back older recordings stored
only on the affected recording server until that recording server is functioning again, and has taken over from the
failover server.
Clients will, however, be able to access archived (see page 70) recordings stored at accessible locations, such as
on available network drives, but clients will not be able to access archived recordings stored at inaccessible
locations, such as on the unavailable recording server itself or on an unavailable network drive.
When the recording server is functioning again, there will usually be a merging process during which recordings
made by the failover server are merged back into the recording server's database. During that merging process,
clients will not be able to play back recordings from the period during which the failover server took over.
Is there a failover solution for failover servers? Setting up one failover server as backup for another failover
server is not necessary. This is because you do not allocate particular failover servers to take over from a regular
recording server; rather you allocate failover groups.
A failover group must contain at least one failover server, but you can add as many failover servers as required to
a failover group. Provided a failover group contains more than one failover server, there will be more than one
failover server capable of taking over from the regular recording server.
For more information about selecting the failover groups you require for a recording server, see the description of
the Management Client's Failover tab (see page 78).
Will archiving work while a failover server has taken over? Any archiving (see page 70) will work even when
a failover server has taken over from a regular recording server, provided the archiving destination is on a
network location accessible by the failover server.
If the archiving destination is inaccessible—such as on the unavailable recording server itself or on an unavailable
network drive—archiving will not work as long as the destination is unavailable.
www.milestonesys.com
Page 227
Failover Servers
Failover Servers
Failover-Related Events
XProtect Corporate features two failover-related events, Failover Started and Failover Stopped, which you can
use when creating rules (see page 155). The two events are further described in the Events Overview (see page
148).
www.milestonesys.com
Page 228
Failover Servers
Map
Maps
With maps, you get a physical overview of your surveillance
system: Which cameras are placed where, and in what
direction are they pointing? Also, maps can be used for
navigation from large perspectives to small perspectives,
and vice versa: For example, a state map can have hot
zones pointing to more detailed maps of cities,
neighborhoods, streets, floor plans, etc.
Can I access maps from the old XProtect map server?
Maps located on your old XProtect map server is
automatically accessible from your new XProtect event
server where maps are located from XProtect Corporate
4.0 and forward.
Example: hierarchy of maps
Apart from the prerequisite mentioned in the following, all
user interaction with maps, including the adding and maintenance of maps, takes place in the Smart Client. For
detailed information, see the Smart Client documentation.
Example: map in Smart Client
Prerequisite: Event Server Service
In order to use maps, the Event Server service must be installed on your
surveillance system. The event server is installed as part of the
Management Server Installation (see page 23), when the management
server is installed with the Typical option. The service does not necessarily
have to be installed on the Management Server—in fact, you can often
achieve better performance by installing the Event Server service on
another server.
Administrators get the Event Server service through the web page
generated by the Download Manager (see page 48). This fact lets you install the Event Server service anywhere.
Once installed, the Event Server service is able to register itself automatically with XProtect Corporate (i.e. it
automatically becomes listed by the Registered Services feature (see page 194) in the Management Client). The
location of the Event Server service is thus known by XProtect Corporate, and clients logging into XProtect
Corporate are thus automatically able to benefit from the Event Server service as well.
However, if you later change the IP address or hostname of the server running the Event Server service, you
must manually edit the information under Tools > Registered Services... in the Management Client.
Also, if you later need to change the user under which the Event Server service was installed, you must remove
the Event Server service and subsequently install it again under the new user.
Note that removing the Event Server service will not in itself remove the Map configuration made through the
Smart Client.
www.milestonesys.com
Page 229
Maps
Database Corruption
Database Corruption
Protect Databases from Corruption
If a recording server's databases become corrupted, the recording server is in many cases able to repair the
corrupt databases. While the ability to repair corrupt databases is highly valuable, it is of course even better to
take steps to ensure that your databases do not become corrupted:
Power Outages: Use a UPS
The single biggest reason for corrupt databases is the recording server being shut down abruptly, without files
being saved and without the operating system being closed down properly. This may happen due to power
outages, due to somebody accidentally pulling out the server's power cable, or similar.
The best way of protecting your recording servers from being shut down abruptly is to equip each of your
recording servers with a UPS (Uninterruptible Power Supply).
The UPS works as a battery-driven secondary power source, providing the necessary power for saving open files
and safely powering down your system in the event of power irregularities. UPSs vary in sophistication, but many
UPSs include software for automatically saving open files, for alerting system administrators, etc.
Selecting the right type of UPS for your organization's environment is an individual process. When assessing your
needs, however, do bear in mind the amount of runtime you will require the UPS to be able to provide if the power
fails; saving open files and shutting down an operating system properly may take several minutes.
Windows Task Manager: Be Careful when Ending Processes
When working in Windows Task Manager, be careful not to end any processes which affect the surveillance
system. If you end an application or system service by clicking End Process in the Windows Task Manager, the
process in question will not be given the chance to save its state or data before it is terminated. This may in turn
lead to corrupt camera databases.
Windows Task Manager will typically display a warning if you attempt to end a process. Unless you are absolutely
sure that ending the process will not affect the surveillance system, make sure you click the No button when the
warning message asks you if you really want to terminate the process.
Hard Disk Failure: Protect Your Drives
Hard disk drives are mechanical devices, and as such they are vulnerable to external factors. The following are
examples of external factors which may damage hard disk drives and lead to corrupt camera databases:

Vibration (make sure the surveillance system server and its surroundings are stable)

Strong heat (make sure the server has adequate ventilation)

Strong magnetic fields (avoid)

Power outages (make sure you use a UPS; see more information in the previous)

Static electricity (make sure you ground yourself if you are going to handle a hard disk drive).

Fire, water, etc. (avoid)
www.milestonesys.com
Page 230
Database Corruption
Services Administration
Services Administration
About the Service Channel
The XProtect service channel enables automatic and transparent configuration communication between servers
and clients in your XProtect Corporate. For example, it is the service channel that enables the fact that if a shared
view is changed on one client, the change is immediately reflected on other clients using the shared view in
question. The service channel also facilitates configuration-related communication between servers and clients in
cases where you use various plug-ins or add-on products with XProtect Corporate.
The service channel is typically installed as part of the management server installation, where it is an installation
option towards the end of the management server installation process. It typically resides on the management
server computer, but if required you may just as well install it on another server in your surveillance system. For
installation information, see Service Channel Installation on page 34.
Once installed, the service channel is able to register itself automatically with XProtect Corporate (meaning that it
automatically becomes listed by the Registered Services feature (see page 194) in the Management Client). It
location is thus known by XProtect Corporate, and clients logging into XProtect Corporate are automatically able
to benefit from it.
If you later change the IP address or hostname of the server running the Service Channel service, you must
manually edit the information under Tool > Registered Services... in the Management Client. Also, if you later
need to change the user under which the Service Channel service was installed, you must remove the Service
Channel service and subsequently install it again under the new user.
It is important that Smart Clients are time-synchronized with the computer running the Service Channel service
(see page 95); if a Smart Client is not time-synchronized with the management server and the computer running
the Service Channel service, the Smart Client is not updated with information about configuration changes made
by other users in the Smart Client’s Setup tab. This means that users risk overwriting each other’s’ configuration
changes. If Smart Clients are not time-synchronized with the computer running the Service Channel service, you
will see an error informing you of this.
Management Server Service and Recording Server Service
When the XProtect Corporate management server software is installed, you are able to check the state of the
Management Server service by looking at the Management Server Service icon in the notification area of the
computer running the management server.
Likewise, when the XProtect Corporate recording server software is installed, you are able to check the state of
the Recording Server service by looking at the Recording Server Service icon in the notification area of the
computer running the recording server in question.
The notification area icon also lets you start and stop the Management Server service/Recording Server service,
view status messages, etc.
Tip: The notification area is also known as the system tray. It is located at the far right of the management /
recording server's Windows taskbar.
IMPORTANT: When the Recording Server service is running, it is very important that neither Windows Explorer
nor other programs are accessing Media Database files or folders associated with your XProtect Corporate
surveillance setup. Otherwise, the recording server might not be able to rename or move relevant media files.
Unfortunately, this might bring the recording server to a halt. If this situation has already occurred, stop the
Recording Server service, close the program
accessing the media file(s) or folder(s) in question,
and simply restart the Recording Server service.
Example: Management Server Service and Recording Server Service icons in notification area
www.milestonesys.com
Page 231
Services Administration
Services Administration
Accessing the Server Service
1.
Right-click the notification area's server service icon (se earlier illustration).
2.
From the menu that appears, depending on server type, select the needed icon (specified in the
following).
If using multiple instances (see page 40) of the Recording Server service, a sub-menu lets you select whether you
want to start a particular instance or all instances.
Starting the Server Service
1.
See Accessing the Server Service described earlier.
2.
Select either Start Management Server Service or Start Recording Server Service.
Stopping the Server Service
While the Recording Server service is stopped, XProtect Corporate will not be able to interact with devices
connected to the recording server. Consequently, no live viewing or recording will be possible.
While the Management Server service is stopped, you will not be able to use the XProtect Corporate
Management Client at all.
1.
See Accessing the Server Service described earlier.
2.
Select either Stop Recording Server Service or Stop Management Server Service.
Changing Recording Server Settings
To change basic settings for the Recording Server service, such as which port numbers to use, do the following:
In order to be able to change settings, the Recording Server service must be stopped. While the Recording
Server service is stopped, XProtect Corporate will not be able to interact with devices connected to the recording
server. Consequently, no live viewing or recording will be possible.
1.
See Accessing the Server Service described earlier.
2.
Select Stop Recording Server Service.
3.
Right-click the notification area's recording server icon.
4.
From the menu that appears, select Change Settings...
The Recording Server Settings window appears. Change the appropriate settings. See the following.
Viewing Status Messages
1.
See Accessing the Server Service
described earlier.
2.
Select Show Status Messages.
Depending on the current server type,
either the Management Server Status
Messages or Recording Server Status
Messages window appears, listing timestamped status messages:
Example from Management Server service
www.milestonesys.com
Page 232
Services Administration
Services Administration
Viewing Version Information
Knowing the exact version of your Management Server service or Recording Server service is an advantage if
you need to contact product support.
1.
In Management Client's menu bar select Help menu, click About....
2.
A small dialog opens. The dialog will, depending on server type, show the exact version of your
Management Server service or Recording Server service.
How to Work with Recording Server Settings in details

Management server hostname / IP address: IP address (example: 123.123.123.123) or host name
(example: ourserver) of the XProtect Corporate management server to which the recording server should
be connected. This information is necessary in order for the recording server to be able to communicate
with the management server.

Management server port: Port number to be used when communicating with the XProtect Corporate
management server. Default is port 9993, although changeable if required.

Web server port: Port number to be used for handling web server requests, for example for handling
PTZ camera control commands and for browse and live requests from Smart Clients. Default is port
7563, although changeable if required.

TCP information port: Port number to be used when the recording server listens for TCP information
(some devices use TCP for sending event messages). Default is port 5432, although changeable if
required.

SMTP server port: Port number to be used when the recording server listens for SMTP information
(some devices use SMTP (e-mail) for sending event messages). Default is port 25, although changeable
if required.

FTP server port: Port number to be used when the recording server listens for FTP information (some
devices use FTP for sending event messages. Default is port 21, although changeable if required.
How to Read Server Service State Icons
The following notification area icons represent the possible states of the management server service and
recording server service:
www.milestonesys.com
Page 233
Services Administration
Services Administration
Management
Server
Service
Recording
Server
Service
Running.
Stopped.
Starting. Appears when a server service is in the process of starting.
Under normal circumstances, the icon will after a short while change to
Management server is running or Recording server is running.
Stopping. Appears when a server service is in the process of stopping.
Under normal circumstances, the icon will after a short while change to
Management server is stopped or Recording server is stopped.
In indeterminate state. Appears when the Recording Server Service is
initially loaded and until the first information is received, upon which the
icon will, under normal circumstances, change to the Recording server is
starting icon, and subsequently to the Recording server is running icon.
Recording
Server Service
only
www.milestonesys.com
Running offline. Typically appears when the Recording Server Service is
running but the Management Server Service is not.
Must be authorized by administrator. Appears when the Recording
Server Service is loaded for the first time. Administrators authorize the
recording server through the XProtect Corporate Management Client: In
the Management Client's Site Navigation pane (see page 56), expand the
Servers list, select the Recording Server node then in the Overview pane
(see page 56) right-click the required recording server and select Authorize
Recording Server.
Page 234
Services Administration
Virus Scanning
Virus Scanning Information
Virus scanning should in some cases be avoided—if allowed in your organization.
If you use virus scanning software on:

recording data in databases on recording servers

data being archived in archiving (see page 70) locations

data from the Download Manager (see page 48) recorded on a management server
it will most likely use a considerable amount of system resources on scanning.
This may affect system performance negatively, notably data in databases containing recordings. Some virus
scanning software may furthermore temporarily lock each file it scans, which may further impact system
performance negatively. Virus scanning may even corrupt recording databases, and render your surveillance
system recordings useless.
Therefore:

Do not use virus scanning on recording server directories containing recording databases (by default
C:\MediaDatabase\ and all folders under that location, but note that different recording paths may have
been specified in your organization).

Do not use virus scanning on archiving locations.

Do not use virus scanning on files with the following file extensions (which are all surveillance systemrelated):
o .blk
o .idx
o .pic
o .pqz
o .sts
o .ts
Do not use virus scanning on the management server.
Your organization may have strict guidelines reg. virus scanning, but it is important that the mentioned locations
and files are exempt from virus scanning. If allowed, you should therefore disable any virus scanning of recording
servers' databases, of any archiving locations as well as on the management server. Consult your organization’s
IT system administrator if in doubt.
www.milestonesys.com
Page 235
Virus Scanning Information
SNMP
SNMP
XProtect Corporate supports SNMP (Simple Network Management Protocol), a standard protocol for monitoring
and controlling network devices, for managing their configuration, or collecting statistics, etc.
XProtect Corporate will act as an SNMP agent, which can generate an SNMP trap as a result of a triggered rule.
A third party SNMP management console can then receive information about the rule-triggering event, and
operators of the SNMP management console can configure their system for further action as required.
The implementation uses Microsoft Windows SNMP Service for triggering SNMP traps. The SNMP Service must
therefore be installed on recording servers. This will—when the SNMP Service has been configured through its
own user interface—enable recording servers to send .mib (Management Information Base) files to the SNMP
management console.
Installing the SNMP Service
1.
On the required recording servers, open Windows' Add or Remove Programs dialog (Start > Control
Panel > Add or Remove Programs).
2.
In the left side of the Add or Remove Programs dialog click Add/Remove Windows Components. This
will open the Windows Components wizard.
3.
In the wizard, select the check box next to Management and Monitoring Tools, then click the Details...
button to open the Management and Monitoring Tools dialog.
4.
In the Management and Monitoring Tools dialog, select the check box next to Simple Network
Management Protocol, then click OK.
5.
Back in the Windows Components wizard, click Next and follow the wizard's further steps.
Configuring the SNMP Service
1.
On the required recording servers, select Start > Control Panel > Administrative Tools > Services.
2.
Double-click the SNMP Service.
3.
Select the Traps tab.
4.
Specify a community name, and click the Add to list button.
5.
Select the Destinations tab.
6.
Click the Add button, and specify the IP address or host name of the server running your third party
SNMP management station software.
7.
Click OK.
www.milestonesys.com
Page 236
SNMP
Daylight Saving Time
Daylight Saving Time
Daylight saving time (DST, also known as summer time) is the practice of
advancing clocks in order for evenings to have more daylight and mornings to
have less. Typically, clocks are adjusted forward one hour sometime during the
spring season and adjusted backward sometime during the fall season, hence the
saying spring forward, fall back. Note that use of DST varies between
countries/regions.
Clocks are adjusted forward when DST starts
When working with a surveillance system, which is inherently time-sensitive, it is
important to know how the system handles DST.
Spring: Switch from Standard Time to DST
The change from standard time to DST is not much of an issue since you jump one hour forward. Typically, the
clock jumps forward from 02:00 standard time to 03:00 DST, and the day thus has 23 hours. In that case, there is
simply no data between 02:00 and 03:00 in the morning since that hour, for that day, did not exist.
Fall: Switch from DST to Standard Time
When you switch from DST to standard time in the fall, you jump one hour back. Typically, the clock jumps
backward from 02:00 DST to 01:00 standard time, repeating that hour, and the day thus has 25 hours.
Server-side Handling
XProtect Corporate uses Coordinated Universal Time (UTC), which is the official world reference for time. UTC is
not adjusted to reflect switches either to or from DST. Since XProtect Corporate uses UTC, no XProtect
Corporate recordings are ever stored with the same timestamp twice, not even during the DST change hour.
Client-side Handling
Both of the client applications used for viewing recordings from XProtect Corporate —the Smart Client and the
Remote Client —also use UTC when displaying recordings. The client simply takes local time settings (time zone
and any DST) from the computer on which the client is used, and converts those time settings to UTC. This
means that there is a very simple solution for viewing recordings from the DST change hour.
Viewing DST Change Hour Recordings in Access Clients
When you want to view recordings from the last (most recent) hour of the DST change hour, simply go ahead and
view them.
When you want to view recordings from the first hour of the DST change hour, do the following:
1.
On the computer on which the access client is used, go to Windows' Start menu, and select Control
Panel.
2.
In the Control Panel, double-click Date and Time.
www.milestonesys.com
Page 237
Daylight Saving Time
Daylight Saving Time
3.
In the Date and Time Properties window, select
the Time Zone tab.
4.
Make sure the Automatically adjust clock for
daylight saving changes check box is cleared,
then click OK.
When the Automatically adjust clock for daylight saving
changes check box is cleared, recordings from the entire
DST period will be Standard Time (or one hour off
compared to DST). This means that recordings from the
first hour of the DST change hour can now be viewed.
IMPORTANT: When you are done viewing recordings from
the first hour of the DST change hour, select the
Automatically adjust clock for daylight saving changes
check box again to avoid confusion. We recommend not to
clear the Automatically adjust clock for daylight saving
changes check box unless you specifically need to view
recordings from the first hour of the DST change hour.
www.milestonesys.com
Page 238
Daylight Saving Time
IPV6
IPv6
XProtect Corporate supports IPv6 as well as IPv4. So does the Smart Client, see page 16.
IPv6 is the latest version of the Internet Protocol (IP). The Internet protocol determines the format and use of IP
addresses. IPv6 coexists with the still much more widely used IP version IPv4. IPv6 was developed in order to
solve the address exhaustion of IPv4. IPv6 addresses are 128 bit long, whereas IPv4 addresses are only 32 bit
long. IPv6 thus offers more than ten billion billion billion times as many addresses as IPv4.
More and more organizations are implementing IPv6 on their networks. For example, all US federal agency
infrastructures are required to be IPv6 compliant.
Examples and illustrations in this manual reflect use of IPv4 since this is still the most widely used IP version.
IPv6 will work equally well with XProtect Corporate, provided you note the following:
Important Information if Using XProtect Corporate with
IPv6
The following conditions apply when using XProtect Corporate with IPv6:

Servers
Servers are often capable of using IPv4 as well as IPv6. However, if just one server in your XProtect
Corporate system (i.e. a management server, a recording server or a failover server) requires a
particular IP version, all other servers in your XProtect Corporate system must communicate using the
same IP version.
Example: All of the servers in your XProtect Corporate system—except one—are able to use IPv4
as well as IPv6. The exception is a server which is only capable of using IPv6. This means that all
servers must communicate with each other using IPv6.
See also the illustration in the following.

Devices
You can use devices (cameras, inputs, outputs, microphones, speakers) with a different IP version than
that being used for server communication provided your network equipment and the recording servers in
question also support the devices' IP version. See also the illustration in the following.

Clients
If your XProtect Corporate system uses IPv6, users should connect with the Smart Client. The Smart
Client supports IPv6 as well as IPv4; the Remote Client supports IPv4 only.
If one or more servers in the XProtect Corporate system are only capable of using IPv6, Smart Client
users must use IPv6 for their communication with those servers. In this context, it is important to
remember that Smart Clients technically connect to a management server for initial authentication, and
then to the required recording servers for access to recordings.
However, the Smart Client users do not have to be on an IPv6 network themselves, provided your
network equipment supports communication between different IP versions, and they have installed the
IPv6 protocol on their computers. See also the illustration in the following.
Tip: To install IPv6 on a client computer, open a command prompt, type ipv6 install, and press ENTER.
www.milestonesys.com
Page 239
IPv6
IPV6

Example Illustration
Example: Since one server in the XProtect Corporate system only uses IPv6, all communication with that server must
naturally use IPv6. However, that server also determines the IP version for communication between all other servers
in the system.

No XProtect Enterprise Integration
If using IPv6, it is not possible to integrate XProtect Enterprise servers (see page 191) in your XProtect
Corporate system.

No Matrix Monitor Compatibility
If using IPv6, it is not possible to use the Matrix Monitor application with your XProtect Corporate system.
Matrix functionality in Smart Clients is not affected.
How to Write IPv6 Addresses
An IPv6 address is usually written as eight blocks of four hexadecimal digits, with each block separated by a
colon.
Example: 2001:0B80:0000:0000:0000:0F80:3FA8:18AB
Addresses may be shortened by eliminating leading zeros in a block. Also note that some of the four-digit blocks
may consist of zeros only. If any number of such 0000 blocks are consecutive, addresses may be shortened by
replacing the 0000 blocks with two colons as long as there is only one such double colon in the address.
Example:
2001:0B80:0000:0000:0000:0F80:3FA8:18AB may be shortened to
2001:B80:0000:0000:0000:F80:3FA8:18AB if removing the leading zeros, or to
2001:0B80::0F80:3FA8:18AB if removing the 0000 blocks, or even to
2001:B80::F80:3FA8:18AB if removing the leading zeros as well as the 0000 blocks.
Using IPv6 Addresses in URLs
IPv6 addresses contain colons. Colons, however, are also used in other types of network addressing syntax. For
example, IPv4 uses a colon to separate IP address and port number when both are used in a URL. IPv6 has
inherited this principle. Therefore, in order to avoid confusion, square brackets are put around IPv6 addresses
when they are used in URLs.
Example of a URL with an IPv6 address:
http://[2001:0B80:0000:0000:0000:0F80:3FA8:18AB], which may of course be shortened to, for
example, http://[2001:B80::F80:3FA8:18AB]
Example of a URL with an IPv6 address and a port number:
http://[2001:0B80:0000:0000:0000:0F80:3FA8:18AB]:1234, which may of course be shortened to, for
example, http://[2001:B80::F80:3FA8:18AB]:1234
For more information about IPv6, see—for example—www.iana.org/numbers/. IANA, the Internet Assigned
Numbers Authority, is the organization responsible for the global coordination of IP addressing.
www.milestonesys.com
Page 240
IPv6
IPV6
Multi-domain Environment with One-way Trust
If you run XProtect Corporate in a multi-domain environment, it is possible to configure this setup with one-way
trust
Prerequisites
XProtect Corporate is installed on the Trusting domain and users log in from Trusting and Trusted domains.
To Configure XProtect Corporate in Multi-domain Environments with One-way Trust
Create a service account in the Trusted domain. It can be named anything you want, for example, svcMilestone.
1.
Add svcMilestone (example name only) to the following local Windows user groups on the server running
XProtect Corporate, in the Trusting domain:

Administrators

IIS_IUSRS (Windows Server 2008, necessary for Internet Information Services (IIS) Application
Pools)

IIS_WPG (Windows Server 2003, necessary for IIS Application Pools).
2.
Ensure that the svcMilestone (example name only) account has system administrator rights on your SQL
Database or SQL Server Express, either directly or through the BUILTIN\Administrators group.
3.
Set the identity of the ManagementServerAppPool Application Pool in the IIS to the svcMilestone
(example name only) account.
4.
Reboot the server to ensure all group membership and permission changes take effect.
Example illustration of Multi-domain Environments
with One-way Trust.
Legend:
1.
One-way Outgoing Domain Trust
2.
MyDomain.local
3.
OtherDomain.edu
4.
Trusting Domain User
5.
XProtect Corporate Management Server
6.
Milestone Service Account
7.
Trusted Domain User
IMPORTANT: To add Trusted domain users to new or existing XProtect Corporate roles, login to Windows as a
Trusted domain user. Next, launch the Management Client and login as user of either the Trusting domain or the
Trusted domain. If you login to Windows as a Trusting domain user, you will be asked for credentials for the
Trusted domain in order to browse for users.
www.milestonesys.com
Page 241
Multi-domain Environment with One-way Trust
IPV6
Index
.lic file ............................................................................................................................................................. 66, 211
.lrq file .................................................................................................................................................................... 66
360 Degree Lens ................................................................................................................................................... 95
About Storage and Archiving ............................................................................................................... 69, 90, 91, 92
Actions Selectable in Rules, List of ...................................................................................................................... 139
Activate Archiving on ... (Rule Action) .................................................................................................................. 144
Activate Output (Output-Related Role Settings)................................................................................................... 171
Activation, Licenses ............................................................................................................................................... 63
Active Directory .................................................................................................... 9, 13, 58, 161, 163, 166, 167, 201
Active Directory, Adding Users without ................................................................................................................ 167
Add (Camera-Related Role Settings)................................................................................................................... 170
Administrators Role.............................................................................................................................................. 164
Alarms .................................................................................................................. 174, 180, 181, 182, 183, 185, 188
Allow Activation of PTZ Presets (PTZ-Related Role Setting) ............................................................................... 172
Allow PTZ Control (PTZ-Related Role Setting) .................................................................................................... 171
Analytics Events................................................................................................................................... 185, 186, 187
Application Rights, Roles ..................................................................................................................................... 173
Apply New Settings on … (Rule Action)............................................................................................................... 144
Archive Available Event ....................................................................................................................................... 149
Archive Not Finished Event .................................................................................................................................. 150
Archive Unavailable Event ................................................................................................................................... 149
Assisted Hardware Detection ................................................................................................................................. 76
Audio.................................................................................................................................................... 132, 146, 147
Audio Falling Event .............................................................................................................................................. 147
Audio Passing Event ............................................................................................................................................ 147
Audio Rising Event............................................................................................................................................... 147
Audit Log .............................................................................................................................................. 176, 177, 179
Authentication, Management Client Login ............................................................................................................. 58
Authorization, Recording Servers .......................................................................................................................... 86
Auto-Hide ............................................................................................................................................................... 63
Automatic Hardware Detection .............................................................................................................................. 74
AUX Commands .................................................................................................................................................. 170
AUX Commands (Camera-Related Role Settings) .............................................................................................. 170
AVI Compression ......................................................................................................................................... 151, 195
AVI Generation (Tab in Options Dialog)............................................................................................................... 195
Bookmarks ................................................................................................................................................... 170, 195
Browse (Application Role Setting)........................................................................................................................ 173
Browse Audio (Microphone-Related Role Setting) ............................................................................................... 170
Browse Audio (Speaker-Related Role Setting) .................................................................................................... 171
www.milestonesys.com
Page 242
Index
IPV6
Built-in Events ...................................................................................................................................................... 148
Camera Status Icons ........................................................................................................................................... 132
Cameras, Managing............................................................................................................................................. 105
Circuit Closed/Open ............................................................................................................................................. 108
Clients .............................................................................................................................................................. 14, 15
Clients, Installation ................................................................................................................................................. 14
Clients, Installation/Removal .................................................................................................................................. 14
Cluster, Installing Management Server in .............................................................................................................. 37
Codecs, AVI ......................................................................................................................................................... 195
Communication Error Event ................................................................................................................................. 148
Communication Started Event ............................................................................................................................. 148
Communication Stopped Event............................................................................................................................ 148
Copyright ................................................................................................................................................................. 5
Create Bookmark on ... (Rule Action) .................................................................................................................. 143
Custom Events................................................................................................................... See User-Defined Events
Database Disk Full Event ..................................................................................................................................... 150
Database Full Auto Archive Event ....................................................................................................................... 150
Database Repair Event ........................................................................................................................................ 150
Database Storage Area Available Event .............................................................................................................. 150
Database Storage Area Unavailable Event .......................................................................................................... 150
Database, Management Server Troubleshooting................................................................................................... 46
Daylight Saving Time ........................................................................................................................................... 234
Default Goto Preset when PTZ is Done (Default Rule) ........................................................................................ 146
Default Rules ............................................................................................................................................... 145, 155
Default Web Page .................................................................................................................................................. 47
Delete (Camera-Related Role Settings)............................................................................................................... 170
Device Drivers.......................................................................................................................................... 42, 43, 217
Device Drivers, Assisted Hardware Detection........................................................................................................ 76
Device Drivers, Automatic Hardware Detection ..................................................................................................... 74
Device Group, Speakers ........................................................................................................................................ 96
Device Groups ....................................................................................................................................................... 96
Device Groups, Cameras ....................................................................................................................................... 96
Device Groups, Input ............................................................................................................................................. 96
Device Groups, Microphones ................................................................................................................................. 96
Device Groups, Output .......................................................................................................................................... 96
Device Groups, Settings for All/Individual Camera Types ...................................................................................... 97
Device Groups, Settings for All/Individual Device Types ....................................................................................... 97
Device Groups, Settings for All/Individual Microphone Types ................................................................................ 97
Device Groups, Settings for All/Individual Speaker Types ..................................................................................... 97
Device Packs ....................................................................................................................................................... 217
Device Rights Roles............................................................................................................................................. 169
Disabling Panomorph Support ............................................................................................................................... 96
Disclaimer ................................................................................................................................................................ 5
www.milestonesys.com
Page 243
Index
IPV6
Download Manager .............................................................................................................. 8, 40, 47, 48, 49, 50, 51
Drivers ................................................................................................................................................................. 217
Drivers, Assisted Hardware Detection ................................................................................................................... 76
Drivers, Automatic Hardware Detection ................................................................................................................. 74
DST.............................................................................................................................................................. 234, 235
Edge Recording ........................................................................................................................................... 111, 130
Edit (Camera-Related Role Settings) ................................................................................................................... 170
Edit Hardware Window .......................................................................................................................................... 79
Edit Menu, Management Client .............................................................................................................................. 59
Effective Archiving ................................................................................................................................................. 70
Effective Roles ............................................................................................................................................. 164, 166
E-Mail Notifications .............................................................................................................................................. 150
E-Mail Notifications, Including AVI Video Clips in ................................................................................................ 151
E-Mail Notifications, Including Still Images in ....................................................................................................... 151
E-Mail Notifications, Using Rules to Trigger E-mail Notifications ......................................................................... 151
Enabling Panomorph Support ................................................................................................................................ 96
Enterprise Servers ............................................................................................................................... 174, 189, 190
Enterprise Servers, Role Settings for ........................................................................................................... 174, 189
Event Log ............................................................................................................................................................. 176
Event Server ................................................................................................................ 30, 31, 40, 43, 181, 213, 215
Event Server and Maps ....................................................................................................................................... 226
Events Selectable in Rules, List of ....................................................................................................................... 146
Events, Camera Properties .................................................................................................................................. 101
Events, Hardware Configurable ................................................................................................................... 101, 102
Events, Microphone Properties ............................................................................................................................ 102
Export Audio (Microphone-Related Role Setting) ................................................................................................ 170
Export Audio (Speaker-Related Role Setting) ...................................................................................................... 171
Export video as AVI/JPEG (Camera-Related Role Settings) ............................................................................... 170
Export video in database format (Camera-Related Role Settings)....................................................................... 170
F1 Help .................................................................................................................................................................. 19
Failover Cluster, installing Management Server in a .............................................................................................. 38
Failover Groups ............................................................................................................................................. 77, 222
Failover Server Service, Starting/Stopping .......................................................................................................... 219
Failover Server Service, Status Messages .......................................................................................................... 219
Failover Server, Installation ................................................................................................................................. 221
Failover Servers ....................................................................................................... 28, 77, 219, 220, 221, 222, 223
Failover Servers, Adding in Management Client .................................................................................................. 221
Failover Servers, Assigning to Recording Servers ......................................................................................... 77, 223
Failover Servers, Enabling/Disabling ................................................................................................................... 222
Failover Servers, Frequently Asked Questions About.......................................................................................... 223
Failover Started Event ................................................................................................................................. 150, 225
Failover Stopped Event................................................................................................................................ 150, 225
Failover, Recording Server Properties ................................................................................................................... 77
www.milestonesys.com
Page 244
Index
IPV6
Federated Architecture ................................................................................................ 198, 200, 201, 203, 204, 206
Federated Hierarchy ........................................................................................................................................ 7, 205
Federated Sites.................................................................................................................... 199, 200, 201, 202, 203
Feed Overflow Started Event ............................................................................................................................... 148
Feed Overflow Stopped Event ............................................................................................................................. 148
File Menu, Management Client .............................................................................................................................. 59
Frame Rate Recording......................................................................................................................................... 127
FTP Server Port ................................................................................................................................................... 230
General (Tab in Options Dialog) .......................................................................................................................... 193
Get Sequences (Camera-Related Role Setting) .................................................................................................. 170
Get Sequences (Microphone-Related Role Setting) ............................................................................................ 170
Get Sequences (Speaker-Related Role Setting).................................................................................................. 171
Getting Started ....................................................................................................................................................... 56
Glossary ................................................................................................................................................................. 19
Groom Databases .................................................................................................................................................. 70
Groups, Adding after Defining Roles.................................................................................................................... 166
Groups, Managing ............................................................................................................................................... 166
Groups, Viewing Members' Roles ........................................................................................................................ 166
Hardware Configuration-Related Events .............................................................................................................. 147
Hardware Detection Wizard ................................................................................................................................... 74
Hardware Drivers, Assisted Hardware Detection ................................................................................................... 76
Hardware Drivers, Automatic Hardware Detection................................................................................................. 75
Help Menu, Management Client............................................................................................................................. 60
Help System..................................................................................................................................................... 19, 54
IGMP, Requirement for Multicasting ...................................................................................................................... 83
IIS Installation .................................................................................................................................................. 23, 43
Image Processing Interval, Motion Detection ....................................................................................................... 116
Images Received Event ....................................................................................................................................... 147
ImmerVision 360 Degree Lens............................................................................................................................... 95
Important Ports Numbers ....................................................................................................................................... 35
Info, Camera Properties ....................................................................................................................................... 104
Info, Hardware Properties .................................................................................................................................... 104
Info, Input Properties............................................................................................................................................ 107
Info, Microphone Properties ................................................................................................................................. 104
Info, Output Properties ......................................................................................................................................... 113
Info, Recording Server Properties .......................................................................................................................... 78
Info, Speaker Properties ...................................................................................................................................... 104
Input Activated Event ........................................................................................................................................... 147
Input Changed Event ................................................................................................................................... 108, 147
Input Deactivated Event ....................................................................................................................................... 148
Input Falling Event ............................................................................................................................................... 108
Input rises on Event ............................................................................................................................................. 108
Input Rising Event ................................................................................................................................................ 108
www.milestonesys.com
Page 245
Index
IPV6
Input Status Icons ................................................................................................................................................ 132
Input, Managing ................................................................................................................................................... 106
Input, Viewing Current State of ............................................................................................................................ 107
Installation Troubleshooting ............................................................................................................................. 23, 43
Installation, Failover Servers .................................................................................................................................. 28
Installation, Management Client ............................................................................................................................. 29
Installation, Smart Client ........................................................................................................................................ 15
Internet Information Services, Installation .............................................................................................................. 43
IP Address Ranges, Automatic Hardware Detection.............................................................................................. 74
IPv6 .......................................................................................................................................... 84, 85, 189, 236, 237
Language Packs .................................................................................................................................................... 47
Layout, Customizing Management Client’s ............................................................................................................ 60
Licenses Activation ................................................................................................................................................ 63
Licensing .............................................................................................................................................................. 200
Listen to Live Audio (Microphone-Related Role Setting)...................................................................................... 170
Listen to Live Audio (Speaker-Related Role Setting) ........................................................................................... 171
Live (Application Role Setting) ............................................................................................................................. 173
Live Client Feed Requested Event....................................................................................................................... 149
Live Client Feed Terminated Event ...................................................................................................................... 149
Live Streams, Preview Images in Management Client ........................................................................................... 56
Local IP Address Ranges, Managing ................................................................................................................... 197
Local IP Ranges, Managing ................................................................................................................................... 86
Log Server ......................................................................................................................................... 30, 31, 40, 213
Logging in, Management Client ............................................................................................................................. 58
Logs ............................................................................................................................................................. 176, 195
Logs, Exporting .................................................................................................................................................... 178
Mail Server (Tab in Options Dialog) ..................................................................................................................... 195
Mail Server, Outgoing SMTP ............................................................................................................................... 196
Make New Log Entry (Rule Action) ...................................................................................................................... 143
Management Client Installation .............................................................................................................................. 21
Management Client, Customizing Layout .............................................................................................................. 60
Management Client, Logging in ............................................................................................................................. 58
Management Client, Menus ................................................................................................................................... 59
Management Server Database Installation ............................................................................................................ 47
Management Server Hostname / IP address ....................................................................................................... 230
Management Server Logs (Tab in Options Dialog) .............................................................................................. 195
Management Server Port ............................................................................................................................... 58, 230
Management Server, Starting/Stopping ............................................................................................................... 228
Management Servers, Multiple .............................................................................................................................. 36
Manager ............................................................................................................................... See Management Client
Managing XProtect Matrix Recipients .................................................................................................................. 137
Manual PTZ Session Started Event ..................................................................................................................... 149
Manual PTZ Session Stopped Event ................................................................................................................... 149
www.milestonesys.com
Page 246
Index
IPV6
Map Server Installation ........................................................................................................................................ 226
Maps, Using ......................................................................................................................................................... 226
Matrix Recipients, Rule-Triggered Video in .......................................................................................................... 144
Matrix Rights, Roles ............................................................................................................................................. 174
MediaDB, Failover Server Installation .................................................................................................................. 221
Menus, Management Client ................................................................................................................................... 59
Microphone Status Icons ..................................................................................................................................... 132
Microphones, Manage ......................................................................................................................................... 109
Minimum System Requirements .............................................................................................................................. 9
Motion Detection .................................................................................................................................. 115, 116, 117
Motion Detection, Ignoring in Parts of a Camera's Images .................................................................................. 117
Motion Started (Hardware Configurable Event) ................................................................................................... 148
Motion Started Event ................................................................................................................................... 147, 148
Motion Stopped (Hardware Configurable Event).................................................................................................. 148
Motion Stopped Event.................................................................................................................................. 147, 148
Motion Window (Hardware Configurable Event Property) .................................................................................... 103
Move Camera to Preset Position (Rule Action) .................................................................................................... 142
Move to Default Preset on … (Rule Action) ......................................................................................................... 142
MTU ................................................................................................................................................................. 83, 84
Multicasting .......................................................................................................................................... 82, 83, 84, 99
Multicasting, Recording Server Properties ............................................................................................................. 82
Multi-domain Environment ................................................................................................................................... 238
Multi-domain Environments with One-way Trust .................................................................................................. 238
Multiple Management Servers ............................................................................................................................... 36
Multiple Recording Server Instances ........................................................................................................... 9, 28, 39
Multistreaming...................................................................................................................................................... 110
NAT.................................................................................................................................................. 85, 86, 197, 223
Network Configuration (XProtect Enterprise Servers) .......................................................................................... 191
Network, Recording Server Properties................................................................................................................... 85
Offline Activation, Licenses .................................................................................................................................... 66
On ... Trigger ... User-Defined Event (Rule Action) .............................................................................................. 145
One-way Trust ..................................................................................................................................................... 238
Online Activation, Licenses .................................................................................................................................... 64
Options Dialog ..................................................................................................................................................... 193
Outgoing SMTP Mail Server ................................................................................................................ 151, 195, 196
Output Activated Event ........................................................................................................................................ 149
Output Changed Event ........................................................................................................................................ 149
Output Deactivated Event .................................................................................................................................... 149
Output Status Icons ............................................................................................................................................. 132
Output, Automatic (Rule-Based) Activation of ...................................................................................................... 112
Output, Managing ................................................................................................................................................ 111
Output, Manual Activation of ................................................................................................................................ 112
Overview Pane, Management Client...................................................................................................................... 55
www.milestonesys.com
Page 247
Index
IPV6
Panes, Customizing Management Client's............................................................................................................. 60
Panomorph Support ............................................................................................................................................... 96
Panomorph Support, Disabling .............................................................................................................................. 96
Panomorph Support, Enabling ............................................................................................................................... 96
Patrolling, PTZ ..................................................................................................................................................... 120
Pause Patrolling on … (Rule Action).................................................................................................................... 141
Playback Video (Camera-Related Role Settings) ................................................................................................ 170
Plugin-Related Events ......................................................................................................................................... 147
Port 5432 ............................................................................................................................................................... 36
Port 7563 ............................................................................................................................................................... 36
Port 9993 ............................................................................................................................................................... 36
Port Conflict ........................................................................................................................................................... 44
Ports ...................................................................................................................................................................... 35
Pre-alarm Images ................................................................................................................................................ 147
Prebuffering ................................................................................................................................................. 128, 129
Presets Positions, PTZ ........................................................................................................................................ 123
Preview Pane ............................................................................................................................................. 55, 56, 63
Preview Pane, Choice of Live or Recording Streams ............................................................................................ 56
Preview Pane, Management Client ........................................................................................................................ 56
Privacy Masking ................................................................................................................................................... 119
Properties Pane, Management Client .................................................................................................................... 56
Prune and Groom Databases ................................................................................................................................ 70
PTZ Priority (PTZ-Related Role Setting) .............................................................................................................. 172
PTZ Rights, Roles ................................................................................................................................................ 171
PTZ Tab, Hardware Properties ............................................................................................................................ 126
PTZ, Camera Properties ...................................................................................................................................... 123
PTZ, Cameras on Video Encoders ...................................................................................................................... 126
PTZ, Rights to Use............................................................................................................................................... 171
Public IP Access .................................................................................................................................................... 85
ReadOnly (View Group-Related Role Settings) ................................................................................................... 173
Record on Motion (Default Rule).......................................................................................................................... 146
Record, Camera Properties ................................................................................................................................. 127
Record, Microphone Properties ........................................................................................................................... 127
Record, Speaker Properties ................................................................................................................................. 127
Recording Frame Rate......................................................................................................................................... 127
Recording Server Related Events ........................................................................................................................ 149
Recording Server Service, Starting/Stopping ....................................................................................................... 228
Recording Server, Multiple Instances .................................................................................................................... 39
Recording Servers, Managing................................................................................................................................ 86
Recording Started Event ...................................................................................................................................... 149
Recording Stopped Event .................................................................................................................................... 149
Recording Streams, Preview Images in Management Client ................................................................................. 56
Recording, Enabling/Disabling ............................................................................................................................. 127
www.milestonesys.com
Page 248
Index
IPV6
Recording, Enabling/Disabling for Camera .......................................................................................................... 127
Recording, Enabling/Disabling for Microphone .................................................................................................... 127
Recording, Enabling/Disabling for Speaker ......................................................................................................... 127
Recurring Time, Time Profiles.............................................................................................................................. 160
Registered Services ..................................................................................................................................... 191, 192
Remote Client, Accessing ...................................................................................................................................... 17
Remote Clients .......................................................................................................................................... 14, 15, 17
Removal ................................................................................................................................................................. 21
Replacing a Recording Server ............................................................................................................................... 87
Restore Default Live Frame Rate (Rule Action) ................................................................................................... 140
Restore Default Recording Frame Rate (Rule Action) ......................................................................................... 140
Resume Patrolling (Rule Action) .......................................................................................................................... 141
Rights, Specifying for a Role ................................................................................................................................ 169
Roles, Adding....................................................................................................................................................... 164
Roles, Assigning Users and Groups to ................................................................................................................ 163
Roles, Deleting..................................................................................................................................................... 165
Roles, Effective .................................................................................................................................................... 166
Roles, Managing .................................................................................................................................................. 164
Roles, Renaming ................................................................................................................................................. 165
Roles, Specify Rights of ....................................................................................................................................... 169
Roles, Viewing a User's/Group's .......................................................................................................................... 166
Rule Log ...................................................................................................................................................... 176, 177
Rule Wizard ................................................................................................................................................. 153, 155
Rules.......................................................................................................99, 100, 101, 137, 138, 151, 153, 154, 155
Rules, Activating/Deactivating.............................................................................................................................. 158
Rules, Copying..................................................................................................................................................... 157
Rules, Creating New ............................................................................................................................................ 155
Rules, Deleting..................................................................................................................................................... 157
Rules, Editing ....................................................................................................................................................... 157
Rules, Renaming ................................................................................................................................................. 157
Rules, Validating .................................................................................................................................................. 158
Save Attached Image (Rule Action) ..................................................................................................................... 144
Send Notification to ... (Rule Action) .................................................................................................................... 143
Send SNMP Trap (Rule Action) ........................................................................................................................... 144
Server Logs.................................................................................................................................. 176, 178, 179, 195
Server Logs, Exporting ........................................................................................................................................ 178
Server Time Synchronization ................................................................................................................................. 94
Service Channel................................................................................................................................. 32, 33, 34, 228
Service Channel Installation ................................................................................................................................ 228
Service Registration API (Application Role Setting) ............................................................................................. 173
Set Device Output to (Rule Action) ...................................................................................................................... 142
Set Live Frame Rate on (Rule Action) ................................................................................................................. 140
Set Matrix to View (Rule Action) .......................................................................................................................... 144
www.milestonesys.com
Page 249
Index
IPV6
Set Recording Frame Rate on (Rule Action) ........................................................................................................ 140
Settings Changed Error Event ............................................................................................................................. 149
Settings Changed Event ...................................................................................................................................... 149
Settings, Camera Properties ................................................................................................................................ 131
Settings, Hardware Properties ............................................................................................................................. 131
Settings, Input Properties ..................................................................................................................................... 108
Settings, Microphone Properties .......................................................................................................................... 131
Settings, Output Properties .................................................................................................................................. 113
Settings, Speaker Properties ............................................................................................................................... 131
Setup (Application Role Setting) .......................................................................................................................... 173
Shortcut (Camera Info Property) .......................................................................................................................... 104
SLC .......................................................................................................................................................... 68, 69, 211
Smart Client Profiles ............................................................................................................................ 134, 135, 159
Smart Client, Camera Shortcuts in....................................................................................................................... 104
Smart Client, Installation ........................................................................................................................................ 15
Smart Client, Silent Installation of .......................................................................................................................... 16
Smart Client, Upgrading ......................................................................................................................................... 43
Smart Client, View Groups for.............................................................................................................................. 132
Smart Clients ................................................................................................................................................... 14, 15
Smart Search (Camera-Related Role Settings) ................................................................................................... 170
SMTP Server Port .......................................................................................................................................... 44, 230
SMTP Service .................................................................................................................................. 44, 45, 150, 196
SMTP, Outgoing Mail Server ....................................................................................................................... 151, 196
SMTP, Pre-Alarm Images via............................................................................................................................... 147
SNMP .......................................................................................................................................................... 144, 233
Software License Code .............................................................................................................. 67, 68, 69, 200, 211
Speak Live (Speech-Related Role Setting).......................................................................................................... 172
Speak Priority (Speech-Related Role Setting) ..................................................................................................... 172
Speaker ......................................................................................................................................... See Loudspeaker
Speaker Status Icons ........................................................................................................................................... 132
Speakers, Managing ............................................................................................................................................ 114
Speech Rights, Roles .......................................................................................................................................... 172
SQL Server ...................................................................................................22, 24, 41, 46, 210, 211, 212, 213, 214
Standard Tume/Daylight Saving Time ................................................................................................................. 234
Start Audio Feed (Default Rule) ........................................................................................................................... 146
Start Feed (Default Rule) ..................................................................................................................................... 145
Start Feed on (Rule Action) ................................................................................................................................. 139
Start patrolling on ... (Rule Action) ....................................................................................................................... 141
Start Plugin on (Rule Action) ................................................................................................................................ 143
Start recording (Rule Action) ................................................................................................................................ 139
Status (Application Role Setting) ......................................................................................................................... 173
Status Icons ......................................................................................................................................................... 132
Status Messages, Failover Server Service .......................................................................................................... 219
www.milestonesys.com
Page 250
Index
IPV6
Stop Feed (Rule Action)....................................................................................................................................... 139
Stop Plug-in on ... (Rule Action) ........................................................................................................................... 143
Stop Recording (Rule Action)............................................................................................................................... 139
Storage, Recording Server Properties ................................................................................................................... 90
Streams, Camera Properties................................................................................................................................ 110
Summer/Winter Time ........................................................................................................................................... 234
Synchronization, Time on Servers ......................................................................................................................... 94
System Log .......................................................................................................................................... 176, 178, 179
System Requirements.............................................................................................................................................. 9
Tampering Event.................................................................................................................................................. 148
TCP Information Port ........................................................................................................................................... 230
Temperature Event .............................................................................................................................................. 148
Time Profiles, Managing ...................................................................................................................................... 159
Time Server ........................................................................................................................................................... 94
Tokens Requiring Time Synchronization on Servers ............................................................................................. 94
Tools Menu, Management Client ........................................................................................................................... 60
Trademarks .............................................................................................................................................................. 5
Transact Servers, Adding as Registered Services ............................................................................................... 192
Trigger User-defined Event (User-Defined Event Role Setting) ........................................................................... 173
Troubleshooting, Installation .................................................................................................................................. 43
TTL .................................................................................................................................................................. 83, 84
Typical Rules ....................................................................................................................................................... 145
Uninstallation ......................................................................................................................................................... 39
Unknown Hardware, Automatic Hardware Detection ............................................................................................. 76
Updates ................................................................................................................................................................... 7
Upgrading from a Previous Version ....................................................................................................................... 41
User Rights ............................................................................................................................................................ 49
User-Defined Event Rights, Roles ....................................................................................................................... 173
User-Defined Events, Managing .......................................................................................................................... 161
User-Defined Events, Selecting in Rules ............................................................................................................. 139
Users, Adding after Defining Roles ...................................................................................................................... 166
Users, Adding Without Active Directory ............................................................................................................... 167
Users, Managing .................................................................................................................................................. 166
Validation, Rule .................................................................................................................................................... 158
Video Device Drivers ....................................................................................................................... 42, 43, 217, 218
Video Encoders, PTZ Cameras on ...................................................................................................................... 126
Video Lost Event .................................................................................................................................................. 148
Video Servers ............................................................................................................................See Video Encoders
View (Camera-Related Role Settings) ................................................................................................................. 170
View Group Rights, Roles .................................................................................................................................... 173
View Groups, Managing ....................................................................................................................................... 132
View live within time profile (Camera-Related Role Settings) .............................................................................. 170
View Menu, Management Client ............................................................................................................................ 60
www.milestonesys.com
Page 251
Index
IPV6
Virtual Servers, Installation on ............................................................................................................................... 21
Virtualization .......................................................................................................................................................... 21
Virus Scanning ......................................................................................................................................... 51, 73, 232
Visible (Camera-Related Role Settings) .............................................................................................................. 170
Visible (Input-Related Role Settings) ........................................................................................................... 171, 173
Visible (Matrix-Related Role Setting) ................................................................................................................... 174
Visible (Microphone-Related Role Settings) ........................................................................................................ 170
Visible (Output-Related Role Settings) ................................................................................................................ 171
Visible (Speaker-Related Role Settings) .............................................................................................................. 171
Web Page, Management Server's ......................................................................................................................... 47
Web Page, XProtect Corporate Applications ......................................................................................................... 47
Web Server Port .................................................................................................................................................. 230
Windows Authentication, Management Client Login .............................................................................................. 58
Winter/Summer Time ........................................................................................................................................... 234
XProtect Corporate Applications Web Page .......................................................................................................... 47
XProtect Enterprise Servers ................................................................................................ 174, 189, 190, 191, 192
XProtect Enterprise Servers, Role Setting for .............................................................................................. 189, 190
XProtect Matrix .................................................................................................................................... 137, 144, 174
XProtect Transact Servers, Adding as Registered Service .................................................................................. 192
www.milestonesys.com
Page 252
Index
Milestone Systems offices are
located across the world. For
details about office addresses,
phone and fax numbers, visit
www.milestonesys.com.