ControlUp On-Premises Release Notes

A full description of our new features and enhancements for this version is available here.

For this ControlUp On-premises (COP) release, we have made some improvements to the installation of the components, including Insights, as well as this new feature: 

• Solve: You can now install a Solve On-premises (SOP) server and gain value from our web app in your own environment. Read here about Solve. For the documentation, see Welcome to Solve.

Note: Some issues listed below refer to those customers who installed the beta version of SOP.

Known Issues and Limitations:

• In the Solve On-premises interface, Edge DX, Scoutbees, and Centralized Auditing are not supported or available.
• After upgrading consoles, clear the monitor cache manually to fix issue 79720 – ControlUp Insight session displays duplicated session ID. To manually clear the monitor cache: 

1. Delete files under C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\ControlUp\CacheActivity
2. Delete files under C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\ControlUp\CacheSchema 
3. Restart the monitor.

• 94751 – After upgrading from version 8.2x to version 8.5, the SOP & Insights On-premises (IOP) settings are deleted from the COP Server Installer.
• Workaround – configure SOP/IOP manually via “modify” on add/remove programs post installation.
• 94021 – IOP server may run out of disk space in standalone deployments (OVA or Linux). Fix to come in a future maintenance release of 8.5. If you encounter this issue prior to the release, we recommend contacting ControlUp Support or Professional Services to perform the fix.  
• 95660 – COP installer might fail to rollback on failed installation, leaving the system in a non-recoverable state. This issue occurs only when COP is installed on a Windows 2019 system. We recommend that you take a snapshot of the system prior to performing an upgrade, and revert to it in case of failed installations. 
• SOP – OVA installer does not enforce providing hostname and domain name while running. Failure to provide hostname or domain name will result in OVA redeployment.

Fixed Issues:

The following issues were fixed for this release of ControlUp On-premises.

• 81890 – Support Console GoTo Insights for IOP 8.x – Go to Insights from Hosts grid views will not check the selected Host.
• 84449 – On-Prem Installer – Win Server 2019 – The ControlUp Central Configuration is disconnected when the COP Server Installation is run with Service User & SQL User.
• 84565 – License Update – The trial expiration bar is displayed even after a paid license is updated. 
• 89048 – COP VMware Server Upgrade – COP VMware Server Upgrade from any VMware version to v8.2.1.6000 in Trial Mode causes the trial license bar to display with an expiration of {0} days.
• 89059 – Solve – COP VMware Server Upgrade – COP VMware Server Upgrade from v8.2.0.12000 to v8.2.1.6000 in Trial Mode causes the trial license bar to display Solve as {21} days.
• 89470 – COP VMware Server Trial Mode – Selecting the Close option of the trial license bar expiration causes the Real-Time Console to crash.

Insights On-premises (IOP) 

IOP Improvements

Note: To benefit from the improvements to Insights, the Insights On-premises Forwarder must also be upgraded to version 8.5.

• Customized reports – Customized reports can now be linked directly to the IOP UI.
• Management UI – Introduced a new management UI that allows executing all management tasks from the UI
• Branch mapping views – Now added to IOP menus.
• Better disk management to provide higher availability.
• Activity files alerting – Issues with the activity files upload stream are now reported by mail.

IOP New Known Issues and Limitations

• Automated reports may produce only 10 results. Workaround:

1. Connect via SSH to the IOP master node or server if standalone.
2. Change directory to  /opt/iop_volumes/config/iop_search/apps/iop/appserver/static vi automated_reports.js​
3. Enter editing mode by typing i. 
4. Go to line 100: 

   pageSize: “100”,

   And add this snippet as follows:
   

5. Save and quit editing mode by typing ​:wq. 
6. Log into IOP, go to Settings > Maintenance Tasks and click Reload Web Server Cache.
   

   Now your users should be able to see 100 results. 

• Management UI: the following behaviour is expected:
• For Linux and OVA when no public key is imported in the Service and Resources pane: 
• On the services table there is no indication for the status of a container. For OVA a button to import a public key appears.
• On the servers table, the OS and version indicated are from the backend server and there is no indication for the Linux distribution.
• Disks details pane is not supported on Linux-based installations.
• Customized reports: A non-admin user can change and delete admin user reports.
• VMware snapshots are not supported in IOP.

IOP Fixed Issues

These reported issues were fixed for this version.

• 85491 – Session Resources logoff time shows wrong data.
• 85933 –  Session Activity last 60 days old sessions as ‘still active’.
• 70639 – Missing data on app usage details when using computer picker to select multiple computers.
• 80844 – IOP forwarder – When modifying “activity file path”, the field displays the path that it was installed with and not the new one.
• 87786 – Users selector does not display all users in the Protocol Trends report.
• 83589 – IOP runs out of space in Linux-based installations.
• 79720 – ControlUp insight session shows duplicated session ID. 
• 83202 – IOP Index overflows and doesn’t truncate old data.
• 84460 – Data flows to IOP intermediately.
• 86027 –  Automated reports provide different result than interactive reports. 

Solve On-premises:

New features and enhancements:

• Real-Time dashboards
• Dynamic Topology view
• Real-time grids
• Grid filtering
• Administration UI for SOP appliance

Known Issues and Limitations:

• Historical troubleshooting and reporting is not available on SOP.
• SAML based authentication is not supported.
• While deploying SOP, domain name must match the COP server domain FQDN.
• Changing SOP server name does not trigger automatic DNS record change and a manual change is required. 
• After importing configuration for SOP server restore, a manual restart of DB config server is required.