立即与支持人员聊天
与支持团队交流

Migrator for Notes to Exchange 4.16.3 - Administration Guide

About the Migrator for Notes to Exchange documentation Notes Migration Manager
Basic operating principles Notes Migration Manager navigation drawer Project management features
NABS Discovery Wizard Internet Domains Discovery Wizard Directory Export Wizard Collection Wizard Groups Provisioning Wizard Notes Data Locator Wizard Provisioning Wizard Send PAB Replicator Wizard Data Migration Wizard SSDM Statistics Collection Wizard The Log Viewer Using the Qsched.exe task-scheduling utility SSDM Scheduling Administration utility Microsoft 365 Admin Account Pool PowerShell cmdlets for Migrator for Notes to Exchange Appendix A: How do I ...?
Post-installation configuration Pre-migration preparations Batch-migration process Other features

Licensing Microsoft 365 accounts for the Admin Account Pooling utility

Licensing Microsoft 365 accounts for the Admin Account Pooling utility

Before March 2015, Microsoft 365 accounts used for the Migrator for Notes to Exchange Admin Account Pooling utility were typically unlicensed. However, some customers began receiving connectivity errors when connecting to Microsoft 365 with those accounts. These customers reported that licensing the Admin Pool users resolved the connectivity errors, so with this feature Migrator for Notes to Exchange can automatically license these accounts (if required), and subsequently unlicense them when the migration is complete.

Microsoft Microsoft 365 licenses are transferable, so they can be reassigned after they are dissociated from the Admin Account Pooling accounts. Note that this dissociation also deletes any Microsoft 365 mailbox that may have been created for the account, but admin accounts created for this purpose typically do not need or use Microsoft 365 mailboxes.

 

This licensing/unlicensing feature is explained in the section titled Managing the Admin Account Pool.

 

 

Necessary preparations for the Admin Account Pooling utility

Necessary preparations for the Admin Account Pooling utility

A few simple preparations are necessary before you can use the Admin Account Pooling utility.

 

Before you use the Admin Account Pool for the first time

Before you use the Admin Account Pool for the first time

These steps are mandatory before you can use the Admin Account Pooling utility the first time.

 

  1. Verify system requirements for the Admin Account Pooling utility.

    Verify that all system requirements for an MNE administrator migration server, and for the Account Pooling Utility in particular, are satisfied. System requirements are documented in the Release Notes that accompany each release. Note that the requirements for migration to Microsoft 365 specify additional requirements for the Migrator for Notes to Exchange Account Pooling feature.

  1. Configure the Admin Role Group Name

    Admin pool accounts are granted administration rights by assigning a set of administration roles to the accounts. Roles are assigned by creating an admin role group and adding the pool accounts to the admin role group. The name of the admin role group can be customized with the following parameter:

    [Exchange] AdminAcctPoolRoleGroupName=<GroupName> For example (value shown is the default group name):

    [Exchange] AdminAcctPoolRoleGroupName=Notes Migrator Admins Role Group

    If the role group specified does not already exist, the Admin Account Pool utility creates it. The role group is assigned the following roles:

    • Mail Recipients

    • Mail Recipient Creation

    • Distribution Groups

    • Security Group Creation and Membership

  1. Configure the Admin Account Pool account name prefix.

    Accounts created for the pool are assigned a name prefix. By default, the name prefix is the current Exchange admin user name as defined in the system. You can customize the name prefix of the pool accounts using the following parameter:

    [Exchange] AdminAcctPoolUserNamePrefix=<UserName> For example:

    [Exchange] AdminAcctPoolUserNamePrefix=PoolAccount

    If the pool account name prefix is not specified or is empty, the Admin Account Pool utility uses the default value (name of the Exchange admin user).

  1. Configure Admin Account Pool account numbers.

    Accounts created for the pool are also assigned a numeric suffix. The suffix is incremented as each account is added to the pool. The starting value for the numeric suffix can be customized with the following parameter:

    [Exchange] AdminAcctPoolFirstAccountSeq=<####> For example (value shown is the default sequence number):

    [Exchange] AdminAcctPoolFirstAccountSeq=1001

  1. Enable the Admin Account Pool.

    The MNE Account Pool utility helps you manage account pool membership but it does not tell the other MNE applications to make use of its pool of accounts. To use the account pool, you must configure Migrator for Notes to Exchange on either of two screens:

    • In the MNE Notes Migration Manager, on the Exchange Server Configuration screen.

      - OR -

    • In the Data Migration Wizard, on the Select Destination Exchange Server screen.

      These screens contain the same Admin Account Pool controls so you can enable the pool and/or run the Admin Account Pool utility from either place:

    • Use admin account pool (check box is available only when migrating to Microsoft 365): Select the check box to use your Admin Account Pool to migrate data. Next to this check box are two buttons:

      • Manage: Launches the Admin Account Pool utility (see Managing the Admin Account Pool).

      • Reset: Resets the pool. This button launches the Admin Account Pool utility and automatically deletes all admin accounts from the pool and exits.

  1. Preempt MS AD sync conflict (in federated environments only).

    The Admin Account Pool utility clashes with the Microsoft AD sync utility in federated environments. To preempt this conflict:

    1. Swap the Admin Pool accounts to tenant.onmicrosoft.com and set the TargetAddress to

      user@[FederatedDomain].com.

    2. Ensure you set Set-ExecutionPolicy Unrestricted in the x86 PowerShell.

 

 

For each MNE task you want to schedule

For each MNE task you want to schedule

The MNE qsched.exe task-scheduling utility is compatible with the Admin Account Pool for migrations to Microsoft 365, but only with an additional step added to the process. For other migration scenarios (to on-premises Exchange or to Microsoft 365 without an Admin Account Pool) the qsched.exe utility regularly checks the MNE SQL database to see whether any tasks are scheduled to run since the last check, and runs any tasks it finds (as explained in the Administration Guide, chapter 13). However, Microsoft 365 access restrictions require an intermediate scheduling mechanism to accommodate the Admin Account Pool.

When migrating to Microsoft 365 with the MNE Admin Account Pool, use the Windows Task Scheduler to run the

qsched.exe for each MNE task you want to run:

  1. Add a Windows scheduled task to run qsched.exe (in the Migrator for Notes to Exchange installation directory) at the task's scheduled run time and set it to “Run only when user is logged on.”

  2. At the time the task is scheduled to run:

    • Ensure the Migrator for Notes to Exchange task scheduler service is disabled.

    • Ensure the task's associated user is logged on (per step 1).

 

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级