Interlogix is part of UTC Climate, Controls & Security, a unit of United
Technologies Corporation. All rights reserved.
Trademarks and patentsInterlogix, TruVision, and logos are trademarks of United Technologies.
Microsoft, Internet Explorer, and W indows are registered trademarks of Microsoft
Corporation in the United States and/or other countries. Apple, iPad, iPhone, and
iTunes are registered trademarks of Apple Inc. Android is a trademark of Google,
Inc. Other trade names used in this document may be trademarks or registered
trademarks of the manufacturers or vendors of the respective products.
ManufacturerInterlogix
3211 Progress Drive, Lincolnton, NC 28092 USA
Authorized EU manufacturing representative:
The TruVision Software Video Recorder (SVR) System User Guide discusses the general capabilities
and technical specifications of the TruVision SVR system. This document also discusses the related
configuration requirements for the TruVision Navigator software.
TruVision SVR Overview
TruVision SVR is the software-based recorder platform for the TruVision product family, giving the
flexibility of commercial-off-the-shelf server support for scalable video recording needs.
TruV ision Navigator is the interface used to view and manage the data recorded in the T ruVision SVR
system. TruVision Navigator v5.0 or a later version is required to manage TruVision SVR. Data can
be accessed and viewed over a LAN or the Internet. Through remote viewing and management of
third-party cameras, TruVision SVR expands the flexibility of corporate security systems.
TruVision SVR, utilizing the technology of IP-addressable cameras, allows system operators to
access and program their cameras from anywhere in the world. These network digital video cameras
are designed specifically for remote monitoring and management applications such as security and esurveillance.
All IP cameras must have their IP addresses configured according to their respective user guide(s).
The IP addresses may also be entered when configuring the camera in the TruVision Navigator
management software.
Once SVR is installed on a system and the system is in production, it is recommended that security on
these servers should be locked down by the system administrator so that only users with valid
Windows domain accounts have access to video. With the introduction of the browser-based
applications, the ability to access video servers is made much easier using Microsoft domain
authentication. It is highly recommended to deny access to these servers for a secure deployment.
TruVision SVR System User Guide9
TruVision SVR Overview
TruVision SVR Configuration
Storage Space Reservation
TruV ision SVR content is stored in separate tracks that contain information on the index, video status,
and events.
TruVision SVR always keeps a certain amount of disk space reserved to be in accordance with
Microsoft’s drive guidelines. Ten percent of the overall disk space is reserved for these guideline
requirements and an additional ten percent is reserved for event storage. In total, twenty percent of the
hard disk space is already in use and cannot be used freely.
Because TruVision SVR content is stored in separate files if even one of those files is deleted or
corrupted video may become inaccessible. For instance, if the index track no longer exists you may
not be able to use video tracking. It is advisable to follow basic backup and security measures to make
sure your data is protected against hardware and network failures.
If your video becomes inaccessible, contact the Interlogix T echnical Support Group to assist you with
data recovery.
10TruVision SVR System User Guide
Digital Video Prerequisites
Digital Video Prerequisites
Time Synchronization
For digital video system to work properly, time must be synchronized on all computers. Third-party
tools are available to synchronize times across multiple time zones. If no NTP source is available,
TruVision Navigator server can be used as the NTP server.
Anti-Virus Software
If this type of software is required (due to corporate policy, for instance), then you must adhere to the
following guidelines:
•For Real-Time protection, you must exclude all files with the extensions .SPFS, .INFO, .LVI,
.LEI, and .LNR.
•For Real-Time protection and virus scan, you must exclude the data drives.
Windows Updates
When running Windows updates, be aware that they require a full shut down of your computer. Make
sure that these updates are scheduled to run when either recording will not be necessary or when
backup or fail over systems are properly configured and running.
Storage File Purging
If the system runs out of hard disk space while the system’s cameras are configured for storage
capacity, the oldest video files are deleted regardless of what camera they are on. In addition to video
files, TruVision SVR content is stored in separate tracks that contain information on the index, video
status, and events.
This can lead to potentially problems if not accounted for. For example, consider a case where the
retention policy is set to five days for all channels, except for one channel which is configured for a
30-day retention policy. The reclamation logic will reclaim files for the channel with 30 day retention
that are 6-30 days old before reclaiming files from any other channel. This would significantly affect
the amount of video that would be stored for the 30 day retention channel.
TruVision SVR System User Guide11
TruVision SVR Overview
12TruVision SVR System User Guide
CHAPTER 2TruVision SVR Network
Configurations
It is very important that all computers on the TruVision SVR Network are on the same domain or
trusted domain. If they are not, the TruVision SVR will not function properly.
Network Configuration
The following firewall and permission information needs to be configured correctly for the TruVision
SVR to work correctly.
Windows Firewall
By default, the Windows firewall is enabled. The system administrator must determine whether
firewall services are used on their system. If the firewall is enabled, it will prevent the security
management system software from functioning properly until certain things are added to the
exception list, which defines which components and ports should not be blocked by the firewall. If
the firewall is enabled during installation of the security management system software, the exception
list will be automatically populated.
IMPORTANT: Since certain elements are added to the exception list, it is mandatory that the
Don’t Allow Exceptions check box on the General tab of the Windows
Firewall dialog is not selected.
Windows Firewall Settings
Exception List:
• TruVision SVR services:
•LnrCapSvcu
•LnrRetrSvcu
•LnrRTPServer
•LpsSearchSvc
• RPC Port (TCP/IP 135)
• RTP Port (TCP/IP 554)
TruVision SVR System User Guide13
TruVision SVR Network Configurations
• UDP Port (5000)
ICMP Settings:
• Allow incoming echo requests
Windows Authentication Model
The process used by Windows to verify a client’s identity is called authentication. In order to properly
set up a system or troubleshoot an existing installation, the first step is to determine the identity of the
client attempting to connect to the server.
Here are some general guidelines:
• Interactive processes always run with the identity of the user that launched them, or they can be
launched with credentials of a different user through the “runas” command.
• Services typically run under the SYSTEM account (or another account specified through
Windows Services).
When a client connects to a remote server, the client’s identity is sent to that machine, and that system
authenticates the client. This process can have several outcomes depending on which user account is
used by the client:
• If both machines are in a domain and the domain user is used, then the server will use the domain
controller to authenticate the incoming client connection.
• If the client used the local machine account and the same local account with the same password
exists on the server, then that account will be used.
Note: If the same local account exists on the server, but the password is different, the client’s
connection attempt will immediately return failure. It will not default to the method
described next.
• If the client used the local machine account and an account with that name is unknown to the
server, an incoming connection will be assigned the ANONYMOUS user on the remote machine.
Note: There is a security policy which allows ANONYMOUS users to be part of the
EVERYONE group, but by default the EVERYONE group only includes users whose
identity was established in some way (i.e., not anonymous).
Local vs. Remote Permissions
Extended Windows security model, introduced in Windows XP SP2 and Windows 2003 Server SP1,
split permissions listed in the previous section into two separate parts: local and remote. This allows
system administrators more granular control over object security.
As the client-server connection is analyzed, the location of the components will determine which
permissions (launch, activation, and access) will be used. If both components are running on the same
machine, local permissions will be used. Otherwise, Windows will use remote permissions.
14TruVision SVR System User Guide
Loading...
+ 30 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.