Hot off the press - Release 15.3 is available now for deployment!

New Feature Microsoft NCE Subscription Management - Phase 1

For Direct CSP partners, Atria brings you Microsoft Subscription Management - Retrieve and view all subscriptions, update subscription quantity.  Delegate management to Resellers and Customers.

Watch out for more NCE updates coming soon...

improvement PartnerCenter Offer Sync

This process has been updated to cater for NCE changes, versions prior to 15.3 will fail to update with a Conversion Failed error.  More improvements are coming to this area with coming NCE changes.

improvement Installer Process

We've added a number of fixes and improvements to installers - all with the goal of making updates easier for Atria administrators.  Includes fixes for updating to v15.x from v12.13.x

improvement PartnerCenter Test Connection Button

The PartnerCenter test connection has been improved, this now runs tests in parallel and returns more meaningful errors to help diagnose issues with PartnerCenter permissions.

improvement Indirect Provider Offers Update

For Indirect CSP providers, the catalog of products is stored in the Atria database, this catalog has been updated.

fix PowerShell Job Runner - Error handling when script is not present (9088)

If a PowerShell script is specified, but is not present on execution - the error message was shown as {message}.  This has been resolved and the message "Job Execution failed with No Script Present" is returned in the job results.

fix Password Expiry Date set to 1-Jan-1900 if password has expired (8475) 

Atria returns 1-Jan-1900 in the Account Settings when a users password has expired, this has now been updated to advise the password has expired, and to show the date of expiry.

fix Copy User function does not set password in Azure AD (9087)

The User Copy function was not setting the Azure AD password.  This bug has now been resolved.

fix AD Sync users can change password when CPNL flag set (9109)

A validation change has been made to stop users from resetting passwords when being synchronised using Atria ADSync from an external directory

fix Department field not being set in Azure AD at first provision (7171)

When creating users, the department field was not being set in Azure AD.  This has now been resolved.

fix Importing users incorrectly warns that users do not belong to current customer (9114)

This was caused by a domain name comparison being case insensitive.  This has been fixed and this error will no longer be displayed.

How to apply updates to Atria 15.x

15.2

A number of improvements have been made which will improve end-user experience and reduce wait times for commonly performed processes.  The net result is an improved user experience and faster turnaround of Atria initiated changes.

Multi-threading provisioning

We've brought back multi-threading to provisioning in 15.2, this means large request volumes from one customer will not cause as much delay in provisioning.  You can adjust configuration for individual provisioning engines as needed.

Provisioning Optimizations

An issue was found where provisioning rules were not being cached after being compiled, this causes every provisioning request to require more processing time. This has been optimized and individual provisioning times have reduced significantly.

Atria UI Performance

We have made caching adjustments to the UI which have boosted responsiveness, page load times are reduced. 

Delay in Edit User Control

In some scenarios the feature added to retrieve the last authentication time from AD was slowing the load time of the edit user control.  This has been optimised and caching introduced to speed load times and remove redundant calls.

Support #5021 : User Import Fails if the Manager account doesn't exist in Atria or was not imported first

Symptom: When importing users, if a users manager had not been imported into Atria, then the user import fails.  

Fix: Imports are processed in correct order, this problem should no longer occur.

Support #4988 : Unable to retrieve shared mailbox (Exchange Online) if a user which no longer has exchange is granted permissions.

Symptom: It is possible for a user to be granted permissions over a mailbox even when they do not have Exchange Online (when Exchange is removed, permissions over other objects are not removed).  The Atria UI for managing Shared mailboxes errors when it finds a shared mailbox in this situation.

Fix: Error handling has been improved to stop this error from occuring.

Support #5061 : Plans added and removed in same month are not shown in the billing detail report.

Symptom: If a service is changed multiple times within a month for a user, the Service Detail report only shows the service being removed.

Fix: The view has been altered to show the detailed adds and removes as separate line items that occurred within the month.  

Support #1510 : Mismatch on UPN duplicates the user when syncing into Atria (Microsoft Online)

Symptom : If a user exists in Atria and Azure AD with different UPNs, the sync process will duplicate the user in Atria.

Fix: Email aliases are now also checked to find a match for the correct user.

Support #4758: Billing Reports are not displaying the correct plan names 

Symptom: If a Service Plan was renamed at a customer level, on the Billing Report it shows as the Root Customer level plan name, not what the customer would know it as.

Fix: Overridden Service Plan Labels are now shown on the billing reports.

15.2

We recently introduced support for you to manage customers who have their own Active Directory instances.  Think each customer with their own AD forest.  

With 15.2 we have made a number of improvements.

• The PowerShell command Update-AtriaRemoteEnvironment has been added to AtriaTools for updating Atria components - this means you can update all Atria components deployed into an Active Directory from your central Atria server.
• Detach Environment - this lets you detach and remove a customers Active Directory from Atria management.  Commands have also been added to remove installed Atria components.
• Use multiple Atria locations for Private ADs.  Locations can now be selected when creating new customers.  This is useful if you need a different default configuration for a sub-set of customers with private Active Directories.

Today, we are pleased to make Release 15.2 available.  This release contains many minor fixes, key performance improvements and also some major new features.

More details will be posted in this feed, but for a quick summary:

• Re-introduction of multi-threading for faster provisioning times
• Caching changes added to improve UI responsiveness
• Add/Manage batch processes through Atria
• Integrations available for the top 3 PSA systems (ConnectWise, Autotask, Kaseya BMS)
• Improvements to update mechanism - easier update for Private Customer ADs
• Various fixes 

Our release cadence slowed due to the types of changes in 15.2, we will now return to more frequent and smaller updates.

15.2

• Map Atria customer to ConnectWise Customers
• Transfer product quantities to ConnectWise Agreement Additions
• Detailed logging for resolution of data problems

Find out more...

15.2

• Map Atria customer to Kaseya BMS Accounts
• Transfer product quantities to Kaseya contract lines
• Detailed logging for resolution of data problems

Find out more

15.2

Autotask is widely used to run the business operations of MSP businesses.  With this release, Atria can now keep your Service Contracts up to date with provisioned quantities - making billing easier and more accurate.

• Map Atria customer to Autotask Accounts
• Transfer product quantities to Autotask contract lines
• Detailed logging for resolution of data problems

Find out more

15.2

Atria now has a feature for managing and executing scheduled jobs.   This has been used for all our billing integrations, but is also there for you to use for running your own batch processes with the included PowerShell job runner.

• Create virtually any schedule 
• Encrypt and store secrets for use in your scripts - e.g. connection strings, API keys or credentials.
• Feed parameters into your PowerShell script
• Extract and use Atria properties for use in your script
• Centralize and standardize logging across processes
• Run processes on-demand through the Atria UI

We are moving our release notes to a new service provided by a third party service called AnnounceKit. This will allow our release notes to be published into Atria, making it easy for you to see what changes have been made.

• Easy to consume mechanism for letting you know about features and fixes in Atria
• Ability for you to give immediate feedback to help us improve Atria

Each note will be tagged with one of :

New Feature improvement fix announcement 

From v15.2, the new Release Notes feature will be enabled by default within Atria for Service Provider level users.  This means only users with the Service Provider security role will see the notification.

The feature can be disabled system wide, and it can also be controlled through permissions.  You will be notified when unread changes are available through an icon on the main Atria toolbar.

Privacy

We care about Privacy, by default, we do not collate any personal information through the use of this tool.  If you register your email address to automatically receive updates, we will store your email address in order to provide you with this service. Announcekit is compliant with GDPR and will protect your information.