Veritas Enterprise Vault PST Migration 12.2

Transcription

1 Veritas Enterprise Vault PST Migration 12.2

2 Veritas Enterprise Vault: PST Migration Last updated: Legal Notice Copyright 2017 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Veritas product may contain third party software for which Veritas is required to provide attribution to the third party ("Third Party Programs"). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Licensed Software does not alter any rights or obligations you may have under those open source or free software licenses. For more information on the Third Party Programs, please see the Third Party Notice document for this Veritas product that is available at The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on-premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Veritas Technologies LLC 500 E Middlefield Road Mountain View, CA

3 Technical Support Technical Support maintains support centers globally. All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policies. For information about our support offerings and how to contact Technical Support, visit our website: You can manage your Veritas account information at the following URL: If you have questions regarding an existing support agreement, please the support agreement administration team for your region as follows: Worldwide (except Japan) Japan Before you contact Technical Support, run the Veritas Quick Assist (VQA) tool to make sure that you have satisfied the system requirements that are listed in your product documentation. You can download VQA from the following article on the Veritas Support website: Documentation Make sure that you have the current version of the documentation. Each document displays the date of the last update on page 2. The latest documentation is available on the Veritas website: Documentation feedback Your feedback is important to us. Suggest improvements or report errors or omissions to the documentation. Include the document title, document version, chapter title, and section title of the text on which you are reporting. Send feedback to: You can also see documentation information or ask a question on the Veritas community site:

4 Contents Chapter 1 About this guide... 7 Introducing this guide... 7 Where to get more information about Enterprise Vault... 7 Enterprise Vault training modules Chapter 2 Introduction to PST migration Introducing PST file migration Tools for migrating PST files Feature comparison of PST migration tools About the Exchange PST Migration policy Improving performance when archiving PST file contents Migrating PST files in hosted environments About the Personal Store Management node Creating filters Chapter 3 PST file ownership About PST file ownership PST file marking to determine PST file ownership PST message sampling to determine PST file ownership Configuring message sampling to determine PST file ownership Results of message sampling Chapter 4 PST migration: scripted Overview of the scripting mechanism for PST migration Undertaking the PST migration process using Policy Manager Preparation for PST scripted migration Output from PST migration [PSTcheckpoint] section PST scripted migration Enterprise Vault event log for PST scripted migration Example initialization file for PST scripted migration... 33

5 Contents 5 Chapter 5 PST migration: wizard-assisted About the PST Migrator wizard Outline of the wizard-assisted PST migration process Preparation for the wizard-assisted PST migration process Migration tips for the wizard-assisted PST migration process How the wizard-assisted PST migration process affects users Starting the wizard-assisted PST migration process Chapter 6 PST migration: Locate and Migrate About Locate and Migrate Setting up PST Locate and Migrate Administrator roles required to manage PST Locate and Migrate Configuring the holding folder for PST Locate and Migrate Creating and configuring the PST Locator, PST Collector, and PST Migrator tasks Migrating PST files using PST Locate and Migrate Running the PST Locator task to find domains and computers Selecting computers for PST searching Configuring paths to include or exclude for PST searching Running the PST Locator task to find PST files Running the PST Collector task Running the PST Migrator task PowerShell cmdlets for PST migration Excluding network shares from PST migration using the PstLocatorTask.exe.config file Troubleshooting PST migration Chapter 7 PST migration: client-driven migration About client-driven PST migration Options to configure client-driven PST migration Preparation for client-driven PST migration Editing the PST migration messages for client-driven PST migration Configuring the PST holding folder for PST client-driven migration Creating a PST Migrator task for PST client-driven migration Enabling mailboxes for PST client-driven migration Enabling mailboxes for PST file submission... 78

6 Contents 6 Permissions required for migrating PST files stored on network drives Index... 80

7 Chapter 1 About this guide This chapter includes the following topics: Introducing this guide Where to get more information about Enterprise Vault Introducing this guide This guide describes how to migrate and archive the contents of PST files to Enterprise Vault. Administrators can configure Enterprise Vault to migrate PST files automatically or let end users choose whether to migrate PST files to Enterprise Vault. Where to get more information about Enterprise Vault Table 1-1 lists the documentation that accompanies Enterprise Vault.

8 About this guide Where to get more information about Enterprise Vault 8 Table 1-1 Document Enterprise Vault documentation set Comments Veritas Enterprise Vault Documentation Library Includes all the following documents in Windows Help (.chm) format so that you can search across them all. It also includes links to the guides in Acrobat (.pdf) format. You can access the library in several ways, including the following: In Windows Explorer, browse to the Documentation\language subfolder of the Enterprise Vault installation folder, and then open the EV_Help.chm file. On the Help menu in the Administration Console, click Help on Enterprise Vault. Introduction and Planning Deployment Scanner Installing and Configuring Upgrade Instructions Setting up Domino Server Archiving Setting up Exchange Server Archiving Setting up File System Archiving Setting up IMAP Setting up Skype for Business Archiving Setting up SMTP Archiving Setting up SharePoint Server Archiving Administrator s Guide Provides an overview of Enterprise Vault functionality. Describes how to check the required software and settings before you install Enterprise Vault. Provides detailed information on setting up Enterprise Vault. Describes how to upgrade an existing Enterprise Vault installation to the latest version. Describes how to archive items from Domino mail files and journal databases. Describes how to archive items from Microsoft Exchange user mailboxes, journal mailboxes, and public folders. Describes how to archive the files that are held on network file servers. Describes how to configure IMAP client access to Exchange archives and Internet mail archives. Describes how to archive Skype for Business conversations. Describes how to archive SMTP messages from other messaging servers. Describes how to archive content from Microsoft SharePoint servers. Describes how to perform day-to-day administration procedures.

9 About this guide Where to get more information about Enterprise Vault 9 Table 1-1 Document Enterprise Vault documentation set (continued) Comments Backup and Recovery Classification using the Microsoft File Classification Infrastructure Describes how to implement an effective backup strategy to prevent data loss, and how to provide a means for recovery in the event of a system failure. Describes how to use the classification engine that is built into recent Windows Server editions to classify all new and existing archived content. Classification using the Veritas Information Classifier Describes how to use the Veritas Information Classifier to evaluate all new and archived content against a comprehensive set of industry-standard classification policies. If you are new to classification with Enterprise Vault, we recommend that you use the Veritas Information Classifier rather than the older and less intuitive File Classification Infrastructure engine. NSF Migration PST Migration Reporting Utilities PowerShell Cmdlets Registry Values Help for Administration Console Help for Enterprise Vault Operations Manager Describes how to migrate content from Domino and Notes NSF files into Enterprise Vault archives. Describes how to migrate content from Outlook PST files into Enterprise Vault archives. Describes how to implement Enterprise Vault Reporting, which provides reports on the status of Enterprise Vault servers, archives, and archived items. If you configure FSA Reporting, additional reports are available for file servers and their volumes. Describes the Enterprise Vault tools and utilities. Describes how to perform various administrative tasks by running the Enterprise Vault PowerShell cmdlets. A reference document that lists the registry values with which you can modify many aspects of Enterprise Vault behavior. The online Help for the Enterprise Vault Administration Console. The online Help for Enterprise Vault Operations Manager. For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts book, which is available from this address:

10 About this guide Where to get more information about Enterprise Vault 10 Enterprise Vault training modules Veritas Education Services provides comprehensive training for Enterprise Vault, from basic administration to advanced topics and troubleshooting. Training is available in a variety of formats, including classroom-based and virtual training. For more information on Enterprise Vault training, curriculum paths, and certification options, see

11 Chapter 2 Introduction to PST migration This chapter includes the following topics: Introducing PST file migration Tools for migrating PST files Feature comparison of PST migration tools About the Exchange PST Migration policy Improving performance when archiving PST file contents Migrating PST files in hosted environments About the Personal Store Management node Introducing PST file migration Enterprise Vault can archive information that is held in PST files on users' computers. Administrators can enable mailboxes for PST file migration. Administrators can also let end users choose whether to migrate PST files to Enterprise Vault. To carry out the PST migration, Enterprise Vault finds the computers that contain PST files, locates the files, determines ownership, and migrates the files to the appropriate archives. To determine ownership of PST files, administrators can use PST file marking or PST message sampling. You can choose to migrate PST files to Exchange Mailbox archives or Internet Mail archives. Enterprise Vault provides the following tools for migrating PST files to archives: Locate and Migrate Client-driven PST migration

12 Introduction to PST migration Tools for migrating PST files 12 Scripted migration using Policy Manager PST Migrator wizard-assisted migration Tools for migrating PST files Enterprise Vault provides the following tools for migrating the contents of PST files to archives: Scripted migration using Policy Manager. This tool is useful for performing bulk migrations of PST files, but you need to collect the PST files in a central location. See Overview of the scripting mechanism for PST migration on page 26. PST Migrator wizard-assisted migration. If you have a small number of PST files, this tool provides a quick way to migrate them to Enterprise Vault. See About the PST Migrator wizard on page 35. Locate and Migrate. This tool locates PST files on users computers, copies them to a central location, and then migrates them. You can configure specific paths to include or exclude during PST searching. Unless you have only a few PST files to migrate, Locate and Migrate is likely to require least effort on your part. See About Locate and Migrate on page 43. Client-driven PST migration. This tool lets you configure users computers to locate PST files automatically and copy them to a central PST holding folder. Enterprise Vault then migrates the PST file contents from the holding folder to Enterprise Vault archives. You can also decide whether you want to give users control over migrating their PST files. Client-driven PST migration is useful in the following situations: Users' computers are available on the network only occasionally. You do not have permission to access PST files on the users' computers. Users need continual access to their PST files. See About client-driven PST migration on page 71. Feature comparison of PST migration tools Table 2-1 shows a feature comparison of the PST migration tools.

13 Introduction to PST migration About the Exchange PST Migration policy 13 Table 2-1 Feature comparison of PST migration tools Feature Scripted using Policy Manager PST Migrator wizard Locate and Migrate Client-driven migration Simple to use for a few PST files No Yes No No Locate PST files on users computers No No Yes Yes Allow users to decide whether or not to migrate the PST files that are found on their computers No No No Yes Allow users to manually submit PST files for migration No No No Yes Collect users PST files in central location No No Yes Yes Suitable for migrating large numbers of PST files Yes No Yes Yes Can use supplied password to open PST file No No Yes Yes Can adjust Exchange Server quotas No No Yes Yes Use marking in PST to determine archive Yes Yes Yes No Use mail profile entry to determine archive No No Yes Yes Use name of host computer to determine archive No No Yes No Migrate files to Internet Mail archives Yes Yes Yes No About the Exchange PST Migration policy To customize the way that PST files are migrated for a group of users, you can edit the settings in the Exchange PST Migration policy that is associated with the

14 Introduction to PST migration Improving performance when archiving PST file contents 14 provisioning group to which the users' mailboxes belong. Exchange PST Migration policies are listed under Policies > Exchange in the Administration Console. The Exchange PST Migration policy properties include settings to define the following: Whether to create shortcuts for migrated items, and where to create them. Custom shortcuts. Whether to adjust Exchange Server quotas to accommodate the additional shortcuts in mailboxes. The default retention category. The migration priority that the PST Collector and PST Migrator should use to collect and migrate PST files. The classes of items to migrate. Whether to allow users to submit PST files for migration and change the retention category of files that they choose to migrate. The paths that the Enterprise Vault Outlook Add-In should specifically look in or ignore when it searches for PST files on users' computers. Whether to migrate the Deleted Items folder and unexpired calendar items. The folder structure to create for shortcuts in users' mailboxes. The Windows code page to use if the PST Migrator creates folders in users' mailboxes. How to process PST files after successful migration. The notification s that you want Enterprise Vault to send for various PST migration events. When items have been migrated, the original items in the PST files are not deleted. If you want to delete the PST files after successful migration, choose to do so on the Post Migration tab of the PST Migration policy. Improving performance when archiving PST file contents When Enterprise Vault archives items, it converts the contents to HTML and indexes them. The default conversion timeout for this process is 30 minutes. Enterprise Vault makes three attempts to convert an item, and so can take up to 90 minutes before it fails an item and moves to the next one.

15 Introduction to PST migration Migrating PST files in hosted environments 15 If there are very large or complex items in a PST file, it can take a long time to migrate them all. If you do not need the content of the items to be indexed, you can improve performance by lowering the conversion timeout to a few minutes. To change the conversion timeout 1 On the Storage service computer, set the string registry value ConversionTimeout to the required timeout in minutes. The entry must be under the following registry key: HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault 2 Restart the Storage service. Note: This change to the conversion timeout also affects normal archiving, so remember to return it to the original value when you have migrated the PSTs. You can also improve performance by making Enterprise Vault create text versions rather than HTML versions of certain document types. See the Administrator s Guide for instructions on how to control content conversion. Migrating PST files in hosted environments For each mail item that Enterprise Vault archives, it creates an XML document that contains the item s sender information and recipient information. This document is archived with the item, and Enterprise Vault subsequently uses the XML data during indexing. Enterprise Vault builds the XML data it requires from the sender information and recipient information in each item as it is archived. However, if any of the information is not present in the item, Enterprise Vault attempts to establish a connection to the relevant Exchange server s domain controller to gather the information. This process requires that at least one Exchange server is targeted in your site. If you migrate PST files in environments where no suitable Exchange server is available to provide the information that Enterprise Vault requires, migration performance can be degraded. For example, this situation can arise in the following circumstances: You migrate legacy data from the PST files that were created in an old Exchange environment, whose Exchange servers no longer exist.

16 Introduction to PST migration About the Personal Store Management node 16 You migrate data from PST files in a hosted environment that has no Exchange server. In cases like these, you should set a registry value to bypass the lookup of addresses during archiving. To bypass Active Directory address lookups 1 On every Enterprise Vault Storage service computer, create a new DWORD registry value that is called BypassAddressLookups under the following registry key: HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault \Storage 2 Set BypassAddressLookups to 1. 3 Restart the Storage service. This setting allows PST migrations to use only the sender information and recipient information that it finds in each mail item that it archives. Enterprise Vault does not attempt to establish an Active Directory connection to resolve addresses. About the Personal Store Management node All the computers, mailboxes, and PST files that are found on the network are listed in various nodes under the Personal Store Management node. When you click Personal Store Management, the page that opens displays a summary view of all the computers, mailboxes, and PST files that Enterprise Vault manages. The Personal Store Management node has the following nodes: Files. This node contains information of the PST files that are being migrated or have been migrated to Enterprise Vault. You can use various options to change the migration status, priority, mailbox, archive, and retention category of the listed files. Computers. This node contains information of all the computers that have been found on the network. You can enable or disable PST file searching on the listed computers.

17 Introduction to PST migration About the Personal Store Management node 17 Mailboxes. This node contains information of the list of mailboxes that are enabled for archiving. You can enable or disable the listed mailboxes for client-driven migration. You can sort and filter the displayed information, and also saved a collection of items for future reference. You can also add, remove, or move columns to further customize the display. You can save the customization you make to the display. You can export the displayed items to a CSV file or an HTML file. Note that when you export the details, Enterprise Vault exports the information in all the columns irrespective of the customization made. Note: This node includes only those PST files that are searched and migrated to Enterprise Vault by the Locate and Migrate method or obtained by client-driven migration. This node does not include the files that have been migrated to Enterprise Vault using the wizard-assisted migration or the scripted migration. For more information about each node, see the Administration Console help. If the Personal Store Management is taking a long time to load, it could be because your Enterprise Vault server does not have a connection to the Internet. For a possible workaround, see the section called "Performance issues when an Enterprise Vault server has no Internet connection " in the Installing and Configuring guide. Creating filters The parent nodes - Files, Computers, and Mailboxes - each have a Filters node. The Filters node includes the predefined filters and the filter criteria that you have created and saved for future reference. When you click a filter node, the filter is run and the display is updated dynamically. Note the following: You can create up to 100 filters within each Filters node. You can configure this number by creating a new DWORD registry value that is called MaxFilterCount under the following registry key: HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault \Admin

18 Introduction to PST migration About the Personal Store Management node 18 Note: We recommend that you limit the filter count to 100. Exceeding this value may affect the performance of Enterprise Vault. The Filters node of each parent node includes predefined filters that you can use. You can rename or delete any of the filters created, including the predefined filters. To filter the list on the basis of multiple keywords, use commas to separate the keywords. To create and save filters 1 Select the filter criteria you want to use to refine the list. You may select multiple criteria by clicking the + button. Use the - button to remove filter criteria. For example, to filter the list to see only those files that have failed to migrate, do the following: In the first drop-down menu, select Migration Status. In the second drop-down menu, select contains any of. In the third drop-down menu, select Failed to migrate. 2 Click Apply. The display changes according to the filter criteria applied, and the Apply button changes to Save. 3 Click Save. 4 In the Save dialog box, do one of the following: Click Save filter and enter a name and description for the filter. Click Save results and enter a name and description for the saved results folder. Alternatively, you may choose to add the displayed items to an existing saved results folder. 5 Click Save. Saved filters are listed as separate nodes within the Filters node. When you click the saved filter, the filter is run and the display is dynamically updated. Saved results are listed as separate nodes within the Saved Results node, and displays static data.

19 Chapter 3 PST file ownership This chapter includes the following topics: About PST file ownership PST file marking to determine PST file ownership PST message sampling to determine PST file ownership About PST file ownership Establishing the ownership of a PST file is important for storing its contents into the appropriate user s archive. Enterprise Vault determines the ownership using several methods. If the PST file is found in a user's Outlook profile, then that user is considered to be the owner of the PST file. For all other PST files that are found on the network, Enterprise Vault tries to determine ownership in the following ways: PST file marking. You can configure the Enterprise Vault Outlook Add-In so that, when a user starts Outlook, the Enterprise Vault Outlook Add-In writes a marker into each PST file that is listed in the mail profile. The marker indicates the Enterprise Vault site, the associated archive, and the associated retention category. If PST Migrator finds one of these marked PST files, it can read this information and determine the mailbox that owns the default archive. See PST file marking to determine PST file ownership on page 20. PST message sampling. If you have chosen to use message sampling to identify the owner, and a possible owner is found, then that user's mailbox is used. See PST message sampling to determine PST file ownership on page 20. You can use message sampling as the initial method to identify PST file owners or you may allow Enterprise Vault to use this method only if PST file marking fails. You can configure this by editing the Personal Store Management properties.

20 PST file ownership PST file marking to determine PST file ownership 20 If Enterprise Vault cannot determine the ownership of the PST file, the associated mailbox, and its corresponding archive, then the PST file status is displayed as Not ready. You need to edit the properties of the PST file to provide the required information, and change the status to Ready to copy. You can also select a default archive to store the PST files that have no owners identified. PST file marking to determine PST file ownership Depending on configuration, when a user starts Outlook, the Enterprise Vault Outlook Add-In writes a marker into each PST file that is listed in the mail profile. The marker indicates the Enterprise Vault site, the associated archive, and the associated retention category. All the PST migration tools can use the marker to determine the owning mailbox and then migrate the file contents to that mailbox's default archive. Marking PST files can be enabled or disabled in Exchange Desktop policies using the setting, Mark PST files, in the list of advanced Outlook settings. If marking is switched on, the Outlook Add-In does the following when Outlook starts: Tries to open every PST that is listed in the user's mail profile. The next time that the user starts Outlook, the Outlook Add-In prompts for passwords to password-protected PSTs, and displays error messages for any inaccessible PSTs. Note: To avoid migration failures due to incorrect passwords or missing passwords, edit the General tab of the Personal Store Management properties to allow Enterprise Vault to override passwords and migrate the files. This feature is not available for client-driven migration. Does not update the PST file marker again except if a different mail profile was used to access it. Enterprise Vault assumes that the owner of the PST file is the last profile that was used to access it. Marks any further PST files that are subsequently added to the mail profile. The marking happens when Outlook is started, so merely opening a PST file and then closing it again is not sufficient to mark that PST. PST message sampling to determine PST file ownership PST message sampling determines the owner of each PST file by sampling a configurable percentage of the messages in the file. Depending on how you have

21 PST file ownership PST message sampling to determine PST file ownership 21 configured message sampling, the feature then sets the migration status of files whose owners have been identified to Ready to copy. See Results of message sampling on page 24. You can use the PST Ownership Identification tab of the Personal Store Management properties to configure the following: Use message sampling as the initial method to identify PST file owners. Allow Enterprise Vault to use this method only if PST file marking fails. Configure the following criteria: Sample size percentage: The percentage of messages within the PST file that you want Enterprise Vault to sample to look for possible owners. Ownership percentage: The percentage of associated messages within the sample size that decides ownership. Change migration state percentage: The percentage of messages that are associated with the assigned owner that decides whether the state of the PST file changes to Ready to copy. For example, for a PST file that has a 100 messages, when you set the sample size to 80%, Enterprise Vault scans 80 random messages to look for a possible owner. If you set the ownership percentage to 70%, Enterprise Vault assigns ownership to the user that has 56 or more associated messages in the PST file. If you set the change migration state percentage to 80%, Enterprise Vault checks whether the identified owner has 64 associated messages, and then changes the PST migration state to Ready to copy. Specify a default archive to store the PST files that do not have identified owners. The Locate and Migrate tool and the options to add single and multiple PST files in the Personal Store Management > Files node in the Administration Console use these settings to identify PST file owners. The ownership identification workflow depends on how you have configured message sampling. Table 3-1 details the owner identification workflow with respect to message sampling.

22 PST file ownership PST message sampling to determine PST file ownership 22 Table 3-1 Owner identification workflow Message sampling Disabled Only if PST file marking fails or the files are unmarked Use message sampling first Locate and Migrate Enterprise Vault tries to identify the owner using the following methods in the listed order: PST file marking PST file permissions Enterprise Vault tries to identify the owner using the following methods in the listed order: PST file marking PST file permissions Message sampling Enterprise Vault tries to identify the owner using the following methods in the listed order: Message sampling PST file marking PST file permissions Add single or multiple PST files Enterprise Vault tries to identify the owner using the following methods in the listed order: PST file marking PST file permissions Directory permissions on the folder Enterprise Vault tries to identify the owner using the following methods in the listed order: PST file marking PST file permissions Directory permissions on the folder Message sampling Enterprise Vault tries to identify the owner using the following methods in the listed order: Message sampling PST file marking PST file permissions Directory permissions on the folder To optimize performance, make sure that you turn off message sampling and run the PST Locator task to look for PST files. After the PST Locator task completes, turn message sampling on and run the task again to identify possible owners. Caution: The performance of message sampling depends on the number of items in the PST file. Configuring message sampling to determine PST file ownership You can use the Personal Store Management properties page to configure message sampling to determine the owners of PST files. Depending on how you configure

23 PST file ownership PST message sampling to determine PST file ownership 23 the message sampling settings Enterprise Vault changes the state of the PST file to Ready to copy, or stores the PST file in a default archive. To optimize performance, make sure that you turn off message sampling and run the PST Locator task to look for PST files. After the PST Locator task completes, turn message sampling on and run the task again to identify possible owners. Caution: The performance of message sampling depends on the number of items in the PST file. To use message sampling to determine ownership of PST files 1 In the left pane of the Administration Console, expand the hierarchy until you see the Personal Store Management node. 2 Right-click Personal Store Management. Then click Properties. The Personal Store Management properties are displayed. 3 Click the PST Ownership Identification tab. 4 Click Use message sampling and do one of the following: Select Only if PST file marking fails, or the files are unmarked. In this case, Enterprise Vault uses message sampling only if it finds unmarked PST files. Select Use message sampling first. In this case, Enterprise Vault uses message sampling to look for possible owners. 5 In PST file sample size, specify the percentage of messages in the PST file you want Enterprise Vault to scan to look for possible owners. 6 Select Assign ownership to users with this percentage of associated messages and specify the percentage of messages that are associated with a certain user within the sample size to assign ownership. You can specify a value in the range 1% through 100%. We recommend that you specify a value between 51% and 100%. 7 In the When no owner is identified section, do one of the following: Select Leave as unassigned. In this case, PST files for which no owner is found remain in the Not ready state. Select Assign to archive and browse to select a default archive to store the PST files that have no owners identified. For such files, the state changes to Do not migrate. 8 Click the Advanced tab.

24 PST file ownership PST message sampling to determine PST file ownership 24 9 Click Change migration state percentage, and then click Modify. Enter a value between Click Message type exclude list, and then click Modify. Enter the message classes you want Enterprise Vault to ignore when it scans the sample size for possible owners. 11 Click Apply, and then click OK to save the settings. Results of message sampling Depending on how you have configured message sampling, you can get any of the following results. Table 3-2 details the behavior of Enterprise Vault with respect to message sampling. Table 3-2 Results of message sampling Message sampling Resulting action PST migration status Message sampling successfully identifies the owner. Enterprise Vault matches the address or display name with the available Exchange mailbox user, and assigns the archive of that user to the PST file so that items are migrated to that archive. The PST file state changes to Do not migrate. If the percentage of associated messages matches the configured criteria for the change of migration state, the PST file state changes to Ready to copy. Message sampling has identified a probable owner, but the number of associated messages does not meet the configured ownership criteria. - The PST file remains in the Not Ready state. If you have specified a default archive to store PST files that have no owners identified, the PST file is assigned to the default archive and the state changes to Do not migrate. If the PST file is in the Not Ready state, you can manually assign the correct archive and change the state.

25 PST file ownership PST message sampling to determine PST file ownership 25 Table 3-2 Results of message sampling (continued) Message sampling Resulting action PST migration status Message sampling has identified multiple possible owners. For example, the PST file has 2 owners with 50% associated messages each or 3 owners with 33.3% associated messages each. Enterprise Vault displays this information in the More details section in the properties page of the PST file. The PST file remains in the Not Ready state. If you have specified a default archive to store PST files that have no owners identified, the PST file is assigned to the default archive and the state changes to Do not migrate. If the PST file is in the Not Ready state, you can manually assign the correct archive and change the state. Message sampling has identified the owner, but the associated archive is not found. This may happen in case the PST file is from outside the network or the user's mailbox is not enabled for archiving. Enterprise Vault displays this information in the More details section in the properties page of the PST file. The PST file remains in the Not Ready state. If you have specified a default archive to store PST files that have no owners identified, the PST file is assigned to the default archive and the state changes to Do not migrate. If the PST file is in the Not Ready state, you can manually assign the correct archive and change the state.

26 Chapter 4 PST migration: scripted This chapter includes the following topics: Overview of the scripting mechanism for PST migration Undertaking the PST migration process using Policy Manager Preparation for PST scripted migration Output from PST migration Example initialization file for PST scripted migration Overview of the scripting mechanism for PST migration You can perform scripted migrations of the contents of PST files to Enterprise Vault using Policy Manager. For detailed information on Policy Manager, see the Utilities guide. The scripting mechanism enables you to configure how each PST file is processed. For example, for each PST file you can do the following: Specify the destination archive. Specify whether to create shortcuts to migrated items and, if so, whether to leave them in the PST file or to put them in a specific folder in the user's mailbox. Specify which retention category to use for migrated items. Control what happens to the PST file itself after the items in it have been migrated. You write the Policy Manager initialization file, in which you list each of the files whose contents you want to migrate to Enterprise Vault. You can set up default

27 PST migration: scripted Undertaking the PST migration process using Policy Manager 27 settings that apply to all PST files and you can override the default settings for individual PST files. It is possible for you to make Enterprise Vault clients save details of the owner's default archive in each PST file (PST marking). Policy Manager can then use this information to determine the correct archive and mailbox to use for each PST file. If you prefer to not to use this mechanism, or to override it for some PST files, then for individual PST files you can override these values. When you migrate PSTs using Policy Manager you can use report mode to check all the PST files listed in your initialization file. This mode generates a new copy of the initialization file, with lines that identify any problems. Entries for PST files that cannot be processed are marked so that PST migrator ignores these files. You can then do either of the following: Fix any problems and run the Policy Manager in report mode again to see whether there are any more problems. When the file is error free, you can run it in process mode to process all the files. You can run in report mode as many times as needed. Each time, Policy Manager creates a new initialization file that you can then run normally or use to fix problems. Run in process mode immediately. Files that could cause problems have been marked so that Policy Manager ignores them. You can then decide later what to do with these problem files. Note the following: Policy Manager uses only message class and shortcut content settings from the Exchange PST Migration policy. The rest of the settings in the policy are ignored. Policy Manager can use the information written into the PST file by PST marking to identify the mailbox and archive associated with the PST file. Veritas recommend that you do not use Policy Manager to perform other tasks at the same time as performing PST migrations. If you have only a few PST files to migrate, you may find it easier to use the wizard-assisted PST migration tool instead. See About the PST Migrator wizard on page 35. Undertaking the PST migration process using Policy Manager In outline, you perform scripted migrations with Policy Manager as follows.

28 PST migration: scripted Preparation for PST scripted migration 28 To undertake the migration process using Policy Manager 1 Decide whether to use markers within PST files to determine their ownership. By default, PST files are marked. You can turn off PST file marking in Exchange Desktop policies using the setting, Mark PST files, in the list of advanced Outlook settings. See PST file marking to determine PST file ownership on page Write the Policy Manager initialization file to specify which PST files you want to migrate to Enterprise Vault. In the file, specify that Policy Manager is to run in report mode. Remember to save the initialization file in Unicode format. 3 Run Policy Manager in report mode with the initialization file. Policy Manager does the following: Checks that all the PST files listed are accessible. Creates a new initialization file that shows any problems with the listed PST files, such as files that could not be accessed or are password-protected. The new initialization file has the same name as the original, with a number added to make it unique. For example, if the original script was called PSTMigration.ini then the new script would be called PSTMigration_1.ini. Creates a log file with the same name as the original initialization file and a file type of.log. For example, if the original script was called PSTMigration.ini then the log would be called PSTMigration.log. 4 You can fix problems that are listed in the new initialization file, or you can leave them for later. 5 Run Policy Manager with the new initialization file. Policy Manager migrates the file contents and writes a log file with the same name as the initialization file and a file type of.log. If any PST files fail the migration process, Policy Manager automatically writes a new script that you can run to process just those failed files. If necessary, fix any problems and then run the new script to migrate the contents of just those PST files that were not processed before. Preparation for PST scripted migration Policy Manager only uses a limited number of settings in Exchange PST Migration policies. Enterprise Vault archives items from the PST files according to the following settings in your Enterprise Vault installation:

29 PST migration: scripted Preparation for PST scripted migration 29 Enterprise Vault archives only the classes of items that are defined as eligible for archiving on the Message Classes tab in Exchange PST Migration properties. The migration obeys the registry settings that are set for the Storage service. If you have configured customized shortcuts on the Shortcut Content tab of the Exchange PST Migration policy, then the PST Migrator uses these settings. Otherwise the shortcut content settings that are configured in the Exchange Mailbox policy are used. Items can be assigned a specific retention category during PST migration. Note: Some Enterprise Vault features, such as the retention folders and classification features, can override the specified retention category. For more information on retention, see the Administrator's Guide. The PST files must not be in use at the time of migration, so make sure that users do not have them open. You may find that it is better to move the PST files. The best procedure may be to gather all the PST files into the same place and then to migrate them from there. This makes it easier to generate the initialization file, assign permissions, and to manage files. Note though, that you may have some file name conflicts if there are PST files with the same name. Also, if any PST files are likely to be unmarked ensure that you know the owners because there may be no identifying information in the PST. The Vault Service account must have Full Control access to the PST file. The Storage service for the destination vault store must be running. PST files that are password-protected cannot be processed. You must remove such protection before migrating their contents. Alternatively, you may allow Enterprise Vault to override PST passwords during PST migration. To override passwords, enable Override passwords for password-protected PST files in the General tab of the Personal Store Management properties. If you intend to use the automatic PST compaction feature at the end of migrations, you may need some spare disk capacity for the compaction to take place. You can need as much as the size of the largest PST file, plus approximately 5% of its size. You may choose to ignore compaction if you plan to delete the PST files after migration. Policy Manager migration checks the mailbox storage limit when a mailbox has either Prohibit Send or Prohibit Send & Receive mailbox limits set. If both these

30 PST migration: scripted Output from PST migration 30 limits are set, Policy Manager does not move any item to the mailbox that exceeds the lower limit. If only one of the limits is set, then Policy Manager obeys that limit. Note that, even if the storage limit prevents items from being moved to the mailbox, the items are still archived in the appropriate archive. In this case you can increase the mailbox quota and then migrate the PST file again to move the items to the mailbox. Output from PST migration When you run Policy Manager with an initialization file containing a [PSTdefaults] section, Policy Manager automatically writes a new initialization file that contains details of any problems that it found. The new initialization file has the following features: There is a [PSTcheckpoint] section at the top of the file, summarizing the results of the run. If you had been using process mode then the following apply: All [PST] sections for files that were processed successfully are commented out. There is a JobStatus entry in each [PST] section, indicating for that file, either success or the type of error that occurred. [PSTcheckpoint] section PST scripted migration The contents of the [PSTcheckpoint] section vary according to whether you run the initialization file in report mode or process mode. Report mode [PSTcheckpoint] section The following [PSTcheckpoint] section results from running an initialization file in report mode. The Generation count of 1 shows that these results are from the first run of the file: [PSTCHECKPOINT] GENERATION = 1 CREATED = 02Oct :58:02 AM SOURCE = E:\EV\pstmigration\pstlist.ini PSTPROCESSEDCOUNT = 118 PSTNOTREADYCOUNT = 3 PSTWARNINGCOUNT = 2

31 PST migration: scripted Output from PST migration 31 The following entries are of interest: PSTPROCESSEDCOUNT = 118 shows that the file contains references to 118 PST files. PSTNOTREADYCOUNT = 3 shows that there are three files with problems. The Report_Error entries in the individual [PST] sections give you more information. Policy Manager automatically adds DONOTPROCESS = TRUE to each of these [PST] sections. PSTWARNINGCOUNT = 2 shows that there are two files with warnings. In this case, these are both marked PST files whose markings are intentionally being overridden. The Report_Error entries in the individual [PST] sections gives more information. Because Policy Manager has added the DONOTPROCESS = TRUE entries to each of the problem PST files, you could run this new initialization file in process mode immediately, leaving the problem PSTs to be addressed later. Alternatively, you could fix the problems, remove the DONOTPROCESS = TRUE entries, and then run the file again in either report mode or process mode. Process mode [PSTcheckpoint] section The following [PSTcheckpoint] section results from running an initialization file in process mode. The Generation count of 2 shows that these results are from the second run of the file: [PSTCHECKPOINT] GENERATION = 2 CREATED = 02Oct :59:36 AM SOURCE = E:\EV\pstmigration\pstlist.ini PSTPROCESSEDCOUNT = 115 PSTFAILEDCOUNT = 0 PSTUNPROCESSEDCOUNT = 3 PSTINCOMPLETECOUNT = 0 PSTPARTIALCOUNT = 0 The following entries are of interest: PSTPROCESSEDCOUNT = 115 shows that 115 PST files were processed. This is the same initialization file as shown above in the Report mode description. The three problem files have been left with DONOTPROCESS = TRUE entries, so Policy Manager has ignored them. PSTFAILEDCOUNT = 0 shows that there were no files for which processing could not be tried.