Converse agora com nosso suporte
Chat com o suporte

Migrator for Notes 20.14.2 - User Guide for Office 365

Section 1. Introduction Section 2. Pre-migration Activities Section 3. User Provisioning Section 4. Email Repliability Section 5. Migrating Mail Files Section 6. Rooms and Resources Database Migration Section 7. Mail-in Database Migration Section 8. Setting Migration Status Section 9. Access and Delegation Migration Section 10. All Accounts Section 11. Customer Status Reports Section 12. Logs About us Technical support resources Appendix A: Staging Replicas Appendix B: Pre-Migration Troubleshooting Appendix C: Work with Files (Import/Export) Appendix D: Item Processing Results Appendix E: Migration Result Statuses Appendix F: Recovery Process Appendix G: Automatic Migration Restart Appendix H: Folder Processing Order

2.2 Auditing Mail Files

Next, you need to audit imported users’ mail files using the Audit Mail Files agents. This tool will check the following (depending upon selections made in the Installation and Configuration for the Required Settings) against each mail file:

  • Mail file exists

  • Migration Notes ID has sufficient access (see the Migrator for Notes Requirements document for more information about required access).

  • Mail file size

  • Number of Contacts

  • Number of Encrypted Items

  • Number of Rules

  • Number of Journal entries (Notebook entries)

To audit mail files:

  1. In the Navigation Pane, expand 2. Mail File Migration and then expand the Audit Mail Files | Audit Mail File Data view:

    Audit Mail File Data View

  2. Select the user Person Documents in the Data Pane; you can either audit a select number of users or all the users at once

  3. Click the Audit Actions button in the Data Pane; the Audit Actions drop-down menu displays:

    Audit Actions Drop-down Menu

  4. Select one of the following options from the drop-down menu:

Option

Description

Audit workflow and delegation

Determines the number of calendar entries affected by delegation for each user and will check for custom repeating meetings. This will provide a report for meetings with repeating patterns that are not supported by Notes Integration (MTCW).

 

Delegation in Notes and Forwarding in Outlook are similar methods of enabling an invitee to share a meeting with someone else; however, these two processes are very different from a system perspective. Migrator for Notes makes every effort to fully support the calendar workflow (see the Known Limitations.pdf for details on unsupported patterns), but some customers may wish to identify users heavily affected by delegated meetings prior to migration.

 

If the Settings option to Audit calendar unsupported patterns is enabled this will also collect a list of any current and future meetings that Outlook cannot fully support. Custom repeating meeting patterns in Notes are migrated to Outlook but are not fully supported for changes in Outlook.

Audit Mail File & Personal Data For Selected Users

Determines each user’s mail file size (includes count of contacts and journal entries (notebook entries)

 

This option will also query the options that you selected in the Required Settings > Domino tab

Audit pNAB DB For Selected Users

Determines if users’ pNAB database is accessible and the number of contacts

 

This agent audits the server-based pNAB for selected users if one is defined in their Person document. This menu option is not used for migration. Irrespective of whether the migration mail agent is used to prompt the user to synchronize their own contacts or the administrator syncs their contacts for them, it is imperative that contacts must be synced into the users’ mail files to migrate contacts.

 

The purpose of the server-based pNAB field is so that the migration coordinator can perform the synchronization on behalf of the user, by clicking Actions > Other to access the Synchronize Address Book agent.

 

Note: If pNAB database information is not populated in the users’ Person documents in Migrator for Notes, then you need to either send users a message to sync the pNAB to the mail file or specify pNAB details to be sure that Migrator for Notes is pointing to the server where pNAB is stored.

 

2.2.1 Audit workflow and delegation

  1. Click the Audit workflow and delegation menu option

  2. Totals will appear in the following columns:

    • Unsupported workflow - unsupported calendar recurrence patterns

    • Was Delegated - another Domino user delegated attendance

    • Delegator – the Chair delegated the meeting

    • Delegatee – the user was delegated to attend the meeting on someone’s behalf

 


Totals will show in these columns only if data is populated in the corresponding fields of the Person Document.

  1. The Calendar MTCW Audit Report will be populated with any meetings that the user is a Chair for, are in the Notes Integration cache range (typically 90 days from current date) and have a repeating meeting pattern that would not be supported for Outlook to Notes coexistence. This will include any meeting in the cache range including cancelled meetings.

 


This is an administrator-only audit for informational purposes to assist with Integration troubleshooting. This can be disregarded if Integration has not been deployed.

  1. If the Settings to Audit calendar unsupported patterns is enabled then the Calendar audit RTF report will be populated with any meetings that have a Notes custom pattern. This will be for meetings where the user is the Chair but can also include meetings where the user an Invitee if that option is enabled. This will not include meetings that have been cancelled. The audit can be sent to the end user through the Remediation Summary message template.

 


The Remediation Summary message will not be sent if the audit does not locate any active meetings with Notes custom patterns.

2.2.2 Audit Mail File & Personal Data For Selected Users

  1. Click the Audit Mail File & Personal Data For Selected Users menu option; a message box appears indicating the number of selected users to audit

  2. Click Yes

  3. Depending upon the number of selected users, this process could take from a few seconds to several minutes. Upon completion, a message box confirms that auditing of the mail database is complete and all users have been promoted to the next step of migration; click OK. If no errors are found, skip to step 4.

    All errors must be fixed and then the Audit Mail File & Personal Data for Selected Users tool must be re-run without errors prior to the mail file migration. Refer to the Pre-Migration Troubleshooting appendix for common audit errors and troubleshooting steps.

 


If problems occur during the audit process, the Person Document will be moved to the Check Errors folder in the Navigation Pane. The Check Errors folder will show any errors found during the audit process.

If you cannot resolve the errors or need assistance determining why an error occurred, contact Product Support.

Check Errors View

  1. After the error is resolved, to re-audit the user, select the user in the Check Errors view and, from the Data Pane, click the Audit Actions | Audit Mail File & Personal Data For Selected Users button in the Data Pane:

    Check Errors View

  2. Successfully audited users are promoted to the next step of migration (Notify)

  3. To view the result of the audit, you can go to the Preparation | Advanced view in the Navigation Pane

    Advanced View

Notice that the tool has audited users’ mail file size and listed the number of encrypted items, rules, contacts and journal entries (notebook entries) that each user’s mail file contains. In addition, the Data Pane also lists the people, journal (notebook) and rule count in all of the user mail files.

2.2.3 Moving the Selected Users Back to Audit Mail File Data

As soon as an audit is run, the successfully audited users are moved to the Notify step; however, you may wish to run the remaining Audit options on the users. To perform more audits, move them back to the Audit step.

2.2.4 Audit pNAB DB For Selected Users

Local Contact Data

Users’ contact data needs to be in the $PeopleGroupsFlat view in their mail file to be migrated. The local contacts’ data needs to be synchronized through Notes replication on the end users’ workstation. This can be enabled through Domino/Notes policies, but if that has not been configured you will need to send each user an email message containing a special button. When clicked, the user’s contact and personal distribution list data found in their local names.nsf will be synchronized with their mail file. This data is then stored in a hidden view called $PeopleGroupsFlat in their mail files. If the view doesn’t exist, it will be created when the user clicks the embedded button in the migration message.

Server-based Contact Data

If a user’s contact data is stored on the Domino server, then you can edit the user’s Person document to point to the location and the name of the Personal Name and Address Book (pNAB). For example, if user Bill Bell has pNAB on the Acme_mail Domino server in the Contacts folder, then his/her Person document must be edited and saved to update this information.


This action is only required if the end user contact data is not being synchronized by Notes directly into their email file using Notes Replication and Sync processing.

  1. Open a user’s Person document in the Data Pane

  2. Open the Additional Databases tab and either click the Edit Document button or double-click inside the document

  3. Edit the PNAB Server and PNAB File Name fields. Specify the Domino server name and the full path to user's server-based personal name and address book (pNAB)

  4. Click the Open link to verify whether the database can access the specified location and open the pNAB

  5. Click Save & Close:

    Person Document

  6. With the user selected in the Data Pane, click the Actions | Other menu option

  7. Select Synchronize Address Book from the list of agents in the Run Agent dialog box, and then click OK

  8. Once the Person document is edited and saved, and the contact data synchronized, select the user (Susan Johnson using the example above), and then select Audit Actions | Audit pNAB DB For Selected Users.. The server-based pNAB is validated and its size is audited and moved to the next step.

2.2.1 Audit workflow and delegation

2.2 Auditing Mail Files

Next, you need to audit imported users’ mail files using the Audit Mail Files agents. This tool will check the following (depending upon selections made in the Installation and Configuration for the Required Settings) against each mail file:

  • Mail file exists

  • Migration Notes ID has sufficient access (see the Migrator for Notes Requirements document for more information about required access).

  • Mail file size

  • Number of Contacts

  • Number of Encrypted Items

  • Number of Rules

  • Number of Journal entries (Notebook entries)

To audit mail files:

  1. In the Navigation Pane, expand 2. Mail File Migration and then expand the Audit Mail Files | Audit Mail File Data view:

    Audit Mail File Data View

  2. Select the user Person Documents in the Data Pane; you can either audit a select number of users or all the users at once

  3. Click the Audit Actions button in the Data Pane; the Audit Actions drop-down menu displays:

    Audit Actions Drop-down Menu

  4. Select one of the following options from the drop-down menu:

Option

Description

Audit workflow and delegation

Determines the number of calendar entries affected by delegation for each user and will check for custom repeating meetings. This will provide a report for meetings with repeating patterns that are not supported by Notes Integration (MTCW).

 

Delegation in Notes and Forwarding in Outlook are similar methods of enabling an invitee to share a meeting with someone else; however, these two processes are very different from a system perspective. Migrator for Notes makes every effort to fully support the calendar workflow (see the Known Limitations.pdf for details on unsupported patterns), but some customers may wish to identify users heavily affected by delegated meetings prior to migration.

 

If the Settings option to Audit calendar unsupported patterns is enabled this will also collect a list of any current and future meetings that Outlook cannot fully support. Custom repeating meeting patterns in Notes are migrated to Outlook but are not fully supported for changes in Outlook.

Audit Mail File & Personal Data For Selected Users

Determines each user’s mail file size (includes count of contacts and journal entries (notebook entries)

 

This option will also query the options that you selected in the Required Settings > Domino tab

Audit pNAB DB For Selected Users

Determines if users’ pNAB database is accessible and the number of contacts

 

This agent audits the server-based pNAB for selected users if one is defined in their Person document. This menu option is not used for migration. Irrespective of whether the migration mail agent is used to prompt the user to synchronize their own contacts or the administrator syncs their contacts for them, it is imperative that contacts must be synced into the users’ mail files to migrate contacts.

 

The purpose of the server-based pNAB field is so that the migration coordinator can perform the synchronization on behalf of the user, by clicking Actions > Other to access the Synchronize Address Book agent.

 

Note: If pNAB database information is not populated in the users’ Person documents in Migrator for Notes, then you need to either send users a message to sync the pNAB to the mail file or specify pNAB details to be sure that Migrator for Notes is pointing to the server where pNAB is stored.

 

  1. Click the Audit workflow and delegation menu option

  2. Totals will appear in the following columns:

    • Unsupported workflow - unsupported calendar recurrence patterns

    • Was Delegated - another Domino user delegated attendance

    • Delegator – the Chair delegated the meeting

    • Delegatee – the user was delegated to attend the meeting on someone’s behalf

 


Totals will show in these columns only if data is populated in the corresponding fields of the Person Document.

  1. The Calendar MTCW Audit Report will be populated with any meetings that the user is a Chair for, are in the Notes Integration cache range (typically 90 days from current date) and have a repeating meeting pattern that would not be supported for Outlook to Notes coexistence. This will include any meeting in the cache range including cancelled meetings.

 


This is an administrator-only audit for informational purposes to assist with Integration troubleshooting. This can be disregarded if Integration has not been deployed.

  1. If the Settings to Audit calendar unsupported patterns is enabled then the Calendar audit RTF report will be populated with any meetings that have a Notes custom pattern. This will be for meetings where the user is the Chair but can also include meetings where the user an Invitee if that option is enabled. This will not include meetings that have been cancelled. The audit can be sent to the end user through the Remediation Summary message template.

 


The Remediation Summary message will not be sent if the audit does not locate any active meetings with Notes custom patterns.

2.2.2 Audit Mail File & Personal Data For Selected Users

  1. Click the Audit Mail File & Personal Data For Selected Users menu option; a message box appears indicating the number of selected users to audit

  2. Click Yes

  3. Depending upon the number of selected users, this process could take from a few seconds to several minutes. Upon completion, a message box confirms that auditing of the mail database is complete and all users have been promoted to the next step of migration; click OK. If no errors are found, skip to step 4.

    All errors must be fixed and then the Audit Mail File & Personal Data for Selected Users tool must be re-run without errors prior to the mail file migration. Refer to the Pre-Migration Troubleshooting appendix for common audit errors and troubleshooting steps.

 


If problems occur during the audit process, the Person Document will be moved to the Check Errors folder in the Navigation Pane. The Check Errors folder will show any errors found during the audit process.

If you cannot resolve the errors or need assistance determining why an error occurred, contact Product Support.

Check Errors View

  1. After the error is resolved, to re-audit the user, select the user in the Check Errors view and, from the Data Pane, click the Audit Actions | Audit Mail File & Personal Data For Selected Users button in the Data Pane:

    Check Errors View

  2. Successfully audited users are promoted to the next step of migration (Notify)

  3. To view the result of the audit, you can go to the Preparation | Advanced view in the Navigation Pane

    Advanced View

Notice that the tool has audited users’ mail file size and listed the number of encrypted items, rules, contacts and journal entries (notebook entries) that each user’s mail file contains. In addition, the Data Pane also lists the people, journal (notebook) and rule count in all of the user mail files.

2.2.3 Moving the Selected Users Back to Audit Mail File Data

As soon as an audit is run, the successfully audited users are moved to the Notify step; however, you may wish to run the remaining Audit options on the users. To perform more audits, move them back to the Audit step.

2.2.4 Audit pNAB DB For Selected Users

Local Contact Data

Users’ contact data needs to be in the $PeopleGroupsFlat view in their mail file to be migrated. The local contacts’ data needs to be synchronized through Notes replication on the end users’ workstation. This can be enabled through Domino/Notes policies, but if that has not been configured you will need to send each user an email message containing a special button. When clicked, the user’s contact and personal distribution list data found in their local names.nsf will be synchronized with their mail file. This data is then stored in a hidden view called $PeopleGroupsFlat in their mail files. If the view doesn’t exist, it will be created when the user clicks the embedded button in the migration message.

Server-based Contact Data

If a user’s contact data is stored on the Domino server, then you can edit the user’s Person document to point to the location and the name of the Personal Name and Address Book (pNAB). For example, if user Bill Bell has pNAB on the Acme_mail Domino server in the Contacts folder, then his/her Person document must be edited and saved to update this information.


This action is only required if the end user contact data is not being synchronized by Notes directly into their email file using Notes Replication and Sync processing.

  1. Open a user’s Person document in the Data Pane

  2. Open the Additional Databases tab and either click the Edit Document button or double-click inside the document

  3. Edit the PNAB Server and PNAB File Name fields. Specify the Domino server name and the full path to user's server-based personal name and address book (pNAB)

  4. Click the Open link to verify whether the database can access the specified location and open the pNAB

  5. Click Save & Close:

    Person Document

  6. With the user selected in the Data Pane, click the Actions | Other menu option

  7. Select Synchronize Address Book from the list of agents in the Run Agent dialog box, and then click OK

  8. Once the Person document is edited and saved, and the contact data synchronized, select the user (Susan Johnson using the example above), and then select Audit Actions | Audit pNAB DB For Selected Users.. The server-based pNAB is validated and its size is audited and moved to the next step.

2.2.2 Audit Mail File & Personal Data For Selected Users

2.2 Auditing Mail Files

Next, you need to audit imported users’ mail files using the Audit Mail Files agents. This tool will check the following (depending upon selections made in the Installation and Configuration for the Required Settings) against each mail file:

  • Mail file exists

  • Migration Notes ID has sufficient access (see the Migrator for Notes Requirements document for more information about required access).

  • Mail file size

  • Number of Contacts

  • Number of Encrypted Items

  • Number of Rules

  • Number of Journal entries (Notebook entries)

To audit mail files:

  1. In the Navigation Pane, expand 2. Mail File Migration and then expand the Audit Mail Files | Audit Mail File Data view:

    Audit Mail File Data View

  2. Select the user Person Documents in the Data Pane; you can either audit a select number of users or all the users at once

  3. Click the Audit Actions button in the Data Pane; the Audit Actions drop-down menu displays:

    Audit Actions Drop-down Menu

  4. Select one of the following options from the drop-down menu:

Option

Description

Audit workflow and delegation

Determines the number of calendar entries affected by delegation for each user and will check for custom repeating meetings. This will provide a report for meetings with repeating patterns that are not supported by Notes Integration (MTCW).

 

Delegation in Notes and Forwarding in Outlook are similar methods of enabling an invitee to share a meeting with someone else; however, these two processes are very different from a system perspective. Migrator for Notes makes every effort to fully support the calendar workflow (see the Known Limitations.pdf for details on unsupported patterns), but some customers may wish to identify users heavily affected by delegated meetings prior to migration.

 

If the Settings option to Audit calendar unsupported patterns is enabled this will also collect a list of any current and future meetings that Outlook cannot fully support. Custom repeating meeting patterns in Notes are migrated to Outlook but are not fully supported for changes in Outlook.

Audit Mail File & Personal Data For Selected Users

Determines each user’s mail file size (includes count of contacts and journal entries (notebook entries)

 

This option will also query the options that you selected in the Required Settings > Domino tab

Audit pNAB DB For Selected Users

Determines if users’ pNAB database is accessible and the number of contacts

 

This agent audits the server-based pNAB for selected users if one is defined in their Person document. This menu option is not used for migration. Irrespective of whether the migration mail agent is used to prompt the user to synchronize their own contacts or the administrator syncs their contacts for them, it is imperative that contacts must be synced into the users’ mail files to migrate contacts.

 

The purpose of the server-based pNAB field is so that the migration coordinator can perform the synchronization on behalf of the user, by clicking Actions > Other to access the Synchronize Address Book agent.

 

Note: If pNAB database information is not populated in the users’ Person documents in Migrator for Notes, then you need to either send users a message to sync the pNAB to the mail file or specify pNAB details to be sure that Migrator for Notes is pointing to the server where pNAB is stored.

 

2.2.1 Audit workflow and delegation

  1. Click the Audit workflow and delegation menu option

  2. Totals will appear in the following columns:

    • Unsupported workflow - unsupported calendar recurrence patterns

    • Was Delegated - another Domino user delegated attendance

    • Delegator – the Chair delegated the meeting

    • Delegatee – the user was delegated to attend the meeting on someone’s behalf

 


Totals will show in these columns only if data is populated in the corresponding fields of the Person Document.

  1. The Calendar MTCW Audit Report will be populated with any meetings that the user is a Chair for, are in the Notes Integration cache range (typically 90 days from current date) and have a repeating meeting pattern that would not be supported for Outlook to Notes coexistence. This will include any meeting in the cache range including cancelled meetings.

 


This is an administrator-only audit for informational purposes to assist with Integration troubleshooting. This can be disregarded if Integration has not been deployed.

  1. If the Settings to Audit calendar unsupported patterns is enabled then the Calendar audit RTF report will be populated with any meetings that have a Notes custom pattern. This will be for meetings where the user is the Chair but can also include meetings where the user an Invitee if that option is enabled. This will not include meetings that have been cancelled. The audit can be sent to the end user through the Remediation Summary message template.

 


The Remediation Summary message will not be sent if the audit does not locate any active meetings with Notes custom patterns.

  1. Click the Audit Mail File & Personal Data For Selected Users menu option; a message box appears indicating the number of selected users to audit

  2. Click Yes

  3. Depending upon the number of selected users, this process could take from a few seconds to several minutes. Upon completion, a message box confirms that auditing of the mail database is complete and all users have been promoted to the next step of migration; click OK. If no errors are found, skip to step 4.

    All errors must be fixed and then the Audit Mail File & Personal Data for Selected Users tool must be re-run without errors prior to the mail file migration. Refer to the Pre-Migration Troubleshooting appendix for common audit errors and troubleshooting steps.

 


If problems occur during the audit process, the Person Document will be moved to the Check Errors folder in the Navigation Pane. The Check Errors folder will show any errors found during the audit process.

If you cannot resolve the errors or need assistance determining why an error occurred, contact Product Support.

Check Errors View

  1. After the error is resolved, to re-audit the user, select the user in the Check Errors view and, from the Data Pane, click the Audit Actions | Audit Mail File & Personal Data For Selected Users button in the Data Pane:

    Check Errors View

  2. Successfully audited users are promoted to the next step of migration (Notify)

  3. To view the result of the audit, you can go to the Preparation | Advanced view in the Navigation Pane

    Advanced View

Notice that the tool has audited users’ mail file size and listed the number of encrypted items, rules, contacts and journal entries (notebook entries) that each user’s mail file contains. In addition, the Data Pane also lists the people, journal (notebook) and rule count in all of the user mail files.

2.2.3 Moving the Selected Users Back to Audit Mail File Data

As soon as an audit is run, the successfully audited users are moved to the Notify step; however, you may wish to run the remaining Audit options on the users. To perform more audits, move them back to the Audit step.

2.2.4 Audit pNAB DB For Selected Users

Local Contact Data

Users’ contact data needs to be in the $PeopleGroupsFlat view in their mail file to be migrated. The local contacts’ data needs to be synchronized through Notes replication on the end users’ workstation. This can be enabled through Domino/Notes policies, but if that has not been configured you will need to send each user an email message containing a special button. When clicked, the user’s contact and personal distribution list data found in their local names.nsf will be synchronized with their mail file. This data is then stored in a hidden view called $PeopleGroupsFlat in their mail files. If the view doesn’t exist, it will be created when the user clicks the embedded button in the migration message.

Server-based Contact Data

If a user’s contact data is stored on the Domino server, then you can edit the user’s Person document to point to the location and the name of the Personal Name and Address Book (pNAB). For example, if user Bill Bell has pNAB on the Acme_mail Domino server in the Contacts folder, then his/her Person document must be edited and saved to update this information.


This action is only required if the end user contact data is not being synchronized by Notes directly into their email file using Notes Replication and Sync processing.

  1. Open a user’s Person document in the Data Pane

  2. Open the Additional Databases tab and either click the Edit Document button or double-click inside the document

  3. Edit the PNAB Server and PNAB File Name fields. Specify the Domino server name and the full path to user's server-based personal name and address book (pNAB)

  4. Click the Open link to verify whether the database can access the specified location and open the pNAB

  5. Click Save & Close:

    Person Document

  6. With the user selected in the Data Pane, click the Actions | Other menu option

  7. Select Synchronize Address Book from the list of agents in the Run Agent dialog box, and then click OK

  8. Once the Person document is edited and saved, and the contact data synchronized, select the user (Susan Johnson using the example above), and then select Audit Actions | Audit pNAB DB For Selected Users.. The server-based pNAB is validated and its size is audited and moved to the next step.

2.2.3 Moving the Selected Users Back to Audit Mail File Data

2.2 Auditing Mail Files

Next, you need to audit imported users’ mail files using the Audit Mail Files agents. This tool will check the following (depending upon selections made in the Installation and Configuration for the Required Settings) against each mail file:

  • Mail file exists

  • Migration Notes ID has sufficient access (see the Migrator for Notes Requirements document for more information about required access).

  • Mail file size

  • Number of Contacts

  • Number of Encrypted Items

  • Number of Rules

  • Number of Journal entries (Notebook entries)

To audit mail files:

  1. In the Navigation Pane, expand 2. Mail File Migration and then expand the Audit Mail Files | Audit Mail File Data view:

    Audit Mail File Data View

  2. Select the user Person Documents in the Data Pane; you can either audit a select number of users or all the users at once

  3. Click the Audit Actions button in the Data Pane; the Audit Actions drop-down menu displays:

    Audit Actions Drop-down Menu

  4. Select one of the following options from the drop-down menu:

Option

Description

Audit workflow and delegation

Determines the number of calendar entries affected by delegation for each user and will check for custom repeating meetings. This will provide a report for meetings with repeating patterns that are not supported by Notes Integration (MTCW).

 

Delegation in Notes and Forwarding in Outlook are similar methods of enabling an invitee to share a meeting with someone else; however, these two processes are very different from a system perspective. Migrator for Notes makes every effort to fully support the calendar workflow (see the Known Limitations.pdf for details on unsupported patterns), but some customers may wish to identify users heavily affected by delegated meetings prior to migration.

 

If the Settings option to Audit calendar unsupported patterns is enabled this will also collect a list of any current and future meetings that Outlook cannot fully support. Custom repeating meeting patterns in Notes are migrated to Outlook but are not fully supported for changes in Outlook.

Audit Mail File & Personal Data For Selected Users

Determines each user’s mail file size (includes count of contacts and journal entries (notebook entries)

 

This option will also query the options that you selected in the Required Settings > Domino tab

Audit pNAB DB For Selected Users

Determines if users’ pNAB database is accessible and the number of contacts

 

This agent audits the server-based pNAB for selected users if one is defined in their Person document. This menu option is not used for migration. Irrespective of whether the migration mail agent is used to prompt the user to synchronize their own contacts or the administrator syncs their contacts for them, it is imperative that contacts must be synced into the users’ mail files to migrate contacts.

 

The purpose of the server-based pNAB field is so that the migration coordinator can perform the synchronization on behalf of the user, by clicking Actions > Other to access the Synchronize Address Book agent.

 

Note: If pNAB database information is not populated in the users’ Person documents in Migrator for Notes, then you need to either send users a message to sync the pNAB to the mail file or specify pNAB details to be sure that Migrator for Notes is pointing to the server where pNAB is stored.

 

2.2.1 Audit workflow and delegation

  1. Click the Audit workflow and delegation menu option

  2. Totals will appear in the following columns:

    • Unsupported workflow - unsupported calendar recurrence patterns

    • Was Delegated - another Domino user delegated attendance

    • Delegator – the Chair delegated the meeting

    • Delegatee – the user was delegated to attend the meeting on someone’s behalf

 


Totals will show in these columns only if data is populated in the corresponding fields of the Person Document.

  1. The Calendar MTCW Audit Report will be populated with any meetings that the user is a Chair for, are in the Notes Integration cache range (typically 90 days from current date) and have a repeating meeting pattern that would not be supported for Outlook to Notes coexistence. This will include any meeting in the cache range including cancelled meetings.

 


This is an administrator-only audit for informational purposes to assist with Integration troubleshooting. This can be disregarded if Integration has not been deployed.

  1. If the Settings to Audit calendar unsupported patterns is enabled then the Calendar audit RTF report will be populated with any meetings that have a Notes custom pattern. This will be for meetings where the user is the Chair but can also include meetings where the user an Invitee if that option is enabled. This will not include meetings that have been cancelled. The audit can be sent to the end user through the Remediation Summary message template.

 


The Remediation Summary message will not be sent if the audit does not locate any active meetings with Notes custom patterns.

2.2.2 Audit Mail File & Personal Data For Selected Users

  1. Click the Audit Mail File & Personal Data For Selected Users menu option; a message box appears indicating the number of selected users to audit

  2. Click Yes

  3. Depending upon the number of selected users, this process could take from a few seconds to several minutes. Upon completion, a message box confirms that auditing of the mail database is complete and all users have been promoted to the next step of migration; click OK. If no errors are found, skip to step 4.

    All errors must be fixed and then the Audit Mail File & Personal Data for Selected Users tool must be re-run without errors prior to the mail file migration. Refer to the Pre-Migration Troubleshooting appendix for common audit errors and troubleshooting steps.

 


If problems occur during the audit process, the Person Document will be moved to the Check Errors folder in the Navigation Pane. The Check Errors folder will show any errors found during the audit process.

If you cannot resolve the errors or need assistance determining why an error occurred, contact Product Support.

Check Errors View

  1. After the error is resolved, to re-audit the user, select the user in the Check Errors view and, from the Data Pane, click the Audit Actions | Audit Mail File & Personal Data For Selected Users button in the Data Pane:

    Check Errors View

  2. Successfully audited users are promoted to the next step of migration (Notify)

  3. To view the result of the audit, you can go to the Preparation | Advanced view in the Navigation Pane

    Advanced View

Notice that the tool has audited users’ mail file size and listed the number of encrypted items, rules, contacts and journal entries (notebook entries) that each user’s mail file contains. In addition, the Data Pane also lists the people, journal (notebook) and rule count in all of the user mail files.

As soon as an audit is run, the successfully audited users are moved to the Notify step; however, you may wish to run the remaining Audit options on the users. To perform more audits, move them back to the Audit step.

2.2.4 Audit pNAB DB For Selected Users

Local Contact Data

Users’ contact data needs to be in the $PeopleGroupsFlat view in their mail file to be migrated. The local contacts’ data needs to be synchronized through Notes replication on the end users’ workstation. This can be enabled through Domino/Notes policies, but if that has not been configured you will need to send each user an email message containing a special button. When clicked, the user’s contact and personal distribution list data found in their local names.nsf will be synchronized with their mail file. This data is then stored in a hidden view called $PeopleGroupsFlat in their mail files. If the view doesn’t exist, it will be created when the user clicks the embedded button in the migration message.

Server-based Contact Data

If a user’s contact data is stored on the Domino server, then you can edit the user’s Person document to point to the location and the name of the Personal Name and Address Book (pNAB). For example, if user Bill Bell has pNAB on the Acme_mail Domino server in the Contacts folder, then his/her Person document must be edited and saved to update this information.


This action is only required if the end user contact data is not being synchronized by Notes directly into their email file using Notes Replication and Sync processing.

  1. Open a user’s Person document in the Data Pane

  2. Open the Additional Databases tab and either click the Edit Document button or double-click inside the document

  3. Edit the PNAB Server and PNAB File Name fields. Specify the Domino server name and the full path to user's server-based personal name and address book (pNAB)

  4. Click the Open link to verify whether the database can access the specified location and open the pNAB

  5. Click Save & Close:

    Person Document

  6. With the user selected in the Data Pane, click the Actions | Other menu option

  7. Select Synchronize Address Book from the list of agents in the Run Agent dialog box, and then click OK

  8. Once the Person document is edited and saved, and the contact data synchronized, select the user (Susan Johnson using the example above), and then select Audit Actions | Audit pNAB DB For Selected Users.. The server-based pNAB is validated and its size is audited and moved to the next step.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação