By default, Microsoft’s automatic Windows updates are not enabled on ExacqVision systems.
There are no known ExacqVision compatibility issues with any currently available Windows updates. However, if you decide to apply Windows updates your ExacqVision system, we suggest that you apply only the critical updates. Do not apply optional updates.
NOTE: If your Windows update settings are set to install your updates automatically, there is a risk of missing important video data during the reboot process. We suggest you choose an update method that does not automatically reboot your system such as “Check for Updates but let me choose whether to download and install them” or “Download updates but let me choose whether to install them”. If you choose to automatically install your Windows updates, make sure you setup an Automatic Maintenance window task to install during off peak hours.
The steps described below are legacy instructions and have been superseded. Use the Exacq Kiosk User software to create kiosk user accounts and select whether or not a kiosk user account will automatically login.
Beginning 12/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems which have an eDVR capture board. In addition, starting with exacqVision Server version 22.06 the XDVPI plugin has been removed and systems where the plugin is present will be blocked from upgrading. In order to either extend the SSA or update to 22.06 or higher the board and the XDVPI plugin must be removed.
Beginning 06/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems using the Dahua DHVECxxxx capture board. The board must be removed in order to extend the SSA.
Note: If your exacqVision Utilities DVD is labeled with a software version 5.6.1.43456 or later, use the following procedure. If your DVD is labeled with an earlier version, skip ahead to the second procedure.
Instructions for exacqVision utilities DVD Versions 5.6.1.43456 and later
Linux
Insert the exacqVision Utilities DVD into the optical drive of the server. The disc will auto-launch.
Double-click BoardPrep.
Type the admin password (admin256 is default).
Press 1 to install the driver.
Press Enter to exit.
Open a Terminal window.
To confirm the module loaded, type the command appropriate for your system:
This is an eDVR card. Write down this information and proceed to Step B.
If you still see no results and you are sure this is a hybrid system, please contact technical support.
<br>
Windows
Open Device Manager. If the capture card driver is not installed, the card appears in the device list as Multimedia Controller under Other Devices.
Right-click the Multimedia Controller entry and select Properties.
On the Details tab, select Hardware IDs from the Property drop-down list.
If the device is an exacqVision capture card, the returned Value should appear similar to the following:
PCI\VEN_18A2&DEV_0026&SUBSYS_000018A2&REV_01
The device code for the card in the example above is 18a2:0026, based on the numbers and letters immediate after VEN_ and DEV_. Write down your specific device code and proceed to Step B.
If the card is an eDVR card, the returned Value should appear similar to this:
PCI\VEN_1131&DEV_5402&CC_0480 This is an eDVR card. Write down this information and proceed to Step B.
If you do not see a Value similar to the ones listed above, and you are sure this is a hybrid system, try to find another Multimedia Controller in Device Manager or contact technical support.
<br>
Download the driver
If you have Internet access, you can find the driver in the following location:
Otherwise, you can find the driver on the exacqVision Recovery CD that shipped with your system.
Use the following table to determine which driver to download:
Device Code (from Step A)
Card Type
Installer Type
Linux Filename
Windows Filename
19e5:xxxx
DHVRC8008HB
Dahua
dahua.deb
N/A
19e5:3520
DHVEC8016HB (see note 1)
Dahua
dahua.deb
N/A
TriMedia TM-1300
N/A (see note 2)
eDVR
xdvapi.deb
xdvapi.exe
18a2:0002
VRC6016
SDVR
sdvr.deb
sdvr.exe
18a2:000a
VRC6016C
SDVR
sdvr.deb
sdvr.exe
18a2:002b
VRC6016C
SDVR
sdvr.deb
sdvr.exe
18a2:0020
VRC7016L
SDVR
s7dvr.deb
s7dvr.exe
18a2:0023
VRC7008L
SDVR
s7dvr.deb
s7dvr.exe
18a2:0025
VRC7032
SDVR
s7dvr.deb
s7dvr.exe
18a2:0026
VRC7016LX
SDVR
s7dvr.deb
s7dvr.exe
18a2:002A
7008E
SDVR
s7eDVR.deb
s7eDVR.exe
18a2:002B
7016XE
SDVR
s7eDVR.deb
s7eDVR.exe
18a2:1974
xsDVR6516
SDVR
xsdvr.deb
xsdvr.exe
18a2:19e8
xsDVR6632
SDVR
xsdvr.deb
xsdvr.exe
5851:8008
TDVR8008
tDVR
tdvr.deb
tdvr-Setup.exe
5851:8016
TDVR8016
tDVR
tdvr.deb
tdvr-Setup.exe
5851:8032
TDVR8032
tDVR
tdvr.deb
tdvr-Setup.exe
Note 1: Beginning 06/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems using the Dahua DHVECxxxx capture board. The board must be removed in order to extend the SSA..
Note 2: Beginning 12/14/2021 extension of the SSA “Software Subscription Agreement” will be restricted on systems which have an eDVR capture board. In addition, starting with exacqVision Server version 22.06 the XDVPI plugin has been removed and systems where the plugin is present will be blocked from upgrading. In order to either extend the SSA or update to 22.06 or higher the board and the XDVPI plugin must be removed.
<br>
Install the driver
Linux
Double click on the appropriate driver file found in Step B.
Click Install Package.
If asked for a password, enter admin256.
After the installation is complete, click Close.
Exit the package installer application by clicking the X in the upper-right corner of the window.
<br>
Windows
Run the EXE file found in Step B.
Open Device Manager.
Verify that the board appears as a device without any yellow exclamation marks.
<br>
Note: For eDVR systems, you must run Control Center in Windows, or /usr/local/xdvapi/bin/xdvccl in Linux, to populate the device info in XDVAPI.ini.
If you are recording video to an iSCSI target in Windows, it is important to ensure the iSCSI device is available in the operating system before the ExacqVision Server starts. Please follow the instructions from the Microsoft iSCSI Software Initiator Version 2.x Users Guide:
Note: The following information was written and published by Microsoft Corporation, which is responsible for the accuracy of the information.
<br>
Running automatic start services on iSCSI disks
The disk startup sequence in Windows when using the Microsoft iSCSI software initiator kernel mode driver is different from the startup sequence when using an iSCSI or other HBA. Disks exposed by the Microsoft iSCSI initiator kernel mode driver are available for applications and services much later in the boot process and in some cases might not be available until after the service control manager begins to start automatic start services. The Microsoft iSCSI initiator service includes functionality to synchronize automatic start services and the appearance of iSCSI disk. The iSCSI service can be configured with a list of disk volumes that are required to be present before the start of automatic start services.
In order to install automatic start services on volumes created from iSCSI disks you need to follow the following steps:
Login to all of the targets your machine will be using. Ensure that these are the only targets that are logged in. Be sure that you have also made them persistent logins by using the iscsicli command PersistentLoginTarget or clicking on the appropriate option in the control panel applet.
Configure all volumes on top of the disks using Disk Administrator
Use the iscsicli commands BindPersistentVolumes, AddPersistentVolume, RemovePersistentVolume and ClearPersistentVolumes (or appropriate button in the control panel applet) to allow the iSCSI service to configure the list of persistent volumes
On Windows 2000 only, make the automatic service dependent upon the msiscsi service.
Note: If you have made any services dependent upon the Microsoft iSCSI initiator service, you will need to manually stop the service before upgrading or removing the Microsoft iSCSI Software initiator package.
If you want to print images from the ExacqVision software on an ExacqVision server, you might need to change the default printer. Because Windows is locked down when you log in as a User, you must perform the following steps to configure the default printer:
Log out of the Windows User account.
Log in to the Windows Admin account.
From the Start menu, select Programs, Accessories, and Notepad.
Type the following, where “Printer Name” is the name of the desired default printer (such as “Lexmark 2310”).
From the File menu, select Save As. Change the filename to DefaultPrinter.bat (make sure the extension is not .txt).
Open the Startup directory. In Windows XP, this directory is found in C:\Documents and Settings\User\Start Manu\Programs. In Windows 7, it is found in C:\Users\User\AppData\Roaming\Microsoft\Windows\Start Menu\Programs.
Copy the DefaultPrinter.bat file to the user profile in the Startup subfolder.
Disk I/O (input/output) plays a crucial role in how you experience the exacqVision software. If disks are unable to handle the amount of data being written to them, you could see reliability issues.
To help pinpoint the source of these issues on your server, use the following steps as a guide based on your system operating system.
<br><br>
Linux (Ubuntu)
How to view I/O wait
Ubuntu, and most versions of Linux, come with the ‘top’ command already installed.
Press CTRL+ALT+T to open a Terminal window and enter ‘top’ by typing top and pressing Enter.
Towards the top-left, find the row that shows ‘%Cpu(s)’ and follow this line over to the right. The ‘wa’ statistic here reports the percentage of time the CPU is waiting for disk I/O to finish.
You may exit ‘top’ by pressing ‘q’.
I/O wait is an indicator to look further. This is where tools such as ‘iotop’ can help determine which processes have high I/O percentages.
How to find the causes of high I/O wait times
The ‘iotop’ command does not come pre-installed with Ubuntu, so you will probably need to install it.
When connected to the internet, enter the following commands to install ‘iotop’.
sudo apt-get update sudo apt-get install iotop
You will probably need to run ‘iotop’ with elevated privileges using the sudo command, so enter sudo iotop.
The top left and right sections display the overall read and write throughput.
Below this, ‘iotop’ displays a live updating list of processes and their individual read and write I/O values.
The column you are most concerned with is that of ‘IO’. This column reports the percentage of time the process on that row was performing I/O against its total processing time.
Let’s say it takes approximately 1 second to write 200 MB to disk. You’ve issued a Save command to write 160 MB to file, which took 800ms, then your I/O wait time would be 80%.
Many systems today have multiple cores. Use Terminal again to enter the following command cat /proc/cpuinfo and find the number of Cores. You may need to scroll up a bit to find this.
Calculate 1/# of Cores.
If your wait time percent is regularly near or above this amount, your CPU is spending a lot of time waiting for disks to catch up, and thus slowing your system.
<br><br>
Windows
Monitoring disk I/O with Performance Monitor
Windows packages a tool called Performance Monitor (perfmon.exe) on it’s operating system. Open this application by clicking on the Windows (Start) icon on the toolbar and typing “Performance Monitor,” then click to open it.
from the left-hand navigation panel, expand ‘Monitoring Tools’ and select ‘Performance Monitor.’
The monitor panel will usually be very empty by default, so you will need to add the specific counters you wish to monitor.
Click the green ‘Add’ button from the toolbar above the main panel.
Beneath ‘Available Counters,’ scroll to find ‘PhysicalDisk’ and expand it. The statistics you will be interested in are:
‘% Disk Time’
‘% Idle Time’
‘Current Disk Queue Length’
‘Disk Reads/sec’
‘Disk Writes/sec’
When you highlight each of these, the below panel allows you to select individual drives, ‘All Instances’, or ‘_Total’. Total will sum all activity between multiple instances, whereas selecting ‘All Instances’ adds them all individually to your displayed data. On your NVR you will probably only be concerned with the recording disk(s).
After selecting each counter and the instances below, be sure to click the ‘Add>>’ button below to move it to the ‘Added counters’ panel on the right.
NOTE: If your system is utilizing RAID or you have partitions spanning multiple disks in a JBOD configuration you can also monitor these using statistics found under ‘LogicalDisk,’ which provides statistics for partitions rather than physical disks.
Before moving on, you may also wish to expand ‘Processor’ from the ‘Available counters’ panel and add:
‘% Idle Time’
When you have finished adding all your counters, click the ‘OK’ button.
By default the Performance Monitor displays a graph, but this can be difficult to read with many counters added at once, nor does it display the current values well. From the toolbar, use the ‘Display Type’ icon to cycle through the type options with each click, or use the drop-down arrow beside it to select ‘Report.’
You are no able to monitor the live disk I/O values and processor time.
The figure you will be most concerned with is the ‘% Disk Time.’ You could also choose to display the ‘% Disk Read Time’ and ‘% Disk Write Time,’ but by using ‘% Disk Time, this is the sum of both reading and writing, so the total I/O for that disk.
Many systems today have multiple cores. Press CTRL+SHIFT+Esc to open Windows Task Manager, then click on the ‘Performance’ tab to find the number of cores on your system. This example from a Windows 10 machine shows 6 cores.
Calculate 1/# of Cores.
If your idle time percent is regularly near or above this amount, then your CPU is spending a lot of time waiting for disks to catch up, and thus slowing your system. I/O wait is merely and indicator to look further.
Adding the ‘Available MBytes’ instance from the ‘Memory’ counter in Performance Monitor will show you if a large amount of memory is being consumed while data is waiting to be written to disk. The ‘Current Disk Queue Length’ instance from the ‘PhysicalDisk’ counter will help display how many operations are in the disk queue waiting to be completed.
Finally, you may search under ‘Process’ for ‘IO Data Bytes/sec’ for the ‘exacqd’ instance to display the amount of ‘IO Bytes’ the Exacq application is performing. High processor idle time, high % Disk Time, combined with high memory usage can point to a disk I/O bottleneck on the system.
<br><br>
Factors that can affect I/O
Average I/O performance per disk Higher Read/Write speeds mean more data transactions per second.
RAID Arrays Having several disks in an array increases I/O transactions.
RAID Factor While RAID factors are varied to provide a number of levels to mitigate the possibility of data loss through fault-tolerance, the RAID factor can determine if more read/write transactions are necessary for each operation. For example, all other things being equal, RAID 5 has better I/O performance than RAID 6 due to the additional parity required by RAID 6.
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>
For Windows: Browse to C:\Program Files\exacqVision\WebService\bin\templates.
For Linux: Browse to /usr/local/exacq/webservice/bin/templates.
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
Save the file.
Open or refresh the Web Server page in your web browser.
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
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>
From this Settings menu, select Remote Desktop. Windows (Start) button > Settings > System > Remote Desktop<br><br>
Set ‘Remote Desktop’ to ‘On’.<br><br>
Windows 10
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>
From the Settings menu, select Remote Desktop. Windows (Start) button > Settings > System > Remote Desktop<br><br>
Turn on the toggle for Enable Remote Desktop.<br><br>
Windows 7
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>
From the left-hand panel, select Remote settings.<br><br>
In the ‘System Properties’ window, note the tabs across the top and select the Remote tab.<br><br>
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.
Determine whether the system has Remote Desktop installed. Open the Windows (Start) button. Right-click Computer and choose Properties from the menu.<br><br>
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>
To install Remote Desktop on the system, perform the following:
Download RDPPack.iso and burn this ISO to a CD/DVD.
Insert the disc into the system’s optical disc drive or use an external disc drive connected to USB.
The installer should run automatically. You will be prompted to enter administrator credentials to install RDP then restart the system.
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>
Follow the steps above under Windows 7 to enable Remote Desktop.<br><br>
Making a connection
Click the Windows (Start) button and begin typing to search for Remote Desktop Connection. Click on it to open.<br><br>
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>
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
Log in to any Windows workstation that has already been added to your domain. You must have at least local admin permissions.
Start the Microsoft Management Console (mmc.exe).
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.
Expand Certificates – Current User in the left pane.
Expand Trusted Root Certification Authorities.
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.
Select that Issued To entry, and then right-click All Tasks and select Export.
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
On the actual exacqVision Server, copy your trusted root certificate to the server’s installation directory.
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.
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.
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.
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 .
If your certificate was successfully imported, you will see something similar to “my domain ca cert” and “C,C,C.
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.
The following procedures describe the process for replacing an eDVR board in a Windows-based exacqVision server. If you have an exacqVision server with multiple eDVR boards, complete both procedures; on a single-board system, you can skip directly to the second procedure.
NOTE: You must be logged in to Windows as an Adminsitrator to perform these procedures. If you are logged in as a User (the account used by default for normal operation of the system), select Log Off from the Start menu and click the Log Off button. When the login screen appears, log in as an Administrator. The default password for the Administrator account is “admin256.”
NOTE: It is recommended that you back up your settings before performing these procedures. To do this, run the exacqVision Client, open the Configuration tree, and select the system in which you will replace the eDVR board. Click Export Settings on the System tab, enter a name for the settings file, and click Save. If you need to restore the settings after the procedures, click Import Settings, browse to the settings file, and click Open.
For a system with multiple eDVR boards
From the Start menu, select Run… . Enter services.msc and click OK.
In the Services window, right-click exacqVision Server and select Stop. Wait for the service to shut down. Leave the Services window open.
Start the Control Center application from the Start, Programs, Exacq eDVR Setup menu.
Select the first eDVR board listed under Exacq in the tree on the left side of Control Center. Determine the Device Number for the board as listed on the Info tab.
Repeat the previous step for each listed eDVR board. There should be a board with a Device Number of 1, and any additional boards should be numbered 2, 3, and 4 (up to the total number of eDVR boards installed).
If an installed eDVR board is not listed in the tree, note the device number that is not associated with a board. For example, if you have a two-board system and the only listed board has a device number of 2, the board that will be replaced is device number 1.
If all the installed eDVR boards are correctly listed, determine which board needs to be replaced by selecting each board and selecting the Test tab. The board that doesn’t display video correctly is the board that needs to be replaced. Note the device number and serial number (12 characters beginning with “SR” or “ER”) for that board by viewing the Info tab.
Close Control Center.
If you are not ready to replace the eDVR board and you want to resume video recording, restart the exacqVision Server service. To do this, right-click exacqVision Server in the Services window and select Start. Wait for the service to start.
Close the Services window.
For ALL systems (with a single eDVR board or with multiple eDVR boards)
Obtain the replacement eDVR board from exacq Technologies.
Shut down the exacqVision system.
Disconnect the power cable from the system.
Remove the lid and determine the location of the eDVR board that needs to be replaced.
NOTE: The location of the eDVR boards and the steps required to remove them vary depending on the exacqVision server model. On a 2U or 4U system with multiple boards lined up horizontally, device number 1 is the top board and device number 2 is the bottom board. On a 4U system with multiple boards plugged into the motherboard, device 1 is the board farthest to the left when looking at the back of the system, and each successive board to the right is device number 2, 3, and so on. If you know the serial number of the board from the previous procedure, look for the serial number sticker affixed to the board (12 characters beginning with “SR” or “ER”). Be sure to note how the cables are connected to the board you remove.
Install the replacement eDVR board and connect all the cables in the same way they were connected to the board you removed.
Connect the power cable. If the system does not start automatically, start the system manually. The system will log in to Windows as a User.
Log out of the User account and log in to the Administrator account, as described in the note at the beginning of this article.
From the Start menu, select Run… . Enter services.msc and click OK.
In the Services window, right-click exacqVision Server and select Stop. Wait for the service to shut down. Leave the Services window open.
Start the Control Center application from the Start, Programs, Exacq eDVR Setup menu.
On a single-board system, select the eDVR board under Exacq in the tree on the left side of Control Center. On the Info tab, change the Device Number to 1. Click Save.
On a multiple-board system, determine which listed eDVR board is the replacement by selecting each board and viewing the Device Number. The replacement board should be the highest-numbered device and should not match the device number for the board you removed. For example, on a two-board system, the replacement board should be shown as device number 3. You must change the device number of the replacement board to match the device number of the board you replaced, as determined in the previous procedure. Click Save.
NOTE: It is very important that the replacement eDVR board’s device number matches the device number of the board you removed. Failure to assign the correct device number to the replacement board will result in incorrect functionality.
Select the Test tab to verify that the new eDVR board is correctly displaying video from the connected cameras.
Close Control Center.
In the Services window, right-click exacqVision Server and select Start. Wait for the service to start.
Close the Services window.
Log out of the Administrator account and log back in to Windows as a User for the normal operation of the system.
NOTE: If these procedures were not followed precisely, the names of the cameras associated with the replaced eDVR board might appear with default names (Input 1, Input 2, and so on). If so, restore the settings that you backed up before starting the replacement process.
Return the eDVR board that you removed to Exacq Technologies using the packaging in which the replacement board was shipped. Print the RMA number on the outside of the package and send it to the following address: Exacq Technologies, Inc. 11955 Exit Five Parkway, Building 3 Fishers, IN 46037 USA
<br><br>