Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Quick Start Guide

To divide permissions between two accounts

One account is configured for access to Active Directory containers and objects, corresponding to Migrator for GroupWise’s AD Information screens. This account must be a domain user account with full access to the target OU. If the contacts will be merged with existing Active Directory user objects, the account must have full control of the OUs/containers where the AD user objects currently reside. This ensures Migrator for GroupWise has sufficient access to properly join to the merged user objects, and prevents the creation of duplicate contacts.

To Set AD Container Permissions in Exchange 2016, 2013, 2010 or Office 365:

... where <UserAcct> is the admin’s SecurityPrincipalIdParameter.

The other account is configured to provide Exchange credentials from Migrator for GroupWise, corresponding to Migrator for GroupWise’s Exchange Information screens, and must be configured with Receive As rights to each mailbox store. To set Receive As rights In Exchange 2016, 2013 or 2010, for all mail stores:

get-mailboxdatabase | add-adpermission -user <username> -extendedrights receive-as
Also, for Exchange 2016, 2013 or 2010: This admin account must be configured with remote PowerShell enabled, by this Exchange Shell command:
Set-User <alias> -remotepowershellenabled $true
... where <alias> is the AD account to which you are granting access.

To combine all necessary permissions in a single account

Remember: This option applies only when migrating to a proprietary Exchange.

The single account will be used to login to the migration workstation and provide the Exchange server credentials and AD credentials as needed. In Active Directory, configure user access to AD containers and data by delegating permissions at the OU level:

1
If you don't already have a mailbox-enabled account for this purpose: Create a new AD user in any OU, and Create an Exchange mailbox housed on a target Exchange server (where user data will be migrated) for the user.
2
Use AD's Delegation of Control Wizard to delegate permissions for each OU that Migrator for GroupWise will touch:
a
On the Users or Groups screen: Add the user, and click Next.
b
On the Tasks to Delegate screen: Click Create a custom task to delegate, and click Next.
c
On the AD Object Type screen: Select the radio button Only the following objects in the folder. Then select (mark checkboxes) Contact objects, Group objects, and User Objects. Finally, mark the checkboxes for both Create selected objects in this folder and Delete selected objects in this folder, and click Next.
d
On the Permissions screen: Mark the General checkbox, and then mark the checkboxes for Read, Write and Write All Properties.
IMPORTANT: Do not establish OU access by simply adding the user to the Domain Admins group. It may seem like an easier method to achieve the same results, but Domain Admins explicitly denies the Receive As right, which is also required (see next step below) for this single-account approach.
3
On each Exchange mailbox store to which the users are migrating, the account must be added to the security access control list with at least Receive As rights (as described for the two-account option above), and must be mailbox-enabled before any data can be migrated to it.

Account permissions for migration to Office 365

Migrator for GroupWise automatically sets and removes most permissions needed for migration to Office 365. But you must manually set account impersonation for a Microsoft- hosted Exchange target. To set account impersonation:

In Office 365 Management | Users | Settings, assign administrator permissions to the admin migration account, and this admin migration account must be granted full access permissions to all mailboxes that you migrate.
Also: The AD admin account must be configured with Application Impersonation, by this PowerShell cmdlet:

Requirement specifications

Migrator for GroupWise requires certain hardware and software prerequisites on the various machines associated with the overall migration project. These requirements are specified in the most recent RTM Release Notes that accompany the product in every release.

Related Documents