Tag: XDV

Categories
Knowledge Support Support exacqVision Client Categories Products Uncategorized

XDV Reference

*** INTERNAL USE ***

Type Definitions

  • Integer – Numeric value
  • Bool – 1 or 0 value where 1 is ‘enabled’ and 0 is ‘disabled’
  • String – Any text value
  • DIP – Device Independent Pixel (represents screen coordinates and sizes)
    • Windows
      • If the system is not using any sort of DPI or screen scaling represents actual pixel values
      • If screen scaling is in use then this number is multiplied by the scaling value
        • Example: A 4k monitor would typically use 200% scaling. A value of 1920 would represent your full display width (1920 * 200% = 3840)
    • Other platforms
  • Epoch – Numeric value representing the number of seconds since January 1st, 1970

The options described in the documentation below are listed in dictionary values, where possible. This is indicated by the key values listed between curly braces ‘{ }’. The key is followed by the description of the key value is colon separated, as in the following example:

    {key1:description1, key2:description2, …}

More than one Instance or Item tag may be defined.

Tags and attributes not included use client defaults.

<br>

XDV / XML Structure

&lt;exacqVision Init&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Instance&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Live&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Layout&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Item/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Layout&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Video&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Input/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Video&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Audio&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Input&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Audio&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/System&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Live&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Instance&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;SecurityIntegrations/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Sync/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Alerts/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;HWAccel/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Joystick&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt/Joystick&gt;
&lt;/exacqVision Init&gt;

<br>

exacqVision Init Attributes

AllowAccelerators
ShowSunkenBorder bool {0:disabled, 1:enabled}
ShowRecStatusBorder bool {0:disabled, 1:enabled}
ShowPTZFocusBorder bool {0:disabled, 1:enabled}
ShowOnScreeDisplay bool {0:disabled, 1:enabled}
UseOsdColor bool {0:disabled, 1:enabled}
Use OSD color for Serial Profiles
KeepAspectRatio bool {0:disabled, 1:enabled}
Keep aspect ratio during resize
RestoreOnAttnReq bool {0:disabled, 1:enabled}
Restore client on user attention request
MySystemsColMask
EntCamColMask
AnalogCamColMask
IPCamColMask
EntCamFilterTreeSize integer (DIP value)
Width of filter tree panel on Enterprise Cameras
NonEntCamFilterTreeSize integer (DIP value)
Width of filter tree panel on Camera Recordings
VGAAccelMode
VGAAccelColorspace
DisplayAdapter
TimelapsePlaybackInterval integer {0-15}
Immediate jump to next frame if gap exceeds X seconds
PanelSizeRatio integer {0:content, 1:window, 2:16×9, 3:4×3}
CameraSortOrder integer {0:default order, 1:ascending, 2:descending}
GroupsSortOrder integer {0:default order, 1:ascending, 2:descending}
MapsSortOrder integer {0:default order, 1:ascending, 2:descending}
ViewsSortOrder integer {0:default order, 1:ascending, 2:descending}
EventsSortOrder integer {0:default order, 1:ascending, 2:descending}
BookmarksSortOrder integer {0:default order, 1:ascending, 2:descending}
ReportsSortOrder integer {0:default order, 1:ascending, 2:descending}
LiveAudioLipSync integer {0:auto, 1:enabled, 2:disabled}
AudioInputDevice integer
0 indexed list based on client detected devices
MuteDuringTwoWayAudio bool {0:disabled, 1:enabled}
AutoFillEmptyVideoPanels bool {0:disabled, 1:enabled}
CPUDecompResult
EnableIndicators bool {0:disabled, 1:enabled}
Show notifications for indicators
ConfirmClose bool {0:disabled, 1:enabled}
Prompts user for confirmation when attempting to close client window
CollapseLiveAutoContexts bool {0:disabled, 1:enabled}
Hide individual quality streams
CombineRegionOfInterestStreams bool {0:disabled, 1:enabled}
Manage all streams as quality streams
CameraPreviewMode integer {0:no preview, 1:thumbnail, 2:video
ShowSystemGroups bool {0:disabled, 1:enabled}
Show system group folders
RequireSSLCert bool {0:disabled, 1:enabled}
Require SSL certificate validation
UseSparseConnections bool {0:disabled, 1:enabled}
Use dynamic connections
SparseSystemCount integer
Number of systems using dynamic connections
EnableAllAnalytics bool {0:disabled, 1:enabled}
NormalLayoutCollapseMode integer {0:auto, 1:expanded, 2:collapsed}
EventButtonCollapseMode
LastUsedNormalLayout
LastUsedWidescreenLayout deprecated
LastUsedEventButton
DeblockingMode integer {0:auto, 1:enabled, 2:disabled}
H.264 deblocking, attempts to smooth sharp edges of decoded compressed video blocks
DirectSearch integer {0:disabled, 1:prefer system video, 2:prefer archive video, 3:prefer cloud video}
LastUsedLayout string
Language
Caption string
Title of the client window
ViewLayout integer
Number of panels in startup layout
LegacyAuthentication integer {0:only if required, 1:force, 2:never}
To be deprecated
TimeoutEnabled bool {0:disabled, 1:enabled}
Inactivity timeout
TimeoutMinutes integer {1-100}
KeepAliveSeconds
CurrentTheme string {light:Light, dark:Dark, classic:Classic}
DisableLiveStreams bool {0:disabled, 1:enabled}
Prevents user from viewing live video, does not affect search
Use12HourClock bool {0:disabled, 1:enabled}
TemperatureScale bool {0:Fahrenheit, 1:Celsius}
LicenseWarningAck bool {0:disabled, 1:enabled}
LicenseExpirationAck epoch
AutoCheckForClientUpdates bool {0:disabled, 1:enabled}
Found on client About pop-up
ShowNotificationsForIndicators bool {0:disabled, 1:enabled}
StartUpInstanceCount integer
Number of client instances to open
IgnoredVersion
SendAnonymousData bool {0:disabled, 1:enabled}
Found on client About pop-up
MotionColor integer {0-16777215}
Decimal color value
AlarmColor integer {0-16777215}
Decimal color value
FreeRunColor integer {0-16777215}
Decimal color value
PTZFocusColor integer {0-16777215}
Decimal color value
EventMonitorColor integer {0-16777215}
Decimal color value
BookmarkColor integer {0-16777215}
Decimal color value
NoColor integer {0-16777215}
Decimal color value
ClientIniAutoUpdateEna bool {0:disabled, 1:enabled}
Toggles automatic import on Add Systems
ClientIniAutoUpdateUrl string (path or url address to XDV file to import)
HWAccelLimit
ShowTrayIcon bool {0:disabled, 1:enabled}
Shows icon for Client instance in System Tray
See also: How to Configure No Close Client Usage
Delete bool {0:disabled, 1:enabled}
Disabling prevents Client instance closure.
See also: How to Configure No Close Client Usage

Instance Attributes

Number integer
Client instance number
Top integer (distance from top of desktop where client window begins)
Left integer (distance from left edge of desktop where client window begins)
Width integer (width of client window from left point)
Height integer (height of client window from top point)
Maximize bool {0:disabled, 1:enabled}
Client window fills screen or not
FullScreen bool {0:disabled, 1:enabled}
Fills screen and hides window controls (F11)
ShowToolbars bool {0:disabled, 1:enabled}
Hide/show toolbar (F8)
ShowNavPanel bool {0:disabled, 1:enabled}
Hide/show nav panel (F4)
LiveMode integer {0:cameras, 1:groups, 2:maps, 3:views}
Client opens with Live nav panel to the selected option
LiveModeNavButtons integer {0:collapsed, 1:cameras, 2:groups, 3:maps, 4:all expanded}
Expanded or collapsed level of nav panel buttons
SearchModeNavButtons integer {0:collapsed, 1:cameras, 2:groups, 3:maps, 4:views, 5:events, 6:bookmarks/cases}
Expanded or collapsed level of search panel buttons
RemoteControlEnabled bool {0:disabled, 1:enabled}
Toggles receiving of video push display
RemoteControlName string
MainSashPos integer (width of left side nav panel)
PTZControlLeft integer (distance from left edge of desktop where ptz pop-up begins)
PTZControlTop integer (distance from top edge of desktop where ptz pop-up begins)
SoftTriggerControlWidth integer (width of soft trigger pop-up from left point)
SoftTriggerControlHeight integer (height of soft trigger pop-up from top point)
SoftTriggerControlLeft integer (distance from left edge of desktop where soft trigger pop-up begins)
SoftTriggerControlTop integer (distance from top edge of desktop where soft trigger pop-up begins)
TwoWayAudioDialogWidth integer (width of two-way audio pop-up from left point)
TwoWayAudioDialogHeight integer (height of two-way audio pop-up from top point)
TwoWayAudioDialogLeft integer (distance from left edge of desktop where two-way audio pop-up begins)
TwoWayAudioDialogTop integer (distance from top edge of desktop where two-way audio pop-up begins)
RemoteControlDialogWidth integer (width of video push pop-up from left point)
RemoteControlDialogHeight integer (height of video push pop-up from top point)
RemoteControlDialogLeft integer (distance from left edge of desktop where video push pop-up begins)
RemoteControlDialogTop integer (distance from top edge of desktop where video push pop-up begins)
RemoteControlGUID string

Live Attributes

View string (name of View)
Tour string (name of Tour)
EventMonitor string (name of Event Monitoring profile)
Must be Switch View type
StartLayout

Layout Attributes

Name string (layout name)
Rows integer (number of video panel rows to allot)
Cols integer (number of video panel columns to allot)

Item Attributes

X integer (beginning column number)
Y integer (beginning row number)
Width integer (number of columns to merge)
Height integer (number of rows to merge

System Attributes

Name string (host/IP:port)

Video Attributes

Position
Name string
CameraID integer
Device string (IP address)
DeviceMac string (MAC address)
Number integer
Context
AutoContext integer
ToggleAnalytics integer

Audio Attributes

Name string
Device string (IP address)
DeviceMac string (MAC address)
Number integer
Context

Systems Attributes

Address
Port
Group
Name
AllowSave
Username
Password
PasswordType
Enabled
Latency
ExportPermission
EnterpriseManaged
UseSystemLogin
SupportsTargetSearch
IsEdgeServer
ExpandedInCamTree
FailoverState
Model
Serial
Package
Version
MAC
License
IsLicensed
IsEnterprise
IsEnterpriseEx
Expiration

Security Integrations

AlwaysPrompt bool

Sync Attributes

Enabled
ConnectedOnce
SyncFrequency
CredsSingleSignOn
CredsPrompt
Username
Password
PasswordType
UpdaterPath
UpdateCheckInterval
ForcedUpdates
Categories
Knowledge Support Support exacqVision Client Categories Products

Deploying System Lists to Client Users

In large organizations, such as multi-site enterprises, K-12 school districts, or university campuses, some admins will desire the ability to remotely manage the server connections their users have added within their ExacqVision Client application. This can result in faster deployments as well as less user support from their IT/Desktop Support teams, avoiding emailing, printing, or reciting information over the phone on how to enter each server’s IP address and that user’s login credentials.

This guide is written for ExacqVision Client version 9.4 and higher. Versions 9.2 and earlier used alternative file types.

This guide is broken into sections for readability but it is recommended to review each section.

<br>

Client Configuration File

The ExacqVision Desktop Client application saves settings information for each user account on the system, allowing users who share the same workstation to login with different operating system accounts and retain different server lists and client settings from each other. These settings are stored in an XML file titled, ‘edvrclient.xml‘, located in the following location:

Windows
C:\Users\%username%\AppData\Roaming\edvrclient\edvrclient.xml

Linux (Ubuntu)
/home/%username%/.edvrclient.dir/edvrclient.xml

macOS
/Users/%username%/Library/Application Support/edvrclient/edvrclient.xml

Each time the ExacqVision Client is opened, it refers to this file for its configuration, unless told otherwise.

<br>

Importing Via Client

There are four methods for populating a system list for client users. Within the client, these can be found on the ‘Add Systems‘ page by selecting the ‘Import/Export‘ tab.

  • Manual Import
  • Automatic Import – File on startup
  • Automatic Import – URL on startup
  • Automatic Import – Synchronize with Enterprise Manager

The first option is ‘Manual Import‘, using an XDV file. XDV is the file format ExacqVision exports, allowing you to configure one client as you’d like it, then export your System List in this XDV file for others to import. This method does little to help those deploying to many systems since it requires manually importing on each client instance.

XDV files are written in standard XML format, but are encrypted and associated to a MIME type which tells the workstation to open it with the ExacqVision Client application. XDVs contain a large amount of information about each connected server as well as client instance settings. XML tags and attributes not included in manually created files are filled in by the software with default information, meaning you only need to include the specific attributes relevant to your case. In this article we focus on providing a list of systems for users to connect to.

Beneath this is the ‘Automatic Import‘ section, which provides a few options. ‘File on startup‘ tells the client software to import client settings from the specified XDV file. This may reside on the local client workstation or on a network file share, but the share must be reachable when the client application is opened.

‘URL on startup‘ works in much the same way as ‘File on startup’, but allows the XDV file to reside at a web URL rather than a local directory or file share.

Finally, ‘Synchronize with ExacqVision Enterprise Manager‘, authenticates to an EM server for a list of ExacqVision Servers the authenticated account has access to and populates the System List based on the systems and user roles EM provides to that account. This method requires an Enterprise Manager instance as well as Enterprise licensed servers.

A benefit of using the ‘Automatic Import’ options is that administrators have control over which systems users have added to their client software and since the software checks this each time it opens, it changes any client settings the user may have tried to make since it was last used. This last part is important since users that you choose to prompt for credentials with each use may try to check the ‘Save credentials’ option, but forcing the client to use this file each time it opens causes them to be prompted for credentials anyway. It also adds or removes systems from their System List as you make changes to your systems and network.

<br>

Creating a Populated System List

The following steps will detail how to populate a user’s System List, which may be a common administrative task in environments where workstations are often reimaged or new users need to add several systems to their client instances.

Using a text edit, you will edit your own files following the examples below.

Ex. 1 – Always prompt for credentials
&lt;exacqVisionInit&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="192.168.0.200" Port="22609"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="192.168.0.201" Port="22609"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="exacq.mysite.com" Port="22609"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Systems&gt;
&lt;/exacqVisionInit&gt;

Within the System tag, in the Address attribute, you will enter the IP address or hostname of your systems. The template provides examples. The default listening port for ExacqVision Server software is 22609. If you have changed this, enter your port number in the corresponding Port attribute for each system.

In this, the most basic configuration, the System rows above end there and the client software will prompt the user to enter their credentials each time the client is opened. Repeat the System rows as many times as needed.

Ex. 2 – Use credentials entered below
&lt;exacqVisionInit&gt;
&nbsp;&nbsp;&nbsp;&nbsp&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="192.168.0.200" Port="22609" Username="myusername" Password="mypassword" PasswordType="0"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="192.168.0.201" Port="22609" Username="myusername" Password="mypassword" PasswordType="0"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="exacq.mysite.com" Port="22609" Username="myusername" Password="mypassword" PasswordType="0"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp&lt;/Systems&gt;
&lt;/exacqVisionInit&gt;

Adding Username and Password attributes provide additional customization. If you choose to add these attributes you will need to enter the user account credentials you’ve previously created on the system for this user. You must also set the PasswordType attribute to a value of 0. After the client imports the settings, it encrypts the plaintext password entered into the edvrclient.xml files mentioned above and the PasswordType value is changed to 3.

Ex. 3 – Synchronize with Enterprise Manager
&lt;exacqVisionInit&gt;
&nbsp;&nbsp;&nbsp;&nbsp&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="192.168.0.200" Port="22609" UseSystemLogin="1"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="192.168.0.201" Port="22609" UseSystemLogin="1"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;System Address="exacq.mysite.com" Port="22609" UseSystemLogin="1"/&gt;
&nbsp;&nbsp;&nbsp;&nbsp&lt;/Systems&gt;
&lt;/exacqVisionInit&gt;

The above example will add the listed systems for the client, but rather than including login credentials or prompting the user for credentials, will tell the client to login with Single Sign-On. Note that this requires the servers to have Active Directory/LDAP configured and the client workstation must be a member of the domain. See other guides for help configuring Active Directory/LDAP.

You may mix and match the examples of System authentication from the previous examples. For instance, you may add one system that logs the user in with credentials provided, but prompt for credentials for another system.

<br>

Enabling Your Configuration on Client Workstations

With the file created, you may now save it in a couple of ways.

If you save the file as an XML file, named ‘edvrclient.xml’, and replace the existing ‘edvrclient.xml’ file in the client directory mentioned earlier, the client will use this the next time it opens.

You may also save the file with a descriptive name of your choice and ensure that the file extension is not XML, but is XDV instead. This XDV file will not be encrypted yet. If you wish to encrypt it, you must first open it with the ExacqVision Client then export a new XDV file from the ‘Import/Export‘ tab on the ‘Add Systems‘ page. Exporting automatically encrypts the contents but you will be unable to edit it again after this process. As mentioned previously XDV files are associated with a MIME type, allowing a user to double-click on the file to open the ExacqVision Client with its configuration. For this reason an XDV file placed on a user’s Desktop provides an easy way for them to open the client with your desired configuration.

With this in mind, you may create one or more XMLs or XDVs to help specific users populate and login to a list of systems, or control a list of systems for a group of users. You will then need to find a method to deploy this to your user’s client workstations. You may choose to use third-party software deployment tools or you may opt to create a script that copies the file(s) to the desired workstations. Note, Exacq Support does not provide such scripts or provide help creating such scripts for your organization. We review some deployment options below.

  1. Copy an XDV file to the user’s Desktop. When the user clicks to run it, the ExacqVision Client opens with the included configuration parameters.<br><br>
  2. Copy the XML file to the client settings directory to replace the existing ‘edvrclient.xml’ file.

    The client automatically uses this configuration when it is launched again. Don’t forget that each user account on a workstation with multiple users will have their own ‘edvrclient.xml’ file in the directories listed near the top of this guide.<br><br>
  3. Save the XDV file to a network location or directory on the client workstation. Copy an ‘edvrclient.xml’ file to the client settings directory on the workstation to instruct the client, when launched, to automatically import the XDV file configuration.

    This method makes the most sense using a networked location because you only need to deploy one file to the workstation (‘edvrclient.xml’), rather than two, but we will cover how to perform both options below.

<br>

Instruct edvrclient.xml to Auto Import XDV

Using a text editor, you will edit your own files using the examples below.

Ex. 4 – Auto Import File on Startup
&lt;exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="C:\Users\RSmith\Documents\Demo.xdv"&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Systems&gt;
&lt;/exacqVisionInit&gt;

In this example we add the attribute ClientInitAutoUpdate=”1″ to the exacqVisionInit tag, which enables the ‘Auto Import’ option. The ClientIniAutoUpdateUrl attribute sets the value to the location of the XDV file you want to import, with a list of servers we want the user to have. In this example, the location is a local directory on a Windows workstation for a user named ‘RSmith’, within his Documents directory. If you want to maintain your XDV files on a network share, be sure the share is always available, or the client will be unable to import the file.

Ex. 5 – Auto Import URL on Startup
&lt;exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://demo.exacq.com/Demo.xdv"&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Systems&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;/Systems&gt;
&lt;/exacqVisionInit&gt;

To import from a URL instead, simply change the ClientIniAutoUpdateUrl value to the URL, as shown in the above example.

Changing the file to force client synchronization with your ExacqVision Enterprise Manager server requires a few more edits.

Ex. 6 – Auto Import Synchronize with Enterprise Manager with credentials
&lt;exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://192.168.0.4"&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Sync Enabled="1" Username="myusername" Password="mypassword" PasswordType="0"/&gt;
&lt;/exacqVisionInit&gt;

The value of the ClientIniAutoUpdateUrl attribute changes to the address/hostname of your Enterprise Manager server.

A new Sync tag replaces the Systems tag in this example, and our Enabled attribute for it has a value of 1. The Username and Password values will be for the user credentials for the Enterprise Manager user. Once again, if opting to enter the Username and Password, you must add the PasswordType attribute and set the value to 0.

Ex. 7 – Auto Import Synchronize with Enterprise Manager prompt for credentials
&lt;exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://192.168.0.4"&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Sync Enabled="1" CredsPrompt="1"/&gt;
&lt;/exacqVisionInit&gt;

To prompt the user to enter their Enterprise Manager credentials each time the client is opened, remove the Username and Password attributes and add the CredsPrompt attribute with a value of 1, as shown above.

Ex. 8 – Auto Import Synchronize with Enterprise Manager single sign-on
&lt;exacqVisionInit ClientIniAutoUpdateEna="1" ClientIniAutoUpdateUrl="https://192.168.0.4"&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&lt;Sync Enabled="1" CredsSingleSignOn="1"/&gt;
&lt;/exacqVisionInit&gt;

If your Enterprise Manager instance is configured for Active Directory/LDAP and the client workstations are members of your domain, you may also set the option to connect using Single Sign-On.

This example removes the CredsPrompt attribute and uses the CredsSingleSignOn attribute instead, setting the value to 1.

<br>

Categories
Knowledge Support Support exacqVision Client Categories

How to Configure No Close Client Usage

Beginning with version 9.4, the exacqVision Desktop Client offers the ability for administrators to prevent users from deactivating an Event Monitoring profile. 

In previous versions, when an Event Monitoring profile was active a user could accidentally deactivate the profile by navigating away from it or by closing the client window.

With Client 9.4 or higher, an administrator can keep an Event Monitoring profile active even if the user tries to close the client window. In this scenario, if the user tries to close the client window it remains active in the system tray. When an event occurs, the window will reappear and come to the foreground in front of any other client instances that may be running.

A user that wants to view other cameras, perform video searches or perform other actions can still do so by opening another client instance, but they won’t miss an event from their Event Monitoring profile. 

To configure this, perform the following steps:

  1. Upgrade the exacqVision Desktop Client to 9.4 or greater.
  2. Open a file editor, such as Notepad for Windows, or gedit on Ubuntu Linux.
  3. Use the sample code, below, as your template.
    • Replace MYPROFILE with the name of the Event Monitoring profile you’ve created and wish to remain active.
    • Replace MYEVSERVER with either the system name or IP address of the exacqVision Server.
&lt?xml ?&gt<br>
&ltexacqVisionInit ShowTrayIcon="1" ShowToolbars="0" ShowNavPanel="0" Caption="Event Monitor System Tray" Delete="0"<br>RestoreOnAttnReq="1" Maximize="1" AllowAccelerators="0"&gt<br>
        &ltLive EventMonitor="MYPROFILE"&gt<br>
                &ltSystem Name="MYEVSERVER"/&gt<br>
        &lt/Live&gt<br>
&lt/exacqVisionInit&gt

<br>

  1. Save the newly created file to the Desktop, or other desired location, with a descriptive name and the .XDV file extension.

    In editors such as Notepad, you will need to use the ‘Save as type’ drop-down menu to select ‘All Files (*.*)’, then enter the desired file name with the .XDV extension included at the end.
    <br>

You may place this .XDV file on any client machine that will connect to the server to run. When run, the client will open to the chosen Event Monitoring profile and cannot be deactivated. 

<br>