Month: August 2010

Categories
Knowledge Support Support exacqVision Server Categories Products

Troubleshooting an eDVR Board

To troubleshoot an eDVR board, complete the following steps:

  1. Download Microsoft’s DebugView program from http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx<br><br>
  2. Open the file
    C:\Windows\xdvapi.ini
    Note: In Windows 7 or Windows Vista, run Notepad as an Administrator and then select Open from the File menu and change the file type to ‘All Files (*.*)’ to open the INI file.<br><br>
  3. Find the [CONFIG] section, or create it if necessary.<br><br>
  4. Add a line after [CONFIG] as follows:
    [CONFIG]
    ODSFlags=0x80000003<br><br>
  5. Run the DebugView application.<br><br>
  6. Stop the ExacqVision Server service.<br><br>
  7. Start ExacqDV Control Center. Several lines of information will scroll in the DebugView window. Click Clear in the DebugView toolbar.
    Note: The Clear button looks like an eraser and a piece of paper and can be found below the Help menu.<br><br>
  8. In the ExacqDV Control Center tree, select the eDVR board that you want to troubleshoot. A “-9005” error will appear along with additional information in DebugView.<br><br>
  9. Copy the information from DebugView into an email and send it to support@exacq.com.

<br>

Categories
Knowledge Support Support Categories exacqVision Hardware Products

Are eDVR boards compatible with an LGA 1156 motherboard?

Yes. Exacq has tested compatibility with the following configuration:

<br>

*Intel Q57TM Micro-ATX motherboard

*Two eDVR boards

*PCIe 1x Riser

<br>

At this time, Q57 is the only chipset that is supported for use with the PCIe 1x riser card.

<br>

Are-eDVR-boards-compatible-with-an-LGA-1156-motherboard.pdf
Categories
Knowledge Support Support exacqVision Webservice Categories Products

Changing Web Server Default Image Quality (Legacy)

Instructions

These instructions only apply to web services 9.4 and earlier. 

The changes described only affect the default image quality in “simple” mode and this process is not upgrade safe. You must perform this process again each time you upgrade Web Server.

<br>

  1. For Windows: Browse to C:\Program Files\exacqVision\WebService\bin\templates.

    For Linux:     Browse to /usr/local/exacq/webservice/bin/templates.
  2. Open the file config.html.mako.
  3. Look for the following section:

    query_string = urllib.urlencode([(“s”, hex(server.id)),
                                       (“p”, camera.plugin),
                                       (“d”, camera.device),
                                       (“i”, camera.input),
                                       (“w”, “320”),
                                       (“h”, “240”),
                                       (“q”, “7”)])
  4. Add a line to the end of that section as follows:

    query_string = urllib.urlencode([(“s”, hex(server.id)),
                                       (“p”, camera.plugin),
                                       (“d”, camera.device),
                                       (“i”, camera.input),
                                       (“w”, “320”),
                                       (“h”, “240”),
                                       (“q”, “7”),
                                       (“r”, “5”)])
  5. Change the values to match your preferred settings for the following parameters:

    NOTE: Starting in Web Server 2.1, the following values are stored in a cookie generated from the Web Server. However, you can add these values to the config.html.mako file to override the cookie.

    w = width
    h = height
    q = quality
    r = refresh interval
  6. Save the file.
  7. Open or refresh the Web Server page in your web browser.

<br>

Categories
Knowledge Support Support Categories Products exacqVision Hardware

Using Remote Desktop to Manage Windows-based ExacqVision Servers

Remote Desktop allows you to connect to your Windows-based ExacqVision server over a network connection and operate it as if you were using the system directly. This can be especially useful when you want to upgrade the server software.

Using Remote Desktop across public networks or the internet introduces many of the same security concerns associated with any internet connection. You must use a Windows operating system user account with sufficient privileges when connecting to the server. Exacq Support cannot assist in retrieving/resetting lost operating system passwords. It is also recommended that you connect to the ExacqVision server over a Virtual Private Network (VPN) for increased security.

<br>

Windows 11

  1. You will need Windows 11 Pro or Enterprise.

    Check this by clicking the Windows (Start) button > Settings > System > About and locate the listed Edition beneath ‘Windows specifications’. <br><br>
  2. From this Settings menu, select Remote Desktop.
    Windows (Start) button > Settings > System > Remote Desktop<br><br>
  3. Set ‘Remote Desktop’ to ‘On’.<br><br>

Windows 10

  1. You will need Windows 10 Pro or Enterprise.

    Check this by clicking the Windows (Start) button > Settings > System > About and locate the listed Edition. <br><br>
  2. From the Settings menu, select Remote Desktop.
    Windows (Start) button > Settings > System > Remote Desktop<br><br>
  3. Turn on the toggle for Enable Remote Desktop.<br><br>

Windows 7

  1. You will need Windows 7 Pro or Enterprise.

    Check this by clicking the Windows (Start) button. Right-click Computer and choose Properties from the menu.<br><br>
  2. From the left-hand panel, select Remote settings.<br><br>
  3. In the ‘System Properties’ window, note the tabs across the top and select the Remote tab.<br><br>
  4. Beneath the Remote Desktop section, check the radio button for one of the Allow connections… options.<br><br>

Windows 7 Embedded

Early versions of ExacqVision systems manufactured with the Windows 7 Embedded operating system did not have Remote Desktop. These systems were manufactured between January and February 2014.

  1. Determine whether the system has Remote Desktop installed. Open the Windows (Start) button. Right-click Computer and choose Properties from the menu.<br><br>
  2. Select Advanced System Settings and look for a tab labeled Remote.
    • If the Remote tab exists, follow the steps under Windows 7 above to continue.
    • If you do not see this tab, Remote Desktop is not installed, continue with the steps below.<br><br>
  3. To install Remote Desktop on the system, perform the following:
    1. Download RDPPack.iso and burn this ISO to a CD/DVD.
    2. Insert the disc into the system’s optical disc drive or use an external disc drive connected to USB.
    3. The installer should run automatically. You will be prompted to enter administrator credentials to install RDP then restart the system.
    4. If the installer does not run automatically within 30-seconds, perform the following steps:
      • Click the Windows (Start) button and double-click Computer.
      • Select the CD/DVD drive.
      • Double-click, to run, the install.bat file.<br><br>
  4. Follow the steps above under Windows 7 to enable Remote Desktop.<br><br>

Making a connection

  1. Click the Windows (Start) button and begin typing to search for Remote Desktop Connection. Click on it to open.<br><br>
  2. In the Computer field, enter the name of the system name or the IP address of the system.
    <br><br>
    NOTE: If on a Domain, you may need open Show Options and change the User name field to include the domain name, i.e. – domain\username<br><br>

<br>

Categories
Knowledge Support Support exacqVision Client Categories Products

Windows Server & Client and OpenLDAP/Kerberos

The following process allows you to configure exacqVision permissions and privileges for accounts that exist on an OpenLDAP/Kerberos server:

1. On the OpenLDAP/Kerberos server, ensure that your installed schema includes the following object types:

inetOrgPerson (RFC 2798)
organization (RFC 2256)
krbPrincipalAux (provided by the Ubuntu krb5-kdc-ldap package)

And at least 1 of the following opject types:

groupOfNames (rfc 2256)
groupOfUniqueNames (rfc 2256) – supported with exacqVision 6.8+
organizationRole (rfc 2256) – supported with exacqVision 6.8+
posixGroup (rfc 2256) – supported with exacqVision 6.8+

2. On the OpenLDAP/Kerberos server, ensure that your user accounts exist as inetOrgPerson objects, and that each account is also marked with the krbPrincipalAux auxiliary object type. Ensure that each user account has the following attribute values:

cn — the user account’s display name (for example, “John Smith”).
krbPrincipalName — the user account’s Kerberos principal name (for example, “john.smith@REALM”).
entryUUID — the unique identifier for the user account, managed by the slapd daemon

3. On the OpenLDAP/Kerberos server, ensure that your user groups exist as organization objects and that each group has the following attribute values:

o — the group’s display name (for example, “Marketing”)
entryUUID — the unique identifier for the group, managed by the slapd daemon

And that each group uses the corresponding attribute to map users.

member (for groupOfNames)
uniqueMember (for groupOfUniqueNames)
roleOccupant (for organizationalRole)
memberUid (for posixGroup)

4. On the OpenLDAP/Kerberos server, ensure that your user accounts are associated with groups via an “o” attribute for each group. Each inetOrgPerson object can have as many associated “o” attribute values as desired. The attribute value should resemble “o=Engineers”, for example, instead of “o=Engineers,dc=exacq,dc=test,dc=com.”

5. Make sure the OpenLDAP/Kerberos server’s fully qualified host name can be resolved. To do this, open a command prompt, ping the fully qualified host name, and look for a reply.

6. Make sure you have access to the ksetup command by completing the following steps:

A. For Windows XP, install the Windows XP Service Pack 2 Support Tools, available from Microsoft; for Windows Vista, find and install the equivalent package. When installing Support Tools, select a “complete” install. After installation, log out of Windows and then log in again.

NOTE: Other recent Windows versions, such as Windows 7 and Windows Server 2003, already include the ksetup command.


B. Open a command prompt and verify that you can execute the ksetup command.

C. Execute ksetup commands to add your Windows machine to the OpenLDAP/Kerberos domain, as shown in the following examples (all are case-sensitive):

ksetup /addkdc EXACQ.TEST.COM kdc.exacq.test.com
ksetup /addkpasswd EXACQ.TEST.COM kdc.exacq.test.com
ksetup /setrealm EXACQ.TEST.COM
ksetup /setcomputerpassword YOURCOMPUTERPASSWORD

NOTE: Be sure to note your chosen computer password for steps later in this process.

7. Restart the server. When the login screen appears after the system restarts, notice that the drop-down list contains the OpenLDAP/Kerberos domain. Select the domain and log in.

8. Open a command prompt and use ipconfig to ensure that the hostname and primary DNS suffix are correct.

9. Note the fully qualified host name (hostname.primary-dns-suffix) and IP address of the exacqVision server computer that you will connect to, the OpenLDAP/Kerberos domain, and the fully qualified host name and IP address of the OpenLDAP/Kerberos server. For example:

evserver.exacq.test.com 192.168.1.16
exacq.test.com
kdc.exacq.test.com 192.168.1.70

10. If installing an exacqVision server, add a service principal name on the OpenLDAP/Kerberos server for the exacqVision server. To do this, open a terminal window on the OpenLDAP/Kerberos server and execute the following command (using your information where appropriate):


sudo kadmin.local
ank -e rc4-hmac:normal EDVR/evserver.exacq.test.com
quit

<br>

NOTE: All text after the forward slash should be lower case, and ‘EDVR’ must be upper case.

11. On the exacqVision server or client computer, download and install the exacqVision software from www.exacq.com. You must be logged in with Local Administrator privileges to do this. The software automatically starts after the installation is complete.

12. If installing an exacqVision server, license the exacqVision server as an Enterprise system. To do this, complete the following steps:

A. Install the exacqVision Client software on the server if it is not already installed.

B. Run the exacqVision Client and connect to the local server (127.0.0.1) using the default ‘admin’ account.

C. Open the System Setup page for the exacqVision server you want to license and select the System tab.

D. Enter the valid Enterprise license as generated by exacq Technologies and click Apply in the License section.


13. If installing an exacqVision server, configure the directory settings. To do this, complete the following steps:

A. In the exacqVision Client software, select the ActiveDirectory/LDAP tab on the System Setup page.

B. Select the Enable Directory Service checkbox.

C. Select OpenLDAP/Kerberos in the LDAP Schema drop-down list. D. Enter the OpenLDAP/Kerberos server’s IP address in the Hostname/IP Address field.

E. Select the SSL checkbox if you want LDAP operations to use secure SSL. If so, see the Configuring SSL on an exacqVision Server document.

F. Verify the OpenLDAP/Kerberos server’s connection port. Unless you have reconfigured your OpenLDAP/Kerberos server, the port should be 636 when using SSL, or 389 without SSL.

G. Enter the LDAP Base DN, the container of all directory user accounts or groups that you want to map in the exacqVision software. For example, if the domain were exacq.test.com, the LDAP Base DN might be:

CN=Users, DC=exacq, DC=test, DC=com

NOTE: Check with the system administrator for the correct LDAP Base DN for your situation.

H. Enter the LDAP Binding DN, the fully qualified distinguished name (DN) of a directory user who has access to view the records of the directory user accounts. It is recommended that you enter the Administrator user account as the LDAP Binding DN. For example, if the domain were exacq.test.com, the LDAP Binding DN of the Administrator account would be:

CN=Administrator, CN=Users, DC=exacq, DC=test, DC=com

I. Enter the password for the account entered in the previous step.

J. To prevent any non-directory users that have previously been created from connecting to the exacqVision server (optional), deselect Enable Local User Accounts.

K. Click Apply to connect. An indicator on the ActiveDirectory/LDAP tab displays the success or failure of the connection attempt.

<br>

Connecting to ExacqVision servers

You can connect to your Enterprise exacqVision servers from the Windows exacqVision Client software in any of the following ways:

A. You can use a local exacqVision username and password.

B. If you are already logged into Windows as a domain user, you can use your system login without entering a username or password. In this case, leave the username and password fields empty on the Add Systems page, select Use Single Sign-On, and click Apply.

C. You can use any domain user account. Enter the account name in user@REALM format as the username (for example, ‘test.user@EXACQ.TEST.COM’), and use the password associated with that account. The realm must be in upper case, as shown in the example. Do NOT select Use Single Sign-On with this login method.

NOTE: If you attempt to connect to an exacqVision server using your system login without first logging in to Windows through the domain, the connection will fail.

<br>

Adding exacqVision users from the OpenLDAP/Kerberos database

When the exacqVision server is appropriately configured and connected to your OpenLDAP/Kerberos server, the Users page and the Enterprise User Setup page each contain a Query LDAP button that allows you to search for users or user groups configured in OpenLDAP/Kerberos. You can manage their exacqVision server permissions and privileges using the exacqVision Client the same way you would for a local user. On the System Information page, the Username column lists any connected OpenLDAP/Kerberos users along with their OpenLDAP/Kerberos origin (whether each user was mapped as an individual or part of a user group) in parentheses.

<br>

Windows-Server-Client-and-OpenLDAP-Kerberos.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Configuring SSL on an exacqVision Server for Active Directory/LDAP (Windows)

exacqVision 7.2 and higher:

Check the box labeled “Use SSL” on the “ActiveDirectory/LDAP” configuration page, then press “Apply”.
<br>

exacqVision prior to 7.2:

This article contains procedures for configuring SSL on exacqVision servers. These steps are necessary if you want Active Directory operations to be made more secure by use of SSL on the exacqVision server.

While there are a number of ways that you can generate, install, and manage certificates in order to use SSL, this document will only describe one of the easiest ways to do so. You can simply export the trusted root certificate that already exists in your Active Directory domain, install it on each of your exacqVision Servers, and thereby enable SSL for successful operations. This article will give you step-by-step instructions on how to do this.

<br>

Export Trusted Root Certificate for Your Domain

  1. Log in to any Windows workstation that has already been added to your domain. You must have at least local admin permissions.
  2. Start the Microsoft Management Console (mmc.exe).
  3. If you haven’t already, add the Certificates snap-in:

    a) On the File menu, click Add/Remove Snap-In.
    b) Select Certificates and click Add.
    c) When prompted, select the option to manage certificates for your user account (instead of the service or computer account).
    d) Click Finish.
    e) Click OK to complete this step.
  4. Expand Certificates – Current User in the left pane.
  5. Expand Trusted Root Certification Authorities.
  6. Select the Certficates folder to display your workstation’s currently installed CA certificates. The Issued To field should contain something similar to mydomain-ROOT-CA, where mydomain is your domain name.
  7. Select that Issued To entry, and then right-click All Tasks and select Export.
  8. In the Certificate Export Wizard, select the format choice of Base-64 encoded binary X.509 (.CER). Save it to a local .cer file that you can relocate later. You will then install this same certificate file on every exacqVision Server for which you intend to use SSL.

<br>

Certificate Database Location on exacqVision Server

Whenever exacqVision Server attempts to connect to an Active Directory server, it creates the following files in the installation directory, if necessary:

  • cert8.db
  • key3.db
  • secmod.db

In the exacqVision Server installation directory on any exacqVision Server, the following command shows all certificates, including all trusted root certificates, that you have made available to that exacqVision Server for connecting to the directory via SSL:

certutil -L -d .
<br>

Import Trusted Root Certificate into Each exacqVision Server

  1. On the actual exacqVision Server, copy your trusted root certificate to the server’s installation directory.
  2. If you have not already verified your exacqVision Server’s LDAP configuration with SSL disabled, do this now. This will create your certificate database files if they do not already.
  3. From within the server’s installation directory, execute the following command as local admin:

certutil -A -n “my domain ca cert” -t “C,C,C” -a -i my_cert_file.cer -d .

where my_cert_file.cer represents your trusted root certificate file, and my domain ca cert represents the name by which you want this certificate to be known in the database.

  1. If you get a certutil error similar to “error converting ascii to binary,” try re-exporting your certificate. You might not have correctly selected the “base-64 encoded” format option as indicated.
  2. If you do not get any error messages, then your trusted root certificate should have been successfully imported into your certificate database. Verify by then executing this command:

certutil -L -d .

  1. If your certificate was successfully imported, you will see something similar to “my domain ca cert” and “C,C,C.
  2. On your exacqVision Server, run exacqVision Client and open the Active Directory/LDAP tab. Select the SSL checkbox (the port should automatically change to 636), and click Apply. Your exacqVision Server should then reconnect to your Active Directory domain controller.

NOTE: The attached article is an older document pertinent to using SSL for communication with an Active Directory or LDAP server.

<br>

Configuring-SSL-on-an-exacqVision-Server-for-Active-Directory-LDAP-Windows-1.pdf
Categories
Knowledge Support Support exacqVision Client Categories Products

MacOS & Mac OS X Client and Active Directory/OpenLDAP/Kerberos

Configuration

The following process allows you to configure ExacqVision permissions and privileges for accounts that exist on an Active Directory/OpenLDAP/Kerberos (directory) server.

NOTE: On a Windows platform, the domain controller must run on Windows Server 2003 operating system or later. If the Active Directory functional level is Windows 2000 or earlier, you must select Password Never Expires in the Active Directory Users and Computers snap-in for any user that will connect to an ExacqVision server.

  1. Note the fully qualified host name (hostname.primary-dns-suffix) and IP address of the ExacqVision server computer, the directory domain, and the fully qualified host name and IP address of the directory server. For example:
        evserver.exacq.test.com        192.168.1.16<br>
        EXACQ.TEST.COM<br>
        adserver2016.exacq.test.com    192.168.1.70<br>
  1. Make sure the fully qualified host names of the directory server and ExacqVision server can be resolved. To do this, open a terminal window, ping the fully qualified host names, and look for a reply. Make sure the IP addresses match the IP addresses of the servers as noted in the previous step.

    NOTE: If the fully qualified host names cannot be resolved for either server, configure your hosts file with the fully qualified host names, as in the following example:
        /etc/hosts<br>
        192.168.1.16        evserver.exacq.test.com<br>
        192.168.1.70        adserver2016.exacq.test.com<br>
  1. Configure Kerberos (KRB5) by completing the following steps:
  1. Execute Kerberos.app from /System/Library/CoreServers
  2. From the menu, select Edit and then Edit Realms.
  3. In the Edit Realms dialog, click the plus (+) button, and enter the Realm Name in upper case.
  4. Select the Servers tab, click the plus button (+), and enter the IP address or fully qualified domain name of the directory server. Leave KDC as the Type and 88 as the Port.
  5. Click Apply and OK to exit.
  6. Click New.
  7. Enter the username and password for the directory account. To avoid entering the password again after the ticket expires, select Remember This Password in My Keychain.
  8. Make sure the Realm entered earlier in this step is selected from the drop-down list.
  9. Click OK.
  10. If the connection is successful, select the new ticket and click Destroy.
  1. On the ExacqVision Client computer, download and install the ExacqVision software from Exacq.com.

Connecting to ExacqVision Servers

You can connect to your Enterprise ExacqVision servers from the MacOS ExacqVision Client software in any of the following ways:

  • You can use a local ExacqVision Username and Password
  • You can always use your system login without having to enter a Username or Password. In this case, leave the Username and Password empty on the Add Systems page, select ‘Use Single Sign-On’, and click Apply. A pop-up window will prompt you to enter your Kerberos password, which is the same as your domain password.

Adding ExacqVision users from the directory database

When the ExacqVision server is appropriately configured and connected to your directory server, the Users page and the Enterprise Users page each contain a ‘Query LDAP’ button that allows you to search for users or user groups configured in the directory. You can manage their ExacqVision server permissions and privileges using the ExacqVision Client the same way you would for a local user. On the System Information page, the Username column lists any connected directory users along with their directory origin (whether each user was mapped as an individual user or part of a user group) in parentheses.

<br>

Mac-OS-X-Client-and-Active-Directory-OpenLDAP.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Firefox will not run on Linux-based exacqVision Server

If you cannot run Mozilla Firefox on a new Linux server, remove the .mozilla directory from the Admin account home folder. To do this, complete the following steps:

<br>

  1. Log in to Ubuntu as an admin.
  2. Open a Terminal window (Start > Accessories > Terminal).
  3. Typesudo rm -rf ~/.mozilla.
  4. Enter the password for the admin account.
  5. Run Firefox.

<br>

Firefox-will-not-run-on-Linux-based-exacqVision-Server.pdf