Adaptiv Cloud Orchestrator v4.1

This page list all the releases for Adaptiv Cloud Orchestrator v4.1.

Release 4.1.12
Release Date: December 5, 2025
Features and Enhancements
- Firewall logs functionality – A new functionality has been added to the Firewall feature, enabling users to download logs of blocked events for all firewall policies. Users can now download up to 1000 of the latest blocked events in the form of a CSV file.
- Peak bandwidth graphs – This release enhances the interface bandwidth graphs on the site monitoring page by adding peak gateway bandwidth utilization to existing average bandwidth across all configured interfaces (WAN and wireless) on the Edge device.
Release 4.1.11.2
Release Date: November 05, 2025
Addressed Issue
This patch release resolves the following issue and addresses the configuration limitations caused by it.
- 2207 – When configuring a Custom Site Configuration under Traffic Steering, it MUST also be configured under App Prioritization before the Update button is selected. Once the Custom Site Configuration is configured for Traffic Steering, a user MUST NOT change the App Prioritization to any default template. Failing to do so will result in a configuration error that removes the site from the customer dashboard. If the site is affected with the issue, recover the site by opening the service order and removing the site from Purchase. In Technical Configuration > Traffic Steering, replace the custom site configuration with a default template. Re-add the site to Purchase and deploy it.
Release 4.1.11.1
Release 4.1.11
Release Date: October 17, 2025
Features and Enhancements
- Support for multi-carrier tier tenancy – This release announces support for multi-carrier tenancy within the Adaptiv Cloud Orchestrator platform, which allows other carrier tenants to configure and manage their own super-partner, partner and customer ecosystem in the orchestrator.
Release 4.1.11
Release 4.1.11
Release Date: October 03, 2025
Features and Enhancements
- Firewall Policy Configuration – We are excited to introduce the much awaited Firewall Policy Configuration – a powerful security enhancement that allows customers to define inbound, outbound, and application traffic policies directly from the Cloud Orchestrator. This feature will allow customers to optimize site traffic by controlling the access to traffic in and out of their network. Firewall Policy Configuration is available only to customers with Web Protect security type configured for their site.
- Support for serial number validation and verification – The orchestrator now supports serial number validation and verification. This feature, in service orders, will now check the serial number against those registered with the database, ensuring it is valid, correctly formatted, and associated with the correct device model. It will help prevent misconfigurations and ensure seamless deployment.
- Addition of new "Add to Purchase" dialog – To ensure transparency and billing clarity, a new confirmation dialog has been added to service orders. Before adding a site or My Connect licenses to the deployment queue, partners will now be prompted to confirm their purchase with Adaptiv Networks. This confirmation acknowledges that billing will begin as soon as the site is added to the deployment queue.
Addressed Issues
- 1021 – In certain cases, the percentage of completed service orders on the partner dashboard does not match the actual data.
- 1562 – In the event of a link outage, the site dashboard fails to show MOS score during the period of outage.
- 1970 – Adding special characters to a customer name might result in customer dashboard loading issues. Removing the special characters from the customer name will resolve the issue.
Release 4.1.10
Release 4.1.10
Release Date: June 27, 2025
Features and Enhancements
- High Availability – We are thrilled to present a new feature in this release: the ability to configure High Availability (HA) sites directly through the orchestrator. With this enhancement, partners can now create and deploy high availability sites seamlessly. They can use the orchestrator to centrally manage HA sites and monitor devices and view detailed statistics at both the site and device level through the site dashboard. For more information, see High Availability Sites.
Addressed Issues
- 1951– On some occasions, when switching customers in the Customer table using the Firefox or Safari browsers, the customer information is not updated, while the breadcrumb and URL get updated. Reselecting the customer resolves the issue.
Release 4.1.9
Release 4.1.9
Release Date: May 09, 2025
Features and Enhancements:
- Virtual Edge – We are pleased to announce the support for Virtual Edge provisioning via orchestrator. Partners can now configure, deploy, and manage Virtual Edge using the orchestrator.
- Adaptiv Managed Sites – This release introduces Adaptiv managed sites. A site that is manually configured and managed by Adaptiv administrators is known as an Adaptiv managed site. Such sites operate in a read-only mode, which means they cannot be modified or deleted from the orchestrator. To learn more about these sites, Adaptiv Managed Sites.
- Renaming Security Types – The existing security feature types are renamed in release 4.1.9 to support marketing rebranding. Cloud Protect is now rebranded as Web Protect and Cloud Secure is rebranded as Network Protect.
- Site Summary Enhancements – To simplify the use of Site Summary, we added the option to copy or download the summary.
- General Improvements – This release adds general improvements to Service Orders and Site Configuration modules to improve user experience.
Addressed Issues
- 1800 – Regardless of the user's time zone, the site monitoring graphs always show data in EST timeline.
- 831 – Although it is possible to configure an E-80 with 5G wireless in the orchestrator, the deployment fails since this configuration is not supported at this time.
- 1913 – The main menu within left panel of the orchestrator might flicker upon browser refresh.
- 1921– For Core and E-80 devices, trying to configure more than 1Gbps/1000 Mbps (on ports supporting it) will fail. Therefore, it is advised to configure a maximum of 1Gbps/1000Mbps on these ports.
Release 4.1.8
Release 4.1.8
Release Date: March 28, 2025
Features and Enhancements
- Branding – This release adds branding capabilities to the orchestrator. Carriers, super-partners, partners, and customers can all apply their own branding standards to the orchestrator through branding. These tenants will be able to promote the orchestrator as their own by adding their own logos and designs to it. Only specific orchestrator components are eligible for branding in this release. Contact our Solutions Team to learn more about branding.
- Status and Status Indicators for Adaptiv My Connect – We have added various statuses and status indicators to the My Connect dashboard in order to efficiently manage My Connect network data, users, and authorized resources. With the use of these indicators, users can now quickly identify modifications made to a user, authorized resources, or network data. See Managing Adaptiv My Connect for details on how these indicators and statuses operate.
- Deployment Progress Indicator – Deploying sites and My Connect licenses through the orchestrator just got more efficient. When the sites or My Connect licenses are being deployed using the orchestrator, we have included a deployment progress indicator that lets users see the deployment status and outcome. The new indicator will display the deployment progress as well as its success or failure. To learn how the functionality works, see Deploying Service Orders.
Addressed Issues
- 1492 – The Deployment Status of only one site is changed to Deployed when multiple sites are deployed simultaneously. The status of the remaining sites is still Pending Deployment.
- 1576 – When a site is redeployed after editing its configuration, the site's status may still remain as "Pending Deployment."
- 1689 – Once My Connect licenses have been cleared from a service order, the order becomes Complete and cannot be deleted. To delete, it must be taken out of the queue. By doing this, the status will be changed to In Progress, enabling the deletion of service order.
- 1754 – A My Connect service order cannot be added to the deployment queue by using the Add to Queue button after the licenses are cleared. A browser refresh is required to enable the button.
- 1755 – When My Connect licenses are deployed first in a service order that contains both sites and licenses, the sites might get stuck in the Deployment page's Pending Deployment status. The site status changes to Deployed when you refresh the browser.
- 1787 – Before using Manage Resources in batch actions, the pagination for resources in user information page must be adjusted such that every resource is displayed in the same window. This will allow Manage Resources form to display all the resources within the form.
- 1792 – Under Deployment page in service orders, deploying sites and My Connect licenses at the same time results in sites getting stuck in Pending Deployment status. A browser refresh is required to update the site status to Deployed.
Release 4.1.7
Release 4.1.7
Release Date: February 07, 2025
Features and Enhancements
- Custom site configuration – This release introduces custom site configuration templates. After a site is deployed, partners and clients can now add a custom configuration that is unique to each site. Application prioritization, traffic steering, and security features can all be customized using these templates. To learn more about using these templates, see Site Configuration Management.
- Multiuser support for My Connect – We enhanced My Connect dashboard with the ability to select multiusers. This enhancement provides partners and customers the ability to manage batch operations for multiple My Connect users at the same time. See User Management to learn more about using this functionality.
- Adaptiv Cloud Orchestrator access for My Connect users – Implemented a workflow that will prevent My Connect users having Adaptiv Cloud Orchestrator access from deleting or disabling themselves. Additionally, it will also prevent them from removing their own orchestrator access.
Addressed Issues
- 1647 – Some city names might not be accepted in the Add Service Order form's address fields. This prevents the creation of a service order.
- 1719 – If a valid address is not entered in the Add and Edit Site forms, the address app will display an error indicating that the address is invalid instead of offering address suggestions. In such a case, it is recommended to verify the address and enter it again.
- 1731 – The customer dashboard and partner dashboard display inconsistent customer network statuses.
- 1737 – If you enter more than one word with a space in the first and last name fields when creating a My Connect user, the space between the two words will be removed when you save it.
- 1772 – A partner or super partner with an orchestrator account will lose access to the Adaptiv Could Orchestrator if they use that account to create a My Connect user account. To avoid this issue, Adaptiv Networks advises against using an existing orchestrator account to create a My Connect user account.
Release 4.1.6
Release 4.1.6
Release Date: December 12, 2024
Features and Enhancements
- With this release, Adaptiv is thrilled to announce a significant milestone. Through the orchestrator, partners can deploy and manage Adaptiv My Connect in addition to other SD-WAN products. My Connect licenses can be deployed and managed by partners through service orders. The My Connect dashboard in device management is equipped with license distribution statistics, My Connect user creation and management capabilities, and the ability to configure authorized resources for My Connect users.
- To apply changes to My Connect users, resources, or private subnet configuration, the Update button from My Connect dashboard must be clicked every time.
Release 4.1.5
Release 4.1.5
Release Date: November 08, 2024
Features and Enhancements
Service Orders
- In service orders, the site form is enhanced with shipping address options. This enhancement will allow partners to select an option to ship the device associated with the site. To learn more, see Managing Service Orders.
Addressed Issues
- 1590 – The regions are not listed alphabetically in Technical Configuration and Deployment pages of a service order.
- 1624 – As a customer user, adding a routable subnet might fail due to subnet validation not being properly applied. Adaptiv advises entering the data again and rechecking the subnet value. If this fails, please get in touch with Adaptiv support to add the necessary subnet.
Release 4.1.4
Release 4.1.4
Release Date: October 10, 2024
Addressed Issues
- 1513 – In rare cases, changing a security template in device management is not successful and the previous template is retained. To successfully change the template, select the new template from the drop-down, click Save and refresh the page.
- 1595 – In the customer dashboard, when a user selects a site pin on the map and opens the site using that pin, they might not be directed to the dashboard of that site.
- 1601 – When a region with no sites is deleted from one service order, the same region is renamed as Undefined in another service order even though it still has sites. Adaptiv recommends to make sure that all sites under a region in different service order are deleted before deleting that region.
Release 4.1.3
Release 4.1.3
Release Date: September 20, 2024
Features and enhancements
Device Management
- This release enables support for routable subnets configuration. With this feature, users can set up subnets that are accessible via a router connected directly or indirectly to the Edge device's LAN interface. Routable subnets can be configured from LAN Configuration page in device management. Learn more about this configuration here.
Addressed Issues
- 1037 – On a service order, when configuring a LAN port on the Technical Configuration page, if a user chooses to use the default router address in a different subnet, validation errors can occur in the router IP and CIDR fields. This is because the CIDR field is grayed out. You must select a different IP address to re-enable the CIDR field and configure the LAN port to adjust the CIDR with the router address value.
- 1512 – The service order stays in "In Progress" status if a site from a completed service order is added back to the deployment queue and deployed again.
- 1560 – The Site Summary column in Deployment Queue table on the Deployment page in service orders is missing title.
- 1582 – The orchestrator response time to update the CIDR field with an increasing subnet value in device management > LAN configuration may be longer than expected.
Release 4.1.3
Release Date: September 20, 2024
Features and enhancements
Device Management
- This release enables support for routable subnets configuration. With this feature, users can set up subnets that are accessible via a router connected directly or indirectly to the Edge device's LAN interface. Routable subnets can be configured from LAN Configuration page in device management. Learn more about this configuration here.
Addressed Issues
- 1037 – On a service order, when configuring a LAN port on the Technical Configuration page, if a user chooses to use the default router address in a different subnet, validation errors can occur in the router IP and CIDR fields. This is because the CIDR field is grayed out. You must select a different IP address to re-enable the CIDR field and configure the LAN port to adjust the CIDR with the router address value.
- 1512 – The service order stays in "In Progress" status if a site from a completed service order is added back to the deployment queue and deployed again.
- 1560 – The Site Summary column in Deployment Queue table on the Deployment page in service orders is missing title.
- 1582 – The orchestrator response time to update the CIDR field with an increasing subnet value in device management > LAN configuration may be longer than expected.
Release 4.1.2
Release 4.1.2
Release Date: August 30, 2024
Features and enhancements
Login
- We are introducing multifactor authentication in release 4.1.2 to guarantee secure access to Adaptiv Cloud orchestrator. To log in to the orchestrator, both new and existing users will need to set up multifactor authentication (MFA). This method prevents unauthorized access to the application and improves security at the same time. Read more about the process here.
Release 4.1.1
Release 4.1.1
Release Date: July 12, 2024
Features and enhancements
Dashboard
- This release brings enhancements across site, customer, and partner dashboards to display service severity and link status with more accuracy. For details, see Service Severity.
Addressed Issues
- 1044 – On some occasions, if no data is available for your site, you will see a message on the device management page indicating that there is insufficient data to display on the page.
- 1151 – The text in the Notes field on the LAN Configuration page from Device Management cannot be removed but can be modified.
- 1190 – On the site dashboard, the online status of a WAN port is retained even after it has been reset.
- 1201 – The site dashboard displays inconsistent WAN port status upon browser refresh.
- 1239 – Resetting a WAN port from Device Management changes its status to medium issues on the site dashboard.
- 1264 – When a wireless port is reset from Device Management > WAN Configuration, it is still displayed on the Site Monitoring page without a status.
- 1266, 1362 – The site statuses are inconsistent across the partner, customer, and site dashboards.
- 1357 – After enabling or disabling DHCP server In Device Management > LAN Configuration, user must select Save to apply the changes.
- 1397, 1047 – Sometimes a deployed site is not shown in the Deployment table in service orders.
- 1366, 1368 – The WAN port statuses for a site are inconsistent.
- 1482 –Even though some customer networks have completed service orders, the Service Orders value for those networks is displayed as zero in the Customers table.
- 1483 – On some occasions, the Service Orders table does not show a completion date for completed service orders.
- 1497 – If an existing site (prior to v4.1.0) is using the default IP address of 192.168.29.1 and a site configuration change from public IP at LAN to public IP at gateway is required on another site within the same customer network, there is a possibility that the changes will not get applied. In such a scenario, Adaptiv recommends to delete the site and re-add it.