Adaptiv Cloud Orchestrator v4.4

This page lists all the releases for Adaptiv Cloud Orchestrator v4.4.0.

Release 4.4.1

Release Date: May 29, 2026

This patch release addresses critical bug fixes, thus, improving overall user experience.

Addressed Issues

2393 – After editing a site and changing the Static Public IP, the updated IP address is not immediately reflected in the Service Order table after saving the change. A browser refresh is required to see the change.
2404 – In Service Orders, when configuring LAN for an HA (High Availability) site, the Primary and Secondary reserved IP addresses are not displayed during initial configuration, even though they are correctly applied when the LAN Configuration form is saved. These reserved IPs only become visible after reopening the LAN configuration in edit mode.
2406 – On the Customer Dashboard, the Edit Network Settings link is not displayed for Customer-role users who have Sites and/or Adaptiv My Connect associated with their account. The customers must contact the Partners to modify their network settings.
2409 – When a site configured with a private IP address is deleted, the associated private IP is not immediately available for reuse. The IP becomes selectable only after performing a manual browser refresh.
2410 – In Service Orders, when configuring CPEs with multiple LAN ports, the values entered in the DHCP First IP and DHCP Last IP fields disappear. After the fields are cleared, the Save button becomes disabled, preventing users from saving the configuration. To save the configuration, a user must enter the values manually or change the Router IP address.
2411 – In Service Orders, when the IP type of a site is changed from Private IP to Public IP at the gateway level, the Router IP field in the LAN Configuration section remains disabled. This prevents users from modifying the Router IP address and forces them to save the existing configuration.

Release 4.4.0

Release Date: May 05, 2026

Features and Enhancements

Please note that these features require the CPE to run on AOS v8.4.0 or greater.

Network Settings (QUIC Protocol Configuration) – The Network Settings functionality enables customers to configure policies at the network level, which are applied consistently across all deployed sites and My Connect users. In this initial phase, customers can define protocol-based controls to block traffic for specific protocols (QUIC), providing greater visibility and centralized control over network traffic.
- By default, QUIC blocking is enabled for new customers on newly deployed sites and My Connect users.
- For existing customers, QUIC blocking remains disabled by default to avoid disruption, but can be enabled at the network level via Network Settings → Protocol Settings. For details, see Network Settings.
PPPoE Link Configuration – Introduced support for PPPoE links under Service Orders → Technical Configuration → Links Configuration. When selected, users can configure the required Username and Password, with an optional Service field, while existing link configurations remain unchanged.
For HA sites, PPPoE settings must be provided separately for both Primary and Secondary devices. For details, see Links Configuration.

Caveats

It is recommended that My Connect licenses be created and deployed using a single service order.
To apply changes to My Connect users, resources, or private subnet configuration, the Update button from the My Connect dashboard must be clicked every time.
Changing the device type for a site with traffic steering, a custom site configuration may result in the custom site configuration not being correctly applied to the site. If a device change is necessary, we advise deleting the current site and creating a new one with a new custom configuration.
The network quality steering feature listed under device configuration in service orders cannot be implemented on the customer sites and is available for demo purposes (demo sites) only.

Addressed Issues

2417 – For some customers, the Security page under My Connect failed to render any data.

Open Issues

1086 – In service orders, users cannot create a customer whose name contains a substring that is already used in an existing customer name.
1462 – The Data Center value for the static IP block cannot be modified for service orders with static IP at the LAN. To change the Data Center value, remove the site from the queue, and edit it to set the static IP configuration to none. Save the site and edit again to choose the static IP at LAN configuration with the required data center.
1556 – If a user did not receive a recovery code during the multifactor authentication (MFA) setup process, multifactor login will not display the recovery code when they choose to "try another method" when they log in with MFA the next time. In this case, please contact Adaptiv Networks to reset the MFA account for the user. Examples of not receiving the recovery code include the browser being killed during the setup process or the user not selecting the "I have safely recorded this code" checkbox.
1561 – The "Forgot Password" login screen allows you to enter an email address other than your own. Adaptiv Networks recommends not editing the email address when trying to reset the password.
1586 – For a site with active DHCP reservations, routable subnets, or IP rules, a user cannot use a service order to modify the static public IP configuration. In this case, the site needs to be deleted and redeployed to modify the static public IP configuration.
1633 – A WAN port that has been configured through device management but has not yet been deployed is displayed as High rather than Not in Use. In order to see the port's correct status, the configuration needs to be deployed.
1676 – A user is prompted to enter the verification code rather than their login credentials after being logged out of the orchestrator and My Connect client due to inactivity.
1744 – An orchestrator user is prompted to reset their password to access the My Connect client after being invited to join Adaptiv My Connect. They can, however, continue to log in to the My Connect client using the same orchestrator password.
1748 – When a user is forced to reset their password for the My Connect client or Adaptiv Cloud Orchestrator, the user is not logged out of the application. However, the user is required to change their password before logging back to the My Connect client or the Adaptiv Cloud Orchestrator.
1773 – Sometimes the customer pin on the map in the partner dashboard is misplaced after changing the customer address.
1775 – On My Connect dashboard, when there is an orchestrator user with My Connect access, the orchestrator is greyed out in the list of resources in the Manage Resources form. To enable the orchestrator resource for the other users, either remove the ACO user with AMC access from the list or enable it for each individual user.
1820 – When using the mobile phone view in the Safari browser, the user profile view does not function as expected.
1837 – Customers who have multiple service orders may occasionally still see a pin on the partner dashboard's map even if they do not have any sites or My Connect licenses deployed.
1890 – In a service order containing only deployed My Connect licenses, if the licenses are removed and a site is added, the service order remains in In Progress status rather than going for completion.
1984 – When the customer address is updated in an existing service order, and a site from that order is added to the deployment queue, the site summary does not reflect the updated address.
2006 – The dashboard maps may occasionally show regions with a note saying "sorry, we have no image here." Refreshing the browser will display the map with all regions.
2022 – In service orders, editing a site to change the device type results in the Traffic Steering template drop-down on the Technical Configuration page being blank. A browser refresh will load the template in the drop-down.
2050 – In certain failure scenarios within an HA deployment, the site dashboard may inaccurately display the Active/Inactive status of the primary and secondary devices. While the traffic continues to flow correctly, the status of the device might be incorrect. In such cases, you can use Remote Access to connect to the device’s GUI and verify its HA status.
2267 – The service order table does not update the status of the order from "Complete" to "In Progress" after all the sites from that order are deleted, and the "Delete" button in the service order table remains disabled as well. A browser refresh is required to reflect the updated status.
2295 – In My Connect bulk user import, sometimes, the cancel import operation might appear to fail because the bulk import operation is completed before the cancel request is processed.
2331 – For customers with a large number of deployed sites, reducing the map size on the customer dashboard may cause the map to display fewer site pins than the actual number of deployed sites.
2356 – When editing a site, removed from the purchase queue, a flickering red error message briefly appears in the Edit Site form.
2357 – When configuring a Virtual Edge using LAN port 1 (default) with an IP@LAN address, the Site Summary page does not display the LAN port information.
2381– When opening the Site Summary page, the Customer section briefly displays the value “undefined” for a few seconds before populating with the correct customer information. During this time, all other sections of the Site Summary page load and display their data correctly.
2418 – In Service Orders, occasionally, when an HA site is removed from purchase and the LAN Configuration form is edited, the Primary and Secondary Reserved IP Address field values are not displayed in the form. Closing the form and reopening it in edit mode displays the values.
2419 – In Service Orders, when configuring a site with a Static Public IP at LAN, changing the subnet from /29 to /30 results in the site being incorrectly deployed with a private IP configuration. To deploy the site with correct IP configuration, edit the site to set the static public IP to None and save, then re-edit the site, select static IP at LAN with the correct subnet, and save again to ensure the LAN Configuration displays the public IPs.
2420 – In Service Orders, when a user changes the IP configuration from Static Public IP at LAN to Private IP, the system (orchestrator) allows the user to add the site to the purchase without requiring the necessary private IP details to be configured. As a result, the site is provisioned with an invalid IP address (0.0.0.0). It is, therefore, advised to add the IP details prior to adding the site to purchase.
2424 – When a user creates a custom site configuration (for app prioritization, traffic steering, and security) from device management and then navigates back to Service Orders, the custom configuration is not immediately displayed under Technical Configuration. A browser refresh is required to see the configuration under Service Orders.
2427 – In Service Orders, if a user verifies multiple sites that have the same serial number before clicking Save, the system allows the configuration to be saved without validation errors. This results in duplicate serial numbers being assigned across sites.