Stratusphere Release Notes v6.6.0 (March 14, 2022)

What’s New?

  • Oracle Linux 8: Stratusphere 6.6.0 appliances now use the Oracle Linux 8 Operating System. This operating system replaces the CentOS 8 which is now EOL. Red Hat CentOS 8 had support until 2028, but Red Hat decided to sunset CentOS 8 by the end of 2021 and switch it to CentOS Stream. Thus, Liquidware Stratusphere appliances now run Oracle Linux 8, which is based on Red Hat CentOS distribution. Oracle Linux 8 was chosen because it has wide acceptance across various hypervisor and cloud platforms as well has universal acceptance within the US Federal Government agencies due to its Security Technical Implementation Guides (STIGs). Liquidware supports in-place upgrade only from 6.5.1-2 to 6.6.0. All earlier versions require migrating the appliances from the old version to the new appliance.

    Note: See the Upgrading section below on how to install it or migrate to it depending on which version you currently have installed.

  • Machine Location: Liquidware added a machine location feature to the CID Key. It is supported on all versions of Windows and Linux. Mac OS will be supported soon as well. The CID Key uses Machine Location services on the machine it is installed on to get the latitude and longitude coordinates of the machine. These are then converted in City, State/Province, Country, and Continent within the Stratusphere Database. This feature must be enabled by the end user, and on doing so, a location database is installed on the Stratusphere Database appliance that requires about 5 GB of space. This data is now available under the Summary | Location | Country, State, City Inspector View with the Advanced > Inspectors > Machines tab and the Advanced > Inspectors > Users tab
  • Machine Local Accounts: Liquidware added a feature to collect information on local accounts on machines. It collects the name of the accounts, whether they have administrator privileges, their statuses regarding locked/unlocked/active/etc. and the last time the account was logged into. This information is available under the Advanced > Inspectors > Inventory tab's Machines | Local User Accounts Inspector view.
  • Microsoft Windows 11 Upgrade Compatibility: Liquidware added a new feature that collects information related to Microsoft Windows 11 Compatibility check that determines whether that machine meets all the criteria to be considered fully supported for Windows 11. This information is available under Advanced > Inspectors > Inventory tab's Machines | Windows Compatibility Inspector View.
  • Metric: User Input Delay: Liquidware added a new metric the collects the User Input Delay for each process as well as on the machine level to detect lag on a machine. User Input Delay is defined as the delay between when an input (keyboard or mouse) was entered into the operating system queue and when it was provided to the application. The longer the delay, the worse the user experience. This metric is available under Advanced > Inspectors > Applications and Process Names tabs in the Application | Input Delay Inspector view.
  • CID Key Supports MacOS Monterey, Windows 11, and Windows Server 2022: Liquidware updated the CID Key to support MacOS Monterey, Windows 11, and Windows Server 2022.

Enhancements

Advanced > Dashboards

  • Sankey Diagrams: Enhanced data visualization by adding a new animated Sankey Diagram widget which displays multi-level data in a beautiful looking widget. Examples of multi-level data include Machines > Users > Processes > Destination IPs or Application Name > Process Name > Version > Destination IP.
  • Access to Dashboards: Liquidware enhanced security by adding a check on whether a user is part of any group that has access to dashboard(s) before displaying the dashboard(s) to a user. If the user is not part of any user group that has been given access to the dashboard by the creator of the dashboard, then the user will not be able to view that dashboard. The user must be part of the user group that is assigned to the dashboard. For the default dashboards, too, the user must belong a user group that is assigned to the dashboard such as “dash_admin” or “dash_user” to get access to the default dashboards.

Advanced > SpotChecks

  • Basis Search: Liquidware enhanced useability by adding an option to search the primary Basis available within a SpotCheck. This enhancement allows end users to search for data based on a particular user, or machine or application/process if they are part of the SpotCheck.
  • Easy Answers: Liquidware enhanced useability of SpotChecks by providing answers or guidance on what to do if a metric is not within acceptable thresholds, along with a brief explanation.

Advanced > Inspectors

  • Liquidware updated the default row limit to 25 rows, down from 100 rows as the original default, to provide faster performance.
  • Liquidware enhanced the Go button to pull fresh data and not use any cached data by detecting a long press on the Go button. When pressed for a longer duration, the Go button sets aside cached data and pulls in up-to-the-minute data from the database. This database pull does NOT update the cache.
  • Liquidware enhanced deeper visibility by adding the MAC address of a Network Interface Card (NIC) as a Basis within the Advanced > Inspectors > User ID and Machines tabs.

Web UI

  • UX Profile: Liquidware now uses Summarized, roll-up table for UX Profile recalculations. It was using Detail data for this that could take a long time for calculations. So, to speed it up, it now uses the Summarized, roll-up tables to quickly calculate averages and standard deviations for each individual metric within UX Profile, which can then be used to update the UX Profile for better rating of the end user experience.
  • VM Directories: Liquidware added an EXCLUDE VMS field to exclude some type of virtual machines that meet a case insensitive naming pattern such as “cp-parent*”. This exclusion list takes precedence over any inclusion list based on naming pattern.
  • Liquidware added the API Builder option to the product switching drop-down list at the top right of the page to easily switch to the API Builder.

CID Key

  • Liquidware added a data sanity check to a couple of metrics such as Process Network Latency and Remote Display Session Latency (e.g., ICA Session Latency). Without a sanity check, the CID Key was reporting what it was receiving from the operating system or from WMI counters and these could be very large numbers that could skew the average and peak values for that entire hour or day or more. To address this, Liquidware added a sanity check that sets the maximum value of latency to 500ms.
  • Liquidware added support for 64bit Teradici PCoIP WMI Counters and updated the administrative scripts to register and use Teradici PCoIP WMI Counter DLLs. These enhancements will work on Amazon WorkSpaces and other platforms that use 64bit WMI Counters.
  • Liquidware removed CID Key components that have been phased out from the installer. Some of these include id_unit.exe, SSWarn.exe, lwldatasvc64.exe, lwlmntr.dll, and lwlmntr64.dll.

Hub, Database, & Collectors

  • Liquidware has begun using TCP/443 for secure inter-appliance communications. This secure communication channel will be used for registrations and upgrades going forward. The usage of SSH (TCP/22) and all the issues related to default passwords and enhanced security etc. is being phased out and will only be supported for backward compatibility during migrations from older versions.
  • Liquidware added support for quicker, smaller updates and patching on Stratusphere appliances. Stratusphere Hubs that have access to the Internet and can check for Liquidware’s update site for updates will display major image upgrades, smaller updates, patches, and hot fixes within the Web UI and end users will be able to use existing Hub Administration > Upgrades functionality to download and apply these software updates across all Stratusphere appliances. For air-gapped Stratusphere Hubs that do NOT have access to the Internet, end users will need to download these updates from our software download site, upload them to the Hub appliance through the Web UI, and apply them to all Stratusphere appliances using the new secure communications channel.
  • Liquidware enhanced useability by adding support for Application Load Balancing (ALB), Network Load Balancing (NLB) and proxies on the Hub and Collectors to collect CID Key data uploads.
  • Liquidware added journal files to the diagnostics log bundle to get deeper view of what was going on within the appliances to resolve and fix issues.
  • Liquidware has increased the /var partition from 2GB to 4GB to make future in-place upgrades possible. Other partitions have also been increased to address other space related issues.
  • Liquidware also added additional logging during upgrades when the database schema is being updated to the latest version to show that schema upgrades started, are running, and have completed successfully.
  • Liquidware has reenabled upgrading Collectors from the Web UI in addition to the console-based upgrades earlier.

Bug Fixes

Advanced > API Builder

  • Fixed an issue within the API Builder > Output tab when selecting CSV ONLY as OUTPUT TYPE would still not enable the CSV OPTIONS tab where other items could not be selected or enabled.

Advanced > Dashboards

  • Fixed an issue where the Preferences > Max Concurrent Connections field would accept values greater than 6 where it needed to only accept values between 1 and 6.
  • Fixed an issue related to creating a new dashboard prior to all existing dashboards being loaded by disabling the + button that creates a new dashboard until all existing dashboards are loaded.
  • Fixed an issue where the EDIT DASHBOARD window would display INVALID DATE messages while creating a new dashboard. These fields were only to be displayed for existing dashboards and not for newly created dashboards.
  • Fixed an issue where the DISPLAY checkbox under the DASHBOARDS list view was not working as expected to display the selected dashboard plus was not being saved as expected either. As a simple workaround related to checkbox states not sticking, the main Dashboards list view defaults to 100 rows to start with.
  • Fixed an issue where the main Dashboards > Home tab would get stuck on displaying Initializing Preferences status and not display any tabs. This issue was caused due to cached preferences and user permissions to see dashboards based on user group settings.
  • Fixed an issue where the Add / Edit Widget windows would let you close the window with required fields not filled in. In a related fix, some of the checkboxes were reset to default states with no user inputs when the widget was edited.
  • Fixed an issue where the DISPLAY column under Dashboard’s tab list view would not sort properly.
  • Fixed an issue where resizing an empty container would break the JavaScript on the page and the end user could no longer save or move or create anything on the page.
  • Fixed an issue where the pagination and number of entries on the table UI elements were missing from the multi-table widget on the dashboard.
  • Fixed an issue where the actual dashboard tabs would be hidden by the top level Home, Dashboards, Widgets, Datasources… tabs wrapping over to the next line if the browser window was at half screen width on a 24” monitor.
  • Fixed an issue where SEARCH would not work as expected if a widget on a dashboard with search item was deleted from the dashboard.

Advanced > Inspectors

  • Fixed an issue where there were differences between the Session Idle Times being displayed while using detail data and roll-up data. The detail data is displayed per CID Callback whereas the roll-up data is for the entire day. The column header and associated hover help text has been appropriately updated to reflect the reasons behind the differences.
  • Fixed an issue within Advanced > Inspectors > Applications and Process Names tabs where the ACTIVE MINUTES PER CID and TOTAL ACTIVE HOURS for the CID Key process in a DAY resolution would display negative values.
  • Fixed an issue within the Advanced > Inspectors > Applications and Process Names tabs under the OVERVIEW | OVERVIEW TYPE table was selected.
  • Fixed an issue within the Advanced > Inspectors > User ID and Machines by enhancing the calculation of the machine’s distance from a Wi-Fi Access Point by using right band frequency and specific channel to provide a more accurate distance from the Access Point. This distance calculation is still an approximation that could change based on the obstacles and their density between the machine and Access Point.
  • Fixed an issue related to seeing an “AW SNAP” browser error while within the Advanced > Inspectors and the mouse is moved over any of the drop-down menus. This error was related to usage of GPU within Chrome while on some of the UI elements like tables.

Advanced > SpotChecks

  • Fixed an issue where a SpotCheck could not be pasted, validated, and imported as expected.
  • Fixed an issue where Action > Enable All and Enable All Showing under the SET THRESHOLDS window were not working as expected.

API

  • Fixed an issue where the API would display an error on Inspector 0 where it was filtering by external IP address and then using UNBASIS on it.
  • Fixed an issue where the API would display an error when working with Peak1 and Peak2 Memory Percent columns.
  • Fixed an issue where and end user could not pull high resolution per minute trending data using the API. The API now supports the “use_trending:1” option to pull high resolution trending data. Liquidware would caution end users to use this option for very small period for specific users or machines due to the high volume of detail data that can be requested from the database.

CID Key

  • Fixed and enhanced associating processes with an application by ignoring processes that have their paths within the Windows system folders.
  • Fixed an issue where the CID Key was not collecting and updating the Windows 10 Version such as 1809 or 21H1 or 21H2 etc.
  • Fixed an issue where the CID Key as part of its software inventory functionality was missing Application Installed Date, processes that are part of the application, the size of the application, and its architecture type (32/64bit) in some cases.
  • Fixed an issue where the Event ID information is truncated for some very long messages within the Event ID. We added special handling for Event ID 1000 that are for application crashes to collect the entire message. However, we still truncate messages within other Event IDs if they are too long as collecting the entire message might increase the database size significantly.
  • Fixed an issue where the CID Key in rare cases would report the incorrect Wi-Fi channel band (2.4GHz or 5GHz).
  • Fixed an issue where the CID Key would not display Wi-Fi metrics for hidden SSIDs. These metrics are now displayed, and the CID Key reports all hidden SSIDs with “!!HIDDEN!!” SSID name.
  • Fixed an issue where the CID Key could crash in rare cases due to a WMI related condition which is now checked for so that it can be avoided.
  • Fixed an issue where the CID Key would take too long to stop all its services causing timeout issues which would then need to issue the commands to stop services multiple times.
  • Fixed an issue where the end user would see an error message when logging into a Windows 7 or Windows Server 2008R2 machine with July 2021 updates.
  • Fixed an issue where the CID Key now properly identifies Oracle Linux 8 as the operating system.
  • Fixed an issue where the CID Key was reporting very high values for Power consumed by the machine.
  • Fixed an issue where the CID Key was not reporting Battery stats as expected.
  • Fixed an issue with auto-upgrade of the CID Key on Ubuntu 20.04.
  • Fixed an issue with 10Zig Zero Client and added 64bit support as they were replacing all older 32bit versions with 64bit versions.

Hub, Database, & Collectors

  • Fixed an issue where the CID Keys on machines that were part of Machine Group with specific CID Key properties were not getting auto-upgraded even when the Auto-upgrade checkbox was enabled for the machine group.
  • Fixed an issue related to anonymizing of user and machine information where the machine’s anonymized hostname was being returned to the CID Key instead of the original hostname which was causing issues.
  • Liquidware is aware of situations where data gets incorrectly inserted into parent partition of the table instead of the day partition. Liquidware is still investigating why this happens but has added a self-healing script to the daily maintenance of the appliance that restores data to the day partition from the parent partition.
  • Fixed an issue where the Hub and Collectors would not collect the latency of the CID Key calling back to the Hub and/or Collectors. Network policies to monitor TCP/443 from specific Collectors and Hubs with full logging were added as default policies to overcome this issue. It must be noted that if a new network policy for TCP/443 is added with any other source machines with no logging is added ahead of these policies then collection of latencies from CID Keys would stop.
  • Fixed an issue where immediate password change with enhanced complexity was not being initiated after enabling Enhanced Security mode. Additionally, some special characters were not allowed in passwords which would cause issues when used during migrations or joining to other appliances. The default SSH users on on-premises appliances is friend, however on some cloud platforms like AWS and Azure the default users could be ec2-user or azureuser or something entirely different. All the scripts and logic were updated to work the non-standard usernames and complex non-default passwords and the friend user account was locked on cloud platforms.
  • Fixed an issue where the Collector would have issues when URL Logging is enabled.
  • Fixed an issue where the Collector would show larger network latency times by using ‘glibc’ library function.
  • Liquidware added additional handling to clean up older kernels on the appliance.
  • Fixed an issue where the Postgres transaction log was not being saved to the separate XLOG partition.
  • Fixed an issue where the /var/log partition on a Collector would get too full and affect upgrades from proceeding. The logs are now rotated at 10MB instead of the earlier 20MB.
  • Fixed an issue related to joining a Hub and Database using SSH joins.
  • Fixed an issue where we were not bringing over the API Whitelist, Blacklist and Client IPs during migrations from earlier versions.
  • Fixed an issue where the Collector interface sent and received counts were not working as expected.
  • Fixed an issue where the CID Key callbacks over an AWS Proxy would fail as our parsing logic for the IP included the port instead of excluding it.
  • Fixed an issue where saving Appliance Configuration or CID Key Properties would cause roll-up data to be reset. Also, disabling rollups would delete existing rolled up data as expected but it would not reset existing detail data so in case rollups were reenabled, it would not rollup all existing detail data as would be expected.
  • Fixed an issue related to using the updated files from the repository for Enhanced Security mode rather than using local files which might not have all the updated requirements.
  • Fixed an issue where in some rare cases the DATASTORES data from a VM DIRECTORY was not being saved on an ongoing basis by properly handling an error condition of a database table already existing properly.
  • Fixed an issue related to handling UPN within client certificates that are laid out slightly differently than expected.
  • Fixed an issue within the database schema that required a value for the channel field within the Wi-Fi stats table that could cause data to be discarded if it were missing.
  • Fixed an issue where the DNS address fields were limited to 64 characters and invite URLs was of a limited field within the database that caused issues when using longer DNS addresses that are automatically generated.
  • Fixed an issue where the backend and database would not handle a machine’s display monitor’s dimensions being empty.

Reports

Added, enhanced, fixed, or made minor formatting updates to the following reports:

  • Administration
    • Alert On Database Disk Purge
    • Database Schema Table Size Breakdown
    • Machine Cid Key Settings
    • Machine Inventory
  • Fit Assessment Reports (Pack 1)
    • 112. Assessment Findings
  • Fit Discovery & Findings
    • (New report) Machine Location Summary by City, State, & Country
  • Fit Reports – Applications
    • Application Comparison By Machine Groups
  • Fit Reports – Machines
    • Machine Age
    • Machine Age Details
    • Machine Configuration Summary
  • UX Diagnostic Reports
    • Diagnostic Findings
  • UX Diagnostic Reports – Apps
    • Application Load Time Summary by Date
    • (New report) Process User Input Delay Details by Machines, User, & Application Process
    • (New report) Process User Input Delay Summary by Application
    • (New report) Process User Input Delay Summary by Machine
    • (New report) Process User Input Delay Summary by User
  • UX Diagnostic Reports - Login & Session
    • User Login Details
  • Health Check Reports
    • 310. Diagnostic Findings
  • UX Diagnostics Reports – Machines
    • (New report) Machine Local Accounts Summary
    • (New report) Machine Local Accounts Details
  • UX Validation Reports
    • Diagnostic Findings
  • Windows Migration
    • Windows 7 Application Compatibility
    • Windows 7 Upgrade Hardware Compatibility
    • Windows 11 Upgrade Hardware Compatibility

Web UI

  • Fixed an issue within the Hub Administration > Connector ID Keys > Connector ID Key Properties tab’s CONFIGURE METRICS section, where the Web UI would not save the Application Process Metrics > Measure Latency filters as expected. Similar issue was fixed on the Inventory > Machines > Edit Machine > Connector ID Key Properties page.
  • Fixed an issue within the Hub Administration > Overview tab where the PENDING DATABASE INSERTS widget would not update information as expected.
  • Fixed an issue in Hub Administration > Upgrades tab where the text was pointing to a download site that did not host the upgrade image files. It has now been updated to point to the Upgrade Instructions that contains the upgrade image links. It also lets the user know if they can upgrade to the latest version of Stratusphere or do they have to migrate to the new appliance version.

Security Updates for Appliances

The update addresses Common Vulnerability and Exposure (CVE) items CVE-2018-5727, CVE-2018-5785, CVE-2018-10237, CVE-2018-20845, CVE-2018-20847, CVE-2018-25009, CVE-2018-25010, CVE-2018-25012, CVE-2018-25013, CVE-2018-25014, CVE-2019-5827, CVE-2019-12973, CVE-2019-13750, CVE-2019-13751, CVE-2019-17546, CVE-2019-17594, CVE-2019-17595, CVE-2019-18218, CVE-2019-19603, CVE-2019-20838, CVE-2020-0543, CVE-2020-0548, CVE-2020-0549, CVE-2020-8695, CVE-2020-8696, CVE-2020-8698, CVE-2020-10001, CVE-2020-12762, CVE-2020-13435, CVE-2020-13558, CVE-2020-14145, CVE-2020-14155, CVE-2020-15389, CVE-2020-16135, CVE-2020-17541, CVE-2020-24370, CVE-2020-24489, CVE-2020-24511, CVE-2020-24512, CVE-2020-24870, CVE-2020-25648, CVE-2020-27619, CVE-2020-27814, CVE-2020-27823, CVE-2020-27824, CVE-2020-27828, CVE-2020-27842, CVE-2020-27843, CVE-2020-27845, CVE-2020-27918, CVE-2020-28052, CVE-2020-28493, CVE-2020-29623, CVE-2020-35521, CVE-2020-35522, CVE-2020-35523, CVE-2020-35524, CVE-2020-36241, CVE-2020-36330, CVE-2020-36331, CVE-2020-36332, CVE-2020-36385, CVE-2021-0512, CVE-2021-1765, CVE-2021-1788, CVE-2021-1789, CVE-2021-1799, CVE-2021-1801, CVE-2021-1844, CVE-2021-1870, CVE-2021-1871, CVE-2021-2341, CVE-2021-2369, CVE-2021-2388, CVE-2021-3272, CVE-2021-3426, CVE-2021-3445, CVE-2021-3481, CVE-2021-3572, CVE-2021-3575, CVE-2021-3580, CVE-2021-3621, CVE-2021-3653, CVE-2021-3656, CVE-2021-3677, CVE-2021-3712, CVE-2021-3733, CVE-2021-3778, CVE-2021-3796, CVE-2021-3800, CVE-2021-4034, CVE-2021-4155, CVE-2021-20095, CVE-2021-20231, CVE-2021-20232, CVE-2021-20266, CVE-2021-20269, CVE-2021-20270, CVE-2021-20317, CVE-2021-20321, CVE-2021-21775, CVE-2021-21779, CVE-2021-21806, CVE-2021-22876, CVE-2021-22898, CVE-2021-22922, CVE-2021-22923, CVE-2021-22924, CVE-2021-22925, CVE-2021-23214, CVE-2021-23222, CVE-2021-23336, CVE-2021-23840, CVE-2021-23841, CVE-2021-25214, CVE-2021-26690, CVE-2021-26926, CVE-2021-26927, CVE-2021-27219, CVE-2021-27291, CVE-2021-27291, CVE-2021-27645, CVE-2021-28153, CVE-2021-28650, CVE-2021-28957, CVE-2021-29338, CVE-2021-30641, CVE-2021-30663, CVE-2021-30665, CVE-2021-30682, CVE-2021-30689, CVE-2021-30720, CVE-2021-30734, CVE-2021-30744, CVE-2021-30749, CVE-2021-30758, CVE-2021-30795, CVE-2021-30797, CVE-2021-30799, CVE-2021-31535, CVE-2021-32399, CVE-2021-33560, CVE-2021-33574, CVE-2021-33909, CVE-2021-33910, CVE-2021-33928, CVE-2021-33929, CVE-2021-33930, CVE-2021-33938, CVE-2021-35550, CVE-2021-35556, CVE-2021-35559, CVE-2021-35561, CVE-2021-35564, CVE-2021-35565, CVE-2021-35567, CVE-2021-35578, CVE-2021-35586, CVE-2021-35588, CVE-2021-35603, CVE-2021-35942, CVE-2021-36084, CVE-2021-36085, CVE-2021-36086, CVE-2021-36087, CVE-2021-36222, CVE-2021-37576, CVE-2021-37750, CVE-2021-38201, CVE-2021-42574, CVE-2021-42574, CVE-2021-42771, CVE-2021-43267, CVE-2021-43527, CVE-2021-44228, CVE-2021-44790, CVE-2021-45046, CVE-2021-45105, CVE-2022-0185, CVE-2022-21248, CVE-2022-21282, CVE-2022-21283, CVE-2022-21293, CVE-2022-21294, CVE-2022-21296, CVE-2022-21299, CVE-2022-21305, CVE-2022-21340, CVE-2022-21341, CVE-2022-21360, CVE-2022-21365, and CVE-2022-23094.

For additional information, refer to http://cve.mitre.org/index.html.

Known Issues

  • Liquidware is aware that 5.8.x version of the CID Key does NOT auto-upgrade to the latest version because the now older and no longer supported version of Stratusphere callback to TCP/5501 which does NOT and will NOT support provide upgrade installers for auto-upgrades. Liquidware strongly recommends upgrading to the latest version of Stratusphere to be up to date on security patches and get the latest features.
  • Liquidware would like to inform our end users that according to VMware Support, the VMWARE BLAST PACKET LOSS % metric under Advanced > Inspectors > Remote Display tab’s PROTOCOL | BLAST INSPECTOR VIEW only displays data for UDP based BLAST protocol connections. It does NOT populate any packet loss for TCP based connections.
  • Liquidware is aware that in one instance Dashboard level overrides (for example, using the same widget on different dashboards but using the API override for different machine groups on different dashboards) did not work as expected and might cause some widgets to display incorrect information related to machine groups. This issue is still being investigated by Liquidware and once a resolution has been developed, it will be provided as a patch and will be included in the next version release.
  • Liquidware is aware of some slowness while using Advanced > Inspectors has been observed on Google Chrome. Chrome has a Blink component that slows down performance when the Stratusphere API is configured to return 100+ rows. The workaround for better performance is to set the Limit to 25 rows so that the table begins to paginate at 25 rows per page.
  • Liquidware is aware that the sort order of the TYPE column within the Inventory > Machines tab is not sorting alphabetically. A fix for this known issue will be provided as patch and/or will be included in the next patch release.
  • On logging in to the Web UI, some pages such as OVERVIEW, DASHBOARDS, API BUILDER, etc. might not load or take a long time to load. This might be due to expired cookies. Log out of the Web UI using the link at the top right of the page and then try again. Clicking on the logout link clears all the cookies that might have been created in the past and starts clean.
  • Within Advanced > Dashboards, when trying to add a new Datasource, users could use the API Builder to formulate the API String and then import it by clicking on the USE CURRENT APISTRING button link. This button link was not working as expected. Due to internal workings, this link has been removed from the product for now and will be reintroduced in the next version. Users are advised to have the API Builder open in another browser tab, and manually copy and paste it within the field for specifying the API.
  • Advanced > Inspectors might appear within a very small window after an upgrade. Hit the F5 key to restore the regular size.
  • While importing Stratusphere OVFs on some ESX versions, the VMware Virtual Infrastructure Client will show a warning. These warnings can be safely ignored.
  • The Windows CID Key on Amazon WorkSpaces depends on the Teradici PCoIP agent to populate the remote client’s name and IP Address within the registry. If the PCoIP agent does not populate the registry, the CID Key will not be able to collect this information.
  • The development of the Windows Advanced CID Key has been paused and will not be available in newer versions of Stratusphere.
  • The Diagnostics > Inspectors > Desktop Application Summary page times out after 15 minutes and might result in an error. This is due to the Chart on the page waiting for a query to finish. If the user uses the browser’s Back button, the table data will be updated but the chart might be empty or displaying existing results.
  • Liquidware is aware of an issue where the end user might see a message "Please use the Console of the Collector appliance to upgrade..." on the Login page. This is a refresh issue and should go away after hard refreshing the Login page (Shift+F5).
  • FIT Reports – Applicatons: APPLICATIONS WITH KNOWN POOR VDI FIT INSTALLED BY USER AND MACHINE (CSV) fails if no applications are set as Poor VDI FIT under the Assessment > VDI FIT Profile tab.

Announcements

Important: End-of-Life for Stratusphere versions 6.0.0–6.1.1: Liquidware will discontinue all sales and technical support of Stratusphere versions 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.1.0 and 6.1.1, effective 12/31/2022. We encourage all customers who might still be using these versions to upgrade to a more recent version to take advantage of the numerous technologies and feature enhancements as well as resolved support issues.

Important: End-of-Life for Stratusphere versions 5.8.7 and 5.8.8: Liquidware has discontinued all sales and technical support of Stratusphere versions 5.8.7 and 5.8.8, effective 12/31/2021. We encourage all customers who might still be using these versions to upgrade to a more recent version to take advantage of the numerous technologies and feature enhancements as well as resolved support issues.

Release Available As

  • Software Update: This release is available as a Software Update across all supported platforms only if you are on 6.5.1-2 version of Stratusphere. However, if you are on 6.5.0 or earlier, we do offer a migration option whereby you can download a new Stratusphere 6.6.0 Hub and Database Appliance and use the migrate option in the consoles of these new appliances to migrate network configuration, certificates, and data from the old 5.8.6 or higher appliances to the newer 6.6.x appliances.

  • Note: See the Upgrading section below for instructions.

  • Virtual Appliance Downloads: Full virtual appliances will be made available for VMware vSphere, Citrix Hypervisor, Microsoft Hyper-V, and Nutanix AHV. Cloud platforms such as AWS, Azure and Google Cloud Platform will also be made available as they are certified. Liquidware has started the onboarding process on these cloud platforms, and they will be available in their respective platform Marketplaces as soon as the onboarding process is complete.

Release Applies To

  • Stratusphere Hub Appliance — Yes
  • Stratusphere Database Appliance — Yes
  • Stratusphere Collector Appliance — Yes
  • Stratusphere Connector ID Key — Yes

Upgrading

If your current installed version of Stratusphere is 6.5.1-2, refer to the 6.6.0 Stratusphere Upgrade Guide to upgrade to the latest version. If Enhanced Security Mode is enabled on 6.5.1-2 appliances, Liquidware strongly recommends using the console for upgrading to 6.6.0-1. The appliance will ask for a reboot to prepare for accepting the upgrade. After the reboot, the end user should initiate the upgrade steps again.

On-Premises Versions

If the current on-premises (VMware vSphere, Microsoft Hyper-V, Citrix Hypervisor, Nutanix AHV) installed version of Stratusphere is at 6.5.0, or 6.1.x, or 6.0.x, or 5.8.6 or higher, refer to the instructions in the Migrating to Stratusphere 6.6.x Appliances Guide to migrate network settings, certificates, and data from 5.8.6 and higher appliances to the 6.6.0 appliances. If the current installed version is earlier than 5.8.6, upgrade to 5.8.6 and then perform a migration using the instructions mentioned above.

Cloud Platform Versions

If the current installation of Stratusphere is on any of our supported Cloud Platforms (AWS, Azure, Google Cloud Platform), the 6.6.0 versions of the appliances are available within each cloud platform vendor. Liquidware is working on onboarding 6.6.0 versions of the appliances on support Cloud Platforms as well. Use the Migrating to Stratusphere 6.6.x Appliances Guide to migrate data and configuration from older versions of Stratusphere.

Alternatively, contact support@liquidware.com for further assistance.