Automate101, Level 27, PwC Tower 188 Quay Street Auckland 1010 sales@automate101.com

Release 12.13.5

Release Date

02 March 2021

Purpose

The main purpose behind this release is to address major issues around Security, Microsoft Online, Branding, and installers.

Bug Fixes and Improvements

Reference

Description

4511

Partner Center Permission
Prior to Atria 12.13, Partner center permissions have been reviewed and following a policy of least required permissions, we have reduced to 9 core permissions that will be granted by default when configuring the Azure AD/ Microsoft Online Service. Atria now requests the following permissions:

– Directory.Read.All​
– Directory.ReadWrite.All​
– Group.ReadWrite.All​
– Organization.ReadWrite.All​​
– RoleManagement.Read.Directory​​
– User.Read.All​
– User.ReadWrite​​​
– User.ReadWrite.All​​​
– User.ReadWrite.Alla​​

Service Providers may need to adjust permissions to meet their own automation requirements, this is still possible and the permissions granted to the Application can still be adjusted as needed.

4630

Underscore character in the brand name breaks the CSS
Unified branding experience was introduced in 12.13. There is a bug in the modern branding system which causes the stylesheet system to break if the brand name has an underscore character in it. This issue is now resolved.

4647

No type was specified for decimal columns error
There is a bug in underlying database access which flooding the logs with “No type was specified for decimal columns” messages. This issue is now fixed.

4652

EnhancedUserSessionLogging setting is blocking localhost connection
Enhanced user session logging was introduced in 12.13 to improve session tracking experience. This feature was blocking localhost connections in some environments. Required changes applied to the code to resolve the issue.

4667

Database upgrade fails due to Page Type Identity
There is a bug in Atria which causes database upgrade to fail due to Page Type Identity. This issue is now resolved.

4670

Microsoft Online – Provisioning fails due to agreement without a phone number
There is a bug in Atria which causes Microsoft Online provisioning to fail with “A partner confirmed agreement already exists for the customer” error. After investigation, it was revealed the issue happens due to the tenant in the partner center has an agreement without a phone number.

4757

Failure to update user with error: Invalid value specified for property ‘businessPhones’
There is an issue where updating a user with error fails with “Invalid value specified for property ‘businessPhones’ of resource ‘User'” error. This issue is now resolved.

4770

Object reference exception when the domain is not associated with Azure AD
Provisioning a user fails when a user has a UPN with an unverified domain assigned to a tenant. This bug is now solved.

New Features

Reference

Description

4532

Partner Center Modern UI Experience
Partner Center screen has been redesigned in modern UI design system and some improvements made to the fields validation.

Installers Bug Fixes and Improvements

Reference

Description

4666

Brand CSS fails to load when the system cannot write file to disk
There is a bug in Atria that fails branded CSS to load due to lack of write permission to wwwroot\brand-assets. A fix has been applied to the code to grant IIS_IUSRS Permissions to the wwwroot.

4430

Exchange Web Service use of -ErrorVariable fails when using Powershell 4.0
The following error is shown by the exchange web service when V4 Powershell is being used: “A variable that cannot be referenced in restricted language mode or a Data section”. This issue is now resolved.

4654

Missing modules required for Installing MSOL web service with scheduled tasks
When installing MSOLWS with createscheduledtasks parameter, it requires securitypolicydsc and computermanagementdsc modules to be installed. The code change has been applied to include these modules into the installation process.

4661

Windows Server 2012 Logging is not working
On Windows Server 2012 Log to sql errors with a TDS Parser exception and logging to event viewer is not working. These issues are now resolved.

Deployment / Update Checklist

The following Atria components need to be updated, please follow the recommended order of update.

Step

Component

Command-Line

Service

1

Database

Update-AtriaComponent -Database

Platform

2

Platform API

Update-AtriaComponent -PlatformAPI

Platform

3

Provisioning

Update-AtriaComponent -Provisioning

Platform

4

Web

Update-AtriaComponent -Web

Platform

5

Msol Service

Import-AtriaServiceSchema -Service

MSOL

6

Microsoft Online WebService

Update-AtriaComponent -MSOL

Azure AD / Microsoft Online

7

Hosted Exchange WebService

Update-AtriaComponent -Exchange

Hosted Exchange

8

PlatformAPI

Reset IIS on the PlatformAPI servers

Platform

9

Web

Reset IIS on the Web servers

Platform

Known Issues

None.

Internal

None.

Release 12.13.6

Release Date

11 March 21

Purpose

The main purpose behind this release is to address major security issues with the platform.

Bug Fixes and Improvements

 

Reference

Description

 

 

4860

Login Problem due to timezone issue
There is a bug in Atria for specific users in specific timezones which causes user login to fail. When the issue occurs the user receives “TimeSpan parameter must be within plus or minus 14.0 hours” error message. Required code changes have been applied to resolve the issue.

 

 

4867

‘Change Password’ redirects to the login page for remote location users
Due to some security tightening changes applied to the platform recently, change password functionality for remote location users was broken. Required changes applied to the code to fix the issue.

 

 

4766

Timeout error on Recorded Errors page
Database timeout occurs in Recorded Errors page when there is a huge amount of data logged on the database. A non-clustered index has been added to the database to resolve the issue.

 

 

4863

Improvements to Exchange Customer Delete
Some improvements and checks have been added to the script that removes everything related to an Address Book Policy.

 

 

 

Deployment/Update Checklist

The following Atria components need to be updated, please follow the recommended order of update.

Step

Component

Command-Line

Service

1

Database

Update-AtriaComponent -Database

Platform

2

Platform API

Update-AtriaComponent -PlatformAPI

Platform

3

Web

Update-AtriaComponent -Web

Platform

4

Msol Service

Import-AtriaServiceSchema -Service

MSOL

5

Microsoft Online WebService

Update-AtriaComponent -MSOL

Azure AD / Microsoft Online

6

Hosted Exchange WebService

Update-AtriaComponent -Exchange

Hosted Exchange

7

PlatformAPI

Reset IIS on the PlatformAPI servers

Platform

8

Web

Reset IIS on the Web servers

Platform

9

Agent

Install-AtriaComponent -Agent

Automated license reporting

Known Issues

None.

Internal

None.