Custom view users cannot be removed from a view as the checkbox for their user name will be dimmed and cannot be unchecked to deselect the user.
Product
C2C
Cloudvue Gateway
Solution
The user who initially creates a custom view becomes the owner of the view i.e., “Custom View owner” and cannot be removed from the view as the checkbox for their username will be dimmed and cannot be unchecked to deselect the user.
Currently there is no method through Cloudvue or Cloudvue Manager to switch this ownership of a view to another user.
In the event a customer runs into this issue you will need to create an AES ticket requesting engineering run a script deleting the current owner of the view(s) and assigning a new owner.
Integrated Dell Remote Access Controller (iDRAC) is a proprietary technology that allows IT administrators to remotely manage and monitor Dell-built servers. This includes software and hardware components.
The Exacq X-Series NVRs include iDRAC micro ports on the front of the system and iDRAC network interfaces on the back. The location of these is noted on the X-Series Quick Start Guide.
<br>
Out of the Box
iDRAC ports are not enabled out of the box. To enable either, or both interfaces, you must access the Lifecycle Control Center on the system.
Enabling iDRAC Ports
During boot up of the system, watch for the boot options to appear on screen.<br><br>
When shown, press the F10 key to boot into the Lifecycle Control Center. <br><br>
The Lifecycle Controller automatically begins a network configuration wizard if it has not been configured before. You may select the Back button to exit the wizard.<br><br>
From the Lifecycle Controller Home screen, navigate to System Setup > Advanced Hardware Configuration. <br><br>
Select iDRAC Settings. Continue to Step 6 to enable iDRAC Direct on the iDRAC micro port. Skip to Step 7 to enable iDRAC networking.<br><br>
To enable the iDRAC micro port, select Media and USB Port Settings. <br>
Beneath USB Management Port, locate the iDRAC Direct: USB Configuration XML setting.
The default setting is ‘Enabled while server has default credential settings only.’ However, for the security of your system, these credentials are changed before shipping from the factory.
Change the above-mentioned setting to ‘Enabled‘.
Select the Back button.<br><br>
To enable the iDRAC network port on the rear of the system, select Network.
NOTE: A VLAN is recommended as a best security practice when iDRAC is in Dedicated or Shared LOM mode, to isolate network access to iDRAC’s management interfaces. Technologies such as VLANs and firewalls help ensure that only authorized users can access network resources.<br><br>
Beneath Network Settings, change the Enabled NIC setting to ‘Enabled‘.
Leave the NIC Selection set to ‘Dedicated‘.
Scroll down to the IPv4 Settings section. The default settings are as follows:
Enable IPv4: Enabled
Enable DHCP: Enabled
Static IP Address: 0.0.0.0
Static Gateway: 0.0.0.0
Static Subnet Mask: 0.0.0.0
Use DHCP to obtain DNS server addresses: Disabled
Static Preferred DNS Server: 0.0.0.0
If you plan to connect this interface to a network with a DHCP server, you may leave the settings as they are.
If you wish to use a static IP address for the iDRAC interface, change the Enable DHCP setting to ‘Disabled‘ and enter the proper Static IP address settings in the fields below.
Select the Back button when done.
Press the Finish button to save your changes and return to the System Setup menu.<br><br>
Press Finish again to return to the Lifecycle Controller main menu.<br><br>
Leave the Lifecycle Control Center and boot to the operating system by selecting the Exit option in the corner of the screen.
<br>
Accessing the iDRAC9 Dashboard
The iDRAC9 Dashboard is accessible using any modern web browser, but there are various methods available to reach it: Local, Network, and USB (iDRAC Direct). <br>
Local Browser Access
Accessing the iDRAC9 Dashboard locally requires a keyboard, mouse, and monitor connected to the system.
Log into the system’s operating system (Windows or Linux).<br><br>
Open a web browser.<br><br>
In the browser address bar, enter: https://169.254.1.1<br><br>
Use the browser’s advanced settings to continue past the warning message. This message appears because the SSL certificate is self-signed.<br><br>
Log into iDRAC using the proper credentials.
<br>
Network Access
iDRAC network interfaces support RJ45 jacks, with 1G BASE-T Ethernet Cat5/6 cables.
The Lifecycle Control Center provides the ability to set the iDRAC network interface to DHCP or static IP address.
If set to a static IP address, a site administrator should be able to provide the configured address.
If configured for DHCP, but a DHCP server is not available, or has no available addresses to offer, this interface should fall back to 192.168.0.120. Otherwise, you may need to determine what address the DHCP server assigned to the system.
Whether using a static or dynamically allocated IP address, you will enter this address into the browser’s address bar.
Example: https://172.10.10.4
<br>
USB Access (iDRAC Direct)
iDRAC Direct allows you to utilize the front-facing iDRAC micro port to connect directly to the system over USB, say from a laptop, which makes ad hoc management in a server room/stack easily accessible.
iDRAC micro ports couple with a USB 2.0 Micro-A or Micro-B connector. You will need a cable with either of these interfaces to connect between the X-Series system and your laptop/workstation. Cable length should not exceed 3ft (0.91m). Cable quality could affect performance. The iDRAC micro port is a Micro-A type port, which will accept either Micro-A or Micro-B connectors, but will not accept USB 3.0/SS Micro-B.
Before beginning, you MUST disable all other network or wireless interfaces on the laptop/workstation you wish to connect from.<br><br>
Make sure the iDRAC micro port is enabled, see Step 6 of Enabling iDRAC Ports above.<br><br>
Turn the flat side of the USB micro connector to the right, so that the beveled side of the USB micro connector faces left, then insert the connector into the iDRAC micro port.<br><br>
Wait a few moments and the laptop/workstation should detect a new virtual network interface.<br> This can be seen using the ipconfig command on Windows, or ifconfig command on Ubuntu/Linux.<br> The IP assigned to this interface should be 169.254.0.4.<br><br>
Open a web browser on the laptop/workstation. In the browser address bar, enter the IP of the iDRAC micro port: https://169.254.0.3<br><br>
Log into the iDRAC Dashboard with the proper credentials.
<br>
Logging into the iDRAC9 Dashboard
When logging into the iDRAC9 Dashboard, use the following credentials
Username: root
Password: admin256
Consider changing your iDRAC Dashboard password using the steps below.
<br>
Changing the iDRAC credentials
Most system users will probably only use the default root user account and factory set password. However, up to 16 local users may be configured in iDRAC with specific access permissions.
If you are already connected to the iDRAC9 Dashboard, you may do this using the following steps:
Select the iDRAC Settings menu.<br><br>
Select Users from the menu drop-down, or from the tabs on the iDRAC Settings page. <br><br>
Select Local Users. <br><br>
Edit an existing account or add a new user account.
If you are not connected to the iDRAC9 Dashboard, you will need physical access to the system.
During boot up of the system, watch for the boot options to appear on screen.<br><br>
When shown, press the F10 key to boot into the Lifecycle Control Center. <br><br>
The Lifecycle Control Center automatically begins a network configuration wizard if it has not been configured before. You may select the Back button to exit the wizard.<br><br>
From the Lifecycle Controller Home screen, navigate to System Setup > Advanced Hardware Configuration. <br><br>
Select iDRAC Settings. <br><br>
Scroll down to find and select User Configuration. <br><br>
Select the text field beside Change Password to enter a new password. <br><br>
When done, select the Back button.<br><br>
Click the Finish button to save your changes.
<br>
iDRAC9 Dashboard Basics
The iDRAC9 Dashboard provides a quick overview of the system. Describing all aspects and controls is outside the scope of this document. The items you should pay the most attention to are your system and drive health.
The Dashboard home page shows a high-level overview of System Health and Drive Health.
Clicking on Details for either of these will bring you to the corresponding pages. You may also reach these pages by selecting System or Storage from the top menu bar.
The System > Overview page displays the status of many hardware components, such as memory, CPU, power supplies, and cooling (system fans). Selecting any of these will provide greater detail on each.
The Storage > Overview page lists the number of physical disks, virtual disks, and graphics of drive status. 2U systems will also display a graphic of the system’s front panel to help identify the drive bays.
Each Virtual Disk is comprised of multiple Physical Disks. These are listed on the corresponding Virtual Disks and Physical Disks pages.
<br>
Virtual Console
iDRAC9 provides a Virtual Console feature which provides a desktop environment as if you were sitting in front of the system. This negates the need to also configure RDP or VNC to configure the system using a GUI.
IMPORTANT: Do not use the Virtual Console for client monitoring of cameras. This method may be used to configure exacqVision software only: add and configure cameras, managing licensing, check system statuses and logs, etc. For regular camera monitoring, install the exacqVision Client on a client workstation suitable for this purpose. See system hardware requirements.
NOTE: Virtual Console performs better when connected via the iDRAC network interface than when connected using iDRAC Direct using the micro USB port.
Enabling the Virtual Console
Virtual Console is disabled by default. Once logged into the iDRAC9 Dashboard, you may enable this feature for use.
From the iDRAC9 Dashboard, locate the Virtual Console panel. The message in this panel indicates the feature is currently disabled for use. <br><br>
Click on the Settings option above the empty panel.<br><br>
From the Virtual Console settings page, change the Enabled setting from ‘Disabled’ to ‘Enabled’, then press the Apply button below. <br><br>
Return to the Dashboard and note that the Virtual Console panel will display an image from the system based on its current state.<br><br>
Select the inset image or press the Start the Virtual Console bar below to open a Virtual Console session.
<br>
Virtual Console Basics
Virtual Console will open a session in a new browser window. Note that the frame rate of the console display is included in the window’s title bar. The console provides some of the following features from the menu buttons. <br><br>
Menu Item
Description
Boot
Chooses what the system will boot to on the next boot up. Options include the Lifecycle Controller, as well as physical or virtual media.
Power
Allows the user to remotely power cycle or shutdown the system.
Chat
Provides a chat window for use when more than one person is using the machine’s Virtual Console.
Keyboard
Displays a virtual keyboard. May be useful when attempting to enter multi-key commands such as CTRL+ALT+DEL.
Screen Capture
Allows the user to save a screen capture PNG image to their local machine.
Refresh
Refreshes the console window.
Fullscreen
Displays the Virtual Console in fullscreen mode. Press ESC to exit fullscreen mode.
Virtual Media
Virtual media allows the managed server to access media devices on the management station or ISO CD/DVD images on a network share as if they were devices on the managed server.
Select Connect Virtual Media to begin, select your chosen media. Use Disconnect to remove that media from the machine’s console connection.
Disconnect Viewer
Closes the console session and window.
Console Controls
Provides settings for viewing, including a virtual clipboard for copying text between the managed server and the management workstation.
The X-Series Network Video Recorder from Exacq provides high performance hardware with exacqVision surveillance video management software. All X-Series systems provide hot-swappable hard drives, dual, hot-swappable power supplies and mirrored operating system drives independent of video storage for continuous uptime. This Quick Start Video will introduce you to the X-Series systems and guide you through initial setup.
exacqVision Client connection status for camera shows “unable to create video stream” status.
Notes
Often this is a firmware compatibility issue. There are some cases that this has been resolved by factory defaulting the camera and/or removing and recreating illustra3pi.xml file in server folder.
DebugView is a tool that can be used to collect more data from PS files in cases where we are missing data from streams or exhibiting issues with exported files.
Once you have exported the PS file from a server you can download the DebugView application and open the program. With Debug View opened, perform the following steps:
Run CMD on a Windows machine using Run as Administrator<br><br>
Change your working directory to the directory where the PS file is located, using the ‘cd’ command. Example: In this example the file is located on the Desktop cd C:\Users\username\Desktop<br><br>
Run the file by entering the file name, and add the ‘-V’ parameter to the end. If located in a different directory, enter the file path. Example: In this example the file name is ‘3505-001A0280.ps’ 3505-001A0280.ps -V or C:\Users\username\Desktop\3505-001A0280.ps -V<br><br>
When the Exacq ePlayer opens, press the play button.<br><br>
DebugView will log activity during playback. Save the file as soon as the clip has finished playback to avoid logging your mouse and keyboard activity.
In this Example- We have an issue where the data that was recorded is not viewable when searching, exporting the video. This tells us that the cameras were getting some of the stream information but not all of the stream information that is vital to play back the video that was recorded. This might suggest that the camera was in a bad state, low power mode or there was something taking place.
As part of the exacqVision 24.03 software release, we are announcing the deprecation of specific installers that were previously part of the collection of software downloads available on the Exacq web site, https://exacq.com.
What installers are being retired?
On both Windows and Ubuntu – the 32-bit installers, also known as “x86” installers, of server, client, and web service will no longer be made available for new releases. The Enterprise Manager 32-bit installer had been deprecated from the 21.12 release. In addition, Illustra 610 and 825 (Edge), and ARM Debian (M-Series) installers will be retired as well.
Why is Exacq taking this step?
This change helps address cyber security/robustness concerns by removing support for those installations that are potentially deployed on operating systems no longer fully supported by the vendor. Additionally, retiring support for older/obsolete technology helps Exacq to streamline engineering resources to focus their efforts on faster delivery of customer outcomes that are needed now and in the future.
What if I have been using 32-bit installers for exacqVision all the time? How do I update to the 24.03 release?
If a customer is currently using 32-bit installers, they would have to move to the 64-bit installers – provided the hardware and the operating system are 64-bit enabled. 32-bit and 64-bit installers cannot co-exist. To move to the 64-bit installation, the 32-bit installation should be uninstalled.
So as to not lose the current configuration, it is recommended that the current configuration be backed up – then restored after the 64-bit installation has been deployed. Please refer to this user guide section for understanding how to do a backup and restore of the exacqVision Server configuration.
If Enterprise Manager is deployed, you may refer to this video to understand how to backup and restore configurations across multiple servers at once.
How do I know if the hardware and operating system on my NVR is 64-bit capable?
It will depend on how old the NVR is.
If the NVR was built by Exacq and is a Windows machine – Any system that shipped on or after May 2013 is capable of running a 64-bit installer.
If the NVR was built by Exacq and is a Ubuntu machine – Any system that shipped on or after August 2017 is capable of running a 64-bit installer.
If the NVR was not built by Exacq, please contact your IT department or the manufacturer of the NVR to assess if it is capable of running a 64-bit installer. As a reference point, Windows started 64-bit support from Windows Vista, with mainstream support adopted in Windows 7, and Ubuntu from Ubuntu 16.04. So it is more than likely that the NVR in question is 64-bit capable. With that said, please double-check with relevant departments and resources to be sure.
NOTE: Operating system vendors, whether or not they support 64-bit, have set time tables for end-of-life (EOL). It is not recommended to use a system for which critical cyber security patches are no longer available. For example, Microsoft no longer supports Windows 7 or 8. Ubuntu does not support systems older than 14.04 today – and they will continue to obsolete older versions as they release new ones.
I can see my NVR is not capable of running a 64-bit installer. What is the recommended course of action?
It is likely that you are running an old NVR that is probably not in compliance with the cyber security standards of your IT department. In addition, you will not benefit from new features, integrations, cyber security patches, and bug fixes that make up the 24.03 and future exacqVision releases. Our recommendation is that you upgrade to newer hardware and operating system for your NVR. Please reach out to your local exacqVision dealer or call Exacq Inside Sales for better understanding of your options.
The exacqReplay feature is a fast and convienient way to view recorded video or simply isolate a live camera for viewing. This short video shows how to use exacqReplay.
Enterprise Manager may fail to send email notifications after update to 23.09.9.0.
ExacqVision support has identified an issue with failing email notifications after updating Enterprise Manager from a previous version to version 23.09.9.0 and up. This occurs when checking “Anonymous” as the send user, or additional configuration required for Exchange servers has not been completed.
NOTE: Email notifications have been confirmed to succeed using same SMTP configuration on version 23.06.2.0 but fails when update to 23.09.9.0 is completed.
Product
exacqVision Enterprise Manager Version 23.09.9.0
Steps to Reproduce
Update Enterprise Manager to version 23.09.9.0 from a previous version
Expected Results
Email notifications should continue to succeed with existing configuration.
Actual Results
Email notifications may fail with all or one of the following log errors: Failed email verification: SMTP AUTH extension not supported by server.
Failed email verification: (550, b'5.7.60 SMTP; Client does not have permissions to send as this sender')
Failed email verification: STARTTLS extension not supported by server.
disable “anonymous users” as send from address in Enterprise Manager and replace with an authorized SMTP user.
2. Turn on Basic Authentication method in Exchange/ SMTP server if option is available.
3. Make sure the user account sending notifications from Enterprise Manager has SMTP Authentication turned on in their exchange profile, and also that the “Send From” address used in Enterprise Manager was added to the exchange user as an email alias.
<br><br>
<br><br>
<br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
