Quest ® Migrator for Notes to Exchange 4.16.

2
Administration Guide
© 2022 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 IRUPTION
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 website (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 www.quest.com/legal.
Trademarks
Quest and the Quest logo are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For
a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. Microsoft, Windows, Outlook and
Active Directory are registered trademarks of Microsoft Corporation in the United States and other countries. Office 365 is a
trademark of Microsoft Corporation in the United States and other countries. Domino is a registered trademark of international
Business Machines Corporation, registered in many jurisdictions worldwide. All other trademarks, servicemarks, registered
trademarks, and registered servicemarks are the 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, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

Migrator for Notes to Exchange Administration Guide

Updated - February 2022
Software Version - 4.16.2
Contents

About the Migrator for Notes to Exchange documentation . . . . . . . . . . . . . . . . . . . . . . . . 9

About this Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About the Migrator for Notes to Exchange documentation suite . . . . . . . . . . . . . . . . . . . . 9
Other sources of information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Notes Migration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Basic operating principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Navigation in Notes Migration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About wizards and tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About Migrator for Notes to Exchange statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Notes Migration Manager navigation drawer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Project management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Project view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
View documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Edit Default Settings: SQL Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Edit Default Settings: Shared Directories Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 17
Edit Default Settings: Notes Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Edit Default Settings: Exchange Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Edit Default Settings: Active Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Discover Notes Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Group Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
User Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Monitor Migration Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Gather Desktop Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Manage Scheduled Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
View Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
View Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

NABS Discovery Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Specify Notes Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Internet Domains Discovery Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Specify Notes Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Quest Migrator for Notes to Exchange 4.16.1 Administration Guide

3
Contents
 Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Directory Export Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configure Directory Export Updates of TSV-Imported Values . . . . . . . . . . . . . . . . . . . . . 46
Specify Notes Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Specify Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Schedule Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Exported data elements in the SQL database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Collection Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Select Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Specify Collection Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Choose Member Selection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Add Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Edit Collection Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Groups Provisioning Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Select Group Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Specify Active Directory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Choose Your Group Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Specify Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Schedule Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Notes Data Locator Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Quest Migrator for Notes to Exchange 4.16.1 Administration Guide

4
Contents
 Select User Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configure Updates of TSV-Imported Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Specify Notes Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Select Notes Data Store Types to Locate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Specify How to Find Notes Mail Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Specify Notes Mail File Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Specify How to Find Notes Personal Address Books . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Specify Notes Personal Address Book Replica Directory . . . . . . . . . . . . . . . . . . . . . . . . 66
Specify Notes PAB Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Specify How to Find Notes Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Specify Notes Archive Replica Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Specify Notes Archive Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Specify How to Determine Owner Using ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Select Administrative Users to Ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Specify Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Provisioning Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
How the wizard works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Before you run the Provisioning Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Select Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Select User Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Specify Active Directory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Choose Your Method for Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Choose the Container for User Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Specify Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Send PAB Replicator Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Select User Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Specify Notes Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Replicator Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Select User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Quest Migrator for Notes to Exchange 4.16.1 Administration Guide

5
Contents
 Confirm Create Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Data Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Select Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Select User Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Select Office 365 Administrative Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configure Migration Notification Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Select Notes Administrative Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Specify Data for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Specify How To Migrate Notes DocLinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Notes Mail Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Select Destinations for Migrated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Specify Mail Routing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Specify Notes to Exchange Mail Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Specify Remove Exchange Forwarding Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Specify Exchange to Notes Mail Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Specify Remove Notes Forwarding Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Select Notes User Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Specify Active Directory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
How Were Accounts Loaded into Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Specify Exchange Mailbox Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Specify Notes Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Select Date and Size Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Select Destination Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Personal Archive Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Specify Migration Run Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Migration Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Specify Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Schedule Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

SSDM Statistics Collection Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Wizard process screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Customize Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Quest Migrator for Notes to Exchange 4.16.1 Administration Guide

6
Contents
 Generating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Creating Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Specify Task Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Schedule Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Task Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Task Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

The Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Log Viewer menus and toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
How to ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Using the Qsched.exe task-scheduling utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Post-installation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

SSDM Scheduling Administration utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

About SSDM Scheduling Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Before you can use the SSDM Scheduling Administration utility . . . . . . . . . . . . . . . . . . . . . 118
Scheduling and limiting concurrent runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Monitoring SSDM usage status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Office 365 Admin Account Pool utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

About the Admin Account Pool utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Licensing Office 365 accounts for the Admin Account Pooling utility . . . . . . . . . . . . . . 123
Necessary preparations for the Admin Account Pooling utility . . . . . . . . . . . . . . . . . . . . . . 124
For each MNE task you want to schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Managing the Admin Account Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

PowerShell cmdlets for Migrator for Notes to Exchange . . . . . . . . . . . . . . . . . . . . . . . 127

Using PowerShell Cmdlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Cmdlets in Quest.MNE.Powershell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Appendix A: How do I ...? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Post-installation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
How do I set the account permissions necessary for migration? . . . . . . . . . . . . . . . . . 312
How do I configure Migrator for Notes to Exchange for a non-English Notes locale? . 312
How do I enable remote management on an Exchange 2010 or later server? . . . . . . . 315
Pre-migration preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
How do I add or edit program parameters? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
How do I migrate from a Notes environment with Symantec E-Vault? . . . . . . . . . . . . . 317
How do I migrate to an Exchange environment with a CAS Array? . . . . . . . . . . . . . . . 317
How do I prepare the SQL database for mailbox-enabling (if AD is configured for a resource
forest and a user forest)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
How do I add to the list of AD attributes available for the merge function? . . . . . . . . . . 319
How do I configure AD to replicate an AD attribute to the Global Catalog? . . . . . . . . . 320
How do I specify per-user locations for Notes source data? . . . . . . . . . . . . . . . . . . . . . 321
How do I specify per-user destination locations for users’ PST files? . . . . . . . . . . . . . . 322

Quest Migrator for Notes to Exchange 4.16.1 Administration Guide

7
Contents
 How do I specify whether to migrate to a single PST file (per user) or multiple PST files? .
322
How do I migrate Notes custom attributes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
How do I customize the placeholder message that the Data Migration Wizard substitutes for
encrypted messages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
How do I customize the placeholder message that the Data Migration Wizard substitutes for
filtered attachments? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
How do I create or edit a template for personalized user-notification emails? . . . . . . . 325
Batch-migration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
How do I synchronize directory data and update the SQL database? . . . . . . . . . . . . . 327
Other features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
How do I schedule tasks? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
How do I troubleshoot service startup permissions? . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
How do I send pre- or post-migration notification emails to end users? . . . . . . . . . . . . 331
How do I perform an offline migration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
How do I migrate resources? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
How do I migrate mail-in databases? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV
files? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

About us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Technical support resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Quest Migrator for Notes to Exchange 4.16.1 Administration Guide

8
Contents
 About the Migrator for Notes to
Exchange documentation
• About this Administration Guide
• About the Migrator for Notes to Exchange documentation suite
• Other sources of information

About this Administration Guide

This Administration Guide provides operating instructions for the various administrator components of Quest
Migrator for Notes to Exchange, with screen-by-screen field definitions and application notes for those tools. This
Guide is organized into 16 chapters plus an appendix:
• Chapter 1: The Notes Migration Manager. An overview of the basic operating principles for the
administrator’s central console, followed by descriptions and application notes for each of its screens.
• Chapters 2–11 (wizards). Operating instructions and screen-by- screen notes for all the wizard
applications that can be launched from the Notes Migration Manager. Each wizard is documented in its own
chapter.
• Chapter 12: The Log Viewer. Operating instructions and application notes for the Log Viewer utility, used
to simplify the viewing and interpretation of Quest program log files.
• Chapter 13: Qsched.exe task-scheduling utility. Operating instructions and application notes for the
Migrator for Notes to Exchange qsched.exe utility, which 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.
• Chapter 14: SSDM Scheduling Administration Utility. Operating instructions and application notes for
the SSDM Scheduling Administration Utility, used to regulate end-user runs of the Self-Service Desktop
Migrator (SSDM) to avoid processing bottlenecks.
• Chapter 15: Office 365 Account Pool Utility. Operating instructions and application notes for the Account
Pool Utility, used to coordinate multiple O365 admin migration accounts to run simultaneously, to sidestep
Microsoft-imposed throttling limits.
• Chapter 16: PowerShell cmdlets for Migrator for Notes to Exchange. A reference listing the purposes,
functions, parameters and other pertinent notes for Migrator for Notes to Exchange’s several dozen
PowerShell cmdlets, which can help automate processes.
• Appendix A: How Do I ...? Process instructions for specific tasks associated with Migrator for Notes to
Exchange migrations.
This Administration Guide is intended for network administrators, consultants, analysts, and any other IT
professionals who install the product, use its admin tools, or contribute to migration project planning.

About the Migrator for Notes to Exchange

documentation suite
This Administration Guide is one of several documents that explain various aspects of the Quest Migrator for
Notes to Exchange product. The complete documentation suite includes:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

9
About the Migrator for Notes to Exchange documentation
 • Quick-Start Guide: An orientation to Migrator for Notes to Exchange's basic purposes, components and
features, with a case study to illustrate typical usage. Also includes instructions for downloading and
installing the software.
• Pre-Migration Planning Guide: A checklist of strategic and tactical issues that an organization must
consider and accommodate before beginning a migration project. An appendix also documents known
limitations of the migration process.
• Scenarios Guide: Descriptions of the most common migration scenarios—migrating to different target
environments and for an array of other variables and preferences—with process instructions and flow
charts that explain how to use Migrator for Notes to Exchange tools and features in each scenario.
• Administration Guide: Operational details, application notes and screen-by-screen field notes for the
administrator components of Migrator for Notes to Exchange.
• Self-Service Desktop Migrator User Guide: Operating instructions, application notes and screen-by-
screen field notes for the Self-Service Desktop Migrator (SSDM) component of Migrator for Notes to
Exchange. The SSDM User Guide is provided as a separate PDF document so that an administrator can
distribute it to any end users who will run the per-desktop program.
• Program Parameters Reference: A listing of all Migrator for Notes to Exchange program parameters (and
their valid values) in the Task Parameters and Global Defaults, and how to use them to control various
program behaviors.
• Online Help: Context-sensitive field definitions and application notes for all Migrator for Notes to
Exchange’s wizards and other component applications.
All these documents, except the SSDM User Guide, are intended for network administrators, consultants,
analysts, and other IT professionals who install the product, use its admin tools, or contribute to migration project
planning. The Pre-Migration Planning Guide and Scenarios Guide present a more conceptual view of the product,
while the Administration Guide provides the hands-on, screen-by-screen descriptions and field notes. The SSDM
User Guide is intended for end users or administrators who use the Self-Service Desktop Migrator component.

NOTE: Quest recommends that all administrators read the Quick-Start Guide and Pre-Migration
Planning Guide (in that order), and the first chapter of the Scenarios Guide. You can use that
information to prepare a detailed written Migration Plan before attempting the migration process.
When you are ready to begin the migration process, you can refer to the process instructions and notes
in the Scenarios Guide, and the operational details in the Administration Guide.

Other sources of information

Visit our Quest communities web site

The Quest communities web site is an online community dedicated to issues relating to:
• Migration of email, identity and applications to the Windows Exchange platform, either on-premises or
hosted Exchange platforms like Office 365—including migrations from Exchange, GroupWise, and Notes.
• Active Directory migrations.
• Migrations from Notes application and Exchange public folders to SharePoint.
• Coexistence strategies and tools.
The community is designed to foster collaboration between Quest Migration experts and users. It’s a place where
you can:
• Learn about product releases and betas before anyone else.
• Get access to Quest product leaders and subject matter experts on migration and coexistence.
• Participate in discussion forums, share insights and ideas, and get common questions answered.
You can browse the forums and the library, but to take full advantage of the community, post new threads, respond
to messages from others, and rate our documents and downloads, you must Join the community. If you already

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

10
About the Migrator for Notes to Exchange documentation
have a Quest account or are a member of another Quest community, Sign in. The Sign in and Join features are
both available from links near the top-right corner of the page at the Quest Communities web site.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

11
About the Migrator for Notes to Exchange documentation
 1
Notes Migration Manager
• Basic operating principles
• Notes Migration Manager navigation drawer
• Project management features

Basic operating principles

Notes Migration Manager is the central console or “hub” program of Migrator for Notes to Exchange (MNE). Most
of the other program features are configured, scheduled, and run from the Notes Migration Manager console. The
primary features—directory data export, Notes data discovery, and locating, object provisioning in AD, data
migration, and so on—are performed by separate wizard applications that are launched from screens in the Notes
Migration Manager. Notes Migration Manager also provides features to help in the planning, monitoring, and
administration of a migration project.

Navigation in Notes Migration Manager

A sidebar on the left side of the Notes Migration Manager window contains a list of the screens in the application.
Each name in the list is a link that you click to display the associated screen. The screens are listed in the order in
which they are typically used but can be viewed and used independently.
Some screen links appear grayed-out (unavailable) if the features require information that is not yet entered (in
other screens).

About wizards and tasks

A migration process is a sequence of tasks to be performed, usually in a particular order. The process instructions
in the Migrator for Notes to Exchange Scenarios Guide (chapters 2 and 3) illustrate how some migration tasks are
performed by Migrator for Notes to Exchange, while others are performed manually or using other applications.
A wizard is a component application of Notes Migration Manager—specialized to perform a particular task such as
exporting directory data, provisioning groups in Active Directory (AD), or defining a task to be run at another time.
The Notes Migration Manager contains 10 wizards that perform or facilitate various steps or aspects of an overall
migration process.
For example, the Notes Migration Manager includes the Data Migration Wizard that can migrate data for the users
in a specific user collection, and also performs related administrative functions in Notes and Exchange. You can
configure the wizard to mailbox-enable existing AD accounts, to set and remove mail forwarding, and so on. A task
is a defined combination of functions with set parameters that dictate how the functions are performed.
All Notes Migration Manager wizards define tasks and all wizards can perform their tasks as soon as they are
defined. Some wizards can schedule tasks to run at a later time or date, or to run at a recurring series of dates and
times.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

12
Notes Migration Manager
Notes Migration Manager Wizards
The following wizards are launched from the Notes Migration Manager:
• NAB Discovery Wizard: Searches the Notes/Domino server to locate all Notes NABs (Name and Address
Books). The Directory Export Wizard and Internet Domains Discovery Wizard extract critical directory
information from the NABs which is read by the MNE provisioning and migration wizards so that they can
perform their tasks.
• Internet Domains Discovery Wizard: Extracts all the Internet domains it finds within the Notes NABs
(Name and Address Books) that were located by the NAB Discovery Wizard. The domains are used to
generate address aliases for all users so that Exchange can recognize and correctly route mail sent to the
user old addresses.
• Directory Export Wizard: Gathers user information from the Domino server to create the SQL Server data
tables that provide critical input data to the MNE provisioning and migration wizards.
• Collection Wizard: Used to define the member contents of user and group collections. Provisioning,
migration, and other functions are applied to collections of users and groups, and the Collection Wizard is
where you create the collections. You can add members to a collection by selecting objects from Active
Directory or by importing the contents of a .tsv (tab-separated-value) file, or both.
• Groups Provisioning Wizard: Defines a task that provisions the distribution groups (creates group
objects) within Active Directory from a designated group collection, and schedules the task to run at a
particular time, or at a series of recurring times.
• Notes Data Locator Wizard: Defines a task that locates the data files in the Notes source for a specific
user collection, or gathers statistics from previously located data stores, and schedules the task to run at a
particular time or at a series of recurring times.
• Provisioning Wizard: Provisions objects in local Active Directory from Notes user data previously
exported from Domino to the MNE SQL database. The Provisioning Wizard consolidates any duplicate
objects in AD by merging information from Exchange contacts (generated by a directory update, typically
using the Quest CMN Directory Connector) into corresponding user AD accounts, and deleting the
contacts, to leave a single mail-enabled security object per user.
• Send PAB Replicator Wizard: Sends a special email form to users in a particular user collection that lets
the users copy their PABs (personal address books) to a centralized Notes server directory, from which the
Data Migration Wizard can find them and migrate them.
• Data Migration Wizard: Defines a task to perform some combination of the following functions for users in
a collection:
▪ Migrate user data for all users within a particular user collection.
▪ Mailbox-enable existing AD accounts.
▪ Set and remove mail-forwarding.
▪ Disable foreign directory sync in the Notes source.
▪ Set user visibility in the Notes source.
• Self-Service Desktop Migration Statistics Collection Wizard: Gathers migration statistics written by the
Self-Service Desktop Migrator (SSDM) and loads the data to the SQL database to help you track the
progress of the migration project.

About Migrator for Notes to Exchange statistics

The Notes Migration Manager and several of the MNE wizards report data statistics from the Notes environment
such as sizes of message stores, data volumes migrated, and so on. The statistics, and corresponding throughput,
that are reported are based on uncompressed data sizes as provided by the Notes APIs. The APIs extract the data
in a compressed format and subsequently provide the data to MNE in an uncompressed state. As a result, the
data amounts reported by MNE are likely higher than the numbers observed natively in Notes or the volumes
transferred over the network to the migration servers.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

13
Notes Migration Manager
Notes Migration Manager navigation
drawer
The MNE console navigation drawer in the top right corner contains the following options.

Global Default Settings

Click Global Default Settings to export the default program-configuration information from the SQL database to a
text-only format and to launch Windows Notepad to view and edit the file. For information and procedural
instructions, see Appendix A: How Do I Add or Edit Program Parameters?
In Notepad, the settings look like the contents of an INI file but are saved as a part of the SQL database. When you
close Notepad, Notes Migration Manager copies the new parameter values to the SQL database.

NOTE: Editing the Global Default Settings does not change any program configuration for previously
created tasks. Wizards retrieve Global Default Settings only as they create tasks, not when they run tasks.

Upgrade Templates
After a software upgrade to 4.16.1, the navigation drawer contains the Upgrade Templates option. Click to
upgrade all the full templates in the database to differential templates. A full template does not pick up new Global
Default settings after it is created. A differential template can pick up new Global Default settings.
If you do not upgrade all full templates in the database to differential templates during the MNE console start up,
you can still select Upgrade Templates from the MNE navigation drawer to upgrade them. After that, the Upgrade
Templates item is removed from the MNE navigation drawer.

Edit Application Timeout

Opens a dialog box on which you can change the number of minutes of inactivity the Data Migration Wizard waits
in a program run before concluding that a process has encountered a fatal error and ends the process. Set the
Minutes parameter to your preferred value and click OK.
For migration to a local Exchange server (not Office 365), shorter and higher-quality transmission paths make
timeouts less common so the default value of 15 is suitable for most circumstances.
For migration to Office 365, more process timeouts are typically generated and this can become problematic if you
are migrating large numbers of large messages (usually due to large attachments). The Data Migration Wizard
may even end its run if it encounters too many timeouts. You might want to set the timeout Minutes value to 30 for
an Office 365 migration to handle less robust transmission paths.

Advanced Wizard Settings

A toggle setting that determines if the wizards allow you to edit Task Parameters—configuration parameters that
are specific to the current task—from within the wizard, without changing the Global Default Settings. For
information and procedural instructions, see Appendix A: How Do I Add or Edit Program Parameters?
The wizard lets you view, edit, and save the parameters pertaining to the task via Notepad as if you were editing
the Global Default Settings using the File menu. However, any changes you enter in a wizard apply only to the
single task being created. Use this feature only if you need to make changes to the configuration of a specific task
as recommended by Quest Support staff or the product documentation.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

14
Notes Migration Manager
View Console Log
Launches the Log Viewer, a program that helps you view and interpret the program log files written by most Quest
applications. When launched from this menu, the Log Viewer opens the log file for Notes Migration Manager.

Visit the Community

Opens a browser window to visit the Quest support website and the Migrator for Notes to Exchange and
Coexistence manager for Notes community, an interactive community dedicated to issues relating to:
• Migration of email, identity and applications to the Windows Exchange platform, either on-premises or
hosted Exchange platforms like Office 365—including migrations from Exchange, GroupWise, and Notes.
• Active Directory migrations.
• Migrations from Notes application and Exchange public folders to Sharepoint.
• Coexistence strategies and tools.
The community is designed to foster collaboration between Quest Migration experts and users. This community is
a place where you can:
• Learn about product releases and betas before anyone else.
• Get access to Quest product leaders and subject matter experts on migration and coexistence.
• Participate in discussion forums, share insights and ideas, and get common questions answered.
You can browse around the forums and the library, but to take full advantage of the community, post new threads,
respond to messages from others, rate our documents and downloads, you must become a registered member. If
you already have a Quest account or are a member of another Quest community, log in. The Login and Register
features are both available from links in the top-left corner of the page.

Check for Updates

Opens a browser window to visit the Quest support web site showing all available versions of the Migrator for
Notes to Exchange product, where you can optionally download a later version.

About Quest Migrator for Notes to Exchange

Displays a dialog with information about your Migrator for Notes to Exchange installation, including version
information and details about your license. You can view and update license information here.

Project management features

These screens permit configuration of project-wide features and options:
• Project view
• View documentation
• Edit Default Settings: SQL Server Configuration
• Edit Default Settings: Shared Directories Configuration
• Edit Default Settings: Notes Server Configuration
• Edit Default Settings: Exchange Server Configuration
• Edit Default Settings: Active Directory Configuration
• Discover Notes Information

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

15
Notes Migration Manager
 • Group Collections
• User Collections
• Monitor Migration Progress
• Gather Desktop Statistics
• Manage Scheduled Operations
• View Summaries
• View Logs

Project view
This screen provides statistics that summarize the status of the various aspects and phases of the overall
migration project:
• Directory: The date and time of the last directory export and the number of users, groups, resources, and
contacts that were exported.
• Collections: The number of defined group and user collections that were defined by the program and
defined by the administrator. Also shows the total number of defined group collections and the number of
group collections that were provisioned into Active Directory.
• Group Provisioning Summary: The number of groups found in the Notes source and the number that
were provisioned in Active Directory.
• Migration summary: The number of users and resources that are ready for migration, numbers that have
been migrated, number that are active (migrating now), and number remaining to be migrated.
• Operation schedule summary: The number of tasks that have been scheduled for later runs: the total
number, the tasks still pending, and tasks currently running.
• License information: The usage data associated with the Quest license that authorizes the use of this
product.

View documentation
This screen lists the available PDF-format documentation and Release Notes associated with Migrator for Notes to
Exchange and provides buttons that let you View or Print the documents. To view PDF documents, you must
install the Adobe Reader software, available for free from: http://www.adobe.com/products/reader/

Edit Default Settings: SQL Server Configuration

This screen collects the information necessary for the program and its wizards to access the MNE SQL database.
Click Apply after you enter new information or changes. The program cannot read or save new information or
changes until Apply is clicked.

SQL Server credentials

• SQL Server host name: The name of the SQL Server. If you are using SQL Express, you must include the
SQLEXPRESS SID in the hostname—for example: (local)\SQLEXPRESS. If your server is listening to a
non-standard TCP/IP port, specify the port after the host (and SID) with a comma preceding it—for
example: sql.example.com\SQLEXPRESS,1234.
Note: If you are using SQLEXPRESS and connecting remotely, you must configure SQLEXPRESS to
allow remote connections.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

16
Notes Migration Manager
 • Authentication options: Specify the method to be used to authenticate the program access to the SQL
server:
▪ Windows authentication: Authenticate using the currently logged-in user Windows credentials.
▪ SQL Server authentication: Authenticate using the SQL Server admin credentials:
▫ SQL user: The SQL Server admin user name.
▫ Password: The password associated with the SQL user.
▫ Bulk import directory: A directory to which the SQL Server can read and write, specified as
a UNC path. This is a mandatory entry; The MNE use of this directory substantially improves
program performance when importing data from the Domino directory.
▪ Apply: Reads and saves new or changed information. Any new information or changes are
discarded if you do not click Apply before you exit.

Edit Default Settings: Shared Directories

Configuration
Click Apply after you enter any new information or changes to existing information. The program cannot read or
save any new information or changes until Apply is clicked.

Administrator tool settings

• Directory for log files (UNC path): Enter the full path for the directory to which the program and wizards
should write their reports and log files.
• Log level: Sets the detail level that the program and wizards will include in their run logs. Usually you
select Normal for a routine production run or select Verbose if you want to diagnose a problem.

Common tool settings:

• Common application directory (Self-Service Desktop Migrator and SMTP translation table): Enter
the path for the directory in which the SSDM program file will reside, for example: \\examplexp\shared\. The
migration administrator must be able to write to this directory but access for all end users should be set to
read-only.

Self-Service Desktop Migrator (SSDM) log settings

• Directory for central log and status files: Enter the full UNC path for the directory that will contain the log
files for the Self-Service Desktop Migrator (SSDM). Each time the SSDM program is run, it writes a
summary of its results to a file that resides in this directory. All user log files are written to this same
centralized directory.
• Post user logs to the central directory: Determines whether the log files written by the Self-Service
Desktop Migrator (SSDM) should be written to the centralized directory specified in the associated text box.
This check box must be selected if you want to gather desktop statistics. If this check box is left empty, the
SSDM log files are written to individual user local temp directories, where they are unavailable to the SSDM
Statistics Collection Wizard.
• Compress user log files: Determines whether the log files written by the SSDM should be compressed to
conserve disk space.
• Log level: Specifies how much detail the SSDM should include in its run logs. Usually you would select
Normal for a routine production run, or select Verbose if you want to diagnose a problem.
• Apply: Reads and saves new or changed information. Any new information or changes are discarded if
you do not click Apply before you exit.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

17
Notes Migration Manager
Edit Default Settings: Notes Server
Configuration
This screen collects the information necessary for the program and its wizards to access the Notes server. Click
Apply after you enter new information or changes to existing information. The program cannot read or save new
information or changes until Apply is clicked.
• Notes credentials (Server, User ID file, Password): These credentials authenticate the administrator by
whose authority the program will access the Notes server for data export, setting and removing mail-
forwarding rules during the migration, and data migration.
• Always use these values: Select this check box if you want the wizards that need this information to
always use these credentials. If this box is selected, the wizard skips the screen that requests credential
information. If the box is clear, the wizard takes the values entered as its defaults but displays the screen to
provide the option of accepting or changing the default credentials.
• Apply: Reads and saves new or changed information. Any new information or changes are discarded if
you do not click Apply before you exit.
• More info: Launches the Log Viewer to display the log file associated with this screen. The button is
enabled only if the program has encountered significant errors or warnings that typically require resolution
before continuing in the migration process. If no significant errors or warnings are encountered, the button
appears grayed-out (unavailable).

Edit Default Settings: Exchange Server

Configuration
This screen collects the information needed for the applications to access the Exchange server or Office 365. Click
Apply after you enter or change information. The program cannot save new or changed information until you click
Apply.
Target Exchange server version: Specify the Exchange version of your migration target: Exchange Server 2010,
Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, or Office 365.
This setting determines how the application facilitates mail-enabling and other AD activities.
If you selected an on-premises Exchange target, see Exchange Server Configuration: Migrating to on-premises
(proprietary) Exchange on page 19.
If you selected Office 365, see Exchange Server Configuration: Migrating to Office 365 on page 20.

NOTE: The Exchange account must be a mailbox-enabled or, if migrating to Office 365, have a license that
includes an Exchange mailbox.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

18
Notes Migration Manager
Exchange Server Configuration: Migrating to on-premises
(proprietary) Exchange
Specify the information that will be used as the defaults for migration to on-premises Exchange.
Exchange credentials:
The account used to access Exchange must be granted Receive-As permissions on the mail store. Also, the
account cannot belong to a group that is explicitly denied access to the mail stores. These groups include
Enterprise Admins, Domain Admins, and the Organization Management role. If the Exchange account is added to
any of these groups, MNE cannot connect to the target mailboxes during the migration.
• To automatically grant permissions to the specified administrator account, select the Automatically grant
permissions check box.
NOTE: There can be a significant delay between granting Receive-As permission and Exchange allowing
the account to access other mailboxes, up to 30 minutes.

Alternately, you could grant the permissions manually using the following PowerShell cmdlet:
get-mailboxdatabase | add-adpermission -user <username> -extendedrights receive-as
However, if you grant permissions manually using PowerShell, you must reconfigure the account each time a new
database is added.
If you use the Automatically grant permissions option, MNE grants permissions on the database container and
the permissions are inherited by all databases, even the databases that are added after initial configuration. If you
are using the PowerShell cmdlet to grant access, disable the built-in mechanism by clearing the check box.
• If the Target Exchange server version is 2013, 2016, or 2019:
Exchange Mailbox Server: Name of the Exchange server, which has the Mailbox role installed on it and
will be the connection used for all Exchange PowerShell activities in the product.
• If the Target Exchange server version is 2010:
Exchange CAS Server: Name of the client-access (CAS) server, not an array. This is the connection used
for all Exchange PowerShell activities in the product.

NOTE: If migrating to a CAS, you must also set a throttling policy and WinRM, as described in
Appendix A (see How Do I Migrate to an Exchange Environment with a CAS Array?).

• Administrator SMTP address: The SMTP address of the administrator by whose authority the wizard will
perform its mail-related operations.
• Administrator domain\user or UPN: Enter the migration administrator login name for the Exchange mail
server (for the account associated with the Administrator SMTP address) in the following format:
domain\name or name@domain.sitraka.com.
• Administrator password: The password associated with the administrator account.
Always use these values:
Select this check box if you want the wizards to always use these credentials and settings.The wizards will
skip the screens that request credential information. If the check box is cleared, the wizards take the values
entered here as defaults, but displays the screens to offer the option of accepting or changing the entries.
More info:
Launches the Log Viewer to display the log file associated with this screen. This button is enabled only if
the program has encountered significant errors or warnings that warrant attention before continuing in the
migration process. If no such significant errors or warnings are encountered, the button appears grayed-out
(unavailable).

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

19
Notes Migration Manager
Exchange Server Configuration: Migrating to Office 365
Specify the information that will be used as the defaults for migration to Office 365 (Exchange Online).
Exchange credentials:
• Automatically grant permissions: You can use this option to automatically grant the MNE admin user (or
assigned Admin Pool account) Full Access permission on the target mailbox during migration.

NOTE: When the target is Office 365, MNE checks to see if the Migration Account (or assigned Admin Pool
account) has Full Access permission on the target mailbox. If it does not, MNE temporarily grants Full
Access permission for the duration of the migration. This feature corresponds to the existing parameter
[Exchange] AddFullAccessPermission. However, the recommended method is to use the
PowerShell cmdlet to grant Full Access before migration (and clear the check box).

• Exchange Administrator: Enter the Office 365 account name for the migration administrator in the format
of name@domain.sitraka.com. The account must have the role of global administrator on the hosted
tenant.
• Administrator password: The password associated with the administrator account.
Tenant settings
• Office 365 Environment: Select the appropriate Office 365 environment in the list. The options are:
▪ Office 365 Global
▪ Office 365 Germany
▪ Office 365 operated by 21Vianet
• Office 365 User domain: In the drop-down list, select the Office 365 domain that should be used to
compose the user Microsoft Online Services ID (logon names and email addresses) in Office 365.

NOTE: The program loads the drop-down list with the domains registered in Office 365 for the
administrator credentials you entered. The Office 365 User domain selected is the portion of each
user email address that follows the @ symbol. The left side of each user ID is his/her User ID from
the MNE SQL server.

• Use Azure Active Directory Synchronization: Select this check box if you are using the Microsoft AD
synchronization tool to copy the contents of a local Active Directory to provision your Office 365 directory.
Leave this check box clear if you will provision Office 365 by any other method.
• Resolve attendees for [type] mail (two check boxes): Controls whether MNE looks up SMTP addresses
in the user server mail, and/or archives, in the Exchange GAL to get Exchange addresses—so that free-
busy lookups succeed. These options are disabled (cleared) by default. Leave the check box empty if you
want to migrate data to PST files without connecting to the Exchange server. Disabling the Resolve
attendees function can increase migration speed in some environments but can cause lost free/busy
information and introduce other issues in Outlook.
• Office 365 PowerShell Throttling: Click Configure to open a PowerShell Throttle Settings dialog box,
which calculates the maximum number of concurrent PowerShell connections each MNE server can open
(the MaxPowerShellConnections setting). MNE uses this value to enforce the limit set by Microsoft for the
tenant. The default for this throttle is 9 simultaneous runspace connections.
The dialog box calculates the MaxPowerShellConnections setting using the formula R / S, where R is the
number of simultaneous runspaces allowed by your tenant (Maximum Tenant Concurrency = 9 by default),
and S is the number of migration servers you will use. If the quotient is not a whole integer, MNE rounds
down to the next lower whole integer. The default value of MaxPowerShellConnections=0 is interpreted as
“no limit,” effectively turning off this limiting feature.
PowerShell Throttle Settings:
▪ Maximum Tenant Concurrency: The throttle set by Microsoft for your Office 365 tenant. The
default is 9.
▪ Maximum Migrations Servers: The maximum number of migration servers to be used for your
migration.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

20
Notes Migration Manager
 ▪ Migrator for Notes to Exchange MaxPowerShellConnections Setting: The maximum number of
concurrent PowerShell connections each migration server can open.
• Use admin account pool: Select this check box to use the Migrator for Notes to Exchange Admin Account
Pool feature (described in chapter 15 of the Administration Guide).
▪ Manage: Launches Migrator for Notes to Exchange’s Admin Account Pool utility.
▪ Reset: Launches the Migrator for Notes to Exchange Admin Account Pool utility and deletes all
admin accounts from the pool.
• Migrate oversized attachments: Oversized attachments are attachments that exceed the limit defined by
the attachment size filter in the Data Migration Wizard. For messages that contain attachments which are
not oversized but where the overall message size exceeds the limit imposed by Office 365, all attachments
are migrated as oversized attachments.
To migrate oversized attachments to the user OneDrive store, you must register MNE with the Microsoft
Azure portal and grant the necessary permissions to OneDrive.
▪ Configure: Opens the Microsoft Azure App Registration page. The page is used to register the
MNE application with the Microsoft Azure portal. It also allows you grant access to the OneDrive
store associated with the user mailbox to store oversized message attachments.
Always use these values:
Select this option if the wizards will always use these credentials and settings. The wizard skips the screen
that requests credential information. If the check box is empty, the wizard uses the values entered as
defaults, but will display the screen to offer the option of accepting or changing the credentials.
More info:
Launches the Log Viewer to display the log file associated with the functionality of this screen. This button
is enabled only if the program has encountered significant errors or warnings that warrant further attention
before continuing in the migration. If no significant errors or warnings are encountered, the button appears
grayed-out (unavailable).

Microsoft Azure App Registration

For migration to Office 365, if you have decided that oversized attachments should be migrated to the Microsoft
OneDrive store associated with the user mailbox, use this page to register the MNE application with the Microsoft
Azure portal and to grant the migration account with access to the OneDrive stores.

NOTE: Oversized attachments are defined using the maximum size limit for attachments that is set in the
Data Migration Wizard on the Select Date and Size Filters screen.

You have the option of automatically registering the MNE application with the Microsoft Azure portal using one-
click registration or you can chose to manually register the application.
App registration
• One-click registration: Click this button to automatically register the MNE application with the Microsoft
Azure portal. The Client ID, Client Secret, and Tenant fields are automatically populated. Once registration
is complete, you can click Save to store the settings in the MNE database and in the INI settings.
- OR -
• Follow instructions to manually register the App: You must perform the steps in Manually registering
the MNE application with the Microsoft Azure portal on page 22 to manually register Migrator for Notes to
Exchange with the Microsoft Azure portal site. It is important that you note the Application (client) ID and
client secret that is assigned since you must enter them, along with Office 365 Tenant name, in this page.
Register with Exchange admin user credential: Selected by default. Used if you want to register the MNE
application using the Exchange account that you entered as the Exchange administrator under Exchange
credentials. The specified account is used to connect to the Microsoft Azure portal and register the application.
Grant admin consent: Click this button to ensure the requested permissions needed to access the Microsoft
OneDrive stores and migrate attachments to the stores are granted to the application. When the Microsoft screen

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

21
Notes Migration Manager
listing the requested permissions for your tenant is displayed, click Accept. A confirmation message appears.
Click Yes.
• Office 365 Tenant: Your Office 365 tenant name. For example, Sitraka.onmicrosoft.com.
• Registered App Client ID (SSDM): The application ID created with delegated permissions after the
application is registered in the Microsoft Azure portal. It is automatically populated if you used the one-click
registration. With the manual registration process, the client ID that you enter for the SSDM is the same as
the Registered App Client ID.
• Registered App Client ID: The Application ID created with application permissions after the application is
registered in the Microsoft Azure portal.
• Registered App Client Secret: The Application Secret created after the application is registered in the
Microsoft Azure portal.
Show App Client Secret: When the check box is selected, the App Client Secret value is not masked but is
displayed so that you can make note of the client secret value to use if you are manually registering the application
with Microsoft Azure.

Manually registering the MNE application with the Microsoft

Azure portal
To find your Office 365 tenant name, log in into Office 365 Admin Center as an administrator. Under Settings, click
Domains and find a domain which ends in .onmicrosoft.com. This is your Office 365 tenant name, for example
Sitraka.onmicrosoft.com.
The process of registering an application with the Microsoft Azure portal is also described in the Microsoft topic
Register an application with the Microsoft identity platform.
NOTE: If you are connecting to Microsoft Azure China portal, you can use the same manual procedure to register
an application with Azure China. You can find the Azure China portal at: https://portal.azure.cn
Depending on the region from which you are accessing the Microsoft portal site, the user interface can differ.

To manually register the MNE application

1 Sign in the Microsoft Azure portal. (You must have global admin rights to register an application.)
2 Search for App registrations in the search box at the top.
- OR-
In the left navigation pane, click the Azure Active Directory service, click App registrations and click New
registration.
3 On the Register an application page, enter the application registration information:
▪ Name: For example, Quest Migrator for Notes to Exchange.
▪ Supported account types: Select Accounts in any organizational directory (Any Azure AD
directory - Multi tenant)
▪ Redirect URI:
▫ Select Public client/native (mobile & desktop)
▫ Enter a URI: https://login.microsoftonline.com/common/oauth2/nativeclient

NOTE: The Redirect URI is required to register the MNE application for both the Admin console and the
SSDM to be able to access mailbox OneDrive storage.

4 Click Register.
The newly registered application is displayed and the following application details become available.
▪ Application (client) ID: The Application ID created after the application is registered in the
Microsoft Azure portal. You must copy this ID and use it later to complete the App Registration.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

22
Notes Migration Manager
 5 Under Manage in the left section, click API permissions and click Add a permission.
6 On the Request API permissions window on the right, under Microsoft APIs, click Microsoft Graph.
a Select Application permissions on the right.
b From the list, expand Files, select Files.ReadWrite.All and click Add permissions to grant
application permission.
c Go back to add a permission for Microsoft Graph under Microsoft APIs and select the left box
Delegated permissions.
d From the list, expand Files, select Files.ReadWrite and click Add permissions to grant delegated
permission.
7 On the App registrations main page, click Certificates & secrets.
8 Under Client secrets, click New client secret
9 Enter a description and specify an expiration for the client secret (for example, In 2 years).
10 Click Add to generate the client secret.
11 Copy the new client secret value and keep it safe as you need it to complete the application registration in
MNE. You cannot retrieve a client secret after you perform another operation or leave this resource
management view (blade).
12 On the App registrations main page, click API permissions.
13 Click Grant admin consent for (your company name).
A confirmation message appears on the top.
14 Click Yes.
15 On the App registration main page, click Authentication.
16 Under Advanced settings, click Yes next to Treat application as a public client and click Save.
17 On the Microsoft Azure App Registration page in MNE, enter the values that were assigned for:
▪ Registered App Client ID: The Application ID created with application permissions after the
application is registered in the Microsoft Azure portal.
▪ Registered App Client Secret: The Application Secret created after the application is registered in
the Microsoft Azure portal.
▪ Office 365 Tenant: Your Office 365 tenant name. For example, Sitraka.onmicrosoft.com.
▪ Registered App Client ID (SSDM): The application ID created with delegated permissions after the
application is registered in the Microsoft Azure portal. With the manual registration process, the
client ID that you enter for the SSDM is the same as the Registered App Client ID.
18 Click Save.

Edit Default Settings: Active Directory

Configuration
This screen collects the information necessary for the program and its wizards to access Active Directory. (The
screen is disabled if you are migrating to Office 365 without using the Microsoft AD synchronization tool.)
Click Apply after you enter new information or changes to existing information. The program does not read or
save any new information or changes until Apply is clicked.
Active Directory credentials:
• Automatically grant permissions: The access credentials must be an Active Directory administrative
account that is a member of the Exchange Organization Management role group, is configured with remote
PowerShell enabled, and has full access to the target Organizational Units (OUs). You can use this option

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

23
Notes Migration Manager
 to automatically grant the required permissions to the specified account.
If you use the Automatically grant permissions option, MNE delegates Full Control permissions to the
root of the target OUs and the permissions are inherited by all OUs, even the OUs that are added after
initial configuration.
Alternately, you could manually grant the permissions using the Active Directory Users and Computers tool.
If you grant full access to the target OU using Delegation of Control Wizard, you must select Full Control.
Open the wizard and select the following: Create a custom task to delegate | This folder, existing
objects in this folder, and creation of new objects in this folder | Full Control.The program will check
that the access credentials have Full Control rights to the target Organization Units (OUs), not just
read/write permissions. You must reconfigure the account each time you change the target OU.
• Global Catalog host name: Specify a Global Catalog (GC) at a level higher than all the users, groups, and
contacts to be migrated. If you have multiple Global Catalogs/Domain Controllers in an AD forest, you can
choose any GC as long as it is in the same domain.

IMPORTANT: You must enter fully qualified domain names (FQDN) for the Global Catalog host name
and the Domain Controller host name.

• Domain Controller host name Specify the Domain Controller that is used to read data from or write data
to Active Directory.
• User name and Password: The access credentials used to authenticate the administrator by whose
authority the program accesses Active Directory.
• Always use these values: Select this check box if the wizards will always use these credentials. If this box
is selected, the wizard skips the screen that requests credential information. If the check box is empty, the
wizard retrieves the values entered here as defaults, but will display the screen to offer the option of
accepting or changing the default credentials.
• Path to existing organizational unit for distribution groups: Fully qualified domain name (FQDN) for
the group organizational unit (OU) path.
• Path to existing organizational unit for creating external members for distribution groups: Fully
qualified domain name (FQDN) for the path for an existing organizational unit (OU) to which group
members will be assigned when a member must be created as a new AD contact (when there is no
corresponding AD user account).
• Create user objects in Active Directory: Determines whether the Provisioning Wizard will create a new
user object in AD when none is found to correspond with a user in the collection. Such new user objects are
created in the container specified by the Path to existing organizational unit for creating user objects
text box. Ordinarily the objects created are not mail-enabled, although the EnableUsers parameter (in Task
Parameters) can be set to 1 to change that default behavior.
• Path to existing organizational unit for creating user objects: Click Browse to find and specify the
relative domain name for an existing organizational unit (for example, cn=users) where any new user
objects will be created in AD (when a wizard encounters a contact for which there is no existing
corresponding AD user account).
• Use resource/user forest: If your target environment is configured for a resource forest and a user forest
with corresponding user accounts, you must provide these credentials for the Data Migration Wizard to
enable mailboxes and to associate the resource accounts with the user accounts. The credentials specified
here identify the user forest, while the credentials specified for AD credentials pertain to the resource
forest.
User forest credentials:

NOTE: In addition to specifying the User forest credentials here, you must also add a set of parameters to
the configuration data for the Data Migration Wizard, explained in Appendix A of the Migrator for Notes to
Exchange Administration Guide—see the topic How do I prepare the SQL database for mailbox-enabling (if
AD is configured for a resource forest and a user forest)?

• Global Catalog host name: The name of the AD server.

• User name: The user ID of the administrator who will be running the migration program, by whose
authority the program accesses the user forest AD. This entry must be the SAM Account name, not the

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

24
Notes Migration Manager
 UPN.
• Password: The password associated with the user name.
• Apply: Reads and saves new or changed information. Any new information or changes are discarded if
you do not click Apply before you exit.
• More info: Launches the Log Viewer to display the associated log file. This button is enabled only if the
program encountered significant errors or warnings that require resolution before continuing in the
migration. If no significant errors or warnings are encountered, the button is dimmed (unavailable).

Discover Notes Information

• Discover Notes Information: Find NABs
• Discover Notes Information: Find Domains
• Discover Notes Information: Export Notes Directory

Discover Notes Information: Find NABs

This screen helps you locate and identify the Notes address books (NABs) that are the sources for information to
provision AD, identify users and other objects for migration, and facilitate mail-forwarding during the migration.
Click Apply after you enter new information or changes to existing information. The program does not read or
save new information or changes until Apply is clicked.
• Find NABs: Launches the NABs Discovery Wizard, which scans the Notes environment to identify and
return a list of Notes address books which may be “mined” by the Directory Export Wizard for information to
provision AD, identify users and other objects for migration, and facilitate mail-forwarding for the transition.
• NABs table: The list of all NABs found by the NABs Discovery Wizard plus any additional NABs added by
the Add NAB option.
• Add NAB: Opens a dialog box that lets you add additional NABs that may have been replicated to some
other location outside the Notes environment where the NABs Discovery Wizard would not locate them.
• Remove NAB: Removes the selected NAB from the NABs table. You can only remove NABs that were
manually added to the table by the Add NAB option and that have not yet been applied to the database (by
Apply).
• Enabled :Select the check boxes for all NABs that you want to include as source directories for directory
export (on the Export Notes Directory screen), and for building a list of domains in the Find Domains
screen. Clear check boxes for NABs that you want to exclude from directory export and the Internet
Domains Discovery Wizard.
• Apply: Reads and saves new or changed information in this screen. Updates are discarded if you do not
click Apply before you exit.

Discover Notes Information: Find Domains

This screen helps you build a comprehensive list of all Internet domains that are likely to be parts of valid SMTP
addresses, which the program needs to generate lists of aliases that Active Directory will accommodate after
migration. The Internet Domains Discovery Wizard compiles a list of all unique domains found in the NABs
selected as “Enabled” on the Find NABs screen, and displays its findings in the Domains table on this screen. You
can add domains that do not occur within the searched NABs, and enable and disable individual domains to
exclude any obscure domains that AD need not support.
Click Apply after you enter new information or changes to existing information in this screen. The program does
not read or save new information or changes until Apply is clicked.
• Find Internet domains: Launches the Internet Domains Discovery Wizard, which compiles a list of all
unique domains found in the NABs selected as “Enabled” on the Find NABs screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

25
Notes Migration Manager
 • Domains table: The list of all found domains found by the Internet Domains Discovery Wizard plus any
domain names added by the Add domain option.
• Add domain: Opens a dialog box that lets you add, to the Domains table, additional domains that do not
occur within the enabled NABs (from which the Internet Domains Discovery Wizard built its original
Domains table).
• Remove domain: Removes the selected domain from the Domains table. You remove only domains that
were manually added to the table by the Add domain feature and that have not yet been applied to the
database (by clicking Apply).
• Enabled: Select the check boxes for all domains that you want AD to regard as valid domains for SMTP
address aliases. Also, be sure to clear the boxes for any domains that you do not want AD to support as
address aliases. Note that enabling larger numbers of domains will generate correspondingly greater
numbers of supported aliases for every user in AD which may become unwieldy. More obscure, lesser-
used domains can usually be excluded with little or no significant loss of inbound mail.
• Apply: Tells the program to read and save any new or changed information in this screen. Any such
updates will be discarded if you do not click Apply before you exit the program.
• Details: For any particular domain selected in the Domains table, opens a pop-up window containing a
table of information about the source(s) where the domain was found, such as the DNS name of the server,
Notes domain, Internet domain name, and so forth. Click OK to dismiss the pop-up window.

Discover Notes Information: Export Notes Directory

This screen lets you run the Directory Export Wizard, which configures a task to export information from Notes
address books that the program will use to provision AD, identify users and other objects for migration, and
facilitate accurate mail-forwarding for the duration of the migration. You may tell the wizard to perform the export
task immediately following its configuration, or the wizard will let you schedule the task to run at a later time.
• Export directory: Launches the Directory Export Wizard.
• Objects found: A table containing a complete list of all users and other objects found by the most recent
directory export.
• Summary data: Reports the numbers of users, groups, resources and contacts found by the most recent
directory export.
Customize:
• Export objects to TSV: Opens a dialog box that lets you export the Objects found table to a tsv-format
(tab-separated-values) data file. You can use a program such as Microsoft Excel to edit the contents of the
table, and import the edited data into the Objects found table and the SQL database. For more information
on editing, see the procedures under User Collections on page 29.
• Import objects from TSV: Opens a dialog box that lets you import, into the Objects found table and the
SQL database, the edited contents of a .tsv data file that was exported to tsv format by the Export objects
to TSV option.

NOTE: After editing data by this Export/Import feature, you may want to run the Notes Data Locator
Wizard to verify you have entered the data correctly (no typos or malformed notations), that the
necessary certifications are in place, and that Migrator for Notes to Exchange can access the NSFs.

NOTE: Each run of the Directory Export Wizard overwrites the current contents of Migrator for Notes
to Exchange’s SQL database (including any imported TSV values) with data newly exported from the
Domino Directory—except that you may choose whether the wizard should overwrite or keep any
DominoServerAddress values that have been changed by a TSV import. The wizard’s default is to
preserve any TSV-imported values, but a screen in the wizard lets you choose to overwrite them.

• Next Notes directory export: Displays the next scheduled run (if any) of a directory export task, as
configured by a previous run of the wizard or as amended on the Manage Scheduled Operations screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

26
Notes Migration Manager
Group Collections
• Group Collections: Manage Groups
• Group Collections: Provision Groups

Group Collections: Manage Groups

This screen lets you define, organize, and manage group collections. The group-provisioning features of Migrator
for Notes to Exchange are applied to collections of groups, and this screen launches the Collection Wizard that
lets you define and edit those collections.
The Current group collections table shows all defined group collections. Notes Migration Manager generates
some standard, default collections from the object data exported from the Notes source directory and these default
collections are identified in the table as Auto-Defined. The Auto-Defined collections include an All Groups
collection, consisting of all Group objects found in the export table.
The table also shows whether each collection is designated as Visible (or not), a designation that determines
whether the collection appears in other tables and lists of collections elsewhere in Migrator for Notes to Exchange.
(Migrator for Notes to Exchange’s provisioning, migration and other features are applied to particular collections,
which are specified from drop-down lists or tables.) Migrator for Notes to Exchange’s Collection Wizard, where
collections are defined and collection attributes may be edited, includes a Visible check box that sets this option.
The Collection Wizard, launched from this screen, lets you define a New collection by selecting groups from
Active Directory, or by importing groups from a .tsv (tab-separated-values format) file or both. You can also Edit an
existing collection (but not an Auto-Defined collection), Copy an existing collection to a new name, and Edit the
copy.

NOTE: Although you cannot edit an Auto-Defined collection, you can Copy an Auto-Defined collection to a
new name, and Edit the copy.

You can filter the contents of the Current group collections table to show only collections associated with a
particular label by specifying the label in the Show collections labeled as drop-down list.

NOTE: Labels are a device for classifying and sorting collections by alphanumeric strings that can be
assigned to collections in the Collection Wizard that creates them. Typically labels are defined to
characterize and group subsets of collections—for example, to sort collections by an organization’s
administrative divisions, you could define labels for Engineering, IS, Marketing, R&D, Sales, and so forth. Or
you could define labels for Atlanta, Chicago, Denver, Houston, Minneapolis, and so on to sort collections by
satellite office locations. Throughout Notes Migration Manager you can sort lists and tables of collections by
label, or specify a particular label to filter a list or table of collections to show only collections that are
assigned that label.

The Collection members table in the bottom half of the screen shows the members of whatever user collection is
currently selected in the table in the top half of the screen.

To view only the collections that are associated with a particular label
• Select the label from the Show collections labeled as drop-down list.

To view the member contents of a collection

• Select the collection in the Current group collections table. Note that these Collection members are
groups, not the individual members of a group.

To view the individual members of a single group

• Select the group in the Collection members table, and click View Members.

To create a new collection

• Click New collection to launch the Collection Wizard, to select members from Active Directory, or import
members from a .tsv file, or both.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

27
Notes Migration Manager
 — OR —
• Select one or more members in the Collection members table, and click Create collection to launch the
Collection Wizard, with the selected members already added to the collection. (This feature lets you easily
define a subset collection from any existing collection.)

To edit the definition (label or members or visibility) of an existing collection

• Select the collection in the Current group collections table, and click Edit to launch the Collection
Wizard.

To copy an existing collection to a new collection under a new name (which you can edit)
• Select the collection in the Current group collections table, and click Copy.

To export all user-defined group collections in Migrator for Notes to Exchange’s SQL database
to a TSV file

NOTE: Note that this feature exports all group collections, not only the collections that are selected in the
table. This includes both auto-defined and user-defined group collections. Also, the export feature sends all
collections to a single TSV file, not to different files for different collections.

1 Click Export Collections.

The feature opens an Export Group Collections dialog box (a standard Windows Save As dialog box).
2 Use the dialog box to specify the full path and file name of the new TSV file that will contain the collections
you are exporting.
3 Click Export.
The program exports all user-defined group collections to the designated path and filename, and a
progress bar reports the feature's progress. If the feature encounters any errors or warnings, the dialog box
displays an Error Log Report option that you can click to open the log file to investigate.
4 When the feature has completed its run, click OK to dismiss the dialog box and return to the Manage Users
screen in Notes Migration Manager.

To import previously exported user-defined group collections from a TSV file into Migrator for
Notes to Exchange’s SQL database
1 Click Import Collections.
The feature opens an Import Group Collections dialog box (a standard Windows Open dialog box).
2 Use the dialog box to find and specify the TSV file that contains the collections you want to import.
3 Click Import.
The program imports the collections in the designated TSV file, and a progress bar reports the feature's
progress. If the feature encounters any errors or warnings, the dialog box displays an Error Log Report
option that you can click to open the log file to investigate.
4 When the feature has completed its run, click OK to dismiss the dialog box and return to the Manage Users
screen in Notes Migration Manager.

Group Collections: Provision Groups

This screen lets you run the Groups Provisioning Wizard which configures a task to provision the groups in a group
collection into Active Directory. You can perform the provisioning task immediately or you can schedule the task to
run at a later time.
• Show collections labeled as: Filters the contents of the Select collection list to show only collections
associated with a label, You select the label in the Show collections labeled as drop-down list. Labels are
a device for classifying and sorting collections. For information, see the note under Group Collections:
Manage Groups.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

28
Notes Migration Manager
 • Select collection to provision: Use this drop-down list to specify the collection you want to provision.
• Provision groups: Launches the Groups Provisioning Wizard.
• Summary of provisioning run (table, not labeled): Reports results of most recent provisioning run, by
numbers of objects of various types.
• Next scheduled run for collection: Displays the next scheduled run of a group-provisioning task for the
selected collection, as configured by a previous run or as amended on the Manage Scheduled Operations
screen.

User Collections
• User Collections: Manage Users
• User Collections: Manage Design Classes
• User Collections: Send PAB Replicator
• User Collections: Locate Notes Data Stores
• User Collections: Provision Users
• User Collections: Migrate User Data

User Collections: Manage Users

This screen lets you define, organize, and manage user collections. Provisioning, migration, and other functions of
MNE are applied to collections of users.This screen launches the Collection Wizard that lets you define and edit
the collections.
The Current user collections table shows all defined user collections. Notes Migration Manager generates some
standard, default collections from the object data exported from the Notes source directory and these default
collections are identified in the table as Auto-Defined. The Auto-Defined collections include an All Users collection,
that consists of all the user objects found in the export table.
MNE can also generate collections of users logically grouped by their Notes ACL and delegation data, so that
users with stronger work associations can be migrated together to minimize business disruptions during the
transition. For information, see To generate Smart Collections.
The Current user collections table also shows whether each collection is designated as Visible, a designation
that determines whether the collection appears in other tables and lists of collections elsewhere in MNE. The
Collection Wizard, where you define collections and you can edit collection attributes.
You can filter the contents of the Current user collections table to show only collections associated with a particular
label by selecting the label in the Show collections labeled as drop-down list.

NOTE: Labels are a device for classifying and sorting collections by alphanumeric strings that can be
assigned to collections in the Collection Wizard. Typically labels are defined to group subsets of
collections—for example, to sort collections by administrative divisions, you could define labels for
Engineering, IS, Marketing, R&D, Sales, and so on. Or you could define labels for Atlanta, Chicago, Denver,
Houston, Minneapolis, and so on, to sort collections by geographic office locations. Throughout Notes
Migration Manager you can sort lists and tables of collections by label or specify a label to filter a list of
collections, to show only the collections that are assigned that label.

The Collection Wizard lets you define a New collection by selecting members from Active Directory, or by
importing members from a .tsv (tab-separated-values format) file, or both. You can also edit an existing collection
(but not an Auto-Defined collection), or copy an existing collection to a new name and edit the copy.
The Collection members table in the bottom of the screen shows the members of the user collection currently
selected in the table.

To view only the collections that are associated with a particular label
• Select the label from the Show collections labeled as drop-down list.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

29
Notes Migration Manager
To view the member contents of a collection
• Select the collection in the Current user collections table.

To create a new collection

• Click New collection to launch the Collection Wizard, to select members from Active Directory, or import
members from a .tsv file, or both.
- OR -
• Select one or more members in the Collection members table and click Create collection to launch the
Collection Wizard with the selected members added to the collection. This feature lets you define a subset
collection from any existing collection.

To generate Smart Collections

NOTE: This feature generates collections of users logically grouped by their Notes ACL and delegation data,
so that users with stronger work associations can be migrated together to minimize business disruptions
during the transition period.

1 Click Smart Collections.

This button launches the Smart Collections Generator where MNE starts reading the user source ACL
data, sorting the users by their ACL associations, and determining logical break points between suggested
collections. When the generator finishes, the suggested Smart Collections appear in the left pane and the
controls at the bottom of the window are enabled.

NOTE: Depending on the size of your user "universe" and other factors in your local environment,
this process can take several minutes or longer. You can click Cancel to cancel the feature.

The suggested Smart Collections that appear in the list are hypothetical (not yet defined to MNE) until you
explicitly save them (in step 5).
2 Optional: Review the collection members. You can click on a collection in the left pane to view its members
in the right pane.
3 Optional: Redistribute members among the collections by adjusting the maximum number of members per
collection. By default, the generator sets the maximum size at whatever number of members permits
grouping without dividing ACL-related members across two collections. If you prefer a different per-
collection maximum, use the track bar (a horizontal slide control) below the collections table to try different
values until you are satisfied with the result. However, a smaller number will divide ACL-related members
across the break point between two collections.
4 Optional: To hide previously defined Smart Collections from the list in the Manage Users table, click the
check box: [X] Hide previously generated Smart Collections.
5 When the Smart Collections are defined, click Save to save them in MNE. When MNE posts its
confirmation note, click OK to return to the Manage Users screen.

NOTE:
• Once created and saved, Smart Collections can be edited or renamed the same as user-defined
collections.
• Smart Collection names are generated. If a collection already exists with the same name, MNE will
rename and hide the earlier collection (whether or not you select the Hide check box). No two
collections can have the same name.
• MNE applies the label “Smart Collection” to all Smart Collections so you can filter the collections table
(on the Manager Users screen) to show only Smart Collections.
• Smart Collections errors and debug info are logged in the migration console log.

To edit the definition (label or members) of an existing collection

• Select the collection in the Current user collections table and click Edit to launch the Collection Wizard.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

30
Notes Migration Manager
To copy an existing collection to a new collection under a new name (which you can edit)
• Select the collection in the Current user collections table and click Copy.

Editing user collections and user collection membership

You can export the user collections to a TSV file and use a program such as Microsoft Excel to edit the file. Use
this procedure to edit user collections and user collection membership.
NOTE: This feature exports all user collections, not only collections that are selected in the table. This
includes both auto-defined and user-defined user collections. The export feature sends all collections to a
single TSV file, not to different files for different collections.

The Collection Wizard lets you use the exported directory data (in the SQL database) to define the member
contents of user and group collections. A collection is a defined subset of the users or groups that were found and
exported from the Notes/Domino source. The provisioning, migration, and other features of MNE are applied to
collections of users and groups, and you use the Collection Wizard ito define these collections.

To export all user collections to a file and make changes

1 Click Export Collections.
2 Specify the full path and file name of the new TSV file that will contain the collections you are exporting.
3 Click Export.
The program exports all user-defined collections to the specified path and filename. If the feature
encounters any errors or warnings, the dialog box displays an Error Log Report button that you can click
to open the log file to investigate.
4 Click OK to return to the Manage Users screen.
Edit the file.
5 Open the file in a TSV file editor and make the required changes.
Import the file.
6 Click Import Collections.
The Import User Collections window opens (a standard Windows Open dialog box).
7 Use the dialog box to find and specify the TSV file that contains the collections you want to import.
8 Click Import.
The program imports the contents of the TSV file and a progress bar shows progress. If the feature
encounters errors or warnings, the dialog box displays an Error Log Report button that you can click to
open the log file to investigate.
9 Click OK to return to the Manage Users screen in Notes Migration Manager.

To edit user properties in a collection

You can export a specific set of users belonging to a collection to a TSV file and use a program such as Microsoft
Excel to edit user properties.
You can edit the exported directory data, and the data associated with defined user collections, for a variety of
reasons including:
• To manually edit one or more addresses before using them for the migration—for example, if your
organization is consolidating on a new SMTP domain as part of the migration process.
• To populate the SearchKey column with appropriate per-user values for the Provisioning Wizard.
• To specify the locations of user PABs, if they reside in diverse, per-user locations.
• To prepare the data so the Data Migration Wizard can properly associate the resource accounts with the
user accounts, and properly enable mailboxes—if your target environment is configured for a resource
forest and a user forest, with corresponding user accounts.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

31
Notes Migration Manager
 NOTE: The SQL database will not accept any entirely new rows or columns. You can only add, edit
and delete the contents of cells that already exist in the table. If you add or delete an entire column or
row, the program will ignore the change when you import the data back into the database.

The names and definitions of column headings in the SQL database table are documented in chapter 4 (Directory
Export Wizard) of this Administration Guide (see Exported Data Elements in the SQL database).
Some of the columns in these data tables contain critical values that must not be edited, while others can be edited
as needed, and still others must be edited to implement certain strategic options or accomplish certain program
features.

NOTE: Each run of the Directory Export Wizard overwrites the current contents of Migrator for Notes to
Exchange’s SQL database (including any imported TSV values) with data newly exported from the Domino
Directory—except that you may choose whether the wizard should overwrite or keep any
DominoServerAddress values that have been changed by a TSV import. The wizard’s default is to preserve
TSV- imported DominoServerAddress values, but the Directory Export Wizard offers an option to overwrite
them.

NOTE: After editing data by these Export/Import features, you may want to run the Notes Data Locator
Wizard to verify that you have entered the data correctly (no typos or malformed notations), that the
necessary certifications are in place, and that Migrator for Notes to Exchange can access the NSFs.

Export a user collection in the MNE SQL database to a TSV file.

1 Select a collection in the Current user collections table

2 Click Export Members to TSV.
The Export Objects window opens (a standard Windows Save As dialog box).
3 Use the dialog box to specify the full path and file name of the new TSV file that will contain the collection of
users you are exporting.
4 Click Export.
The program exports the user-defined collection to the designated path and filename, and a progress bar
reports progress. If the feature encounters errors or warnings, the dialog box displays an Error Log Report
option that you can click to open the log file to investigate.
5 When the feature has completed its run, click OK to dismiss the dialog box and return to the Manage Users
screen.
Edit the file.
6 Open the file in a TSV file editor and make the required changes.
Import the file.
7 Click Import Members from TSV.
The Import Objects window opens (a standard Windows Open dialog box).
8 Use the dialog box to find and specify the TSV file that contains the collection you want to import.
9 Click Import.
The program imports the contents of the designated TSV file, and a progress bar reports progress. If the
feature encounters errors or warnings, the dialog box displays an Error Log Report option that you can
click to open the log file to investigate.
10 When the feature has completed its run, click OK to dismiss the dialog box and return to the Manage Users
screen in Notes Migration Manager.

User Collections: Manage Design Classes

This screen lets you identify any non-standard Notes design classes that may be associated with Notes NSF files,
but that the wizards would not otherwise recognize because their names are different from the Notes-standard

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

32
Notes Migration Manager
design classes. The Design Classes table on this screen identifies all such non-standard design classes, and
associates each design class with one or more particular data types: mail, archives, or PABs.
Remember to click Apply after you Add or Remove an item from the table. The program will not read or save any
new information or changes until Apply is clicked.

To add a new design class to the table

1 Click Add.
2 The program displays an Add Design Class dialog box.
3 In the Add Design Class dialog box: Type the Design class name, and select the appropriate check boxes
to associate the new design class with one or more of MailFiles, PABs, or Archives. Click OK to add the
new design class to the table and dismiss the dialog box.
4 Click Apply to save the updated Design Classes table to the SQL database.

To remove a not-yet-Applied design class from the table

1 In the Design Classes table: Select the item you want to remove.
Note: You can remove only design classes that have not yet been applied to the database (by clicking
Apply). A design class that has not yet been applied appears in italics in the table.
2 Click Remove.
3 Click Apply to save the updated table to the SQL database.

Add Design Class dialog box

In the Add Design Class dialog box: Type the Design class name, and select the appropriate check boxes to
associate the new design class with one or more of MailFiles, PABs, or Archives. Click OK to add the new design
class to the table and dismiss the dialog box.

User Collections: Send PAB Replicator

This screen lets you run the Send PAB Replicator Wizard, which sends a special email form to all users in a
particular user collection, so that users can copy all their personal address books (PABs) to a centralized Notes
server directory, where the program can find them to migrate them.
• Collections labeled as: A drop-down list that lets you filter the contents of the User collection list (below),
to show only collections associated with the particular label specified here. Labels are a device for
classifying and sorting collections. For more information, see the note under User Collections: Manage
Users.
• User collection: Use this drop-down list to specify the collection of users to whom you want the PAB
Replicator sent.
• Send PAB Replicator: Launches the Send PAB Replicator Wizard for the designated user collection.

User Collections: Locate Notes Data Stores

This screen lets you run the Notes Data Locator Wizard, which configures a task to locate Notes data stores for a
particular user collection, and refresh the statistics for any data stores that were previously located for users in the
selected collection. You may tell the wizard to perform the task immediately following its configuration, or the
wizard will let you schedule the task to run at a later time.
• Collections labeled as: A drop-down list that lets you filter the contents of the user collection list to show
only collections associated with the particular label specified here. Labels are a device for classifying and
sorting collections. For more information, see the note under User Collections: Manage Users.
• User collection: Use this drop-down list to specify the collection for which you want to locate data stores.
• Locate data stores: Launches the Notes Data Locator Wizard for the designated user collection.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

33
Notes Migration Manager
 • Data stores table: The list of all found data stores (found by the Notes Data Locator Wizard).

NOTE: If the Notes Data Locator Wizard does not find users' NSF files, but you know their locations,
you can add the per-user NSF paths to the SQL database so the Data Migration Wizard can migrate
them. The procedure to edit the contents of a SQL Server data table is explained in Appendix A,
under How Do I Specify Per-User Locations for Notes Source Data? Within the data table, the
MailFilePath column defines the specific paths and NSF filenames to users' mail files. For example:
\\server\home\user\jdoe.nsf
\\server\home\user

• Next scheduled run for collection: Displays the next scheduled run (if any) of this task for the selected
collection, as configured by a previous run of the wizard or as amended on the Manage Scheduled
Operations screen.

NOTE: Statistics reported by Migrator for Notes to Exchange are based on uncompressed data sizes
provided by the Notes APIs. The APIs extract data in compressed form and provide the data to Migrator for
Notes to Exchange in an uncompressed state. Data volumes reported by Migrator for Notes to Exchange are
often higher than the values observed natively in Notes or transferred over the network to the migration
servers.

User Collections: Provision Users

This screen lets you run the Provisioning Wizard, which merges duplicate objects in AD into a single mail-enabled
account per user. The merge feature will be applied to a particular user collection, specified on this screen.
If you used the Quest Coexistence Manager for Notes (CMN) Directory Connector to synchronize the source and
destination directories, and if the migrating users were already using AD security objects for network
authentication, the dirsync should have been configured to create new AD contacts, which now correspond to the
existing user objects. In this case, you should use MNE Provisioning Wizard to consolidate such duplicates before
any data is migrated.
The Provisioning Wizard merges information from AD contacts (generated by the CMN Directory Connector) into
the corresponding users’ Active Directory accounts, and deletes the contacts, to create a single mail-enabled
security object per user in AD. If you require this feature, do it before you attempt to migrate any users.
Before running the Provisioning Wizard:
• You must verify that the SQL database contains a column whose per-contact values are unique and
correspond to the values for the pertinent AD object attribute. If the wizard does not offer a suitable column
in its drop-down list (see the Provisioning Wizard chapter of the Admin Guide), you must manually enter the
appropriate per-contact data values into the SearchKey column that will correspond to the AD attribute
values of the associated AD objects. This procedure also is explained in the Provisioning Wizard chapter of
the Admin Guide.
• Collections labeled as: A drop-down list that lets you filter the contents of the user collection list, to show
only collections associated with the label specified here. Labels are a device for classifying and sorting
collections. For information, see the note under User Collections: Manage Users.
• User collection: Use this drop-down list to specify the collection whose objects you want to merge into AD.
• Provision: Launches the Provisioning Wizard for the designated user collection.

User Collections: Migrate User Data

This screen lets you run the Data Migration Wizard, which configures a task to migrate all users in a particular user
collection. You may tell the wizard to perform the migration task immediately following its configuration, or the
wizard will let you schedule the task to run at a later time.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

34
Notes Migration Manager
 NOTE: Smart resource reservation detection: The Migration Wizard detects an attempt to migrate
calendar data for a collection in which some objects are not classified as resources in Migrator for Notes to
Exchange's database, when [Notes] MigrateReservationsAlways is enabled (set to 1). In that case, the
wizard presents a popup warning explaining that the calendars of non-resource objects may not migrate
correctly, and suggesting that MigrateReservationsAlways be disabled (set to 0) unless the admin is certain
that all objects in the collection are resources. (This feature offers the option of ignoring
MigrateReservationsAlways=1.)

• Collections labeled as: A drop-down list that lets you filter the contents of the User collection list (below),
to show only collections associated with the particular label specified here. Labels are a device for
classifying and sorting collections. For more information, see the note under User Collections: Manage
Users.
• User collection: Use this drop-down list to specify the collection of users you want to migrate.
• Migrate: Launches the Migration Wizard for the designated user collection.
• Next scheduled run for collection: Displays the next scheduled run (if any) of this task for the selected
collection, as configured by a previous run of the wizard or as amended on the Manage Scheduled
Operations screen.

Monitor Migration Progress

The screen displays a table that lists all tasks that are currently running or that have run in the preceding two days,
and shows the current status of each.

Gather Desktop Statistics

This screen runs the Self-Service Desktop Migration Statistics (SSDM) Collection Wizard which gathers the run-
result statistics generated by the SSDM and adds the data to the SQL database. Each time the SSDM is run, it
writes a summary of its results to a log file and the log file is the data source for the SSDM Statistics Collection
Wizard.

NOTE: Statistics reported by MNE are based on uncompressed data sizes provided by the Notes APIs. The
APIs extract data in compressed form and provide the data to <NE in an uncompressed state. Data volumes
reported by MNE are often higher than the values observed natively in Notes or transferred over the network
to the migration servers.

The wizard may perform the data-gathering task immediately following its configuration, or you can schedule the
task to run at a later time.

NOTE: This wizard can collect per-desktop statistics if the Post user logs to the central directory check
box is selected in the Shared Directories Configuration screen. If the check box is empty, the SSDM writes
its log files to the individual user local temp directories where the files are unavailable to the wizard.

• Statistics last gathered: Reports the date and time that per-desktop statistics were last gathered.
• Self-Service Desktop Migration statistics directory (UNC Path): The full path for the directory that
contains the central log file for the SSDM or click Browse to locate and specify a path. This is the same as
the directory for central log and status files that you entered in the Log Directory Configuration screen.
• Gather statistics: Launches the SSDM Statistics Collection Wizard.
• Next scheduled run for collection: Displays the next scheduled run of this task as configured by a
previous run or as amended on the Manage Scheduled Operations screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

35
Notes Migration Manager
Manage Scheduled Operations
This screen lets you edit the scheduled task runs (as defined by wizards launched from other screens), to change
the run times or run frequencies, or to run immediately.

NOTE: This Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, as explained in chapter 13. The Task
Scheduler checks the SQL database to see whether any tasks are scheduled to run since the last check,
and runs any tasks it finds. See Using the Qsched.exe task-scheduling utility on page 116 for details on the
Task Scheduler.

Filter list:
• Operation type: Use this drop-down list to specify a task that you want to add to the Tasks table below.
Tasks in the Tasks table can be scheduled, edited, or run immediately, as explained below.
• Collections labeled as: A drop-down list that lets you filter the contents of the Collection name list to show
only collections associated with the specified label. Labels are a device for classifying and sorting
collections (see the note under User Collections: Manage Users).
• Collection name: Use this drop-down list to specify the collection to which you want.
Tasks table:
• Reschedule: Specify the date and time that you want the selected task to run. The task runs for all objects
in the collection even if some objects in the collection were processed in an earlier run of the task.
• Run now: Run the selected task immediately. The task will run for all objects in the collection, even if some
objects in the collection were processed in an earlier run of the task.

TIP: If the MNE Task Scheduler experiences logon failures when trying to start the service, see How do I
troubleshoot service startup permissions? in the How Do I ...? in Appendix A in this guide.

View Summaries
This screen lists an assortment of available statistics to help you plan for the migration and track its progress. Click
View summary to view a pop-up display of the associated information.

NOTE: Statistics reported by MNE are based on uncompressed data sizes provided by the Notes APIs. The
APIs extract data in compressed form and provide the data to MNE in an uncompressed state. Data volumes
reported by MNE are often higher than the values observed natively in Notes or transferred over the network
to the migration servers.

The first five summaries in the list provide pre-migration assessments of your existing Notes infrastructure. These
summaries derive their data from runs of the two Notes Discovery Wizards, followed by the Directory Export
Wizard, and the Notes Data Locator Wizard (for the All Users and Resources collection):
• User and resource details: A valuable information resource for migration planning, this summary lists all
resources and user mailboxes eligible for migration and reports the number of items and size of the data
store in Notes, identifying information such as department, location and server. Use this information to
define collections of resources and mailboxes to be migrated together. Typically, collections contain users
in the same department and location. The use of the data store size estimates permits you to create
collections of appropriate sizes so they can be completed in your intended time frame.
• Distribution list details: This summary shows the groups (distribution lists) defined in the Notes
environment, which MNE can migrate to Exchange. Information such as owner, group type, Notes and
Internet Address can help you collect similar groups together and have MNE provision them in the same
Organizational Unit (OU) in Active Directory. Many administrators prefer this approach instead of placing an
extremely large number of groups into the same OU container.
• Internet domains: Sometimes, usually in large Notes installations, an additional Internet domain is
configured on some servers. In cases such as mergers or acquisitions, the Notes infrastructure may
support some domains that are unknown to the staff performing the migration. This summary documents

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

36
Notes Migration Manager
 domains that are currently configured on the Notes servers and identifies whether each domain is
considered primary or secondary by Notes, so you can configure Internet domains for the Exchange
environment.
• Notes domains: Large Notes installations sometimes contain multiple Notes domains, some of which may
be unknown to migration administrators—for example, in the case of a merger or acquisition.
Administrators should carefully review this summary to ensure it includes all Notes domains. The Data
Migration Wizard can migrate only the servers and domains listed in this summary. For additional domains
not listed, use the NAB Discovery Wizard to add an appropriate Name and Address Book to the MNE
configuration.
• Datastore design classes: Notes permits the use of different design classes to support different types of
data. Some examples include STDR6Mail for mail, and STDR6PersonalAddressBook for personal address
books. Notes also supports the creation of custom design classes, either by creating a new one or making
modifications to an existing design class. When migrating data, MNE uses the design classes to determine
the types of data and how they should be mapped to Exchange. All default design classes are mapped.
This report shows you all the different design classes in use in the data scanned by MNE. For each class,
the summary indicates if it is mapped or not, and identifies a specific example of a data store using each
design class. If your enterprise has customized data classes, review the unmapped data classes to
determine if they contain standard data, such as messages and calendar data, and if they should be
mapped for migration. If expected design classes are missing from the summary, you can add them to the
database in the User Collection: Manage Design Classes screen of Notes Migration Manager.
Other summaries are migration status summaries that help you understand what is happening during a migration:
• User migration status per collection: This summary reports, for each user or resource in the collection,
the amount of data migrated and how many errors were encountered. Use this summary to identify
mailboxes and resources that require cleanup, re-migration, or other attention. You can also use the data to
calculate throughput and estimate the throughput of subsequent migrations. Adjusting the size of different
collections based upon these numbers lets you optimize migration resources.
• Distribution list provisioning: This summary shows which distribution lists have and have not been
provisioned, and also documents any changes to previously migrated lists, so you can use Notes as the
authoritative source for a list and periodically re-migrate the list.
• Datastore status: This summary reports the migration status of specific user mailboxes or resource
reservation databases. You can report on NSF files specific to a server, or select specific user mailboxes or
resource reservation databases and determine if and when they were migrated, error counts, and how
much data was migrated. You can filter results for runs with errors, and group migration runs by user and
datastore.
From the pop-up display, you can:
• Export to TSV: Export the displayed data to a TSV-format (tab-separated-values) data file.
• Refresh Data: Regenerate the display, to include any new data from tasks currently running or recently
concluded.
• OK: Close the pop-up window.
If the summary pertains to a particular collection, you can use the Collections drop-down list to view the data
associated with some other collection.

View Logs
This screen launches the Log Viewer to view the program log file associated with a particular task run. You can
view the log of any task run by selecting it from the Task runs table and clicking View log file. You build the Task
runs table by defining the filters for its contents. In most cases, a combination of task type and the collection to
which the task was applied limits the run list to a manageable length.
Filter list:
• Operation type: Use this drop-down list to specify a task whose runs you want to add to the Task runs
table. You can filter the displayed list by collection.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

37
Notes Migration Manager
 • Collections labeled as: A drop-down list that lets you filter the contents of the collection name list to show
only collections associated with the specified label. Labels are a device for classifying and sorting
collections. For more information, see the note under User Collections: Manage Users.
• Collection name: Use this drop-down list to specify the collection to which the task was applied.
Task runs table:
• View log file: Launches the Log Viewer for the selected task run.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

38
Notes Migration Manager
 2
NABS Discovery Wizard
• Introduction
• Wizard process screens

Introduction
The NABs Discovery Wizard searches the Notes/Domino server to locate all Notes NABs (Name and Address
Books). The Directory Export Wizard and the Internet Domains Discovery Wizard extract critical directory
information from the NABs, which is read by the MNE provisioning and migration wizards so that they can perform
their tasks.
Field definitions and application notes for the wizard’s screens appear in the sections that follow.

Wizard process screens

The following sections describe the screens that can be displayed and the configuration settings for each screen.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable this capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.
The Advanced Settings option is a toggle that determines whether the wizards will let you open and edit Task
Parameters. If the feature is enabled, this extra Customize Configuration screen will appear at the start of the
screen sequence for any Wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file, although the parameters are stored as
part of the task definition within the SQL database. The Customize Configuration feature copies the current
parameter settings from the SQL database into a text document in Windows' Notepad, so you can use the
Notepad text-editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task configuration settings into Windows Notepad.
2 Find the pertinent [SectionName] for the parameter you want to add, or whose value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is very important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

39
NABS Discovery Wizard
 4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter value(s) back into the SQL database.

Specify Notes Login Information

This screen appears only if the Always use these settings check box is cleared in the Notes Server
Configuration screen of Notes Migration Manager.
These fields specify Notes server access credentials, to authenticate the administrator by whose authority the
program will perform its administrative functions:
• Domino Server: Enter the name of the Domino server to be connected.
• User ID file: Click Browse to find and specify the path and filename of the User ID file, or type or paste the
path and filename into the text box.
• Password: Type the password associated with the User ID file.
Enter the requested information, and click Next.

Generating Task
No information is entered into this screen.
This screen reports the wizard's progress as it determines the details and associated work items of the task you
have prepared it to create. You can review (in the next screen) the details and associated work items, and decide
whether to create the task, or go back and change specifications that define the task.
When this generation process is complete, the wizard displays the next screen.

Configuration Summary
This screen shows a summary of the task configuration you have specified, as defined by the Notes server
information and access credentials entered in previous screens.
Review this information to confirm that it describes the task you want to create. If you want to change anything,
click Back to return to earlier screens in this Wizard, to change values as necessary, or click Cancel to cancel the
wizard and return to the Find NABs screen in Notes Migration Manager. From earlier screens within this wizard,
you can click Next to return to this Configuration Summary screen.
Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and filename
for the text file.
Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the destination
printer.
Run: Creates the task as defined in the configuration summary, and immediately run the task. When you click
Run, the wizard displays a screen that reports its progress as it creates the task and a screen that reports its
progress as the task runs. When the task run is complete, the wizard displays a screen that reports the statistical
results of the task.

Creating Task
This screen reports the wizard progress as it creates the task defined on the Configuration Summary screen.
When the task-creation process is complete, the wizard clears this screen and runs the newly created task.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

40
NABS Discovery Wizard
Task Progress
The screen reports the program's progress as it performs the defined task.
You can click Cancel to cancel the task before it completes.
When the process is complete, the program displays its Task Completed screen to report the results.

Task Completed
No information is entered into this screen. The screen reports the results of the task run.
This screen may also display an Error Log Report option if the program encountered any errors during its run. If
Error Log Report does appear, click it to view the program log and assess the severity of the errors. The Error
Log Report option launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and
resolve the errors.
When you are finished using the Error Log Report feature (or if the Error Log Report button does not appear),
click Exit to exit the wizard.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

41
NABS Discovery Wizard
 3
Internet Domains Discovery Wizard
• Introduction
• Wizard process screens

Introduction
The Internet Domains Discovery Wizard extracts all Internet domains it finds within the Notes NABs (Name and
Address Books) that were located by the NAB Discovery Wizard. These domains are used to generate address
aliases for all users, so that Exchange can recognize and correctly route mail sent to the users' old addresses.
Field definitions and application notes for the wizard’s screens appear in the sections that follow.

Wizard process screens

The following sections describe the screens that can be displayed and the configuration settings for each screen.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable the capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.
The Advanced Settings option is a toggle that determines whether the wizards let you open and edit Task
Parameters. If the feature is enabled, the Customize Configuration screen is displayed at the start of the screen
sequence for any wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file although the parameters are stored as
part of the task definition in the SQL database. The Customize Configuration feature copies the current parameter
settings from the SQL database into a text document in Windows Notepad, so you can use the Notepad text-
editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task configuration settings in Windows Notepad.
2 Find the pertinent [SectionName] for the parameter you want to add, or the value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

42
Internet Domains Discovery Wizard
 4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter value(s) back into the SQL database.

Specify Notes Login Information

This screen appears only if the information it requests was not already collected in the Notes Migration Manager in
the Notes Server Configuration screen.
These fields specify the Notes server access credentials used to authenticate the administrator by whose authority
the program performs its administrative functions:
• User ID file: Click Browse to find and specify the path and filename of the User ID file, or type or paste the
path and filename into the text box.
• Password: Type the password associated with the User ID file.
Enter the requested informations and click Next.

Generating Task
No information is entered into this screen.
This screen reports the wizard progress as it determines the details and associated work items of the task you
prepared it to create. You can review (in the next screen) the details and associated work items, and decide
whether to create the task, or go back and change any specifications that define the task.
When this generation process is complete, the wizard displays the next screen.

Configuration Summary
This screen shows a summary of the task configuration you specified, as defined by the Notes server information
and access credentials entered in previous screens.
Review this information to confirm that it describes the task you want to create. To change anything, click Back to
return to previous screens, to change values as necessary, or click Cancel to end the wizard and return to the Find
NABs screen in Notes Migration Manager. In previous screens, you can click Next to return to this Configuration
Summary screen.
Save As: Lets you save the summary information to a text file. Follow the prompts to specify a path and filename
for the text file.
Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the destination
printer.
Run: Creates the task as defined in the configuration summary and run the task. When you click Run, the wizard
displays a screen that reports its progress as it creates the task and a screen that reports its progress as the task
runs. When the task run is complete, the wizard displays a screen that reports the statistical results of the task.

Creating Task
No information is entered into this screen. This screen reports the wizard's progress as it creates the task defined
on the Configuration Summary screen.
When the task-creation process is complete, the wizard clears this screen and runs the newly created task.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

43
Internet Domains Discovery Wizard
Task Progress
No information is entered into this screen. The screen reports the program's progress as it performs the defined
task.
You can click Cancel to cancel the task before it completes.
When the process is complete, the program displays the Task Completed screen to report the results.

Task Completed
No information is entered into this screen. The screen reports the results of the task run.
This screen can also display an Error Log Report button if the program encountered errors during its run. If the
Error Log Report button appears, click it to view the program log and assess the severity of the errors. The Error
Log Report button launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and
resolve the errors.
When you are finished, click Exit.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

44
Internet Domains Discovery Wizard
 4
Directory Export Wizard
• Introduction
• Wizard process screens
• Exported data elements in the SQL database

Introduction
The Directory Export Wizard gathers user information from the Domino servers to create SQL Server data tables
that provide critical input data to the MNE provisioning and migration wizards. These wizards use this data to:
• Provision users and groups in Active Directory (AD).
• Merge Exchange contacts into corresponding AD accounts to create a single mail-enabled security object
per user.
• Convert Notes-format addresses in messages, address books, and contacts to the appropriate Internet
address for each user.
The Directory Export Wizard is run before the first run of any of the MNE provisioning or migration wizards.
Throughout the transition period, the Directory Export Wizard can be re-run as necessary to update the data files,
to accommodate any staff changes that are recorded in Domino during the transition.
You can configure the wizard to perform the export task immediately following configuration or you can schedule
the task to run at a later time.
A reference list of the wizard Exported data elements in the SQL database appears at the end of this chapter,
following the field definitions and application notes in the sections that follow.

Wizard process screens

The screens in the Directory Export Wizard are:
• Customize Configuration
• Configure Directory Export Updates of TSV-Imported Values
• Specify Notes Login Information
• Generating Task
• Configuration Summary
• Creating Task
• Specify Task Schedule
• Schedule Summary
• Task Progress
• Task Completed

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

45
Directory Export Wizard
Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable this capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.
The Advanced Settings option is a toggle that determines whether wizards allow you to open and edit Task
Parameters. If the feature is enabled, the Customize Configuration screen appears at the start of the screen
sequence for any wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file, though the parameters are stored as
part of the task definition in the SQL database. The Customize Configuration feature copies the current parameter
settings from the SQL database into a text document in Windows Notepad so you can use the Notepad text-editing
features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task's configuration settings into Windows Notepad.
2 Find the [SectionName] for the parameter you want to add, or whose value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is very important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter value(s) back into the SQL database.

Configure Directory Export Updates of TSV-

Imported Values
This screen appears only when a previous TSV import has updated one or more DominoServerAddress values.
(The Export Notes Directory screen in Notes Migration Manager lets you export SQL data to a TSV file, edit the
contents, and import the changes back into the SQL database.)
The Directory Export Wizard overwrites the current contents of the MNE SQL database with the newly exported
data from the Domino Directory, except that you can choose whether the wizard overwrites or keeps any of the
DominoServerAddress values that were changed by the TSV import. The wizard default is to preserve any TSV-
imported values but this screen lets you overwrite the values with new data from the Domino Directory.
The option appears on the screen as two mutually exclusive radio buttons:
Please choose whether you want this run to update ‘DominoServerAddress’ values:
O Keep existing modified ‘DominoServerAddress’ values imported from TSV
O Replace existing ‘DominoServerAddress’ values
The first option is selected by default, but you can select the other option to overwrite the TSV-imported values.
When the option you want is selected, click Next.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

46
Directory Export Wizard
Specify Notes Login Information
This screen appears only if the login information was not already collected in Notes Migration Manager (in the
Notes Server Configuration screen).
These fields specify Notes server access credentials used to authenticate the administrator by whose authority the
program performs its administrative functions:
• Domino Server: Enter the name of the Domino server to be connected.
• User ID file: Click Browse to find and specify the path and file name of the User ID file or enter the path
and file name into the text box.
• Password: Enter the password associated with the User ID file.
Click Next.

Generating Task
This screen reports the wizard progress as it determines the process details and associated work items of the task
you have prepared it to create. You can review (in the next screen) the details and associated work items, and
decide whether to create the task, or go back and change any of the specifications that define the task.
When this generation process is complete, the wizard displays the next screen.

Configuration Summary
This screen shows a summary of the task configuration you specified, as defined by the Notes server information
and access credentials previously entered and the NABs and domains specified in the Notes Migration Manager.
Review the information to confirm that it describes the task you want to create. To make changes, click Back to
display the earlier screens and change the values, or click Cancel to cancel the wizard and display the Export
Notes Directory screen in Notes Migration Manager. From earlier screens in this wizard, you click Next to return to
this screen.
Two buttons offer the following options:
• Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and
filename for the text file.
• Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the
destination printer.
When you are satisfied that the displayed summary describes the task you want to create, click Next to create the
task.
The wizard displays a screen that reports its progress as it creates the task and clears the screen when the
process is complete.

Creating Task
This screen reports the wizard progress as it creates the task that you defined
When the task-creation process is complete, the wizard displays the Specify Task Schedule screen in which you
can schedule task runs for the newly created task.

Specify Task Schedule

This screen lets you schedule the task you created.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

47
Directory Export Wizard
 NOTE: The Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, as explained in chapter 13 of the Migrator
for Notes to Exchange Administration Guide. The Task Scheduler checks the SQL database to see whether
any tasks have been scheduled to run since the last check, and runs any such tasks it finds. See chapter 13
for details on the Task Scheduler.

The drop-down list at the top of the screen offers these scheduling options:
• Now on this computer: Runs the task when you click Next. The other scheduling controls on the screen
appear grayed out (unavailable) since they do not apply. Click Next to display the Task Progress screen.
• One or more times, as indicated below: The task will run one or more times, according to your
scheduling entries in this screen. If you select this option you must also specify where and when you want
the task to run.
• Manually: The task will not run or be scheduled at all. The other scheduling controls on the screen appear
grayed out (unavailable), since they do not apply. Click Next to display the Schedule Summary screen.
• Once: The task runs only once and not repeat. You can specify where to run and the start date and time.
Click Next to display the Schedule Summary screen.
These scheduling controls are enabled only if One or more times... is selected in the drop-down list:
• Where to run: Select either On any computer or On a specific computer. If you choose a specific
computer, you must also specify the machine name in the adjacent drop-down list.
• When to run:
▪ Start: Specify the calendar date for the first (or only) task run.
▪ Days of the Week: Specify one or more days of the week that you want the task to run. If you select
two or more days, the first task run will occur on the first selected day occurring on or after the
specified Start date.
▪ Between ____ and ____: Specify the beginning and ending times of a range of start times for the
task to run.
▪ Select one of these options for the end date:
▫ No end date: The task runs will adhere to this schedule until someone manually ends the
series by editing this schedule definition in Notes Migration Manager (in the Manage
Scheduled Operations screen).
▫ End after __ occurrences: The task runs will adhere to this schedule until the cumulative
number of runs matches the number specified here.
▫ End by: The task runs will adhere to this schedule until the calendar date specified here.
▪ [_] Start this task only after completing: [________________________]: Select this check box if
you want this new task to run only after some other previously defined Migrator for Notes to
Exchange task has run. If you select the check box, use the drop-down list to specify which
previously defined task must precede this one.
When you have set the task schedule in these scheduling controls, click Next to display the Schedule
Summary screen.

Schedule Summary
This screen appears only if you have selected One or more times... Once or Manually as your scheduling option
on the preceding Specify Task Schedule screen. The screen shows a summary of the task schedule you specified
in the Specify Task Schedule screen, or notes that the task will be run only Manually.
Review this information to confirm that it describes the schedule you want to define. If you want to change
anything, click Back to return to the Specify Task Schedule screen, to change the schedule specification, or click
Cancel to return to the Export Notes Directory screen in Notes Migration Manager. From the preceding screen
within this wizard, you can click Next to return to this Schedule Summary screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

48
Directory Export Wizard
When you are satisfied that the displayed summary describes the task schedule you want to create, click Finish to
dismiss this screen:
• Finish: Clears this Schedule Summary screen, to return to the Export Notes Directory screen in Notes
Migration Manager.
The remaining screens documented for this Wizard are skipped if you have selected One or more times... or
Manually as your scheduling option on the preceding Specify Task Schedule screen.

Task Progress
The screen reports the program's progress as it performs the defined task. When the process is complete, the
program displays its Task Completed screen to report the results.

Task Completed
The screen reports the results of the task run.
This screen may also offer an Error Log Report button if the program encountered errors during its run. If the
button does appear, click it to view the program log and assess the severity of the errors. The Error Log Report
button launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and resolve the
errors.
Other buttons can display that allow you to view .TSV files that are created to capture data for auto-resolved
addresses or for duplicate SMTP addresses that were skipped by the wizard.
When you are finished using the Error Log Report feature or viewing any .TSV files, (or if no buttons appear),
click Exit to exit.

Exported data elements in the SQL

database
The Directory Export Wizard gathers user information from the Domino servers to create SQL Server data tables
that provide critical input data to several of the MNE wizards. These wizards use the exported data to:
• Define collections (subsets) of users and groups for provisioning and migration.
• Provision users and groups in AD and identify which AD/Exchange accounts correspond to which Notes
source accounts.
• Merge Exchange contacts into corresponding AD accounts to create a single mail-enabled security object
per user.
• Migrate user data from Notes source accounts into the correct corresponding AD/Exchange accounts.
• Convert Notes-format addresses in messages, address books, and contacts to the appropriate SMTP
(Internet) address for each user.
You might edit the exported directory data and the same data elements as they are associated with defined user
collections (but not group collections) for a variety of reasons including:
• To manually edit one or more addresses before using them for the migration—for example, if your
organization is consolidating on a new SMTP domain as part of the migration process.
• To populate the SearchKey column with appropriate per-user values for the Provisioning Wizard.
• To specify the locations of user PABs, if they reside in diverse, per-user locations.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

49
Directory Export Wizard
 • To prepare the data so the Data Migration Wizard can associate the resource accounts with the user
accounts and enable mailboxes—if your target environment is configured for a resource forest and a user
forest, with the corresponding user accounts.
Exported directory data cannot be edited directly in the SQL database. Instead, directory data can be exported
from the SQL database to a .tsv-format file, viewed and edited in Microsoft Excel, and imported back into the SQL
database from the modified .tsv file. For information about editing .tsv files, see the procedures under User
Collections on page 29.
The SQL database also stores Global Defaults and Task Parameters, and task-run schedules, project statistics,
and other information, but the reference list that follows contains only the data elements of the exported directory
data tables.
The Migrator for Notes to Exchange SQL database table column headings appear in the table in this order, left to
right:
NMEObjectGUID | DisplayName | ObjectType | SourceAddress | SourceAlias | Target-Address |
TargetAlias | PSTDir | ExchangeMailboxStore | SearchKey | SearchKey2 | MailFilePath |
PABPaths | SharedPABDirs | ArchivePaths | SharedArchiveDirs | TargetForwardingAddress |
SourceForwardingAddress | DominoServerAddress
The bulleted list below presents the same column headings in alphabetical order by their names:
• ArchivePaths: The specific UNC path and filename for a user's Notes archive file(s). Multiple archives can
be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are
given, and file ownership is not checked. If a directory (only) is specified, all archives found in the directory
are assumed to be owned by the user. Examples:
\\server\data\arch1.nsf | \\server\data\arch2.nsf
\\server\data\user\archive_jdoe.nsf
\\server\data\
• DisplayName: Notes user name of the user. Example:
John Doe
The DisplayName is copied by the Directory Export Wizard from the first value of Notes FullName attribute
that is not a DN ("CN=Joe Schmoe/O=Acme") or SMTP address (Joe.Schmoe@acme.com) or, if every
FullName is a DN or SMTP address, the "CN" portion of the first FullName that is a DN (“CN=xxx/...”).
• DominoServerAddress: Full address of Notes mail file, including server, generated by the Directory
Export Wizard by joining the Mail server and Mail file fields from Notes Person Documents, like this:
[Mail server]!![Mail file]
• ExchangeMailboxStore: The home mailbox store in Exchange for a migrating user, used when mailbox-
enabling users in the Exchange Administrative Operations of the Data Migration Wizard. If left blank, a
suitable default value is derived from the configuration settings defined for the mailbox-enabling task. In
certain circumstances, the migration administrators may want to specify per-user mailbox store
assignments for some or all users. For example:
CN=Mailbox Store (MOBE),CN=First Storage Group,CN=InformationStore,CN=MOBE,
CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=User,
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Example,DC=com

NOTE: The Exchange admin credentials for the mailbox-enabling task must have sufficient rights to
create mailboxes on the Exchange server specified in this ExchangeMailboxStore column.

NOTE: The value in the ExchangeMailboxStore column is not immediately applied to users' AD
objects when the value is imported into the SQL database. The value is applied in AD only when the
corresponding mail-enabling task is performed.

• MailFilePath: The specific path and NSF filename to a user mail file, used when an administrator knows
the specific path and NSF file name for each user. If this MailFilePath column does not exist or is left empty,
the program will find the user's mail file by appending the MailFile column value to the path entered on the
Specify Notes Data Directory screen. Example:
\\server\home\user\jdoe.nsf

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

50
Directory Export Wizard
• NMEObjectGUID: Reserved internal database identifier — do not change!
• ObjectType: Reserved internal database identifier for object type in Notes — do not change!
• PABPaths: The specific UNC path and filename for a user Notes address book. Multiple address books
can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are
given and file ownership is not checked. If a directory (only) is specified, all PABs found in the directory are
assumed to be owned by the user. Examples:
\\server\data\addr1.nsf | \\server\data\addr2.nsf
\\server\data\user\address_book.nsf
\\server\data\
• PSTDir: The directory where PSTs are stored for the user—used if each user PST will go to a separate
directory. Normally the administrator would specify a central location for the program to create all PSTs,
and the program would create a directory subtree under that. If you would rather put each PST in the user
home directory, each user home directory can be added here. For example:
\\server\home\user
• SearchKey: A user-identifying value (unique per user) that can be used by the Provisioning Wizard to
match objects for merging, as described in chapter 8 (see Provisioning Wizard). This column is not
populated by the Directory Export Wizard but can be manually populated with user-identifying values
(unique per user). The Provisioning Wizard can use these values to match objects for merging if none of
the other column options is suitable for the merge process.
• SearchKey2: A user-identifying value (unique per user) that is used by the Data Migration Wizard to
properly associate resource accounts with corresponding user accounts, and enable mailboxes (used only
when the target environment is configured for a resource forest and a user forest, with corresponding user
accounts). The wizard compares the values in the SearchKey2 column with the values of a particular AD
attribute to associate corresponding accounts, as explained in Appendix A, see How Do I Prepare the SQL
database for Mailbox-Enabling (If AD Is Configured for a Resource Forest and a User Forest)? This column
is not populated by the Directory Export Wizard, but can be manually populated with user-identifying values
as explained in Appendix A.
• SharedArchiveDirs: A file system directory or Notes server directory that contains NSF files for multiple
users. This column can be used to specify a more specific set of directories to scan for a user's data so the
application can scan a subset of a larger shared directory structure and determine the owner based on
profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure
and you are not certain that all address books belong to one user. If a file system path is specified here,
ownership is checked based on the profile documents and/or ACLs. Examples:
\\server\data\archives
\\server\data\archives\archive_jdoe.nsf
• SharedPABDirs: A file system directory or Notes server directory that contains NSF files for multiple users.
This column can be used to specify a more specific set of directories to scan for a user's data, so the
application can scan a subset of a larger shared directory structure and determine the owner based on
profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure
and you are not certain that all address books belong to one user. If a file system path is specified here,
ownership is checked based on the profile documents and/or ACLs. Examples:
\\server\data\groupdir
\\server\data\groupdir\address_book.nsf
• SourceAddress: Primary Notes address of the user. Example:
John Doe/MyOrganization
The SourceAddress value is derived by the Directory Export Wizard from the first value of Notes’ FullName
attribute that is a DN ("CN=Joe Schmoe/O=OurCompany"), with "CN=" and "O=" stripped out (leaving "Joe
Schmoe/OurCompany").
• SourceAlias: Any additional Notes addresses for the user. This field may contain zero, one, or more than
one alias; multiple aliases are separated by a percent symbol (%). Example:
John Doe%Jdoe%Johnny D

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

51
Directory Export Wizard
• SourceForwardingAddress: Notes-format address used to forward mail from Exchange to Notes, used in
the Data Migration Wizard for the Set Mail Routing feature. This column is not populated by the Directory
Export Wizard, but can be manually populated with suitable data. If this column is empty when the wizard’s
forwarding feature is invoked, the wizard infers suitable values from the values in other database columns.
Example:
NOTES:John Doe/MyOrganization@NOTES

NOTE: The value in this SourceForwardingAddress column is not immediately applied to the users’
Active Directory objects when the value is imported into the SQL database. The value is applied in
AD only when the corresponding forwarding feature is invoked.

• TargetAddress: Exchange address of the user. Example:

JDoe@example.com
The TargetAddress is copied by the Directory Export Wizard from the Notes internetAddress attribute. If
there is no internetAddress attribute defined in the Notes person document, the wizard generates a
TargetAddress from ShortName@ the default domain (designated on the Find Domains screen).
• TargetAlias: Any user aliases found in Notes for the user. This field can contain zero, one, or more than
one alias. Multiple aliases are separated by a percent symbol (%). When provisioning user accounts, any
found aliases are added as proxy addresses so any mail previously sent to one of these aliases is still
routed to the user account. Examples:
John.Doe@example.com
Jane.Doe@example.com%JaneD@example.com
• TargetForwardingAddress: SMTP-format address used to forward mail from Notes to Exchange, used in
the Data Migration Wizard for the Set Mail Routing features. This column is not populated by Directory
Export Wizard, but can be manually populated with suitable values. If this column is empty when the
wizard’s forwarding feature is invoked, the wizard infers suitable values from the values in other database
columns. Example:
Jdoe@migrate.example.com

NOTE: The value in the TargetForwardingAddress column is not immediately applied to the users’
Active Directory objects when the value is imported into the SQL database. The value is applied in
AD only when the corresponding forwarding feature is invoked.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

52
Directory Export Wizard
 5
Collection Wizard
• Introduction
• Wizard process screens

Introduction
The Collection Wizard lets you define the member contents of new user and group collections or change the
attributes of an existing collection. Migrator for Notes to Exchange provisioning, migration, and other features are
applied to collections of users and groups. You define these collections in the Collection Wizard. You can add
members to a collection by selecting objects from the SQL database or by importing the contents of a .tsv (tab-
separated-values format) file.

Wizard process screens

The Collection Wizard contains these screens:
• Select Collection
• Specify Collection Name
• Choose Member Selection Method
• Add Members
• Edit Collection Members

Select Collection
This screen appears only if you have started this wizard from outside Notes Migration Manager. The screen asks
you to specify an existing user collection whose definition you want to edit or to create a new User Collection.
If you launch this wizard from the Notes Migration Manager, click New collection to create a new collection or
select a collection in the drop-down list to edit and click Edit.
This screen contains one field with a drop-down list:
• Select an existing Collection or choose to create a new one: Use the drop-down list to select the
collection that you want, or to select Create a new User Collection.
Click Next.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

53
Collection Wizard
Specify Collection Name
The screen lets you name (or rename) the defined collection. You can also assign a Label to this collection to help
organize multiple collections by a classification scheme of your own design This screen also sets the visibility of
this collection and, optionally, attaches supplemental descriptive text about the collection.
• Collection name: The name by which this collection is shown in drop-down lists and tables in Notes
Migration Manager and elsewhere in Migrator for Notes to Exchange.
• Label (optional): Select a Label for this collection from the drop-down list or type a new Label name into
the text box to create a Label definition.
Labels are an arbitrary device for classifying and grouping collections. For example, you could define labels
for Engineering, IS, Marketing, R&D, Sales, and so on, for group collections based on the divisions in an
organization. Or you could define labels for Atlanta, Chicago, Denver, Houston, Memphis, Minneapolis,
Toronto, and so on, to group collections using the geographic locations of offices. Within Notes Migration
Manager, you can sort lists and tables of collections by label or you can specify a label to filter a list of
collections to show only the collections that were assigned that label.
• Visible: Check box that determines whether this collection appears in other lists of collections elsewhere in
Migrator for Notes to Exchange. (Migrator for Notes to Exchange’s provisioning, migration and other
features are applied to particular collections, which are specified from drop-down lists or tables.)
• Description (optional): Enter a text description of the collection. The contents of this field will appear in
tables of selections within Notes Migration Manager.
Enter the requested information, and click Next.

Choose Member Selection Method

This screen asks you to specify which of two methods to use to define the “first draft” member set of the collection.
Later screens let you edit the member contents of the collection. The two options are:
• Find members by searching the directory: Lets you specify the search criteria for selecting objects from
the SQL database to add to the member set for this collection. The search criteria is defined with respect to
one or more specified attribute values.
• Import members from a .tsv file: Lets you import the contents of a .tsv (tab-separated-values format) file
to define the “first draft” member set of this collection. The .tsv file must contain the NMEObjectGUID
column which is used as a key to associate users with a collection. One way to create a .tsv as a starting
point is to export another collection to a .tsv file.
Choose the method by which you want to define the “first draft” member set, and click Next.

Add Members
This screen lets you specify the search criteria for selecting objects from the SQL database to add members to this
collection. Regardless of how you define the addition of collection members from the database, the next screen
lets you (optionally) import additional members from a .tsv (tab-separated-values format) file.
The search criteria are defined with respect to one or more specified Attribute values. If you define multiple
criteria, they are applied in an AND fashion, as multiple filters (an object must satisfy all criteria to be included as a
member in the collection).

To add members to the collection from the SQL database:

1 Specify the Attribute, Condition, and Value that define the criterion that objects must satisfy to be
included as members in the collection.
2 Click Add to add the criterion to the list of Conditions.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

54
Collection Wizard
 3 Repeat steps 1 and 2 to define multiple selection criteria. Multiple criteria are applied in an AND fashion as
multiple filters (an object must satisfy all criteria to be included as a member in the collection).
4 To remove a criterion from the list of Conditions, select the line you want to remove, and click Remove.
5 When the list of Conditions appears as you want it, click Find Now to perform the search in the SQL
database.
The selected objects appear in the Search Results table.
Note: The Find Now function will replace any results that may already appear in the Search Results table.

To clear the Search Results table (to start over adding members):
• Click Clear.

To interrupt and end a search in progress (after clicking Find Now):

• Click Stop.

To save the collection member set:

• If you want the member set to include only some objects in the Search Results table, select the objects you
want to include and click OK.
• If you want the member set to include all the objects in the Search Results table, leave all objects
unselected and click OK.

Edit Collection Members

This screen lets you:
• Import from .tsv: Import the contents of a .tsv file to add members to the displayed collection. A dialog box
prompts for the location and name of a .tsv file to import. The contents of the .tsv file will be added to any
members already appearing in the collection table.
• Export to .tsv: Export the member-data contents of the displayed collection to a .tsv file so that you can
edit the data (and later import the data into a new collection). A dialog box prompts for the location and
name of the .tsv file to which you want to export the displayed member set.
• Add Members: Display the Add Members screen, which lets you select objects from the SQL database to
add members to this collection. (The displayed collection contents are carried into the Add Members
screen where you can add to them by selecting objects from the SQL database.)
• Delete Members: Delete from the collection the members that are selected in the displayed table. To
select two or more adjacent members (table rows) click on the first or last member you want to delete,
press Shift+Click on the member at the other end of the block to select the two rows and all rows between
them. To select two or more members whose table rows are not adjacent: click the first member row you
want to delete, and press Ctrl+Click on each additional row you want to delete.
When you are finished on this screen, click Finish to save the displayed members table for this collection, exit the
wizard, and return to Notes Migration Manager.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

55
Collection Wizard
 6
Groups Provisioning Wizard
• Introduction
• Wizard process screens

Introduction
The Groups Provisioning Wizard:
• Defines a task that provisions the distribution groups (create group objects) within Active Directory or Office
365 from a designated group collection (designated in the Provision Groups screen of Notes Migration
Manager from which this wizard is launched).
• Schedules the task to run at a particular time or at a series of recurring times.
Each run of the wizard is applied to a particular group collection that is designated by the Select collection to
provision drop-down list in the Provision Groups screen of Notes Migration Manager. Field definitions and
application notes for the wizard screens are described in the sections that follow.
Notes groups are typically provisioned all at once after all users have been migrated in the per-batch migration
process (see the Migrator for Notes to Exchange Scenarios Guide). Since the only data associated with a group is
its member list, the migration of a group consists only of it being provisioned into the target environment.

TIP: Group Membership Updating Privilege: The Groups Provisioning Wizard can provision groups so
that group managers who are not in Domain Admins can still update group membership. This privilege
corresponds to a check box in Active Directory, the Manager can update membership list check box in the
Managed By tab of AD Group Properties.
The feature is enabled/disabled in Migrator for Notes to Exchange through a boolean parameter in the
[ActiveDirectory] section of MNE Global Defaults or Task Parameters. The parameter is enabled by default:
[ActiveDirectory] GroupManagerCanUpdateMembershipList=1
However, you can set GroupManagerCanUpdateMembershipList=0 to tell MNE not to extend the updating
privilege to group managers who are not Domain Admins.

Screen-by-screen field notes and application notes for the Wizard process screens are described in the following
sections.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

56
Groups Provisioning Wizard
Wizard process screens
The Groups Provisioning Wizard is configured in these screens:
• Select Group Collection
• Customize Configuration
• Specify Active Directory Information
• Choose Your Group Settings
• Generating Task
• Configuration Summary
• Creating Task
• Specify Task Schedule
• Schedule Summary
• Task Progress
• Task Completed

Select Group Collection

This screen appears only if you have started this wizard from outside of the Migration Manager. The screen asks
you to specify the user collection to which you want to apply the wizard’s functions. (If you launch this screen from
the Groups Provisioning Wizard, you must select a collection in the table before you can click the button to start
the wizard.)
This screen contains only one field:
• Select the Group Collection you want to work with: In the drop-down list, specify the collection you
want.
Click Next.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager.

To enable or disable this capability to edit Task Parameters

• On the View menu in the Notes Migration Manager, select (enable) or clear (disable) the Advanced
Settings option.
The Advanced Settings option is a toggle that determines whether the wizards allow you open and edit
Task Parameters. If the feature is enabled, a Customize Configuration screen appears at the start of the
screen sequence for any wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file, although the parameters are stored as
part of the task definition within the SQL database. The Customize Configuration feature copies the current
parameter settings from the SQL database into a text document in Windows Notepad so you can use the Notepad
text-editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task configuration settings in Windows Notepad.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

57
Groups Provisioning Wizard
 2 Find the pertinent [SectionName] for the parameter you want to add or whose value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value.

4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter value(s) back into the SQL database.

Specify Active Directory Information

This screen appears if you are provisioning groups to a local AD either as your migration target or for later relay to
Office 365 by Microsoft AD sync, but not if you are provisioning groups directly from the source Domino to Office
365. This screen also appears if the information it requests was not collected in Notes Migration Manager (in the
Active Directory Configuration screen).
These fields specify AD server access credentials to authenticate the administrator by whose authority the
program reads the Active Directory:
• Global Catalog host name: Type the name of the AD Global Catalog server—for example, sitraka.com or
name.sitraka.com.

NOTE: If you have multiple Global Catalogs/Domain Controllers in an AD forest, you can choose any
GC in the setup as long as it is in the same domain.

IMPORTANT: If migrating to an Exchange on-premises server, you must enter fully qualified domain
names for the Global Catalog host name and Domain Controller host name.

• Domain Controller host name: Specify the PowerShell Domain Controller that Migrator for Notes to
Exchange will call to perform operations in Exchange 2010 or later.
• User name: The sAMAccountName, UPN, or fully qualified DN of the administrator by whose authority the
wizard will access the target AD. If your sAMAccountNames are ambiguous, use the UPN or DN.
• Password: Password associated with the User name.
Click Next.

Choose Your Group Settings

Enter the choices here to determine how the groups will be provisioned into the target directory and click Next.
• Group Scope: This setting determines whether a group can accept members from other domains and
whether it can be used in other domains. Groups in AD are assigned one of three scopes: Domain Local
groups, Global groups, and Universal groups. Group scopes are less important if you have only one
domain. For a single-domain environment, all groups can be Universal groups unless you expect to expand
to multiple domains at a later time. For information about AD Group Scope, see your Microsoft Active
Directory documentation.
• Group Type: Groups in AD are designated as one of two types: Security groups and Distribution groups.
Either type can include users, contacts, and computer objects as members. For information about AD
Group Type, see your Microsoft Active Directory documentation.
• Container for Groups (appears grayed-out if provisioning directly to Office 365): Specify (fully qualified)
the AD container that will contain the groups created during the provisioning process. For example:
OU=Groups,DC=mydomain,DC=com.
• Add contacts for members not found in the target system: A check box to determine whether the
wizard should create new contact objects for any group member that does not already exist in AD.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

58
Groups Provisioning Wizard
 • Container for Contacts (appears grayed-out if provisioning directly to Office 365): Specify (fully qualified)
the AD container that will contain the new contacts the program will create for group members who are not
found in AD. For example: OU=Contacts,OU=Groups, DC=mydomain,DC=com.
• Keep groups in sync with corresponding Notes groups: A check box to determine whether the wizard
should delete a Group member from an AD Group if the member is found to not be a member of the
corresponding Group in Notes.

Generating Task
The screen reports progress as it determines the details and associated work items of the task you configured. In
the next screen you can review the details and associated work items, and decide whether to create the task, or go
back and change any specifications that define the task. When the process is complete, the wizard displays the
next screen.

Configuration Summary
This screen shows a summary of the task configuration you have specified.
Review this information to confirm that it describes the task you want to create. To change anything, click Back to
return to earlier screens and change values as necessary, or click Cancel to return to the Provision Groups screen
in Notes Migration Manager. From earlier screens within this wizard, you can click Next to return to this
Configuration Summary screen.
Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and filename
for the text file.
Print: Prints a paper copy of this summary information. Follow the prompts to specify the destination printer.
Run: Creates the task as defined in the configuration summary and run the task. When you click Run, the wizard
displays a screen that reports its progress as it creates the task, and a screen that reports its progress as the task
runs. When the task run is complete, the wizard displays a screen that reports the statistical results of the task.

Creating Task
No information is entered into this screen. This screen reports the wizard's progress as it creates the task defined
on the preceding Configuration Summary screen.
When the task-creation process is complete, the wizard clears this screen and runs the newly created task.

Specify Task Schedule

This screen lets you schedule the task you have created.

NOTE: The Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, as explained in chapter 13 of the Migrator
for Notes to Exchange Administration Guide. The Task Scheduler checks the SQL database to see whether
any tasks have been scheduled to run since the last check, and runs any tasks it finds. See chapter 13 for
details on the Task Scheduler.

The drop-down list at the top of the screen offers the following scheduling options:
• Now on this computer: The wizard runs the task when you click Next. The other scheduling controls on
the screen appear grayed out (unavailable), since they do not apply. Click Next to display the Task
Progress screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

59
Groups Provisioning Wizard
 • One or more times, as indicated below: The task runs one or more times, according to your entries in the
scheduling controls later in this screen. If you select this option you must also specify where and when you
want the task to run in the scheduling controls.
• Manually: The task will not run or be scheduled. The other scheduling controls on the screen appear
grayed out (unavailable), since they do not apply. Click Next to display the Schedule Summary screen.
• Once: The task runs once and will not repeat. You can specify where to run and the start date and time.
Click Next to display the Schedule Summary screen.
These scheduling controls are enabled only if One or more times... is selected in the drop-down list:
• Where to run: Select either On any computer or On a specific computer. If you choose a specific
computer, you must also specify the machine name in the adjacent text box.
• When to run:
▪ Start: Specify the calendar date for the first (or only) task run.
▪ Days of the Week: Specify one or more days of the week that you want the task to run. If you select
two or more days, the first task run will occur on the first selected day occurring on or after the
specified Start date.
▪ Between ____ and ____: Specify the beginning and ending times of a range of start times for the
task to run.
▪ Select one of these options for the end date:
▫ No end date: The task runs will adhere to this schedule until you manually end the series by
editing this schedule definition in Notes Migration Manager (in the Manage Scheduled
Operations screen).
▫ End after __ occurrences: The task runs will adhere to this schedule until the cumulative
number of runs matches the number specified here.
▫ End by: The task runs will adhere to this schedule until the calendar date specified here.
▪ [_] Start this task only after completing: [________________________]: Select this check box if
you want this new task to run only after some other previously defined task has run. If you select the
check box, use the drop-down list to specify which previously defined task must precede this one.
When you have set the task schedule in these scheduling controls, click Next to display the Schedule
Summary screen.

Schedule Summary
This screen appears only if you have selected One or more times... or Manually as the scheduling option on the
Specify Task Schedule screen. The screen shows a summary of the task schedule you specified in the Specify
Task Schedule screen or notes that the task will be run Manually.
Review this information to confirm that it describes the schedule you want to define. To change anything, click
Back to return to the Specify Task Schedule screen, or click Cancel to cancel this wizard and return to the Export
Notes Directory screen in Notes Migration Manager. From the preceding screen, you can click Next to return to
this Schedule Summary screen.
When you are satisfied that the displayed summary describes the task schedule you want to create, click Finish to
dismiss this screen:
• Finish: Clears this Schedule Summary screen, to return to the Export Notes Directory screen in Notes
Migration Manager.
The remaining screens documented for this Wizard are skipped if you have selected One or more times... or
Manually as your scheduling option on the preceding Specify Task Schedule screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

60
Groups Provisioning Wizard
Task Progress
No information is entered into this screen. The screen reports the program's progress as it performs the defined
task.
You can click Cancel to cancel the task before it completes.
When the process is complete, the program displays its Task Completed screen to report the results.

Task Completed
No information is entered into this screen. The screen reports the results of the task run.
f the program encountered errors during its run, the Task Completed screen displays an Error Log Report button.
Click the button to view the program log and assess the severity of the errors. The Error Log Report button
launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and resolve the errors.
When you are finished, click Exit to exit the wizard.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

61
Groups Provisioning Wizard
 7
Notes Data Locator Wizard
• Introduction
• Wizard process screens

Introduction
Notes data stores contain the data associated with Notes features: emails, PABs, archives, calendar data, and so
on. (Generically, a data store is any repository of data.) Some Notes data stores reside in central locations where
they are available to all users. Other data stores reside on user local workstations, each containing only the
information associated with the individual user. Migrator for Notes to Exchange can migrate data from anywhere
within the Notes system but only if it knows where the various data stores reside.
Migrator for Notes to Exchange includes a Notes Data Locator Wizard that scans the Notes environment for all
data stores associated with a designated user collection. The wizard records (in the MNE SQL database) the
locations of all data stores it finds together with associated statistics. The wizard displays the information in a table
in the MNE Notes Migration Manager, on the Locate Notes Data Stores screen under User Collections. Statistics
include information such as the size of the store, number of items in the store, average per-item size of items in the
store, date and time the statistics were last collected or updated.
Using the Notes Data Locator Wizard, you define a task to locate data files in the Notes source for a specific user
collection or gather statistics from previously located data files. You can schedule the task to run at a particular
time or at a series of recurring times. You can configure the wizard to locate data files by type (mail vs. PABs vs.
archives) in any combination.
The Notes Data Locator Wizard is launched from the Locate Notes Data Stores screen of Notes Migration
Manager, and is always applied to the user collection specified in the Locate Notes Data Stores screen. Field
definitions and application notes for the wizard screens appear in the sections that follow.

NOTE: Since the PAB Replicator is designed to copy the user local data stores to a centralized location,
ensure that all users have run the PAB Replicator before you run the Notes Data Locator Wizard.

How to add NSF file locations to user collections

If the Notes Data Locator Wizard does not find user NSF files but you know the locations, you can add the per-user
NSF paths to the SQL database so the Data Migration Wizard can migrate them. To edit the contents of a SQL
Server data table, you must export the table to a .tsv file, use Microsoft Excel or a similar application to edit the
contents, and import the amended values back into the SQL database. This process is explained in Appendix A
under How do I specify per-user locations for Notes source data?.
Within the data table, the MailFilePath column defines the specific paths and NSF filenames to users' mail files.
For example:
\\server\home\user\jdoe.nsf

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

62
Notes Data Locator Wizard
Wizard process screens
The Notes Data Locator Wizard is configured using these screens:
• Select User Collection
• Customize Configuration
• Configure Updates of TSV-Imported Values
• Specify Notes Login Information
• Select Notes Data Store Types to Locate
• Specify How to Find Notes Mail Files
• Specify Notes Mail File Directories
• Specify How to Find Notes Personal Address Books
• Specify Notes Personal Address Book Replica Directory
• Specify Notes PAB Directories
• Specify How to Find Notes Archives
• Specify Notes Archive Replica Directory
• Specify Notes Archive Directories
• Specify How to Determine Owner Using ACL
• Select Administrative Users to Ignore
• Generating Task
• Configuration Summary
• Creating Task
• Specify Task Schedule
• Task Progress
• Task Completed

Select User Collection

This screen appears only if you started this wizard from outside of the Notes Migration Manager. The screen asks
you to specify the user collection that you want. (If you launch this screen from outside of the wizard, you must
select a collection in the table before you can click the button to start the wizard.)
This screen contains one field:
• Select the User Collection you want to work with: Use the drop-down list to specify the collection that
you want.
Click Next.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable this capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

63
Notes Data Locator Wizard
The Advanced Settings option is a toggle that determines whether the wizards allow you to open and edit Task
Parameters. If the feature is enabled, the Customize Configuration screen appears at the start of the screen
sequence for any wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file, although the parameters are stored as
part of the task definition within the SQL database. The Customize Configuration feature copies the current
parameter settings from the SQL database into a text document in Windows Notepad, so you can use the Notepad
text-editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task configuration settings into Windows Notepad.
2 Find the pertinent [SectionName] for the parameter you want to add, or whose value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter values back into the SQL database.
When you are finished editing Task Parameters, click Next.

Configure Updates of TSV-Imported Values

This screen appears only if the wizard detects that a TSV import has changed one or more DominoServerAddress
values. A pair of mutually exclusive radio buttons let you choose whether to overwrite or preserve any
DominoServerAddress values that were modified by a TSV import:
O Keep existing modified ‘DominoServerAddress’ values imported from TSV
O Replace existing ‘DominoServerAddress’ values
Click Next.

Specify Notes Login Information

This screen appears only if the information it requests is not already collected in the Notes Migration Manager (in
the Notes Server Configuration screen). These fields specify Notes server access credentials used to authenticate
the administrator by whose authority the program performs its administrative functions:
• User ID file: Click Browse to find and specify the path and filename of the User ID file, or type or paste the
UNC path and filename into the text box.
• Password: Type the password associated with the User ID file.
Enter the requested information, and click Next.

Select Notes Data Store Types to Locate

This screen lets you specify what types of data to find, and whether to find new data stores or gather statistics from
previously located data stores.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

64
Notes Data Locator Wizard
 NOTE: This wizard’s performance is dramatically affected by the location of archives and PABs being
located and scanned. It typically runs much slower when scanning archives and PABs on a remote file
system.

Select either of these options:

• Find new data stores and gather statistics: Scans the Notes environment for all data stores, and collects
statistics for each.
• Gather statistics on previously located data stores: Update the statistics for data stores that were found
in a previous run of this Wizard, and do not look for any other data stores.
▪ Add/Replace mode: A drop-down list for you to specify what the wizard should do with the
information it finds (choose one option):
▫ Add to existing data: Scan for data stores, and add the found stores (and their statistics) to
the existing list of previously found data stores.
▫ Replace data previously found in these locations: Update the statistics for the existing
list of previously found data stores.
▫ Replace all previously located data: Delete all previously found data stores and their
associated statistics from the Migrator for Notes to Exchange database, and scan and
collect statistics from scratch.
Data to locate: Select one or more of the check boxes for the types of data you want to find:
[ ] Mail files
[ ] Personal Address Books (PABs)
[ ] Archives
Click Next.

Specify How to Find Notes Mail Files

Select the appropriate option to tell the wizard how it should look for users' server mail files:
• Through Domino server(s): Looks for users' server-based mail files via the server. The wizard opens
each mail file using the administrator credentials provided in the Specify Notes Login Information screen (or
in the Notes Server Configuration screen in Notes Migration Manager). The administrator must be listed in
the Manager ACL for the NSF file.
• Scan file system directories that I specify: Looks for server-based mail via the file system, in a subtree
to be specified later in this wizard.
A third option is offered only if at least one user has a MailFilePath specified in the SQL database:
• Use MailFilePath from database (m of n populated): Looks for server-based mail in the locations
specified per-user in the MailFilePath column of the SQL database. The “m of n populated” reports the
number of users in the collection who have a MailFilePath (m) out of the total number of users in the
collection (n).
Click Next.

Specify Notes Mail File Directories

This screen appears if you selected (in the Specify How to Find Notes Mail Files screen) Scan file system
directories to look for users' server-based mail files.
Specify the directory subtrees in which the wizard should look for users' server-based mail files. Directories must
be specified as UNC paths.
Click Next.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

65
Notes Data Locator Wizard
To specify each subtree:
• Click Browse to find the subtree (or type the subtree notation), and click Add to add it to the Mail file
directories list.

To specify more than one subtree:

• Repeat the process: Click Add for as many subtrees as you want to add to the Mail file directories list.

To remove a subtree from the Mail file directories list:

• Select the subtree within the list and click Remove selected.
When the Mail file directories list contains all the subtrees you want to search for the user server-based mail files
(and no others), click Next.

Specify How to Find Notes Personal Address

Books
Select the appropriate option to look for user PABs (personal address books):
• Scan for replicas on the server: Looks for the user PABs in replicas that were uploaded to a particular
location on a server. For this option the administrator account specified in the Specify Notes Login
Information screen (or in the Notes Server Configuration screen in Notes Migration Manager) must be
listed as a manager for all NSF files to be migrated. If the MNE PAB Replicator is used, the administrator
account is added as a manager when users copy their PABs to the server.
• Scan file system directories that I specify: Looks for the user PABs via the file system in a subtree to be
specified in this wizard.

NOTE: If the Notes Data Locator Wizard finds a PAB twice, once by the server and again by the file
system, the Data Migration Wizard tries to migrate it twice. But the file-system attempt will fail and
generate an error because the successful server access locks the file, rendering it inaccessible.
While the radio buttons make it impossible to locate by both methods at once, it is possible to run the
wizard more than once, and to select different location methods in different runs of the wizard.

NOTE: PAB data will be duplicated in Exchange if you remigrate to the server and use a different
method (server vs. file system) than the first migration.

A third option is shown only if at least one user has an entry in the SQL database for PABPaths or SharedPABDirs:
• Use PABPaths and/or SharedPABDirs from database (m of n populated): Looks for the user PABs in
the locations specified per-user in the PABPaths or SharedPABDirs column of the SQL database. The “m
of n populated” reports the number of users in the collection who have a PABPaths or SharedPABDirs entry
(m) out of the total number of users in the collection (n).
Click Next.

Specify Notes Personal Address Book Replica

Directory
This screen appears only if you have selected (in the preceding screen) Scan for replicas on the server. The
screen asks you to specify the location of the PAB replicas by Server and Directory:
• Server: The name of the server to which users' PAB replicas will be uploaded. The Server specified must
be accessible by the Notes Login User ID file and Password specified in the Specify Notes Login
Information screen, or specified in the Default Settings of Notes Migration Manager (see Edit Default
Settings: Notes Server Configuration in chapter 1).

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

66
Notes Data Locator Wizard
 • Directory: The directory on the server to which user PAB replicas will be uploaded.
Click Next.

Specify Notes PAB Directories

This screen appears only if you selected (in the Specify How to Find Notes PABs screen) Scan file system
directories that I specify to look for users' personal address books (PABs).
Specify the directory subtrees where the wizard should look for users' PABs. Directories must be specified as UNC
paths.
Click Next.

To specify each subtree:

• Click Browse to find the subtree (or type the subtree notation), and click Add to add it to the Root
Directories list.

To specify more than one subtree:

• Repeat the process: Click Add for each subtree you want to add to the Root Directories list.

To remove a subtree from the Mail file directories list:

• Select the subtree in the list, and click Remove selected.
When the Root Directories list contains all the subtrees you want to search for user PABs, click Next.

Specify How to Find Notes Archives

Select the appropriate option to tell the wizard how it should look for users' archives:
• Scan for replicas on the server: Looks for users' archives in replicas that have been uploaded to a
particular location on a server. For this option the administrator account specified in the Specify Notes
Login Information screen (or in the Notes Server Configuration screen in Notes Migration Manager) must
be listed as a manager for all NSF files to be migrated.
• Scan file system directories that I specify: Looks for users' archives via the file system, in a subtree to
be specified later in this Wizard.

NOTE: If the Notes Data Locator Wizard finds an Archive twice, once by the server and again by the
file system, the Data Migration Wizard will try to migrate it twice. But the file-system attempt will fail
and generate an error because the successful server access will have locked the file, rendering it
inaccessible. While the radio buttons in this screen make it impossible to locate by both methods at
once, it is possible to run the wizard more than once, and to select different location methods in
different runs of the wizard.

NOTE: Archive data will be duplicated in Exchange if you remigrate to the server and use a different
method (server vs. file system) than the first migration.

A third option is shown only if at least one user has an entry for ArchivePaths or SharedArchiveDirs in the SQL
database:
• Use ArchivePaths and/or SharedArchiveDirs from database (m of n populated): Looks for users'
archives in the locations specified per-user in the ArchivePaths or SharedArchiveDirs column of the SQL
database. The “m of n populated” reports the number of users who have an ArchivePaths or
SharedArchiveDirs value (m) out of the total number of users in the collection (n).
Click Next.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

67
Notes Data Locator Wizard
Specify Notes Archive Replica Directory
This screen appears selected (in the preceding screen) Scan for replicas on the server. The screen asks you to
specify the location of the archive replicas by Server and Directory:
• Server: The name of the server to which users' archive replicas will be uploaded. The Server specified
here must be accessible by the Notes Login User ID file and Password specified in the Specify Notes
Login Information screen, or specified in the Default Settings of Notes Migration Manager (see Edit Default
Settings: Notes Server Configuration in chapter 1).
• Directory: The directory on the specified Server to which users' archive replicas will be uploaded.
Click Next.

Specify Notes Archive Directories

This screen appears only if you told the wizard (in the Specify How to Find Notes Archives screen) to Scan file
system directories to look for users' archives.
Directories must be specified here as UNC paths.
Specify the directory subtree(s) where the wizard should look for users' archives, and click Next.

To specify each subtree:

Click Browse to find the subtree (or type the subtree notation), and click Add to add it to the Root
directories list.

To specify more than one subtree:

Repeat the process: Click Add for each subtree you want to add to the Root directories list.

To remove a subtree from the Mail file directories list:

Select the subtree within the list and click Remove selected.
When the Root directories list contains all the subtrees you want, click Next.

Specify How to Determine Owner Using ACL

This screen indicates whether file ownership should be determined by checking the Manager entries in a file’s
Access Control List (ACL) if ownership cannot be determined using the file profile.
Examine ACLs to determine owner: Select the check box to enable this feature or clear it to disable the feature.
If you enable this feature, you can also specify a list of administrative users to be ignored when the wizard consults
the ACLs. Many organizations routinely list one or more administrators as co-Managers of all (or most) files, but
you can tell the program to ignore any such administrator/managers that appear in the file ACLs, but who are not
the owners of the files. To add one or more new names to the “ignore” list, click Add to display a selection dialog
box: Select Administrative Users to Ignore (described in next topic). That dialog box lets you prepare a list of
administrator names to add to the “ignore” list, and displays this screen when you click OK.
You can also select one or more names in the “ignore” list and click Remove Selected to remove them from the
list of administrator users to ignore.
When the entries correctly specify how file ownership should be determined, click Next to display the Generating
Task screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

68
Notes Data Locator Wizard
Select Administrative Users to Ignore
This dialog box lets you add one or more names to the “ignore list” of Managers to be ignored when the wizard
determines file ownership from a file’s Access Control List (ACL). Since many organizations routinely list one or
more administrators as co-Managers of all (or most) files, you can tell the program to ignore any such
administrator Managers who appear in the file ACLs, but who are not the owners of the files.
The names you specify in the Selected Users list are added to the “ignore list”.

To add a name to the Selected Users list:

• Select one or more names from the list at left, and click the right arrow button (—>).
To select more than one name, hold the Shift key down as you click on each additional name.

To remove a name from the Selected Users list:

• Select one or more names from the list, and click the left arrow button (<—).

To return to the previous screen and copy the Selected Users list into the “ignore list” on the
previous screen:
• Click OK.
When the Selected Users “ignore” list appears as you want it, click OK to save the list and return to the Specify
How to Determine Owner Using ACL screen.

Generating Task
This screen reports the wizard's progress as it determines the details and associated work items of the task you
have configured. You can review (in the next screen) the details and associated work items, and decide whether to
create the task or go back and change any specifications that define the task.
When this generation process is complete, the wizard displays the next screen.

Configuration Summary
This screen shows a summary of the task configuration you have specified.
Review the information to confirm that it describes the task you want to create. To change anything, click Back to
return to earlier screens in the wizard and change values, or click Cancel to cancel the wizard and return to the
Locate Notes Data Stores screen in Notes Migration Manager. From earlier screens within this wizard, you can
click Next to display this screen.
Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and filename
for the text file.
Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the destination
printer.
Run: Creates the task as defined in the configuration summary and immediately runs the task. When you click
Run, the wizard displays a screen that reports its progress as it creates the task and displays a screen that reports
progress as the task runs. When the task run is complete, the wizard displays a screen that reports the statistical
results of the task.

Creating Task
This screen reports the wizard's progress as it creates the task defined on the Configuration Summary screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

69
Notes Data Locator Wizard
When the task-creation process is complete, the wizard clears this screen and runs the newly created task.

Specify Task Schedule

This screen lets you specify when to run the task you have created—immediately or at a later time.

NOTE: The Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, explained in chapter 13 of the Migrator for
Notes to Exchange Administration Guide. The Task Scheduler checks the SQL database to see whether any
tasks have been scheduled to run since the last check, and runs any tasks it finds.

The drop-down list at the top of the screen offers the following scheduling options:
• Now on this computer: Runs the task as soon as you click Next. The other scheduling controls on the
screen appear grayed out (unavailable) since they do not apply. Click Next to display the Task Progress
screen.
• One or more times, as indicated below: The task runs one or more times, according to the entries in the
scheduling controls. If you select this option you must specify where and when you want the task to run.
• Manually: The task will not run or be scheduled at all. The other scheduling controls on the screen appear
grayed out (unavailable) since they do not apply. Click Next to display the Schedule Summary screen.
• Once: The task runs only once and does not repeat. You can specify where to run and the start date and
time.
These scheduling controls are enabled if One or more times... is selected in the drop-down list:
• Where to run: Select either On any computer or On a specific computer. If you choose a specific
computer, you must specify the computer name in the adjacent text box.
• When to run:
▪ Start: Specify the calendar date for the first (or only) task run.
▪ Days of the Week: Specify one or more days of the week on which you want the task to run. If you
select two or more days, the first task run occurs on the first selected day on or after the specified
Start date.
▪ Between [____] and [____]: Specify the beginning and ending times of a range of start times for
the task to run.
▪ Select one of these options for the end date:
▫ No end date: The task runs adhere to this schedule until you manually end the series by
editing the schedule definition in Notes Migration Manager (in the Manage Scheduled
Operations screen).
▫ End after __ occurrences: The task runs will adhere to this schedule until the cumulative
number of runs matches the number specified here.
▫ End by: The task runs adhere to this schedule until this date.
▪ [_] Start this task only after completing: [________________________]: Select this check box if
you want this new task to run only after some other previously defined Migrator for Notes to
Exchange task has run. If you select the check box, use the drop-down list to specify which
previously defined Migrator for Notes to Exchange task must precede this one.
When you have set the task schedule, click Next to display the Task Progress and Schedule Summary screens.

Task Progress
The screen reports the program's progress as it performs the defined task.
You may click Cancel to cancel the task before it completes.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

70
Notes Data Locator Wizard
When the process is complete, the program displays its Task Completed screen to report the results.

Task Completed
The screen reports the results of the task run.
This screen can also display an Error Log Report button if the program encountered errors during its run. If the
Error Log Report button appears, click the button to view the program log and assess the severity of the errors.
The Error Log Report button launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you
interpret and resolve the errors.
When you are finished, click Exit.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

71
Notes Data Locator Wizard
 8
Provisioning Wizard
• Introduction
• Wizard process screens

Introduction
The most common method for provisioning Active Directory begins with a directory update using the Quest
Coexistence Manager for Notes (CMN) Directory Connector. The CMN tool can extract data from the
Notes/Domino source and create mail-enabled security objects or contacts in Active Directory for all Notes users.
If the migrating users are already using AD security objects for network authentication, the directory update should
have been configured to create new AD contacts which now correspond to the existing user objects in AD. In this
case, The Provisioning Wizard can consolidate such duplicates before any data is migrated.
The Provisioning Wizard is run only once per user collection and must be run before the Data Migration Wizard is
run for those users. The user collection is specified in the Notes Migration Manager screen (see User Collections:
Provision Users).
Field definitions and application notes for the wizard screens appear in the sections that follow (under Wizard
process screens).

How the wizard works

User object records in Active Directory contain several data elements—last names, first names, titles, SMTP email
addresses, and so on—and the values for at least one of these attributes must be unique per object record. For
example, no two users can have the same DN. (For the Provisioning Wizard we assume that no two users can
have the same SMTP email address.)
Contacts in AD are characterized by a similar set of field values, at least one of which must be unique per contact.
When a Domino-to-AD directory update creates new AD contacts (representing Notes users), some or all the
contact records can correspond to existing user objects in AD. The Provisioning Wizard can associate contacts
with user objects by finding the unique values of the pertinent AD object attribute that match unique values of the
corresponding field in the contacts. The wizard prompts you for an attribute that corresponds to which field for
these comparisons.
The Provisioning Wizard is applied to a particular user collection that you specify when you launch the wizard from
Notes Migration Manager (see User Collections: Provision Users). The “match” attribute that the wizard uses to
compare and match AD contacts and users must correspond to an attribute in the MNE SQL database from which
the collections are drawn. For each user in the designated collection, the wizard reads the match attribute value,
and looks in AD for the single contact and the single user whose corresponding attribute values both match the
value from the user record in the SQL database. When it finds a match, it merges the contact information into the
user object record, and deletes the contact, leaving a single mailbox- enabled object per user in Active Directory.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

72
Provisioning Wizard
Before you run the Provisioning Wizard
Before running the Provisioning Wizard, you must:
• Verify that the SQL database contains a column whose per- contact values are unique and that match the
values for a corresponding AD object attribute. If the database does not contain a populated column for this
purpose, you must enter appropriate values into the SearchKey column as described following. The
Provisioning Wizard provides the following options in a drop-down list:
▪ DisplayName: Copied by Directory Export Wizard from the first value of the Notes FullName
attribute that is not a DN ("CN=Joe Schmoe/O=Acme") or SMTP address
(Joe.Schmoe@acme.com) or, if every FullName is a DN or SMTP address, the “CN” portion of the
first FullName that is a DN ("CN=xxx/...").
▪ GivenName: Copied by Directory Export Wizard from the Notes FirstName.
▪ Userid: Copied by Directory Export Wizard from the first value of the Notes ShortName that is not
an SMTP address (same as Nickname column below).
▪ Surname: Copied by Directory Export Wizard from the Notes LastName attribute.
▪ PhoneticName: Copied by Directory Export Wizard from the Notes AltFullNameSort attribute.
▪ Nickname: Copied by Directory Export Wizard from the first value of the Notes ShortName that is
not an SMTP address (same as Userid column).
▪ EmployeeID: Copied by Directory Export Wizard from the Notes EmployeeID.
▪ SourceAddress: Derived by Directory Export Wizard from the first value of the Notes FullName
attribute that is a DN ("CN=Joe Schmoe/O=OurCompany"), with “CN=” and “O=” stripped out
(leaving “Joe Schmoe/OurCompany”).
▪ TargetAddress: Copied by the Directory Export Wizard from the Notes internetAddress. If there is
no internetAddress attribute defined in the Notes person document, the wizard generates a
TargetAddress from ShortName@ the default domain (designated on the Find Domains screen).
▪ SearchKey: Column not populated by Directory Export Wizard. May be manually populated with
user-identifying values (unique per user) that the Provisioning Wizard can use to match objects for
merging if none of the other column options is suitable for the merge process. The procedure to edit
these values is explained in the following section.
▪ SearchKey2: Column is not populated by Directory Export Wizard. Can be manually populated with
user-identifying values (unique per user) that the Data Migration Wizard can use to properly
associate resource accounts with corresponding user accounts, and properly enable mailboxes
(used only when Active Directory is configured for a resource forest and a user forest, with
corresponding user accounts). This process is explained in Appendix A, under How Do I Prepare
the SQL database for Mailbox-Enabling (If AD Is Configured for a Resource Forest and a User
Forest)?
▪ SourceForwardingAddress: Column is not populated by Directory Export Wizard. Can be
manually populated to contain addresses used by the Data Migration Wizard to forward mail from
Notes to Exchange. If this column is empty and the Data Migration Wizard set for Notes-to-
Exchange forwarding, the wizard will infer suitable values from the values in other database
columns.
▪ TargetForwardingAddress: Column is not populated by Directory Export Wizard. Can be manually
populated to contain addresses used by the Data Migration Wizard to forward mail from Exchange
to Notes. If this column is empty and the Data Migration Wizard set for Exchange-to-Notes
forwarding, the wizard will infer suitable values from the values in other database columns.

To edit the SearchKey column of the data table

1 In the Manage Users (User Collections) screen of Notes Migration Manager, select the collection whose
contacts you want to merge.
2 Click Export objects to TSV to export the data to a .tsv (tab-separated values format) file.
3 Enter the destination folder and file name in the dialog box.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

73
Provisioning Wizard
 4 Use Microsoft Excel (or some program that can edit a tsv-format file) to edit the contents of the table.
You can add, edit, and delete the contents of any existing cell in the table, but any addition or deletion of an
entire row or column is ignored when you import the data back into the database.
5 Find a column in the exported data table that is suitable for the merge process—containing values that are
unique per user, and that correspond to the values of the pertinent AD object attribute.
6 Copy the values of that column into the SearchKey column. If no column exactly corresponds to the
pertinent AD attribute, you can find a column with values that can be massaged to match by appending or
stripping some segment of the data string, or merging the values with the data in another column or from
some other source.
7 In Notes Migration Manage, click Import objects from TSV to import the edited .tsv file into the SQL
database. A dialog box will prompt you for the filename and its location.
8 Verify that the drop-down list in the Choose Your Method... screen offers the AD attribute you want for the
merge function. By default, the drop-down list contains these options:

cn altRecipient extensionAttribute8
mail legacyExchangeDN extensionAttribute9
mailNickname extensionAttribute1 extensionAttribute10
proxyAddresses extensionAttribute2 extensionAttribute11
sAMAcountName extensionAttribute3 extensionAttribute12
userPrincipalName extensionAttribute4 extensionAttribute13
targetAddress extensionAttribute5 extensionAttribute14
employeeNumber extensionAttribute6 extensionAttribute15
distinguishedName extensionAttribute7

If the attribute you want does not appear in this list, you must add it as described in Appendix A: see How Do I Add
to the List of AD Attributes Available for the Merge Function?

Wizard process screens

The Provisioning Wizard is configured on these screens:
• Select Configuration
• Select User Collection
• Customize Configuration
• Specify Active Directory Information
• Choose Your Method for Finding Objects
• Choose the Container for User Objects
• Generating Task
• Configuration Summary
• Creating Task
• Specify Task Schedule
• Task Progress
• Task Completed

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

74
Provisioning Wizard
Select Configuration
You can save and recall sets of entries in this wizard, as templates, to simplify future runs when you expect to have
multiple runs that are similarly configured. Each configuration template consists of the entries from all the wizard
screens.
Create new configuration or select from existing templates: Drop-down list offers a choice of selecting a
previously saved template to recall for this run, or <Create new configuration>. Previously saved templates appear
in the list by the Names under which they were saved (see the Name field below).
If you choose <Create new configuration> from the drop-down list, the wizard displays the following options:
• [ ] Save as template: When selected, your entries in the remaining screens are saved as a template for
future use. A checked box enables the Name and Description fields. The name you assign to the template
appears in the drop down list in future wizard runs.
When Save as template is selected, you can select to create a Full Template or a Differential template.
▪ A full template is a snapshot of the INI configuration file used to run a task when the template was
created. This INI file includes all the settings from the Global Default settings plus any additions or
modifications that were made by the wizard used to run the task. A full template does not retrieve
new Global Default settings after it is created.
▪ A differential template contains only the INI settings that are different than those in the Global
Default INI file. A differential template can retrieve new Global Default settings.
A differential template takes precedence over the Global Default settings. Consider the following scenarios:
▪ A parameter in the Global Default settings is changed in the differential template. The differential
template setting is used.
▪ A parameter in the Global Default settings is removed from the differential template. The differential
template setting is used. Changing the setting in the Global Default settings has no impact on the
differential template.
▪ A parameter is not in the Global Default settings when a differential template is created. When the
parameter is added to the Global Default settings, it is also added to the differential template.
▪ A parameter is set to the same value in the Global Default settings and in the differential template.
When the parameter is removed from the Global Default settings, it is also removed from the
differential template.
▪ A parameter is set to the same value in the Global Default settings and in the differential template.
When the parameter is changed in the Global Default settings, the differential template is updated
with the new value.
If you select a previously saved template from the drop-down list, the wizard imports all of its saved settings into all
wizard screens, and displays:
• [ ] Modify this template: Select this check box if you want to run the wizard this time with one or more
entries different from the settings that were imported from the selected template.
A selected check box permits changes to any of the settings that appear in any of its screens, including the
Name and Description fields here. (You can save the changes under a new template Name, and leave the
originally selected template unchanged.)
If the check box is left clear, the wizard skips most of its screens when you click Next to skip directly to the
Configuration Summary screen.
• Delete Selected Template: Click this button to delete the selected template from the drop-down list (which
will make it unavailable in future runs of the wizard). If you click Delete, the wizard prompts you to confirm
(or cancel) the command.
Click Next to save your entries and display the next screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

75
Provisioning Wizard
Select User Collection
This screen appears only if you have started this Wizard from outside Notes Migration Manager. The screen asks
you to specify the user collection to which you want to apply this Wizard’s functions. (If you launch screen from
outside of the wizard, you must select a collection in the table before you can click the button to start the wizard.)
This screen contains only one field:
• Select the User Collection you want to work with: Use the drop-down list to specify the collection to
which you want to apply this Wizard’s functions.
Click Next.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable this capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.
The Advanced Settings option is a toggle that determines whether the wizards will let you open and edit Task
Parameters. If the feature is enabled, this extra Customize Configuration screen will appear at the start of the
screen sequence for any Wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file, although the parameters are stored as
part of the task definition within the SQL database. The Customize Configuration feature copies the current
parameter settings from the SQL database into a text document in Windows' Notepad, so you can use the
Notepad text-editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit to open the task configuration settings in Windows Notepad.
2 Find the pertinent [SectionName] for the parameter you want to add, or whose value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is very important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 as necessary to make any other additions and changes to the parameters.
5 Close Notepad.
Notes Migration Manager copies the new parameter value(s) back into the SQL database.

Specify Active Directory Information

This screen appears only if the information it requests has not already been collected in Notes Migration Manager
(Active Directory Configuration screen).
These fields specify AD server access credentials, to authenticate the administrator by whose authority the
program will manipulate the contents of the Active Directory:
• Global Catalog host name: Type the name of the AD Global Catalog server—for example, sitraka.com or
name.sitraka.com.

NOTE: If you have multiple Global Catalogs/Domain Controllers in an AD forest, you may choose any
GC in the setup as long as it is in the same domain.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

76
Provisioning Wizard
 IMPORTANT: If migrating to an Exchange on-premises server, you must enter fully qualified domain
names for the Global Catalog host name and Domain Controller host name.

• Domain Controller host name: Specify the PowerShell Domain Controller that Migrator for Notes to
Exchange will call to perform operations in Exchange.
• User name: The user name of the administrator by whose authority the program will access the Active
Directory.
• Password: The password associated with the user name.
Click Next.

Choose Your Method for Finding Objects

Enter information to tell the wizard how to associate contacts with user security objects in Active Directory and
click Next.
The Provisioning Wizard associates contacts with user objects by finding the unique values of the pertinent AD
object attribute that match unique values of the corresponding column in the SQL database. The wizard asks you
to specify the SQL database column and AD attribute that correspond to each other for these comparisons:
• Choose a database column from the following: Specify the column in the SQL database whose values
(for contacts) will match the values for the corresponding attribute for associated objects in Active Directory.

IMPORTANT: The AD Object Wizard generates an error if the database column you specify is not
populated with data

• Specify the Active Directory Attribute that matches: Specify the AD attribute whose values (for mail-
enabled objects) will match the values in the corresponding column for associated contacts in the SQL
database.

Choose the Container for User Objects

Create new objects for recipients that do not already exist in Active Directory: Check box that determines
whether the Provisioning Wizard creates a new user object in AD when none is found that corresponds with a user
in the collection. Such new user objects are created in the container specified by the User Container text box.
Usually the created objects are not mail-enabled, although the EnableUsers parameter (in Task Parameters) can
be set to 1 to change the default behavior.
User Container: Click Browse to find and specify the relative domain name for an existing organizational unit (for
example, cn=users) where any new user objects will be created in AD—when a wizard encounters a Contact for
which there is no corresponding AD user account.
When the values on this screen are set as you want them, click Next.

Generating Task
No information is entered into this screen.
This screen reports progress as the wizard determines the details and associated work items for the task. You can
review (in the next screen) the details and associated work items, and decide whether to create the task, or go
back and change any specifications that define the task.
When this generation process is complete, the wizard displays the next screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

77
Provisioning Wizard
Configuration Summary
This screen shows a summary of the task configuration you specified.
Review this information to confirm that it describes the task you want to create. To change anything, click Back to
return to earlier screens and change values as necessary, or click Cancel to return to the Provision screen in the
Notes Migration Manager. From earlier screens in the wizard, you can click Next to return to this Configuration
Summary screen.
When the configuration summary describes this provisioning task as you want it to run, you can click:
• Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and
filename for the text file.
• Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the
destination printer.
• Next: Creates the task as defined in the configuration summary, and displays a Specify Task Schedule
screen in which you can run the task immediately, or schedule the task for a specified time.

Creating Task
No information is entered into this screen. This screen reports progress as the wizard creates the task defined on
the preceding Configuration Summary screen.
When the task-creation process is complete, the wizard clears this screen and runs the newly created task.

Specify Task Schedule

This screen lets you specify when to run the task you have created—immediately, or at some later time.

NOTE: The Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, as explained in chapter 13 of the Migrator
for Notes to Exchange Administration Guide. The Task Scheduler checks the SQL database to see whether
any tasks have been scheduled to run since the last check, and runs any such tasks it finds. See chapter 13
for more information about the Task Scheduler.

The drop-down list at the top of the screen offers these scheduling options:
• Now on this computer: The wizard runs the task as soon as you click Next. The other scheduling controls
on the screen appear grayed out (unavailable), since they do not apply. Click Next to display the Task
Progress screen.
• One or more times, as indicated below: The task runs one or more times, according to your entries in the
scheduling controls. If you select this option you must specify where and when you want the task to run in
the scheduling controls.
• Manually: The task will not run or be scheduled at all. The other scheduling controls on the screen appear
grayed out (unavailable), since they do not apply. Click Next to display the Schedule Summary screen.
• Once: The task runs only once and will not repeat. You can specify where to run and the start date and
time.
These scheduling controls are enabled only if One or more times... is selected in the drop-down list:
• Where to run: Select either On any computer or On a specific computer. If you choose a specific
computer, you must also specify the machine name in the adjacent text box.
• When to run:
▪ Start: Specify the calendar date for the first (or only) task run.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

78
Provisioning Wizard
 ▪ Days of the Week: Specify one or more days of the week that you want the task to run. If you select
two or more days, the first task run will occur on the first selected day occurring on or after the
specified Start date.
▪ Between [____] and [____]: Specify the beginning and ending times of a range of start times for
the task to run.
▪ Select one of these options for the end date:
▫ No end date: The task runs will adhere to this schedule until someone manually ends the
series by editing this schedule definition in Notes Migration Manager (in the Manage
Scheduled Operations screen).
▫ End after __ occurrences: The task runs will adhere to this schedule until the cumulative
number of runs matches the number specified here.
▫ End by: The task runs will adhere to this schedule until the calendar date specified here
▪ [_] Start this task only after completing: [________________________]: Select this check box if
you want this new task to run only after some other previously defined task has run. If you select the
check box, use the drop-down list to specify which previously defined task must precede this one.
When you have set the task schedule, click Next to display the Task Progress and Schedule Summary screens.

Task Progress
No information is entered into this screen. The screen reports the program's progress as it performs the defined
task. You can click Cancel to cancel the task before it completes.
When the process is complete, the program displays its Task Completed screen to report the results.

Task Completed
No information is entered into this screen. The screen reports the results of the task run.
This screen can display an Error Log Report button if the program encountered errors during its run. If the Error
Log Report button appears, click it to view the program log and assess the severity of the errors. The Error Log
Report button launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and resolve
the errors.
When you are finished, click Exit.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

79
Provisioning Wizard
 9
Send PAB Replicator Wizard
• Introduction
• Wizard process screens

Introduction
The Send PAB Replicator Wizard sends a special email form to Notes users in a particular user collection that lets
them copy all their PABs (personal address books) to a centralized Notes server directory, where the Data
Migration Wizard can find and migrate them.
The PAB Replicator Wizard is applied to a particular user collection, designated in the Send PAB Replicator screen
of Notes Migration Manager, from which this wizard is launched. Field definitions and application notes for the
wizard’s screens are provided in the sections that follow.

NOTE: The email form that this feature sends to users contains a button icon that users can click to start the
replication function. An iNotes client, however, renders the message as plain text, so the button does not
appear for iNotes users. The form tells users to Press the button below so the loss of the button in iNotes
can confuse iNotes users who receive the form. Most iNotes users do not need the PAB Replicator form
since their address books are stored in their mail files. However, if your user population contains iNotes
users and Notes users, you may want to organize your collections to segregate the two groups and send the
PAB Replicator form only to the latter.

Migrator for Notes to Exchange offers a choice of six standard templates for the Replicator form and you can
customize any of the templates to suit your needs. The wizard also signs the selected Replicator form with the
digital keys associated with a specified administrator (identified during the program run), to authorize running the
form’s instructions on user workstations and on the server without triggering security alerts (or at least triggering
fewer of them).

NOTE: The administrator specified on the wizard Notes Login screen is identified as the sender (From) of
the form, and is the administrator whose digital keys are used to sign the form. The User ID file must be the
one that is on the ECL when sending PAB Replicators—not a separate, Quest-specific ID file that would not
be present on the ECL.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

80
Send PAB Replicator Wizard
Wizard process screens
The Send PAB Replicator Wizard is configured in these screens:
• Customize Configuration
• Select User Collection
• Specify Notes Login Information
• Replicator Information
• Select User
• Confirm Create Access
• Generating Task
• Configuration Summary
• Creating Task
• Task Progress
• Task Completed

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable this capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.
The Advanced Settings option is a toggle that determines whether the wizards let you open and edit Task
Parameters. If the feature is enabled, the Customize Configuration screen is displayed at the start of the screen
sequence for any wizard that offers this feature.
Task Parameters are edited as if the parameters were stored in an INI file, although the parameters are stored as
part of the task definition within the SQL database. The Customize Configuration feature copies the current
parameter settings from the SQL database into a text document in Windows Notepad, so you can use the Notepad
text-editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task configuration settings in Windows Notepad.
2 Find the pertinent [SectionName] for the parameter you want to add, or the value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is very important
that parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter value(s) back into the SQL database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

81
Send PAB Replicator Wizard
Select User Collection
This screen appears only if you have started this Wizard from outside of the Notes Migration Manager. The screen
asks you to specify the user collection to which you want to apply this Wizard’s functions. (If you launch this screen
from outside of the Migration Manager, you must select a collection in the table before you can click the button to
start the wizard.)
This screen contains only one field:
• Select the User Collection you want to work with: Use the drop-down list to specify the collection to
which you want to apply this Wizard’s functions.
Click Next.

Specify Notes Login Information

This screen appears even if the information it requests has already been collected in Notes Migration Manager
(Notes Server Configuration screen). The credentials specified here will authenticate the administrator whose
digital keys will be used to sign the form.
• Server: Specify the server the wizard will use to access the Name and Address Book and route the
replicator emails generated by the wizard.
• User ID file: This field specifies the administrator whose digital keys will be used to sign the replicator form.
Click the Browse button to find and specify the path and filename of the User ID file, or type or paste the
path and filename into the text box. The User ID file must be the one that is on the ECL when sending PAB
Replicators—not a separate, Quest-specific ID file that would not be present on the ECL.
• Password: Type the password associated with the User ID file.
Enter the requested information, and click Next.

Replicator Information
Enter the particulars of the Mail Message that will carry the upload form to users, and the Destination for the users'
PABs, and click Next.
Mail Message entries and controls:
• Template: A drop-down list to specify the template form that constitutes the body of the email message.
The wizard offers a choice of six predefined forms:
▪ PabReplicator.CopyToServer: Copies PABs to the specified Domino server directory. Does not
use mail file.
▪ PabReplicator.CopyToServer.Popups: Same as PabReplicator.CopyToServer, but also displays
informational popups (message boxes) before and after the form runs.
▪ PabReplicator.SyncAndCopyToMailFile: Performs iNotes sync if available, copies all remaining
PAB entries to mail file.
▪ PabReplicator.SyncAndCopyToMailFile.Popups: Same as the
PabReplicator.SyncAndCopyToMailFile but also displays informational popups (message boxes)
before and after the form runs.
▪ PabReplicator.SyncAndCopyToServer: Performs iNotes sync if available, copies PABs to the
specified Domino server directory.
▪ PabReplicator.SyncAndCopyToServer.Popups: Same as PabReplicator.SyncAndCopyToServer,
but also displays informational popups (message boxes) before and after the form runs.
To the right of the Template field:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

82
Send PAB Replicator Wizard
 ▪ Customize...: Launches the Notes client, which lets you modify the selected Template form to suit
your own needs.
• Following the Template field, a non-editable Comment provides a brief description of the selected
Template.
• From: The string to be inserted into the From field in the email.
▪ Address...: Lets you consult the Domino address book and select a name and address to be auto-
inserted into the From box.
• Subject: The string to be inserted info the Subject field in the email.
Destination (fields are grayed out if the selected Template does not need a destination server/directory):
• Server: The name of the server to which user PABs will be uploaded. The server specified here must be
accessible by the Notes Login User ID file and Password specified in the preceding screen.
• Directory: The directory on the server to which user PABs will be uploaded.

Select User
This dialog box lets you select, from the Domino address book, a user to appear in the From field of the PAB
Replicator email. The name you specify in the User side of this dialog box will be inserted into the From field on
the Replicator Information screen when you click OK.
Use the add (—>) and remove (<—) features as described to select a particular user, and click OK.

Table 1. Select User dialog options.

If you want Action

To change the address book (contents of the left- Use the Show Names from drop-down list (top-right corner
side list) of the dialog box) to select a different address book.
To add a name to the User list Select a name from the address-book list on the left side of
the screen and click the right arrow button.
To remove a name from the User list Select the name from the list and click the left arrow button
To display the previous screen and copy the Click OK.
designated User to the From field

Confirm Create Access

This is a popup that appears only if the target server Server document has a non-blank Create databases and
templates. (When Create databases and templates is blank, all users have access.)
If the popup appears, check if each user in the collection appears in the displayed list of users who are permitted
to Create databases and templates and click the appropriate response button:
• Yes: Proceeds with sending the PAB Replicator form to all users. However, if a user not on the list, the
wizard uses the email form to attempt a PAB upload and the attempt fails.
• No: Cancels the run so you can use Domino administrative features to make all users eligible and attempt
access again.

Generating Task
This screen reports the wizard's progress as it determines the details and associated work items of the task you
configured. You can review (in the next screen) the details and associated work items, and decide whether to
create the task, or go back and change the specifications that define the task.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

83
Send PAB Replicator Wizard
When this generation process is complete, the wizard displays the next screen.

Configuration Summary
This screen shows a summary of the task configuration as defined by the information entered in previous screens.
Review the information to confirm that it describes the task you want to create. To change anything, click Back to
return to earlier screens to change values, or click Cancel to cancel the wizard and return to the Send PAB
Replicator screen in Notes Migration Manager. From earlier screens in this wizard, you can click Next to return to
this screen.
Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and filename
for the text file.
Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the destination
printer.
Run: Creates the task as defined in the configuration summary and immediately runs the task. When you click
Run, the wizard displays a screen that reports progress as the task is created and displays a screen that reports
progress as the task runs. When the task run is complete, the wizard displays a screen that reports the statistical
results of the task.

Creating Task
This screen reports the wizard's progress as it creates the task defined on the preceding Configuration Summary
screen. When the task-creation process is complete, the wizard clears this screen and runs the newly created
task.

Task Progress
The screen reports the program's progress as it performs the defined task.
You can click Cancel to cancel the task before it completes.
When the process is complete, the program displays its Task Completed screen to report the results.

Task Completed
The screen reports the results of the task run.
This screen can also display an Error Log Report button if the program encountered errors during its run. If the
Error Log Report button appears, click the button to view the program log and assess the severity of the errors.
The Error Log Report button launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you
interpret and resolve the errors.
When you are finished using the Error Log Report feature (or if the Error Log Report button does not appear),
click Exit to exit the wizard.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

84
Send PAB Replicator Wizard
 10
Data Migration Wizard
• Introduction
• Wizard process screens

Introduction
The Data Migration Wizard is a multi-function application that lets you perform various functions in various
combinations in a single program run. The first screens in each program run ask what you want to accomplish. The
program proceeds through a sequence of screens, skipping screens that do not pertain to the functions you
selected.
The wizard features can be grouped into these categories
• mailbox creation (mailbox-enabling) in the target environment
• setting and removing mail routing rules in source and target
• user data migration
• administrative functions such as disabling Notes synchronization with the foreign directory, setting user
visibility in Domino, and so forth.

To start the Data Migration Wizard:

• In the Migrate User Data screen of Notes Migration Manager, select a user collection and click Migrate.

NOTE: Many screens described in this chapter are conditional, appearing in a wizard only when
necessary for the selected features and functions, and for the local network configuration and
designated target environment type.

Field definitions and application notes for the wizard screens appear in separate sections that follow, grouped by
screen.

Smart resource reservation detection: The Data Migration Wizard detects an attempt to migrate calendar
data for a collection in which some objects are not classified as resources in the MNE database when [Notes]
MigrateReservationsAlways is enabled (set to 1).
In that case, the wizard presents a popup warning that explains that calendars of a non-resource object may
not migrate correctly, and suggests that the MigrateReservationsAlways parameter be disabled (set to 0)
unless the administrator is certain all objects in the collection are resources. This feature offers the option of
ignoring a MigrateReservationsAlways=1 setting.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

85
Data Migration Wizard
Wizard process screens
The Data Migration Wizard is configured in these screens:

Select Configuration Specify Remove Notes Forwarding Settings

Select User Collection Select Notes User Visibility
Customize Configuration Specify Active Directory Information
Operations How Were Accounts Loaded into Active Directory
Select Office 365 Administrative Operations Specify Exchange Mailbox Information
Configure Migration Notification Messages Specify Notes Login Information
Select Notes Administrative Operations Select Date and Size Filters
Specify Data for Migration Select Destination Exchange Server
Specify How To Migrate Notes DocLinks Personal Archive Location
Notes Mail Files Specify Migration Run Information
Select Destinations for Migrated Data Generating Task
Specify Mail Routing Options Configuration Summary
Specify Notes to Exchange Mail Forwarding Creating Task
Specify Remove Exchange Forwarding Settings Specify Task Schedule
Specify Exchange to Notes Mail Forwarding Schedule Summary
Task Progress
Task Completed

Select Configuration
This screen lets you save and recall sets of entries as templates to simplify future runs of the wizard when you
expect to have multiple runs that are similarly configured. Each configuration template consists of the entries on all
the wizard screens.
Create new configuration or select from existing templates: A drop-down list lets you select a previously
saved template or create a new configuration <Create new configuration>. Previously saved templates are listed
by the names under which they were saved (see the Name field).
If you choose <Create new configuration> from the drop-down list, the wizard displays:
• [ ] Save as template: When the option is selected, your entries in the screens are saved as a template for
future use. This option enables the Name and Description fields. The name you assign to the template
appears in the drop-down list in future wizard runs.
When you select Save as template, you can create a Full Template or a Differential template.
▪ A full template is a snapshot of the INI configuration file that was used to run a task when the
template was created. The INI file includes all the settings from the Global Default settings plus any
additions or modifications that were made by the wizard used to run the task. A full template does
not retrieve new Global Default settings after it is created.
▪ A differential template contains only the INI settings that are different than those in the Global
Default INI file rather than saving all the INI settings in the template. A differential template can
retrieve new Global Default settings.
A differential template takes precedence over the Global Default settings. Consider the following scenarios:
▪ A parameter in the Global Default settings is changed in the differential template. The differential
template setting is used.
▪ A parameter in the Global Default settings is removed from the differential template. The differential
template setting is used. Changing the setting in the Global Default settings has no impact on the
differential template.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

86
Data Migration Wizard
 ▪ A parameter is not in the Global Default settings when a differential template is created. When the
parameter is added to the Global Default settings, it is also added to the differential template.
▪ A parameter is set to the same value in the Global Default settings and in the differential template.
When the parameter is removed from the Global Default settings, it is also removed from the
differential template.
▪ A parameter is set to the same value in the Global Default settings and in the differential template.
When the parameter is changed in the Global Default settings, the differential template is updated
with the new value.
If you select a previously saved template from the drop-down list, the wizard imports the saved settings into the
wizard screens and displays:
• [ ] Modify this template: Select this check box to run the wizard with one or more entries that are different
from the settings that were imported from the selected template.
This option permits changes to the settings that appear in its screens including the Name and Description
fields. (You can save the changes under a new template Name, and leave the original selected template
unchanged.)
If the check box is left empty, the wizard skips most of its screens when you click Next and goes directly to
the Configuration Summary screen.
• Delete Selected Template: Click this button to delete the selected template from the drop-down list (which
makes it unavailable for future runs). If you click Delete, the wizard prompts you to confirm (or cancel) the
command.
Click Next to save your entries and display the next screen.

Select User Collection

This screen appears only if you started this wizard from outside of the Notes Migration Manager. The screen asks
you to specify the user collection to which you want. (If you launch this screen from outside of the wizard, you must
select a collection before you can click the button to start the wizard.)
This screen contains only one field.
• Select the User Collection you want to work with: Specify the collection to which you want to apply the
wizard functions.
Use the drop-down list to specify your choice and click Next.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in the Notes Migration Manager.
The Advanced Settings option is a toggle that determines whether you can open and edit Task Parameters. If the
feature is enabled, this Customize Configuration screen appears at the start of the screen sequence for any wizard
that offers this feature. To enable or disable the ability to edit Task Parameters, in Notes Migration Manager, select
View and select or clear the Advanced Settings option.
Task Parameters are edited as if the parameters were stored in an INI file although the parameters are stored as
part of the task definition in the SQL database. The Customize Configuration feature copies the current parameter
settings from the SQL database into a text document in Windows Notepad, so you can use the Notepad text-
editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task configuration settings in Notepad.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

87
Data Migration Wizard
 2 Find the [SectionName] for the parameter you want to add or the parameter value you want to edit.

NOTE: Some parameters in different sections share the same keyname so it is important that
parameter values are entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter values into the SQL database.

Operations
Select the types of operations you want to perform during this run and click Next. The available function categories
that appear depend on the target Exchange environment type you have specified in Notes Migration Manager as
listed in the following topics.

Operations screen when migrating to a local, proprietary

Exchange, or a “hosted Exchange”
When migrating to on-premises Exchange or to “hosted Exchange” (other than Office 365), the Operations screen
lists the following options:
• Mailbox-enable existing Active Directory accounts (this option disabled for Hosted Exchange): Creates
a new Exchange mailbox for each user in the selected collection whose Exchange account has already
been mail-enabled, and for each security object found in Active Directory.
In a typical scenario, the user Exchange accounts are created and mail- enabled by the Quest Coexistence
Manager for Notes (CMN) Directory Connector.
• Manage mail routing: Displays a screen with options for setting and removing mail- forwarding rules in the
source and target environments, for all users in the designated collection.
• General administrative functions (visibility and directory sync flags, migration notifications):
Displays a screen with options for disabling Notes synchronization with AD, setting user visibility in
Domino, sending migration notifications to migrated users, and sending migration status notifications to
administrators.
• Migrate mailbox data: Displays a screen with options for migrating user data from Notes to Exchange in
any combination of: server-based or archived mail, calendar data, trash folder, iNotes contacts, and/or
personal address books.

NOTE: By default, the wizard preserves ACL information as it migrates Notes source data to Exchange. To
disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults.

NOTE: If the Notes Data Locator Wizard finds a PAB or Archive twice (once by the server and again by the
file system), the Data Migration Wizard tries to migrate it twice. But the file-system attempt will fail and
generate an error because the prior successful server access locked the file, rendering it inaccessible. The
Data Locator Wizard cannot be configured to search using both methods at once, but you can run the wizard
more than once, selecting different search methods in subsequent runs.

Operations screen when migrating to Office 365 with

Microsoft AD synchronization
When migrating to Office 365 and using the Microsoft AD synchronization tool, the Operations screen offers the
following options:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

88
Data Migration Wizard
 • Prepare local Active Directory accounts for MS AD Sync: Prepares the accounts in your local AD to be
provisioned into the Office 365 AD by the Microsoft AD synchronization tool.

IMPORTANT: The Prepare local AD accounts feature is a necessary administrative step that must
precede running the MS AD synchronization, and must precede running this wizard for any other
function. After running MS AD synchronization, you must run the Data Migration Wizard again and
Set Office 365 resource capacity (below) to complete mailbox-enabling in Office 365.

NOTE: When you select Prepare local AD accounts, all other options are disabled (grayed out).
When you select any other option, the Prepare Local AD accounts option is disabled.

• Set Office 365 resource capacity: Reads (from the local AD) the capacities of any resource objects in the
collection, and copies that information into the corresponding object records in Office 365 AD. Do not select
this operation until you have completed the Prepare local Active Directory accounts operation and
successfully run MS AD sync.
• Manage mail routing: Displays a screen with options for setting and removing mail-forwarding rules in the
source and target environments for all users in the designated collection.
• Notes administrative functions (includes setting visibility and directory synchronization flags):
Displays a screen with options for disabling Notes synchronization with AD, setting user visibility in Domino
or both environments, sending migration notifications to migrated users, and sending migration status
notifications to administrators.
• Office 365 administrative functions (includes password reset and license assignment): Select this
check box to display the Select Office 365 Administrative Operations screen. On that screen, you can reset
passwords and specify licensing options.
• Migrate mailbox data: Displays a screen with options for migrating user data from Notes to Exchange, in
any combination of: server-based or archived mail, calendar data, the trash folder, iNotes contacts, and/or
personal address books.

NOTE: By default, the wizard preserves ACL information as it migrates Notes source data to Exchange. To
disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults.

NOTE: If the Notes Data Locator Wizard finds a PAB or Archive twice (once by the server and again by the
file system), the Data Migration Wizard tries to migrate it twice. But the file-system attempt will fail and
generate an error because the prior successful server access locked the file, leaving it inaccessible. The
Data Locator Wizard cannot be configured to search using both methods at once, but you could run the
wizard more than once, selecting different search methods in subsequent runs.

Operations screen when migrating to Office 365 without

Microsoft AD synchronization
When migrating to Office 365 without Microsoft AD synchronization, the Operations screen offers the following
options:
• Create Office 365 accounts: Creates a new Office 365 Exchange mailbox and sets user properties for
every user in the selected collection.
• Manage mail routing: Displays a screen with options for setting and removing mail-forwarding rules in the
source and target environments for all users in the designated collection.
• Notes administrative functions (includes setting visibility and directory synchronization flags):
Displays a screen with options for disabling Notes synchronization with AD, setting user visibility in Domino
or both environments, sending migration notifications to migrated users, and sending migration status
notifications to administrators.
• Office 365 administrative functions (includes password reset and license assignment): Select this
option to display the Select Office 365 Administrative Operations screen. On that screen, you can reset
passwords and specify licensing options.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

89
Data Migration Wizard
 • Migrate mailbox data: Displays a screen with options for migrating user data from Notes to Exchange, in
any combination of: server-based or archived mail, calendar data, the trash folder, iNotes contacts, and/or
personal address books.

NOTE: By default, the wizard preserves ACL information as it migrates Notes source data to Exchange. To
disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults.

NOTE: If the Notes Data Locator Wizard finds a PAB or Archive twice (once by the server and again by the
file system), the Data Migration Wizard will try to migrate it twice. But the file-system attempt will fail and
generate an error because the prior successful server access locked the file, rendering it inaccessible. The
Data Locator Wizard cannot be configured to search using both methods at once, but you could run the
wizard more than once, selecting different search methods in subsequent runs.

Select Office 365 Administrative Operations

This screen appears if you selected the Office 365 administrative functions check box on the Operations
screen. It lets you select the following options.
• Reset user passwords: Resets the user passwords for mailboxes in the collection. This function assigns
random one-time-only passwords that permit a user to log onto Office 365 the first time.The user must
reset the password to something more durable and memorable.
• Assign user licenses: When this option is selected, MNE performs a new Office 365 user licensing
operation.

NOTE: The Data Migration Wizard can license Office 365 users when the userPrincipalName
differs from the primary SMTP address. With this feature, an administrator can use TSV Import
feature to assign alternate UPN values to the SQL database. To do this, from the Export Notes
Directory screen:
1 Export the collection SQL data to a tsv file.
2 Enter the users' UPN values into the UPN column of the tsv file.
3 Import the tsv file back into the SQL database.
MNE will read the imported UPN values, if they are present in the database, when licensing Office
365 users.
Without this feature, the wizard uses the SMTP address for the userPrincipalName, but this can
cause issues in environments where the userPrincipalName is different, since the Office 365
Administrative Operations wizard would not find the users in the target Office 365 environment.

▪ License users: Select this option to assign licenses to users.

▪ Unlicense users: Select this option to remove user licenses.
▪ Usage Location: Use the drop-down list to specify your users’ Usage Location. This is a
mandatory designation that Microsoft requires for its Office 365 licenses (see this Microsoft article).
Your selection corresponds to a two-letter Usage Location code that is saved in MNE Global
Defaults and Task Parameters as the [Exchange] O365UsageLocation=<xx> parameter.
▪ Product License: Office 365 is available in a variety of plans (see this Microsoft article). MNE
populates the Product License field with the Office 365 licensing plans available to your
organization and the number of licenses available for each plan. If the
[Exchange]O365AccountSkuId parameter is set, the specified license plan is the default
selection.
Select the licensing plan to apply from the drop-down list. Once a licensing plan is selected, all the
services available within the licensing plan are listed. By default, all services are selected. You can
clear a service to disable it. Disabled services are listed in the
[Exchange]O365DisabledServicePlans parameter.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

90
Data Migration Wizard
 NOTE: Unable to assign the license error.
License plan services can have dependencies on other services. When licensing users, MNE
does not validate that the combination of services selected is valid. If you disable a service on
which another enabled service is dependent, user licensing will fail with the error Unable to
assign the license.

Configure Migration Notification Messages

This screen is displayed if you selected Migrate users on the Operations screen, or if you selected Send
migration notification messages on the Administrative Operations screen. You can define personalized (mail-
merge) migration notification emails to send to the users in this collection or define emails containing migration
status summary information to send to administrators.
The first two check boxes let you specify whether to send migration notification messages to Notes mailboxes only,
Exchange mailboxes only, or both. The third check box allows you to send migration status summary messages to
one or more administrators.
The wizard generates the emails by merging a template file with per-user variable values drawn from the collection
data table in the SQL database.

Sending migration notifications to user Notes and/or

Exchange mailboxes
Select options for these message types:
• Send “You’ve been migrated” messages to Notes mailboxes: The wizard generates a merged email to
the Notes mailbox of every user in the collection, notifying them of their migration to Exchange. (The wizard
inserts these messages directly into users’ Notes mailboxes, so they are not intercepted by any forwarding
rules that would re-route them to Exchange.) The email typically explains to users that they have been
migrated to Exchange, and should use the Outlook client for future email and calendar activities. The email
also typically provides each user’s new Outlook login credentials, and any other special instructions or
helpful tips. The default Template file for this email varies depending on your Exchange destination:
▪ ybm_template.html: for migration to any on-premises Exchange server, or to a hosted-Exchange
environment other than Office 365.
▪ ynma_template.html: for migration to Office 365.
Another template file (o365_pwreset.html) is provided for Office 365 migrations, with language and a
merge variable to notify users of their new one-time-only Office 365 passwords. The notice delivers a
randomly generated password (generated by Migrator for Notes to Exchange), and explains that the user
should use it to log on to Office 365 the first time, and change the password to something more durable and
memorable.
• Send “Welcome to Exchange” messages to Exchange mailboxes: The wizard generates a merged
email to the Exchange mailbox of every user in the collection, welcoming them to the Exchange
environment and the Outlook client, and often including an attachment to orient users to their new tools.
The template file for these “Welcome to Exchange” messages is wte_template.html.
Two text boxes also ask you to specify the SMTP address and Display Name to be identified as the
Sender of the messages (usually the migration administrator).
For each selected mail-merge message, you must specify:
▪ Subject: Enter the text to be inserted into the email Subject line.
▪ Template file: Click Browse to locate and specify the template file to be used for the body of the
mail-merge message. You can choose one of the standard templates installed with Migrator for
Notes to Exchange, or create and use your own.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

91
Data Migration Wizard
 NOTE: You can also edit any of the template files to add or delete or modify content to better suit your
organization’s needs. For information about editing and creating these template files, see in Appendix
A: How Do I Create or Edit a Template for Personalized User-Notification Emails?

Sending migration summary messages to administrators

• Send “Migration summary” messages to administrators: The wizard sends a merged email to all the
SMTP addresses that are specified in the Recipient SMTP address text box. The email provides the
migration summary and often includes an attachment containing logs of the migration statistics for each
user in the collection. The email message might also include an attachment that contains a log of deferred
Notes emails to be sent at a future date and time by Domino.
For each selected mail-merge message, you must specify:
▪ Recipient SMTP address: Enter the SMTP address for each administrator that will receive the
migration summary email. You can enter multiple SMTP addresses, separated by a ; (semi-colon).
▪ Subject: Enter the text to be inserted into the email Subject line.
▪ Template file: Click Browse to locate and specify the template file to be used for the body of the
mail-merge message. The template file for the migration summary messages is named
migration_summary_template.html.
Note: If the sent email is triggered by the Migrate mailbox data operation, the migration summary
information describes the current migration statistics. If the sent email is triggered by the General
administrative functions (visibility and directory sync flags, migration notifications) operation, the migration
summary information describes the migration statistics of last data migration that performed the Migrate
mailbox data operation.

Select Notes Administrative Operations

This screen appears if you have selected Notes administrative functions in the Operations screen. Specify
which Notes administrative functions you want to perform for users in the selected collection and click Next.
• Set Notes foreign directory sync (feature available only when not performing mail routing): Allows the
CMN Directory Connector to extract user data from the Notes directory during its directory synchronization.
(This corresponds to the Notes parameter Allow foreign directory synchronization.) To disable foreign
directory synchronization, leave the check box selected but select Disable in the drop-down list. In some
configurations, migrated objects that were merged or mailbox-enabled in AD become unrecognizable to a
Notes directory update, so the update mistakenly creates duplicate objects in AD.
You should Disable foreign directory sync if all of the following conditions apply:
▪ You are using the CMN Directory Connector to perform directory updates from Notes to Exchange
during coexistence.
▪ Your mail-routing method during coexistence is to use Notes forwarding addresses to set forwarding
from Notes to Exchange.
▪ The Notes person documents are not set to turn users into Exchange objects.
• Set Notes user visibility: Lets you specify the preferred scope of user visibility in the Domino directory. If
this check box is selected, the wizard will later display another screen for you to specify user visibility.
• Set Notes Person Document Attributes (appears only if Migrate users is selected on the Operations
screen and the Count=<#> parameter value is greater than zero in the [PersonDocCustom] section of the
Task Parameters): Tells the wizard whether to assign attribute values to Notes person documents as
defined by parameters in the same [PersonDocCustom] section. (See the Program Parameters Reference
Guide for information about how to assign the values.) If this check box is clear, the wizard ignores the
[PersonDocCustom] parameters.
• Send migration notification messages: Select this option to send mail-merge messages when a data
migration is not in progress. It displays the Configure mail-merge messages to migrating users screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

92
Data Migration Wizard
Specify Data for Migration
This screen appears only if you selected Migrate users in the Operations screen. Select items to define the scope
of this migration and click Next. A later screen asks you to specify whether each type of data should be migrated
to personal folder (.pst) files or to server-based mailboxes.

NOTE: If a user mail file is missing or incorrectly specified, the wizard notes the error and does not migrate
the user archives or PABs, even if they are selected for migration.

NOTE: The Data Migration Wizard preserves ACL information, including calendar and task folder ACLs, as it
migrates Notes source data to Exchange. To disable this feature, you could set ACLs=0 in the [General]
section of Task Parameters or Global Defaults.

IMPORTANT: For delegates and ACLs to migrate properly the following prerequisites must be met:
• The ACL/Delegates mailboxes in Exchange must be mailbox-enabled.
• The AD profiles for users that receive migrated ACL information in Outlook must be enabled in AD. (If
the user cannot log on to Outlook, the wizard cannot migrate the ACL data.) If you inadvertently
migrate users who are not enabled in AD, you can remigrate with the RemigrateMode=0 parameter
to replace the previously migrated data (without ACLs) with new copies of the same data with ACLs.

This screen is designed to let you migrate email messages, calendar data, and the trash folder independently from
the server and/or from the archives.
• Migrate mail data: You can specify one or more of email messages, “Active Mail,” calendar data, task
data, the trash folder, and/or iNotes contacts.

NOTE: Active Mail processing is an optional feature that is disabled by default but can be enabled by
the following check box, under the Migrate mail data check box:
[] Migrate Active Mail [Configure]
This Migrator for Notes to Exchange feature can detect and convert Notes rich-content features
whereby messages carry “live” or “active” functional content. For more information about Active Mail,
see Migrating Notes “Active Mail” in chapter 3 of Migrator for Notes to Exchange’s Pre-Migration
Planning Guide.

To enable Active Mail processing: Select the Migrate Active Mail check box, click Configure and enter
your preferences in the pop-up dialog box:
Active Mail types to migrate:
[ ] Encrypted mail
[] Stored forms
[] Hotspots
[] Rich markup
Active Mail template: [_________________] [...]
Notification message: [_________________] [...]
Attachment name: [_________________]
Click OK to save your preferences and return to the Specify Data to Migrate screen.
The Notification message (whose file path is specified in the dialog box) is a file containing a text string
that the wizard inserts at the top of the body of any migrated message containing Active Mail. MNE installs
a default file, ActiveMailNotificationMessage.txt, to the installation directory, but you can specify a different
filename and/or folder in the dialog box.
The text file must be UTF-8 encoded and must contain a placeholder, called $ActiveMailAttachment$, that
MNE replaces with the Active Mail NSF attachment when the message is migrated. Since the contents of
this text file become part of an RTF body, characters such as "\", "{", and "}" must be escaped with a leading
"\" (so they become, respectively, "\\", "\{", and "\}").
• Migrate archives: You can specify one or more of email messages, calendar data, task data, and/or the
trash folder.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

93
Data Migration Wizard
 • Migrate personal address books: The Notes user PABs typically are stored locally (per user), but can
also reside with the mailfile, or on a server, and can be migrated by any of four different methods. The Send
PAB Replicator Wizard can help users copy their PABs to a central location on the Domino server so that
this feature can migrate them. For more information about migrating PABs, see “Migrating PABs” in chapter
3 of the Pre-Migration Planning Guide.
▪ Merge into folder named: Enter the name for the folder that will contain the migrated PABs—a
Contacts folder in a mailbox or .pst file, not a file system folder.

NOTE: If Contacts were migrated to a folder other than the default Contacts folder, the wizard
will remigrate Contacts only to the same folder, even if you specify a different folder name. To
remigrate Contacts to a different folder name, you must hard-delete the previous Contacts
folder and its contents. If you try to remigrate Contacts to a different folder name without
deleting the previous folder, the wizard migrates them (excluding duplicates) to the previous
folder.

▪ Migrate recent contacts into folder named: Enter the name for the folder that will contain the
migrated PABs' Recent Contacts lists.
▪ Set contact 'File as' to: Determines the format of the contact’s File As attribute in Exchange. The
File As attribute is used by Outlook to alphabetize your contacts. The options for this setting are:
▫ Use current display name: Use the Display Name attribute of the address book entry. By
default, the wizard migrates contacts using display names that match the display name of
the contact in Notes, however the contact’s display format can be modified using the
[General] ContactDisplayNameFormat parameter.
▫ FirstLast: Create the File As using the first name and last name attributes separated by a
space. The middle name and name suffix are included if present.
▫ LastFirst: Create the File As using the last name and first name attributes separated by a
comma. The middle name is included if present.

Specify How To Migrate Notes DocLinks

This screen appears only if you have selected Migrate mail data in the Specify Data for Migration screen. Select
one option to specify the format you want migrated DocLinks to take, and click Next. The options are:
• NOTES links (default): This option requires the Notes client to be installed and running on end users’
desktops to facilitate the rendering of the Notes documents.
• Notes .NDL attachment: This option requires the Notes client to be installed and running on end users’
desktops to facilitate the rendering of the Notes attachments.
• HTML links to your Domino webserver: A DocLink migrated as an HTML link will not require the Notes
client on the user’s desktop, and will instead open into a web browser if iNotes is enabled.

NOTE: The Domino webserver option is incompatible with an Offline migration (as described in
chapter 1 of the Migrator for Notes to Exchange Scenarios Guide), since MNE cannot connect to an
offline Domino server to perform the DocLink translation.

• HTML links to your SharePoint Server: A SharePoint server link will point to a document on a separate
SharePoint server. This requires that you have Notes Migrator for SharePoint (formerly “Proposition Portal
format”). If you select the SharePoint option, you must also specify:
▪ Site Address: URL to location of these documents on the SharePoint server.

Notes Mail Files

This screen appears only if you have selected Migrate mail data in Specify Data for Migration. Select one option
to tell the program how to locate server-based mail files for migration and click Next. Your options are as follows:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

94
Data Migration Wizard
 • Through Domino server(s): Tells the program migrate the user server-based mail via the server, which
will require an administrator login. Each user's server-based mail file was located (by an earlier run of the
Notes Data Locator Wizard) by combining the MailServer column and the MailFile column in the SQL
database. This Data Migration Wizard opens the mail file using the administrator user credentials. The
administrator must be listed in the Manager ACL for the NSF file.

NOTE: Private folders cannot be migrated through Domino servers.

• Through the file system: Migrates the user server-based mail through the file system from source files
located in an earlier run of the Notes Data Locator Wizard in subtrees located by the wizard, or in the path
specified by the MailFilePath column of the SQL database.

Select Destinations for Migrated Data

This screen appears only if you have selected Migrate users in the Operations screen. Specify your preferred
target destination (within the Exchange environment) for each type of migrated data and click Next.
For each data type (Archives or Address books or Server-based data), specify where you want items of that
type to be migrated:
• Server-based mailbox
• Personal folders (.pst file)
• Server-based Personal Archive (only for Exchange 2010 or later)

NOTE: When migrating to .pst files, the UseSeparatePSTs parameter (in the Global Defaults and
Task Parameters) lets you specify whether the wizard should migrate all data into a single .pst file per
user, or to multiple .pst files. For more information, see in Appendix A: How Do I Specify Whether to
Migrate to a Single PST File (Per User) or Multiple PST Files?

NOTE: PAB or Archive Notes data will be duplicated in Exchange if you remigrate to the server and
use a different method (server vs. file system) than the first migration. No duplicates will occur when
migrating to PSTs. Any duplicate archives on the server appear in a duplicate folder with the digit “1”
appended to the folder name.

Specify Mail Routing Options

This screen appears only if you have selected the Manage mail routing option in the Operations screen, at the
beginning of this Wizard’s run.

NOTE: The Data Migration Wizard lets you remove and set mail-forwarding rules, and move user data, all in
a single run of the wizard. The wizard always performs the “remove forwarding” function first (per user),
before setting the new forwarding rule in the corresponding mailbox, to prevent mail looping. (If an Exchange
mailbox and its corresponding Notes mailbox are simultaneously set to forward mail to each other, any new
mail arriving in either mailbox would loop endlessly between the two.) As an additional precaution, the wizard
verifies the success of each remove function before setting the new forwarding rule in Notes.

Each of the items in this screen offers a "pick one of the following" choice of two or more options. Specify your
choice for each item, and click Next.
• All new mail for users in the collection will be delivered to: Sets the direction of the mail-forwarding
rules you want to set and remove, and determines which screens the wizard will display to collect the
necessary information:
▪ Notes: Facilitates target-to-source (Exchange to Notes) mail forwarding. The wizard displays the
screens that let you set the forwarding rule in Exchange and let you remove any existing forwarding
rules in Notes.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

95
Data Migration Wizard
 ▪ Exchange: Facilitates source-to-target (Notes to Exchange) mail forwarding. The wizard displays
the screens that let you set the forwarding rule in Notes and let you remove any existing forwarding
in Exchange.
• Mail co-existence is using: Specify the method you want to use for email-routing during the transition
period:
▪ Quest Coexistence Manager for Notes (CMN): Uses CMN to facilitate mail routing by SMTP
addressing, with rich email remediation to resolve many incompatibilities between Notes/Domino
and Outlook/Exchange. If you select CMN here, you must also specify whether you will be ...
▫ Using ActiveMail Processing: Select this check box if you will use the CMN ActiveMail
processing feature, or leave it clear if you will not use those features.

NOTE: Select the Quest Coexistence Manager for Notes option if you are using CMN for
email remediation with SMTP mail routing. Designating CMN for mail routing here will process
user objects in a way that requires using the CMN option as the method for Calendar
coexistence (next field). If you select CMN here, the wizard selects the CMN option for your
calendar coexistence method.

▪ SMTP: Uses SMTP addressing for mail routing, but requires admin configuration of Notes person
documents and AD object records.

Specify Notes to Exchange Mail Forwarding

This screen appears only if you have chosen Exchange as the destination for new emails (in the preceding
Specify Mail Routing Options screen). Enter the information required to facilitate the mail-routing scheme you want
to implement in this run of the wizard, and click Next.
• Set mail domain: Select this check box, and enter the Notes Mail Domain parameter value in the
accompanying text box, if you want to forward mail from Notes to Exchange. If CMN is selected for mail
coexistence, the check box is selected, the value is blank, and the entire item is grayed-out to prevent any
changes.
• Set mail system: Select this check box and select the Mail System value (a Notes parameter, Notes or
Other or Other Internet Mail) from the accompanying drop-down list. If CMN is selected for mail
coexistence, the check box is selected, the value is set to Other Internet Mail, and the entire item is grayed-
out to prevent any changes.
• Set calendar domain: Select this check box and enter a value (a Notes parameter) in the accompanying
text box if you want to forward free- busy lookup replies from Notes to Exchange. If CMN is selected for
mail coexistence, the check box is select and grayed-out to prevent changes, and the text box must contain
the name of the Foreign Domain specified in the Domino Administrator’s Domain Configuration.
• Set server running qcalcon (or excalcon): Name of the server running the qcalcon (for the CMN
Free/Busy Connector) application. This field is enabled only if CMN is selected for mail coexistence. Set
the value here to the Notes Mail Server parameter.
• Specify your Domino domain (field is enabled only if CMN is selected for mail coexistence): The root
(highest- ranking) domain containing the Domino server. If, for example, your server is server/xyzcorp,
enter xyzcorp here.
Mail forwarding address options:
• Set mail forwarding address: Select this check box if you want the wizard to compose and use email
forwarding addresses for the users in the designated collection. (This is mandatory if you want to forward
mail or free/busy lookup replies from Notes to Exchange.) If you select this check box, you must also
choose between these two options:
▪ Use current Domino internet address: Migrator for Notes to Exchange uses the internet address
already configured in Domino.
▪ Build address from: Select an option from the drop-down list to specify the method by which the
Data Migration Wizard composes forwarding addresses from Notes to Exchange. By default the
wizard uses the Internet Address method. The options in the list are:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

96
Data Migration Wizard
 ▫ Internet Address (default): The left-hand side (LHS) of the Target- Address column in the
collection data table becomes the LHS of the forwarding address to which the wizard
appends the Forwarding mail domain specified below.
▫ TargetForwardingAddress: The TargetForwardingAddress column in the collection data
table becomes the entire forwarding address. If this column is empty in the data table, the
wizard generates suitable values.
▫ Notes Address: The SourceAddress column in the data table becomes the left-hand side
(LHS) of the forwarding address to which the wizard appends the Forwarding mail domain
specified below.
Forwarding mail domain (field is disabled/grayed-out if Build address from is set to
TargetForwardingAddress): The domain (in SMTP format) to which mail is forwarded from
Notes to Exchange—for example, fwd.sitraka.com.
• Append Domino domain to forwarding address: Select this check box if you want the second @XXXX
element from the Domino forwarding address and AD proxyAddress values to be appended to the
forwarding address string:

If check box is selected: If check box is not selected:

user@smtp.sitraka.com@DOMDOMAIN user@smtp.sitraka.com
smtp:user@smtp.sitraka.com@DOMDOMAIN smtp:user@smtp.sitraka.com

This option can be useful when using CMN for coexistence and new mail goes to Exchange, if users in a
single collection but two different Domino domains migrate with mail routing. This option could be used to
not include the same domain for every user, when it is incorrect for some users. Other adments may be
needed outside of Migrator for Notes to Exchange to make free/busy or mail coexistence work.
Sample address: An illustration of the format of a complete forwarding address, as defined by your two
preceding entries. An informational display only, this value can be changed only indirectly, by changing
either or both of the two preceding entries.
• Overwrite existing mail forwarding address: Select one of three options to indicate whether the
forwarding address as defined on this screen should overwrite any existing mail-forwarding rules the
wizard may find already in place for a user:
▪ Only if domain matches “Forwarding mail domain”: Overwrites an existing forwarding address
with the new forwarding address as defined only if the domain of the old address is the same as the
specified Forwarding mail domain. This is a precaution to prevent the inadvertent overwriting or
removal of existing forwarding that have nothing to do with migration.
▪ Always: Always overwrites any existing forwarding address with the new forwarding address as
defined on this screen.
▪ Never: Never overwrites existing forwarding address with the new forwarding address—it skips the
mail-routing function for any user whose Notes account already contains a mail-forwarding.
• Verify source forwarding address in target mail system: Determines whether the wizard verifies the
existence of each target forwarding address in Active Directory before setting it as a forwarding address in
Domino. This check box is selected by default. Validating the AD address can cause problems when an
email address does not exist in AD (for example, in an Office 365 or other hosted-Exchange migration),
since MNE does not set the forwarding address in Notes. Quest recommends that you clear the check box
for an Office 365 or other hosted-Exchange migration.

Specify Remove Exchange Forwarding Settings

This screen appears only if you select Exchange as the destination for new emails in the Specify Mail Routing
Options screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

97
Data Migration Wizard
 NOTE: The Data Migration Wizard lets you remove and set mail-forwarding rules and move user data, all in
a single run of the wizard. The wizard always performs the “remove forwarding” function first (per user),
before setting the new forwarding rule in the corresponding mailbox to prevent mail looping. As an additional
precaution, the wizard also verifies the success of each remove function before setting the new forwarding
rule in Notes.

Many migrating organizations configure the user Exchange accounts to forward mail to the corresponding
mailboxes in Notes for any mail that arrives in Exchange before the users are migrated. As each user group
migrates, the original forwarding rule in Exchange must be removed and a new forwarding rule is set in Notes so
any mail arriving in Notes is routed to the corresponding mailbox in Exchange. If the Notes-to-Exchange
forwarding rule is set before the Exchange-to-Notes rule is removed, new mail arriving in either mailbox will loop
endlessly between the two—a phenomenon known as mail “looping.” This screen collects the information that the
wizard needs to remove any previously set mail-forwarding rules in Exchange.
Enter the requested information in this screen, and click Next.
• Remove directory synchronization exclusion (This check box is enabled only when CMN Coexistence
is specified): Removes an attribute set by CMN that allows the object to sync back to the other system.
Mail forwarding address options:
• Remove mail Forwarding address: Select this check box if you want to remove previously set mail-
forwarding rules it may find in Exchange, per the Only if... vs. Always option selected.
• Remove existing forwarding address:
▪ Only if domain matches “Forwarding mail domain”: Removes previously set mail-forwarding
rules found in Exchange only if the domain in the found address matches the specified Forwarding
mail domain. This is a precaution to prevent the inadvertent overwriting or removal of existing
forwarding that have nothing to do with migration.
▪ Always: Removes all previously set mail-forwarding found in Exchange, regardless of the
Forwarding mail domain.

Specify Exchange to Notes Mail Forwarding

This screen appears only if you have chosen Notes as the destination for new emails (in the Specify Mail Routing
Options screen). Enter the information required to facilitate the mail-routing scheme you want to implement in this
run of the wizard, and click Next.

NOTE: Migrator for Notes to Exchange’s Exchange-to-Notes mail forwarding ordinarily sets the MailServer
attribute in a Notes Person document in flat format (i.e., ServerName/DomainName). In some environments,
however, that practice can inadvertently disable mail routing. In that case, the problem may be resolved by
setting the MailServer attribute in canonical format (i.e., CN=<server>/O=<domain>).
A boolean program parameter determines how the Data Migration Wizard will format the MailServer attribute
when configuring Exchange-to-Notes forwarding. For example:
[Notes]
UseCanonicalForwardingServerName=1
... tells the wizard to write the attribute in canonical format (CN=ServerName/ O=DomainName), which is
suitable for mail routing via CMN, but not via SMTP. By default (UseCanonicalForwardingServerName=0)
the attribute is set in flat format: ServerName/DomainName.

Mail forwarding address options:

• Set mail forwarding address: Select this check box if you want the wizard to compose and use email
forwarding addresses for the users in the designated collection. (This option is mandatory if you want to
forward mail from Exchange to Notes.)
▪ Address format: This field indicates whether the forwarding address format is set to SMTP or
Notes-style addresses. The value cannot be changed here, and is set via the Mail Co-Existence
field on the Specify Mail Routing Options screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

98
Data Migration Wizard
 • Build address from: Select an option from the drop-down list to specify the method by which the Data
Migration Wizard will compose forwarding addresses from Exchange to Notes. By default the wizard will
use the Notes Address method. The options in the list are:
▪ Notes Address (default): The SourceAddress column in the data table becomes the left-hand side
(LHS) of the forwarding address, to which the wizard will append the Forwarding mail domain
specified below.
▪ Internet Address: The left-hand side (LHS) of the TargetAddress column in the collection data
table becomes the LHS of the forwarding address, to which the wizard appends the Forwarding
mail domain specified below.
▪ SourceForwardingAddress: The SourceForwardingAddress column in the collection data table
becomes the entire forwarding address. If this column is empty in the data table, the wizard
generates suitable values.
• Forwarding mail domain: The domain to which mail will be forwarded, from Exchange to Notes:
▪ If the Address format field is set to SMTP, enter the SMTP-format domain name (for example,
"fwd.sitraka.com”).
▪ If the Address format field is set to "Notes" (to route email using Notes style addresses), enter the
name of the Notes foreign domain name for the Exchange system (for example, "Exchange").
• Sample address: An illustration of the format of a complete forwarding address as defined by your entries.
An informational display only, this value can be changed only indirectly by changing either or both of the
two preceding entries.
• Overwrite existing mail forwarding address: Select one of three options to indicate whether the
forwarding address should overwrite existing mail-forwarding the wizard may find for a user:
▪ Only if domain matches “Forwarding mail domain”: Overwrites an existing forwarding address
with the new forwarding address only if the domain of the old address is the same as the specified
Forwarding mail domain. This is a precaution to prevent the inadvertent overwriting or removal of
existing forwarding rules that have nothing to do with migration.
▪ Always: Always overwrites any existing forwarding address with the new forwarding address as
defined on this screen.
▪ Never: Never overwrites any existing forwarding address with the new forwarding address— skips
the mail-routing function for any user whose Notes account already contains a mail-forwarding.

Specify Remove Notes Forwarding Settings

This screen appears only if you selected Notes as the destination for new emails (in the earlier Specify Mail
Routing Options screen).
Most migrating organizations set mail-forwarding rules in Notes as users migrate to Exchange so any mail arriving
in Notes is routed to the corresponding mailboxes in Exchange. In some circumstances, an organization may want
to reverse the mail-forwarding flow for a time—to set forwarding rules in Exchange to route mail back to Notes. In
that case, any previously set forwarding rules in Notes must be removed to prevent mail looping—a phenomenon
where rules in both mailboxes, each pointing to the other mailbox, cause new mail to loop endlessly between the
two. This screen collects the required information for removing any previously set mail-forwarding rules in
Exchange.

NOTE: The Data Migration Wizard lets you remove and set mail-forwarding rules, and move user data, all in
a single run of the wizard. The wizard always performs the “remove forwarding” function first (per user),
before setting the new forwarding rule to prevent mail looping. The wizard also verifies the success of each
remove function before setting the new forwarding rule.

Enter the requested information in this screen and click Next.

Do not change Notes forwarding attributes: Select this box to disable the remaining fields on this screen, if you
do not want to remove any existing mail-forwarding rules from Notes. If this box is not selected, select or clear the
following fields and enter suitable values to specify how you want to change Notes forwarding attributes:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

99
Data Migration Wizard
 • Set mail domain: Select this check box and enter the domain value (Notes parameter Domain) in the
accompanying text box to permit mail delivery in Notes.
• Set calendar domain: Select this check box and enter the calendar domain value (Notes parameter
Calendar domain) in the accompanying text box to permit the delivery in Exchange of free/busy lookup
replies.
• Set mail system: Select this check box and select the Mail System value (a Notes parameter: Notes or
Other or Other Internet Mail or None) from the accompanying drop-down list.

NOTE: If there is no valid user mail file specified in its SQL database, this Set mail system field must
be set to None or the wizard will ignore all these Notes forwarding attributes settings.

• Set format preference: Select this check box and use the drop-down list to select the appropriate value to
set for the Notes parameter, Format preference for incoming mail. The wizard sets this value to Prefers
MIME upon users’ migration to Exchange; this field lets you restore the prior value (typically Keep in
senders’ format) if you prefer. Select Prefers MIME setting if you will use CMN without Active Mail
remediation, or select Keep in senders’ format to use CMN with Active Mail.
• Allow foreign directory synchronization: Lets the CMN Directory Connector extract user data from the
Domino directory during its dirsync. (This corresponds to the Notes parameter Allow foreign directory
synchronization.) To disable foreign directory sync, leave the check box selected but select Disable in the
drop-down list. Sometimes migrated objects that have been merged or mailbox-enabled in AD become
unrecognizable to a Notes' directory update, so the update mistakenly creates duplicate objects in AD. You
should Disable foreign directory sync if:
▪ You are using the CMN Directory Connector to perform directory updates from Notes to Exchange
during coexistence; and
▪ Your mail-routing method during coexistence is to use Notes forwarding addresses to set forwarding
from Notes to Exchange; and
▪ The Notes person documents are not set to turn users into Exchange objects.
Mail forwarding address options:
• Remove mail forwarding address: Select this check box if you want the wizard to remove previously set
mail-forwarding rules it may find in Notes, per the Only if... vs. Always option selected below:
▪ Only if domain matches “Forwarding mail domain”: Removes the previously set Forwarding
address (a Notes parameter) found in Notes only if the domain in the found address matches the
Forwarding mail domain specified in the accompanying text box. This would be a precaution to
prevent the inadvertent overwriting or removal of existing forwarding addresses that have nothing to
do with migration.
▪ Always: Removes the previously set Forwarding address (a Notes parameter) found in Notes,
regardless of Forwarding mail domain.

Select Notes User Visibility

This screen appears only if you selected Set User Visibility in Select Notes Administrative Operations. Specify
the preferred scope of user visibility in the Domino directory, enter the name of a Domino group that will hide
users, and click Next.
• None or System: Select one or the other to specify the preferred scope of user visibility in the Domino
directory.
• Group used to hide a user from the NAB: The name of a Domino group to which visibility will be limited.
(Users will be visible only to members of this group, typically created to consist of only one or a very few
administrator users.)

NOTE: Setting visibility to System here will not restore the visibility of a user who has been manually
hidden in Notes.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

100
Data Migration Wizard
Specify Active Directory Information
This screen does not appear if Office 365 without MS AD Sync is designated as the migration target. Also, this
screen appears only if the information it requests has not already been collected in Notes Migration Manager (in
the Active Directory Configuration screen), or if the Always Use option was not selected there.
These fields specify AD server access credentials, to authenticate the administrator by whose authority the
program will manipulate the contents of the AD:
• Global Catalog host name: Type the name of the AD Global Catalog server—for example, sitraka.com or
name.sitraka.com.

NOTE: If you have multiple Global Catalogs/Domain Controllers in an AD forest, you may choose any
GC in the setup as long as it is in the same domain.

IMPORTANT: If migrating to an Exchange on-premises server, you must enter fully qualified domain
names for the Global Catalog host name and Domain Controller host name.

• Domain Controller host name: Specify the PowerShell Domain Controller that Migrator for Notes to
Exchange will call to perform operations in Exchange.
• User name: The user name of the administrator by whose authority the program will access the Active
Directory.
• Password: The password associated with the user name.
Click Next.

How Were Accounts Loaded into Active

Directory
This screen appears only if you have designated your migration target as Exchange 2010 or later, or Hosted
Exchange (other than Office 365), and only if you have indicated earlier in this Wizard that you will create
mailboxes in Exchange, or set forwarding in Exchange or Notes, or remove forwarding from Exchange.
How users were loaded into Active Directory: Use the drop-down list to specify the method by which user data
was loaded into your local AD. Ordinarily user data is loaded into AD by Quest’s CMN Directory Connector (see
the Pre-Migration Preparations in chapter 2 of the Migrator for Notes to Exchange Scenarios Guide). If you are
following that typical scenario (using CMN), select Coexistence Manager for Notes/Other; find users by SMTP
address here.

Specify Exchange Mailbox Information

This screen appears only if you selected one of these Operations screen options:
• Mailbox-enable existing AD accounts
• Create Office 365 accounts
• Prepare local AD accounts for MS AD Sync

NOTE: The wizard will perform (or attempt) the mailbox-enabling functions by the authority of
whatever user is running the Notes Migration Manager— not necessarily the same as the user whose
AD credentials are entered into the Active Directory Configuration screen of Notes Migration
Manager.

Mail (these fields are disabled if migrating to Office 365):

• From the drop-down listes, select the locations of the Exchange mail Server and Exchange Mailbox
database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

101
Data Migration Wizard
 NOTE: The Mailbox store selected here can be overridden on a per-user basis by the contents of
the ExchangeMailboxStore column in the SQL database.

Personal Archives:
• Enable Exchange Personal Archive (available only when migrating to Exchange 2010 or later, or Office
365): Select this check box if you want the wizard to create a new Personal Archive mailbox in Exchange
for each user in the collection. This is required if you want to migrate any data to Personal Archives (as
specified in the Select Destinations for Migrated Data screen, earlier in this Wizard).
• Use alternate mail store for Personal Archives (disabled if migrating to Office 365): Select if you want to
specify a separate mail store for Exchange Personal Archives (separate from the active mailbox—e.g., to
distribute storage). If you select this option, you must also specify, from the drop-down lists, the locations of
the alternate mail server and alternate mailbox database.
Click Next.

Specify Notes Login Information

This screen appears only if the information it requests has not already been collected in the Notes Migration
Manager (in the Notes Server Configuration screen), or if the Always Use option was not selected there.
These fields specify Notes server access credentials, to authenticate the administrator by whose authority the
program will perform its administrative functions:
• Domino Server: Enter the name of the Domino server to be connected.
• User ID file: Click Browse to find and specify the path and filename of the User ID file, or type or paste the
path and filename into the text box.
• Password: Type the password associated with this User ID file.
Enter the requested information, and click Next.

Select Date and Size Filters

This screen appears only if you have selected Migrate users in the Operations screen. Select the desired date
and attachment size filters, and click Next.
• Mail dates: You may migrate all mail, or no mail, or use date-based filtering to migrate only mail items that
are time-stamped before or after a particular date, or within a range of dates.
• Calendar dates: You may migrate all calendar items, or no calendar items, or use date-based filtering to
migrate only calendar items time- stamped before or after a particular date, or within a range of dates.
• Attachment sizes: You may use size-based filtering to limit the size of attachments migrated, or migrate all
attachments regardless of size. Migrating only attachments smaller than a specified size will reduce the
amount of disk space needed to create the new .pst files or server database.

NOTE: Even if you filter attachments based on size, all messages are migrated. The filter excludes
only attachments that exceed the size limit; the messages to which oversized attachments were
attached are still migrated.
If Office 365 is selected as the Target Exchange System: The Attachment size defaults to 24.5
MB, which is the maximum message size allowed by Office 365. If the limit is set higher than Office
365 allows, the program reads and attempts to migrate larger attachments, but they will be
disallowed by Office 365 and logged as an error unless the migration has the [Exchange]
MigrateOversizedAttachments feature enabled in which the program attempts to upload large
attachments to the user OneDrive store.
For Office 365, you can configure MNE to migrate oversized attachments to the Microsoft OneDrive
store associated with the user mailbox. For details, see Exchange Server Configuration: Migrating to
Office 365 on page 20.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

102
Data Migration Wizard
Select Destination Exchange Server
This screen appears only if you have selected Migrate users in the Operations screen, and if the information it
requests has not already been collected in the Notes Migration Manager (in the Exchange Server Configuration
screen), or if the Always Use option was not selected there.
Enter the information that will authorize and characterize (or forgo) the program’s connection to the Exchange
server, and click Next.
NOTE: The Exchange account must be mailbox enabled or, if migrating to Office 365, have a license that
includes an Exchange mailbox.

• Do not connect to an Exchange server: This feature makes possible the migration of data to Outlook
personal folder (.pst) files prior to the setup of your Exchange server, but the check box will be available
only if none of your entries on earlier screens will require a connection to an Exchange server. (For
example, if you have told the program to create Exchange mailboxes, or to migrate any data to server-
based mailboxes, this check box will appear grayed-out and unavailable.) If you do forgo a connection to
an Exchange server, attendees’ free/busy information will be unavailable in migrated calendar
appointments.
• If you are migrating to Exchange 2013, 2016, or 2019:
Exchange Mailbox Server: Name of the Exchange server, which has the Mailbox role installed on it and
will be the connection used for all Exchange PowerShell activities in the product.
• If you are migrating to Exchange 2010:
Exchange CAS Server (displayed when migrating to Exchange 2010): Name of the client-access server (a
specific CAS server, not the array), if any.

NOTE: If migrating to a CAS, you must also set a throttling policy and WinRM, as described in
Appendix A (see How Do I Migrate to an Exchange Environment with a CAS Array?).

• If you are migrating to an on-premises Exchange server:

Administrator SMTP address: SMTP address of the administrator by whose authority the wizard will
perform its mail-related operations. The associated profile must have “Receive As” rights.
• If you are migrating to an on-premises Exchange server:
Administrator domain\user or UPN: The migration administrator login name to the Exchange mail server
(for the administrator account associated with the Administrator SMTP address). This field entry should
take the form domain\name or name@domain.sitraka.com.
• If you are migrating to Office 365:
Exchange Administrator: The migration administrator Office 365 account name. This field entry should
take the form name@domain.sitraka.com.
• Administrator password: The password associated with the migration administrator.
• Use admin account pool (check box, available only when migrating to Office 365): Select the check box if
you want to use the Migrator for Notes to Exchange Admin Account Pooling features (as described in
chapter 15 of the Administration Guide).
▪ Manage: Launches the Migrator for Notes to Exchange Admin Account Pool utility.
▪ Reset: Launches the Migrator for Notes to Exchange Admin Account Pool utility, deletes all admin
accounts from the pool, and exits.
Resolve attendees for [type] mail (two check boxes, available only for Office 365 target): Controls whether MNE
will look up SMTP addresses in user server mail and/or archives in the Exchange Global Address List (GAL) to get
Exchange addresses so free-busy lookups succeed. These options are disabled by default, but can be enabled by
selecting one or more of the check boxes. For example, you could select a check box to migrate data to PST files
without connecting to the Exchange server. Disabling the Resolve attendees function can increase migration
speed in some environments, but may cause lost free/busy information and may introduce other issues in Outlook.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

103
Data Migration Wizard
Personal Archive Location
This screen appears only if you have selected (in Select Destinations for Migrated Data) to migrate one or more
types of data to Outlook personal folders (.pst) files. Select the desired location and name for delivering any
Outlook personal folders (.pst) files generated during the migration, and click Next.

NOTE: When migrating to .pst files, a program parameter in the Global Defaults and Task
Parameters lets you specify whether the wizard should migrate all data into a single .pst file per user,
or to multiple .pst files. See in Appendix A, How Do I Specify Whether to Migrate to a Single PST File
(Per User) or Multiple PST Files? for information about this option.

The options to specify the .pst output file name and directory are listed below.
• Subdirectories of root directory specified below: Places .pst files in subdirectories under the .pst output
root directory designated in the accompanying text box. This option creates a directory structure that
matches the user's Notes folder hierarchy.
When this option is selected, you must also specify the file name format in the Generate the .pst filename
using field.
• Directory specified by the PSTDir column from database: Places new .pst files in the directory
specified for each user in the PSTdir column of the SQL database. The PSTdir column values must be in
the SQL database prior to this program run (see the Pre-Migration Preparations in chapter 2 of the Migrator
for Notes to Exchange Scenarios Guide).
▪ Generate the .pst filename as: When this check box is enabled, you can enter a file name string in
the text field. When the check box is disabled, you must specify the file name format in the
Generate the .pst filename using field.
▪ Generate the .pst filename using: You can select one of the following options for the .pst file name
format:
▫ Source Notes filename
▫ User display name
▫ User id
▫ SMTP email address
▫ Notes email address
In addition to specifying the location for new .pst files, you must also specify the file format (by Outlook version) for
which you want the files created:
• Use Outlook 97-2002 Personal Folders File (.pst): Tells the program to format .pst files in this format
(supports 2GB of data).
• Use Office Outlook Personal Folders File (.pst): Tells the program to format the .pst files in this format,
which supports up to 20GB of Unicode data. This option requires that Outlook 2010 be installed on the
migration machine, and will otherwise appear grayed-out as an unavailable option.
You can specify a language for personal archive folder names using the [General] LanguageCode parameter.
See the Programming Parameters Reference guide.

Specify Migration Run Information

Enter the requested information to control this program run and its log file, and click Next.
• Number of migration threads (simultaneous user migrations): The number of simultaneous processes
the program will use to perform migrations. The optimum number of threads depends on several factors
such as processor speed and bandwidth. Most administrators report optimum performance from settings of
8 to 12 concurrent processes. You may want to experiment with different values to determine the optimum
setting for your network configuration and processing capacity.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

104
Data Migration Wizard
Generating Task
No information is entered into this screen.
This screen reports the wizard's progress as it determines the details and associated work items of the task you
have prepared it to create. You will (in the next screen) have a chance to review the details and associated work
items, and decide whether to create the task, or go back and change any of the specifications that define the task.
When this generation process is complete, the wizard displays the next screen.

Migration Prioritization
This screen allows you to prioritize a specific user or users in the migration queue.
The screen shows the list of users currently in the migration queue. The Row count field displays the number of
users currently in the queue.
The table provides the user’s Display Name and SMTP Address. It also provides following information regarding
the migration data for each user:
• Data Store Estimate Item Count
• Data Store Estimate Item Size
For both fields, if you select Migrate mail data and Migrate archives on the Specify Data for Migration screen,
the estimates include both mail and archive data.
To change the priority of a user, select the user and click Move to change the user’s position in the list. Users at
the top of the list are migrated first. To select multiple users, press and hold the Shift key.
You can click on the column headers to reverse the order of the list. For example, click Data Store Estimate Item
Count to move users with the least amount of data to the top or bottom of the list.
Click Next to move to the next screen. If you opened this window from the Task Progress window, click Apply to
save your changes and close the window.

Configuration Summary
This screen shows a summary of the task configuration you have specified, as defined by the information entered
in previous screens.
Review this information to confirm that it describes the task you want to create. If you want to change anything,
click Back to return to earlier screens in this Wizard, to change values as necessary, or click Cancel to cancel this
wizard and return to the Migrate User Data screen in Notes Migration Manager. From earlier screens within this
wizard, you can click Next to return to this Configuration Summary screen.
• Next: Creates the task as defined in the configuration summary and immediately runs the task. When you
click Run, the wizard displays a screen that reports progress as the task is created and displays a screen
that reports progress as the task runs. When the task run is complete, the wizard displays a screen that
reports the statistical results of the task.

Creating Task
No information is entered into this screen, which reports the wizard's progress as it creates the task defined on the
preceding Configuration Summary screen.
When the task-creation process is complete, the wizard clears this screen and runs the newly created task.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

105
Data Migration Wizard
Specify Task Schedule
This screen lets you schedule the task you have created.

NOTE: The Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, explained in chapter 13 of the Migrator for
Notes to Exchange Administration Guide. The Task Scheduler checks the SQL database to see whether any
tasks are scheduled to run since the last check, and runs any tasks it finds.

The drop-down list at the top of the screen offers these scheduling options:
• Now on this computer: The wizard runs the task when you click Next. The other scheduling controls on
the screen appear grayed out (unavailable), since they do not apply. Click Next to display the Task
Progress screen.
• One or more times, as indicated below: The task runs one or more times, according to your entries in the
scheduling controls. If you select this option you must specify where and when you want the task to run in
the scheduling controls.
• Manually: The task will not run or be scheduled. The other scheduling controls on the screen appear
grayed out (unavailable), since they do not apply. Click Next to display the Schedule Summary screen.
• Once: The task will run only once and will not repeat. You can specify where to run and the start date and
time. Click Next to display the Schedule Summary screen.
These scheduling controls are enabled only if One or more times... is selected in the drop-down list:
• Where to run: Select either On any computer or On a specific computer. If you choose a specific
computer, you must also specify the machine name in the text box.
• When to run:
▪ Start: Specify the calendar date for the first (or only) task run.
▪ Days of the Week: Specify one or more days of the week that you want the task to run. If you select
two or more days, the first task run will occur on the first selected day occurring on or after the
specified Start date.
▪ Between [____] and [____]: Specify the beginning and ending times of a range of start times for
the task to run.
▪ Select one of these options for the end date:
▫ No end date: The task runs will adhere to this schedule until someone manually ends the
series by editing this schedule definition in Notes Migration Manager (in the Manage
Scheduled Operations screen).
▫ End after __ occurrences: The task runs will adhere to this schedule until the cumulative
number of runs matches the number specified here.
▫ End by: The task runs will adhere to this schedule until the calendar date specified here
▪ [_] Start this task only after completing: [________________________]: Select this check box if
you want this new task to run only after some other previously defined Migrator for Notes to
Exchange task has run. If you select the check box, use the drop-down list to specify which
previously defined Migrator for Notes to Exchange task must precede this one.
When you have set the task schedule in these scheduling controls, click Next to display the Schedule Summary
screen.

Schedule Summary
This screen appears only if you have selected One or more times... Once or Manually as your scheduling option
on the preceding Specify Task Schedule screen. The screen shows a summary of the task schedule you specified
in the Specify Task Schedule screen, or notes that the task will be run only Manually.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

106
Data Migration Wizard
Review this information to confirm that it describes the schedule you want to define. If you want to change
anything, click Back to return to the Specify Task Schedule screen, to change the schedule specification, or click
Cancel to cancel this Wizard and return to the Export Notes Directory screen in Notes Migration Manager. From
the preceding screen within this Wizard, you may click Next to return to this Schedule Summary screen.
When you are satisfied that the displayed summary describes the task schedule you want to create, click Finish to
dismiss this screen:
• Finish: Clears this Schedule Summary screen, to return to the Export Notes Directory screen in Notes
Migration Manager.
The remaining screens documented for this Wizard are skipped if you have selected One or more times... or
Manually as your scheduling option on the preceding Specify Task Schedule screen.

Task Progress
No information is entered into this screen. The screen reports the program's progress as it performs the defined
task. You can click Cancel to cancel the task before it completes.
You can click User Status to open the User Migration Status window. This window displays detailed per-user
migration status in real time during the migration. In the User Migration Status window, click Export to TSV to
create a local tsv file containing the data. Click View Error Log to open the Log Viewer.
You can click Prioritization to open the Migration Prioritization window and prioritize a specific user or users in the
migration queue. See Migration Prioritization.
When the process is complete, the program displays its Task Completed screen to report the results.

Task Completed
No information is entered into this screen. The screen reports the results of the task run.
Click User Status to open the User Migration Status window. This window displays detailed per-user migration
data. In the User Migration Status window, click Export to TSV to create a local tsv file containing the data.
NOTE: Notes stores RTF message bodies in compressed form, but in this screen, MNE reports the volume
of migrated data as uncompressed bytes, and the data is also stored uncompressed in Exchange mailboxes.
The migrated data volume that is reported here, and the corresponding mailbox sizes in Exchange, are likely
to be somewhat larger than the data volume reported in the Notes source in which RTF message bodies are
compressed.
• if the program encountered errors during its run, the Task Completed screen displays an Error Log Report
button. Click the button to view the program log and assess the severity of the errors. The Error Log
Report button launches the MNE Log Viewer utility to help you interpret and resolve the errors. For more
information see “The Log Viewer” chapter in this guide.
• If a migration included Notes messages that were scheduled to be delivered on a future date, MNE
generates a deferred email report file (DeferredEmails.tsv) in the shared log folder and the Task Completed
screen displays a Deferred Email Report button. Click the button to view the DeferredEmails.tsv log file.
For more information see the “Migrating delayed delivery mail” chapter in the Pre-Migration Planning
Guide.
When you are finished, click Exit to exit the wizard.

Remember to Distribute Any New .pst Files

If the Data Migration Wizard has migrated any data to Outlook Personal Folder (.pst) files, when the migration is
complete you must either:
• Notify users of the locations of their new .pst files (so each user can specify the location within his or her
own desktop copy of Outlook) — OR —
• Distribute the newly created .pst files to users’ desktops.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

107
Data Migration Wizard
The Data Migration Wizard names any new .pst files using the common filename, if specified, or the specified
filename format. if more than one file is generated per User ID, incremental numbers are appended to the
filename. For example, Smith.pst, Smith-1.pst, Smith-2.pst, etc.

Post-Migration Report and Assessment

The Data Migration Wizard generates a post-migration TSV report that lists users migrated, together with per-user
numbers and data volumes of items migrated, and counts of process errors and/or warnings, and a short verbal
assessment of whether these statistics might warrant a closer look at particular mailboxes. The verbal
assessments (OK, some warnings, and Errors, please investigate, etc.) are arbitrary, based on the numbers and
rates of errors and warnings in a given mailbox, but can help draw attention to particular mailboxes. The wizard
saves its post-migration report in a TSV file, in the shared log folder. Each report is named to match exactly the
associated log for the same Wizard run, but with a .tsv extension instead of .wlog.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

108
Data Migration Wizard
 11
SSDM Statistics Collection Wizard
• Introduction
• Wizard process screens

Introduction
The SSDM Statistics Collection Wizard defines a task that will gather migration statistics written by the Self-
Service Desktop Migrator (SSDM, and loads the data to the SQL database, so you can track the progress of a
migration project.

NOTE: The SSDM Statistics Collection Wizard can collect user statistics only if the Post user logs to the
central directory check box has been selected in the Shared Directories Configuration screen in Notes
Migration Manager. If that check box has been left cleared, the per-desktop migration program will have
written its log files to individual users' local temp directories, where they will be unavailable to the wizard.

Each time a user runs the Self-Service Desktop Migrator, the program writes its run statistics to the Directory for
central log and status files, specified in the Shared Directories Configuration screen of Notes Migration
Manager. This Wizard gathers those statistics and adds them to the SQL database, so they will appear in the
Project View screen of Notes Migration Manager.

NOTE: Statistics reported by Migrator for Notes to Exchange are based on uncompressed data sizes
provided by the Notes APIs. The APIs extract data in compressed form and provide the data to Migrator for
Notes to Exchange in an uncompressed state. Data volumes reported by Migrator for Notes to Exchange are
often higher than the values observed natively in Notes or transferred over the network to the migration
servers.

Field definitions and application notes for the wizard’s screens appear in the sections that follow.

Wizard process screens

The following sections describe the screens that may be displayed and the configuration settings for each screen.

Customize Configuration
This screen, which lets you edit the Task Parameters for this task, appears only if the Advanced Settings option is
selected on the View menu in Notes Migration Manager. To enable or disable this capability to edit Task
Parameters:
• In Notes Migration Manager, on the View menu, select (enable) or clear (disable) the Advanced Settings
option.
The Advanced Settings option is a toggle that determines whether the wizards will let you open and edit Task
Parameters. If the feature is enabled, the Customize Configuration screen is displayed at the start of the screen
sequence for any Wizard that offers this feature.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

109
SSDM Statistics Collection Wizard
Task Parameters are edited as if the parameters were stored in an INI file, although the parameters are stored as
part of the task definition within the SQL database. The Customize Configuration feature copies the current
parameter settings from the SQL database into a text document in Windows Notepad so you can use the Notepad
text-editing features to change parameter values or add new parameter specifications.

To add or edit Task Parameters:

1 Click Edit.
The wizard opens the task's configuration settings in Notepad.
2 Find the pertinent [SectionName] for the parameter you want to add, or whose value you want to edit.

NOTE: Some parameters in different sections share the same keyname, so it is very important that
parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager copies the new parameter values back into the SQL database.

Generating Task
No information is entered into this screen.
This screen reports the wizard's progress as it determines the details and associated work items of the task you
have prepared.You can review (in the next screen) the details and associated work items, and decide whether to
create the task, or go back and change any specifications that define the task.
When the process is complete, the wizard displays the next screen.

Configuration Summary
This screen shows a summary of the task configuration you have specified. The Configuration Summary for this
wizard shows only the directory that contains the statistics files written by the Self-Service Desktop Migrator. The
source directory was specified in the Notes Migration Manager, in the Gather Desktop Statistics screen from which
this wizard was launched.
Review this information to confirm that it describes the task you want to create. If you want to change anything,
click Back to return to earlier screens to change values as necessary, or click Cancel to cancel this wizard and
return to the Gather Desktop Statistics screen in Notes Migration Manager. From earlier screens, you may click
Next to return to this Configuration Summary screen.
• Save As: Lets you save this summary information to a text file. Follow the prompts to specify a path and
filename for the text file.
• Print: Lets you print a paper copy of this summary information. Follow the prompts to specify the
destination printer.
• Run: Creates the task as defined in the configuration summary and runs the task. When you click Run, the
wizard displays a screen that reports its progress as it creates the task, and displays a screen that reports
its progress as the task runs. When the task run is complete, the wizard displays a screen that reports the
statistical results of the task.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

110
SSDM Statistics Collection Wizard
Creating Task
No information is entered into this screen. This screen reports the wizard's progress as it creates the task defined
on the Configuration Summary screen. When the task-creation process is complete, the wizard clears this screen
and runs the newly created task.

Specify Task Schedule

This screen lets you schedule the task you have created.

NOTE: The Manage Scheduled Operations screen manages the scheduling of task runs as saved in the
SQL database. Scheduled tasks are run by the Task Scheduler, explained in chapter 13 of the Migrator for
Notes to Exchange Administration Guide. The Task Scheduler checks the SQL database to see whether any
tasks have been scheduled to run since the last check, and runs any tasks it finds. See chapter 13 for details
on the Task Scheduler.

The drop-down list at the top of the screen offers these scheduling options:
• Now on this computer: Runs the task when you click Next. The other scheduling controls on the screen
appear grayed out (unavailable), since they do not apply. Click Next to display the Task Progress screen.
• One or more times, as indicated below: The task runs one or more times, according to your entries in the
scheduling controls. If you select this option you must specify where and when you want the task to run in
the scheduling controls.
• Manually: The task will not run or be scheduled. The other scheduling controls on the screen appear
grayed out (unavailable), since they do not apply. Click Next to display the Schedule Summary screen.
• Once: The task runs only once and will not repeat. You can specify where to run and the start date and
time. Click Next o display the Schedule Summary screen.
These scheduling controls are enabled only if One or more times... is selected in the drop-down list:
• Where to run: Select either On any computer or On a specific computer. If you choose a specific
computer, you must also specify the machine name in the adjacent text box.
• When to run:
▪ Start: Specify the calendar date for the first (or only) task run.
▪ Days of the Week: Specify one or more days of the week that you want the task to run. If you select
two or more days, the first task run will occur on the first selected day occurring on or after the
specified Start date.
▪ Between ____ and ____: Specify the beginning and ending times of a range of start times for the
task to run.
▪ Select one of these options for the end date:
▫ No end date: The task runs will adhere to this schedule until someone manually ends the
series by editing this schedule definition in Notes Migration Manager (in the Manage
Scheduled Operations screen).
▫ End after __ occurrences: The task runs will adhere to this schedule until the cumulative
number of runs matches the number specified here.
▫ End by: The task runs will adhere to this schedule until the calendar date specified here.
▪ [_] Start this task only after completing: [________________________]: Select this check box if
you want the new task to run only after some other previously defined task has run. If you select the
check box, use the drop-down list to specify which previously defined task must precede this one.
When you have set the task schedule in these scheduling controls, click Next to display the Schedule
Summary screen.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

111
SSDM Statistics Collection Wizard
Schedule Summary
This screen appears only if you have selected One or more times... Once or Manually as your scheduling option
on the preceding Specify Task Schedule screen. The screen shows a summary of the task schedule you specified
in the Specify Task Schedule screen, or notes that the task will be run only Manually.
Review this information to confirm that it describes the schedule you want to define. If you want to change
anything, click Back to return to the Specify Task Schedule screen, to change the schedule specification, or click
Cancel to end this Wizard and return to the Export Notes Directory screen in Notes Migration Manager. From the
preceding screen within this Wizard, you may click Next to return to this Schedule Summary screen.
When you are satisfied that the displayed summary describes the task schedule you want to create, click Finish to
dismiss this screen:
• Finish: Clears this Schedule Summary screen, to return to the Export Notes Directory screen in Notes
Migration Manager.
The remaining screens documented for this Wizard are skipped if you have selected One or more times... or
Manually as your scheduling option on the preceding Specify Task Schedule screen.

Task Progress
No information is entered into this screen. The screen reports the program's progress as it performs the defined
task. You can click Cancel to cancel the task before it completes.
When the process is complete, the program displays the Task Completed screen to report the results.

Task Completed
No information is entered into this screen. The screen reports the results of the task run.
if the program encountered errors during its run, the Task Completed screen displays an Error Log Report button.
Click the button to view the program log and assess the severity of the errors. The Error Log Report button
launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and resolve the errors.
When you are finished, click Exit to exit the wizard.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

112
SSDM Statistics Collection Wizard
 12
The Log Viewer
The Log Viewer utility simplifies the viewing and interpreting of program log files that document alerts and
warnings in Quest application programs. The same Log Viewer utility is used for several Quest products, including
Migrator for Notes to Exchange.

IMPORTANT: The full benefit of the Log Viewer requires that the application to transmit log event codes from
the computer hosting the Log Viewer to a remote Quest database of Solutions (useful information about the
events associated with the log codes). The Quest Solutions database sends a corresponding Solution back
to the Log Viewer for display to the user.
This feature is enabled by default, but can be disabled by clearing the Enable Internet Access option on the
View menu. For more information, see the IMPORTANT disclosures in the View menu topic that follows, in
the field notes for the Enable Internet Access option.

These Log Viewer topics document Log Viewer menus and toolbar and How to ... (accomplish various tasks).

Log Viewer menus and toolbar

Most Log Viewer features are accessible by the program’s menus and/or the program tool bar, which share a
horizontal band across the top of the screen:

Several features are also available directly from the keyboard, and those keyboard shortcuts are displayed in the
menus and noted here.
The Log Viewer menus are: File menu • Edit menu • View menu • Help menu

File menu
• Open Log File... (or Ctrl+O): Opens a standard Windows Open dialog box from which you can specify the
file you want to open in the Log Viewer. The Log Viewer can open and display WLog (optionally
compressed) files and plain text files.

NOTE: Drag-and-Drop Option: You can also open a wlog file in the Log Viewer by dragging and
dropping a filename from Windows Explorer into the Log Viewer window.

• Save Copy Of Log File As... (appears when a file is open): Opens a standard Windows Save As dialog
box, from which you can specify the filename and location where you want the file to be saved. The Log
Viewer lets you edit the contents of an open file, but does not replace the original on disk with the edited
version (you cannot save it under the same name in the same location).
• Recent Files: Shows a list of recently opened files from which you can select a file to re-open (to quickly
re-open a file you have recently viewed and closed).

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

113
The Log Viewer
 • Exit: Closes the Log Viewer window.

Edit menu
• Copy (or Ctrl+C): Copies the selected line to the Windows clipboard.
• Find... (or Ctrl+F): Opens a Find dialog box that lets you specify a text string to search for within the open
file:

The dialog box lets you search for the next or preceding occurrence, or for the first or last occurrence in the
file. The Find feature highlights the entire line that contains the target string.
• Go To Line Number: Opens a dialog box that lets you jump to a particular line number of the file. (Enter
the line number and click OK.)

View menu
• Show Line Numbers (or Ctrl+L): Toggles the display of line numbers (within the open file) on and off.
• Show Complete Log Entry (or F5): Opens a Log Detail window that shows the entire string for the
selected item—useful when the item text overruns the Log Viewer’s maximum line length (maximum 259
characters), or if the line extends beyond the right edge of the viewer window without wrapping.
• Enable Internet Access: Toggles the Internet connection on and off. Note these important disclosures:

IMPORTANT: The Quest Log Viewer requires that the application transmit log event codes from the
computer hosting the Log Viewer to a remote Quest database of Solutions (useful information about
the events associated with the log codes). The Quest Solutions database sends a corresponding
Solution back to the Log Viewer for display to the user.
This feature is enabled by default, but you can disable it by clearing the Enable Internet Access
option on the View menu. Note:
• The Log Viewer sends event codes to Quest servers in the United States, as the codes
appear in a log file that has been opened into the Log Viewer window.
• The Log Viewer sends only event codes and source IP addresses to Quest's server. No
personally identifying information other than IP addresses is collected or sent.
• Quest's transmission of Solutions corresponding to received event codes is fully automated
(no human intervention or observation). Quest tallies the frequencies of event codes received
and Solutions sent in reply, but does not associate those tallies with IP addresses or any other
personally identifying information, and no other information is logged.
• Quest servers treat each received event code as a query. Quest uses an event code only to
determine which Solution to send back to the source of the query, and uses an IP address
only to transmit the Solution to the source of the query. Quest servers log querying IP
addresses as a matter of course, but Quest does not use them for any other purpose and
does not disclose them to any other entity.
• You may opt out of this feature, to prevent the transmission of event codes and IP addresses
to Quest, by clearing the Enable Internet Access option on the View menu.

• Goto Line Number: Prompts for a line number in the file to display.

Help menu
• Online Help... (or F1): Opens Quest’s online Help file for the Log Viewer, which documents its features.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

114
The Log Viewer
 • About...: Opens a window of information about the Log Viewer—identifying the current release, and
asserting Quest’s intellectual property rights to the software.

How to ...
This section describes how to accomplish various tasks in the Log Viewer.

To open a specific log

• Drag and drop a wlog file name from Windows Explorer into the Log Viewer window.
— OR —
Click the Open Log File button (in the Toolbar) to view a list of log files that can be opened. In the File
section of the screen, select a log file and click OK to open the log in the Quest Log File Viewer.

To find a particular text string within an open file

• Edit | Find... (or Ctrl+F): Opens a Find dialog box that lets you specify a text string to search for within the
open file. The Find feature highlights the entire line that contains the target string.

To re-open a recently viewed file

• File | Recent Files: Shows a list of recently opened files, from which you can select a file to re-open (to
quickly re-open a file you have recently viewed and closed).

To save a copy of a file

• File | Save Copy Of Log File As... (appears when a file is open): Opens a standard Windows Save As
dialog box, from which you can specify the filename and location where you want the open file to be saved.
(This feature does not permit any revisions to the open file. It lets you save the file in its original form to a
new filename and/or a new location.)

To show or hide line numbers

• View | Show Line Numbers (or Ctrl+L): Toggles the display of line numbers (within the open file) on and
off.

To jump to a particular line number in the file

• Edit | Go To Line Number: Opens a dialog box that lets you specify the destination line number. (Enter the
number and click OK.)

To view an entire log entry

• View | Show Complete Log Entry (or F5): Opens a Log Detail window that shows the entire string for the
selected item—useful when the item text overruns the Log Viewer’s maximum line length (maximum 259
characters), or if the line extends beyond the right edge of the viewer window without wrapping.

To turn internet access on or off

• View | Enable Internet Access: Toggles the Internet connection on and off.

To copy a selected line to the clipboard

• Edit | Copy (or Ctrl+C): Copies the selected line to the Windows clipboard.

To close the log viewer

• File | Exit: Closes the Log Viewer window, or click the Log Viewer Close box ([X]) to dismiss the window
and return to the previous display.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

115
The Log Viewer
 13
Using the Qsched.exe task-
scheduling utility
The Migrator for Notes to Exchange (MNE) wizards are used to define the tasks that run migrations. Many wizards
let you schedule tasks to run at certain times on certain days. Using the Manage Scheduled Operations screen in
the Notes Migration Manager, you can revise the task-run schedules. However, the wizards and Manage
Scheduled Operations screen only manage the scheduling of task runs and these schedules are saved in the SQL
database.
The scheduled tasks are run by a low-level Migrator for Notes to Exchange Task Scheduler utility called
qsched.exe which is located in the MNE installation directory. This utility is controlled by the MNE Task Schedule
service.
The name of the task scheduler service is “Quest Migrator for Notes to Exchange Task Scheduler” and it is
installed when you install MNE. By default, the task scheduler service is configured to be in the disabled state. The
service is installed to run as Local System.
You can manage the task scheduler service as you would any other Windows service using the Windows Service
Manager. Instructions for configuring a Windows service can be found at: http://msdn.microsoft.com/en-
us/library/ms681921(v=vs.85).aspx.

TIP: If the Migrator for Notes to Exchange Task Scheduler experiences logon failures when trying to start the
service, see How do I troubleshoot service startup permissions? in the How Do I ...? Appendix of the
Migrator for Notes to Exchange Administration Guide.

When used, the task scheduler service polls the Migrator for Notes to Exchange database at regular intervals for
any scheduled tasks and invokes the qsched.exe utility to run those tasks at the designated times.

Post-installation configuration
After installing MNE, there are additional configuration steps required to use the Migrator for Notes to Exchange
Task Scheduler utility. Open the Windows Service Manager and complete the following steps:
1 Ensure the task scheduler service is configured to run on behalf of an account that has the necessary
permissions to access all MNE resources. It is recommended that you use the same account that is used to
run the MNE console. The display name of the task scheduler service is “Quest Migrator for Notes to
Exchange Task Scheduler”.
2 Configure the Quest Migrator for Notes to Exchange Task Scheduler service for autostart mode.
a If the MNE database is located on a local SQL instance, configure the service to start in the
Autostart (Delayed Start) mode.
b If the MNE database is located on a remote SQL instance, configure the service to start in the
Autostart mode.
3 Start the task scheduler service.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

116
Using the Qsched.exe task-scheduling utility
Log files
The Migrator for Notes to Exchange Task Scheduler logs to a file named SchedulerService.wlog that is located in
the installation directory.
You can change the location of the SchedulerService.wlog by completing the following steps.

To change the log file location

1 Stop the Migrator for Notes to Exchange Task Scheduler service.
2 Open the SchedulerService.exe.config file in the Migrator for Notes to Exchange installation directory.
3 Find the following line: <file value=".\SchedulerService.wlog" />
4 Replace the value in double quotes with a full path to the desired location.
5 Save the file.
6 Start the Scheduler Service.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

117
Using the Qsched.exe task-scheduling utility
 14
SSDM Scheduling Administration
utility
• About SSDM Scheduling Administration
• Before you can use the SSDM Scheduling Administration utility
• Scheduling and limiting concurrent runs
• Monitoring SSDM usage status

About SSDM Scheduling

Administration
The SSDM Scheduling Administration utility lets you control when users can run the SSDM (Self-Service Desktop
Migrator) to more evenly distribute the demand on network and server resources. Each user collection is assigned
a specific date and time period when its member users are permitted to migrate. When a user runs the SSDM, the
program identifies the user by his or her login credentials and checks the schedule to see whether the user is
early, late, or “in the window” for his or her migration.
The SSDM Scheduling Administration utility also lets you set per-collection limits on the number of concurrent
migration runs to prevent processing bottlenecks that can occur if too many users run the SSDM at the same time.
If a user’s SSDM run exceeds the limit, the user has the option of “parking” the run in a waiting queue so that his or
her migration would run in the next available slot.

Before you can use the SSDM

Scheduling Administration utility
To use these features, you must install and configure Microsoft Internet Information Services (IIS) and the SSDM
Scheduling Administration web service. This procedure differs depending on whether you install IIS version 6 or
IIS version 7 and higher.

To install and configure IIS version 7 or later and the SSDM

Scheduling Administration Web Service
To install IIS 7 manually, see Microsoft’s instructions at:
http://learn.iis.net/page.aspx/28/installing-iis-7-on-windows-vista-and-windows-7/

To install IIS 7 using the Microsoft Web Platform Installer.

1 Download and run the Microsoft Web Platform Installer (Web PI) from Microsoft:
http://www.microsoft.com/web/downloads/platform.aspx

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

118
SSDM Scheduling Administration utility
 2 Click I Accept to accept the license terms of the associated third-party and Microsoft software.
3 On the Web Platform tab, select the Web Server option Click to include the recommended products,
and click Install.
4 When the installation completes, click Finish and click Exit.

To configure IIS 7 for the SSDM Scheduling Administration web service:

1 Create a new virtual directory:
2 In the IIS Manager window, right-click on Default Web Site and select Add Virtual Directory from the
menu.
3 On the Add Virtual Directory screen, complete the fields and click OK.
▪ Alias: Enter SSDMSchedulingWebService.
▪ Physical path: Browse ([...]) to locate the SSDMSchedulingWebService path (typically C:\Program
Files (x86)\Quest\Migrator for Notes to Exchange\SSDM Scheduling Web Service\).
4 Convert the new virtual directory to an application: Right-click on SSDMSchedulingWebService, and
select Convert to Application from the pop-up menu.
5 Change the DefaultAppPool's Identity to a user with access to SQL:
6 Right-click on DefaultAppPool, and select Advanced Settings from the menu.
7 In the Advanced Settings window: In the Identity field, browse ([...]) to specify a user who has SQL access.
8 Click OK.

To install and configure IIS 6 and the SSDM Scheduling

Administration Web Service
1 Install Microsoft Internet Information Services (IIS) using Windows’ Control Panel: Add/Remove
Programs | Add/Remove Windows Components.
IIS is a part of your Windows operating system (any supported version).
2 Run Administrative tools | Internet Information Services.
3 Right-click the Default Web Site, and select New | Virtual Directory.
4 Set the Alias to “SSDMSchedulingWebService”
5 For the Directory, browse to: C:\Program Files (x86)\Quest\Migrator for Notes to Exchange\SSDM
Scheduling Web Service\.
6 On the Access Permissions screen, select the check boxes to allow only Read and Run scripts.
7 Right-click the new SSDMSchedulingWebService virtual directory and select Properties.
8 In the SSDMSchedulingWebService Properties, select the ASP.NET tab, and click Edit Configuration
near the bottom of the panel.
9 In the ASP.net Configuration Settings, select the Application tab and, under Identity settings:
a Verify that the Local impersonation check box is selected.
b Enter a User name (must be in the form domain\username) and password to be used to connect to
the database.
c Click OK to save your ASP.net Configuration Settings.
10 In the SSDMSchedulingWebService Properties window, click OK.
11 In IIS Manager, under Web Service Extensions, set all three items to Allow: Active Server Pages,
ASP.NET v 1.1, ASP.NET v 2.0.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

119
SSDM Scheduling Administration utility
 12 To verify that everything is configured correctly, go to:
http://localhost/ssdmschedulingwebservice/SSDMSchedulingWebService.asmx

Scheduling and limiting concurrent

runs
To schedule user SSDM runs and set limits on concurrent runs
1 From your Windows Start menu: Select All Programs | Quest | Migrator for Notes to Exchange | SSDM
Scheduling Administration.
The SSDM Scheduling Administration Utility appears, with four tabs: Collection Settings, Global
Settings, Custom Notifications, and Monitor. The utility opens to the Collection Settings panel.
2 On the File menu, select the Configuration option to open the Configuration dialog box.
3 In the Configuration dialog box, set or change the following value:
▪ Web Service Location: The URL of the web service.
Click Save to register the value, clear the dialog and return to the Collection Settings panel.
4 Click the Global Settings tab to show the Global Settings panel. The settings in this panel apply to all
SSDM migration runs, regardless of user collection.
5 In the Global Settings panel:
a Select or clear the following check boxes as appropriate:
▫ Enable SSDM Scheduling: Determines whether the SSDM Scheduling features, as defined
on the Collection Settings panel, will be used at all. If this check box is cleared, the SSDM
will run with no scheduling restrictions and no limits on number of concurrent users.
▫ Schedule Reminder: In the event a user tries to use the SSDM prior to his/her scheduled
migration window, this check box determines whether the SSDM will schedule a task to
restart for the user when it is permitted to run.

IMPORTANT: Since a non-privileged user cannot create a reminder task (by Windows
policy) and would not be alerted if the task could not be scheduled, an administrator
should not allow this scheduled-reminder option for users that lack that privilege.

▫ Email Migration Team: Determines whether the SSDM will be enabled to notify the
migration administrator in the event the program cannot run due to scheduling restrictions.
The Auto Send Email field determines whether the notification is generated, or if an option
posed to the SSDM user. If Email Migration Team is cleared, the program does not auto-
matically send an email or offer the option to users.

IMPORTANT: If this feature is disabled, the Report This Issue button will not appear
to the user, so the message defined in the Custom Notifications panel should not
mention the button.

▫ Auto Send Email (valid only if Email Migration Team is selected): Determines whether the
SSDM notifies the migration administrator in the event the program cannot run due to
scheduling restrictions. If this box is selected and the SSDM is unable to run, the program
generates notification emails to the migration administrator defined in the Migration Team
Email Information fields. If this box is cleared and the SSDM is unable to run, the error
screen presented to the user includes a button that lets the user choose whether to send a
notification to the migration team.
b Set values for the update and timeout fields:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

120
SSDM Scheduling Administration utility
 ▫ Update progress after ____ minutes: Defines the interval at which the program will update
the system’s migration statistics while the SSDM is running.
▫ Session timeout after ____ minutes: The number of minutes of program inactivity after
which the SSDM would timeout.
c Specify your choices for the User Connection Settings, to (optionally) limit SSDM connection-retry
attempts. Choose either:
▫ Allow unlimited retry attempts within date/time window.
— OR —
▫ Limit retry attempts within date/time window.
If you choose to Limit retry attempts, you must also specify values for the number of SSDM
retry migration attempts, and the interval (in number of minutes) between retries (SSDM
retry migration request after).
d Set values for the Migration Team Email Information. These fields define the recipients and
contents of the notification email the program can send if a user cannot run the SSDM due to
scheduling restrictions or concurrency limits:
▫ Email Addresses: Defines the recipients of the notification email. To add an address to the
list, type an email address in the text box and click the Add button. To remove an address
from the list, select the address and click Delete Selected.
▫ Subject: The Subject line of the notification email.
▫ Message: The body of the notification email.
e When all the Global Settings field values are set as you want them, click Save to save the settings.
6 Click Custom Notifications to show that panel, and make any changes you care to make to the messages
that will be presented to users in these different circumstances:
▪ Not Scheduled Notification: The message that will be presented to the user if his/her User ID is
not a part of any user collection that is scheduled for migration.
▪ Before Migration Window Notification: The message that is presented if you try to run the SSDM
before the earliest date and time set for your collection’s migration window.

IMPORTANT: The default text entries for the “Before” and “After” conditions noted here and
below make no mention of the Schedule Reminder button—an option that may or may not be
offered depending on your setting for Schedule Reminder in the Global Settings panel (step
5a). If the Schedule Reminder option is enabled, you should add brief explanations of the
button to the messages here.

▪ After Migration Window Notification: The message that is shown if the user tries to run the
SSDM after the latest date and time set for his/her collection’s migration window.
▪ Before Migration Time Window Notification: The message that is shown if the user tries to run
the SSDM within the migration window date range, but before the permitted time-of-day range. Also
see the IMPORTANT note above.
▪ After Migration Time Window Notification: The message that is shown if the user tries to run the
SSDM within the migration window date range, but after the permitted time-of-day range. Also see
the IMPORTANT note above.
▪ Too Many Connections Notification: The message that is shown if the number of other users
running the SSDM at the same time has reached the concurrency limit set for the collection.
When all the Custom Notifications field values are set as you want them, click Save to save the settings.
7 Click the Collection Settings tab to show that panel, and:
a Select a collection from the list of Collections on the left. The fields in the right half of the screen will
set the schedule “window” and concurrent usage limit for all users in the selected collection.

NOTE: To define a new collection while in this Collection Settings panel, click the Add/Edit
Collection button (below the Collections list, on the left) to launch the Collection Wizard.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

121
SSDM Scheduling Administration utility
 b Set the Migration Time Window values for the selected collection in the right half of the panel: the
From (beginning) and To (ending) dates and times.
c Optional: If you want to allow SSDM runs only within a certain time period (per day), recurring daily
throughout the From—To period defined in the preceding step:
▫ Select the check box for Only allow migrations between, and enter the beginning and
ending times of the daily range in the accompanying "________ and ________" time fields.
d Set the Number of concurrent users allowed value for this collection in the right half of the
screen. Any integer greater than zero will limit concurrent runs of the SSDM to the specified value.
A zero (0) sets the limit to “unlimited” (any number of concurrent users will be allowed).
e When the values in the right half of the screen define the migration window and concurrency limit
you want for the selected collection, click the Save button.
f Repeat steps 7a through 7e as often as you like to define the migration windows and concurrency
limits for other collections. Remember to click the Save button after setting values for each
collection, or the settings will be lost when you select a different collection or Exit the SSDM
Scheduling Administration Utility.
8 When all three tabs’ field values are set as you want them, click Exit to close the SSDM Scheduling
Administration Utility.
9 Add the following parameters to the notesdtapp.ini file:
[SSDMThrottle]
UseThrottle=1
WebServiceUrl=<UrlToWebsite>
For example:
http://xyzcorp.com/ssdmschedulingwebservice/SSDMSchedulingWebService.asmx

Monitoring SSDM usage status

The SSDM Scheduling Administration Utility includes a Monitor panel that lets you monitor the current status of
SSDM usage, by numbers of users:
• Processing: Number of users currently running the SSDM.
• Waiting: Number of users waiting for an opening to start running the SSDM.
• Timed Out Waiting: Number of users whose SSDM was waiting for so long that it timed out.
• Cancelled Waiting: Number of users who were waiting for an opening to start processing, but clicked
Cancel on the SSDM to stop waiting.
To monitor SSDM usage status: Click the Monitor tab in the SSDM Scheduling Administration Utility. To leave the
Monitor panel: Click a different tab in the Utility, or click Exit to close the SSDM Scheduling Administration Utility
altogether.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

122
SSDM Scheduling Administration utility
 15
Office 365 Admin Account Pool
utility
• About the Admin Account Pool utility
• Necessary preparations for the Admin Account Pooling utility
• Managing the Admin Account Pool

About the Admin Account Pool utility

Microsoft currently imposes various throttles in Office 365 to ensure service availability and performance for all
tenants. Some of these throttles take effect when any account (including a migration administrator account)
initiates more than two concurrent connections. Each migration thread counts as a connection, so throttling can
have a dramatic impact on migration performance to Office 365.
Migration solutions commonly achieve optimal throughput with eight to 12 threads for migration to local targets,
and potentially more threads for higher-end hardware. To achieve similar results to Office 365, separate migration
administrator accounts must be used to bypass the throttling limitations.

NOTE: When running Migrator for Notes to Exchange in a federated Office 365 environment, the Account
Pool Utility cannot use a federated domain.

Since Microsoft’s throttling is applied per administrator account, Migrator for Notes to Exchange runs multiple
administrator accounts simultaneously on separate machines, each set to migrate with only one thread at a time.
The net throughput becomes a function of the sum of all these multiple accounts’ processing threads—one per
administrator account.
Migrator for Notes to Exchange includes an Admin Account Pool utility that helps you manage a pool of Office 365
administrator accounts for this purpose. The utility is designed to help you coordinate and "choreograph" these
administrator accounts.

NOTE: To maximize the performance of concurrent migration threads, ensure the size of the pool is greater
than or equal to the total number of threads across all migration servers.

Licensing Office 365 accounts for the Admin

Account Pooling utility
Before March 2015, Office 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
Office 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 Office 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 Office 365 mailbox that may have
been created for the account, but admin accounts created for this purpose typically do not need or use Office 365
mailboxes.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

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

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
• For each MNE task you want to schedule

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 Office 365 specify additional requirements for the Migrator for
Notes to Exchange Account Pooling feature.

2. 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

3. 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).

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

124
Office 365 Admin Account Pool utility
4. 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

5. 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 Office 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.

6. 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

The MNE qsched.exe task-scheduling utility is compatible with the Admin Account Pool for migrations to Office
365, but only with an additional step added to the process. For other migration scenarios (to on-premises
Exchange or to Office 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, Office 365 access restrictions require an
intermediate scheduling mechanism to accommodate the Admin Account Pool.
When migrating to Office 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).

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

125
Office 365 Admin Account Pool utility
Managing the Admin Account Pool
Use the Admin Account Pool utility to manage your account pool. The utility lets you view the accounts in the pool,
change the common password for all admin accounts in the pool, and/or change the number of accounts in the
pool.

To make changes using the Admin Account Pool utility

1 Click Manage on one of the following screens:
▪ In the MNE Notes Migration Manager, on the Exchange Server Configuration screen.
▪ In the Data Migration Wizard, on the Select Destination Exchange Server screen.
- OR -
Run the program file (AdminAcctPoolManager.exe) independently.
The Admin Account Pool utility contains a single screen that contains a table of the Admin pool accounts that are
registered in the MNE database. Each time the program is started, it uses remote PowerShell to scan Office 365
and synchronize the MNE list of accounts with the Office 365 list.
2 Select the options that you want.
▪ Click Refresh to refresh the Current Owner, Allocate Time and Use Count values in the table:
These values change as migrations allocate, use, and release Admin pool accounts but you can get
the current values by clicking Refresh.
▪ Click Synchronize to resynchronize the utility’s list of accounts with Exchange and to view the
current list of Office 365 accounts registered in the MNE database. This is the same synchronization
that the utility performs each time you start the program.
▪ Reconfigure your Admin Account Pool by changing the values for any of these fields:
▫ Password: Enter a new password in the text box. The same password is assigned to all the
pooled admin accounts.
▫ New pool size: Change the number of accounts in the pool by setting a new number in the
New pool size field.

NOTE: If you set the New pool size to 0, or otherwise reduce the pool size, any licenses
associated with accounts no longer in the pool become available for other accounts.

▫ License Admin Pool Accounts: Select the check box to assign Office 365 licenses to
these accounts, or clear the check box to dissociate Office 365 licenses from these
accounts.

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

3 When you have entered the changes you want, click Apply.
The Apply button applies the changes, automatically synchronizes with Office 365, and refreshes the table
display.
4 Click Close.
While any of these operations are in progress, the status bar at the bottom of the screen displays progress
information, and the Close button temporarily changes to a Cancel button.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

126
Office 365 Admin Account Pool utility
 15
PowerShell cmdlets for Migrator for
Notes to Exchange

Using PowerShell Cmdlets

You may use these PowerShell cmdlets to configure and troubleshoot various wizards and other components of
Quest’s Migrator for Notes to Exchange.
To import the PowerShell module so you can use the Migrator for Notes to Exchange cmdlets, enter the following
command in a PowerShell console:
Import-Module Quest.MNE.Powershell
To view a list of the available Migrator for Notes to Exchange cmdlets, enter the following command:
Get-Command -Module Quest.MNE.Powershell

Common Parameters
In addition to the cmdlet-specific parameters documented following, all these cmdlets support the common
parameters that Microsoft builds into all PowerShell cmdlets, as described in the Microsoft article
about_CommonParameters.

Cmdlets in Quest.MNE.Powershell
Add-MNECollectionMember

Synopsis
Adds a member object to the specifies collection.

Syntax
Add-MNECollectionMember [-CollectionGuid] <Guid> [-ObjectSmtpAddress] <string>
[<CommonParameters>]

Add-MNECollectionMember [-CollectionGuid] <Guid> -ObjectGuid <Guid>

[<CommonParameters>]

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

127
PowerShell cmdlets for Migrator for Notes to Exchange
Description
Adds a specified object (either selected by GUID or SMTP address) to the specified collection (by GUID).
Validates whether there is an object GUID or SMTP address given in the input.

Parameters
-CollectionGuid <Guid>
The Guid of the collection to add the member to.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ObjectSmtpAddress <string>
The SMTP address of the object to be added to the collection.

Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ObjectGuid <Guid>
The Guid of the object to be added to the collection.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
Accepts pipeline input for the collection guid.

Outputs
QuestSoftware.NMEAPI.Controllers.NMECollection
Outputs the collection that was added to, if there are no errors.

Examples
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
128
PowerShell cmdlets for Migrator for Notes to Exchange
PS C:\>Add-MNECollectionMember -CollectionGuid 455E1829-45D1-4485-8467-80A463DA5227
-ObjectGuid DA096D83-A07D-44F6-A0D2-35B88A10F6A5
Adds the object with the given Guid to the collection with the given Guid.

PS C:\>Add-MNECollectionMember -CollectionGuid 455E1829-45D1-4485-8467-80A463DA5227

-ObjectSmtpAddress Admin@Sample.test.com
Adds the object with the given Smtp address to the collection with the given Guid.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

129
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNEDesignClass

Synopsis
Adds a design class to the database.

Syntax
Add-MNEDesignClass [-DesignClassName] <string> -Authoritative <Boolean> -
DataStoreTypeMask <DataStoreTypeMaskEnum> [<CommonParameters>]

Description
Adds a design class to the database, per specified parameters.

Parameters
-DesignClassName <string>
Name of the design class to add.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Authoritative <Boolean>
Whether or not the design class to add has authoritative status.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DataStoreTypeMask <DataStoreTypeMaskEnum>
Data store type mask of the design class to add.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

130
PowerShell cmdlets for Migrator for Notes to Exchange
Inputs
System.String
Pipeline input for the DesignClassName.

Outputs
NMEDesignClass
Design class that was added, if there are no errors.

Examples
PS C:\>Add-MNEDesignClass -DesignClassName "TestName" -Authoritative $true -
DataStoreTypeMask All
Adds a design class with the given parameters to the database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

131
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNEGroupCollection

Synopsis
Adds a group collection.

Syntax
Add-MNEGroupCollection [-Name] <string> [-Label <string>] [-Description <string>] [-
Query <string>] [-QueryType <NmeCollectionQueryType>] [-Disabled]
[<CommonParameters>]

Description
Adds a specified new group collection.

Parameters
-Name <string>
The name of the group collection to add.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Label <string>
The label to add to the group collection.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Description <string>
The description of the group collection to add.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Query <string>
The query of the group collection to add.

Required: false
Position: Named
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
132
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QueryType <NmeCollectionQueryType>
The query type of the group collection to add.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Disabled [<SwitchParameter>]
The collection should be disabled after adding.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Collection
Returns the collection that was added, if there are no errors.

Examples
PS C:\>Add-MNEGroupCollection -Name "GroupCollection" -Label "SampleGroup" -
Description "This is a test" -Query "This is a query"
Adds the group collection with the given values into the database.

PS C:\>Add-MNEGroupCollection -Name "GroupCollection" -Label "SampleGroup" -

Description "This is a test" -QueryType Dynamic -Query "This is a query"
Adds the group collection with the given values into the database and sets the group collection to use dyanmic
query to populate members.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

133
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNEInetDomain

Synopsis
Adds specified InetDomain to the database by specific name or an existing object.

Syntax
Add-MNEInetDomain [-DomainName] <string> [-Disabled] [-IsDefault]
[<CommonParameters>]

Add-MNEInetDomain [-AsObject] <InetDomain> [-Disabled] [-IsDefault]

[<CommonParameters>]

Description
Adds specified InetDomain to the database by specific name or an existing object.

By default, the domain is marked as active and does not change the default.

Throws errors if domain already exist in database or has incorrect syntax.

Parameters
-DomainName <string>
The name of the domain. Must have a period and only consist of Letters, Numbers, and Hyphens.

The cmdlet throws an error if domain is already present in database or have incorrect syntax.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-AsObject <InetDomain>
Create and add a new domain to database from existing object.

All same rules for domainName, and IsDefault apply.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Disabled [<SwitchParameter>]
Sets the Domain to be disabled, not active.

Required: false
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
134
PowerShell cmdlets for Migrator for Notes to Exchange
 Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-IsDefault [<SwitchParameter>]
Sets domain to be the default domain. Changes all other domain defaults to be false.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
Add new domain by domain name from pipeline input.

InetDomain
Add new domain by InetDomain object from pipeline input.

Outputs
InetDomain
Returns the InetDomain object that was added to the database.

Examples
PS C:\>Add-MNEInetDomain "test.domain.com"
Adds the domain "test.domain.com" to the database. Enabled is "true". This domain is not the default.

PS C:\>Add-MNEInetDomain "test.domain.com" -Disabled

Adds the domain "test.domain.com" to the database. Enabled is "false". This domain is not the default.

PS C:\>Add-MNEInetDomain "test.domain.com" -IsDefault

Adds the domain "test.domain.com" to the database. Enabled is "false". This domain is the default.

PS C:\>Add-MNEInetDomain -AsObject $domain

Adds the domain name from $domain to the database with the same GUID, DomainName, Enabled value, and
IsDefault status.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

135
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNEMailboxAdminPermission

Synopsis
Add the MNE admin user Full Access permission to mailboxes in the user collection for Office 365. If Admin
Account Pool is used, the Office365 admin role specified by the configuration will be used instead of the MNE
admin user.

Syntax
Add-MNEMailboxAdminPermission [-CollectionName] <string> [<CommonParameters>]

Add-MNEMailboxAdminPermission [-CollectionName] <string> -ConfigurationId <string>

[<CommonParameters>]

Add-MNEMailboxAdminPermission [-CollectionName] <string> -ConfigurationFileName

<string> [<CommonParameters>]

Description
Prior to migrating the Notes mail database to Office Online, you must grant the migration admin user Full Access
permission to the mailboxes in the user collection. This cmdlet takes the MNE user collection name and grants the
migration admin user Full Access to the mailboxes in the user collection. Use the cmdlet Remove-
MNEMailboxAdminPermission to remove the Full Access permission granted to the admin user once the migration
is complete.

Parameters
-CollectionName <string>
Name of the user collection containing the mailboxes where the Exchange admin user will be granted Full
Access
permission.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationId <string>
Name or Guid of the existing configuration to use.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationFilename <string>
File name of a configuration settings .ini file to use as the configuration.
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
136
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
QuestSoftware.NME.PSModule.Utils.ManageMailboxPermissionResult
Returns a ManageMailboxPermissionResult object that contains information regarding the result of this
cmdlet.

Examples
PS C:\>Add-MNEMailboxAdminPermission "All Users"
Grants MNE admin user Full Access permission to mailboxes in the "All Users" collection using default
configuration setting and returns the results.

PS C:\>Add-MNEMailboxAdminPermission -CollectionName "All Users"

Grants the MNE admin user Full Access permission to mailboxes in the "All Users" collection using default
configuration settings and returns the results.

PS C:\>Add-MNEMailboxAdminPermission "All Users" -ConfigurationId "CDB86C40-49E2-

43E1-8DE5-E1B2F4A55B51"
Grants the MNE admin user Full Access permission to mailboxes in the "All Users" collection using configuration
settings by the given configuration id and returns the results.

PS C:\>Add-MNEMailboxAdminPermission "All Users" -ConfigurationId "Default Settings"

Grants the MNE admin user Full Access permission to mailboxes in "All Users" collection using configuration by
the given name and returns the results.

PS C:\>Add-MNEMailboxAdminPermission -CollectionName "All Users" -

ConfigurationFilename "C:\defaultconfig.ini"
Grants MNE admin user Full Access permission to mailboxes in the "All Users" collection using the configuration
settings specified in the file C:\defaultconfig.ini.

PS C:\>Add-MNEMailboxAdminPermission "All Users" | ForEach-Object -MemberName

"Mailboxes"
Grants the MNE admin user Full Access permission to mailboxes in the "All Users" collection using default
configuration settings and returns a list of mailboxes that were processed.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

137
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNENotesDomain

Synopsis
Adds a NotesDomain to the database using a domain name and type or NotesDomain object

Syntax
Add-MNENotesDomain [-DomainName] <string> [[-DomainType] <DomainTypeEnum>]
[<CommonParameters>]

Add-MNENotesDomain [-AsObject] <NotesDomain> [<CommonParameters>]

Description
Parameters
-DomainName <string>
The name of the domain. Follows URI DNS syntax.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-DomainType <DomainTypeEnum>
The type of domain. The default type is None if not specified.

The valid type are None, Domain, and GlobalDomain.

Required: false
Position: 1
Default value:"None"
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-AsObject <NotesDomain>
Add a NotesDomain from the properties of another NotesDomain object.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
138
PowerShell cmdlets for Migrator for Notes to Exchange
Inputs
string
The name of the domain. Follows URI DNS syntax.

DomainTypeEnum
The type of domain. The valid type are None, Domain, and GlobalDomain.

NotesDomain
Add a NotesDomain from the properties of another NotesDomain object.

Outputs
NotesDomain
Returns the NotesDomain object that was added to the database.

Examples
PS C:\>Add-MNENotesDomain "test.domain.com"
Adds the domain "test.domain.com" to the database. DomainType defaults to "None".

PS C:\>Add-MNENotesDomain "test.domain.com" GlobalDomain

Adds the domain "test.domain.com" to the database. DomainType is set to "GlobalDomain".

PS C:\>Add-MNENotesDomain -AsObject $domain

Adds the domain name from $domain to the database with the same GUID, DomainName, and DomainType.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

139
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNENotesNab

Synopsis
Adds the Nab specified by the given path. The Nab is either from a local file or from the domino server.

Syntax
Add-MNENotesNab [-FilePath] <string> [-NotesPassword <string>] [-Title <string>]
[<CommonParameters>]

Description
The Add-MNENotesNab cmdlet add the Nab (Notes Address Book) that is given by the filepath.

The title is automatically added from the Nab if not specified by the user.

Displays warnings if the path is not found, it is of the incorrect file type, or the NAB already exists in the database.

Throws an exception if trying to access Notes Server on non-32 bit PowerShell.

Parameters
-FilePath <string>
The location of the Notes Address Book to add. The path may be a local path or a path to the Notes Server
formatted as it is in the NME program.

The cmdlet confirms whether the file is the correct extension, whether the FilePath already exists in the
database, and whether the FilePath is valid.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByPropertyName)
Accept wildcard characters:false

-NotesPassword <string>
The password for the Domino server if needed. Must have ID file already selected for Notes.

Can be left as empty if the NAB is on a local (non-Notes) path.

Required: false
Position: Named
Default value:
Accept pipeline input:true (ByPropertyName)
Accept wildcard characters:false

-Title <string>
Allows the user to specify a title for the NAB.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

140
PowerShell cmdlets for Migrator for Notes to Exchange
 If left null, the title will be retrieved from the NAB.

Required: false
Position: Named
Default value:
Accept pipeline input:true (ByPropertyName)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
This cmdlet accepts FilePath, NotesPassword, Title from pipeline input.

Outputs
This cmdlet either returns a warning if incorrect or returns nothing and simply adds the NAB to the SQL
database.

Examples
PS C:\>Add-MNENotesNab -Filepath "C:\Example.nsf" -Title "Test"
Retrieves the NAB located at "C:\Example.nsf" from the local files. Sets the title as "Test".

PS C:\>Add-MNENotesNab -Filepath "!!names.nsf"

Retrieves the NAB located in the local Notes server named names.nsf.

PS C:\>Add-MNENotesNab -Filepath "NotesServer/Example!!names.nsf" -NotesPassword

"pa55w0rd"
Retrieves the NAB located in the Notes server "NotesServer/Example" named names.nsf. Gives the password to
initialize the notes server rather than prompting.

PS C:\>Import-Csv .\test.csv | Add-MNENotesNab

Retrieves the NAB(s) in the specified .csv file.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

141
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNEUserCollection

Synopsis
Adds a user collection.

Syntax
Add-MNEUserCollection [-Name] <string> [-Label <string>] [-Description <string>] [-
Query <string>] [-QueryType <NmeCollectionQueryType>] [-Disabled]
[<CommonParameters>]

Description
Adds a specified new user collection.

Parameters
-Name <string>
The name of the user collection to add.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Label <string>
The label of the user collection to add.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Description <string>
The description of the user collection to add.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Query <string>
The query of the user collection to add.

Required: false
Position: Named
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
142
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QueryType <NmeCollectionQueryType>
The query type of the user collection to add.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Disabled [<SwitchParameter>]
The collection should be disabled after adding.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Collection
Outputs the collection that was added, if there are no errors.

Examples
PS C:\>Add-MNEUserCollection -Name "UserCollection" -Label "SampleGroup" -
Description "This is a test" -Query "This is a query"
Adds the user collection with the given values into the database.

PS C:\>Add-MNEUserCollection -Name "UserCollection" -Label "SampleGroup" -

Description "This is a test" -QueryType Dynamic -Query "This is a query"
Adds the user collection with the given values into the database and sets the user collection to use dyanmic query
to populate members.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

143
PowerShell cmdlets for Migrator for Notes to Exchange
Add-MNEWorkstation

Synopsis
Adds a new workstation to the database.

Syntax
Add-MNEWorkstation -WorkstationName <string> -TcpipAddress <string>
[<CommonParameters>]

Description
Adds a new workstation to the SQL database with the given workstation name and TCP/IP address.

Parameters
-WorkstationName <string>
Name of the workstation to add.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByPropertyName)
Accept wildcard characters:false

-TcpipAddress <string>
TCPaddress of the workstation to add.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByPropertyName)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
Both the WorkstationName and TCPIPAddress parameters accept pipeline input by property value.

Outputs
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
144
PowerShell cmdlets for Migrator for Notes to Exchange
QuestSoftware.NMEAPI.Controllers.Workstation
Returns the workstation that was added to the database.

Examples
PS C:\>Add-MNEWorkstation -WorkstationName "MyComputer" -TCPIPAddress
"000.000.00.000"

Add the workstation to the database with name "MyComputer" and IP address "000.000.00.000"

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

145
PowerShell cmdlets for Migrator for Notes to Exchange
Convert-MNEConfiguration

Synopsis
Converts a configuration between a Task and Template Config.

Syntax
Convert-MNEConfiguration [-ConfigurationFromPipeline] <NMEConfiguration> -
ConvertToTask [<CommonParameters>]

Convert-MNEConfiguration [-ConfigurationFromPipeline] <NMEConfiguration> -

ConvertToTemplate [-TemplateType <TemplateTypeEnum>] [<CommonParameters>]

Description
Converts a configuration from a task to a template or vise versa, then saves it to the database.

Parameters
-ConfigurationFromPipeline <NMEConfiguration>
Configuration to convert.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ConvertToTask [<SwitchParameter>]
Convert the Configuration to a Task Config.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConvertToTemplate [<SwitchParameter>]
Convert the Configuration to a Template Config.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TemplateType <TemplateTypeEnum>
Convert the Template Configuration to Full Template or Differential Template. If the configuration is already a
Template configuration, no conversion will be done if the TemplateType parameter is not specified.
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
146
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: Named
Default value:.Full
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
Configuration
The Configuration parameter accepts pipeline input.

Outputs
Configuration
Returns the converted configuration.

Examples
PS C:\>$config | Convert-MNEConfiguration -ConvertToTemplate

Converts the config piped in to a Template

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

147
PowerShell cmdlets for Migrator for Notes to Exchange
Copy-MNEGroupCollection

Synopsis
Copies a group collection.

Syntax
Copy-MNEGroupCollection [-CollectionName] <string> [-Name] <string> [-Label
<string>] [-Description <string>] [-Query <string>] [-QueryType
<NmeCollectionQueryType>] [<CommonParameters>]

Description
This cmdlet copies a specified group collection.

Parameters
-CollectionName <string>
Name of the group collection to copy.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Name <string>
Name of the group collection to copy to.

Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Label <string>
Label of the group collection to copy to.

If not specified, the label of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Description <string>
Description of the group collection to copy to.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

148
PowerShell cmdlets for Migrator for Notes to Exchange
 If not specified, the description of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Query <string>
Query of the group collection to copy to.

If not specified, the query of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QueryType <NmeCollectionQueryType>
Query type of the group collection to copy to.

If not specified, the query type of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Collection
Returns the collection that was copied to, if there are no errors.

Examples
PS C:\>Copy-MNEGroupCollection -CollectionName "OriginalCollection" -Name
"GroupCollection" -Label "SampleGroup" -Description "This is a test" -Query "This
is a query"
Copies the group collection with the given values into the database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

149
PowerShell cmdlets for Migrator for Notes to Exchange
PS C:\>Copy-MNEGroupCollection -CollectionName "OriginalCollection" -Name
"GroupCollection" -Label "SampleGroup" -Description "This is a test" -QueryType
Dynamic -Query "This is a query"
Copies the group collection with the given values into the database and sets the group collection to use dyanmic
query to populate members.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

150
PowerShell cmdlets for Migrator for Notes to Exchange
Copy-MNEUserCollection

Synopsis
Copies a user collection.

Syntax
Copy-MNEUserCollection [-CollectionName] <string> [-Name] <string> [-Label <string>]
[-Description <string>] [-Query <string>] [-QueryType <NmeCollectionQueryType>]
[<CommonParameters>]

Description
Copies a specified user collection.

Parameters
-CollectionName <string>
Name of the user collection to copy.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Name <string>
Name of the user collection to copy to.

Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Label <string>
Label of the user collection to copy to.

If not specified, the label of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Description <string>
Description of the user collection to copy to.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

151
PowerShell cmdlets for Migrator for Notes to Exchange
 If not specified, the description of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Query <string>
Query of the user collection to copy to.

If not specified, the query of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QueryType <NmeCollectionQueryType>
Query type of the user collection to copy to.

If not specified, the query type of the copy collection is set to that of the original.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Collection
Outputs the collection that was copied to, if there are no errors.

Examples
PS C:\>Copy-MNEUserCollection -CollectionName "OriginalCollection" -Name
"UserCollection" -Label "SampleGroup" -Description "This is a test" -Query "This is
a query"
Copies the user collection with the given values into the database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

152
PowerShell cmdlets for Migrator for Notes to Exchange
PS C:\>Copy-MNEUserCollection -CollectionName "OriginalCollection" -Name
"UserCollection" -Label "SampleGroup" -Description "This is a test" -QueryType
Dynamic -Query "This is a query"
Copies the user collection with the given values into the database and sets the user collection to use dyanmic
query to populate members.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

153
PowerShell cmdlets for Migrator for Notes to Exchange
Export-MNECollections

Synopsis
Exports collections of a specific type to a .tsv file.

Syntax
Export-MNECollections [-Path] <string> [-CollectionType] <CollectionTypeEnum> [-
Autodefined <Boolean>] [-LogFile <string>] [<CommonParameters>]

Description
This cmdlet exports the collections of a specific type to a file specified by the user.

Exports all non-autodefined collections in the database by default.

Parameters
-Path <string>
The file to export the group collection to.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-CollectionType <CollectionTypeEnum>
The type of collection to export. Valid collection types are None, User, Group or Scheduling.

Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Autodefined <Boolean>
Include autodefined collections
Required: false
Position: Named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-LogFile <string>
Location of the Logfile to create/append to.

Required: false
Position: Named
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
154
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
The file to export the group collection to.

Boolean
Include autodefined collections.

Outputs
PSObject
Returns the stats of the export.

Examples
PS C:\>Export-MNECollections -Path "C:\Path.tsv" -CollectionType Group
Exports the group collections to the file at "C:\Path.tsv".

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

155
PowerShell cmdlets for Migrator for Notes to Exchange
Export-MNEConfiguration

Synopsis
Export a configuration to a file.

Syntax
Export-MNEConfiguration [-ConfigurationGuid] <Guid> [[-FileName] <string>] [-Force]
[-RawConfiguration] [<CommonParameters>]

Description
Exports a configuration to the specified file.

Updates the file with the configuration represented by the configuration Guid.

Parameters
-ConfigurationGuid <Guid>
Guid of the configuration to export to the file.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-FileName <string>
File to export the configuration to.

Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Force [<SwitchParameter>]
Overwrite an existing file without prompting the user for confirmation.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RawConfiguration [<SwitchParameter>]
Export configuration settings from database without merging with default settings.

Required: false
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
156
PowerShell cmdlets for Migrator for Notes to Exchange
 Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
Configuration Guid accepts input from the pipeline.

Outputs
This cmdlet returns the directory path of the exported file upon a successful run.

Examples
PS C:\>Export-MNEConfiguration -ConfigurationGuid 69F764C9-D209-4C4D-BCCB-
6E59F615CD9D -FileName "TestName"
Exports the configuration from the specified Guid to the file named "TestName" with the default file extension ".ini"
in the current directory.

PS C:\>Export-MNEConfiguration -ConfigurationGuid 69F764C9-D209-4C4D-BCCB-

6E59F615CD9D -FileName "C:\Temp.ini"
Exports the configuration from the specified Guid to the file of the given file path.

PS C:\>Export-MNEConfiguration -ConfigurationGuid 69F764C9-D209-4C4D-BCCB-

6E59F615CD9D
Exports the configuration from the specified Guid to the file with the name of the given Guid and file extension ".ini"
in the current directory.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

157
PowerShell cmdlets for Migrator for Notes to Exchange
Export-MNEConfigurationData

Synopsis
Export configuration data to a file.

Syntax
Export-MNEConfigurationData [-ConfigurationData] <ConfigurationData> [[-FileName]
<string>] [-Force] [<CommonParameters>]

Description
Exports configuration data to the specified file.

Updates the file with the configuration data.

Parameters
-ConfigurationData <ConfigurationData>
Configuration data to export to the file.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-FileName <string>
File to export the configuration data to.

Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Force [<SwitchParameter>]
Overwrite an existing file without prompting the user for confirmation.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
158
PowerShell cmdlets for Migrator for Notes to Exchange
 about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
ConfigurationData
The ConfigurationData parameter accepts input from the pipeline.

Outputs
This cmdlet returns the directory path of the exported file upon a successful run.

Examples
PS C:\>Export-MNEConfigurationData -ConfigurationData $data -FileName "TestName"
Exports the configuration data object to the specified file with the default file extension ".ini" in the current directory.

PS C:\>Export-MNEConfigurationData -ConfigurationData $data -FileName "c:\temp.ini"

Exports the configuration data object to the file specified in the directory path.

PS C:\>Export-MNEConfigurationData -ConfigurationData $data

Exports the given configuraiton data object to a file specified in the configuration data object or to the default file
name "ConfigurationData.ini" in the current directory.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

159
PowerShell cmdlets for Migrator for Notes to Exchange
Export-MNESummary

Synopsis
Exports data from the specified summary to the designated tsv (tab-delimited file).

Syntax
Export-MNESummary [-FilePath] <string> [-Summary] <ViewSummary> [<CommonParameters>]

Description
Exports data from the specified summary to the designated tsv (tab-delimited file).
The path specified will automatically overwrite any existing file.

The Summary is chosen by a ViewSummary enum value

Parameters
-FilePath <string>
The designated export location and filename for the summary.

The cmdlet will confirm if the file is the correct extension and overwrite any existing file.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Summary <ViewSummary>
The chosen summary to be exported.

Valid summary type are UserAndResources, DistributionList, InetDomains, NotesDomains, DatastoreDesign,

UserMigrationStatus, DistributionListProvisioning and DatastoreStatus.

Uses a ViewSummary enum for ease of use.

Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

160
PowerShell cmdlets for Migrator for Notes to Exchange
Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
This cmdlet returns no values on a successful run.

Examples
PS C:\>Export-MNESummary -Filepath "C:\summary.tsv" -Summary UserAndResources
Exports the user and resurces summary to a tsv file called "summary" in the root of the c drive.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

161
PowerShell cmdlets for Migrator for Notes to Exchange
Format-MNEDatabaseExport

Synopsis
Removes certain lines in the NME Database Export that are expected to change.

For this cmdlet to work properly, the export must be exported with high width, so that the file was not cut off by the
window size.

Syntax
Format-MNEDatabaseExport -InputFile <string> [-IgnoreFile <string>]
[<CommonParameters>]

Description
Parameters
-InputFile <string>
File that will be formatted.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-IgnoreFile <string>
Path to a file containing all the lines of text to ignore in it.

If not specified, the text to ignore will default to "ComputerName :", "TcpipAddress :", "LogDir=",
"EndUserDir=", "SMTPTranslationTable=", "CentralLogDir=", "~AdminPassword=", "UserIdFile=", "~Password=",
"LastProvisionUserCollectionsCollection=", "LastLocateNotesDataStoresCollection=", "ATGenerated=",
"LastManageUserCollectionsLabel=", "LastManageGroupsLabel=", "LastProvisionUserCollectionsLabel=",
"LastSendPabReplicatorLabel=", "LastSendPabReplicatorCollection=", "DefaultAdminIniStatus=",
"DefaultDesktopIniStatus=", "LastProvisionGroupsLabel=", "LastProvisionGroupsCollection=",
"LastLocateNotesDataStoresLabel=", "LastMigrateUserDataLabel=", "LastMigrateUserDataCollection=".

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

162
PowerShell cmdlets for Migrator for Notes to Exchange
Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
System.String
Returns the formatted output.

Examples
PS C:\>Format-MNEDatabaseExport -InputFile C:\exampleexport.txt
Formats the database export at C:\exampleexport.txt using the default ignore lines and outputs it to the console.

PS C:\>Format-MNEDatabaseExport -InputFile C:\exampleexport.txt -IgnoreFile

C:\ignore.txt
Formats the database export at C:\exampleexport.txt using the ignore lines from C:\ignore.txt and outputs it to the
console.

PS C:\>Format-MNEDatabaseExport -InputFile C:\exampleexport.txt | Out-File

C:\formattedexport.txt -Width 9001
Formats the database export at C:\exampleexport.txt using the default ignore lines and outputs it to
C:\formattedexport.txt.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

163
PowerShell cmdlets for Migrator for Notes to Exchange
Format-MNEGroupCollection

Synopsis
Formats a group collection.

Syntax
Format-MNEGroupCollection [-CollectionName] <string> [-Name <string>] [-Label
<string>] [-Description <string>] [-Query <string>] [-QueryType
<NmeCollectionQueryType>] [<CommonParameters>]

Description
Formats the indicated group collection with the values of the other parameters.

Parameters
-CollectionName <string>
Name of the group collection to format.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Name <string>
Name to change the group collection name to.

If not specified, the name of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Label <string>
Label to change the group collection label to.

If not specified, the label of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Description <string>
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
164
PowerShell cmdlets for Migrator for Notes to Exchange
 Description to change the group collection description to.

If not specified, the description of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Query <string>
Query to change the group collection query to.

If not specified, the query of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QueryType <string>
Query type to change the group collection query to.

If not specified, the query type of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Collection
Outputs the collection that was updated to, if there are no errors.

Examples
PS C:\>Format-MNEGroupCollection -CollectionName "OriginalCollection" -Name
"GroupCollection" -Label "SampleGroup" -Description "This is a test" -Query "This
is a query"

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

165
PowerShell cmdlets for Migrator for Notes to Exchange
Updates the group collection with the given values into the database.

PS C:\>Format-MNEGroupCollection -CollectionName "OriginalCollection" -Name

"GroupCollection" -Label "SampleGroup" -Description "This is a test" -QueryType
Dynamic -Query "This is a query"
Updates the group collection with the given values into the database and sets the group collection to use dyanmic
query to populate members.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

166
PowerShell cmdlets for Migrator for Notes to Exchange
Format-MNEUserCollection

Synopsis
Formats a user collection.

Syntax
Format-MNEUserCollection [-CollectionName] <string> [-Name <string>] [-Label
<string>] [-Description <string>] [-Query <string>] [-QueryType
<NmeCollectionQueryType>] [<CommonParameters>]

Description
This cmdlet formats the indicated user collection with the values of the other parameters.

Parameters
-CollectionName <string>
Name of the user collection to format.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Name <string>
Name to change the user collection name to.

If not specified, the name of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Label <string>
Label to change the user collection label to.

If not specified, the label of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Description <string>
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
167
PowerShell cmdlets for Migrator for Notes to Exchange
 Description to change the user collection description to.

If not specified, the description of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Query <string>
Query to change the user collection query to.

If not specified, the query of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QueryType <NmeCollectionQueryType>
Query type to change the user collection query to.

If not specified, the query type of the collection will remain the same.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Collection
Outputs the collection that was updated to, if there are no errors.

Examples
PS C:\>Format-MNEUserCollection -CollectionName "OriginalCollection" -Name
"GroupCollection" -Label "SampleGroup" -Description "This is a test" -Query "This
is a query"

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

168
PowerShell cmdlets for Migrator for Notes to Exchange
Updates the user collection with the given values into the database.

PS C:\>Format-MNEUserCollection -CollectionName "OriginalCollection" -Name

"GroupCollection" -Label "SampleGroup" -Description "This is a test" -QueryType
Dynamic -Query "This is a query"
Updates the user collection with the given values into the database and sets the user collection to use dyanmic
query to populate members.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

169
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEAutodiscoverUserSettings

Synopsis
Returns the user settings obtained from the Plain Old XML (POX) Autodiscover service.

Syntax
Get-MNEAutodiscoverUserSettings [-UserSmtpAddress] <string> [-AutodiscoverUrl
<string>] [-Credential <PSCredential>] [-WebProxyCredential <PSCredential>] [-
AllowSelfSignedCertificates] [-EnableScpLookup] [-DisableMapiHttp] [-MaxHops
<Integer>] [<CommonParameters>]

Description
Returns the user settings obtained from the Plain Old XML (POX) Autodiscover service.

Parameters
-UserSmtpAddress <string>
Specifies the user SMTP address used to perform autodiscover.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-AutodiscoverUrl <string>
Specifies the Autodiscover Url endpoint.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Credential <PSCredential>
Specifies the credentials that are used to authenticate with the Autodiscover service.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WebProxyCredential <PSCredential>
Specifies the HTTP proxy credential settings.

Required: false
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
170
PowerShell cmdlets for Migrator for Notes to Exchange
 Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AllowSelfSignedCertificates [<SwitchParameter>]
Validate the certificate for the server responding to the Autodiscover request. By default only certificates
signed by a trusted root authority are considered valid. Self-signed certificates are only considered valid if this is
set to True.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EnableScpLookup [<SwitchParameter>]
Indicates whether MNE should perform a service connection point (SCP) lookup when it is determining the
service URL.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DisableMapiHttp [<SwitchParameter>]
Determines whether or not MNE requests MAPI/HTTP protocol information from the Autodiscover service.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxHops <Integer>
Specifies the value for maximum number of redirects or hops when performing autodiscover. The default value
is
10.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
171
PowerShell cmdlets for Migrator for Notes to Exchange
 The UserSmtpAddress parameter accepts values from the pipeline.

Outputs
QuestSoftware.EwsMe.IPoxUserSettings
Returns user settings from the Plain old XML (POX) Autodiscover service response.

Examples
PS C:\>Get-MNEAutodiscoverUserSettings -UserSmtpAddress test@domain.com
Returns user settings such as UserDisplayName, UserDN, ExternalMailboxServer, etc. from the Autodiscover
service response.

PS C:\>$cred = Get-CredentialGet-MNEAutodiscoverUserSettings -UserSmtpAddress

test@company.onmicrosoft.de -Credential $cred
Returns user settings by supplying user credential obtained from Get-Credential cmdlet.

PS C:\>Get-MNEAutodiscoverUserSettings -UserSmtpAddress test@company.onmicrosoft.de

-AutodiscoverUrl https://outlook.office.de/autodiscover/autodiscover.svc
Returns user settings by supplying AutodiscoverUrl. This eliminates the need for MNE to have to resolve the
Autodiscover URL.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

172
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNECollection

Synopsis
Gets all of the collections or the indicated collection from the database.

Syntax
Get-MNECollection [-CollectionType <NmeCollectionType>] [<CommonParameters>]

Get-MNECollection [-CollectionGuid] <Guid> [<CommonParameters>]

Description
This cmdlet returns either all collections in the database, or the collection for the specified GUID.

Parameters
-CollectionType <NmeCollectionType>
The collection type to search for. The default type is User.

Valid collection type must be either User or Group.

Required: false
Position: named
Default value:.User
Accept pipeline input:false
Accept wildcard characters:false

-CollectionGuid <Guid>
Guid of the collection to get from the database.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
Guid
The CollectionGuid parameter accepts input from the pipeline.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

173
PowerShell cmdlets for Migrator for Notes to Exchange
Outputs
Collection
Returns either a single specified collection, or all collections in the database of the specified type.

Examples
PS C:\>Get-MNECollection -CollectionGuid 455E1829-45D1-4485-8467-80A463DA5227
Returns the user or group collection associated with the given Guid.

PS C:\>Get-MNECollection
Returns all user collections in the database.

PS C:\>Get-MNECollection -CollectionType Group

Returns all group collections in the database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

174
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNECollectionMember

Synopsis
Returns all members in a collection.

Syntax
Get-MNECollectionMember [-CollectionGuid] <Guid> [<CommonParameters>]

Description
Returns all members in a collection that is specified by the Guid given by the user.

Parameters
-CollectionGuid <Guid>
Guid of collection to retrieve the collection members from.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
The CollectionGuid parameter accepts values from the pipeline.

Outputs
CollectionMember
Returns all members of the given collection.

Examples
PS C:\>Get-MNECollectionMember -CollectionGuid 69F764C9-D209-4C4D-BCCB-6E59F615CD9D
Returns all members in the collection with the specified Guid.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

175
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEConfiguration

Synopsis
Returns either a single or multiple configurations.

Syntax
Get-MNEConfiguration [[-ConfigurationGuid] <Guid>] [-RawConfiguration
<SwitchParameter>] [<CommonParameters>]

Get-MNEConfiguration -Name <string> [-ConfigurationType <ConfigurationTypeEnum>] [-

RawConfiguration <SwitchParameter>] [<CommonParameters>]

Get-MNEConfiguration -ConfigurationType <ConfigurationTypeEnum> [-RawConfiguration

<SwitchParameter>] [<CommonParameters>]

Description
Returns either a single or multiple configurations based on the user input.

The inputs are given priority, with GUID being the highest, then name and configuration type enum (Optional),
then configuration type enum, then none.

Giving a GUID returns a single configuration with that Guid. Name and configuration type enum (Optional) returns
a single configuration with that name. The enum returns all configurations of that type. None returns all
configurations in the database.

Parameters
-ConfigurationGuid <Guid>
Can be used to retrieve the configuration of the specified Guid.

Required: false
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Name <string>
Can be used to retrieve the configuration of the specified name.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ConfigurationType <ConfigurationTypeEnum>
Can be used to retrieve the configuration of the specified name and the specified type based on the
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
176
PowerShell cmdlets for Migrator for Notes to Exchange
ConfigurationTypeEnum.

Can be used to retrieve all configurations of the specified type based on the ConfigurationTypeEnum.

The valid configuration types are Default, DiscoverNabs, DiscoverDomains, DirExport, MergeContacts,
DiscoverData, ProvisionGroups, SendPabReplicator, MigrateWithSSDM, MigrateWithAdmin and
GatherUserStats.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RawConfiguration [<SwitchParameter>]
Get raw configuration settings without merging with default settings.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.String
The Name of the configuration to retrieve.

System.Guid
The Guid of the configuration to retrieve.

Outputs
Configuration
Returns either a single or multiple configurations based on the user given input.

Examples
PS C:\>Get-MNEConfiguration -ConfigurationGuid 69F764C9-D209-4C4D-BCCB-6E59F615CD9D
Returns the configuration with the specified Guid.

PS C:\>Get-MNEConfiguration -Name "Migration Configuration"

Returns the configuration with the specified name.

PS C:\>Get-MNEConfiguration -Name "Migration Configuration" -ConfigurationType

MigrateWithAdmin

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

177
PowerShell cmdlets for Migrator for Notes to Exchange
Returns the configuration with the specified name and configuration type.

PS C:\>Get-MNEConfiguration -ConfigurationType DiscoverNabs

Returns all configurations with the specified configuration type.

PS C:\>Get-MNEConfiguration
Returns all configurations in the database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

178
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEDatabaseConnectionString

Synopsis
Gets the database connection string for the SQL database.

Syntax
Get-MNEDatabaseConnectionString [<CommonParameters>]

Description
Builds the connection string using SqlConnectionStringBuilder.

Then writes the connection after getting the connection string from the NME database connection.

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet does not have any parameters that accept pipeline input.

Outputs
System.Data.SqlClient.SqlConnectionStringBuilder
Returns the database connection string object.

Examples
PS C:\>Get-MNEDatabaseConnectionString
Retrieves the connection to the SQL database for Notes Migrator for Exchange.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

179
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEDatabaseExport

Synopsis
Accesses the NME Database and exports it.

Quest recommendeds you pipe the output to Out-File.

Syntax
Get-MNEDatabaseExport [<CommonParameters>]

Description
Accesses the NME Database and exports it to console output.

Quest recommendeds you pipe the output to Out-File.

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
System.String
Outputs the full NME database. Quest recommendeds you to output this to a file.

Examples
PS C:\>Get-MNEDatabaseExport
Exports the NME Database directly to the console.

PS C:\>Get-MNEDatabaseExport | Out-File C:\exampleexport.txt -Width 9001

Exports the NME Database to the file C:\exampleexport.txt with a high width, so that the text does not get cut off
by the size of the window.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

180
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEDatabaseVersion

Synopsis
Gets the database version.

Syntax
Get-MNEDatabaseVersion [<CommonParameters>]

Description
This cmdlet returns the database version.

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Version
Returns the current database version.

Examples
PS C:\>Get-MNEDatabaseVersion
Returns the current database version.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

181
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEGlobalDefaultSettings

Syntax
Get-MNEGlobalDefaultSettings [<CommonParameters>]

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
None

Outputs
System.ObjectALIASES
NoneREMARKS
None

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

182
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNELicense

Synopsis
Gets the currently installed license information from MNE.

Syntax
Get-MNELicense [<CommonParameters>]

Description
Gets the currently installed license information from MNE.

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
LicenseInfo
PSObject that contains license Type, ExpirationDate, Status, IsValid, Number, MigratedUsers, and
SeatsUsed.

Examples

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

183
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEMigrationResult

Synopsis
Returns all relevant data from the migration for the specified objects. You can input an SMTP address, object
Guid, or collection Guid to get the information.

Syntax
Get-MNEMigrationResult [-SmtpAddress] <string> [<CommonParameters>]

Get-MNEMigrationResult -ObjectGuid <Guid> [<CommonParameters>]

Get-MNEMigrationResult -CollectionGuid <Guid> [<CommonParameters>]

Description
This cmdlet returns all relevant data from the migration for the specfied objects. You can input an SMTP address,
object Guid, or collection Guid to get the information.

Parameters
-SmtpAddress <string>
The SMTP address of the object to check the migration results for.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ObjectGuid <Guid>
The Guid of the object to check the migration results for.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CollectionGuid <Guid>
The Guid of the collection to check the migration results for.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
184
PowerShell cmdlets for Migrator for Notes to Exchange
 This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.String
The cmdlet parameter SmtpAddress accepts input from the pipeline.

Outputs
MigrationUserResult, MigrationResourceResult
Returns all relevant data from the migration for the specified objects.

Examples
PS C:\>Get-MNEMigrationResult -SmtpAddress sample@test.nme.com
Returns the migration information for the user(s) or resource(s) with the given smtp address.

PS C:\>Get-MNEMigrationResult -ObjectGuid 555B8BB5-7AE0-4CBF-A7FF-9B11163CD9B1

Returns the migration information for the object with the given Guid.

PS C:\>Get-MNEMigrationResult -CollectionGuid 54899105-83EC-4009-B763-E54CA8C8B302

Returns the migration information for the collection members in the collection with the given Guid.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

185
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEMigrationTask

Synopsis
Gets either a single migration task (by task Guid) or multiple tasks (by Configuration type enum).

Syntax
Get-MNEMigrationTask -TaskGuid <Guid> [<CommonParameters>]

Get-MNEMigrationTask -ConfigurationType <ConfigurationTypeEnum>

[<CommonParameters>]

Description
Gets either a single migration task (by task Guid) or multiple tasks (by Configuration type enum).

Parameters
-TaskGuid <Guid>
Guid of the migration task to retrieve.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationType <ConfigurationTypeEnum>
Configuration type of the migration task(s) to retrieve.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept input from pipeline.

Outputs
Task

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

186
PowerShell cmdlets for Migrator for Notes to Exchange
 Returns the task(s) based on the given input.

Examples
PS C:\>Get-MNEMigrationTask -TaskGuid 555B8BB5-7AE0-4CBF-A7FF-9B11163CD9B1
Returns the migration task with the given Guid.

PS C:\>Get-MNEMigrationTask -ConfigurationType Default

Returns the migration task(s) with the given configuration type.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

187
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEMigrationTimeWindow

Synopsis
Gets the migration time window.

Syntax
Get-MNEMigrationTimeWindow [[-CollectionName] <string>] [<CommonParameters>]

Description
Gets the migration time window.

Returns the migration schedule for a given collection if the collection name is specified or for all scheduled
collections.

Parameters
-CollectionName <string>
Name of the collection to retrieve the schedule for if specfied.

Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept input from pipeline.

Outputs
SingleCollectionSchedule
Returns the schedule for a given collection if the collection name is specified.

Examples
PS C:\>Get-MNEMigrationTimeWindow -CollectionName "Test"
Returns the migration time information for the collection named "Test".
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
188
PowerShell cmdlets for Migrator for Notes to Exchange
PS C:\>Get-MNEMigrationTimeWindow
Returns the migration time information for all scheduled collections.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

189
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEResource

Synopsis
Gets the specified resource.

Syntax
Get-MNEResource [-SmtpEmailAddress] <string> [<CommonParameters>]

Get-MNEResource -ObjectGuid <Guid> [<CommonParameters>]

Description
This cmdlet returns the specified mail-in database or resource based on the specified smtp address or object
Guid.

Parameters
-SmtpEmailAddress <string>
SMTP address of the resource to retrieve.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ObjectGuid <Guid>
Guid of the object associated with the resource to retrieve.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.String
SMTP address of the resource to retrieve.

System.Guid

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

190
PowerShell cmdlets for Migrator for Notes to Exchange
 Guid of the object associated with the resource to retrieve.

Outputs
Resource
Returns the specified resource information (either by SMTP address or object Guid).

Examples
PS C:\>Get-MNEResource -SmtpEmailAddress sample@test.nme.com
Returns the resource associated with the given smtp address.

PS C:\>Get-MNEResource -ObjectGuid 335B8BB5-7AE0-4CBF-A7FF-9B11122CD9B1

Returns the resource associated with the given object Guid.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

191
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNESchedulingConfigFile

Synopsis
Gets the list of scheduling configuration files and returns them.

Syntax
Get-MNESchedulingConfigFile [<CommonParameters>]

Description
Gets the list of scheduling configuration files and returns them.

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
ConfigNames
Returns the names of the scheduling config files.

Examples
PS C:\>Get-MNESchedulingConfigFile
Gets and returns the names of the configuration files for the SSDM Scheduling Administration tool.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

192
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNESchedulingSetting

Synopsis
Gets and returns the list of global scheduling settings for the SSDM Scheduling Administration tool.

Syntax
Get-MNESchedulingSetting [<CommonParameters>]

Description
Gets the list of global scheduling settings for the SSDM Scheduling Administration tool and returns them.

Parameters
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
SchedulingGlobalSettings
Return the global settings for scheduling in SSDM Scheduling Administration tool.

Examples
PS C:\>Get-MNESchedulingSetting
Gets and returns the list of global scheduling settings for the SSDM Scheduling Administration tool.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

193
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNETaskError

Synopsis
Gets the Task Errors for a specified given task or run.

Syntax
Get-MNETaskError [-TaskRunGuid] <Guid> [<CommonParameters>]

Get-MNETaskError -TaskGuid <Guid> [<CommonParameters>]

Description
This cmdlet outputs the errors for a specified task and/or task run.

Parameters
-TaskRunGuid <Guid>
Guid of the task run to retrieve the errors from if retrieving by task run.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-TaskGuid <Guid>
Guid of the task to retrieve the errors from if retrieving by task.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
Guid
Guid of the task run to retrieve the errors from.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

194
PowerShell cmdlets for Migrator for Notes to Exchange
Outputs
string
Returns the errors for the task and/or task run as strings.

Examples
PS C:\>Get-MNETaskError -TaskGuid 555B8BB5-7AE0-4CBF-A7FF-9B11163CD9B1
Returns the task error information for the specified task.

PS C:\>Get-MNETaskError -TaskRunGuid 335B8BB5-7AE0-4CBF-A7FF-9B11122CD9B1

Returns the task error information for the specified task(s) from the run.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

195
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNETaskRun

Synopsis
Gets the specified task run.

Syntax
Get-MNETaskRun [-TaskRunGuid] <Guid> [<CommonParameters>]

Get-MNETaskRun -TaskName <string> [<CommonParameters>]

Get-MNETaskRun -TaskGuid <Guid> [<CommonParameters>]

Get-MNETaskRun -ConfigurationType <ConfigurationTypeEnum> [<CommonParameters>]

Description
This cmdlet retrieves information for a specified task run.

Parameters
-TaskRunGuid <Guid>
Guid of a task run, if looking for a task run by its own Guid.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-TaskName <string>
Task Name, if finding all task runs associated with a particular task.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-TaskGuid <Guid>
Guid of the task, if finding the task runs associated with that task.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

196
PowerShell cmdlets for Migrator for Notes to Exchange
 -ConfigurationType <ConfigurationTypeEnum>
Configuration Type, if finding all task runs associated with a particular configuration.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
Guid of a task run, if looking for a task run by its own Guid.

System.String
Task Name, if finding all task runs associated with a particular task.

Outputs
TaskRun
Outputs information on the specified task run.

Examples
PS C:\>Get-MNETaskRun -TaskGuid 555B8BB5-7AE0-4CBF-A7FF-9B11163CD9B1
Returns the task run associated with the task with the given Guid.

PS C:\>Get-MNETaskRun -TaskRunGuid 335B8BB5-7AE0-4CBF-A7FF-9B11122CD9B1

Returns the task run associated given task run Guid.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

197
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNETaskSchedule

Synopsis
Gets the specified task schedule.

Syntax
Get-MNETaskSchedule [-TaskGuid <Guid>] [<CommonParameters>]

Description
Retrieves information for a specific task schedule.

If no Guid is specified, this cmdlet returns all scheduled tasks.

Using verbose will output the name and Guid prior to the schedule.

Parameters
-TaskGuid <Guid>
Guid of the task specified to get the schedule for.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Schedule
Returns the schedule of the specified task, or the schedules of all scheduled tasks.

Examples
PS C:\>Get-MNETaskSchedule -TaskGuid 555B8BB5-7AE0-4CBF-A7FF-9B11163CD9B1
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
198
PowerShell cmdlets for Migrator for Notes to Exchange
Returns the task schedule associated with specified task Guid.

PS C:\>Get-MNETaskSchedule
Returns all schedules of scheduled tasks.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

199
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEUser

Synopsis
Gets the specified user.

Syntax
Get-MNEUser [[-SmtpEmailAddress] <string>] [<CommonParameters>]

Get-MNEUser -ObjectGuid <Guid> [<CommonParameters>]

Description
This cmdlet returns the specified user based on the defined smtp address or object Guid.

Parameters
-SmtpEmailAddress <string>
SMTP address of the user to retrieve.

Required: false
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ObjectGuid <Guid>
Guid of the object associated with the user to retrieve.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.String
SMTP address of the user to retrieve.

System.Guid
Guid of the object associated with the user to retrieve.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

200
PowerShell cmdlets for Migrator for Notes to Exchange
Outputs
User
Outputs the specified user information (either by SMTP address or object Guid).

Examples
PS C:\>Get-MNEUser -SmtpEmailAddress sample@test.nme.com
Returns the user associated with the given smtp address.

PS C:\>Get-MNEUser -ObjectGuid 335B8BB5-7AE0-4CBF-A7FF-9B11122CD9B1

Returns the user associated with the given object Guid.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

201
PowerShell cmdlets for Migrator for Notes to Exchange
Get-MNEWorkstation

Synopsis
Gets the workstation specified or all workstations.

Syntax
Get-MNEWorkstation [-WorkstationGuid <Guid>] [<CommonParameters>]

Description
This cmdlet returns the workstation specified by the given Guid or all workstation if no Guid is given.

Parameters
-WorkstationGuid <Guid>
Guid of the workstation to retrieve.

Required: false
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
WorkstationGuid parameter accepts pipeline input.

Outputs
Workstation
Outputs the workstation specified by user, or all workstations if no Guid is given.

Examples
PS C:\>Get-MNEWorkstation -WorkstationGuid 69F764C9-D209-4C4D-BCCB-6E59F615CD9D
Returns the workstation with the specified Guid.

PS C:\>Get-MNEWorkstation
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
202
PowerShell cmdlets for Migrator for Notes to Exchange
Returns all workstations in the database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

203
PowerShell cmdlets for Migrator for Notes to Exchange
Hide-MNECollection

Synopsis
Sets a Collection to be "invisible" in the UI.

Syntax
Hide-MNECollection [-Collection] <NmeCollection> [<CommonParameters>]

Description
Sets a Collection to be "invisible" in the UI. The collection is added/updated in the database upon completion.
Collections that are "invisible" are essentially disabled and will not be included during migrations.

Parameters
-Collection <NmeCollection>
The collection object to be hidden.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
NmeCollection
The Collection parameter accepts object input from the pipeline.

Outputs
None if successful

Examples
Get-MNECollection -CollectionGuid "e50d5123-2ec8-4096-816e-8e0e458d12e7" | Hide-
MNECollection
A collection is retrieved from the database and its visiblity is set to hidden.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

204
PowerShell cmdlets for Migrator for Notes to Exchange
Import-MNECollections

Synopsis
Import collections of any kind from a specified file.

Syntax
Import-MNECollections [-Path] <string> [-LogFile <string>] [<CommonParameters>]

Description
Import collections of any kind from a specified file.

Parameters
-Path <string>
Path to the file from which the collections will be imported.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-LogFile <string>
Path to which the log will be written.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
This cmdlet accepts file path input from the pipeline.

Outputs
PSObject

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

205
PowerShell cmdlets for Migrator for Notes to Exchange
 Import statistics information.

Examples
PS C:\>Import-MNECollections -Path "C:\Collections.tsv"
Imports the collections from the file at "C:\Collections.tsv".

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

206
PowerShell cmdlets for Migrator for Notes to Exchange
Import-MNEConfiguration

Synopsis
Import a configuration from file.

Syntax
Import-MNEConfiguration [-ConfigurationGuid] <Guid> [-FileName] <string> [-
RawConfiguration] [<CommonParameters>]

Description
Imports configurations from the given file.

Updates the configuration represented from the configuration Guid with the settings from the file.

Parameters
-ConfigurationGuid <Guid>
Guid of the configuration to which the settings from the file will be imported.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-FileName <string>
The name of the file that has the configuration settings to import.

Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RawConfiguration [<SwitchParameter>]
Import configuration settings from file without comparing with default settings.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
207
PowerShell cmdlets for Migrator for Notes to Exchange
 about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
The ConfigurationGuid parameter accepts input from the pipeline.

Outputs
This cmdlet returns no values upon a successful run.

Examples
PS C:\>Import-MNEConfiguration -ConfigurationGuid 69F764C9-D209-4C4D-BCCB-
6E59F615CD9D -FileName "TestName"
Imports the configuration from the file named "TestName" and updates the configuration with the given Guid with
those settings.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

208
PowerShell cmdlets for Migrator for Notes to Exchange
Import-MNEConfigurationData

Synopsis
Import configuration data from file.

Syntax
Import-MNEConfigurationData [-FileName] <string> [<CommonParameters>]

Description
Imports configuration data from the given file.

Parameters
-FileName <string>
Name of the file to import the configuration data from.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
ConfigurationData
Returns the configuration data from the file.

Examples
PS C:\>Import-MNEConfigurationData -FileName "TestName"
Imports the configuration data from the file named "TestName".

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

209
PowerShell cmdlets for Migrator for Notes to Exchange
Initialize-MNEOneDriveUserCollection

Synopsis
Preprovision mailbox user's OneDrive store in the user collection for Office 365. It is required for the user's
OneDrive store to be ready if the feature for MNE to migrate oversized attachments to OneDrive is enabled..

Syntax
Initialize-MNEOneDriveUserCollection [-CollectionName] <string> [<CommonParameters>]

Initialize-MNEOneDriveUserCollection [-CollectionName] <string> -ConfigurationId <string>

[<CommonParameters>]

Initialize-MNEOneDriveUserCollection [-CollectionName] <string> -ConfigurationFileName <string>

[<CommonParameters>]

Description
Prior to migrating the Notes mail database to Office Online, if you enable oversized attachments migration to
OneDrive store, all users in the user collection should have their OneDrive stores provisioned. This cmdlet takes
the MNE user collection name and initializes OneDrive store for each user in the user collection.

Parameters
-CollectionName <string>
Name of the user collection containing the mailbox users that have licensed OneDrive store to be
preprovisioned by the Exchange admin user.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationId <string>
Name or Guid of the existing configuration to use.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationFilename <string>
File name of a configuration settings .ini file to use as the configuration.

Required: true
Position: Named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

210
PowerShell cmdlets for Migrator for Notes to Exchange
 Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
None if successful.

Examples
PS C:\>Initialize-MNEOneDriveUserCollection "All Users"
Preprovision OneDrive store for all mailbox users in the "All Users" collection using default configuration setting.

PS C:\>Initialize-MNEOneDriveUserCollection -CollectionName "All Users" -

ConfigurationId "CDB86C40-49E2-43E1-8DE5-E1B2F4A55B51"
Preprovision OneDrive store for all mailbox users in the "All Users" collection using configuration settings by the
given configuration id.

PS C:\>Initialize-MNEOneDriveUserCollection "All Users" -ConfigurationId "Default

Settings"
Preprovision OneDrive store for all mailbox users in the "All Users" collection using configuration by the given
name.

PS C:\>Initialize-MNEOneDriveUserCollection -CollectionName "All Users" -

ConfigurationFilename "C:\defaultconfig.ini"
Preprovision OneDrive store for all mailbox users in the "All Users" collection using the configuration settings
specified in the file C:\defaultconfig.ini.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

211
PowerShell cmdlets for Migrator for Notes to Exchange
Install-MNELicense

Synopsis
Installs a license file for MNE using the given file path.

Syntax
Install-MNELicense [-Path] <string> [<CommonParameters>]

Description
Installs a license file for MNE using the given file path.

Parameters
-Path <string>
File path for the license to install.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
LicenseInfo
PSObject that contains license Type, ExpirationDate, Status, IsValid, Number, MigratedUsers, and
SeatsUsed.

Examples

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

212
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEExportObjectsToTsv

Synopsis
Exports the Directory Exporter objects in MNE to a tsv file.

Syntax
Invoke-MNEExportObjectsToTsv [-TsvFilePath] <string> [<CommonParameters>]

Description
Exports the directory exporter objects in NME to a tsv file.

Parameters
-TsvFilePath <string>
The UNC path of the tsv file to export to.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
This cmdlet accepts file path input from the pipeline.

Outputs
Nothing is returned from this cmdlet.

Examples
PS C:\>Invoke-MNEExportObjectsToTsv -TsvFilePath "C:\exampletsv.tsv"
Exports all objects to the tsv specified if it exists, otherwise creates a new tsv file.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

213
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEFindNotesDomain

Synopsis
Runs the Enumerate Notes Domains executable with the configuration in the database or user-defined values.

Syntax
Invoke-MNEFindNotesDomain [[-DominoServer] <string>] [[-UserIdFile] <string>] [[-
Password] <string>] [-WorkStation <WorkStation>] [-LogFile <string>]
[<CommonParameters>]

Description
Runs the get notes domains executable with the configuration in the database or user defined values.

Parameters
-DominoServer <string>
Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserIdFile <string>
Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Password <string>
Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

214
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNEFindNotesDomain
Runs the NME Enumerate Notes Domain task and returns the process results.

PS C:\>Invoke-MNEFindNotesDomain -DominoServer "Domino/Server"

Runs the NME Enumerate Notes Domain task with default configuration except DominoServer is set to
"Domino/Server".

PS C:\>Invoke-MNEFindNotesDomain -UserIdFile "C:\Admin-id.id"

Runs the NME Enumerate Notes Domain task with default configuration except UserIdFile is set to "C:\Admin-
id.id".

PS C:\>Invoke-MNEFindNotesDomain -Password "password"

Runs the NME Enumerate Notes Domain task with default configuration except Password is set to "password".

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

215
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEFindNotesNab

Synopsis
Runs the Enumerate Notes NABs executable with the configuration in the database or user-defined values.

Syntax
Invoke-MNEFindNotesNab [[-DominoServer] <string>] [[-UserIdFile] <string>] [[-
Password] <string>] [-WorkStation <WorkStation>] [-LogFile <string>]
[<CommonParameters>]

Description
Runs the Enumerate Notes NABs executable with the configuration in the database or user-defined values.

Parameters
-DominoServer <string>
Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserIdFile <string>
Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Password <string>
Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation this task should be ran on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

216
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNEFindNotesNab
Runs the NME Enumerate Notes Nabs task and returns the process results.

PS C:\>Invoke-MNEFindNotesNab -DominoServer "Domino/Server"

Runs the NME Enumerate Notes Nabs task with default configuration except DominoServer is set to
"Domino/Server".

PS C:\>Invoke-MNEFindNotesNab -UserIdFile "C:\Admin-id.id"

Runs the NME Enumerate Notes Nabs task with default configuration except UserIdFile is set to "C:\Admin-id.id".

PS C:\>Invoke-MNEFindNotesNab -Password "password"

Runs the NME Enumerate Notes Nabs task with default configuration except Password is set to "password".

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

217
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEGatherDesktopStatistics

Synopsis
Runs the Gather Desktop Statistics executable with the configuration in the database or user-defined values.

Syntax
Invoke-MNEGatherDesktopStatistics [[-StatisticsDirectory] <string>] [-WorkStation
<WorkStation>] [-LogFile <string>] [<CommonParameters>]

Description
Runs the Gather Desktop Statistics executable with the configuration in the database or user-defined values.

Parameters
-StatisticsDirectory <string>
The UNC path of the directory containing the SSDM statistics.

Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>
The full path of the file the application should log to. If no path is provided, log files will be created in the Log
Directory as defined in the default NME configuration.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

218
PowerShell cmdlets for Migrator for Notes to Exchange
 about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNEGatherDesktopStatistics
Runs the NME Gather Desktop Statistics enumerable.

PS C:\>Invoke-MNEGatherDesktopStatistics -StatisticsDirectory "\\elmo\C$\ssdm\" -

LogFile "C:\testlog.wlog"
Runs the NME Gather Desktop Statistics executable, looking for statistics in the "\\elmo\C$\ssdm\" folder and
creating a log file at C:\testlog.wlog.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

219
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEImportObjectsFromTsv

Synopsis
Imports the Directory Exporter objects from a tsv file.

Syntax
Invoke-MNEImportObjectsFromTsv [-TsvFilePath] <string> [<CommonParameters>]

Description
Imports the directory exporter objects from a tsv file.

Parameters
-TsvFilePath <string>
UNC path of the tsv file from which to import.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
string
This cmdlet accepts file path input from the pipeline.

Outputs
Returns done or job failed status at the end of the run.

Examples
PS C:\>Invoke-MNEImportObjectsFromTsv -TsvFilePath "C:\exampletsv.tsv"
Imports all objects from the tsv file.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

220
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNELocateNotesDataStore

Synopsis
Runs the Enumerate Data executable with the configuration in the database or user-defined values.

Syntax
Invoke-MNELocateNotesDataStore [-UserCollection] <string> [[-UserIdFile] <string>]
[[-Password] <string>] -ConfigurationId <string> [-WorkStation <WorkStation>] [-
LogFile <string>] [<CommonParameters>]

Invoke-MNELocateNotesDataStore [-UserCollection] <string> [[-UserIdFile] <string>]

[[-Password] <string>] [-LocateNew <NotesUpdateModeTypeEnum>] [-LocateMailFiles
<LocateDatastoresFindByEnum>] [-LocatePabs <LocateDatastoresFindByEnum>] [-
LocateArchives <LocateDatastoresFindByEnum>] [-MailFileDir <string>] [-PabDir
<string>] [-PabReplicaServer <string>] [-ArchiveDir <string>] [-ArchiveReplicaServer
<string>] [-AclIgnoreList <string>] [-OwnerByAcl] [-WorkStation <WorkStation>] [-
LogFile <string>] [<CommonParameters>]

Description
Scans the Notes environment for all data stores associated with a designated user collection.

Parameters
-UserCollection <string>
Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserIdFile <string>
Required: false
Position: 1
Default value:in default settings
Accept pipeline input:false
Accept wildcard characters:false

-Password <string>
Required: false
Position: 2
Default value:in default settings
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationId <string>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

221
PowerShell cmdlets for Migrator for Notes to Exchange
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LocateNew <NotesUpdateModeTypeEnum>
Required: false
Position: Named
Default value:.Append
Accept pipeline input:false
Accept wildcard characters:false

-LocateMailFiles <LocateDatastoresFindByEnum>
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LocatePabs <LocateDatastoresFindByEnum>
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LocateArchives <LocateDatastoresFindByEnum>
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailFileDir <string>
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabDir <string>
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicaServer <string>
Required: false
Position: Named
Default value:in default config
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveDir <string>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

222
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveReplicaServer <string>
Required: false
Position: Named
Default value:in default config
Accept pipeline input:false
Accept wildcard characters:false

-AclIgnoreList <string>
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-OwnerByAcl [<SwitchParameter>]
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>
The full path of the file the application should log to. If no path is provided, log files will be created in the Log
Directory as defined in the default MNE configuration.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
223
PowerShell cmdlets for Migrator for Notes to Exchange
 This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNELocateNotesDataStore "All Users" -ConfigurationId "8846d710-03df-
4c51-ab51-4fe738526a78"
Creates and runs the NME Locate Notes Datastores Task and returns the process results on collection "All Users"
with settings from Configuration with guid "8846d710-03df-4c51-ab51-4fe738526a78".

PS C:\>Invoke-MNELocateNotesDataStore "All Users" "C:\admin.id" "pa55w0rd" -

LocateMailFiles Nab
Creates and runs a NME Locate Notes Datastores Task and returns the process results on collection "All Users"
and logging in with UserIdFile "C:\admin.id" and password "pa55w0rd" that updates the mail files with thoes
located on the domino server.

PS C:\>Invoke-MNELocateNotesDataStore "All Users" -LocateNew Append -LocatePabs

Replica -PabReplicaServer "Domino/Server" -PabDir "Pab"
Creates and runs a NME Locate Notes Datastores Task and returns the process results on collection "All Users"
that finds new Pabs on server "Domino/Server" in directory "Pab" and adds them to the database.

PS C:\>Invoke-MNELocateNotesDataStore "All Users" -LocateNew ReplaceAll -

LocateArchives Scan -ArchiveDir "Domino/Server!!Archives" -OwnerByAcl -AclIgnoreList
"admin,owner"
Creates and runs a NME Locate Notes Datastores Task and returns the process results on collection "All Users"
that finds new Archivess on server "Domino/Server" in directory "Archives" and Replaces all in database with the
located files.
Also attempts to find owners for all data without an owner and Ignoring users "admin" and "owner."

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

224
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEMigrateUserData

Synopsis
Runs the Migrate User Data application with a specified configuration.

Syntax
Invoke-MNEMigrateUserData [-UserCollectionId] <string> -ConfigurationId <string> [-
MaxMigrationThreads <Integer>] [-WorkStation <WorkStation>] [-LogFile <string>] [-
ShowProgressDialog] [-ProgressDialogIsTopmost] [-ManuallyCloseProgressDialog]
[<CommonParameters>]

Invoke-MNEMigrateUserData [-UserCollectionId] <string> -ConfigurationFilename

<string> [-RawConfiguration] [-MaxMigrationThreads <Integer>] [-WorkStation
<WorkStation>] [-LogFile <string>] [-ShowProgressDialog] [-ProgressDialogIsTopmost]
[-ManuallyCloseProgressDialog] [<CommonParameters>]

Description
Runs the Migrate User Data application with a specified configuration.

Parameters
-UserCollectionId <string>
Name or GUID of the user collection to migrate data from.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationId <string>
Name or Guid of the existing configuration to use for this migration.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationFilename <string>
Filename of a configuration settings .ini file to use as the configuration for this migration.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
225
PowerShell cmdlets for Migrator for Notes to Exchange
 -RawConfiguration [<SwitchParameter>]
Switch parameter that, if used with FileName, means this is a differential file and will save it to database as
differential file.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxMigrationThreads <Integer>
Maximum amount of migration threads to run at once.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>
File to log the results to. If specified, this is used, otherwise a default value is used.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ShowProgressDialog [<SwitchParameter>]
Switch parameter that, if used, will display the task progress along with key migration statistics within a pop-up
dialog.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ProgressDialogIsTopmost [<SwitchParameter>]
Switch parameter that, when used with the ShowProgressDialog parameter, will cause the progress dialog to
be displayed on top of all other windows that are not topmost windows.

Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

226
PowerShell cmdlets for Migrator for Notes to Exchange
 Accept pipeline input:false
Accept wildcard characters:false

-ManuallyCloseProgressDialog [<SwitchParameter>]
Switch parameter that, when used with the ShowProgressDialog parameter, will cause the progress dialog to
remain open after the migration task has completed until the progress dialog is manually closed. The invoke
cmdlet will not terminate until the progress dialog has been closed.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNEMigrateUserData -UserCollectionId "All Users" -ConfigurationId
"CDB86C40-49E2-43E1-8DE5-E1B2F4A55B51"
Runs the MNE User Data Migrator with the "All Users" collection and the configuration with the GUID identifier
"CDB86C40-49E2-43E1-8DE5-E1B2F4A55B51". Returns the process results.

PS C:\>Invoke-MNEMigrateUserData -UserCollectionId "All Users" -ConfigurationId

"User Migration Template"
Runs the MNE User Data Migrator with the "All Users" collection and the configuration with the name "User
Migration Template". Returns the process results.

PS C:\>Invoke-MNEMigrateUserData -UserCollectionId "All Users" -ConfigurationId

"User Migration Template" -MaxMigrationThreads 4
Runs the MNE User Data Migrator with the specified user collection and configuration using 4 migration threads.
Returns the process results.

PS C:\>Invoke-MNEMigrateUserData -UserCollectionId "All Users" -ConfigurationId

"User Migration Template" -LogFile "C:\Log.wlog"
Runs the MNE User Data Migrator with the specified user collection and configuration, and logs the task to the
specified log file. Returns the process results.

PS C:\>Invoke-MNEMigrateUserData -UserCollectionId "All Users" -

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

227
PowerShell cmdlets for Migrator for Notes to Exchange
ConfigurationFilename "C:\defaultconfig.ini"
Runs the MNE User Data Migrator with "All Users" collection and uses the configuration settings specified in
C:\defaultconfig.ini. Returns the process results.

PS C:\>Invoke-MNEMigrateUserData -UserCollectionId "All Users" -

ConfigurationFilename "C:\defaultconfig.ini" -ShowProgressDialog -
ProgressDialogIsTopmost -ManuallyCloseProgressDialog
Runs the MNE User Data Migrator with "All Users" collection and uses the configuration settings specified in
C:\defaultconfig.ini. Returns the process results.

While the migration task is running, a progress dialog will be displayed indicating the task progress along with key
migration statistics. The progress dialog will be displayed on top of other windows and will remain open after the
task has completed until the progress dialog is manually closed.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

228
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNENotesDirectoryExport

Synopsis
Runs the Directory Exporter executable with the configuration in the database or user defined values.

Syntax
Invoke-MNENotesDirectoryExport [[-DominoServer] <string>] [[-UserIdFile] <string>]
[[-Password] <string>] [-WorkStation <WorkStation>] [-LogFile <string>]
[<CommonParameters>]

Description
Runs the get notes directory exporter executable with the configuration in the database or user defined values.

Parameters
-DominoServer <string>
Name of the Domino server to export directory from.

Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserIdFile <string>
Location of the user ID file to log into the domino server.

Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Password <string>
The password to access the Domino server.

Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
229
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>
File to log the results to. If specified, this is used, otherwise a default value is used.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNENotesDirectoryExport
Runs the MNE Directory Exporter task and returns the process results.

PS C:\>Invoke-MNENotesDirectoryExport -DominoServer "Domino/Server"

Runs the MNE Directory Exporter task with default configuration except DominoServer is set to "Domino/Server".

PS C:\>Invoke-MNENotesDirectoryExport -UserIdFile "C:\Admin-id.id"

Runs the MNE Directory Exporter task with default configuration except UserIdFile is set to "C:\Admin-id.id".

PS C:\>Invoke-MNENotesDirectoryExport -Password "password"

Runs the MNE Directory Exporter task with default configuration except Password is set to "password".

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

230
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEProvisionGroupCollection

Synopsis
Runs the Provision Group Collection executable with the configuration in the database or user-defined values.

Syntax
Invoke-MNEProvisionGroupCollection [-GroupCollection] <string> [-GroupContainer
<string>] [-ContactContainer <string>] [-AddNotFoundContacts] [-KeepGroupsInSync]
[-SwitchToSecurityGroup] [-WorkStation <WorkStation>] [-LogFile <string>]
[<CommonParameters>]

Invoke-MNEProvisionGroupCollection [-GroupCollection] <string> -ConfigurationId

<string> [-WorkStation <WorkStation>] [-LogFile <string>] [<CommonParameters>]

Invoke-MNEProvisionGroupCollection [-GroupCollection] <string> -

ConfigurationFilename <string> [-WorkStation <WorkStation>] [-LogFile <string>]
[<CommonParameters>]

Description
Runs the provision group collection application with a specified configuration or user defined values.

Parameters
-GroupCollection <string>
Guid or name of the group collection to provision.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationId <string>
Name or Guid of the existing configuration to be used for this task.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationFilename <string>
Path to the configuration settings .ini file to be used for this task.

Required: true
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

231
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

-GroupContainer <string>
Path to existing organizational unit for distribution groups.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ContactContainer <string>
Path to existing organizational unit for creating external members for distribution groups.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AddNotFoundContacts [<SwitchParameter>]
Switch parameter that, if used, will add contacts not found in Active Directory to AD.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-KeepGroupsInSync [<SwitchParameter>]
Switch parameter that, if used, will keep the provisioned group in sync with the Notes group.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SwitchToSecurityGroup [<SwitchParameter>]
Switch parameter that, if used, will provision the new group as a security group instead of a distribution
list.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

232
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>
Logfile to which the results will be logged. Uses a default file if parameter is not specified.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNEProvisionGroupCollection -GroupCollection "All Groups" -LogFile
"C:\Log.txt"
Runs the NME Provision Group Collection task, logs to Log.txt on the C: drive, and returns the status.

PS C:\>Invoke-MNEProvisionGroupCollection -GroupCollection "All Groups" -

ConfigurationId "Default Settings" -LogFile "C:\Log.txt"
Runs the MNE Provision Group Collection task with "All Groups" collection and the specified configuration name
or GUID, and returns the status.

PS C:\>Invoke-MNEProvisionGroupCollection -GroupCollection "All Groups" -

ConfigurationFilename "C:\defaultconfig.ini" -LogFile "C:\Log.txt"
Runs the MNE Provision Group Collection task with "All Groups" collection and the configuration settings specified
in C:\defaultconfig.ini.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

233
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNEProvisionUserCollection

Synopsis
Runs the Provision User Collection application with a specified configuration or user-defined values.

Syntax
Invoke-MNEProvisionUserCollection [-UserCollection] <string> -DatabaseColumn
<DbColumn> -AdAttribute <ActiveDirectoryAttribute> [-
CreateNonExistingUsersFromContacts] [-UserContainer <string>] [-WorkStation
<WorkStation>] [-LogFile <string>] [<CommonParameters>]

Invoke-MNEProvisionUserCollection [-UserCollection] <string> -ConfigurationId

<string> [-WorkStation <WorkStation>] [-LogFile <string>] [<CommonParameters>]

Invoke-MNEProvisionUserCollection [-UserCollection] <string> -ConfigurationFilename

<string> [-WorkStation <WorkStation>] [-LogFile <string>] [<CommonParameters>]

Description
Runs the Provision User Collection application with a specified configuration or user-defined values.

Parameters
-UserCollection <string>
GUID or name of the user collection to provision.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DatabaseColumn <string>
Database colummn to match to the selected active directory attribute (AdAttribute).
Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdAttribute <string>
Active Directory attribute to match to the selected database colummn (DatabaseColumn).
Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

234
PowerShell cmdlets for Migrator for Notes to Exchange
 -ConfigurationId <string>
Name or Guid of the existing configuration to be used for this task.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationFilename <string>
Path to the configuration settings .ini file to be used for this task.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CreateNonExistingUsersFromContacts [<SwitchParameter>]
Switch parameter that, if used, will add users not currently in Active Directory to the AD.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserContainer <string>
Relative domain name path to an existing organizational unit for creating user object, must be specified if
CreateNonExistingUsers switch is on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogFile <string>
The file to which results will be logged. Uses a default value if parameter is not specified.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

235
PowerShell cmdlets for Migrator for Notes to Exchange
 <CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNEProvisionUserCollection -UserCollection "All Users" -DatabaseColumn
"GivenName" -AdAttribute "mailNickname" -LogFile "C:\Log.txt"
Runs the MNE Provision User Collection task with user-defined values and returns the status.

PS C:\>Invoke-MNEProvisionUserCollection -UserCollection "All Users" -DatabaseColumn

"GivenName" -AdAttribute "mailNickname" -CreateNonExistingUsers -UserContainer
"OU=Target Organization" -LogFile "C:\Log.txt"
Runs the MNE Provision User Collection task with user-defined values and create users in specified organizational
unit (relative domain name path to an existing organizational unit) if not exist and returns the status.

PS C:\>Invoke-MNEProvisionUserCollection -UserCollection "All Users" -

ConfigurationId "Default Settings" -LogFile "C:\Log.txt"
Runs the MNE Provision User Collection task with "All Users" collection and the specified configuration name or
GUID, and returns the status.

PS C:\>Invoke-MNEProvisionUserCollection -UserCollection "All Users" -

ConfigurationFilename "C:\defaultconfig.ini" -LogFile "C:\Log.txt"
Runs the MNE Provision User Collection task with "All Users" collection and the configuration settings specified in
C:\defaultconfig.ini.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

236
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNESendPabReplicator

Synopsis
Sends PABs to all collection members

Syntax
Invoke-MNESendPabReplicator -CollectionName <string> -ConfigurationGuid <Guid> [-
WorkStation <WorkStation>] [-LogFile <string>] [<CommonParameters>]

Invoke-MNESendPabReplicator [[-DominoServer] <string>] [[-UserIdFile] <string>] [[-

Password] <string>] -CollectionName <string> [-TargetServer <string>] [-TargetDir
<string>] [-MessageSubject <string>] [-MessageFrom <string>] [-WorkStation
<WorkStation>] [-LogFile <string>] [<CommonParameters>]

Description
Sends Pabs to all collection members.

Parameters
-DominoServer <string>
Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserIdFile <string>
Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Password <string>
Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CollectionName <string>
Name of the collection to send the Pabs to.

Required: true
Position: Named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

237
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-ConfigurationGuid <Guid>
Guid of the configuration for the cmdlet.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetServer <string>
Target Domino Server.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetDir <string>
Target Destination Directory.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MessageSubject <string>
Subject for the message.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MessageFrom <string>
Mark the message as sent from this user.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WorkStation <WorkStation>
The WorkStation to run this task on.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

238
PowerShell cmdlets for Migrator for Notes to Exchange
 -LogFile <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
TaskRunInfo
Returns a TaskRunInfo object that contains information regarding the invoked task.

Examples
PS C:\>Invoke-MNESendPabReplicator -CollectionName "All Users" -ConfigurationGuid
e6a70f5e-e0d3-4692-a5ad-08b541ace006
Sends the PABs using all the settings from the configuration.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

239
PowerShell cmdlets for Migrator for Notes to Exchange
Invoke-MNESSDM

Synopsis
Runs the Self Service Desktop Migrator (SSDM) executable with the configuration in the database or user-defined
values.

Syntax
Invoke-MNESSDM -TargetProfile <string> [-NotesUserIdPath <string>] [-NotesPassword
<string>] [-TargetPassword <string>] [-TargetUser <string>] [-TargetServer
<string>] [-TargetDomain <string>] [-DontMigrateMailFile] [-DontMigrateArchive] [-
DontMigrateAddressBook] [-AddressBookFilePath <string>] [-MailFilePath <string>] [-
MailArchivePath <string>] [<CommonParameters>]

Description
Runs the self service desktop manager executable with the configuration in the database or user defined values.

Parameters
-TargetProfile <string>
Name of the outlook profile to migrate to.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesUserIdPath <string>
Full path to the Notes user id file.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesPassword <string>
Password for the notes user.

Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetPassword <string>
Password for the outlook profile.
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
240
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetUser <string>
Username of the AD user to attach to.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetServer <string>
Active Directory server to attach to.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetDomain <string>
Active Directory Domain to attach to.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DontMigrateMailFile [<SwitchParameter>]
Changes the ini to exclude the migration of mail files.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DontMigrateArchive [<SwitchParameter>]
Changes the ini to exclude the migration of mail archives.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DontMigrateAddressBook [<SwitchParameter>]
Changes the ini to exclude the migration of address books.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

241
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AddressBookFilePath <string>
Full path to the address book file.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailFilePath <string>
Full path to the mail file.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailArchivePath <string>
Full path to the mail archive file.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Returns done or job failed status at the end of the run.

Examples
PS C:\>Invoke-MNESSDM -TargetProfile "Outlook"
Runs the MNE SSDM and returns the status.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

242
PowerShell cmdlets for Migrator for Notes to Exchange
PS C:\>Invoke-MNESSDM -TargetProfile "Outlook" -DontMigrateMailFile
Runs the MNE SSDM without migrating the mail file, and returns the status.

PS C:\>Invoke-MNESSDM -TargetProfile "Outlook" -NotesUserIdPath "C:\oscar.id" -

NotesPassword "password"
Sets the id file, then runs the MNE SSDM and returns the status.

PS C:\>Invoke-MNESSDM -TargetProfile "Outlook" -TargetPassword "Alt0ids" -Targetuser

"migadmin"
Sets the target user's name and password then runs the MNE SSDM and returns the status.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

243
PowerShell cmdlets for Migrator for Notes to Exchange
New-MNEConfiguration

Synopsis
Creates and saves a new configuration to the database.

Syntax
New-MNEConfiguration [-Name] <string> [[-Type] <ConfigurationTypeEnum>] [[-
Description] <string>] [<CommonParameters>]

New-MNEConfiguration [-Name] <string> [[-Type] <ConfigurationTypeEnum>] [[-

Description] <string>] -MakeTemplate [-TemplateType] [<CommonParameters>]

Description
Creates a new configuration or configuration template with a user-specified name, type, and description, and/or
and saves it to the database.

Parameters
-Name <string>
Name of the new configuration to create. Name automatically appends the current date/time to the end.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Type <ConfigurationTypeEnum>
Type of configuration to create.

Required: false
Position: 1
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Description <string>
Description for the configuration.

Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MakeTemplate [<SwitchParameter>]
Converts configuration into a template configuration.
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
244
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TemplateType <TemplateTypeEnum>
Convert the Template Configuation to Full Template or Differential Template.

Required: false
Position: Named
Default value:.Full
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.String
Name of the new configuration to create.

ConfigurationTypeEnum
Type of configuration to create.

Outputs
NMEConfiguration
Outputs the created configuration.

Examples
PS C:\>New-MNEConfiguration -Name "NewConfiguration"
Creates a new configuration with the name "NewConfiguration" plus the current date/time.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

245
PowerShell cmdlets for Migrator for Notes to Exchange
New-MNEDirectoryExportConfiguration

Synopsis
Creates a new configuration of the type for Directory Export.

Syntax
New-MNEDirectoryExportConfiguration -Name <string> [<CommonParameters>]

Description
Creates and saves a new configuration of type ConfigurationTypeEnum.DirExport, with name specified by the
user.

Outputs the created configuration.

Parameters
-Name <string>
Name of the configuration to create.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
Configuration
Outputs the newly created configuration.

Examples
PS C:\>New-MNEDirectoryExportConfiguration -Name "NewConfiguration"
Creates a new configuration with the given name and of type ConfigurationTypeEnum.DirExport.
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
246
PowerShell cmdlets for Migrator for Notes to Exchange
Remove-MNECollectionMember

Synopsis
Removes a member object to the specifies collection.

Syntax
Remove-MNECollectionMember [-CollectionGuid] <Guid> [-ObjectSmtpAddress] <string>
[<CommonParameters>]

Remove-MNECollectionMember [-CollectionGuid] <Guid> -ObjectGuid <Guid>

[<CommonParameters>]

Remove-MNECollectionMember [-CollectionGuid] <Guid> -CollectionMember

<CollectionMember> [<CommonParameters>]

Description
Removes a specified object (either selected by GUID, SMTP address, or passed in) to the specified collection (by
GUID).
Validates whether there is an object GUID, SMTP address, or a CollectionMember are given in the input.

Parameters
-CollectionGuid <Guid>
The Guid of the collection to removed the member from.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-ObjectSmtpAddress <string>
The SMTP address of the object to be removed from the collection.

Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ObjectGuid <Guid>
The Guid of the object to be removed from the collection.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
247
PowerShell cmdlets for Migrator for Notes to Exchange
 Accept wildcard characters:false

-CollectionMember <CollectionMember>
The CollectionMember to be removed from the collection.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
The parameter CollectionGuid accepts pipeline input.

Outputs
QuestSoftware.NMEAPI.Controllers.NMECollection
Returns the collection that was removed from, if there are no errors.

Examples
PS C:\>Remove-MNECollectionMember -CollectionGuid 455E1829-45D1-4485-8467-
80A463DA5227 -ObjectGuid DA096D83-A07D-44F6-A0D2-35B88A10F6A5
Removes the object with the given Guid from the collection with the given Guid.

PS C:\>Remove-MNECollectionMember -CollectionGuid 455E1829-45D1-4485-8467-

80A463DA5227 -ObjectSmtpAddress Admin@Sample.test.com
Removes the object with the given Smtp address from the collection with the given Guid.

PS C:\>$members = Get-MNECollectionMember -CollectionGuid 789E1829-45D1-4485-8467-

80A463DA5227Remove-MNECollectionMember -CollectionGuid 455E1829-45D1-4485-8467-
80A463DA5227 -CollectionMember $members
Adds all the members from the first collection to the second collection.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

248
PowerShell cmdlets for Migrator for Notes to Exchange
Remove-MNEMailboxAdminPermission

Synopsis
Remove the MNE admin user Full Access permission to mailboxes in the user collection for Office 365. If Admin
Account Pool is used, the Office365 admin role specified by the configuration will be used instead of the MNE
admin user.

Syntax
Remove-MNEMailboxAdminPermission [-CollectionName] <string> [<CommonParameters>]

Remove-MNEMailboxAdminPermission [-CollectionName] <string> -ConfigurationId

<string> [<CommonParameters>]

Remove-MNEMailboxAdminPermission [-CollectionName] <string> -ConfigurationFileName

<string> [<CommonParameters>]

Description
The admin user must be granted Full Access permission to mailboxes in the user collection prior to migration. After
completion of the migration, use this cmdlet to revoke admin user Full Access permission to the mailboxes in the
user collection. This cmdlet takes the user collection name and revokes the Full Access permission of the admin
user.

Parameters
-CollectionName <string>
Name of the user collection containing the mailboxes granted Full Access permission to Exchange admin
user.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationId <string>
Name or Guid of the existing configuration to use.

Required: true
Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConfigurationFileName <string>
File name of a configuration settings .ini file to use as the configuration.

Required: true
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
249
PowerShell cmdlets for Migrator for Notes to Exchange
 Position: Named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
QuestSoftware.NME.PSModule.Utils.ManageMailboxPermissionResult
Returns a ManageMailboxPermissionResult object that contains information regarding the result of this
cmdlet.

Examples
PS C:\>Remove-MNEMailboxAdminPermission "All Users"
Revokes the MNE admin user Full Access permission to mailboxes in the "All Users" collection using default
configuration setting and returns the results.

PS C:\>Remove-MNEMailboxAdminPermission -CollectionName "All Users"

Revokes the MNE admin user Full Access permission to mailboxes in the "All Users" collection using default
configuration settings and returns the results.

PS C:\>Remove-MNEMailboxAdminPermission "All Users" -ConfigurationId "CDB86C40-49E2-

43E1-8DE5-E1B2F4A55B51"
Revokes the MNE admin user Full Access permission to mailboxes in the "All Users" collection using configuration
settings by the given configuration id and returns the results.

PS C:\>Remove-MNEMailboxAdminPermission "All Users" -ConfigurationId "Default

Settings"
Revokes the MNE admin user Full Access permission to mailboxes in the "All Users" collection using configuration
by the given name and returns the results.

PS C:\>Remove-MNEMailboxAdminPermission -CollectionName "All Users" -

ConfigurationFilename "C:\defaultconfig.ini"
Revokes MNE admin user Full Access permission to mailboxes in the "All Users" collection using the configuration
settings specified in the file C:\defaultconfig.ini.

PS C:\>Remove-MNEMailboxAdminPermission "All Users" | ForEach-Object -MemberName

"Mailboxes"
Removes MNE admin user Full Access permission to mailboxes in the "All Users" collection using default
configuration settings and returns a list of mailboxes that were processed.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

250
PowerShell cmdlets for Migrator for Notes to Exchange
Set-MNEConfiguration

Synopsis
Allows you to set absolutely everything in the configuration.

Syntax
Set-MNEConfiguration [-ConfigurationFromPipeline] <Configuration> [-Section]
<string> [-Key] <string> [[-Value] <string>] [<CommonParameters>]

Set-MNEConfiguration [-ConfigurationFromPipeline] <Configuration> [-AclIgnore

<string>] [-AclIgnoreCount <Int32>] [-AclRootVisibleOnly <Boolean>] [-Acls
<Boolean>] [-ActiveDirectoryAlwaysUseDefaults <Boolean>] [-ActiveDirectoryGroupType
<ActiveDirectoryGroupTypeEnum>] [-ActiveDirectoryHost <string>] [-
ActiveDirectoryPassword <string>] [-ActiveDirectoryUserId <string>] [-Ad2AdAttribute
<string>] [-Ad2OpenFlags <AuthenticationTypes>] [-Ad2UserFilter <string>] [-
AdAttribute <string>] [-AddFullAccessPermission <Boolean>] [-AddressListName
<string>] [-AddressPolicyName <string>] [-AdjustTaskReminderToMidnight <Boolean>] [-
AdminDomain <string>] [-AdminMailbox <string>] [-AdminPassword <string>] [-
AdminProfile <string>] [-AdminUsername <string>] [-AllowForwardToNotesConnector
<Boolean>] [-AllowHtmlCalendarBodies <Boolean>] [-AllowNotesForeignDirSync
<Boolean>] [-AllowSelfSignedCerts <Boolean>] [-AltAddressAttribute <string>] [-
AlwaysDoForwarding <Int32>] [-AlwaysRmvForwarding <Boolean>] [-AlwaysUseDefaults
<Boolean>] [-AlwaysUseOldAlias <Boolean>] [-AlwaysUseOldExchDn <Boolean>] [-
AppDoesArch <Boolean>] [-AppDoesEncrypted <Boolean>] [-AppDoesMail <Boolean>] [-
AppDoesPabs <Boolean>] [-AppendSmtpAddressToContactsDisplayName <Boolean>] [-
AppointmentForms <string>] [-AppointmentLocationSource <Int16>] [-
ArchiveDesignClass <string>] [-ArchiveDest <GeneralDestinationTypeEnum>] [-
ArchiveDestServerArchive <Boolean>] [-ArchiveDir <string>] [-ArchiveReplicaDir
<string>] [-ArchiveReplicaServer <string>] [-ArchiveResolveAttendees <Boolean>] [-
AskArchiveDest <Boolean>] [-AskFilter <Boolean>] [-AskPabDest <Boolean>] [-
AskServerMailDest <Boolean>] [-AttachmentFilteredBySizeMsg <string>] [-
AttachmentLostDueToEncryptionMsg <string>] [-Attribute <string>] [-AuthMechanismType
<AuthenticationMechanismTypeEnum>] [-AutodiscoverDisableMapiHttp <Boolean>] [-
AutodiscoverEnableScpLookup <Boolean>] [-AutodiscoverMaxHops <Integer>] [-
AutodiscoverPreferInternalRpcHttpUrl <Boolean>] [-AutodiscoverPreferInternalUrl
<Nullable<Boolean>>] [-AutodiscoverUrl <string>] [-BodyLostDueToEncryptionMsg
<string>] [-CalMaxRecurrenceFixType <CalMaxRecurrenceFixTypeEnum>] [-
CanAddGroupMembers <Boolean>] [-CanDeleteGroupMembers <Boolean>] [-CentralLogDir
<string>] [-CentralLogLevel <Int32>] [-CmnExcludeFromDirSync <string>] [-
CompressLogFile <Boolean>] [-ContactFilter <string>] [-ContactsName <string>] [-
CreateFwdAddrInAd <Boolean>] [-CreateGroupDelay <Int32>] [-CreateMailBox <Boolean>]
[-CreateMailboxDelay <Int32>] [-CurArchiveDir <string>] [-CurMailFileDir <string>]
[-DateFilterUsingFormula <Boolean>] [-DeclineFolderCheck <Boolean>] [-
DeleteAutoCompleteMessages <Boolean>] [-DeleteMailDomain <Boolean>] [-
DisableCredentialScanner <Boolean>] [-DisableDialogScanner <Boolean>] [-
DisableModernAuthentication <Boolean>] [-DisableDirSync <Boolean>] [-DoAuditLog
<Boolean>] [-DocLinksDefaultServer <string>] [-DocLinksFastLookupOnly <Boolean>] [-
DocLinksHttpPort <Int32>] [-DoHtmlBody <Boolean>] [-DoMailRouting <Boolean>] [-
Domain <string>] [-DomainController <string>] [-DominoDomain <string>] [-DoNeedAdsi
<Boolean>] [-DoNeedCdoexm <Boolean>] [-DoNotesMailRouting <Boolean>] [-

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

251
PowerShell cmdlets for Migrator for Notes to Exchange
DoRmvForwarding <Boolean>] [-DoSetCalDomain <Boolean>] [-DoSetExcalconServer
<Boolean>] [-DoSetForwarding <Boolean>] [-DoSetMailDomain <Boolean>] [-
DoSetMailSystem <Boolean>] [-DoSetNotesFormatPreference <Boolean>] [-
DoShowRmvForwarding <Boolean>] [-DoShowSetForwarding <Boolean>] [-DoSourceAdmin
<Boolean>] [-DoTargetAdmin <Boolean>] [-DoVisibility <Boolean>] [-DoX500Proxy
<Boolean>] [-EmailAddressPolicyEnabled <Boolean>] [-EnableArchiveMailbox <Boolean>]
[-EnableUsers <Boolean>] [-EncryptedMailOnly <Boolean>] [-EndUserDir <string>] [-
EndUserStatsDir <string>] [-ExcalconServer <string>] [-ExchangeServer <string>] [-
ExcludeDominoDomainFromFwdAddrInAD <Boolean>] [-FileAsFormat <string>] [-
FindArchivesBy <string>] [-FindMailFilesBy <string>] [-FindPabsBy <string>] [-
ForceAddrBooks <Boolean>] [-ForceAddress <Boolean>] [-ForceOldNxRtfDll <Boolean>]
[-ForceTargetAdmin <Boolean>] [-ForwardingAddress <string>] [-ForwardingDomain
<string>] [-ForwardingMethod <Int32>] [-FwdAddrDelim <string>] [-FwdAttrField
<string>] [-FwdCalDomain <string>] [-FwdMailDomain <string>] [-
GroupContactsContainer <string>] [-GroupFilter <string>] [-GroupsContainer <string>]
[-GroupsSearchFilter <string>] [-HomeMailBoxStore <string>] [-HomeServer <string>]
[-HtmlDocLinks <Int32>] [-IgnoreAcls <string>] [-IgnoreForms <IList`1[String]>] [-
IncludeServerMailFile <Boolean>] [-JournalEntryMessageType
<NotesJournalEntryMessageTypeEnum>] [-LoadMethod <string>] [-LocateArchives
<Boolean>] [-LocateMailFiles <Boolean>] [-LocateNew <Boolean>] [-LocatePabs
<Boolean>] [-LogDir <string>] [-LogLevel <Int32>] [-LookupDisplayNames <Boolean>]
[-MailDesignClass <string>] [-MailEnableAttempts <Int32>] [-
MailEnableRetryWaitSeconds <Int32>] [-MailFileDir <string>] [-MailSystem
<MailSystemTypeEnum>] [-MailTarget <MailTargetTypeEnum>] [-MapiAdminProfile
<string>] [-MapiRecipient <MapiRecipientActionEnum>] [-MapiRetryCount <Int32>] [-
MapiUseSharedProfile <Boolean>] [-MapPrivateAsPublic <Boolean>] [-
MaxExceptionsPerMessage <Int32>] [-MaxExtractedImageArea <Int32>] [-MaxFolderCache
<Int32>] [-MaxLargePstSize <Int32>] [-MaxMailboxConnectionRetryWaitTime <Int32>] [-
MaxPstSize <Int32>] [-MaxSessionReconnectCount <Int32>] [-MBoxFromContact
<Boolean>] [-MemoForms <string>] [-MergeAddressBookFolder <string>] [-
MergeAddressBooks <Boolean>] [-MergeContactAttribWins <Boolean>] [-
MergeContactIsAuthoritative <Boolean>] [-MergeCrossCheckObjs <Boolean>] [-
MergeFindBySmtp <Boolean>] [-MergeGrpMembership <Boolean>] [-MergeReqImportedFrom
<Boolean>] [-MergeReqProxyAddress <Boolean>] [-MergeSyncObjRequired <Boolean>] [-
MergeX500 <Boolean>] [-MessageRetryCount <Int32>] [-MessageRetryWait <Int32>] [-
Migrate <Boolean>] [-MigrateAppointmentResponses <Boolean>] [-MigrateArchives
<Boolean>] [-MigrateConflictDocs <Boolean>] [-MigrateEmptyFolders <Boolean>] [-
MigrateMailOrCalendar <Boolean>] [-MigrateMailUsingServer <Boolean>] [-
MigrateOrphanedDocs <Boolean>] [-MigratePab <Boolean>] [-
MigrateRecurringBeforeRange <Boolean>] [-MigrateReservationsAlways <Boolean>] [-
MigrateServerMail <Boolean>] [-MigForwarding <Boolean>] [-
MimeIgnoreBoundaryWhitespace <Boolean>] [-MinSpace <Int32>] [-MsgRequireAnyFeature
<MsgRequireAnyFeatureTypeEnum>] [-NabCount <Int32>] [-NabReaderGroup <string>] [-
NeedLoginInfo <Boolean>] [-NoServer <Boolean>] [-NotesAlwaysDoForwarding <Int16>] [-
NotesAlwaysRmvForwarding <Boolean>] [-NotesAlwaysUseDefaults <Boolean>] [-
NotesDoRmvForwarding <Boolean>] [-NotesDoSetForwarding <Boolean>] [-
NotesDoShowRmvForwarding <Boolean>] [-NotesDoShowSetForwarding <Boolean>] [-
NotesEncryptedMailOnly <Boolean>] [-NotesFormatPreference
<NotesFormatPreferenceTypeEnum>] [-NotesForwardingDomain <string>] [-
NotesFwdAddrDelim <string>] [-NotesFwdAttrField <string>] [-NotesIniPath <string>]
[-NotesPassword <string>] [-NotesPreferredNab <string>] [-NotesServer <string>] [-
NotesUserIdFile <string>] [-NoticeForms <string>] [-O365Environment <string>] [-
O365MaxMailboxConnectionWaitTime <Int32>] [-O365PSConnectionUri <string>] [-Offline
<Boolean>] [-OpenFlags <AuthenticationTypes>] [-OrphanedDocsFolder <string>] [-
OwnerByAcl <Boolean>] [-PabDesignClass <string>] [-PabDest

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

252
PowerShell cmdlets for Migrator for Notes to Exchange
<GeneralDestinationTypeEnum>] [-PabDestServerArchive <Boolean>] [-PabDir <string>]
[-PabGroupForms <string>] [-PabPersonForm <string>] [-PabReplicaDir <string>] [-
PabReplicaServer <string>] [-PabReplicatorFrom <string>] [-PabReplicatorSign
<Boolean>] [-PabReplicatorSubject <string>] [-PabReplicatorTargetDir <string>] [-
PabReplicatorTargetServer <string>] [-PabRequiredAttrs <IList`1[String]>] [-
PabsInMailFile <Boolean>] [-Pass2Delay <Int32>] [-PostLogs <Boolean>] [-
PowerShellXmlErrorFile <string>] [-ProvisionUsers <Boolean>] [-PsRetryAttempts
<Int32>] [-PsRetryWait <Int32>] [-PstDirMode <OutlookPstDirectoryModeEnum>] [-
PstFileName <string>] [-PstFileNameFormat <OutlookPstFileNameFormatEnum>] [-
PstRootDir <string>] [-PublicDelegates <Boolean>] [-PurgePabs <Boolean>] [-
QuotaMode <NotesQuotaModeTypeEnum>] [-QuoteNonAsciiCharsInRtf <Boolean>] [-
RemigrateMode <Int32>] [-RemoveDirSyncAttribute <Boolean>] [-RemoveSrcAddresses
<Boolean>] [-ReportErrors <Boolean>] [-ReportMofN <Boolean>] [-ReportPct <Boolean>]
[-ReservationForms <string>] [-ReplaceForwardAddressInUserName <Boolean>] [-
RewriteRtf <Int32>] [-RmvForwarding <Boolean>] [-RootFolderAclMode
<RootFolderAclModeEnum>] [-RpcProxyServerCertificationUrl <Uri>] [-
RPCProxyServerUrl <Uri>] [-RpcUseAuthType <OutlookLogonNetworkSecurityEnum>] [-
RPCUseFastHttp <Boolean>] [-RPCUseHttp <Boolean>] [-RPCUseProxyCertification
<Boolean>] [-RPCUseSlowHttp <Boolean>] [-RPCUseSsl <Boolean>] [-RunAsService
<Boolean>] [-RunUpdateAddressList <Boolean>] [-RunUpdateEmailAddressPolicy
<Boolean>] [-SelectedMailFile <string>] [-SelectedProfile <string>] [-
SelectedPstDir <string>] [-SendStatus <Boolean>] [-ServerMailDest
<GeneralDestinationTypeEnum>] [-ServerMailDestServerArchive <Boolean>] [-
ServerMailResolveAttendees <Boolean>] [-SetManagedByToUserForest <Boolean>] [-
SetPersonDocCustom <Boolean>] [-SetUserAccountControl <Boolean>] [-
SkipDisabledGroupMembers <Boolean>] [-SharePointServerName <string>] [-
ShowSetMailDomain <Boolean>] [-SkipCompletedTasks <Boolean>] [-SkipConflictDocs
<Boolean>] [-SkipNotes <IList`1[String]>] [-SkipOutOfRangeException <Boolean>] [-
SmtpForwardingAddress <Boolean>] [-SmtpTranslationTable <string>] [-
SourceAdminDirSync <Boolean>] [-SqlColumn <string>] [-SqlCredentials <string>] [-
StationaryFolder <string>] [-StationaryForms <string>] [-TargetType <string>] [-
TargetTypeTested <Int32>] [-TaskForms <string>] [-TaskNoticeForms <string>] [-
ThreadCount <Int32>] [-TotalSelAddrBooks <Int64>] [-TotalSelArchives <Int64>] [-
TotalSelMailFiles <Int64>] [-UpdateMode <NotesUpdateModeTypeEnum>] [-UpdateRtfFonts
<Boolean>] [-UseAdminAcctPool <Boolean>] [-UseAppNxRtfDll <Boolean>] [-
UseAutodiscoverCreateProfile <Boolean>] [-UseFilteredAttachmentMsg <Boolean>] [-
UseFilteredBodyMsg <Boolean>] [-UseImapFlags <Boolean>] [-UseLargePsts <Boolean>]
[-UseMailFileOnly <Boolean>] [-UseMailFileOwner <Boolean>] [-UserAccountControl
<Int32>] [-UserContainer <string>] [-UserFilter <string>] [-UserFolderPrefix
<string>] [-UserForestHost <string>] [-UserForestPassword <string>] [-
UserForestUserId <string>] [-UsePseudoRoot <Boolean>] [-UseSeparatePsts <Boolean>]
[-UseSpecialArchiveFolder <Boolean>] [-UseUserForest <Boolean>] [-VisibilityMode
<NotesVisibilityModeEnum>] [-WatchDogMinutes <Int32>] [-WriteCpidForRichText
<Boolean>] [<CommonParameters>]

Description
The cmdlet allows you to set every part of the configuration through parameters.

Warning: parameters do not have descriptions.

Parameters

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

253
PowerShell cmdlets for Migrator for Notes to Exchange
-ConfigurationFromPipeline <Configuration>
The configuration from the pipeline to set.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Section <string>
Required: true
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Key <string>
Required: true
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Value <string>
Required: false
Position: 3
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AclIgnore <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AclIgnoreCount <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AclRootVisibleOnly <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Acls <Boolean>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

254
PowerShell cmdlets for Migrator for Notes to Exchange
Accept pipeline input:false
Accept wildcard characters:false

-ActiveDirectoryAlwaysUseDefaults <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ActiveDirectoryGroupType <ActiveDirectoryGroupTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ActiveDirectoryHost <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ActiveDirectoryPassword <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ActiveDirectoryUserId <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Ad2AdAttribute <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Ad2OpenFlags <AuthenticationTypes>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Ad2UserFilter <string>
Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

255
PowerShell cmdlets for Migrator for Notes to Exchange
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdAttribute <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AddFullAccessPermission <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AddressListName <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AddressPolicyName <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdjustTaskReminderToMidnight <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdminDomain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdminMailbox <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdminPassword <string>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

256
PowerShell cmdlets for Migrator for Notes to Exchange
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdminProfile <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AdminUsername <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AllowForwardToNotesConnector <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AllowHtmlCalendarBodies <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AllowNotesForeignDirSync <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AllowSelfSignedCerts <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AltAddressAttribute <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AlwaysDoForwarding <Int32>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

257
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AlwaysRmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AlwaysUseDefaults <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AlwaysUseOldAlias <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AlwaysUseOldExchDn <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AppDoesArch <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AppDoesEncrypted <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AppDoesMail <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

258
PowerShell cmdlets for Migrator for Notes to Exchange
-AppDoesPabs <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AppendSmtpAddressToContactsDisplayName <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AppointmentForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AppointmentLocationSource <Int16>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveDesignClass <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveDest <GeneralDestinationTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveDestServerArchive <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

259
PowerShell cmdlets for Migrator for Notes to Exchange
-ArchiveReplicaDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveReplicaServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ArchiveResolveAttendees <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AskArchiveDest <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AskFilter <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AskPabDest <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AskServerMailDest <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AttachmentFilteredBySizeMsg <string>
Required: false
Position: named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

260
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-AttachmentLostDueToEncryptionMsg <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Attribute <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AuthMechanismType <AuthenticationMechanismTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AutodiscoverDisableMapiHttp <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AutodiscoverEnableScpLookup <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AutodiscoverMaxHops <Integer>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AutodiscoverPreferInternalRpcHttpUrl <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AutodiscoverPreferInternalUrl <Nullable<Boolean>>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

261
PowerShell cmdlets for Migrator for Notes to Exchange
Accept pipeline input:false
Accept wildcard characters:false

-AutodiscoverUrl <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-BodyLostDueToEncryptionMsg <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CalMaxRecurrenceFixType <CalMaxRecurrenceFixTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CanAddGroupMembers <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CanDeleteGroupMembers <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CentralLogDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CentralLogLevel <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CmnExcludeFromDirSync <string>
Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

262
PowerShell cmdlets for Migrator for Notes to Exchange
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CompressLogFile <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ContactFilter <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ContactsName <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CreateFwdAddrInAd <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CreateGroupDelay <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CreateMailBox <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CreateMailboxDelay <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CurArchiveDir <string>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

263
PowerShell cmdlets for Migrator for Notes to Exchange
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CurMailFileDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DateFilterUsingFormula <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DeclineFolderCheck <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DeleteAutoCompleteMessages <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DeleteMailDomain <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DisableCredentialScanner <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DisableDialogScanner <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DisableModernAuthentication <Boolean>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

264
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DisableDirSync <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoAuditLog <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DocLinksDefaultServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DocLinksFastLookupOnly <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DocLinksHttpPort <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoHtmlBody <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoMailRouting <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

265
PowerShell cmdlets for Migrator for Notes to Exchange
-Domain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DomainController <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DominoDomain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoNeedAdsi <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoNeedCdoexm <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoNotesMailRouting <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoRmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoSetCalDomain <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

266
PowerShell cmdlets for Migrator for Notes to Exchange
-DoSetExcalconServer <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoSetForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoSetMailDomain <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoSetMailSystem <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoSetNotesFormatPreference <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoShowRmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoShowSetForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoSourceAdmin <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

267
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-DoTargetAdmin <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoVisibility <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DoX500Proxy <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EmailAddressPolicyEnabled <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EnableArchiveMailbox <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EnableUsers <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EncryptedMailOnly <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EndUserDir <string>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

268
PowerShell cmdlets for Migrator for Notes to Exchange
Accept pipeline input:false
Accept wildcard characters:false

-EndUserStatsDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ExcalconServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ExchangeServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ExcludeDominoDomainFromFwdAddrInAD <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FileAsFormat <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FindArchivesBy <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FindMailFilesBy <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FindPabsBy <string>
Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

269
PowerShell cmdlets for Migrator for Notes to Exchange
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForceAddrBooks <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForceAddress <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForceOldNxRtfDll <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForceTargetAdmin <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForwardingAddress <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForwardingDomain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ForwardingMethod <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FwdAddrDelim <string>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

270
PowerShell cmdlets for Migrator for Notes to Exchange
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FwdAttrField <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FwdCalDomain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FwdMailDomain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-GroupContactsContainer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-GroupFilter <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-GroupsContainer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-GroupsSearchFilter <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-HomeMailBoxStore <string>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

271
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-HomeServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-HtmlDocLinks <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-IgnoreAcls <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-IgnoreForms <IList`1[String]>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-IncludeServerMailFile <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-JournalEntryMessageType <NotesJournalEntryMessageTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LoadMethod <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

272
PowerShell cmdlets for Migrator for Notes to Exchange
-LocateArchives <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LocateMailFiles <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LocateNew <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LocatePabs <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LogLevel <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-LookupDisplayNames <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailDesignClass <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

273
PowerShell cmdlets for Migrator for Notes to Exchange
-MailEnableAttempts <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailEnableRetryWaitSeconds <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailFileDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailSystem <MailSystemTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MailTarget <MailTargetTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MapiAdminProfile <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MapiRecipient <MapiRecipientActionEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MapiRetryCount <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

274
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-MapiUseSharedProfile <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MapPrivateAsPublic <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxExceptionsPerMessage <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxExtractedImageArea <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxFolderCache <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxLargePstSize <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxMailboxConnectionRetryWaitTime <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MaxPstSize <Int32>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

275
PowerShell cmdlets for Migrator for Notes to Exchange
Accept pipeline input:false
Accept wildcard characters:false

-MaxSessionReconnectCount <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MBoxFromContact <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MemoForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeAddressBookFolder <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeAddressBooks <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeContactAttribWins <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeContactIsAuthoritative <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeCrossCheckObjs <Boolean>
Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

276
PowerShell cmdlets for Migrator for Notes to Exchange
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeFindBySmtp <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeGrpMembership <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeReqImportedFrom <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeReqProxyAddress <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeSyncObjRequired <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MergeX500 <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MessageRetryCount <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MessageRetryWait <Int32>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

277
PowerShell cmdlets for Migrator for Notes to Exchange
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Migrate <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateAppointmentResponses <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateArchives <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateConflictDocs <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateEmptyFolders <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateMailOrCalendar <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateMailUsingServer <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateOrphanedDocs <Boolean>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

278
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigratePab <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateRecurringBeforeRange <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateReservationsAlways <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrateServerMail <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MimeIgnoreBoundaryWhitespace <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MinSpace <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

279
PowerShell cmdlets for Migrator for Notes to Exchange
-MsgRequireAnyFeature <MsgRequireAnyFeatureTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NabCount <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NabReaderGroup <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NeedLoginInfo <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NoServer <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesAlwaysDoForwarding <Int16>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesAlwaysRmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesAlwaysUseDefaults <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

280
PowerShell cmdlets for Migrator for Notes to Exchange
-NotesDoRmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesDoSetForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesDoShowRmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesDoShowSetForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesEncryptedMailOnly <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesFormatPreference <NotesFormatPreferenceTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesForwardingDomain <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesFwdAddrDelim <string>
Required: false
Position: named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

281
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-NotesFwdAttrField <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesIniPath <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesPassword <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesPreferredNab <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotesUserIdFile <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NoticeForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-O365Environment <string>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

282
PowerShell cmdlets for Migrator for Notes to Exchange
Accept pipeline input:false
Accept wildcard characters:false

-O365MaxMailboxConnectionWaitTime <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-O365PSConnectionUri <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Offline <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-OpenFlags <AuthenticationTypes>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-OrphanedDocsFolder <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-OwnerByAcl <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabDesignClass <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabDest <GeneralDestinationTypeEnum>
Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

283
PowerShell cmdlets for Migrator for Notes to Exchange
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabDestServerArchive <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabGroupForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabPersonForm <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicaDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicaServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicatorFrom <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicatorSign <Boolean>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

284
PowerShell cmdlets for Migrator for Notes to Exchange
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicatorSubject <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicatorTargetDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabReplicatorTargetServer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabRequiredAttrs <IList`1[String]>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PabsInMailFile <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-Pass2Delay <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PostLogs <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PowerShellXmlErrorFile <string>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

285
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ProvisionUsers <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PsRetryAttempts <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PsRetryWait <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PstDirMode <OutlookPstDirectoryModeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PstFileName <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PstFileNameFormat <OutlookPstFileNameFormatEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PstRootDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

286
PowerShell cmdlets for Migrator for Notes to Exchange
-PublicDelegates <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-PurgePabs <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QuotaMode <NotesQuotaModeTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-QuoteNonAsciiCharsInRtf <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RemigrateMode <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RemoveDirSyncAttribute <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RemoveSrcAddresses <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ReplaceForwardAddressInUserName <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

287
PowerShell cmdlets for Migrator for Notes to Exchange
-ReportErrors <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ReportMofN <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ReportPct <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ReservationForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RewriteRtf <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RmvForwarding <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RootFolderAclMode <RootFolderAclModeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RpcProxyServerCertificationUrl <Uri>
Required: false
Position: named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

288
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-RPCProxyServerUrl <Uri>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RpcUseAuthType <OutlookLogonNetworkSecurityEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RPCUseFastHttp <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RPCUseHttp <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RPCUseProxyCertification <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RPCUseSlowHttp <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RPCUseSsl <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RunAsService <Boolean>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

289
PowerShell cmdlets for Migrator for Notes to Exchange
Accept pipeline input:false
Accept wildcard characters:false

-RunUpdateAddressList <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RunUpdateEmailAddressPolicy <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SelectedMailFile <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SelectedProfile <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SelectedPstDir <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SendStatus <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ServerMailDest <GeneralDestinationTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ServerMailDestServerArchive <Boolean>
Required: false
Position: named

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

290
PowerShell cmdlets for Migrator for Notes to Exchange
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ServerMailResolveAttendees <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SetManagedByToUserForest <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SetPersonDocCustom <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SetUserAccountControl <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SkipDisabledGroupMembers <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SharePointServerName <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ShowSetMailDomain <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SkipCompletedTasks <Boolean>
Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

291
PowerShell cmdlets for Migrator for Notes to Exchange
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SkipConflictDocs <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SkipNotes <IList`1[String]>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SkipOutOfRangeException <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SmtpForwardingAddress <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SmtpTranslationTable <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SourceAdminDirSync <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SqlColumn <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SqlCredentials <string>

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

292
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-StationaryFolder <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-StationaryForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetType <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TargetTypeTested <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TaskForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TaskNoticeForms <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ThreadCount <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

293
PowerShell cmdlets for Migrator for Notes to Exchange
-TotalSelAddrBooks <Int64>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TotalSelArchives <Int64>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TotalSelMailFiles <Int64>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UpdateMode <NotesUpdateModeTypeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UpdateRtfFonts <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseAdminAcctPool <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseAppNxRtfDll <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseAutodiscoverCreateProfile <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

294
PowerShell cmdlets for Migrator for Notes to Exchange
-UseFilteredAttachmentMsg <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseFilteredBodyMsg <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseImapFlags <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseLargePsts <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseMailFileOnly <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseMailFileOwner <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserAccountControl <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserContainer <string>
Required: false
Position: named
Default value:
Accept pipeline input:false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

295
PowerShell cmdlets for Migrator for Notes to Exchange
Accept wildcard characters:false

-UserFilter <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserFolderPrefix <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserForestHost <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserForestPassword <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UserForestUserId <string>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UsePseudoRoot <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseSeparatePsts <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseSpecialArchiveFolder <Boolean>
Required: false
Position: named
Default value:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

296
PowerShell cmdlets for Migrator for Notes to Exchange
 Accept pipeline input:false
Accept wildcard characters:false

-UseUserForest <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-VisibilityMode <NotesVisibilityModeEnum>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WatchDogMinutes <Int32>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WriteCpidForRichText <Boolean>
Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
Configuration
The configuration object to update. This parameter accepts input from the pipeline.

Outputs
None if successful.

Examples
PS C:\>Set-MNEConfiguration -ConfigurationFromPipeline $Config -Acls $true -
AllowForwardToNotesConnector $false
Sets the specified values.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

297
PowerShell cmdlets for Migrator for Notes to Exchange
Set-MNEDatabaseConnectionString

Synopsis
Sets the database connection string for Notes Migrator for Exchange.

Syntax
Set-MNEDatabaseConnectionString [-IntegratedSecurity <Boolean>] [-DbUser <string>]
[-DbPassword <string>] -DbServer <string> -DbSharedDir <string> [<CommonParameters>]

Description
Sets the database connection string.

There are two parameter sets, based on whether you are accessing the database using Windows Authentication
or SQL Authentication.

The database name and database provider are constant for MNE.

Parameters
-IntegratedSecurity [<Boolean>]
Used if the database is accessed using Windows Authentication.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DbUser <string>
Used if the database is accessed by SQL Server Authentication.

This is the username for accessing the database.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DbPassword <string>
Used if the database is accessed by SQL Server Authentication.

This is the password for accessing the database.

Required: false
Position: named
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
298
PowerShell cmdlets for Migrator for Notes to Exchange
 Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DbServer <string>
Server of the database being accessed.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DbSharedDir <string>
Shared directory of the database being accessed.

Required: true
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
This cmdlet returns no value or output upon success.

Examples
PS C:\>Set-MNEDatabaseConnectionString -IntegratedSecurity $true -DbServer "(local)"
-DbSharedDir "\\Computer\C$\NME Stuff\"
Uses Windows Authentication to connect to the server and set the database connection string.

PS C:\>Set-MNEDatabaseConnectionString -DbUser "username" -DbPassword "password" -

DbServer "(local)" -DbSharedDir "\\Computer\C$\NME Stuff\"
Uses SQL Authentication to connect to the server and set the database connection string.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

299
PowerShell cmdlets for Migrator for Notes to Exchange
Set-MNEDesignClass

Synopsis
Sets a design class in the database.

Syntax
Set-MNEDesignClass -DesignClassGuid <Guid> [-Authoritative <Boolean>] [-
DataStoreTypeMask <DataStoreTypeMaskEnum>] [<CommonParameters>]

Set-MNEDesignClass -DesignClassName <string> [-Authoritative <Boolean>] [-

DataStoreTypeMask <DataStoreTypeMaskEnum>] [<CommonParameters>]

Description
Sets the Authoritative status and/or the DataStoreTypeMask for a design class in the database, selected either by
name or Guid.

Parameters
-DesignClassGuid <Guid>
Guid of the design class to set.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-DesignClassName <string>
Name of the design class to set.

Required: true
Position: named
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

-Authoritative <Boolean>
Whether the design class to set has authoritative status.

Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-DataStoreTypeMask <DataStoreTypeMaskEnum>
Data store type mask of the design class to set.
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
300
PowerShell cmdlets for Migrator for Notes to Exchange
 Required: false
Position: named
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
System.Guid
Guid of the design class to set.

System.String
Name of the design class to set.

Outputs
NMEDesignClass
Outputs the design class that was set if there are no errors.

Examples
PS C:\>Set-MNEDesignClass -DesignClassName "TestName" -Authoritative $true -
DataStoreTypeMask All
Sets the specified design class in the database to the parameters given.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

301
PowerShell cmdlets for Migrator for Notes to Exchange
Set-MNEMigrationTimeWindow

Synopsis
Sets the migration windows used in the SSDM Scheduling Administration tool.

Syntax
Set-MNEMigrationTimeWindow [-CollectionName] <string> [[-ConcurrentUsers] <Integer>]
[[-MigrationDateFrom] <string>] [[-MigrationDateTo] <string>] [[-EnableTimeWindow]
<Boolean>] [[-MigrationTimeFrom] <string>] [[-MigrationTimeTo] <string>]
[<CommonParameters>]

Description
Sets the migration windows used in the SSDM Scheduling Administration tool.

Parameters
-CollectionName <string>
Name of the collection to set the window for. The collection cannot be auto-defined.

Required: true
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-ConcurrentUsers <Integer>
Number of users that can migrate at one time.

Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrationDateFrom <string>
Date when users can start migrating.

Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrationDateTo <string>
Date when users must stop migrating.

Required: false
Quest Migrator for Notes to Exchange 4.16.2 Administration Guide
302
PowerShell cmdlets for Migrator for Notes to Exchange
 Position: 3
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EnableTimeWindow <Boolean>
Whether the users are limited to a certain time to migrate each day.

Required: false
Position: 4
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrationTimeFrom <string>
Time of day when users can start migrating.

Required: false
Position: 5
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-MigrationTimeTo <string>
Time when users must stop migrating.

Required: false
Position: 6
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
This cmdlet returns nothing.

Examples
PS C:\>Set-MNEMigrationTimeWindow -CollectionName "some users" -ConcurrentUsers 5 -
MigrationDateFrom "8/15/2013 8:45:00 AM" -MigrationDateTo "8/31/2013 4:00:00 PM" -
EnableTimeWindow $false
Sets the migration window for the collection "some users" to 8/15/2013 at 8:45:00 AM to 8/31/2013 at 4:00:00 PM,

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

303
PowerShell cmdlets for Migrator for Notes to Exchange
with a max of 5 concurrent users, and no specific time window.

PS C:\>Set-MNEMigrationTimeWindow -CollectionName "other users" -ConcurrentUsers 2 -

MigrationDateFrom "8/15/2013 8:45:00 AM" -MigrationDateTo "8/31/2013 4:00:00 PM" -
EnableTimeWindow $true -MigrationTimeFrom "5:00:00 PM" -MigrationTimeTo "11:00:00
PM"
Sets the migration window for the collection "other users" to 8/15/2013 at 8:45:00 AM to 8/31/2013 at 4:00:00 PM,
with a max of 2 concurrent users, and a specific time window between 5:00 PM and 11:00 PM.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

304
PowerShell cmdlets for Migrator for Notes to Exchange
Set-MNESchedulingConfigFile

Synopsis
Sets the configuration files used in the SSDM Scheduling Administration tool.

Syntax
Set-MNESchedulingConfigFile [[-XmlConfigPath] <string>] [[-CollWizPath] <string>]
[[-WebServiceLocation] <string>] [<CommonParameters>]

Description
Sets the configuration files used in the SSDM Scheduling Administration tool.

Parameters
-XmlConfigPath <string>
Path to the Xml Config File.

Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-CollWizPath <string>
Path to the MNE Collection Wizard.

Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-WebServiceLocation <string>
URI to the SSDM Web Service.

Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

305
PowerShell cmdlets for Migrator for Notes to Exchange
Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
This cmdlet returns nothing.

Examples
PS C:\>Set-MNESchedulingConfigFile -XmlConfigPath "c:\conf.xml" -CollWizPath
"c:\collwiz.exe" -WebServiceLocation
"http://localhost/SSDMSchedulingWebService/SSDMSchedulingWebService.asmx"
Sets XmlConfigFile to c:\conf.xml, CollWizPath to c:\collwiz.exe, and WebServiceLocation to
http://localhost/SSDMSchedulingWebService/SSDMSchedulingWebService.asmx.

PS C:\>Set-MNESchedulingConfigFile -XmlConfigPath "c:\conf2.xml"

Sets XmlConfigFile to c:\conf2.xml and leaves the rest of the parameters alone.

PS C:\>Set-MNESchedulingConfigFile
Doesn't change the parameters, unless the file doesn't exist or is invalid. In that case, it creates the file with empty
parameters.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

306
PowerShell cmdlets for Migrator for Notes to Exchange
Set-MNESchedulingSetting

Synopsis
Sets the settings used in the SSDM Scheduling Administration tool.

Syntax
Set-MNESchedulingSetting [[-UseSsdmSched] <Boolean>] [[-TimeOut] <Integer>] [[-
FileProc] <Integer>] [[-IsEmail] <Boolean>] [[-EmailAddresses] <String[]>] [[-
EmailSubject] <string>] [[-EmailBody] <string>] [[-EmailAutoSend] <Boolean>] [[-
SchedReminder] <Boolean>] [[-NotScheduled] <string>] [[-BeforeMigrationDate]
<string>] [[-AfterMigrationDate] <string>] [[-BeforeMigrationTime] <string>] [[-
AfterMigrationTime] <string>] [[-TooManyConnections] <string>] [[-RetryAttempt]
<Integer>] [[-RetryWaitMinute] <Integer>] [[-UseLimitedRetry] <Boolean>]
[<CommonParameters>]

Description
Sets the settings used in the SSDM Scheduling Administration tool.

Parameters
-UseSsdmSched <Boolean>
Whether or not to use SSDM Scheduling
Required: false
Position: 0
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TimeOut <Integer>
Session timeout in minutes
Required: false
Position: 1
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-FileProc <Integer>
Update progress in minutes
Required: false
Position: 2
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-IsEmail <Boolean>
Whether to email the migration team on problems.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

307
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: 3
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EmailAddresses <string[]>
The email addresses to send to when problems occur.

Required: false
Position: 4
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EmailSubject <string>
The subject of the email dispatched when problems occur.

Required: false
Position: 5
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EmailBody <string>
The body of the email dispatched when problems occur.

Required: false
Position: 6
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-EmailAutoSend <Boolean>
Whether the user automatically sends email if problems occur.

Required: false
Position: 7
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-SchedReminder <Boolean>
Lets users add a scheduled task if before window.

Required: false
Position: 8
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-NotScheduled <string>
Text the user sees if not scheduled to migrate.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

308
PowerShell cmdlets for Migrator for Notes to Exchange
Required: false
Position: 9
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-BeforeMigrationDate <string>
Text the user sees if before migration date window.

Required: false
Position: 10
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AfterMigrationDate <string>
Text the user sees if after migration date window.

Required: false
Position: 11
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-BeforeMigrationTime <string>
Text the user sees if before migration time window.

Required: false
Position: 12
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-AfterMigrationTime <string>
Text the user sees if after migration time window.

Required: false
Position: 13
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-TooManyConnections <string>
Text the user sees if too many users simulataneously migrating.

Required: false
Position: 14
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RetryAttempt <Integer>
Number of SSDM retry migration attempts.

Required: false

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

309
PowerShell cmdlets for Migrator for Notes to Exchange
 Position: 15
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-RetryWaitMinute <Integer>
Time to (in minutes) before retrying.

Required: false
Position: 16
Default value:
Accept pipeline input:false
Accept wildcard characters:false

-UseLimitedRetry <Boolean>
Whether to limit the number of retries.

Required: false
Position: 17
Default value:
Accept pipeline input:false
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
This cmdlet has no parameters that accept pipeline input.

Outputs
This cmdlet returns nothing.

Examples
PS C:\>Set-MNESchedulingSetting -UseSsdmSched $true -TimeOut 10 -FileProc 1000 -
IsEmail $false
Sets UseSsdmSched to true, the timeout to 10 minutes, the file proc to 1000 minutes, and IsEmail to false. The
rest of the parameters are left alone.

PS C:\>Set-MNESchedulingSetting
Doesn't change any of the parameters, unless the file doesn't exist or is invalid. In that case, it creates the file with
empty parameters.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

310
PowerShell cmdlets for Migrator for Notes to Exchange
Show-MNECollection

Synopsis
Sets a Collection to be "visible" in the UI.

Syntax
Show-MNECollection [-Collection] <NmeCollection> [<CommonParameters>]

Description
Sets a Collection to be "visible" in the UI. The collection is added/updated in the database upon completion.

Parameters
-Collection <NmeCollection>
The collection object to be set visible.

Required: true
Position: 0
Default value:
Accept pipeline input:true (ByValue)
Accept wildcard characters:false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)

Inputs
NmeCollection
The collection to be set visible.

Outputs
None if successful.

Examples
Get-MNECollection -CollectionGuid "e50d5123-2ec8-4096-816e-8e0e458d12e7" | Show-
MNECollection
A collection is retrieved from the database and its visiblity is set to visible.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

311
PowerShell cmdlets for Migrator for Notes to Exchange
 17
Appendix A: How do I ...?
• Post-installation configuration
• Pre-migration preparations
• Batch-migration process
• Other features

Post-installation configuration
These tasks configure the Migrator for Notes to Exchange process as a whole, so are typically performed before
the more specific configuration tasks for a particular migration project:
• How do I set the account permissions necessary for migration?
• How do I configure Migrator for Notes to Exchange for a non-English Notes locale?
• How do I enable remote management on an Exchange 2010 or later server?

How do I set the account permissions

necessary for migration?
This question is answered, for both proprietary and hosted Exchange targets, in the System Requirements (see
the Migrator for Notes to Exchange Quick-Start Guide and the Migrator for Notes to Exchange Pre-Migration
Planning Guide, preceding the Requirement Specifications).

How do I configure Migrator for Notes to

Exchange for a non-English Notes locale?
For a non-English locale, you may need to reconfigure up to four sets of parameters for both the Data Migration
Wizard (for batch migrations) and the SSDM (for per-desktop migrations). Review the four sections that follow to
determine whether you need to edit the parameters for your locale.
The topic How do I add or edit program parameters? in this Appendix explains how to change these parameter
values, and also explains the important difference between Global Parameters (system-wide defaults) and Task
Parameters (parameter settings for a single specific task).
These parameter configuration changes should be entered in the Global Parameters if all or most of the migrating
users reside in a single non-English locale. If the migrating users are distributed across a variety of locales, it may
be more practical to define separate collections and migration tasks for users in the different locales, and make
these configuration changes in the Task Parameters. In either case, remember that the parameters should also be
reconfigured in notesdtapp.ini.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

312
Appendix A: How do I ...?
Reconfiguring Outlook Categories
If these defaults are not the correct values for your locale, be sure to
change them before you run either of the migration programs. For
example, the values in Japanese would be as shown in the left
column here.
The Setup program automatically configures both the Data Migration
Wizard (for batch migrations) and the SSDM (for per-desktop
migrations) with these English-language values for Outlook
Categories as shown in the right column here.

Renaming the Orphaned Documents folder

The Setup program automatically sets the name of the “All Documents” folder in Exchange, which receives
orphaned documents from Notes' “All Documents” folder. The folder is named “All Documents” (in English) by
default, but you can assign any other valid folder name. The parameter is set in two different places for the Data
Migration Wizard and the Self-Service Desktop Migrator, so you should reset the folder name in both places.
In the [Notes] section, set the appropriate value for:
OrphanedDocsFolder=<Folder Name>
For example, for a Japanese Notes environment:

Defining new language sections

The Global Defaults, Task Parameters, and notesdtapp.ini file contain parameter
sections that specify the names of migrated Outlook folders in various lan-
guages. For example, the section for Japanese [JPN] appears in the example
here. The Data Migration Wizard refers to the appropriate section when naming
new Outlook folders. (The wizard determines the “appropriate” language section
by reading the Windows locale.)
The Global Defaults and notesdtapp.ini file contain sections for several common
languages, and common variants of the world's primary languages—for
example, French as spoken in France vs. Canada vs. Belgium vs. Monaco, and
so forth. But the default program parameters do not include sections for many
less common language variants.
The Global Defaults and notesdtapp.ini file do, however, contain sections for more generic forms of the world's
primary languages, so if the wizard can't find a section for a language variant associated with a particular locale,
the wizard will instead consult the more generic section. In Quebec, for example, if the wizard can't find a section
for [FRC] (Canadian French), it will instead use the folder names specified in [FR] (generic French). In releases
prior to 4.0.0.34, the wizard would default to English-language folder names if it couldn't find a section for a
particular language variant.
If the default program parameters do not contain a section for the language variant associated with your locale,
and if you don't want to use the more generic language alternative, you can create a new section for the language
variant you want. You can add a new section to the Global Defaults, or notesdtapp.ini, or both. The section name
must be exactly three letters, and must conform to the conventions of the Language TLAs for Various Locales
table (below).

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

313
Appendix A: How do I ...?
Language TLAs for Various Locales
Afrikaans–South Africa AFK English–Trinidad ENT Polish–Poland PLK
Albanian–Albania SQI English–United Kingdom ENG Portuguese–Brazil PTB
Arabic–Algeria ARG English–United States ENU Portuguese–Portugal PTG
Arabic–Bahrain ARH English–Zimbabwe ENW Punjabi–India (Gurmukhi Script) PAN
Arabic–Egypt ARE Estonian–Estonia ETI Romanian–Romania ROM
Arabic–Iraq ARI Faeroese–Faeroe Islands FOS Russian–Russia RUS
Arabic–Jordan ARJ Farsi–Iran FAR Sanskrit–India SAN
Arabic–Kuwait ARK Finnish–Finland FIN Serbian–Serbia (Cyrillic) SRB
Arabic–Lebanon ARB French–Belgium FRB Serbian–Serbia (Latin) SRL
Arabic–Libya ARL French–Canada FRC Slovak–Slovakia SKY
Arabic–Morocco ARM French–France FRA Slovenian–Slovenia SLV
Arabic–Oman ARO French–Luxembourg FRL Spanish–Argentina ESS
Arabic–Qatar ARQ French–Monaco FRM Spanish–Bolivia ESB
Arabic–Saudi Arabia ARA French–Switzerland FRS Spanish–Chile ESL
Arabic–Syria ARS FYRO Macedonian– MKI Spanish–Colombia ESO
FYRO Macedonia
Arabic–Tunisia ART Galician–Spain GLC Spanish–Costa Rica ESC
Arabic–U.A.E. ARU Georgian–Georgia KAT Spanish–Dominican Republic ESD
Arabic–Yemen ARY German–Austria DEA Spanish–Ecuador ESF
Armenian–Armenia HYE German–Germany DEU Spanish–El Salvador ESE
Azeri–Azerbaijan (Cyrillic) AZE German–Liechtenstein DEC Spanish–Guatemala ESG
Azeri–Azerbaijan (Latin) AZE German–Luxembourg DEL Spanish–Honduras ESH
Basque–Spain EUQ German–Switzerland DES Spanish–Mexico ESM
Belarusian–Belarus BEL Greek–Greece ELL Spanish–Nicaragua ESI
Bulgarian–Bulgaria BGR Gujarati–India (Gujarati Script) GUJ Spanish–Panama ESA
Catalan–Spain CAT Hebrew–Israel HEB Spanish–Paraguay ESZ
Chinese–Hong KongSAR ZHH Hindi–India HIN Spanish–Peru ESR
Chinese–Macau SAR ZHM Hungarian–Hungary HUN Spanish–Puerto Rico ESU
Chinese–PRC CHS Icelandic–Iceland ISL Spanish–Spain (Inat’l Sort) ESN
Chinese–Singapore ZHI Indonesian–Indonesia IND Spanish–Spain (Trad Sort) ESP
Chinese–Taiwan CHT Italian–Italy ITA Spanish–Uruguay ESY
Croatian–Croatia HRV Italian–Switzerland ITS Spanish–Venezuela ESV
Czech–Czech Republic CSY Japanese–Japan JPN Swahili–Kenya SWK
Danish–Denmark DAN Kannada–India (Kannada Script) KAN Swedish–Finland SVF
Divehi–Maldives DIV Kazakh–Kazakstan KKZ Swedish–Sweden SVE
Dutch–Belgium NLB Konkani–India KNK Syriac–Syria SYR
Dutch–Netherlands NLD Korean KOR Tamil–India TAM
(Extended Wansung)–Korea
English–Australia ENA Kyrgyz–Kyrgyzstan KYR Tatar–Tatarstan TTT
English–Belize ENL Latvian–Latvia LVI Telugu–India (Telugu Script) TEL
English–Canada ENC Lithuanian–Lithuania LTH Thai–Thailand THA
English–Caribbean ENB Malay–Brunei Darussalam MSB Turkish–Turkey TRK
English–Ireland ENI Malay–Malaysia MSL Ukrainian–Ukraine UKR
English–Jamaica ENJ Marathi–India MAR Urdu–Pakistan URD
English–New Zealand ENZ Mongolian (Cyrillic)–Mongolia MON Uzbek–Uzbekistan (Cyrillic) UZB
English–Philippines ENP Norwegian–Norway (Bokmål) NOR Uzbek–Uzbekistan (Latin) UZB
English–South Africa ENS Norwegian–Norway (Nynorsk) NON Vietnamese–Viet Nam VIT

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

314
Appendix A: How do I ...?
How do I enable remote management on an
Exchange 2010 or later server?
Run "winrm quickconfig" on the Exchange server, as shown below. These lines show your user input (in bold) in
addition to the program output:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>winrm quickconfig
WinRM already is set up to receive requests on this machine.
WinRM is not set up to allow remote access to this machine for management.
The following changes must be made:
Create a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
Enable the WinRM firewall exception.
Make these changes [y/n]? y
WinRM has been updated for remote management.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
WinRM firewall exception enabled.
C:\Users\Administrator>_

Pre-migration preparations
These tasks are typically performed when configuring Migrator for Notes to Exchange for a particular migration
project:
• How do I add or edit program parameters?
• How do I migrate from a Notes environment with Symantec E-Vault?
• How do I migrate to an Exchange environment with a CAS Array?
• How do I prepare the SQL database for mailbox-enabling (if AD is configured for a resource forest and a
user forest)?
• How do I add to the list of AD attributes available for the merge function?
• How do I configure AD to replicate an AD attribute to the Global Catalog?
• How do I specify per-user locations for Notes source data?
• How do I specify per-user destination locations for users’ PST files?
• How do I specify whether to migrate to a single PST file (per user) or multiple PST files?
• How do I migrate Notes custom attributes?
• How do I customize the placeholder message that the Data Migration Wizard substitutes for encrypted
messages?
• How do I customize the placeholder message that the Data Migration Wizard substitutes for filtered
attachments?
• How do I create or edit a template for personalized user-notification emails?
• How do I synchronize directory data and update the SQL database?

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

315
Appendix A: How do I ...?
How do I add or edit program parameters?
The parameters for the Self-Service Desktop Migrator are saved and may be edited in a text file, notesdtapp.ini,
which resides in the same path with the Desktop Migrator application. All other Migrator for Notes to Exchange
parameters are for the administrator components, and these parameters exist in two forms:
• Task Parameters: Settings that apply to the operations of only single particular tasks.
• Global Defaults: Values that constitute the initial Task Parameters (as defined above) when a task is
created, unless and until the Task Parameters are edited.
The Notes Migration Manager maintains the Global Defaults in the SQL database, and permits editing Global
Defaults to suit local circumstances and preferences. Each time a wizard creates a task, the wizard copies the
parameters from the Global Defaults to the task definition, where they become Task Parameters. The Task
Parameters may then be edited separately for each particular task.
Global Defaults, Task Parameters, and the parameters within notesdtapp.ini are all edited the same way, as if all
three sets of parameters were stored in an INI file. The features that let you edit Global Defaults and Task
Parameters copy the current parameter settings from the SQL database into a text document in Windows'
Notepad, so you can use Notepad's text-editing features to change parameter values or add new parameter
specifications. The full procedures are described separately below. Since notesdtapp.ini is an INI text file, you can
use Notepad or any other text editor to edit its contents.

How to add or edit Global Defaults

Within Notes Migration Manager:
1 Select File | Global Default Settings.
The program then opens the Global Default Settings into Windows Notepad. Within Notepad, the settings
look like the contents of an INI file, but they are saved as a part of the SQL database rather than as an
independent INI file.
2 Find the pertinent [SectionName] for the parameter you want to add, or whose value you want to edit.

IMPORTANT: Some parameters in different sections share the same keyname, so it is very important
that parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager will then copy the new parameter value(s) back into the SQL database.

How to add or edit Task Parameters

In Notes Migration Manager, make sure this feature is enabled: On the View menu, make sure the Advanced
Settings option is marked. This is a toggle setting that determines whether the wizards will let you open and edit
Task Parameters. If the feature is enabled, an extra screen titled "Customize Configuration" will appear at the start
of the screen sequence for each Wizard.
From the Customize Configuration screen in any of the wizards:
1 Click the Edit button. The wizard then opens the task's configuration settings into Windows Notepad.
Within Notepad, the settings look like the contents of an INI file, but they are saved as a part of the SQL
database rather than as an independent INI file.
2 Find the pertinent [SectionName] for the parameter you want to add, or whose value you want to edit.

IMPORTANT: Some parameters in different sections share the same keyname, so it is very important
that parameter values be entered and edited in the correct sections.

3 Add the parameter or edit its value, as appropriate.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

316
Appendix A: How do I ...?
 4 Repeat steps 2 and 3 as necessary to make as many additions and changes to the parameters as needed.
5 Close Notepad.
Notes Migration Manager will then copy the new parameter value(s) back into the SQL database.

How do I migrate from a Notes environment

with Symantec E-Vault?
When migrating from a Notes environment with Symantec E-Vault, Exchange propagation issues may ifere with
Migrator for Notes to Exchange setting custom attributes when the destination mailbox has never been accessed
either by Outlook or by the migration application. One simple work-around would be to first run a "dummy"
migration (e.g., use a date filter where date > 1/1/2100) to open all the target mailboxes before running the real
migration.

How do I migrate to an Exchange environment

with a CAS Array?
The following instructions do not apply to Exchange 2013. See this Knowledge Base article for instructions for
Exchange 2013.
To configure Migrator for Notes to Exchange for an Exchange target environment configured with a CAS (Client
Access Server) array:
1 In the Exchange management console, point at the Mailbox server.
2 In the Migrator for Notes to Exchange Global Defaults, in the [Exchange] section, set:
Server=array.sitraka.com
3 Create, modify and apply a throttling policy for the migration:
a Create the new policy by this command:
New-ThrottlingPolicy QuestMigration
b Modify the policy with these settings:
set-throttlingpolicy QuestMigration -RCAMaxConcurrency $null -RCAPercentTimeInAD
$null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null
c Apply the policy to the Quest migration account:
Set-Mailbox [MNEServiceAccount] -ThrottlingPolicy QuestMigration
4 Set WinRM on all relevant boxes:
winrm set winrm/config/winrs '@{MaxShellsPerUser="150"}'
winrm set winrm/config/winrs '@{MaxConcurrentUsers="100"}'
winrm set winrm/config/winrs '@{MaxProcessesPerShell="150"}'
winrm set winrm/config/winrs '@{AllowRemoteShellAccess="true"}'
set-executionpolicy unrestricted; get-executionPolicy

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

317
Appendix A: How do I ...?
How do I prepare the SQL database for mailbox-
enabling (if AD is configured for a resource
forest and a user forest)?
This section applies only if your AD/Exchange environment is configured for a resource forest and a user forest,
with corresponding user accounts. In that case, you must configure the Global Default Settings in Notes
Migration Manager, and then prepare (or verify) the values in a column of the exported directory data, for the Data
Migration Wizard to properly associate the resource accounts with the user accounts and properly enable
mailboxes.
Before you begin, you must determine which column in the SQL database will correspond to which AD attribute,
for the wizard to match corresponding user accounts in the resource forest and user forest. The column
(AdSearchCol) and attribute (AdAttribute) are both specified in the [ActiveDirectory2] section of the Global
Default Settings of Notes Migration Manager:
• AdSearchCol: The column in the SQL database whose values the program should search for each
particular AdAttribute value, to match corresponding user accounts in the resource forest and user forest.
Note that the column specified here and its per-user values must exist before the Data Migration Wizard is
run.

IMPORTANT: In the current Migrator for Notes to Exchange version, this AdSearchCol parameter
value must be set to SearchKey2 (the default for this parameter) for the mailbox-enabling process to
succeed.

• AdAttribute: The AD attribute whose values the program should read in the AdSearchCol column of the
SQL database, to match corresponding user accounts in the resource and user forests. For example:
[ActiveDirectory2]
AdSearchCol=SearchKey2
AdAttribute=userPrincipalName
... tells the wizard to match AD objects with users such that the value of each AD object’s
userPrincipalName attribute matches the value of the corresponding user’s SearchKey2 column in the SQL
database.

To configure the Global Default settings:

1 Within Notes Migration Manager, select File | Global Default Settings. The program then opens the
program’s configuration settings into Windows Notepad. Within Notepad, the settings look like the contents
of an INI file, but they are saved as a part of the SQL database rather than as an independent INI file.
2 In the [ActiveDirectory2] section, set the appropriate parameter value for AdAttribute, as described above.
3 Close Notepad. Notes Migration Manager will then copy the new parameter value back into the SQL
database.

If you need to enter or edit the AdSearchCol column values in the SQL database:
1 Within Notes Migration Manager, in the Export Notes Directory screen: Click Export objects to TSV. A
dialog box will prompt you for a destination folder and filename for the exported file.
2 Use Microsoft Excel (or some other program that can edit a tsv-format file) to enter or edit the contents of
the column you have designated as the AdSearchCol column.
3 In the Export Notes Directory screen: Click Import objects from TSV to import the edited .tsv file into the
SQL database. A dialog box will prompt you for the filename and its location.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

318
Appendix A: How do I ...?
How do I add to the list of AD attributes
available for the merge function?
The Provisioning Wizard associates contacts with AD objects by comparing the unique values of a particular AD
object attribute to the unique values of a corresponding column in the SQL database. Where these values match,
the associated contact and AD object are assumed to represent the same entity, and the two are merged. During
the wizard run, the Choose Your Method... screen requires that you specify the AD attribute and the database
column to use for the comparisons. You specify the attributes and columns using drop-down lists of available
options for the database column and AD attribute, respectively.
By default, the list of choices for the AD attribute contains these 26 options:

cn sAMAcountName distinguishedName extensionAttribute1

mail userPrincipalName altRecipient extensionAttribute2
mailNickname targetAddress legacyExchangeDN extensionAttribute3
proxyAddresses employeeNumber ... [to 15]

The 26 defaults are defined by a series of ADML[#] parameters in the [ActiveDirectoryMatchList] section of the
Global Defaults and Task Parameters:
[ActiveDirectoryMatchList]
Count=26
ADML0=cn
ADML1=mail
ADML2=mailNickname
ADML3=proxyAddresses
ADML4=sAMAccountName
[...]
ADML25=extensionAttribute15
If the AD attribute you want to use is not among the 26 defaults, you can add one or more other attributes to the list
by defining each addition in the Global Defaults or Task Parameters. See How do I add or edit program
parameters? above for the procedure to add and edit these parameter(s):
• ADML[#]=<AttribName>
Each ADML[#] parameter names an AD attribute that the Provisioning Wizard will include in its list of
options, from which one attribute must be chosen to facilitate the matching of contacts with AD objects. The
digit(s) appended to an ADML[#] key name differentiate one parameter from another. The multiple ADML[#]
parameters need not appear in numerical order, and need not form an unirupted numerical sequence. But
the wizard will read only ADML[#] parameters whose differentiating digits are less than a value specified by
a Count parameter (see below).

NOTE: Migrator for Notes to Exchange’s Provisioning Wizard merge function requires that any AD
attribute added to the list be replicated to the Global Catalog. You can configure AD to replicate an
attribute to the Global Catalog; see How do I configure AD to replicate an AD attribute to the Global
Catalog?

• Count=<##>
A limit to the number of ADML[#] parameters (see above) that the Provisioning Wizard will process in this
section. The wizard will read only ADML[#] parameters whose differentiating digits are less than the Count
parameter value. For example, if:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

319
Appendix A: How do I ...?
 [ActiveDirectoryMatchList]
Count=6
ADML0=cn
ADML1=mail
ADML2=mailNickname
ADML3=proxyAddresses
ADML4=sAMAccountName
ADML5=userPrincipalName
ADML6=targetAddress
ADML7=employeeNumber
... then the wizard will read all the parameters except ADML6 and ADML7, since Count=6, and neither 6
nor 7 is less than 6.
If unspecified, the Count parameter defaults to 26. If specified, the parameter must occur as the first line of
the section, as shown above.
For example: If the ADML[#] parameters are set for only their 26 defaults, and you want to add a single new AD
attribute option, you would add an ADML26 parameter and change the Count parameter to 27, like this:
[ActiveDirectoryMatchList]
Count=27
ADML0=cn
ADML1=mail
ADML2=mailNickname
ADML3=proxyAddresses
ADML4=sAMAccountName
[...]
ADML25=extensionAttribute15
ADML26=NewAttributeName

How do I configure AD to replicate an AD

attribute to the Global Catalog?
If the AD attribute you want to use for the Provisioning Wizard is not among the 26 defaults, you can add one or
more other attributes to the list by defining each addition in the Global Defaults or Task Parameters. This
procedure is explained elsewhere in this Appendix (see How do I add to the list of AD attributes available for the
merge function?).
Any AD attribute added to the list must be replicated to the Global Catalog, or the merge function will fail. You can
configure AD to replicate an AD attribute to the Global Catalog as explained in the following procedure:

CAUTION: This procedure manipulates AD configuration parameters, and an error could generate adverse
consequences throughout the Active Directory environment. Use extreme caution whenever
manipulating AD configuration parameters in this way.

To configure AD to replicate an AD attribute to the Global Catalog:

1 At a computer where you can manage your Active Directory, open a command prompt and e:
regsvr32 schmmgmt.dll
2 Launch the Microsoft Management Console (mmc.exe).
3 On the File menu, select Add/Remove Snap-in.
4 Click Add, select Active Directory Schema, click Add, and then return to the main window.
5 Click Attributes, and wait for the list to expand.
6 Find the name of the attribute you want to replicate, then right-click it and select Properties.
7 Select Replicate the attribute to the Global Catalog, and click OK.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

320
Appendix A: How do I ...?
 8 Wait for the Global Catalog to replicate the attribute.

How do I specify per-user locations for Notes

source data?
Per-user locations for users’ source data are (if necessary) specified in the SQL database. To edit the contents of
that database, you must export the data to a .tsv (tab-separated-values format) file, then edit the contents of the
table, and then import the edited .tsv file back into the SQL database.

NOTE: After importing values into any of the listed columns, you must run the Notes Data Locator Wizard so
the data stores that are specified by the values you provide are located and the user's datastore information
is updated. To run the Notes Data Locator Wizard, select the Locate Notes Data Stores page in Notes
Migration Manager.

For PABs: To designate the locations of user PABs, enter the appropriate per-user values into one of these
columns (not both):
• PABPaths column: The specific UNC path and filename for a user's Notes address book(s). Multiple
address books can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and
file name are given, and file ownership is not checked. If a directory (only) is specified, all PABs found in the
directory are assumed to be owned by the user. Examples:
\\server\data\addr1.nsf | \\server\data\addr2.nsf
\\server\data\user\address_book.nsf
\\server\data\
• SharedPabDirs column: A file system directory or Notes server directory that contains NSF files for
multiple users. This column can be used to specify a more specific set of directories to scan for a user's
data, so the application can scan a subset of a larger shared directory structure and determine the owner
based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a
directory structure and you can't be certain that all address books belong to one user. If a file system path
is specified here, ownership is checked based on the profile documents and/or ACLs. Examples:
\\server\data\groupdir
\\server\data\groupdir\address_book.nsf
For Archives: To designate the locations of user archives, enter the appropriate per-user values into one of these
columns (not both):
• ArchivePaths column: The specific UNC path and filename for a user's Notes archive file(s). Multiple
archives can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file
name are given, and file ownership is not checked. If a directory (only) is specified, all archives found in the
directory are assumed to be owned by the user. Examples:
\\server\data\arch1.nsf | \\server\data\arch2.nsf
\\server\data\user\archive_jdoe.nsf
\\server\data\
• SharedArchiveDirs column: A file system directory or Notes server directory that contains NSF files for
multiple users. This column can be used to specify a more specific set of directories to scan for a user's
data, so the application can scan a subset of a larger shared directory structure and determine the owner
based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a
directory structure and you can't be certain that all address books belong to one user. If a file system path
is specified here, ownership is checked based on the profile documents and/or ACLs. Examples:
\\server\data\archives
\\server\data\archives\archive_jdoe.nsf
For Mail Files: To specify per-user locations and filenames for users’ source mail files in the SQL database rather
than from entries in the Data Migration Wizard, enter the appropriate per-user values into this column:
• MailFilePath column: The specific path and NSF filename to a user's mail file, used when an administrator
knows the specific path and NSF file name for each user. Example:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

321
Appendix A: How do I ...?
 \\server\home\user\jdoe.nsf
If the MailFilePath column does not exist or is left empty, the program will look for the user's mail file in the
path entered in the Notes Data Locator Wizard (on the Specify Notes Mail File Directories screen).

How do I specify per-user destination locations

for users’ PST files?
Per-user destination locations for users’ new PST files are (if necessary) specified in the SQL database. To edit
the contents of the SQL database, you must export the data to a .tsv (tab-separated-values format) file, then edit
the contents of the table, and then import the edited .tsv file back into the SQL database.
To specify per-user destinations for users’ new PST files in the SQL database rather than from entries in the Data
Migration Wizard, enter the appropriate per-user values into this column:
• PSTdir column: The directory where PSTs are stored for the user, used if each user's PST will go to a
separate directory. Normally the admin would specify a central location for the wizard to create all PSTs,
and the wizard would create a subtree under that. If the admin would rather put each PST in each user's
home directory, then each user's home directory can be added here. Example:
\\server\home\user

How do I specify whether to migrate to a single

PST file (per user) or multiple PST files?
When migrating to .pst files, a program parameter in the Global Defaults and Task Parameters lets you specify
whether the Data Migration Wizard should migrate all data into a single .pst file per user, or to multiple .pst files.
The boolean parameter that controls this option is UseSeparatePSTs. By default (1), data is migrated to multiple
.pst files. But:
UseSeparatePSTs=0
... tells the wizard to migrate all data into a single .pst file per user.
If you are unfamiliar with the procedure to edit program parameters, see How do I add or edit program
parameters? elsewhere in this Appendix.

How do I migrate Notes custom attributes?

A Notes message contains several standard attributes such as the From, To and Subject fields, and can also
include user-defined fields. The Data Migration Wizard and SSDM can migrate custom Notes attributes from email
messages and Notes contacts to unused properties in Exchange, but only if the migration application knows which
properties in the target correspond to which attributes in the source. The migration of custom attributes requires
that the source-to-target attribute associations be mapped in a tsv data file before the migration so that Migrator for
Notes to Exchange (MNE) can refer to the file to migrate the attributes.
The attribute-mapping file must be a Unicode (not ANSI) file named customattrs.tsv located in the default
installation folder for the Data Migration Wizard (typically C:\Program Files\Quest\Migrator for Notes to Exchange),
or in the folder containing notesdtapp.exe if you want to migrate Notes custom attributes via the SSDM. MNE
installs a Unicode attrs.tsv file, with the same column headings required for customattrs.tsv, that you can use as a
template to create the customattrs.tsv file.

To create and prepare the customattrs.tsv file

1 Use a text editor to open attrs.tsv, and save the open copy under the new name customattrs.tsv. Ensure
you save customattrs.tsv as a unicode (not ANSI) file, in the folder(s) as previously specified. Delete any
data rows that may appear in the copy.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

322
Appendix A: How do I ...?
 2 Enter a data row for each Notes custom attribute you want to migrate, as follows:
▪ ID: Name of the custom attribute—a unique string that distinguishes this row’s custom attribute from
all others in the file.
+

IMPORTANT: If any data rows remain in the original attrs.tsv file, ensure that no ID value in
customattrs.tsv is the same as any ID value in attrs.tsv. Custom attributes will not migrate
correctly if any ID value appears in both files.

▪ SourceProperty: Name of an attribute that has been added to a Notes mail message, or a Notes
contact, to be migrated to a property in Exchange.
▪ TargetPropertySet: The GUID for the target property set, which must be one of these values:
PS_PUBLIC_STRINGS
{HHHHHHHH-HHHH-HHHH-HHHH-HHHHHHHHHHHH}
... where each 'H' is a hexadecimal character, with letters capitalized.
If the TargetPropertySet value is PS_PUBLIC_STRINGS, the familiar GUID for the set named will
be substituted for the string provided.
TargetPropertySet can be left blank, but in that case TargetProperty (see following) must be an
integer property ID in the range 0x0000-0x7FFF.
▪ TargetProperty: Name of the corresponding MAPI property in Exchange. A hexadecimal user-
property value is created in Exchange on each migrated mail message or contact with the Notes
property, which will hold the value. The hexadecimal values of the created properties are reported in
the log (search for "custom attr" in the log file).
If TargetPropertySet (above) is left blank, this TargetProperty value must be specified as a 16-bit
integer in the range 0x0000- 0x7FFF that is not already defined for some other MAPI property.
▪ TargetPropertyType: Data type of the MAPI property, which must logically correspond to the data
type used in Notes. Valid values are:
STRING
MV_STRING
SYSTIME
BOOLEAN
LONG
Also, "PT_" may be prepended to any of the five types above, so valid values include PT_STRING,
PT_MV_STRING, etc.
3 Save and close the updated customattrs.tsv file.
For example, a typical customattrs.tsv file might look something like this:

ID SourceProperty TargetPropertySet TargetProperty TargetPropertyType

Attr1 ArchiveId {D0F41A15-9E91-D111-84E6-0000F877D428} Archive ID STRING
Attr2 ArchivedDate {D0F41A15-9E91-D111-84E6-0000F877D428} Archived Date STRING
Attr3 SaveSetId {D0F41A15-9E91-D111-84E6-0000F877D428} Saveset ID STRING
Attr4 RetentionCategory {D0F41A15-9E91-D111-84E6-0000F877D428} Retention Category STRING
Attr5 HasAttachments {D0F41A15-9E91-D111-84E6-0000F877D428} HasAttachments STRING

Troubleshooting problems in migrating Notes custom

attributes
You can use Microsoft’s MfcMapi.exe utility to view the property and its value, if they have been created. (The
utility is a free download from Microsoft. You can search in Google for "mfcmapi" and visit the
www.microsoft.com/downloads link.) Most problems in migrating custom attributes can be diagnosed by these
quick tests:
• Verify the target property specified in the customattrs.tsv file does not already exist, and that the target
property is in the correct format. See About MAPI properties below for more information about this.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

323
Appendix A: How do I ...?
 • Verify that the customattrs.tsv file is UNICODE, not ANSI.
• Verify that the last line in the customattrs.tsv file is followed by a line feed and carriage return (achieved by
positioning the cursor at the end of the last line and pressing E).
• If any data rows remain in the original attrs.tsv file, ensure that no ID value in customattrs.tsv is the same
as any ID value in attrs.tsv. Custom attributes will not migrate correctly if any ID value appears in both files.

About MAPI properties

A named property's name is a property-set GUID and an ID that is either a 32-bit integer or a string. A 16-bit
integer alias in the range 0x8000 to 0xFFFF is assigned to the named property by MAPI. That alias is mailbox-
specific.
An unnamed property's name is a 16-bit integer in the range 0x0001 to 0x7FFF. That 16-bit integer is valid in all
mailboxes. Examples of unnamed properties are 0x0070 (i.e., PR_CONVERSATION_TOPIC) and 0x6656, both of
which happen to be used by MAPI. So these two examples cannot be used as target property values for message
attributes since they are already used, although they may be used to map Notes contact attributes to Exchange.
A custom property can be unnamed or named. If it is unnamed, you must select a 16-bit integer TargetProperty in
the range 0x0001 to 0x7FFF that is not already in use by MAPI. If it is named, you can select any property-set
GUID. If you select a property set that is already in use, you must choose a 32-bit integer or string ID that is not
already in use in that property set. If you select a brand new property-set GUID, you need not worry about IDs
already in use because there will not be any.
If you want named custom properties, Quest recommends you use the PS_PUBLIC_STRINGS property-set GUID,
(PS_PUBLIC_STRINGS being an alias for {00020329-0000-0000-C000-000000000046}), and use string IDs with
a prefix that is unique to your application (like "Quest-").

How do I customize the placeholder message

that the Data Migration Wizard substitutes for
encrypted messages?
Since the Data Migration Wizard does not migrate encrypted messages, it will substitute placeholder messages for
encrypted messages in your users’ Exchange mailboxes. The Self-Service Desktop Migrator will then replace the
placeholder messages with the real messages as it de-crypts and migrates them.
You can customize the content of this placeholder message by creating a simple text file of the content, and then
editing the Global Default Settings to specify the use and location of the file. The message can be a simple
notification, or may include instructions for launching and running the Self-Service Desktop Migrator to migrate the
encrypted message bodies. For information about customizing the user iface of the Self-Service Desktop Migrator,
see How to customize the SSDM (in the Migrator for Notes to Exchange Scenarios Guide).
After you create the text file, edit the Global Default Settings (see How do I add or edit program parameters?):
• In the [General] section, set UseFilteredBodyMsg=1, and set an appropriate parameter value for
BodyLostDueToEncryptionMsg (the full path and filename of the customized text file). For example:
[General]
UseFilteredBodyMsg=1
BodyLostDueToEncryptionMsg=c:\temp\replace.txt
Then use Notepad or some other text editor to open the notesdtapp.ini file, set the same two parameter values in
the [General] section of that file, and save the changes to notesdtapp.ini.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

324
Appendix A: How do I ...?
How do I customize the placeholder message
that the Data Migration Wizard substitutes for
filtered attachments?
The Data Migration Wizard does not migrate encrypted messages or their attachments, so it substitutes
placeholder messages for the filtered attachments in your users’ Exchange mailboxes. The Self-Service Desktop
Migrator can then replace the placeholder messages with the corresponding attachments as it de-crypts and
migrates the associated messages.
You can customize the content of this placeholder message by creating a simple text file of the content, and then
editing the Global Default Settings to specify the use and location of the file. The message can be a simple
notification, or may include instructions for launching and running the Self-Service Desktop Migrator to migrate the
encrypted message bodies. For information about customizing the user iface of the Self-Service Desktop Migrator,
see How to customize the SSDM (in the Migrator for Notes to Exchange Scenarios Guide).
After you create the text file, edit the Global Default Settings (see How do I add or edit program parameters?):
• In the [General] section, set UseFilteredAttachmentMsg=1, and set a suitable parameter value for
AttachmentLostDueToEncryptionMsg (the full path and filename of the customized text file). Example:
[General]
UseFilteredAttachmentMsg=1
AttachmentLostDueToEncryptionMsg=c:\temp\replace2.txt
Then use Notepad or some other text editor to open the notesdtapp.ini file, set the same two parameter values in
the [General] section of that file, and save the changes to notesdtapp.ini.

How do I create or edit a template for

personalized user-notification emails?
The Data Migration Wizard can generate personalized (mail-merge) notification emails to end users to inform them
of their migration and provide useful information to help them in their transition. The wizard can also generate
migration summary emails to administrators to keep them apprised of migration status.
The wizard lets you send the following messages:
• "You’ve been migrated" messages to Notes mailboxes: Generates a personalized mail-merge email to
the Notes mailbox of every user in the collection, notifying them of their migration to the Exchange server.
(The wizard inserts these messages directly into the users’ Notes mailboxes, so they are not icepted by
any forwarding rules that would re-route them to Exchange.)
This email typically explains to the user that he or she has been migrated to Exchange, and should use the
Outlook client for all future email and calendar activities. The email also typically provides each user’s new
Outlook login credentials, and any other special instructions or tips that may be helpful.
• "Welcome to Exchange" messages to Exchange mailboxes: Generates a personalized mail-merge
email to the Exchange mailbox of every user in this collection, welcoming him or her to the Exchange
environment and the Outlook client, and typically including information (or a link) to orient users to their new
tools.
• Send "Migration summary" messages to administrators: Generates a personalized mail-merge email
to all the SMTP addresses that are specified in the Recipient SMTP address text box. The email provides
the migration summary and often includes an attachment containing logs of the migration statistics for each
user in the collection. The email message might also include an attachment that contains a log of deferred
Notes emails to be sent at a future date and time by Domino.
The first two options were developed to facilitate notification emails to users at the time of migration, but the
feature can also be used to send personalized emails to users before or after they are migrated. You can use such
pre- and post-migration notifications to announce an upcoming migration, explain the implications to end users,
and tell them what they can expect and what will be expected of them.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

325
Appendix A: How do I ...?
To send pre/post-migration emails, use the process for creating or editing a template described in this section, and
use the Data Migration Wizard only to send the messages (and not mailbox-enable users or migrate user data).
See How do I send pre- or post-migration notification emails to end users? on page 331 for more information.
The third option can be used to provide migration summary information to administrators and migration teams. An
email attachment can provide detailed migration status information for each user in a collection. Another
attachment can provide a list of Notes emails that were scheduled to be sent by Domino at a future date and time.
As in any mail-merge process, the template files contain variables that are replaced with values as each email is
created. The wizard merges a template file with per-user variable values drawn from the collection’s data table (in
the SQL database), and/or with environment or system variables. (The wizard draws the per-user values from an
INI file, but the INI-file values are drawn from the SQL database and are rewritten, per user, as each user is
processed.)
Migrator for Notes to Exchange installs with the following standard template files:
• ybm_template.html: for delivery to users’ Notes mailboxes immediately after migration when migrating to
an on-premises Exchange server, or to a hosted Exchange environment other than Office 365.
• ynma_template.html: for delivery to users’ Notes mailboxes immediately after migration when migrating to
Office 365.
• migration_summary_template.html: for delivery to the specified SMTP addresses of the administrators who
should receive migration summary emails.
• wte_template.html: for delivery to users’ Outlook mailboxes immediately after migration when migrating to
any target type.
• ada_template.html: for delivery to users' Notes mailboxes when migrating to on-premises Exchange. Tells
the users that their AD accounts have been created and provides account information and passwords.
• o365_pwreset.html: for delivery to user's Notes mailboxes when migrating to Office 365. Tells the users
that their Office 365 account passwords have been reset.
The Data Migration Wizard prompts you to specify a template file for each merged email you want to send. You
can choose one of the standard templates, or you can create and use your own templates. You can also edit any
of the template files to add or delete or modify content to better suit your needs.

Rules for mail-merge template files

A mail-merge template file must conform to the following specifications:
• The template file must be an HTML file with file extension .html or .htm.
• A template file can contain UNICODE, UTF-8 or ANSI characters. UTF-16 is not supported. If an HTML tag
specifying charset is included in the file, the charset is sent with each email.
• Maximum file size (including the merge variables, but before the variables are expanded) is 64K–1 byte. If
the file is 64K or larger, the email will not be sent.
• Maximum length of any single line in the file (after any merge variables are expanded) is 512 bytes, or 256
UNICODE characters. Any line that exceeds this limit will be omitted from the merged email. This may vary
from user to user, as variables in the form are replaced with user-specific values.
A variable specification in a mail-merge template is enclosed in a pair of dollar signs, such as: $VarSpec$. (Also
see the default templates installed with the applications to see how variables are used within a template file.)
A template can contain any combination of INI variables, environment variables, and system variables.
Environment and system variables characterize the wizard operating environment—the current date and time, for
example— and are not unique per user.
An INI variable is so named because its value is drawn from the associated INI file that the wizard checks as it
processes users in a collection. The wizard generates this "scratch" INI file at the start of every run by copying
parameter values from the wizard Task Parameters. The [User] section of the INI file contains only a single user’s
data drawn from the collection data table in the SQL database, but this per-user data is rewritten to the INI file
before processing of each user so that the correct values are available to the wizard for each user processed. The
wizard can check the [User] section of the INI file for per-user values when generating a notification email.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

326
Appendix A: How do I ...?
Using "INI" variables in a mail-merge template
An INI replacement variable refers the wizard to a particular parameter value within a particular section of the INI
file, and takes the form $Section:Param$. For example:
• $User:DisplayName$: Specifies the value of the DisplayName parameter in the [User] section of the INI
file.
• $Notes:Server$: Specifies the value of the Server parameter in the [Notes] section of the INI file.
• $Exchange:Server$: Specifies the value of the Server parameter in the [Exchange] section of the INI file.
The $Notes:Server$ and $Exchange:Server$ examples above are commonly used in merge templates, but the
most commonly used INI variables are drawn from the [User] section, representing values that vary per user:
• $user:displayname$: The user’s Notes user name, from the SQL DB DisplayName column.
• $user:TargetAddress$: The user’s Exchange email address, from the SQL DB TargetAddress column.
• $user:MovedMsgCnt$: the number of the user’s mail messages that were migrated.
• $user:MovedContactCnt$: the number of the user’s contacts that were migrated.
• $user:MovedApptCnt$: the number of the user’s calendar items that were migrated.
• $user:MovedEncryptedMsgCnt$: the number of the user's encrypted messages (found in the Notes
source, but not migrated).

Using environment and system variables in a mail-merge

template
An environment or system variable in a mail-merge template takes the form $env:VarName$, as in these
examples:
• $env:date$: the date system variable
• $env:time$: the time system variable
You can view Windows default environment and system variables through the System utility in the Windows
Control Panel: On the Advanced tab of System Properties, click Environment Variables. You can also define
new variables in the same Environment Variables dialog box.

Batch-migration process

How do I synchronize directory data and update

the SQL database?
If synchronization of coexisting directories during the transition period is not a high priority, the administrator can
add and delete users and update user data in the Exchange environment (only), using Exchange administration
software.
If it is important to keep the two directories synchronized throughout the transition period, you should:
1 Enter any staff changes in the Domino environment as they occur.
2 Prior to the migration of each user collection, perform the following tasks:
a Use the Quest Coexistence Manager for Notes (CMN) Directory Connector to update Active
Directory to match the updated Domino directory. (You do not need perform this step explicitly if the
CMN Directory Connector is scheduled to automatically update the directories at regular intervals.)

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

327
Appendix A: How do I ...?
 b After the directories are updated, update the SQL database by using the Migrator for Notes to
Exchange Directory Export Wizard to re-export Domino directory data. (Again, you do not need to
perform this step explicitly if you used Notes Migration Manager to schedule recurring runs of the
Directory Export Wizard—for example, 30 minutes after each scheduled update run of the CMN
Directory Connector.)
c Check the export results (the summary table in the Export Notes Directory screen) to verify the
integrity of the exported data. Any format or translation errors should be apparent; missing users, or
inappropriate data forms in any fields would indicate that the export process was corrupted or
otherwise unsuccessful.
3 For any already-migrated user that leaves the organization, delete the user from the Exchange server,
using Exchange administration software.
The most efficient updating strategy is to automate the process by scheduling the CMN Directory Connector and
Migrator for Notes to Exchange Directory Export Wizard to automatically run successively, in tandem, at regular
recurring times—such as every night at midnight or 2 am.

Other features
The following sections describe additional features that may be used to perform tasks in Migrator for Notes to
Exchange:
• How do I schedule tasks?
• How do I troubleshoot service startup permissions?
• How do I send pre- or post-migration notification emails to end users?
• How do I perform an offline migration?
• How do I migrate resources?
• How do I migrate mail-in databases?
• How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV files?

How do I schedule tasks?

Scheduled tasks are run using the Migrator for Notes to Exchange (MNE) Task Scheduler (qsched.exe). The Task
Scheduler runs as a Windows service and is installed when you install Migrator for Notes to Exchange. The Task
Scheduler is configured by default to autostart (upon every workstation reboot) and run under the credentials of
the administrator account that runs the MNE installer.
The Task Scheduler polls the MNE database at regular intervals for any scheduled tasks and runs those tasks at
the designated times.
See Admin Guide chapter 13 for information about the Task Scheduler (qsched.exe).

How do I troubleshoot service startup

permissions?
If the MNE Task Scheduler experiences logon failures when trying to start the service, the following information will
help you resolve them.
When a service does not start because of a logon failure, you might find error messages in the system event log
when you restart the server:
Source: Service Control Manager
Event ID: 7000

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

328
Appendix A: How do I ...?
 Description:
The %service% service failed to start due to the following error:
The service did not start due to a logon failure.
No Data will be available.Source: Service Control Manager
Event ID: 7013
Description:
Logon attempt with current password failed with the following error:
Logon failure: unknown user name or bad password.
No Data will be available.
When you attempt to manually start the service, you might see the following error message, even though the user
account is a valid user:
Microsoft Management Console
Could not start the %service% service on Local Computer
Error 1069: The service did not start due to a logon Failure.
This behavior can occur for any of these reasons:
• The password has changed on the account that the service is configured to use to log on.
• The password data in the registry is damaged.
• The right to “log on as a service” is revoked for the specified user account.
To resolve these issues, you can configure the service to use the built-in system account, change the password for
the specified user account to match the current password for that user, or restore the user's right to “log on as a
service”.

How to configure user rights

If the right to “log on as a service” is revoked for the specified user account, restore the right by performing the
following steps:

in the Domain controller domain

If the user is in an Active Directory domain:
1 Start the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in.
2 Right-click the Organizational Unit (OU) in which the user right to log on as a service was granted. By
default, this is in the Domain Controller OU.
3 Right-click the container and then click Properties.
4 On the Group Policy tab, click Default Domain Controllers Policy and click Edit.
This starts Group Policy Manager.
5 Expand the Computer Configuration object by clicking the plus sign (+) next to the policy object.
6 Under the Computer Configuration object, expand Windows Settings, and then expand Security
Settings.
7 Expand Local Policies, and click User Rights Assignment.
8 In the right pane, right-click Log on as a service, and click Security.
9 Add the user to the policy, and click OK.
10 Quit Group Policy Manager, close Group Policy properties, and close the Active Directory Users and
Computers MMC snap-in.

On a member server
If the user is a member of a stand-alone member server:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

329
Appendix A: How do I ...?
 1 Start the Local Security Settings MMC snap-in.
2 Expand Local Policies and click User Rights Assignment.
3 In the right pane, right-click Log on as a service and click Security.
4 Add the user to the policy and click OK.
5 Close the Local Security Settings MMC snap-in.

How to configure service logon information

To configure the password for the specified user account to match the current password for that user, use the
following steps:
1 Click Start, select Settings, click Control Panel and double-click Administrative Tools.
2 Double-click Services.
3 Right-click the appropriate service and click Properties.
4 On the Log On tab, change the password and click Apply.
5 On the General tab, click Start to restart the service.
6 Quit the Services tool.

How to configure the service to start up with the built-in

system account
If the service still does not work with the specified user account, you can configure the service to start up with the
built-in system account using the following steps:
1 Click Start, select Settings, click Control Panel, and then double-click Administrative Tools.
2 Double-click Services.
3 Right-click the appropriate service, and then click Properties.
4 On the Log On tab, click Local System Account, and then click Apply.

NOTE: You typically do not need to configure a service to interact with the desktop, so you can leave
the Allow service to interact with desktop check box clear.

5 On the General tab, click Start to restart the service.

6 Exit the Services tool.
When you attempt to open the properties of a service using the Services tool in Control Panel, the computer may
stop responding (hang) and/or can display this error message:
The RPC Server is unavailable
This message can occur due to a logon failure with the Remote Procedure Call (RPC) service or some other
dependent service. Some services cannot start until after dependency services have started (for example, the
Workstation service).
If you cannot start the Services tool, follow these steps to configure the service to use the built-in system account:
1 Start Registry Editor (Regedit.exe).

CAUTION: These steps tell you to modify the registry. Serious problems might occur if you modify the
registry incorrectly. Ensure that you follow these steps carefully. Quest strongly recommends that
you back up the registry before you modify it so you can restore the registry if a problem occurs.

2 Locate the ObjectName value in this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceName

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

330
Appendix A: How do I ...?
 3 On the Edit menu, click Modify.
4 In the Value Data box, type localsystem and click OK.
5 Exit the Registry Editor.
6 Attempt to restart the service. You may need to restart the computer for some services to restart properly.
If you cannot start Registry Editor, you can modify the service account information by performing a parallel
installation. See the Microsoft Knowledge Base for information about parallel installations.
Although most system services are configured to use the system account credentials for logon by default, you can
configure them to use a specific user account instead. When a user's password is changed, the password
information field is not automatically changed for services.
You can start a service with the local system account or by specifying a specific user account and password. If you
choose to specify a user account and password, it is important that the account name and password remain
constant. For example, this account should not be required to change password or be renamed. If these two
events (or other similar events) occur, you should also update the logon credentials for the service.

How do I send pre- or post-migration

notification emails to end users?
The Data Migration Wizard contains a feature originally developed to facilitate notification emails to users at the
time of migration, but you can use this feature to send personalized emails to users before or after they are
migrated. For example, you can use notifications to announce an upcoming migration, explain the implications to
end users, and tell them what they can expect and what will be expected of them.
To send pre- or post-migration emails you can run the Data Migration Wizard to only send the messages—but not
mailbox-enable users or perform any other migration or administrative functions.

To send a notification email to end users without migrating data:

1 Perform the Pre-Migration Preparations described in chapter 2 or 3 of the Migrator for Notes to Exchange
Scenarios Guide.
2 Prepare a suitable mail-merge template file, as described in this Appendix. See How do I create or edit a
template for personalized user-notification emails?
3 On the Select Notes Administrative Operations screen, select the Send migration notification messages
check box. This option allows you to send mail merge messages when a data migration is not in progress.
The Configure mail-merge messages to migrating users screen is displayed.
4 On the Configure mail-merge messages to migrating users screen, define the personalized (mail-merge)
notification emails you want the wizard to send to the users in this collection and click Next.

How do I perform an offline migration?

Migrator for Notes to Exchange supports offline migration—a strategy in which Notes source data that was
previously extracted from Notes is migrated directly to the Exchange target.
An offline strategy can be useful:
• if problematic bandwidth makes direct connection impractical (e.g., if the source and target servers are far
apart—geographically and/or from a network perspective).
• if the Domino environment is managed by a third party that does not allow admin access.
• in a disaster scenario, where the Domino server is destroyed but backup NSF files survive.
An offline migration can be accomplished by either of these two approaches:

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

331
Appendix A: How do I ...?
 • Notes source data is saved to replica or otherwise-disconnected NSFs and the MNE Data Migration Wizard
migrates from the NSF files directly to Exchange.
• The MNE Data Migration Wizard migrates Notes source data to PST files (rather than directly to an online
Exchange target), and the PST files are imported into the Exchange target by some other application. The
Quest Migration Manager for PSTs would be a good choice.
See the “Offline migration” topic in chapter 1 of the Migrator for Notes to Exchange Scenarios Guide for more
information, including requirements and guidelines, for offline migrations.

How do I migrate resources?

Exchange 2010 and later permit the differentiation of resources into three types: Room, Equipment and Online
Meeting. The Directory Export Wizard copies the resource type designations from Domino into the object records
in the SQL database, and the Provisioning Wizard then provisions the objects into Active Directory (AD) with the
type designations intact. When the Data Migration Wizard mailbox-enables those objects, the mailboxes are
created with the correct resource type.
In a typical scenario, AD security objects have been created for all users and resources, and a dirsync creates
mail-enabled AD contacts that correspond to existing security objects. The Provisioning Wizard merges the
contact information (including resource types) into the existing security objects, and deletes the contacts, leaving a
single mail-enabled security object in AD per user or resource. After the merge process creates the mail-enabled
security objects, the Data Migration Wizard can mailbox-enable the objects.
Note: If a resource appears in a collection but no corresponding security object or contact resides in AD, the
Provisioning Wizard can be configured to overlook the missing entities. This feature is enabled or disabled by a
check box on the Choose the Container for User Objects screen:
[ ] Create new objects for recipients that do not already exist in Active Directory
Select the check box if you want to create a new mail-enabled object in AD when none is found to correspond with
a user (resource) in the collection. Leave the check box clear to disable that feature. Any such new objects are
created in the container specified by the User Container text box (on the Choose the Container for User Objects
screen).

NOTE: Use this Create new objects... feature only if no corresponding contact or user object already exists
in AD. If an AD user object exists without a corresponding contact, the wizard will mail-enable the existing
object.

How do I migrate mail-in databases?

Migrator for Notes to Exchange migrates Notes mail-in databases, such as Resources, to Exchange as Shared
mailboxes. The Directory Export Wizard recognizes mail-in databases as distinct from other (user) mailboxes and
identifies them as Mail-in Databases in Notes Migration Manager in the Object Type column of the Objects found
table.
When migrating a mail-in database, verify that the source address in the TSV file matches the name associated
with the mail-in database folder to be migrated. You can verify the name in the Notes administrator account under
the Mail-In Database section. The mail-in database is matched up using either of:
• SourceAddress: Notes address for the resource.
• TargetAddress: SMTP address of the target account in Exchange.
The application does not perform a lookup in the names.nsf file but instead looks for the matching address in the
mail-in-database NSF file.

NOTE: The Data Migration Wizard sets forwarding on a mail-in database if it is told to do so by setting the
MailAddress attribute in Notes Document Properties for the mail-in database.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

332
Appendix A: How do I ...?
How do I save and restore all Migrator for Notes
to Exchange-defined collections from TSV
files?
It is rare but possible that data corruption or incongruities in the SQL database can make it easier to delete the
database contents and re-export data from the Notes/Domino source, although it would be tedious in most
environments to manually recreate collections one at a time.
The Manage User Collections and Manage Group Collections screens in Notes Migration Manager allow you
export all Migrator for Notes to Exchange-defined collections (all at once) to a TSV file, and later restore them to
the SQL database (also all at once), to spare you the time and trouble of having to manually recreate collections in
the event the SQL database is deleted and reloaded.
See Group Collections: Manage Groups and User Collections: Manage Users in chapter 1 for the export and
import procedures.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

333
Appendix A: How do I ...?
 About us

Quest provides software solutions for the rapidly-changing world of enterprise IT. We help simplify the challenges
caused by data explosion, cloud expansion, hybrid datacenters, security threats, and regulatory requirements. We
are a global provider to 130,000 companies across 100 countries, including 95% of the Fortune 500 and 90% of
the Global 1000. Since 1987, we have built a portfolio of solutions that now includes database management, data
protection, identity and access management, Microsoft platform management, and unified endpoint management.
With Quest, organizations spend less time on IT administration and more time on business innovation. 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.

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

334
About us
 Index

A Bulk import directory (for SQL Server), 17

Access Control List, 68, 69, 88, 89, 90, 93
Account Pool Utility, 123 C
Active Directory attribute, replicating to Global Catalog, CAS array, migrating to, 19, 103
320 Client Access Server (CAS) array, migrating to, 317
Active Directory Configuration (in Notes Migration Client Access Server, migrating to, 19, 103, 317
Manager), 23 cmdlet
Active Directory configured for resource forest and user get-executionPolicy, 317
forest, 24, 318
New-ThrottlingPolicy, 317
Active Directory credentials (in NMM Active Directory
set-executionpolicy, 317
Configuration screen), 23
Set-Mailbox, 317
Active Directory object attributes, 34, 72, 77, 319
set-throttlingpolicy, 317
Active Directory server, configuration of, 23
CMN, 96
Active Mail processing, 93
CMN Active Mail remediation, 100
Active Mail remediation by CMN, 100
CMN Directory Connector, 72, 92, 100
AD attribute, replicating to Global Catalog, 320
CMN Free/Busy Connector, 96
AD object attributes, 34, 72, 77, 319
Coexistence Manager for Notes, 96
AD sync utility, conflict with Admin Account Pool utility,
125 collection data tables, editing, 31, 49
AdAttribute column in SQL Server database, 318 collection labels, 27, 29, 54
address books, location of in Notes/Domino Collection Wizard, 27, 31, 53
environment, 33, 62, 66 collections, adding members to, 29, 54, 55
address books, within server mail files, 80 collections, creating, 27, 29, 53
Admin Account Pool Utility, 123 collections, deleting members from, 55
Admin Account Pool utility collections, editing, 27, 29
conflict with AD sync utility, 125 Common tool settings (in NMM Shared Directories
Administrator tool settings (in NMM Shared Directories Configuration screen), 17
Configuration screen), 17 configuration, for Data Migration Wizard, saving and
AdSearchCol column in SQL Server database, 318 reusing, 75, 86
Advanced Settings, editing, 14, 39, 42, 46, 57, 63, 76, configuring for non-English locale, 312
81, 87, 109, 316 custom attributes, migrating, 322
Advanced Settings, option on View menu, 14, 316 custom Notes attributes, migrating, 322
All Documents folder, 313 customattrs.tsv file, 322
ArchivePaths column in SQL Server database, 50, 67,
321 D
archives, location of in Notes/Domino environment, 62, Data Locator Wizard, 33, 62
65, 67, 321 Data Migration Wizard, 34, 85
attachment size filtering, 102 Data Migration Wizard template, 75, 86
attribute values in Notes person documents, 92 Data Migration Wizard template, deleting, 75, 87
attrs.tsv file, 322 Data Migration Wizard template, saving and reusing,
Authentication options (for access to SQL Server), 17 75, 86
Auto-Defined collections, 27, 29 Datastore status (in NMM View Summaries), 37
date limits for messages to be migrated, 102
B deleting a Data Migration Wizard template, 75, 87
batch migration process, 327 design classes, 32, 37

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

335
Index
Directory Export Wizard, 26, 39, 45 GivenName column in SQL Server database, 73
directory synchronization, 327 Global Default Settings, 312, 316
Discover Notes Information (in Notes Migration group collections, 27, 53, 56
Manager), 25 Group Collections (in Notes Migration Manager), 27
discovery of Notes information, 25 groups (distribution lists), provisioning, 27, 28, 56
DisplayName column in SQL Server database, 50, 73 Groups Provisioning Wizard, 28, 56
Distribution list details (in NMM View Summaries), 36
Distribution list provisioning (in NMM View H
Summaries), 37
HTML format DocLinks, 94
distribution lists, provisioning, 27, 28, 56
Do not connect to an Exchange server (in Data Migr
Wiz), 103 I
documentation, 16 IIS, installing, 118
Domino directory data, export of, 26, 39, 45 importing data from TSV, 26, 54, 55
Domino server, configuration of, 18 iNotes, 80
DominoServerAddress column in SQL Server internet access for Log Viewer, 115
database, 50 Internet domains (in NMM View Summaries), 36
duplicate objects in AD, 34, 72 Internet Domains Discovery Wizard, 39, 42
Internet Information Services, installing, 118
E
Edit Default Settings (in Notes Migration Manager), 16 L
email routing method, 96 labels (of collections), 54
EmployeeID column in SQL Server database, 73 license keys, 15
encrypted data, migration of, 324, 325 line numbers (in Log Viewer), how to show or hide, 115
Error Log Report feature, 41, 44, 49, 61, 71, 79, 84, line overrun in Log Viewer, 114, 115
107, 112 line wrapping in Log Viewer, 114, 115
E-Vault (Symantic), migration involving, 317 Locate Notes Data Stores (in Notes Migration
Exchange mailboxes, creating, 318 Manager), 33
Exchange Server Configuration (in Notes Migration location of Notes user source data, 33, 62, 65, 66, 67,
Manager), 18 321
Exchange server, configuration of, 18 Log Viewer, 15, 37, 41, 44, 49, 61, 71, 79, 84, 107, 112,
ExchangeMailboxStore column in SQL Server 113
database, 50 Log Viewer menus, 113
Export Notes Directory (in Notes Migration Manager), Log Viewer toolbar, 113
26
exported directory data, editing, 31, 49 M
exporting data to TSV, 26, 37, 55 mail forwarding address format options, 96, 98
mail forwarding rules, setting and removing, 95, 96, 97,
F 98, 99
file system access to source data, 65, 66, 67, 68, 88, mail location in Notes/Domino environment, 62
89, 90, 95 mail looping, 95, 98, 99
filtering options, 102 mail merge notification emails, 91, 325
Find Domains Configuration (in Notes Migration mail routing during migration, 95, 96, 97, 98, 99
Manager), 25 mail routing method, 96
Find NABs Configuration (in Notes Migration Manager), mailbox enabling, 318
25
MailFilePath column in SQL Server database, 34, 50,
foreign directory synchronization, 85, 92, 100 62, 65, 321
Free/Busy Connector in CMN, 96 Manage Design Classes (in Notes Migration Manager),
32
G Manage Groups (in Notes Migration Manager), 27
Gather Desktop Statistics (in Notes Migration Manage Scheduled Operations (in Notes Migration
Manager), 35 Manager), 36
get-executionPolicy, 317 Manage Users (in Notes Migration Manager), 29

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

336
Index
MAPI Properties, 324 PABs, within server mail files, 80
maximum line length in Log Viewer, 114, 115 PhoneticName column in SQL Server database, 73
merging contacts and security objects in AD, 34, 72, placeholder messages for unmigrated material, 324,
319 325
MfcMapi.exe utility, 323 PowerShell cmdlet
Microsoft AD sync utility, conflict with Admin Account get-executionPolicy, 317
Pool utility, 125 New-ThrottlingPolicy, 317
Microsoft Internet Information Services, installing, 118 set-executionpolic, 317
Migrate User Data (in Notes Migration Manager), 34 Set-ExecutionPolicy Unrestricted, 125
migration statistics, 16, 33, 35, 36, 109 Set-Mailbox, 317
Monitor Migration Progress (in Notes Migration set-throttlingpolicy, 317
Manager), 35 pre-migration notification emails, 325, 331
pre-migration preparations, 315
N product documentation, 16
NABs Discovery Wizard, 39 program parameters, 14, 39, 42, 46, 57, 63, 76, 81, 87,
NABs, location of in Notes/Domino environment, 39 109, 312, 316
NDL files, 94 project statistics, 16, 33, 36, 109
New-ThrottlingPolicy, 317 project status, 16, 33, 36, 109
Nickname column in SQL Server database, 73 Project View (in Notes Migration Manager), 16
NMEObjectGUID column in SQL Server database, 51 Proposion Portal format DocLinks, 94
non-English locale, configuring for, 312 Provision Groups (in Notes Migration Manager), 28
Notes credentials (in NMM Notes Server Configuration Provision Users (in Notes Migration Manager), 34
screen), 18 provisioning distribution groups, 27, 28, 56
Notes custom attributes, migrating, 322 Provisioning Wizard, 34, 72
Notes Data Locator Wizard, 33, 62 pst file format (by Outlook version), 104
Notes design classes, 32, 37 pst files, distribution of (post-migration), 107
Notes domains (in NMM View Summaries), 37 pst files, location of, 104, 322
Notes Migration Manager, 12, 316 pst files, migrating to, 95, 103, 104, 107, 322
Notes Migration Manager, menus, 14 pst files, naming of, 108
Notes Migration Manager, navigation within, 12 PSTdir column in SQL Server database, 51, 104, 322
Notes person documents, attribute values in, 92 public distribution lists, migrating, 27, 28, 56
Notes Server Configuration (in Notes Migration
Manager), 18
Q
Notes user source data, location of, 33, 62, 65, 66, 67,
Quest license keys, 15
321
notesdtapp.ini file, 316
notification emails, 91, 325, 331 R
remote management, enabling on Exchange server,
315
O
replicas, copying to server, 33, 66, 67, 80
ObjectType column in SQL Server database, 51
resource forest, 24, 318
Office 365 Admin Account Pool Utility, 123
resource types, migration of, 332
offline migration, 331
orphaned documents folder, 313
S
Outlook Categories, 313
Scheduling Administration Utility for SSDM, 118
Outlook folder names, language of, 313
Scheduling Administration Utility for SSDM,
configuring, 120
P scheduling tasks, 36, 47, 59, 70, 78, 106, 111
PAB Replicator, 33 SearchKey column in SQL Server database, 34, 51, 73
PAB Replicator, signing, 80 SearchKey2 column in SQL Server database, 51, 73
PABPaths column in SQL Server database, 51, 66, 321 Self-Service Desktop Migrator, log settings (in NMM
PABs, location of in Notes/Domino environment, 33, Shared Directories Configuration screen), 17
62, 66 Self-Service Desktop Migrator, scheduling, 120

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

337
Index
Self-Service Desktop Migrator, statistics collected from, task parameters, editing, 14, 39, 42, 46, 57, 63, 76, 81,
35, 109 87, 109, 316
Send PAB Replicator (in Notes Migration Manager), 33 tasks, defined, 12
Send PAB Replicator Wizard, 33, 80, 94 tasks, scheduling, 36, 47, 59, 70, 78, 106, 111
set-executionpolic, 317 template file for user-notification emails, 91, 326
Set-Mailbox, 317 template, deleting, 75, 87
set-throttlingpolicy, 317 template, for Data Migration Wizard, 75, 86
Shared Directories Configuration (in Notes Migration Trash folder, migrating, 93
Manager), 17 tsv files, exporting to, 26, 37, 55
SharedArchiveDirs column in SQL Server database, tsv files, importing from, 26, 54, 55
51, 67, 321
SharedPABDirs column in SQL Server database, 51,
U
66, 321
Unicode data, 104
Sharepoint server links (migrated DocLinks), 94
updating SQL Server database, 327
Smart Collections, 30
User and resource details (in NMM View Summaries),
SMTP addressing method of mail routing, 96
36
source data, access by file system, 65, 66, 67, 68, 88,
user collections, 29, 53
89, 90, 95
User Collections (in Notes Migration Manager), 29
source data, access by location specified in SQL
Server database, 65, 66, 67, 321 user forest, 24, 318
source data, access by server, 65, 66, 67, 68, 88, 89, User forest credentials (in NMM Active Directory
90, 95 Configuration screen), 25
source data, location of, 33, 62, 65, 66, 67, 321 User migration status per collection (in NMM View
Summaries), 37
SourceAddress column in SQL Server database, 51,
73, 97 user visibility (in Notes), 92, 100
SourceAlias column in SQL Server database, 51 Userid column in SQL Server database, 73
SourceForwardingAddress column in SQL Server
database, 52, 73, 99 V
SQL Server configuration, 16 View Documentation (in Notes Migration Manager), 16
SQL Server Configuration (in Notes Migration View Logs (in Notes Migration Manager), 37
Manager), 16 View Summaries (in Notes Migration Manager), 36
SQL Server data table column headings, 32, 50 visibility (in Notes), 92, 100
SQL Server database, 316
SQL Server database, updating, 327 W
SQL Server host name, 16
Welcome to Exchange (mail-merge notification
SSDM Scheduling Administration Utility, 118 messages), 91, 325
SSDM Scheduling Administration Utility, installing, 118 winrm quickconfig, 315
SSDM Scheduling utility, 120 Wizards, 12
statistics, 16, 33, 35, 36, 109
statistics from SSDM, 35, 109 Y
status of project, 16, 33, 36, 109
You’ve been migrated (mail-merge notification
Surname column in SQL Server database, 73 messages), 91, 325
Symantic E-Vault, migration involving, 317
synchronization of directories, 327

T
target Exchange server version, 18
TargetAddress column in SQL Server database, 52,
73, 97
TargetAlias column in SQL Server database, 52
TargetForwardingAddress column in SQL Server
database, 52, 73, 97
task parameters, 14, 39, 42, 46, 57, 63, 76, 81, 87, 109,
312, 316

Quest Migrator for Notes to Exchange 4.16.2 Administration Guide

338
Index