Skip to content
English
  • There are no suggestions because the search field is empty.

Orchestry Updates for July 2024 | Part 2

This update includes several improvements and bug fixes

July has already been a huge month for Orchestry, releasing Health Checks, custom recommendations and partner tools.

 

Check out the dedicated release notes for that release earlier this month.

Improvements

Health Check Benchmarks: For both 'Workspace Inactivity' and 'Secure Score Benchmarks', we have updated the delta logic to show the increase/decrease in a more intuitive way. 

 

JulyUpdates1

Health Check Orchestry Usage: Improved the Orchestry Usage section of the Health Check to better capture previous data points from the last 30 days of activity.

 

JulyUpdates2

Optimized Efficiency of Scanning Engine: Scanning engine is now programmed to resume an interrupted scan more efficiently by tracking exactly where it left off.


Improved Change Detection of Scanning Engine: Scanning engine will now detect changes such as SharePoint Sharing Settings and ensure a workspace is re-crawled.

Bug Fixes

  • Large Archival Arithmetic: Fixed an issue where archivals could fail in a "Move to SharePoint" method where the file storage was over 2GB and the built-in integrity check was not converting the value properly.
  • Health Checks for Beacon Customers: Fixed an issue where partners of Beacon customers may not see a Health Check in Partner Tools exactly the same way as the customer.
  • Sending Notifications as Shared Mailbox: Fixed an issue where sending as a Shared Mailbox was no longer working as expected. A known issue with this release is that the fix does not yet correct the issue for Archival Policy Escalation (No Response Received) emails. This will be corrected in an upcoming release.
  • Orchestry Install without Viva Engage: To better support GCC customers who may not have Viva Engage enabled, we have adjusted the installer to account for this and allow the install to continue.
  • Duplicate Owner as Requestor: Fixed an issue where a requestor can be incorrectly added twice to a request if mistakenly added by the user again.
  • Public Sites Using Wrong Claims Group: Fixed an issue where provisioning Public SharePoint Sites was adding the Everyone claims group which diverges from native functionality. This has been altered to use the Everyone Except External Users group, aligning with SharePoint native functionality.