This licensing/unlicensing feature is explained below under Managing the Admin Account Pool.
A few simple preparations are necessary before you can use the Admin Account Pooling utility.
These steps are mandatory before you can use the Admin Account Pooling utility the first time.
Verify that all system requirements for an Migrator for Notes to Exchange admin migration server, and for the Account Pooling Utility in particular, are satisfied. System requirements are documented in the most recent RTM Release Notes that accompany every release. Note that the requirements for migration to Office 365 specify additional requirements for Migrator for Notes to Exchange’s Account Pooling feature.
For example (value shown is the default group name):
For example (value shown is the default sequence number):
• |
In Migrator for Notes to Exchange’s Notes Migration Manager, on the Exchange Server Configuration screen; or |
• |
In the Data Migration Wizard, on the Select Destination Exchange Server screen. |
• |
Use admin account pool (checkbox, available only when migrating to Office 365): Mark this checkbox to tell Migrator for Notes to Exchange to use your Admin Account Pool to migrate data. Next to this checkbox are two buttons that will run the Admin Account Pool Utility by either of two options: |
• |
Manage button: Launches Migrator for Notes to Exchange’s Admin Account Pool utility (see Managing the Admin Account Pool below). |
• |
Reset button: Used to reset the pool, this button launches Migrator for Notes to Exchange’s Admin Account Pool utility, and then automatically deletes all admin accounts from the pool and exits. |
1 |
Swap the Admin Pool accounts to tenant.onmicrosoft.com, and set the TargetAddress to user@[FederatedDomain].com. |
2 |
Make sure to set Set-ExecutionPolicy Unrestricted in the x86 PowerShell. |
Migrator for Notes to Exchange's qsched.exe task-scheduling utility is compatible with Migrator for Notes to Exchange's Admin Account Pool for migrations to Office 365, but only with an additional step added to the process. For other migration scenarios (to an on-premises Exchange, or to Office 365 without the Admin Account Pool) the qsched.exe utility regularly checks Migrator for Notes to Exchange's SQL database to see whether any tasks have been scheduled to run since the last check, and then executes any such tasks it finds (as explained in Migrator for Notes to Exchange's Admin Guide, chapter 13). But Office 365 access restrictions require an intermediate scheduling mechanism to accommodate the Admin Account Pool.
When migrating to Office 365 with Migrator for Notes to Exchange's Admin Account Pool, use Windows' Task Scheduler to run Migrator for Notes to Exchange's qsched.exe for each Migrator for Notes to Exchange task you want to run:
1 |
Add a Windows scheduled task to run Migrator for Notes to Exchange's qsched.exe (in the Migrator for Notes to Exchange installation directory) at the task's scheduled execution time, and to "Run only when user is logged on." |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center