Tag: Operating Systems

Categories
Knowledge Support Support exacqVision Hardware

exacqVision – Resetting the Operating System Password

Title

exacqVision – Resetting the Operating System Password

Description 

How to reset the OS password on an ExacqVision Server

Product 

exacqVision Server

Solution

Either a full re-image or an on-board system recovery will need to be performed to reset the operating system password. 
Knowledge Base Article #935 “System Recovery using on-board recovery partition”

Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories Products

ExacqVision stance on updating the Windows Operating System

ExacqVision has tested and recommends the Windows 10 LTSB and LTSC releases from Microsoft. These are the only two releases we recommend and support.

Categories
Knowledge Support Support exacqVision Server Categories Products

What file systems does ExacqVision support?

File systems supported by ExacqVision are as follows:

<br>

Windows:

  • NTFS

Ubuntu/Linux:

  • ext4 (recommended)
  • ext3 (only used for older 8.04 systems)

<br>

Using file systems other than those listed may result in data loss, inability to recognize storage volumes, incompatibility when updating to future software versions.

<br>

Categories
User Guides Documentation exacqVision Mobile Categories Products

What Operating Systems are supported for Exacq Mobile 3?

Exacq Mobile 3 is supported on the following platforms:

  • Android 6.0 or newer
  • iOS 12.0 or newer

<br>

Categories
Knowledge Support Documentation Support exacqVision Client Products

What Operating Systems does ExacqVision software support?

The Exacq.com web site provides a list of supported operating systems for each software product under System Requirements. This is the best location for current OS information.

<br>
ExacqVision Server
ExacqVision Client
ExacqVision Webserver

<br>

Categories
Knowledge Support Support exacqVision Client Categories Products

Installing Third-Party Software Fails in Windows Embedded (Installer Service Error 1719)

Some third-party programs cannot be installed in Windows Embedded because the Windows Installer service fails to start (error 1719). This usually occurs with programs that change the registry in conjunction with other third-party software, such as anti-virus programs.


As a workaround, you can start the service manually, install the program, and then stop the service.


Locating and Starting the Service

  1. If logged in as a user, log out and then log in as an administrator. To do this, click Start, log off, select admin, and type the password.
  2. If exacqVision Client automatically opens, close it.
  3. Click Start, type services.msc in the Search bar, and press Enter. This will launch a new window with a list of services.
  4. Scroll down the list and locate the Windows Installer service.
  5. Make sure that the Startup Type is Manual. If so, right-click it and select Start.

    6. NOTE: If it is not Manual, right-click the service and select Properties. Select Manual from the drop-down menu. Select Start and then OK to start the service.
  6. Leave the Services window open.

Run the Third-Party Software Installer and Stop the Service

  1. Follow the instructions provided by the third-party software manufacturer to run the installer.
  2. When finished, restart the system if prompted by the installer or Windows.
  3. Stop the Windows Installer service if it hasn’t been stopped automatically. In the Services window, right-click the Windows Installer service and select Stop. (If you restarted the system, click Start, type services.msc in the Search bar, and press Enter to open the Services window.) Close the Services window when finished.
  4. If you restarted the system, log in as an administrator.
  5. Open the newly installed software and verify that it operates as expected.
  6. If you cannot use the newly installed third-party software, contact the manufacturer for support.
Installing-Third-Party-Software-Fails-in-Windows-Embedded-Installer-Service-Error-1719.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Best Practices When Upgrading Hard Drives on exacqVision Servers

The following considerations are for 32-bit Windows-based A-Series systems without a RAID controller:

  • Desktop and 2U A-Series systems do not have a separate physical drive for the operating system. This means that we cannot load Windows on anything larger than 2.2TB. By default, Windows 7 loads with an MBR partition table, which has a maximum addressable space of 2.2TB.
  • UEFI is not supported for booting with 32-bit versions of Windows.
  • The operating system needs its own partition (30-60GB) to use the rest of the drive as storage. If the drive containing the operating system is replaced, you will need to back up your settings and other important information, so plan accordingly. 
  • Although it is possible to use a storage drive that is larger than 2.2TB with GUID Partition table (GPT), we do not support mixed-capacity systems.
  • A BIOS upgrade might be required to detect >2TB drives for older systems.

Bottom line: 2TB drives are the maximum supported upgrade for 32-bit Windows-based Desktop and 2U A-Series systems.

<br>

The following considerations are for 32-bit Windows-based A-Series and Z-Series systems with a RAID Controller:

  • 4U A-Series systems (JBOD or RAID) use a separate boot partition made by the RAID Controller. Windows detects as a separate drive, so MBR may be used and the operating system may be installed here. If the drive containing the operating system is replaced, you will need to back up your settings and other important information, so plan accordingly.
  • All Z-Series systems use a separate physical drive for the operating system. We use this separate drive exclusively to install the operating system. This drive should not have to be changed when upgrading the storage drives.
  • With JBOD and RAID arrays larger than 2.2TB, GPT must be used to see the entirety of the drive.
  • Although it is possible to add larger drives to an existing RAID array, the controller will base the capacity on the drive with the lowest capacity. Even if all drives are replaced with larger capacity drives, the controller will not automatically adjust to the larger size. You will need to destroy and re-create the RAID array, so plan accordingly.
  • Also, it is possible to mix capacities with JBOD arrays. However, JBOD arrays are not fault-tolerant, and the existing data on the drive will be lost, so plan accordingly. Of more importance, we do not support mixed-capacity systems.
  • A BIOS upgrade and/or controller firmware update might be required to detect >2TB drives for older systems.

Bottom line: 6TB drives are the maximum supported upgrade for 32-bit Windows-based 4U-Series and all Z-Series systems.

<br>

The following considerations are for 64-bit Windows-based A-Series and Z-Series systems:

  • We use UEFI partitions and GPT with 64-bit Windows-based systems. This eliminates the 2.2TB limit of MBR partitioning on the operating system drive.
  • However, if the drive containing the operating system is replaced, you will need to back up your settings and other important information, so plan accordingly.
  • Although it is possible to add larger drives to an existing RAID array, the controller will base the capacity on the drive with the lowest capacity. Even if all drives are replaced with larger capacity drives, the controller will not automatically adjust to the larger size. You will need to destroy and re-create the RAID array, so plan accordingly.
  • Also, it is possible to mix capacities with JBOD arrays or single drive systems. However, JBOD arrays are not fault-tolerant, and the existing data on the drive will be lost, so plan accordingly. Of more importance, we do not support mixed capacity systems.

Bottom line: 6TB drives are the maximum supported upgrade for all 64-bit Windows-based systems.

<br>

The following considerations are for Linux-based LC, EL, ELS, ELX, ELP, A-Series, and Z-Series systems:

  • All Linux systems use a separate physical drive for the operating system (except for LC, as explained below).
  • We use either ext3 or ext4 file systems (depending upon the Linux version). In either case, we use a maximum single drive size of 16TB. For systems that have more (RAID systems), the drives must be split up into smaller, equal partitions. Using the diskprep.sh script will achieve this split automatically.
  • Although it is possible to add larger drives to an existing RAID array, the controller will base the capacity on the drive with the lowest capacity. Even if all drives are replaced with larger capacity drives, the controller will not automatically adjust to the larger size. You will need to destroy and re-create the RAID array, so plan accordingly.
  • Also, it is possible to mix capacities with JBOD arrays or single drive systems. However, JBOD arrays and single drive systems are not fault-tolerant, and the existing data on the drive will be lost, so plan accordingly. Of more importance, we do not support mixed capacity systems.
  • LC systems: LC systems do not have a separate boot drive. Before you upgrade the drive, back up the configuration and any other important information. Additionally, the data on the drive will be lost, so plan accordingly. The LC recovery image accounts for the single-drive setup, but it should not be used with other types of systems. LC also uses a different drive model than the other models.
  • A BIOS upgrade might be required to detect >2TB drives for older systems.

Bottom line: 6TB drives are the maximum supported upgrade for all Linux systems if all drives are replaced at the same capacity.

<br>

A note about drive speed:

  • Based on the age of the system, either the RAID controller or the SATA port on the motherboard may only support hard drives at 3 GB/s (SATA II). While this does not limit the motherboard from potentially detecting the larger drive, it will reduce its performance as new drives purchased from exacqVision will be 6 Gb/s (SATA III) drives.
  • Some motherboards do not have SATA III connectors, some only have two to four. Older RAID controllers only support SATA II speeds on drives.
  • For assistance on determining which motherboard you have and which connector to use, please contact Technical Support with your system’s serial number (number beginning with ER).

<br>

Best-Practices-When-Upgrading-Hard-Drives-on-exacqVision-Servers.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Best Practices when Upgrading an exacqVision Server from Windows XP to Windows 7

DISCLAIMER: Any user attempting to upgrade an exacqVision system using this procedure assumes all risk of data loss and hardware issues, and must troubleshoot all related issues without the assistance of Exacq Technologies.

<br>

Section 1: Pre-requisites

  • USB drive, at least 4GB (preferably new).
  • A valid copy of Windows 7 Pro 32-bit and license.
  • Motherboard drivers downloaded from the manufacturer (BIOS, LAN, INF, Audio, AMT, and ME). You can reference the exacqVision Knowledge Base on how to determine which motherboard you have.
  • Capture board drivers, SysPrep, and exacqVision software. Download the newest version of capture board drivers and exacqVision client available at exacq.com. If your exacqVision license is expired, use the version of exacqVision software and SysPrep included with the system; you can find them on the Windows Utilities Disc that came with the server.
  • Determine whether you have a RAID Controller. If so, download its drivers and software from the manufacturer’s web site. Be sure to obtain the Windows 7 32-bit drivers.

NOTE: You might lose the video data on the disk where the operating system is located, so plan accordingly. The only case in which you should not lose any video data is with a RAID system not using JBOD.

<br>

Section 2: System Preparation

  1. Use exacqVision Client to export both the existing system settings and the license from the exacqVision server. These options are available by opening the Config (Setup) page and then the System page for the server.
  2. Copy the settings and license information to the USB Drive.
  3. It is suggested that you run the BIOS upgrade at this point. Use the instructions from the manufacturer’s web site.

<br>

Section 3: Operating System Installation

  1. If you have a RAID controller, you must load its drivers before you can see the partitions associated with those drives.
  2. Use a separate partition 30GB or larger for the operating system. This might require you to format the drive that currently contains the operating system partition, which would destroy the data it contains.

<br>

Section 4: Post-Installation Considerations

  1. Install packages in the following order:
  2. Windows updates (install only up to Internet Explorer 10); 
  3. motherboard drivers; 
  4. RAID controller software; 
  5. capture board drivers; 
  6. SysPrep; 
  7. exacqVision software.
  8. Reboot the system after each step or as prompted.
  9. Import your license and original settings. Please note that some new features (such as hardware monitoring) might still not be available.
  10. If your capture boards appear to have swapped order, see https://exacq.com/kb/?crc=2347 for information on changing their order.

<br>

Best-Practices-when-Upgrading-an-exacqVision-Server-from-Windows-XP-to-Windows-7-1.pdf
Categories
Knowledge Support Documentation Support exacqVision Hardware Products

exacqVision Windows XP Support

Microsoft has informed consumers that Windows XP is no longer supported as of April 8, 2014. This means that Microsoft no longer supplies security updates for Windows XP. Note the following information about how this affects exacqVision products.


Can I upgrade from Windows XP to Windows 7 on my Exacq-built exacqVision system?

Any system built by Exacq with Windows XP installed contains hardware that is more than three years old. This means that much of the hardware does not have proper drivers for use with Windows 7. Therefore, it is not recommended that you upgrade those systems from Windows XP. Exacq explicitly will not support such upgraded systems; if you try to perform the upgrade on your own, you will be responsible for ensuring that the operating system and drivers are properly installed and running on the system.


Will Exacq software still continue to function correctly if I do not upgrade the operating system?

exacqVision features will continue to function as they do currently. However, it is possible that some new features introduced may not be compatible with Windows XP.

Categories
Knowledge Support Documentation Support Products exacqVision Hardware

Enabling iSCSI Support on exacqVision Systems with Windows Embedded

Early versions of exacqVision systems with the Windows Embedded operating system did not have support for iSCSI. These systems were manufactured in in January and early February 2014.


To determine whether a system supports iSCSI, complete the following steps:

  1. Open the Start menu.
  2. Right-click Computer.
  3. Select Manage from the pop-up menu.
  4. Double-click Services and Applications.
  5. Double-click Services.
  6. If Microsoft iSCSI Initiator Service is not running, start it.
  7. Click Device Manager.
  8. Expand the Storage Controllers node if necessary.
  9. If you do not see Unknown Device, your system supports iSCSI.
  1. If you do see Unknown Device, right-click it, select Properties, select Details, and select Hardware IDs. If the value is ROOT\ISCSIPRT, your system does not support iSCSI.

To enable iSCSI support on the system, complete the following steps:

  1. Download iSCSIPack.zip from https://exacq.com/files and unzip it to a flash drive or directly to the exacqVision system.
  2. On the exacqVision system, navigate to the directory containing the unzipped installation files.
  3. Double-click the install.bat file.
  4. The installer prompts for administrator rights, installs the files, and restarts the system.
Enabling-iSCSI-Support-on-exacqVision-Systems-with-Windows-Embedded.pdf