Chat now with support
Chat with Support

Binary Tree Power365 Current - Release Notes

Binary Tree® Power365® 20.12.3

Release Notes

June 2021

These release notes provide information about the Binary Tree® Power365® 20.12.3 release.

Topics:

About this release

Binary Tree Power365 is a Software-as-a-Service (SaaS) suite that includes the following solutions:

  • Binary Tree Power365 Directory Sync

Binary Tree Power365 Directory Sync can set up and maintain an Active Directory sync, an Azure AD sync, or even a sync between Active Directory and Azure AD. Users in merging organizations can find each other in a unified Global Address List (GAL).

  • Binary Tree Power365 Migration

Binary Tree Power365 Migration lets you migrate mailboxes, archives, and content for Office 365 tenant migrations, for a secure, cloud-based transformation experience. With Binary Tree Power365 Migration, you also have the option to migrate OneDrive, OneNote, and SharePoint content as well as migrate from on-premises or hosted Exchange environments.

  • Binary Tree Power365 Integration

Binary Tree Power365 Integration introduces Day One collaboration capabilities to manage multiple Office 365 tenants by removing communication blockers that create challenges for end-users. This powerful tenant to tenant migration solution enables users in different tenants to share a common address list and view calendar availability while their mail and Office 365 workloads are being migrated.

It includes the capabilities of Binary Tree Power365 Migration and adds the ability to unify tenant address lists and calendar availability lookups as well as migrate Microsoft Teams, Groups and public folders.

  • Binary Tree Power365 Integration Pro

Binary Tree Power365 Integration Pro is a comprehensive solution for Office 365 tenant to tenant migration and integration. It unifies email domains and user collaboration across tenants while you migrate. This enterprise solution enables you to completely move users, workloads, directories and domains between enterprise environments without disrupting business.

Binary Tree Power365 Integration Pro includes all of the functionality of the Binary Tree Power365 Migration and Binary Tree Power365 Integration solutions and adds the ability to unify email addresses across tenants and to move domains without downtime.

  • Binary Tree Power365 for Active Directory

Binary Tree Power365 for Active Directory enables you to migrate Active Directory to accelerate your enterprise M&A and modernization initiatives. Binary Tree Power365 for Active Directory is a solution that integrates and migrates Active Directory, Azure Active Directory, and hybrid directory environments without requiring trusts, SQL, network connectivity, or installing servers.

 

Binary Tree Power365 20.12.3 is a minor release, with no new functionality. See Resolved issues.

Enhancements

The following is a list of enhancements implemented in Binary Tree Power365 20.12.3.

Table 1. General enhancements

Enhancement

Issue ID

Desktop Setup Pro has been updated to allow users to reconfigure their OneDrive for Business application after their source email addresses/usernames have been changed during a big bang domain move.

27140

The DumpStack.log.tmp file has been added to the default ReACL file exclusion list.

27337

The ability to exclude selected files from Device and File Share ReACL processing has been added.  To exclude files from ReACL processing, list the files in the "Exclude These Files From Processing" box in the Device ReACL Profile or File Share ReACL Profile.

27454

Installing the Active Directory Agent on 32-bit workstations is now supported.

27778

Desktop Setup Pro now migrates default signature settings when syncing signatures.

28051

The GetList function can now be used when mapping allowing the merging of multiple values in attributes like showInAddressBook.

28511

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where a Directory Sync profile could be created without a default password due to a user interface timeout has been resolved.

26901

An issue where the GetCred.exe localization instructions were missing has been resolved.

27269

An issue where users that are not sys admins could not skip Domain Cutover step has been resolved.

27473

An issue where Repositories settings could not be modified unless all fields were populated has been resolved.

27590

An issue where Global Variables were not loaded when included in PowerShell scripts has been resolved.

27634

An issue where Directory Sync cannot update users if the source accounts contain commas in the CN and are moved has been resolved.

27797

An issue where Desktop Setup Pro would hang when configuring Teams/OneDrive has been resolved.

27853

An issue where the link to the Cutover conversation history in Teams resulted an error has been resolved.

27860

Support for 21Vianet has been removed.

28132

An issue where conversation history was not migrated during Teams Cutover has been resolved.

28661

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 3. Tenant-to-Tenant known issues

Known Issue

Issue ID

Target MailUsers will be hidden from the GAL during cloud migrations after they have been prepared and until they have been provisioned. A matched target Mailbox will continue to be visible in the GAL after being prepared.

8125

Power365® does not support migration of the following mailbox settings at this time:

  • OWA:

    • Configuration

    • Time Zone

    • Work Hours

    • Signature

    • View Settings

  • Work Hours

  • Out of Office Settings

  • Calendar Configuration

  • Safe/Blocked Senders from Junk Email Rule

  • High Resolution User Photo (Root of the Mailbox)

  • Clutter Opt-In

  • Quick Steps

  • External Calendar Sharing

  • Mailbox Shortcuts to Shared Mailbox folders

7987

The Power365 mail migration engine supports migration of an archive to an archive only. Mailbox to an archive or archive to a mailbox migration is not supported.

7988

The Power365 mail migration engine does not support migration of client-side delegates or delegation for groups.

7989

The Power365 mail migration engine does not support Modern attachments (links to OneDrive files).

 

A duplicate source folder exception occurs when the same folder is copied multiple times as part of multiple migrations.

8002

Power365 only supports Free/Busy lookup when the recipient is being selected from the GAL.

8003

Signed and encrypted messages will not be rewritten by the email rewrite service (ERS).

8004

Additional custom SMTPs added to groups (outside of the email address policy) are not migrated during Group Sync.

8010

When using Directory Sync Lite, nested groups that exist in the target cloud only cannot be synced as group members.

8012

When Power365 creates groups using Directory Sync Lite, the groups will be created in the target on-premises hybrid exchange environment automatically, regardless of the origin of the source group.

8013

Accepted Senders (within Delivery Management) and Moderation settings (in Message Approval) are not migrated by Power365 Group Sync.

8014

MailTips (msExchSenderHintTranslations AD property) are not migrated by Power365 Directory Sync.

8015

Discoverability by Power365 may be delayed for new groups or recent updates to existing groups. This is due to delays in graph returning updated information.

8016

If a "matched" group is manually deleted from the target Exchange forest, the matching status in Power365 is not removed. This may result in errors during the group sync, as Power365 believes the target group already exists.

8017

Source mailbox retention policies and retention tags applied at the folder level are not copied to the target mailbox during mail migration.

8027

Power365 does not support changes to the mail-enabled folder's display name on the target.

8029

Contacts that are linked may not be copied during the mail migration if the PidLidIsContactLinked property is true and the linked ID points to an address hidden from the GAL.

8034

Prepare Job will fail if Power365 Directory Sync finds an existing contact object in the target tenant that is not created by DirSync.

8036

Hidden Public Folders will not be provisioned or migrated.

8039

Messages filtered with Azure Information Rights Management (IRM) will be migrated, but they will not be accessible by the end user. Messages encrypted with Office365 message encryption will be migrated, but they will need to be opened and decrypted via the web browser using the original source mailbox credentials.

8041

Hidden folders are not copied during mailbox migration.

8047

For on-premises migration projects, if a user is renamed in the on-premises environment after the upload has completed, Power365 will be unable to migrate that user. The migration will have to be deleted, and re-uploaded.

8052

If the Discovery Hold (eDiscovery in Office 365) hasn't been enabled, the DiscoveryHold folder will not exist in the Target. DiscoveryHold is a system folder which Power365 does not create. Migration of Litigation Hold settings isn't possible in this scenario.

8054

If there are any items in the purges folder that are within the retention period the item can't be deleted, therefore errors will appear in the logs. The overall status of rollback job will be successful. The purges folder isn't visible to the user. See the below link for information about the retention period settings, which defaults to 14 days.

https://technet.microsoft.com/en-us/library/dn163584(v=exchg.150).aspx

8055

If the Outlook Categories XML configuration file gets corrupted, the categories will not be copied, however the rest of the sync will continue, and will still be marked as completed if no other errors occur.

Workaround: A workaround would be to open Outlook and edit the categories in any way, which would cause the XML file to be rewritten.

8056

EWS access policies are not currently supported in Power365. (8061)

8061

Mail migration cannot be performed on mailboxes that are assigned an Office365 Kiosk License as MAPI connection is disabled for this license type. As a workaround, assign the mailbox an E1 or higher license during the migration, and then revert to the kiosk license.

8062

For on-premises migration projects, any user “Receive-As” permissions are not copied to the target. (Note: “Send-As” permissions ARE copied.)

8063

For on-premises migration projects (“on-premises to cloud”, or “cloud to on-premises”), any source forwarding addresses will not be set on the target.

8064

If the Shared Mailbox has In-Place archive or litigation hold enabled, an Exchange Online Plan 1 or Plan 2 license is required. Therefore, the target mailbox may also require a license. More information from Microsoft can be found here: https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits

8094

The incorrect domain is selected as the default domain for the Public Folder domain mappings. When the default domain is calculated, the initial domain (IsInitial) is set as default instead of the default domain (IsDefault).

8096

Public Folder domain mappings are case-sensitive. The DomainName value in the database can be set to lowercase to work around this issue.

8097

PowerBI reporting is not available outside of the US. (8103)

8103

Due to an Outlook bug, duplicate rules are added to the target when rules are viewed or edited using Outlook. Refer to the Knowledge Base article at https://binarytree.zendesk.com/knowledge/articles/360039534652/en-us?brand_id=360001123812 for information on avoiding this issue.

14613

Mailbox migrations will fail if the PowerShell User and the Archive and User Mailboxes are in different Exchange Online regions.

16982, 16983

Holiday calendars may be duplicated in the target mailbox after migration if the OWA holiday calendar is enabled.

19542

The assigned owner of tasks is not updated with the target username after migration, the owner will remain the source username.

7990

Although address translation in Power365 will work for attached messages in the .MSG format, it does not work for messages in .EML format or calendar attachments in iCal format. Any attached messages in .EML format or appointments in iCal that are migrated will still have the source display name and SMTP address after migration.

7991

If a contact with a birthday or anniversary appointment is migrated, and the birthday or anniversary date is changed, the corresponding appointment on the calendar is not updated and a new appointment will be created with the new birthday or anniversary date and the old appointment is retained.

7992

A Contact linked to a user that is migrated does not migrate with the link.

7993

After migrating a mailbox with conversation history, the "From" and the Subject for the conversation history items are being left as-is with the source user names still visible in the conversation history items.

7995

After the mailbox migration completes, the Skype for Business Meeting URL and Voice Mail Message listed in appointments and meetings will not be translated with target tenant information. The Skype for Business Meeting URL will be invalid once the source tenant is switched off.

7996

Birthday calendar appointments may be duplicated in the target mailbox after migration if the OWA Birthday calendar is enabled.

7997

When a calendar request is migrated, the "Accept" button does not add the calendar to the target user's Outlook/OWA.

8000

When using "Reply All" to a migrated conversation history message the source user's name is added to the recipient list.

7994

Internet calendars are migrated to "My Calendars" instead of "Other Calendars" Any updates to the internet calendars are not received as they are no longer internet calendars on the target.

7998

Not all Internet, Sharepoint, and Shared calendars for all Outlook versions are migrated. Users must manually re-add any calendars they have permissions to after the migration is complete.

7999

Folder permissions are not removed on the target when the permissions are removed on the source and synced again.

8025

Junk mail rules are not copied to the target.

8026

During mailbox sync and cutover, OOF (Out of Office) Rules, Junk Email Rules, Sweep Rules, and any client-side Rules cannot be read in the source tenant or written to the target tenant. Note that most mailbox server-side inbox rules and OOF settings are synchronized.

8734, 8735

The following server-side inbox rules cannot be synced:

  • Action "Pin to Top"(Outlook Web Access only)

  • Action "Apply retention policy"

  • Condition "Classified as"(Outlook Web Access only)

  • Condition "From any RSS feed"

  • Condition "From any RSS feed with xxx in the title"

14616

Migration does not work if an on-premises user has an online archive.

8046

In a hybrid environment with a "Basic" project, Power365 cannot automatically enable the archive for on-premises source users. Upgrade to a Power365 "Advanced Migration" or "Premium Integration" project, or, as a manual workaround, enable each archive manually.

8051

OneDrive for Business content migration will not be successful, unless the user opens OneDrive for Business from the portal.office.com, if the following is true:

  • The target user was prepared and synced with OneDrive for Business enabled.

  • The target tenant administrator deletes the target user and mailbox.

  • The target mailbox was then recreated and provisioned with OneDrive for Business.

8115

When there is a Preservation Policy enabled in the Target tenant One Drive or OneNote syncs will fail.

8126

OneDrive for Business content does not sync when using the Advanced from File project type.

8131

OneDrive for Business migration does not sync the "Restricted View" sharing permission during Cutover.

8120

The OneDrive for Business sync will not start during Cutover if the target user's UPN has changed.

8132

For OneDrive for Business migrations, an error message is not logged when you attempt to migrate a file currently in use.

8088

Full discovery is needed to detect OneDrive for Business changes.

8085

Power365 will discover the user’s OneDrive used storage size and quota based on SharePoint’s current information. The used storage size reflects all used space, including the Recycle Bin. Power365 does not migrate the user’s recycle bin therefore comparing used storage between source and target users does not indicate the success of a user’s OneDrive migration.

8117

OneNote data being edited in the source during a OneDrive for Business migration will log an "item has active edits" error.

8116

During OneNote cutover, if a Notebook is open in the source, edits will not be reflected in the target when cutover completes.

8118

OneNote fails to sync when the source is a Team that was converted from an Office 365 Group and the target is an Office 365 Group.

8130

Microsoft Teams/Office 365 Group OneNote pages are not synced at this time.

17201

OneDrive for Business migration does not set the folder/files containing shareable links to the matched users in the source.

8086

Some Site Permissions Levels such as Full Control, Design and Edit are not fully migrated during the OneDrive for Business Final Cutover Sync Job. The default level assigned to the target during migration is the “Contribute” permission level. Read and Contribute permission levels are migrated successfully to the target.

8087

OneDrive for Business migration does not set permission inheritance flag correctly.

8090

OneDrive for Business quotas are not set or enforced in the source and target.

8091

The OneDrive for Business migration report does not contain permissions that cannot be applied because there is not a matching target user in the target tenant.

8092

The Admin will be listed as last modifying a migrated OneDrive for Business item instead of the actual migrating user.

8089

When enabled, the OneDrive backup feature may duplicate OneDrive known folders (desktop, documents, photos).

16747

OneDrive for Business syncs fail if Legacy Authentication is disabled.

21302

The Admin is removed as an owner in target when Admin is a co-owner of the Office 365 Group in source.

16763

The Get-BTWorkflowLog cmdlet does not support the -Filter parameter.

8136

The Set-BTEnvironment -SkipUserDiscovery PowerShell command can only specify the parameter with numerical values as the boolean value (1=True, 0=False). If a user mistakenly attempts to enter a numerical value such as "16", the setting will get set to True because the "1" will be accepted as the boolean value.

18881

Folder permissions that are removed from the source are not updated on the target when synchronized.

8008

If a Source user is deleted after being discovered, Power365 will not process the deletion. The user will remain in the UI and in the Target if previously prepared. An error is received when a user is deleted on the Source or Target and the migration (Sync) is run again.

8009

An error message is displayed and the subfolder on the target is not deleted when the subfolder on the source is deleted and the migration is run again.

8018

The Public Folder engine will not rewrite source folder email address to target folder email address during content copy.

8038

Power365 does not support public folder sync if the folder name contains a back slash (\).

8020

Public Folder content copying will not start if the Provision job reported an error when mail enablement failed.

8042

If a migrated public folder is renamed after the first synchronization, upon the next sync, the "Folder Renamed" count will be incorrectly incremented again.

8053

During Public Folder migration, the job can be archived when the status is "Syncing".

8023

Security group sync and Security group membership sync are not supported. Permission sync on Public Folders and mail folders will use matched users and mail-enabled security groups, but permissions to members of the mail-enabled security group will not be propagated unless the admin has set up the target security group to have the same members as the source.

8024

If ERS is disabled, the DKIM-Inbound rule is removed. Any custom actions of the DKIM-Inbound rule would need to be set up again if ERS is enabled.

8121

The group owner is displayed as the author of Team conversations entered by a member who has left the team when synced.

8127

Synchronized Team conversations display up to 15 user reactions only.

8128

When an Office 365 Group is converted to a Team or matched to an already existing Team in the target, OneDrive for Business syncs may remove channels from the target Team if they were created directly in the target.

8129

Microsoft Teams migrated conversation history does not display reactions, emoji, and file icons in Internet Explorer.

18304

Team syncs may take longer when creating new Private Channels if delays to access to the channel folders occur.

19000

Due to changes by Microsoft, migration of files for Private Channels is not currently supported.

19571

Microsoft Teams system-generated event messages will not be copied by Power365 during Teams migration because these messages are protected and can only be set by Teams.

28661

The Admin account is removed from the source and target regardless of whether the account was added or it was already an owner. To ensure that removal of temp permissions does not remove any actual owners, connect the source and target tenants using accounts that are not owners of any users, groups, or teams.

14227

The ERS user's SMTP address is not rewritten to the target SMTP address when they send on behalf of a non-ERS user.

8030

There is an issue in a project using the Address Rewrite Service (Email Rewriting) with a single source tenant and multiple target tenants. Messages sent from one of the targets ("Target A") that contain the source address of another target ("Target B"), will not be rewritten.

8050

ERS mailflow jobs do not remove connectors and rules on a tenant when the tenant is removed from the ERS-enabled project.

8098

If a member of the "DayOne" (BT-IntegrationPro-DayONE) email rewrite group is manually mailbox-enabled after the "Prepare" action has been run, rewrites from the target tenant will fail. As a workaround, when you manually mailbox-enable a mailuser, you must also manually move the mailuser's TargetEmailAddress to the mailbox's ForwardingSmtpAddress. If the mailbox's ForwardingSmtpAddress is empty, opt-in sync assumes the mailbox has already been cutover.

8071

Messages sent to a unified group in the source cannot be delivered during the Domain Move process.

8048

When performing a domain move, ensure that AzureADSync has synchronized all proxy addresses to the cloud before restoring the Office365 MX record.

8058

Directory Sync Lite does not remove the source email address if the object does not have a mail or ProxyAddress attribute value.

8100

The source email addresses of Office 365 Groups are not added to the target during a Domain Move.

8119

Free/Busy for Room and Resource meeting requests are displayed as tentative when the request is sent from the target tenant.

8007

Notification emails from Power365 may be delivered to the Junk Mail folder instead of the Inbox.

8019

Due to a limitation of Azure B2B, collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you cannot invite a user as a guest whose account is in a national cloud.

22492

A timeout error is encountered in the Directory Sync Lite installer when attempting to connect to the SQL Server.

8028

When installing French or German versions of Power365 Directory Sync, the installation path, localized SSDT install helpers, and SQL installation screens appear in English.

8031

The Power365 Directory Sync Lite installer cannot install .NET 4.6.1 if the machine is not fully patched and updated.

8084

During cutover process, target contact's LegacyExchangeDN will be added to the target mailbox as a x500 address by Power365 DirSync, Microsoft Azure Connect Sync will need to sync these changes to O365 Tenant in the cloud. However, sometime the x500 address is not being stamped in the cloud object even thought it was synced by Microsoft Azure Connect Sync per Azure Sync log.

8037

Users must run the Outlook/Desktop Setup Pro agent again if the cutover is stopped after the cutover message is sent and Outlook/desktop is already configured.

21819

An issue has been found where the Prepare job for users will fail, in the rare instance that a naming convention is used where the only difference between names is a special character. For example, Special#User and Special$User.

8067

Power365 will not update the msExchRecipientDisplayType,msExchRecipientTypeDetails and msExchRemoteRecipientType attributes if the target mailbox was already provisioned in the cloud directly. Since AADC Sync will not back-sync the changes to AD, the AD local object will not be shown as remote mailbox in the on-prem Exchange environment.

8123

Office 365 Groups created by Power365 cannot have aliases added to them using the Microsoft admin interface. Aliases can be added using PowerShell.

17431

ERS Opt-in Groups will be created in the target On-Prem Exchange Environment if the source group was added to a migration profile that has group sync set to continuous mode.

8035

Cutover email cannot be sent when EWS is set to use an Allow list.

8065

Outlook Setup Pro does not provide an error message when an incorrect password is entered for Outlook 2016 and the profile is created.

8083

Outlook Setup Pro incorrectly displays the profiles from Outlook 2013 if Outlook 2010 is currently installed and Outlook 2013 was previously installed.

19903

When Outlook Setup Pro is run, the cutover job log incorrectly displays the status information for OneDrive for Business and Teams.

223346

The Desktop Setup Pro agent displays "Success" for the status of Teams before the password for the Teams app is validated.

18743

Desktop Setup Pro cannot configure Outlook in Windows 7.

19823

Desktop Setup Pro appears as "OutlookAgent.exe" in Task Manager.

20718

When Desktop Setup Pro is run more than once, the results of additional runs are not recorded in the summary section of the Cutover job log.

21428

The content in the Planner is not migrated to the target when syncing Office 365 Groups.

8105

Email Rewrite Services (ERS) currently does not support Office 365 (Unified) Groups. Attempts to enable Unified Groups will fail.

8606

After Office 365 Group Mailbox migration, email attachments uploaded to the group files have broken links in the target.

8109

Cutover does not copy a Office 365 Group's direct access shares if the trustee is not a member of the group.

19957

DirSync does not enable user objects not created by DirSync.

8022

In a one-to-many migration scenario where the source tenant’s domain is being mapped to two different target domains in two different tenants in the same project, duplicate users will be created if Power365 is configured to create users. To remedy this, target users should be pre-created in the target tenants prior to the migration so source users can be properly matched with the target users. Alternatively, create a separate project for each tenant pair.

8045

The Tenant's Org Name is not updated by Discovery if the name is changed after the project is created.

8021

When a source tenant is removed from a project (by clicking the "X" next to tenant in the project wizard) the user migration records associated with the removed tenant are not removed. This could cause issues if future migration actions are attempted against the orphaned users.

8045

Only some nested groups used for group migration filtering are added during the first discovery pass.

8044

The source Room or Equipment Mailbox Capacity is only copied from the source to the target object during the Prepare action. Any changes to the source mailbox capacity will not be reflected during the migration or if Prepare was successfully completed.

8044

Automatic detection of deleted contacts is no longer support by Microsoft Graph. In order to remediate deleted contacts (for example, during a Domain Move), users will need to run a Reconcile discovery and then mark the un-discovered contacts as deleted or remove them from the database.

8124

Task request and reply messages are synced when the content filter is set to sync only task items.

8113

Auto-Expanding Archives are not supported due to the way that Office 365 spreads the data over multiple mail stores. A workaround to migrating such an archive is to export to PST and import manually via Outlook. More information about this issue can be found at https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784 and https://docs.microsoft.com/en-us/microsoft-365/compliance/enable-unlimited-archiving?view=o365-worldwide

8135

For Email from File project types only, a user’s UPN value must not be changed while the project is being configured via the wizard. Any changes to the UPN value during this process (before the "Submit" button) will cause the user's Exchange attribute to fail to be located.

8049

The SharePoint Admin Role will be added to the Binary Tree PowerShell account created during project setup when the client has the OneDrive license added to their account. This includes when using the Basic Migration Project. However, the Basic Migration Project does not support OneDrive migrations. Use the Advanced Migration or Premium Integration project type to migrate OneDrive.

8111

On Windows 10 Enterprise - Build 1511 and Internet Explorer version 11.589.10586.0, the Add Tenant window fails to close after authentication which prevents the tenant from being listed on the Project Wizard screen.

8005

The Power365 portal requires users to re-authenticate when the browser token expires.

8006

 

 

 

Table 4. Directory Sync known issues

Known Issue

Issue ID

An attempt to install an older version of the agent software will fail if a newer version has already been successfully installed. If, for some reason, the older version is needed, first uninstall the newer version, then remove all registry references to the agent.

8060

The agent installer cannot accept a password with a first character of !.

8122

When discovery discovers an environment, it will read in the OU structure of all domains within the forest. The UI will show all domains and you can select them for use in all workflows. However, if a DC for that domain is not included, or the agent account does not have read access to the objects, they will not be read into the database.

8077

Cloud Only Security Groups are not read in when reading a cloud endpoint.

22453

User thumbnail photos do not sync to cloud environments.

8069

The PowerShell User Group should be added to the Tenant Group Filter as the Group Owner. A security group should not be used.

8070

An account with access to all domains within the forest is needed if you want to sync all domains within a single forest with a single agent. Using an enterprise admin account is the most efficient method for doing this.

8073

Mapping functions do not work with multivalued attributes. For example, (results(proxyaddresses,"x500:") will not return a true even if an X500 address is present.

8075

When a workflow for a cloud environment has been run once, but then has been idle for longer than 30 days, an error will be encountered when the job starts, and the job will fail and loop repeatedly until the retry count has been reached.

8079

Using a federated target domain to sync users and mailboxes cloud to cloud and on-premises to cloud is currently not supported. Syncing groups and contacts is supported.

8082

In the German and Chinese Office365 tenants, Power365 Directory Sync will always do full synchronizations because the delta sync functionality is not available in these local tenants.

8095

An "Object with ID xyz was not found" error may occur when reading recently created Azure guest users due to the longer length of time for guest users to propagate.

8101

Remote Mailboxes from the source are incorrectly created in the target as Users instead of MailUsers.

8102

Delta syncs are limited to 30 days. To avoid full synchronization, a read in should be performed for all cloud environments every 29 days or less.

8108

Password sync does not support AES hashes.

21796

A template configured to sync a binary attribute to a non-binary attribute will not sync correctly. For example, if syncing Binary (ThumbnailPhoto) to String(ExtensionAttribute), the target attribute will be synced as "System.Byte[]" instead of the expected binary value converted into a string.

15683

Domains cannot be discovered if IPV6 is disabled on the host.

27654

A security group cannot be used as a filter group.

8057

When using filter groups for Cloud environments you need to ensure that a group containing any newly created objects is present in the environment filter. This can be accomplished by having a source and target filter group with the same name so they will match and synchronize between the environments. If these objects are not read in after creation, they will not have any additional updates synchronized and they will not be matched.

8076

When synchronizing local AD groups to Office 365 as Office 365 groups (Unified Groups) any contact in the source group will record an error in the logs and the contact will not appear in the target group.

8081

Office 365 Group settings are not copied to the target Office 365 Group.

8104

Likes for Office 365 Group conversations are not migrated.

8122

Custom schema attributes can be added to template mappings but are not visible in the drop-down selection list.

8072

All domains within an Active Directory Forest are visible within an environment when adding a single domain even though the agent account credentials may not have access to all domains.

8074

System requirements

Ensure that your system meets the following minimum platform requirements.

Browser requirements

Table 5. Browser requirements

Requirement

Details

Chrome or Firefox

Power365 is a cloud-based service. We recommend using Chrome or Firefox for the best cloud-based platform experience.

Online Help requirements

Table 6. Online Help requirements

Requirement

Details

Internet Connection

An internet connection is required to access the online help system.

Product licensing

Binary Tree® Power365® is a Software as a Service (SaaS) application where application software is hosted in the cloud and made available to users through power365.quest.com.

Use of this software is governed by the Software Transaction Agreement found at www.quest.com/legal/sta.aspx and the SaaS Addendum at www.quest.com/legal/saas-addendum.aspx.

A valid license is required for Binary Tree Power365.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Different licenses types are consumed during different activities in Binary Tree Power365. To manage licenses, go to Licenses under Manage in the left navigation menu.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

 

The release is localized to the following languages: Chinese (Simplified), French, German, Japanese, Spanish.

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

About this release

Binary Tree® Power365® 20.12.3

Release Notes

June 2021

These release notes provide information about the Binary Tree® Power365® 20.12.3 release.

Topics:

Binary Tree Power365 is a Software-as-a-Service (SaaS) suite that includes the following solutions:

  • Binary Tree Power365 Directory Sync

Binary Tree Power365 Directory Sync can set up and maintain an Active Directory sync, an Azure AD sync, or even a sync between Active Directory and Azure AD. Users in merging organizations can find each other in a unified Global Address List (GAL).

  • Binary Tree Power365 Migration

Binary Tree Power365 Migration lets you migrate mailboxes, archives, and content for Office 365 tenant migrations, for a secure, cloud-based transformation experience. With Binary Tree Power365 Migration, you also have the option to migrate OneDrive, OneNote, and SharePoint content as well as migrate from on-premises or hosted Exchange environments.

  • Binary Tree Power365 Integration

Binary Tree Power365 Integration introduces Day One collaboration capabilities to manage multiple Office 365 tenants by removing communication blockers that create challenges for end-users. This powerful tenant to tenant migration solution enables users in different tenants to share a common address list and view calendar availability while their mail and Office 365 workloads are being migrated.

It includes the capabilities of Binary Tree Power365 Migration and adds the ability to unify tenant address lists and calendar availability lookups as well as migrate Microsoft Teams, Groups and public folders.

  • Binary Tree Power365 Integration Pro

Binary Tree Power365 Integration Pro is a comprehensive solution for Office 365 tenant to tenant migration and integration. It unifies email domains and user collaboration across tenants while you migrate. This enterprise solution enables you to completely move users, workloads, directories and domains between enterprise environments without disrupting business.

Binary Tree Power365 Integration Pro includes all of the functionality of the Binary Tree Power365 Migration and Binary Tree Power365 Integration solutions and adds the ability to unify email addresses across tenants and to move domains without downtime.

  • Binary Tree Power365 for Active Directory

Binary Tree Power365 for Active Directory enables you to migrate Active Directory to accelerate your enterprise M&A and modernization initiatives. Binary Tree Power365 for Active Directory is a solution that integrates and migrates Active Directory, Azure Active Directory, and hybrid directory environments without requiring trusts, SQL, network connectivity, or installing servers.

 

Binary Tree Power365 20.12.3 is a minor release, with no new functionality. See Resolved issues.

Enhancements

The following is a list of enhancements implemented in Binary Tree Power365 20.12.3.

Table 1. General enhancements

Enhancement

Issue ID

Desktop Setup Pro has been updated to allow users to reconfigure their OneDrive for Business application after their source email addresses/usernames have been changed during a big bang domain move.

27140

The DumpStack.log.tmp file has been added to the default ReACL file exclusion list.

27337

The ability to exclude selected files from Device and File Share ReACL processing has been added.  To exclude files from ReACL processing, list the files in the "Exclude These Files From Processing" box in the Device ReACL Profile or File Share ReACL Profile.

27454

Installing the Active Directory Agent on 32-bit workstations is now supported.

27778

Desktop Setup Pro now migrates default signature settings when syncing signatures.

28051

The GetList function can now be used when mapping allowing the merging of multiple values in attributes like showInAddressBook.

28511

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where a Directory Sync profile could be created without a default password due to a user interface timeout has been resolved.

26901

An issue where the GetCred.exe localization instructions were missing has been resolved.

27269

An issue where users that are not sys admins could not skip Domain Cutover step has been resolved.

27473

An issue where Repositories settings could not be modified unless all fields were populated has been resolved.

27590

An issue where Global Variables were not loaded when included in PowerShell scripts has been resolved.

27634

An issue where Directory Sync cannot update users if the source accounts contain commas in the CN and are moved has been resolved.

27797

An issue where Desktop Setup Pro would hang when configuring Teams/OneDrive has been resolved.

27853

An issue where the link to the Cutover conversation history in Teams resulted an error has been resolved.

27860

Support for 21Vianet has been removed.

28132

An issue where conversation history was not migrated during Teams Cutover has been resolved.

28661

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 3. Tenant-to-Tenant known issues

Known Issue

Issue ID

Target MailUsers will be hidden from the GAL during cloud migrations after they have been prepared and until they have been provisioned. A matched target Mailbox will continue to be visible in the GAL after being prepared.

8125

Power365® does not support migration of the following mailbox settings at this time:

  • OWA:

    • Configuration

    • Time Zone

    • Work Hours

    • Signature

    • View Settings

  • Work Hours

  • Out of Office Settings

  • Calendar Configuration

  • Safe/Blocked Senders from Junk Email Rule

  • High Resolution User Photo (Root of the Mailbox)

  • Clutter Opt-In

  • Quick Steps

  • External Calendar Sharing

  • Mailbox Shortcuts to Shared Mailbox folders

7987

The Power365 mail migration engine supports migration of an archive to an archive only. Mailbox to an archive or archive to a mailbox migration is not supported.

7988

The Power365 mail migration engine does not support migration of client-side delegates or delegation for groups.

7989

The Power365 mail migration engine does not support Modern attachments (links to OneDrive files).

 

A duplicate source folder exception occurs when the same folder is copied multiple times as part of multiple migrations.

8002

Power365 only supports Free/Busy lookup when the recipient is being selected from the GAL.

8003

Signed and encrypted messages will not be rewritten by the email rewrite service (ERS).

8004

Additional custom SMTPs added to groups (outside of the email address policy) are not migrated during Group Sync.

8010

When using Directory Sync Lite, nested groups that exist in the target cloud only cannot be synced as group members.

8012

When Power365 creates groups using Directory Sync Lite, the groups will be created in the target on-premises hybrid exchange environment automatically, regardless of the origin of the source group.

8013

Accepted Senders (within Delivery Management) and Moderation settings (in Message Approval) are not migrated by Power365 Group Sync.

8014

MailTips (msExchSenderHintTranslations AD property) are not migrated by Power365 Directory Sync.

8015

Discoverability by Power365 may be delayed for new groups or recent updates to existing groups. This is due to delays in graph returning updated information.

8016

If a "matched" group is manually deleted from the target Exchange forest, the matching status in Power365 is not removed. This may result in errors during the group sync, as Power365 believes the target group already exists.

8017

Source mailbox retention policies and retention tags applied at the folder level are not copied to the target mailbox during mail migration.

8027

Power365 does not support changes to the mail-enabled folder's display name on the target.

8029

Contacts that are linked may not be copied during the mail migration if the PidLidIsContactLinked property is true and the linked ID points to an address hidden from the GAL.

8034

Prepare Job will fail if Power365 Directory Sync finds an existing contact object in the target tenant that is not created by DirSync.

8036

Hidden Public Folders will not be provisioned or migrated.

8039

Messages filtered with Azure Information Rights Management (IRM) will be migrated, but they will not be accessible by the end user. Messages encrypted with Office365 message encryption will be migrated, but they will need to be opened and decrypted via the web browser using the original source mailbox credentials.

8041

Hidden folders are not copied during mailbox migration.

8047

For on-premises migration projects, if a user is renamed in the on-premises environment after the upload has completed, Power365 will be unable to migrate that user. The migration will have to be deleted, and re-uploaded.

8052

If the Discovery Hold (eDiscovery in Office 365) hasn't been enabled, the DiscoveryHold folder will not exist in the Target. DiscoveryHold is a system folder which Power365 does not create. Migration of Litigation Hold settings isn't possible in this scenario.

8054

If there are any items in the purges folder that are within the retention period the item can't be deleted, therefore errors will appear in the logs. The overall status of rollback job will be successful. The purges folder isn't visible to the user. See the below link for information about the retention period settings, which defaults to 14 days.

https://technet.microsoft.com/en-us/library/dn163584(v=exchg.150).aspx

8055

If the Outlook Categories XML configuration file gets corrupted, the categories will not be copied, however the rest of the sync will continue, and will still be marked as completed if no other errors occur.

Workaround: A workaround would be to open Outlook and edit the categories in any way, which would cause the XML file to be rewritten.

8056

EWS access policies are not currently supported in Power365. (8061)

8061

Mail migration cannot be performed on mailboxes that are assigned an Office365 Kiosk License as MAPI connection is disabled for this license type. As a workaround, assign the mailbox an E1 or higher license during the migration, and then revert to the kiosk license.

8062

For on-premises migration projects, any user “Receive-As” permissions are not copied to the target. (Note: “Send-As” permissions ARE copied.)

8063

For on-premises migration projects (“on-premises to cloud”, or “cloud to on-premises”), any source forwarding addresses will not be set on the target.

8064

If the Shared Mailbox has In-Place archive or litigation hold enabled, an Exchange Online Plan 1 or Plan 2 license is required. Therefore, the target mailbox may also require a license. More information from Microsoft can be found here: https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits

8094

The incorrect domain is selected as the default domain for the Public Folder domain mappings. When the default domain is calculated, the initial domain (IsInitial) is set as default instead of the default domain (IsDefault).

8096

Public Folder domain mappings are case-sensitive. The DomainName value in the database can be set to lowercase to work around this issue.

8097

PowerBI reporting is not available outside of the US. (8103)

8103

Due to an Outlook bug, duplicate rules are added to the target when rules are viewed or edited using Outlook. Refer to the Knowledge Base article at https://binarytree.zendesk.com/knowledge/articles/360039534652/en-us?brand_id=360001123812 for information on avoiding this issue.

14613

Mailbox migrations will fail if the PowerShell User and the Archive and User Mailboxes are in different Exchange Online regions.

16982, 16983

Holiday calendars may be duplicated in the target mailbox after migration if the OWA holiday calendar is enabled.

19542

The assigned owner of tasks is not updated with the target username after migration, the owner will remain the source username.

7990

Although address translation in Power365 will work for attached messages in the .MSG format, it does not work for messages in .EML format or calendar attachments in iCal format. Any attached messages in .EML format or appointments in iCal that are migrated will still have the source display name and SMTP address after migration.

7991

If a contact with a birthday or anniversary appointment is migrated, and the birthday or anniversary date is changed, the corresponding appointment on the calendar is not updated and a new appointment will be created with the new birthday or anniversary date and the old appointment is retained.

7992

A Contact linked to a user that is migrated does not migrate with the link.

7993

After migrating a mailbox with conversation history, the "From" and the Subject for the conversation history items are being left as-is with the source user names still visible in the conversation history items.

7995

After the mailbox migration completes, the Skype for Business Meeting URL and Voice Mail Message listed in appointments and meetings will not be translated with target tenant information. The Skype for Business Meeting URL will be invalid once the source tenant is switched off.

7996

Birthday calendar appointments may be duplicated in the target mailbox after migration if the OWA Birthday calendar is enabled.

7997

When a calendar request is migrated, the "Accept" button does not add the calendar to the target user's Outlook/OWA.

8000

When using "Reply All" to a migrated conversation history message the source user's name is added to the recipient list.

7994

Internet calendars are migrated to "My Calendars" instead of "Other Calendars" Any updates to the internet calendars are not received as they are no longer internet calendars on the target.

7998

Not all Internet, Sharepoint, and Shared calendars for all Outlook versions are migrated. Users must manually re-add any calendars they have permissions to after the migration is complete.

7999

Folder permissions are not removed on the target when the permissions are removed on the source and synced again.

8025

Junk mail rules are not copied to the target.

8026

During mailbox sync and cutover, OOF (Out of Office) Rules, Junk Email Rules, Sweep Rules, and any client-side Rules cannot be read in the source tenant or written to the target tenant. Note that most mailbox server-side inbox rules and OOF settings are synchronized.

8734, 8735

The following server-side inbox rules cannot be synced:

  • Action "Pin to Top"(Outlook Web Access only)

  • Action "Apply retention policy"

  • Condition "Classified as"(Outlook Web Access only)

  • Condition "From any RSS feed"

  • Condition "From any RSS feed with xxx in the title"

14616

Migration does not work if an on-premises user has an online archive.

8046

In a hybrid environment with a "Basic" project, Power365 cannot automatically enable the archive for on-premises source users. Upgrade to a Power365 "Advanced Migration" or "Premium Integration" project, or, as a manual workaround, enable each archive manually.

8051

OneDrive for Business content migration will not be successful, unless the user opens OneDrive for Business from the portal.office.com, if the following is true:

  • The target user was prepared and synced with OneDrive for Business enabled.

  • The target tenant administrator deletes the target user and mailbox.

  • The target mailbox was then recreated and provisioned with OneDrive for Business.

8115

When there is a Preservation Policy enabled in the Target tenant One Drive or OneNote syncs will fail.

8126

OneDrive for Business content does not sync when using the Advanced from File project type.

8131

OneDrive for Business migration does not sync the "Restricted View" sharing permission during Cutover.

8120

The OneDrive for Business sync will not start during Cutover if the target user's UPN has changed.

8132

For OneDrive for Business migrations, an error message is not logged when you attempt to migrate a file currently in use.

8088

Full discovery is needed to detect OneDrive for Business changes.

8085

Power365 will discover the user’s OneDrive used storage size and quota based on SharePoint’s current information. The used storage size reflects all used space, including the Recycle Bin. Power365 does not migrate the user’s recycle bin therefore comparing used storage between source and target users does not indicate the success of a user’s OneDrive migration.

8117

OneNote data being edited in the source during a OneDrive for Business migration will log an "item has active edits" error.

8116

During OneNote cutover, if a Notebook is open in the source, edits will not be reflected in the target when cutover completes.

8118

OneNote fails to sync when the source is a Team that was converted from an Office 365 Group and the target is an Office 365 Group.

8130

Microsoft Teams/Office 365 Group OneNote pages are not synced at this time.

17201

OneDrive for Business migration does not set the folder/files containing shareable links to the matched users in the source.

8086

Some Site Permissions Levels such as Full Control, Design and Edit are not fully migrated during the OneDrive for Business Final Cutover Sync Job. The default level assigned to the target during migration is the “Contribute” permission level. Read and Contribute permission levels are migrated successfully to the target.

8087

OneDrive for Business migration does not set permission inheritance flag correctly.

8090

OneDrive for Business quotas are not set or enforced in the source and target.

8091

The OneDrive for Business migration report does not contain permissions that cannot be applied because there is not a matching target user in the target tenant.

8092

The Admin will be listed as last modifying a migrated OneDrive for Business item instead of the actual migrating user.

8089

When enabled, the OneDrive backup feature may duplicate OneDrive known folders (desktop, documents, photos).

16747

OneDrive for Business syncs fail if Legacy Authentication is disabled.

21302

The Admin is removed as an owner in target when Admin is a co-owner of the Office 365 Group in source.

16763

The Get-BTWorkflowLog cmdlet does not support the -Filter parameter.

8136

The Set-BTEnvironment -SkipUserDiscovery PowerShell command can only specify the parameter with numerical values as the boolean value (1=True, 0=False). If a user mistakenly attempts to enter a numerical value such as "16", the setting will get set to True because the "1" will be accepted as the boolean value.

18881

Folder permissions that are removed from the source are not updated on the target when synchronized.

8008

If a Source user is deleted after being discovered, Power365 will not process the deletion. The user will remain in the UI and in the Target if previously prepared. An error is received when a user is deleted on the Source or Target and the migration (Sync) is run again.

8009

An error message is displayed and the subfolder on the target is not deleted when the subfolder on the source is deleted and the migration is run again.

8018

The Public Folder engine will not rewrite source folder email address to target folder email address during content copy.

8038

Power365 does not support public folder sync if the folder name contains a back slash (\).

8020

Public Folder content copying will not start if the Provision job reported an error when mail enablement failed.

8042

If a migrated public folder is renamed after the first synchronization, upon the next sync, the "Folder Renamed" count will be incorrectly incremented again.

8053

During Public Folder migration, the job can be archived when the status is "Syncing".

8023

Security group sync and Security group membership sync are not supported. Permission sync on Public Folders and mail folders will use matched users and mail-enabled security groups, but permissions to members of the mail-enabled security group will not be propagated unless the admin has set up the target security group to have the same members as the source.

8024

If ERS is disabled, the DKIM-Inbound rule is removed. Any custom actions of the DKIM-Inbound rule would need to be set up again if ERS is enabled.

8121

The group owner is displayed as the author of Team conversations entered by a member who has left the team when synced.

8127

Synchronized Team conversations display up to 15 user reactions only.

8128

When an Office 365 Group is converted to a Team or matched to an already existing Team in the target, OneDrive for Business syncs may remove channels from the target Team if they were created directly in the target.

8129

Microsoft Teams migrated conversation history does not display reactions, emoji, and file icons in Internet Explorer.

18304

Team syncs may take longer when creating new Private Channels if delays to access to the channel folders occur.

19000

Due to changes by Microsoft, migration of files for Private Channels is not currently supported.

19571

Microsoft Teams system-generated event messages will not be copied by Power365 during Teams migration because these messages are protected and can only be set by Teams.

28661

The Admin account is removed from the source and target regardless of whether the account was added or it was already an owner. To ensure that removal of temp permissions does not remove any actual owners, connect the source and target tenants using accounts that are not owners of any users, groups, or teams.

14227

The ERS user's SMTP address is not rewritten to the target SMTP address when they send on behalf of a non-ERS user.

8030

There is an issue in a project using the Address Rewrite Service (Email Rewriting) with a single source tenant and multiple target tenants. Messages sent from one of the targets ("Target A") that contain the source address of another target ("Target B"), will not be rewritten.

8050

ERS mailflow jobs do not remove connectors and rules on a tenant when the tenant is removed from the ERS-enabled project.

8098

If a member of the "DayOne" (BT-IntegrationPro-DayONE) email rewrite group is manually mailbox-enabled after the "Prepare" action has been run, rewrites from the target tenant will fail. As a workaround, when you manually mailbox-enable a mailuser, you must also manually move the mailuser's TargetEmailAddress to the mailbox's ForwardingSmtpAddress. If the mailbox's ForwardingSmtpAddress is empty, opt-in sync assumes the mailbox has already been cutover.

8071

Messages sent to a unified group in the source cannot be delivered during the Domain Move process.

8048

When performing a domain move, ensure that AzureADSync has synchronized all proxy addresses to the cloud before restoring the Office365 MX record.

8058

Directory Sync Lite does not remove the source email address if the object does not have a mail or ProxyAddress attribute value.

8100

The source email addresses of Office 365 Groups are not added to the target during a Domain Move.

8119

Free/Busy for Room and Resource meeting requests are displayed as tentative when the request is sent from the target tenant.

8007

Notification emails from Power365 may be delivered to the Junk Mail folder instead of the Inbox.

8019

Due to a limitation of Azure B2B, collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you cannot invite a user as a guest whose account is in a national cloud.

22492

A timeout error is encountered in the Directory Sync Lite installer when attempting to connect to the SQL Server.

8028

When installing French or German versions of Power365 Directory Sync, the installation path, localized SSDT install helpers, and SQL installation screens appear in English.

8031

The Power365 Directory Sync Lite installer cannot install .NET 4.6.1 if the machine is not fully patched and updated.

8084

During cutover process, target contact's LegacyExchangeDN will be added to the target mailbox as a x500 address by Power365 DirSync, Microsoft Azure Connect Sync will need to sync these changes to O365 Tenant in the cloud. However, sometime the x500 address is not being stamped in the cloud object even thought it was synced by Microsoft Azure Connect Sync per Azure Sync log.

8037

Users must run the Outlook/Desktop Setup Pro agent again if the cutover is stopped after the cutover message is sent and Outlook/desktop is already configured.

21819

An issue has been found where the Prepare job for users will fail, in the rare instance that a naming convention is used where the only difference between names is a special character. For example, Special#User and Special$User.

8067

Power365 will not update the msExchRecipientDisplayType,msExchRecipientTypeDetails and msExchRemoteRecipientType attributes if the target mailbox was already provisioned in the cloud directly. Since AADC Sync will not back-sync the changes to AD, the AD local object will not be shown as remote mailbox in the on-prem Exchange environment.

8123

Office 365 Groups created by Power365 cannot have aliases added to them using the Microsoft admin interface. Aliases can be added using PowerShell.

17431

ERS Opt-in Groups will be created in the target On-Prem Exchange Environment if the source group was added to a migration profile that has group sync set to continuous mode.

8035

Cutover email cannot be sent when EWS is set to use an Allow list.

8065

Outlook Setup Pro does not provide an error message when an incorrect password is entered for Outlook 2016 and the profile is created.

8083

Outlook Setup Pro incorrectly displays the profiles from Outlook 2013 if Outlook 2010 is currently installed and Outlook 2013 was previously installed.

19903

When Outlook Setup Pro is run, the cutover job log incorrectly displays the status information for OneDrive for Business and Teams.

223346

The Desktop Setup Pro agent displays "Success" for the status of Teams before the password for the Teams app is validated.

18743

Desktop Setup Pro cannot configure Outlook in Windows 7.

19823

Desktop Setup Pro appears as "OutlookAgent.exe" in Task Manager.

20718

When Desktop Setup Pro is run more than once, the results of additional runs are not recorded in the summary section of the Cutover job log.

21428

The content in the Planner is not migrated to the target when syncing Office 365 Groups.

8105

Email Rewrite Services (ERS) currently does not support Office 365 (Unified) Groups. Attempts to enable Unified Groups will fail.

8606

After Office 365 Group Mailbox migration, email attachments uploaded to the group files have broken links in the target.

8109

Cutover does not copy a Office 365 Group's direct access shares if the trustee is not a member of the group.

19957

DirSync does not enable user objects not created by DirSync.

8022

In a one-to-many migration scenario where the source tenant’s domain is being mapped to two different target domains in two different tenants in the same project, duplicate users will be created if Power365 is configured to create users. To remedy this, target users should be pre-created in the target tenants prior to the migration so source users can be properly matched with the target users. Alternatively, create a separate project for each tenant pair.

8045

The Tenant's Org Name is not updated by Discovery if the name is changed after the project is created.

8021

When a source tenant is removed from a project (by clicking the "X" next to tenant in the project wizard) the user migration records associated with the removed tenant are not removed. This could cause issues if future migration actions are attempted against the orphaned users.

8045

Only some nested groups used for group migration filtering are added during the first discovery pass.

8044

The source Room or Equipment Mailbox Capacity is only copied from the source to the target object during the Prepare action. Any changes to the source mailbox capacity will not be reflected during the migration or if Prepare was successfully completed.

8044

Automatic detection of deleted contacts is no longer support by Microsoft Graph. In order to remediate deleted contacts (for example, during a Domain Move), users will need to run a Reconcile discovery and then mark the un-discovered contacts as deleted or remove them from the database.

8124

Task request and reply messages are synced when the content filter is set to sync only task items.

8113

Auto-Expanding Archives are not supported due to the way that Office 365 spreads the data over multiple mail stores. A workaround to migrating such an archive is to export to PST and import manually via Outlook. More information about this issue can be found at https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784 and https://docs.microsoft.com/en-us/microsoft-365/compliance/enable-unlimited-archiving?view=o365-worldwide

8135

For Email from File project types only, a user’s UPN value must not be changed while the project is being configured via the wizard. Any changes to the UPN value during this process (before the "Submit" button) will cause the user's Exchange attribute to fail to be located.

8049

The SharePoint Admin Role will be added to the Binary Tree PowerShell account created during project setup when the client has the OneDrive license added to their account. This includes when using the Basic Migration Project. However, the Basic Migration Project does not support OneDrive migrations. Use the Advanced Migration or Premium Integration project type to migrate OneDrive.

8111

On Windows 10 Enterprise - Build 1511 and Internet Explorer version 11.589.10586.0, the Add Tenant window fails to close after authentication which prevents the tenant from being listed on the Project Wizard screen.

8005

The Power365 portal requires users to re-authenticate when the browser token expires.

8006

 

 

 

Table 4. Directory Sync known issues

Known Issue

Issue ID

An attempt to install an older version of the agent software will fail if a newer version has already been successfully installed. If, for some reason, the older version is needed, first uninstall the newer version, then remove all registry references to the agent.

8060

The agent installer cannot accept a password with a first character of !.

8122

When discovery discovers an environment, it will read in the OU structure of all domains within the forest. The UI will show all domains and you can select them for use in all workflows. However, if a DC for that domain is not included, or the agent account does not have read access to the objects, they will not be read into the database.

8077

Cloud Only Security Groups are not read in when reading a cloud endpoint.

22453

User thumbnail photos do not sync to cloud environments.

8069

The PowerShell User Group should be added to the Tenant Group Filter as the Group Owner. A security group should not be used.

8070

An account with access to all domains within the forest is needed if you want to sync all domains within a single forest with a single agent. Using an enterprise admin account is the most efficient method for doing this.

8073

Mapping functions do not work with multivalued attributes. For example, (results(proxyaddresses,"x500:") will not return a true even if an X500 address is present.

8075

When a workflow for a cloud environment has been run once, but then has been idle for longer than 30 days, an error will be encountered when the job starts, and the job will fail and loop repeatedly until the retry count has been reached.

8079

Using a federated target domain to sync users and mailboxes cloud to cloud and on-premises to cloud is currently not supported. Syncing groups and contacts is supported.

8082

In the German and Chinese Office365 tenants, Power365 Directory Sync will always do full synchronizations because the delta sync functionality is not available in these local tenants.

8095

An "Object with ID xyz was not found" error may occur when reading recently created Azure guest users due to the longer length of time for guest users to propagate.

8101

Remote Mailboxes from the source are incorrectly created in the target as Users instead of MailUsers.

8102

Delta syncs are limited to 30 days. To avoid full synchronization, a read in should be performed for all cloud environments every 29 days or less.

8108

Password sync does not support AES hashes.

21796

A template configured to sync a binary attribute to a non-binary attribute will not sync correctly. For example, if syncing Binary (ThumbnailPhoto) to String(ExtensionAttribute), the target attribute will be synced as "System.Byte[]" instead of the expected binary value converted into a string.

15683

Domains cannot be discovered if IPV6 is disabled on the host.

27654

A security group cannot be used as a filter group.

8057

When using filter groups for Cloud environments you need to ensure that a group containing any newly created objects is present in the environment filter. This can be accomplished by having a source and target filter group with the same name so they will match and synchronize between the environments. If these objects are not read in after creation, they will not have any additional updates synchronized and they will not be matched.

8076

When synchronizing local AD groups to Office 365 as Office 365 groups (Unified Groups) any contact in the source group will record an error in the logs and the contact will not appear in the target group.

8081

Office 365 Group settings are not copied to the target Office 365 Group.

8104

Likes for Office 365 Group conversations are not migrated.

8122

Custom schema attributes can be added to template mappings but are not visible in the drop-down selection list.

8072

All domains within an Active Directory Forest are visible within an environment when adding a single domain even though the agent account credentials may not have access to all domains.

8074

System requirements

Ensure that your system meets the following minimum platform requirements.

Browser requirements

Table 5. Browser requirements

Requirement

Details

Chrome or Firefox

Power365 is a cloud-based service. We recommend using Chrome or Firefox for the best cloud-based platform experience.

Online Help requirements

Table 6. Online Help requirements

Requirement

Details

Internet Connection

An internet connection is required to access the online help system.

Product licensing

Binary Tree® Power365® is a Software as a Service (SaaS) application where application software is hosted in the cloud and made available to users through power365.quest.com.

Use of this software is governed by the Software Transaction Agreement found at www.quest.com/legal/sta.aspx and the SaaS Addendum at www.quest.com/legal/saas-addendum.aspx.

A valid license is required for Binary Tree Power365.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Different licenses types are consumed during different activities in Binary Tree Power365. To manage licenses, go to Licenses under Manage in the left navigation menu.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

 

The release is localized to the following languages: Chinese (Simplified), French, German, Japanese, Spanish.

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

Enhancements

Binary Tree® Power365® 20.12.3

Release Notes

June 2021

These release notes provide information about the Binary Tree® Power365® 20.12.3 release.

Topics:

About this release

Binary Tree Power365 is a Software-as-a-Service (SaaS) suite that includes the following solutions:

  • Binary Tree Power365 Directory Sync

Binary Tree Power365 Directory Sync can set up and maintain an Active Directory sync, an Azure AD sync, or even a sync between Active Directory and Azure AD. Users in merging organizations can find each other in a unified Global Address List (GAL).

  • Binary Tree Power365 Migration

Binary Tree Power365 Migration lets you migrate mailboxes, archives, and content for Office 365 tenant migrations, for a secure, cloud-based transformation experience. With Binary Tree Power365 Migration, you also have the option to migrate OneDrive, OneNote, and SharePoint content as well as migrate from on-premises or hosted Exchange environments.

  • Binary Tree Power365 Integration

Binary Tree Power365 Integration introduces Day One collaboration capabilities to manage multiple Office 365 tenants by removing communication blockers that create challenges for end-users. This powerful tenant to tenant migration solution enables users in different tenants to share a common address list and view calendar availability while their mail and Office 365 workloads are being migrated.

It includes the capabilities of Binary Tree Power365 Migration and adds the ability to unify tenant address lists and calendar availability lookups as well as migrate Microsoft Teams, Groups and public folders.

  • Binary Tree Power365 Integration Pro

Binary Tree Power365 Integration Pro is a comprehensive solution for Office 365 tenant to tenant migration and integration. It unifies email domains and user collaboration across tenants while you migrate. This enterprise solution enables you to completely move users, workloads, directories and domains between enterprise environments without disrupting business.

Binary Tree Power365 Integration Pro includes all of the functionality of the Binary Tree Power365 Migration and Binary Tree Power365 Integration solutions and adds the ability to unify email addresses across tenants and to move domains without downtime.

  • Binary Tree Power365 for Active Directory

Binary Tree Power365 for Active Directory enables you to migrate Active Directory to accelerate your enterprise M&A and modernization initiatives. Binary Tree Power365 for Active Directory is a solution that integrates and migrates Active Directory, Azure Active Directory, and hybrid directory environments without requiring trusts, SQL, network connectivity, or installing servers.

 

Binary Tree Power365 20.12.3 is a minor release, with no new functionality. See Resolved issues.

The following is a list of enhancements implemented in Binary Tree Power365 20.12.3.

Table 1. General enhancements

Enhancement

Issue ID

Desktop Setup Pro has been updated to allow users to reconfigure their OneDrive for Business application after their source email addresses/usernames have been changed during a big bang domain move.

27140

The DumpStack.log.tmp file has been added to the default ReACL file exclusion list.

27337

The ability to exclude selected files from Device and File Share ReACL processing has been added.  To exclude files from ReACL processing, list the files in the "Exclude These Files From Processing" box in the Device ReACL Profile or File Share ReACL Profile.

27454

Installing the Active Directory Agent on 32-bit workstations is now supported.

27778

Desktop Setup Pro now migrates default signature settings when syncing signatures.

28051

The GetList function can now be used when mapping allowing the merging of multiple values in attributes like showInAddressBook.

28511

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where a Directory Sync profile could be created without a default password due to a user interface timeout has been resolved.

26901

An issue where the GetCred.exe localization instructions were missing has been resolved.

27269

An issue where users that are not sys admins could not skip Domain Cutover step has been resolved.

27473

An issue where Repositories settings could not be modified unless all fields were populated has been resolved.

27590

An issue where Global Variables were not loaded when included in PowerShell scripts has been resolved.

27634

An issue where Directory Sync cannot update users if the source accounts contain commas in the CN and are moved has been resolved.

27797

An issue where Desktop Setup Pro would hang when configuring Teams/OneDrive has been resolved.

27853

An issue where the link to the Cutover conversation history in Teams resulted an error has been resolved.

27860

Support for 21Vianet has been removed.

28132

An issue where conversation history was not migrated during Teams Cutover has been resolved.

28661

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 3. Tenant-to-Tenant known issues

Known Issue

Issue ID

Target MailUsers will be hidden from the GAL during cloud migrations after they have been prepared and until they have been provisioned. A matched target Mailbox will continue to be visible in the GAL after being prepared.

8125

Power365® does not support migration of the following mailbox settings at this time:

  • OWA:

    • Configuration

    • Time Zone

    • Work Hours

    • Signature

    • View Settings

  • Work Hours

  • Out of Office Settings

  • Calendar Configuration

  • Safe/Blocked Senders from Junk Email Rule

  • High Resolution User Photo (Root of the Mailbox)

  • Clutter Opt-In

  • Quick Steps

  • External Calendar Sharing

  • Mailbox Shortcuts to Shared Mailbox folders

7987

The Power365 mail migration engine supports migration of an archive to an archive only. Mailbox to an archive or archive to a mailbox migration is not supported.

7988

The Power365 mail migration engine does not support migration of client-side delegates or delegation for groups.

7989

The Power365 mail migration engine does not support Modern attachments (links to OneDrive files).

 

A duplicate source folder exception occurs when the same folder is copied multiple times as part of multiple migrations.

8002

Power365 only supports Free/Busy lookup when the recipient is being selected from the GAL.

8003

Signed and encrypted messages will not be rewritten by the email rewrite service (ERS).

8004

Additional custom SMTPs added to groups (outside of the email address policy) are not migrated during Group Sync.

8010

When using Directory Sync Lite, nested groups that exist in the target cloud only cannot be synced as group members.

8012

When Power365 creates groups using Directory Sync Lite, the groups will be created in the target on-premises hybrid exchange environment automatically, regardless of the origin of the source group.

8013

Accepted Senders (within Delivery Management) and Moderation settings (in Message Approval) are not migrated by Power365 Group Sync.

8014

MailTips (msExchSenderHintTranslations AD property) are not migrated by Power365 Directory Sync.

8015

Discoverability by Power365 may be delayed for new groups or recent updates to existing groups. This is due to delays in graph returning updated information.

8016

If a "matched" group is manually deleted from the target Exchange forest, the matching status in Power365 is not removed. This may result in errors during the group sync, as Power365 believes the target group already exists.

8017

Source mailbox retention policies and retention tags applied at the folder level are not copied to the target mailbox during mail migration.

8027

Power365 does not support changes to the mail-enabled folder's display name on the target.

8029

Contacts that are linked may not be copied during the mail migration if the PidLidIsContactLinked property is true and the linked ID points to an address hidden from the GAL.

8034

Prepare Job will fail if Power365 Directory Sync finds an existing contact object in the target tenant that is not created by DirSync.

8036

Hidden Public Folders will not be provisioned or migrated.

8039

Messages filtered with Azure Information Rights Management (IRM) will be migrated, but they will not be accessible by the end user. Messages encrypted with Office365 message encryption will be migrated, but they will need to be opened and decrypted via the web browser using the original source mailbox credentials.

8041

Hidden folders are not copied during mailbox migration.

8047

For on-premises migration projects, if a user is renamed in the on-premises environment after the upload has completed, Power365 will be unable to migrate that user. The migration will have to be deleted, and re-uploaded.

8052

If the Discovery Hold (eDiscovery in Office 365) hasn't been enabled, the DiscoveryHold folder will not exist in the Target. DiscoveryHold is a system folder which Power365 does not create. Migration of Litigation Hold settings isn't possible in this scenario.

8054

If there are any items in the purges folder that are within the retention period the item can't be deleted, therefore errors will appear in the logs. The overall status of rollback job will be successful. The purges folder isn't visible to the user. See the below link for information about the retention period settings, which defaults to 14 days.

https://technet.microsoft.com/en-us/library/dn163584(v=exchg.150).aspx

8055

If the Outlook Categories XML configuration file gets corrupted, the categories will not be copied, however the rest of the sync will continue, and will still be marked as completed if no other errors occur.

Workaround: A workaround would be to open Outlook and edit the categories in any way, which would cause the XML file to be rewritten.

8056

EWS access policies are not currently supported in Power365. (8061)

8061

Mail migration cannot be performed on mailboxes that are assigned an Office365 Kiosk License as MAPI connection is disabled for this license type. As a workaround, assign the mailbox an E1 or higher license during the migration, and then revert to the kiosk license.

8062

For on-premises migration projects, any user “Receive-As” permissions are not copied to the target. (Note: “Send-As” permissions ARE copied.)

8063

For on-premises migration projects (“on-premises to cloud”, or “cloud to on-premises”), any source forwarding addresses will not be set on the target.

8064

If the Shared Mailbox has In-Place archive or litigation hold enabled, an Exchange Online Plan 1 or Plan 2 license is required. Therefore, the target mailbox may also require a license. More information from Microsoft can be found here: https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits

8094

The incorrect domain is selected as the default domain for the Public Folder domain mappings. When the default domain is calculated, the initial domain (IsInitial) is set as default instead of the default domain (IsDefault).

8096

Public Folder domain mappings are case-sensitive. The DomainName value in the database can be set to lowercase to work around this issue.

8097

PowerBI reporting is not available outside of the US. (8103)

8103

Due to an Outlook bug, duplicate rules are added to the target when rules are viewed or edited using Outlook. Refer to the Knowledge Base article at https://binarytree.zendesk.com/knowledge/articles/360039534652/en-us?brand_id=360001123812 for information on avoiding this issue.

14613

Mailbox migrations will fail if the PowerShell User and the Archive and User Mailboxes are in different Exchange Online regions.

16982, 16983

Holiday calendars may be duplicated in the target mailbox after migration if the OWA holiday calendar is enabled.

19542

The assigned owner of tasks is not updated with the target username after migration, the owner will remain the source username.

7990

Although address translation in Power365 will work for attached messages in the .MSG format, it does not work for messages in .EML format or calendar attachments in iCal format. Any attached messages in .EML format or appointments in iCal that are migrated will still have the source display name and SMTP address after migration.

7991

If a contact with a birthday or anniversary appointment is migrated, and the birthday or anniversary date is changed, the corresponding appointment on the calendar is not updated and a new appointment will be created with the new birthday or anniversary date and the old appointment is retained.

7992

A Contact linked to a user that is migrated does not migrate with the link.

7993

After migrating a mailbox with conversation history, the "From" and the Subject for the conversation history items are being left as-is with the source user names still visible in the conversation history items.

7995

After the mailbox migration completes, the Skype for Business Meeting URL and Voice Mail Message listed in appointments and meetings will not be translated with target tenant information. The Skype for Business Meeting URL will be invalid once the source tenant is switched off.

7996

Birthday calendar appointments may be duplicated in the target mailbox after migration if the OWA Birthday calendar is enabled.

7997

When a calendar request is migrated, the "Accept" button does not add the calendar to the target user's Outlook/OWA.

8000

When using "Reply All" to a migrated conversation history message the source user's name is added to the recipient list.

7994

Internet calendars are migrated to "My Calendars" instead of "Other Calendars" Any updates to the internet calendars are not received as they are no longer internet calendars on the target.

7998

Not all Internet, Sharepoint, and Shared calendars for all Outlook versions are migrated. Users must manually re-add any calendars they have permissions to after the migration is complete.

7999

Folder permissions are not removed on the target when the permissions are removed on the source and synced again.

8025

Junk mail rules are not copied to the target.

8026

During mailbox sync and cutover, OOF (Out of Office) Rules, Junk Email Rules, Sweep Rules, and any client-side Rules cannot be read in the source tenant or written to the target tenant. Note that most mailbox server-side inbox rules and OOF settings are synchronized.

8734, 8735

The following server-side inbox rules cannot be synced:

  • Action "Pin to Top"(Outlook Web Access only)

  • Action "Apply retention policy"

  • Condition "Classified as"(Outlook Web Access only)

  • Condition "From any RSS feed"

  • Condition "From any RSS feed with xxx in the title"

14616

Migration does not work if an on-premises user has an online archive.

8046

In a hybrid environment with a "Basic" project, Power365 cannot automatically enable the archive for on-premises source users. Upgrade to a Power365 "Advanced Migration" or "Premium Integration" project, or, as a manual workaround, enable each archive manually.

8051

OneDrive for Business content migration will not be successful, unless the user opens OneDrive for Business from the portal.office.com, if the following is true:

  • The target user was prepared and synced with OneDrive for Business enabled.

  • The target tenant administrator deletes the target user and mailbox.

  • The target mailbox was then recreated and provisioned with OneDrive for Business.

8115

When there is a Preservation Policy enabled in the Target tenant One Drive or OneNote syncs will fail.

8126

OneDrive for Business content does not sync when using the Advanced from File project type.

8131

OneDrive for Business migration does not sync the "Restricted View" sharing permission during Cutover.

8120

The OneDrive for Business sync will not start during Cutover if the target user's UPN has changed.

8132

For OneDrive for Business migrations, an error message is not logged when you attempt to migrate a file currently in use.

8088

Full discovery is needed to detect OneDrive for Business changes.

8085

Power365 will discover the user’s OneDrive used storage size and quota based on SharePoint’s current information. The used storage size reflects all used space, including the Recycle Bin. Power365 does not migrate the user’s recycle bin therefore comparing used storage between source and target users does not indicate the success of a user’s OneDrive migration.

8117

OneNote data being edited in the source during a OneDrive for Business migration will log an "item has active edits" error.

8116

During OneNote cutover, if a Notebook is open in the source, edits will not be reflected in the target when cutover completes.

8118

OneNote fails to sync when the source is a Team that was converted from an Office 365 Group and the target is an Office 365 Group.

8130

Microsoft Teams/Office 365 Group OneNote pages are not synced at this time.

17201

OneDrive for Business migration does not set the folder/files containing shareable links to the matched users in the source.

8086

Some Site Permissions Levels such as Full Control, Design and Edit are not fully migrated during the OneDrive for Business Final Cutover Sync Job. The default level assigned to the target during migration is the “Contribute” permission level. Read and Contribute permission levels are migrated successfully to the target.

8087

OneDrive for Business migration does not set permission inheritance flag correctly.

8090

OneDrive for Business quotas are not set or enforced in the source and target.

8091

The OneDrive for Business migration report does not contain permissions that cannot be applied because there is not a matching target user in the target tenant.

8092

The Admin will be listed as last modifying a migrated OneDrive for Business item instead of the actual migrating user.

8089

When enabled, the OneDrive backup feature may duplicate OneDrive known folders (desktop, documents, photos).

16747

OneDrive for Business syncs fail if Legacy Authentication is disabled.

21302

The Admin is removed as an owner in target when Admin is a co-owner of the Office 365 Group in source.

16763

The Get-BTWorkflowLog cmdlet does not support the -Filter parameter.

8136

The Set-BTEnvironment -SkipUserDiscovery PowerShell command can only specify the parameter with numerical values as the boolean value (1=True, 0=False). If a user mistakenly attempts to enter a numerical value such as "16", the setting will get set to True because the "1" will be accepted as the boolean value.

18881

Folder permissions that are removed from the source are not updated on the target when synchronized.

8008

If a Source user is deleted after being discovered, Power365 will not process the deletion. The user will remain in the UI and in the Target if previously prepared. An error is received when a user is deleted on the Source or Target and the migration (Sync) is run again.

8009

An error message is displayed and the subfolder on the target is not deleted when the subfolder on the source is deleted and the migration is run again.

8018

The Public Folder engine will not rewrite source folder email address to target folder email address during content copy.

8038

Power365 does not support public folder sync if the folder name contains a back slash (\).

8020

Public Folder content copying will not start if the Provision job reported an error when mail enablement failed.

8042

If a migrated public folder is renamed after the first synchronization, upon the next sync, the "Folder Renamed" count will be incorrectly incremented again.

8053

During Public Folder migration, the job can be archived when the status is "Syncing".

8023

Security group sync and Security group membership sync are not supported. Permission sync on Public Folders and mail folders will use matched users and mail-enabled security groups, but permissions to members of the mail-enabled security group will not be propagated unless the admin has set up the target security group to have the same members as the source.

8024

If ERS is disabled, the DKIM-Inbound rule is removed. Any custom actions of the DKIM-Inbound rule would need to be set up again if ERS is enabled.

8121

The group owner is displayed as the author of Team conversations entered by a member who has left the team when synced.

8127

Synchronized Team conversations display up to 15 user reactions only.

8128

When an Office 365 Group is converted to a Team or matched to an already existing Team in the target, OneDrive for Business syncs may remove channels from the target Team if they were created directly in the target.

8129

Microsoft Teams migrated conversation history does not display reactions, emoji, and file icons in Internet Explorer.

18304

Team syncs may take longer when creating new Private Channels if delays to access to the channel folders occur.

19000

Due to changes by Microsoft, migration of files for Private Channels is not currently supported.

19571

Microsoft Teams system-generated event messages will not be copied by Power365 during Teams migration because these messages are protected and can only be set by Teams.

28661

The Admin account is removed from the source and target regardless of whether the account was added or it was already an owner. To ensure that removal of temp permissions does not remove any actual owners, connect the source and target tenants using accounts that are not owners of any users, groups, or teams.

14227

The ERS user's SMTP address is not rewritten to the target SMTP address when they send on behalf of a non-ERS user.

8030

There is an issue in a project using the Address Rewrite Service (Email Rewriting) with a single source tenant and multiple target tenants. Messages sent from one of the targets ("Target A") that contain the source address of another target ("Target B"), will not be rewritten.

8050

ERS mailflow jobs do not remove connectors and rules on a tenant when the tenant is removed from the ERS-enabled project.

8098

If a member of the "DayOne" (BT-IntegrationPro-DayONE) email rewrite group is manually mailbox-enabled after the "Prepare" action has been run, rewrites from the target tenant will fail. As a workaround, when you manually mailbox-enable a mailuser, you must also manually move the mailuser's TargetEmailAddress to the mailbox's ForwardingSmtpAddress. If the mailbox's ForwardingSmtpAddress is empty, opt-in sync assumes the mailbox has already been cutover.

8071

Messages sent to a unified group in the source cannot be delivered during the Domain Move process.

8048

When performing a domain move, ensure that AzureADSync has synchronized all proxy addresses to the cloud before restoring the Office365 MX record.

8058

Directory Sync Lite does not remove the source email address if the object does not have a mail or ProxyAddress attribute value.

8100

The source email addresses of Office 365 Groups are not added to the target during a Domain Move.

8119

Free/Busy for Room and Resource meeting requests are displayed as tentative when the request is sent from the target tenant.

8007

Notification emails from Power365 may be delivered to the Junk Mail folder instead of the Inbox.

8019

Due to a limitation of Azure B2B, collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you cannot invite a user as a guest whose account is in a national cloud.

22492

A timeout error is encountered in the Directory Sync Lite installer when attempting to connect to the SQL Server.

8028

When installing French or German versions of Power365 Directory Sync, the installation path, localized SSDT install helpers, and SQL installation screens appear in English.

8031

The Power365 Directory Sync Lite installer cannot install .NET 4.6.1 if the machine is not fully patched and updated.

8084

During cutover process, target contact's LegacyExchangeDN will be added to the target mailbox as a x500 address by Power365 DirSync, Microsoft Azure Connect Sync will need to sync these changes to O365 Tenant in the cloud. However, sometime the x500 address is not being stamped in the cloud object even thought it was synced by Microsoft Azure Connect Sync per Azure Sync log.

8037

Users must run the Outlook/Desktop Setup Pro agent again if the cutover is stopped after the cutover message is sent and Outlook/desktop is already configured.

21819

An issue has been found where the Prepare job for users will fail, in the rare instance that a naming convention is used where the only difference between names is a special character. For example, Special#User and Special$User.

8067

Power365 will not update the msExchRecipientDisplayType,msExchRecipientTypeDetails and msExchRemoteRecipientType attributes if the target mailbox was already provisioned in the cloud directly. Since AADC Sync will not back-sync the changes to AD, the AD local object will not be shown as remote mailbox in the on-prem Exchange environment.

8123

Office 365 Groups created by Power365 cannot have aliases added to them using the Microsoft admin interface. Aliases can be added using PowerShell.

17431

ERS Opt-in Groups will be created in the target On-Prem Exchange Environment if the source group was added to a migration profile that has group sync set to continuous mode.

8035

Cutover email cannot be sent when EWS is set to use an Allow list.

8065

Outlook Setup Pro does not provide an error message when an incorrect password is entered for Outlook 2016 and the profile is created.

8083

Outlook Setup Pro incorrectly displays the profiles from Outlook 2013 if Outlook 2010 is currently installed and Outlook 2013 was previously installed.

19903

When Outlook Setup Pro is run, the cutover job log incorrectly displays the status information for OneDrive for Business and Teams.

223346

The Desktop Setup Pro agent displays "Success" for the status of Teams before the password for the Teams app is validated.

18743

Desktop Setup Pro cannot configure Outlook in Windows 7.

19823

Desktop Setup Pro appears as "OutlookAgent.exe" in Task Manager.

20718

When Desktop Setup Pro is run more than once, the results of additional runs are not recorded in the summary section of the Cutover job log.

21428

The content in the Planner is not migrated to the target when syncing Office 365 Groups.

8105

Email Rewrite Services (ERS) currently does not support Office 365 (Unified) Groups. Attempts to enable Unified Groups will fail.

8606

After Office 365 Group Mailbox migration, email attachments uploaded to the group files have broken links in the target.

8109

Cutover does not copy a Office 365 Group's direct access shares if the trustee is not a member of the group.

19957

DirSync does not enable user objects not created by DirSync.

8022

In a one-to-many migration scenario where the source tenant’s domain is being mapped to two different target domains in two different tenants in the same project, duplicate users will be created if Power365 is configured to create users. To remedy this, target users should be pre-created in the target tenants prior to the migration so source users can be properly matched with the target users. Alternatively, create a separate project for each tenant pair.

8045

The Tenant's Org Name is not updated by Discovery if the name is changed after the project is created.

8021

When a source tenant is removed from a project (by clicking the "X" next to tenant in the project wizard) the user migration records associated with the removed tenant are not removed. This could cause issues if future migration actions are attempted against the orphaned users.

8045

Only some nested groups used for group migration filtering are added during the first discovery pass.

8044

The source Room or Equipment Mailbox Capacity is only copied from the source to the target object during the Prepare action. Any changes to the source mailbox capacity will not be reflected during the migration or if Prepare was successfully completed.

8044

Automatic detection of deleted contacts is no longer support by Microsoft Graph. In order to remediate deleted contacts (for example, during a Domain Move), users will need to run a Reconcile discovery and then mark the un-discovered contacts as deleted or remove them from the database.

8124

Task request and reply messages are synced when the content filter is set to sync only task items.

8113

Auto-Expanding Archives are not supported due to the way that Office 365 spreads the data over multiple mail stores. A workaround to migrating such an archive is to export to PST and import manually via Outlook. More information about this issue can be found at https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784 and https://docs.microsoft.com/en-us/microsoft-365/compliance/enable-unlimited-archiving?view=o365-worldwide

8135

For Email from File project types only, a user’s UPN value must not be changed while the project is being configured via the wizard. Any changes to the UPN value during this process (before the "Submit" button) will cause the user's Exchange attribute to fail to be located.

8049

The SharePoint Admin Role will be added to the Binary Tree PowerShell account created during project setup when the client has the OneDrive license added to their account. This includes when using the Basic Migration Project. However, the Basic Migration Project does not support OneDrive migrations. Use the Advanced Migration or Premium Integration project type to migrate OneDrive.

8111

On Windows 10 Enterprise - Build 1511 and Internet Explorer version 11.589.10586.0, the Add Tenant window fails to close after authentication which prevents the tenant from being listed on the Project Wizard screen.

8005

The Power365 portal requires users to re-authenticate when the browser token expires.

8006

 

 

 

Table 4. Directory Sync known issues

Known Issue

Issue ID

An attempt to install an older version of the agent software will fail if a newer version has already been successfully installed. If, for some reason, the older version is needed, first uninstall the newer version, then remove all registry references to the agent.

8060

The agent installer cannot accept a password with a first character of !.

8122

When discovery discovers an environment, it will read in the OU structure of all domains within the forest. The UI will show all domains and you can select them for use in all workflows. However, if a DC for that domain is not included, or the agent account does not have read access to the objects, they will not be read into the database.

8077

Cloud Only Security Groups are not read in when reading a cloud endpoint.

22453

User thumbnail photos do not sync to cloud environments.

8069

The PowerShell User Group should be added to the Tenant Group Filter as the Group Owner. A security group should not be used.

8070

An account with access to all domains within the forest is needed if you want to sync all domains within a single forest with a single agent. Using an enterprise admin account is the most efficient method for doing this.

8073

Mapping functions do not work with multivalued attributes. For example, (results(proxyaddresses,"x500:") will not return a true even if an X500 address is present.

8075

When a workflow for a cloud environment has been run once, but then has been idle for longer than 30 days, an error will be encountered when the job starts, and the job will fail and loop repeatedly until the retry count has been reached.

8079

Using a federated target domain to sync users and mailboxes cloud to cloud and on-premises to cloud is currently not supported. Syncing groups and contacts is supported.

8082

In the German and Chinese Office365 tenants, Power365 Directory Sync will always do full synchronizations because the delta sync functionality is not available in these local tenants.

8095

An "Object with ID xyz was not found" error may occur when reading recently created Azure guest users due to the longer length of time for guest users to propagate.

8101

Remote Mailboxes from the source are incorrectly created in the target as Users instead of MailUsers.

8102

Delta syncs are limited to 30 days. To avoid full synchronization, a read in should be performed for all cloud environments every 29 days or less.

8108

Password sync does not support AES hashes.

21796

A template configured to sync a binary attribute to a non-binary attribute will not sync correctly. For example, if syncing Binary (ThumbnailPhoto) to String(ExtensionAttribute), the target attribute will be synced as "System.Byte[]" instead of the expected binary value converted into a string.

15683

Domains cannot be discovered if IPV6 is disabled on the host.

27654

A security group cannot be used as a filter group.

8057

When using filter groups for Cloud environments you need to ensure that a group containing any newly created objects is present in the environment filter. This can be accomplished by having a source and target filter group with the same name so they will match and synchronize between the environments. If these objects are not read in after creation, they will not have any additional updates synchronized and they will not be matched.

8076

When synchronizing local AD groups to Office 365 as Office 365 groups (Unified Groups) any contact in the source group will record an error in the logs and the contact will not appear in the target group.

8081

Office 365 Group settings are not copied to the target Office 365 Group.

8104

Likes for Office 365 Group conversations are not migrated.

8122

Custom schema attributes can be added to template mappings but are not visible in the drop-down selection list.

8072

All domains within an Active Directory Forest are visible within an environment when adding a single domain even though the agent account credentials may not have access to all domains.

8074

System requirements

Ensure that your system meets the following minimum platform requirements.

Browser requirements

Table 5. Browser requirements

Requirement

Details

Chrome or Firefox

Power365 is a cloud-based service. We recommend using Chrome or Firefox for the best cloud-based platform experience.

Online Help requirements

Table 6. Online Help requirements

Requirement

Details

Internet Connection

An internet connection is required to access the online help system.

Product licensing

Binary Tree® Power365® is a Software as a Service (SaaS) application where application software is hosted in the cloud and made available to users through power365.quest.com.

Use of this software is governed by the Software Transaction Agreement found at www.quest.com/legal/sta.aspx and the SaaS Addendum at www.quest.com/legal/saas-addendum.aspx.

A valid license is required for Binary Tree Power365.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Different licenses types are consumed during different activities in Binary Tree Power365. To manage licenses, go to Licenses under Manage in the left navigation menu.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

 

The release is localized to the following languages: Chinese (Simplified), French, German, Japanese, Spanish.

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

Resolved issues

Binary Tree® Power365® 20.12.3

Release Notes

June 2021

These release notes provide information about the Binary Tree® Power365® 20.12.3 release.

Topics:

About this release

Binary Tree Power365 is a Software-as-a-Service (SaaS) suite that includes the following solutions:

  • Binary Tree Power365 Directory Sync

Binary Tree Power365 Directory Sync can set up and maintain an Active Directory sync, an Azure AD sync, or even a sync between Active Directory and Azure AD. Users in merging organizations can find each other in a unified Global Address List (GAL).

  • Binary Tree Power365 Migration

Binary Tree Power365 Migration lets you migrate mailboxes, archives, and content for Office 365 tenant migrations, for a secure, cloud-based transformation experience. With Binary Tree Power365 Migration, you also have the option to migrate OneDrive, OneNote, and SharePoint content as well as migrate from on-premises or hosted Exchange environments.

  • Binary Tree Power365 Integration

Binary Tree Power365 Integration introduces Day One collaboration capabilities to manage multiple Office 365 tenants by removing communication blockers that create challenges for end-users. This powerful tenant to tenant migration solution enables users in different tenants to share a common address list and view calendar availability while their mail and Office 365 workloads are being migrated.

It includes the capabilities of Binary Tree Power365 Migration and adds the ability to unify tenant address lists and calendar availability lookups as well as migrate Microsoft Teams, Groups and public folders.

  • Binary Tree Power365 Integration Pro

Binary Tree Power365 Integration Pro is a comprehensive solution for Office 365 tenant to tenant migration and integration. It unifies email domains and user collaboration across tenants while you migrate. This enterprise solution enables you to completely move users, workloads, directories and domains between enterprise environments without disrupting business.

Binary Tree Power365 Integration Pro includes all of the functionality of the Binary Tree Power365 Migration and Binary Tree Power365 Integration solutions and adds the ability to unify email addresses across tenants and to move domains without downtime.

  • Binary Tree Power365 for Active Directory

Binary Tree Power365 for Active Directory enables you to migrate Active Directory to accelerate your enterprise M&A and modernization initiatives. Binary Tree Power365 for Active Directory is a solution that integrates and migrates Active Directory, Azure Active Directory, and hybrid directory environments without requiring trusts, SQL, network connectivity, or installing servers.

 

Binary Tree Power365 20.12.3 is a minor release, with no new functionality. See Resolved issues.

Enhancements

The following is a list of enhancements implemented in Binary Tree Power365 20.12.3.

Table 1. General enhancements

Enhancement

Issue ID

Desktop Setup Pro has been updated to allow users to reconfigure their OneDrive for Business application after their source email addresses/usernames have been changed during a big bang domain move.

27140

The DumpStack.log.tmp file has been added to the default ReACL file exclusion list.

27337

The ability to exclude selected files from Device and File Share ReACL processing has been added.  To exclude files from ReACL processing, list the files in the "Exclude These Files From Processing" box in the Device ReACL Profile or File Share ReACL Profile.

27454

Installing the Active Directory Agent on 32-bit workstations is now supported.

27778

Desktop Setup Pro now migrates default signature settings when syncing signatures.

28051

The GetList function can now be used when mapping allowing the merging of multiple values in attributes like showInAddressBook.

28511

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where a Directory Sync profile could be created without a default password due to a user interface timeout has been resolved.

26901

An issue where the GetCred.exe localization instructions were missing has been resolved.

27269

An issue where users that are not sys admins could not skip Domain Cutover step has been resolved.

27473

An issue where Repositories settings could not be modified unless all fields were populated has been resolved.

27590

An issue where Global Variables were not loaded when included in PowerShell scripts has been resolved.

27634

An issue where Directory Sync cannot update users if the source accounts contain commas in the CN and are moved has been resolved.

27797

An issue where Desktop Setup Pro would hang when configuring Teams/OneDrive has been resolved.

27853

An issue where the link to the Cutover conversation history in Teams resulted an error has been resolved.

27860

Support for 21Vianet has been removed.

28132

An issue where conversation history was not migrated during Teams Cutover has been resolved.

28661

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 3. Tenant-to-Tenant known issues

Known Issue

Issue ID

Target MailUsers will be hidden from the GAL during cloud migrations after they have been prepared and until they have been provisioned. A matched target Mailbox will continue to be visible in the GAL after being prepared.

8125

Power365® does not support migration of the following mailbox settings at this time:

  • OWA:

    • Configuration

    • Time Zone

    • Work Hours

    • Signature

    • View Settings

  • Work Hours

  • Out of Office Settings

  • Calendar Configuration

  • Safe/Blocked Senders from Junk Email Rule

  • High Resolution User Photo (Root of the Mailbox)

  • Clutter Opt-In

  • Quick Steps

  • External Calendar Sharing

  • Mailbox Shortcuts to Shared Mailbox folders

7987

The Power365 mail migration engine supports migration of an archive to an archive only. Mailbox to an archive or archive to a mailbox migration is not supported.

7988

The Power365 mail migration engine does not support migration of client-side delegates or delegation for groups.

7989

The Power365 mail migration engine does not support Modern attachments (links to OneDrive files).

 

A duplicate source folder exception occurs when the same folder is copied multiple times as part of multiple migrations.

8002

Power365 only supports Free/Busy lookup when the recipient is being selected from the GAL.

8003

Signed and encrypted messages will not be rewritten by the email rewrite service (ERS).

8004

Additional custom SMTPs added to groups (outside of the email address policy) are not migrated during Group Sync.

8010

When using Directory Sync Lite, nested groups that exist in the target cloud only cannot be synced as group members.

8012

When Power365 creates groups using Directory Sync Lite, the groups will be created in the target on-premises hybrid exchange environment automatically, regardless of the origin of the source group.

8013

Accepted Senders (within Delivery Management) and Moderation settings (in Message Approval) are not migrated by Power365 Group Sync.

8014

MailTips (msExchSenderHintTranslations AD property) are not migrated by Power365 Directory Sync.

8015

Discoverability by Power365 may be delayed for new groups or recent updates to existing groups. This is due to delays in graph returning updated information.

8016

If a "matched" group is manually deleted from the target Exchange forest, the matching status in Power365 is not removed. This may result in errors during the group sync, as Power365 believes the target group already exists.

8017

Source mailbox retention policies and retention tags applied at the folder level are not copied to the target mailbox during mail migration.

8027

Power365 does not support changes to the mail-enabled folder's display name on the target.

8029

Contacts that are linked may not be copied during the mail migration if the PidLidIsContactLinked property is true and the linked ID points to an address hidden from the GAL.

8034

Prepare Job will fail if Power365 Directory Sync finds an existing contact object in the target tenant that is not created by DirSync.

8036

Hidden Public Folders will not be provisioned or migrated.

8039

Messages filtered with Azure Information Rights Management (IRM) will be migrated, but they will not be accessible by the end user. Messages encrypted with Office365 message encryption will be migrated, but they will need to be opened and decrypted via the web browser using the original source mailbox credentials.

8041

Hidden folders are not copied during mailbox migration.

8047

For on-premises migration projects, if a user is renamed in the on-premises environment after the upload has completed, Power365 will be unable to migrate that user. The migration will have to be deleted, and re-uploaded.

8052

If the Discovery Hold (eDiscovery in Office 365) hasn't been enabled, the DiscoveryHold folder will not exist in the Target. DiscoveryHold is a system folder which Power365 does not create. Migration of Litigation Hold settings isn't possible in this scenario.

8054

If there are any items in the purges folder that are within the retention period the item can't be deleted, therefore errors will appear in the logs. The overall status of rollback job will be successful. The purges folder isn't visible to the user. See the below link for information about the retention period settings, which defaults to 14 days.

https://technet.microsoft.com/en-us/library/dn163584(v=exchg.150).aspx

8055

If the Outlook Categories XML configuration file gets corrupted, the categories will not be copied, however the rest of the sync will continue, and will still be marked as completed if no other errors occur.

Workaround: A workaround would be to open Outlook and edit the categories in any way, which would cause the XML file to be rewritten.

8056

EWS access policies are not currently supported in Power365. (8061)

8061

Mail migration cannot be performed on mailboxes that are assigned an Office365 Kiosk License as MAPI connection is disabled for this license type. As a workaround, assign the mailbox an E1 or higher license during the migration, and then revert to the kiosk license.

8062

For on-premises migration projects, any user “Receive-As” permissions are not copied to the target. (Note: “Send-As” permissions ARE copied.)

8063

For on-premises migration projects (“on-premises to cloud”, or “cloud to on-premises”), any source forwarding addresses will not be set on the target.

8064

If the Shared Mailbox has In-Place archive or litigation hold enabled, an Exchange Online Plan 1 or Plan 2 license is required. Therefore, the target mailbox may also require a license. More information from Microsoft can be found here: https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits

8094

The incorrect domain is selected as the default domain for the Public Folder domain mappings. When the default domain is calculated, the initial domain (IsInitial) is set as default instead of the default domain (IsDefault).

8096

Public Folder domain mappings are case-sensitive. The DomainName value in the database can be set to lowercase to work around this issue.

8097

PowerBI reporting is not available outside of the US. (8103)

8103

Due to an Outlook bug, duplicate rules are added to the target when rules are viewed or edited using Outlook. Refer to the Knowledge Base article at https://binarytree.zendesk.com/knowledge/articles/360039534652/en-us?brand_id=360001123812 for information on avoiding this issue.

14613

Mailbox migrations will fail if the PowerShell User and the Archive and User Mailboxes are in different Exchange Online regions.

16982, 16983

Holiday calendars may be duplicated in the target mailbox after migration if the OWA holiday calendar is enabled.

19542

The assigned owner of tasks is not updated with the target username after migration, the owner will remain the source username.

7990

Although address translation in Power365 will work for attached messages in the .MSG format, it does not work for messages in .EML format or calendar attachments in iCal format. Any attached messages in .EML format or appointments in iCal that are migrated will still have the source display name and SMTP address after migration.

7991

If a contact with a birthday or anniversary appointment is migrated, and the birthday or anniversary date is changed, the corresponding appointment on the calendar is not updated and a new appointment will be created with the new birthday or anniversary date and the old appointment is retained.

7992

A Contact linked to a user that is migrated does not migrate with the link.

7993

After migrating a mailbox with conversation history, the "From" and the Subject for the conversation history items are being left as-is with the source user names still visible in the conversation history items.

7995

After the mailbox migration completes, the Skype for Business Meeting URL and Voice Mail Message listed in appointments and meetings will not be translated with target tenant information. The Skype for Business Meeting URL will be invalid once the source tenant is switched off.

7996

Birthday calendar appointments may be duplicated in the target mailbox after migration if the OWA Birthday calendar is enabled.

7997

When a calendar request is migrated, the "Accept" button does not add the calendar to the target user's Outlook/OWA.

8000

When using "Reply All" to a migrated conversation history message the source user's name is added to the recipient list.

7994

Internet calendars are migrated to "My Calendars" instead of "Other Calendars" Any updates to the internet calendars are not received as they are no longer internet calendars on the target.

7998

Not all Internet, Sharepoint, and Shared calendars for all Outlook versions are migrated. Users must manually re-add any calendars they have permissions to after the migration is complete.

7999

Folder permissions are not removed on the target when the permissions are removed on the source and synced again.

8025

Junk mail rules are not copied to the target.

8026

During mailbox sync and cutover, OOF (Out of Office) Rules, Junk Email Rules, Sweep Rules, and any client-side Rules cannot be read in the source tenant or written to the target tenant. Note that most mailbox server-side inbox rules and OOF settings are synchronized.

8734, 8735

The following server-side inbox rules cannot be synced:

  • Action "Pin to Top"(Outlook Web Access only)

  • Action "Apply retention policy"

  • Condition "Classified as"(Outlook Web Access only)

  • Condition "From any RSS feed"

  • Condition "From any RSS feed with xxx in the title"

14616

Migration does not work if an on-premises user has an online archive.

8046

In a hybrid environment with a "Basic" project, Power365 cannot automatically enable the archive for on-premises source users. Upgrade to a Power365 "Advanced Migration" or "Premium Integration" project, or, as a manual workaround, enable each archive manually.

8051

OneDrive for Business content migration will not be successful, unless the user opens OneDrive for Business from the portal.office.com, if the following is true:

  • The target user was prepared and synced with OneDrive for Business enabled.

  • The target tenant administrator deletes the target user and mailbox.

  • The target mailbox was then recreated and provisioned with OneDrive for Business.

8115

When there is a Preservation Policy enabled in the Target tenant One Drive or OneNote syncs will fail.

8126

OneDrive for Business content does not sync when using the Advanced from File project type.

8131

OneDrive for Business migration does not sync the "Restricted View" sharing permission during Cutover.

8120

The OneDrive for Business sync will not start during Cutover if the target user's UPN has changed.

8132

For OneDrive for Business migrations, an error message is not logged when you attempt to migrate a file currently in use.

8088

Full discovery is needed to detect OneDrive for Business changes.

8085

Power365 will discover the user’s OneDrive used storage size and quota based on SharePoint’s current information. The used storage size reflects all used space, including the Recycle Bin. Power365 does not migrate the user’s recycle bin therefore comparing used storage between source and target users does not indicate the success of a user’s OneDrive migration.

8117

OneNote data being edited in the source during a OneDrive for Business migration will log an "item has active edits" error.

8116

During OneNote cutover, if a Notebook is open in the source, edits will not be reflected in the target when cutover completes.

8118

OneNote fails to sync when the source is a Team that was converted from an Office 365 Group and the target is an Office 365 Group.

8130

Microsoft Teams/Office 365 Group OneNote pages are not synced at this time.

17201

OneDrive for Business migration does not set the folder/files containing shareable links to the matched users in the source.

8086

Some Site Permissions Levels such as Full Control, Design and Edit are not fully migrated during the OneDrive for Business Final Cutover Sync Job. The default level assigned to the target during migration is the “Contribute” permission level. Read and Contribute permission levels are migrated successfully to the target.

8087

OneDrive for Business migration does not set permission inheritance flag correctly.

8090

OneDrive for Business quotas are not set or enforced in the source and target.

8091

The OneDrive for Business migration report does not contain permissions that cannot be applied because there is not a matching target user in the target tenant.

8092

The Admin will be listed as last modifying a migrated OneDrive for Business item instead of the actual migrating user.

8089

When enabled, the OneDrive backup feature may duplicate OneDrive known folders (desktop, documents, photos).

16747

OneDrive for Business syncs fail if Legacy Authentication is disabled.

21302

The Admin is removed as an owner in target when Admin is a co-owner of the Office 365 Group in source.

16763

The Get-BTWorkflowLog cmdlet does not support the -Filter parameter.

8136

The Set-BTEnvironment -SkipUserDiscovery PowerShell command can only specify the parameter with numerical values as the boolean value (1=True, 0=False). If a user mistakenly attempts to enter a numerical value such as "16", the setting will get set to True because the "1" will be accepted as the boolean value.

18881

Folder permissions that are removed from the source are not updated on the target when synchronized.

8008

If a Source user is deleted after being discovered, Power365 will not process the deletion. The user will remain in the UI and in the Target if previously prepared. An error is received when a user is deleted on the Source or Target and the migration (Sync) is run again.

8009

An error message is displayed and the subfolder on the target is not deleted when the subfolder on the source is deleted and the migration is run again.

8018

The Public Folder engine will not rewrite source folder email address to target folder email address during content copy.

8038

Power365 does not support public folder sync if the folder name contains a back slash (\).

8020

Public Folder content copying will not start if the Provision job reported an error when mail enablement failed.

8042

If a migrated public folder is renamed after the first synchronization, upon the next sync, the "Folder Renamed" count will be incorrectly incremented again.

8053

During Public Folder migration, the job can be archived when the status is "Syncing".

8023

Security group sync and Security group membership sync are not supported. Permission sync on Public Folders and mail folders will use matched users and mail-enabled security groups, but permissions to members of the mail-enabled security group will not be propagated unless the admin has set up the target security group to have the same members as the source.

8024

If ERS is disabled, the DKIM-Inbound rule is removed. Any custom actions of the DKIM-Inbound rule would need to be set up again if ERS is enabled.

8121

The group owner is displayed as the author of Team conversations entered by a member who has left the team when synced.

8127

Synchronized Team conversations display up to 15 user reactions only.

8128

When an Office 365 Group is converted to a Team or matched to an already existing Team in the target, OneDrive for Business syncs may remove channels from the target Team if they were created directly in the target.

8129

Microsoft Teams migrated conversation history does not display reactions, emoji, and file icons in Internet Explorer.

18304

Team syncs may take longer when creating new Private Channels if delays to access to the channel folders occur.

19000

Due to changes by Microsoft, migration of files for Private Channels is not currently supported.

19571

Microsoft Teams system-generated event messages will not be copied by Power365 during Teams migration because these messages are protected and can only be set by Teams.

28661

The Admin account is removed from the source and target regardless of whether the account was added or it was already an owner. To ensure that removal of temp permissions does not remove any actual owners, connect the source and target tenants using accounts that are not owners of any users, groups, or teams.

14227

The ERS user's SMTP address is not rewritten to the target SMTP address when they send on behalf of a non-ERS user.

8030

There is an issue in a project using the Address Rewrite Service (Email Rewriting) with a single source tenant and multiple target tenants. Messages sent from one of the targets ("Target A") that contain the source address of another target ("Target B"), will not be rewritten.

8050

ERS mailflow jobs do not remove connectors and rules on a tenant when the tenant is removed from the ERS-enabled project.

8098

If a member of the "DayOne" (BT-IntegrationPro-DayONE) email rewrite group is manually mailbox-enabled after the "Prepare" action has been run, rewrites from the target tenant will fail. As a workaround, when you manually mailbox-enable a mailuser, you must also manually move the mailuser's TargetEmailAddress to the mailbox's ForwardingSmtpAddress. If the mailbox's ForwardingSmtpAddress is empty, opt-in sync assumes the mailbox has already been cutover.

8071

Messages sent to a unified group in the source cannot be delivered during the Domain Move process.

8048

When performing a domain move, ensure that AzureADSync has synchronized all proxy addresses to the cloud before restoring the Office365 MX record.

8058

Directory Sync Lite does not remove the source email address if the object does not have a mail or ProxyAddress attribute value.

8100

The source email addresses of Office 365 Groups are not added to the target during a Domain Move.

8119

Free/Busy for Room and Resource meeting requests are displayed as tentative when the request is sent from the target tenant.

8007

Notification emails from Power365 may be delivered to the Junk Mail folder instead of the Inbox.

8019

Due to a limitation of Azure B2B, collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you cannot invite a user as a guest whose account is in a national cloud.

22492

A timeout error is encountered in the Directory Sync Lite installer when attempting to connect to the SQL Server.

8028

When installing French or German versions of Power365 Directory Sync, the installation path, localized SSDT install helpers, and SQL installation screens appear in English.

8031

The Power365 Directory Sync Lite installer cannot install .NET 4.6.1 if the machine is not fully patched and updated.

8084

During cutover process, target contact's LegacyExchangeDN will be added to the target mailbox as a x500 address by Power365 DirSync, Microsoft Azure Connect Sync will need to sync these changes to O365 Tenant in the cloud. However, sometime the x500 address is not being stamped in the cloud object even thought it was synced by Microsoft Azure Connect Sync per Azure Sync log.

8037

Users must run the Outlook/Desktop Setup Pro agent again if the cutover is stopped after the cutover message is sent and Outlook/desktop is already configured.

21819

An issue has been found where the Prepare job for users will fail, in the rare instance that a naming convention is used where the only difference between names is a special character. For example, Special#User and Special$User.

8067

Power365 will not update the msExchRecipientDisplayType,msExchRecipientTypeDetails and msExchRemoteRecipientType attributes if the target mailbox was already provisioned in the cloud directly. Since AADC Sync will not back-sync the changes to AD, the AD local object will not be shown as remote mailbox in the on-prem Exchange environment.

8123

Office 365 Groups created by Power365 cannot have aliases added to them using the Microsoft admin interface. Aliases can be added using PowerShell.

17431

ERS Opt-in Groups will be created in the target On-Prem Exchange Environment if the source group was added to a migration profile that has group sync set to continuous mode.

8035

Cutover email cannot be sent when EWS is set to use an Allow list.

8065

Outlook Setup Pro does not provide an error message when an incorrect password is entered for Outlook 2016 and the profile is created.

8083

Outlook Setup Pro incorrectly displays the profiles from Outlook 2013 if Outlook 2010 is currently installed and Outlook 2013 was previously installed.

19903

When Outlook Setup Pro is run, the cutover job log incorrectly displays the status information for OneDrive for Business and Teams.

223346

The Desktop Setup Pro agent displays "Success" for the status of Teams before the password for the Teams app is validated.

18743

Desktop Setup Pro cannot configure Outlook in Windows 7.

19823

Desktop Setup Pro appears as "OutlookAgent.exe" in Task Manager.

20718

When Desktop Setup Pro is run more than once, the results of additional runs are not recorded in the summary section of the Cutover job log.

21428

The content in the Planner is not migrated to the target when syncing Office 365 Groups.

8105

Email Rewrite Services (ERS) currently does not support Office 365 (Unified) Groups. Attempts to enable Unified Groups will fail.

8606

After Office 365 Group Mailbox migration, email attachments uploaded to the group files have broken links in the target.

8109

Cutover does not copy a Office 365 Group's direct access shares if the trustee is not a member of the group.

19957

DirSync does not enable user objects not created by DirSync.

8022

In a one-to-many migration scenario where the source tenant’s domain is being mapped to two different target domains in two different tenants in the same project, duplicate users will be created if Power365 is configured to create users. To remedy this, target users should be pre-created in the target tenants prior to the migration so source users can be properly matched with the target users. Alternatively, create a separate project for each tenant pair.

8045

The Tenant's Org Name is not updated by Discovery if the name is changed after the project is created.

8021

When a source tenant is removed from a project (by clicking the "X" next to tenant in the project wizard) the user migration records associated with the removed tenant are not removed. This could cause issues if future migration actions are attempted against the orphaned users.

8045

Only some nested groups used for group migration filtering are added during the first discovery pass.

8044

The source Room or Equipment Mailbox Capacity is only copied from the source to the target object during the Prepare action. Any changes to the source mailbox capacity will not be reflected during the migration or if Prepare was successfully completed.

8044

Automatic detection of deleted contacts is no longer support by Microsoft Graph. In order to remediate deleted contacts (for example, during a Domain Move), users will need to run a Reconcile discovery and then mark the un-discovered contacts as deleted or remove them from the database.

8124

Task request and reply messages are synced when the content filter is set to sync only task items.

8113

Auto-Expanding Archives are not supported due to the way that Office 365 spreads the data over multiple mail stores. A workaround to migrating such an archive is to export to PST and import manually via Outlook. More information about this issue can be found at https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784 and https://docs.microsoft.com/en-us/microsoft-365/compliance/enable-unlimited-archiving?view=o365-worldwide

8135

For Email from File project types only, a user’s UPN value must not be changed while the project is being configured via the wizard. Any changes to the UPN value during this process (before the "Submit" button) will cause the user's Exchange attribute to fail to be located.

8049

The SharePoint Admin Role will be added to the Binary Tree PowerShell account created during project setup when the client has the OneDrive license added to their account. This includes when using the Basic Migration Project. However, the Basic Migration Project does not support OneDrive migrations. Use the Advanced Migration or Premium Integration project type to migrate OneDrive.

8111

On Windows 10 Enterprise - Build 1511 and Internet Explorer version 11.589.10586.0, the Add Tenant window fails to close after authentication which prevents the tenant from being listed on the Project Wizard screen.

8005

The Power365 portal requires users to re-authenticate when the browser token expires.

8006

 

 

 

Table 4. Directory Sync known issues

Known Issue

Issue ID

An attempt to install an older version of the agent software will fail if a newer version has already been successfully installed. If, for some reason, the older version is needed, first uninstall the newer version, then remove all registry references to the agent.

8060

The agent installer cannot accept a password with a first character of !.

8122

When discovery discovers an environment, it will read in the OU structure of all domains within the forest. The UI will show all domains and you can select them for use in all workflows. However, if a DC for that domain is not included, or the agent account does not have read access to the objects, they will not be read into the database.

8077

Cloud Only Security Groups are not read in when reading a cloud endpoint.

22453

User thumbnail photos do not sync to cloud environments.

8069

The PowerShell User Group should be added to the Tenant Group Filter as the Group Owner. A security group should not be used.

8070

An account with access to all domains within the forest is needed if you want to sync all domains within a single forest with a single agent. Using an enterprise admin account is the most efficient method for doing this.

8073

Mapping functions do not work with multivalued attributes. For example, (results(proxyaddresses,"x500:") will not return a true even if an X500 address is present.

8075

When a workflow for a cloud environment has been run once, but then has been idle for longer than 30 days, an error will be encountered when the job starts, and the job will fail and loop repeatedly until the retry count has been reached.

8079

Using a federated target domain to sync users and mailboxes cloud to cloud and on-premises to cloud is currently not supported. Syncing groups and contacts is supported.

8082

In the German and Chinese Office365 tenants, Power365 Directory Sync will always do full synchronizations because the delta sync functionality is not available in these local tenants.

8095

An "Object with ID xyz was not found" error may occur when reading recently created Azure guest users due to the longer length of time for guest users to propagate.

8101

Remote Mailboxes from the source are incorrectly created in the target as Users instead of MailUsers.

8102

Delta syncs are limited to 30 days. To avoid full synchronization, a read in should be performed for all cloud environments every 29 days or less.

8108

Password sync does not support AES hashes.

21796

A template configured to sync a binary attribute to a non-binary attribute will not sync correctly. For example, if syncing Binary (ThumbnailPhoto) to String(ExtensionAttribute), the target attribute will be synced as "System.Byte[]" instead of the expected binary value converted into a string.

15683

Domains cannot be discovered if IPV6 is disabled on the host.

27654

A security group cannot be used as a filter group.

8057

When using filter groups for Cloud environments you need to ensure that a group containing any newly created objects is present in the environment filter. This can be accomplished by having a source and target filter group with the same name so they will match and synchronize between the environments. If these objects are not read in after creation, they will not have any additional updates synchronized and they will not be matched.

8076

When synchronizing local AD groups to Office 365 as Office 365 groups (Unified Groups) any contact in the source group will record an error in the logs and the contact will not appear in the target group.

8081

Office 365 Group settings are not copied to the target Office 365 Group.

8104

Likes for Office 365 Group conversations are not migrated.

8122

Custom schema attributes can be added to template mappings but are not visible in the drop-down selection list.

8072

All domains within an Active Directory Forest are visible within an environment when adding a single domain even though the agent account credentials may not have access to all domains.

8074

System requirements

Ensure that your system meets the following minimum platform requirements.

Browser requirements

Table 5. Browser requirements

Requirement

Details

Chrome or Firefox

Power365 is a cloud-based service. We recommend using Chrome or Firefox for the best cloud-based platform experience.

Online Help requirements

Table 6. Online Help requirements

Requirement

Details

Internet Connection

An internet connection is required to access the online help system.

Product licensing

Binary Tree® Power365® is a Software as a Service (SaaS) application where application software is hosted in the cloud and made available to users through power365.quest.com.

Use of this software is governed by the Software Transaction Agreement found at www.quest.com/legal/sta.aspx and the SaaS Addendum at www.quest.com/legal/saas-addendum.aspx.

A valid license is required for Binary Tree Power365.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Different licenses types are consumed during different activities in Binary Tree Power365. To manage licenses, go to Licenses under Manage in the left navigation menu.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

 

The release is localized to the following languages: Chinese (Simplified), French, German, Japanese, Spanish.

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating