Quest® Public Folder Migrator for SharePoint
Version 2.2
Release Notes
May 12, 2008
Welcome to Public Folder Migrator for SharePoint
Resolved Issues and Enhancements
Quest Public Folder Migrator for SharePoint facilitates the migration of data stored in the public folders on Exchange Server to the SharePoint Server while preserving the folder hierarchy to ensure data consistency and availability. With your data assets moved to the SharePoint Server, you can benefit from its advanced features to enhance information sharing and document collaboration, increasing individual and team productivity.
New Features in Quest Public Folder Migrator for SharePoint:
|
Feature |
Enhancement |
Change Request |
| Names and Character Sets | Public Folder Migrator preserves extension during the file name truncation (by default, long file names are truncated to 122 characters). | CR#49160 |
| Permissions Revocation | Public Folder Migrator does not attempt to set new folder owner during the permission revocation if the migration job does not have the information about this user. | CR#49292 |
| SharePoint API mode | The "All day event" meetings are migrated using SharePoint Object Model. |
CR#00000 |
|
Source Items |
By default Public Folder Migrator only allows to select public folders that have local replicas on the specified source Exchange server for migration (applies to Exchange 2000, 2003 and 2007). In certain environments, e.g. using Exchange clusters, this might make it impossible to migrate public folders from the source Exchange server. To disable the request to Exchange servers 2000, 2003 or 2007 for local replicas of the public folders, create "GetLocalReplicas" DWORD value in the Public Folder Migrator key in Registry Editor (HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Public Folder Migrator) and set it to "0". If the value is set to "1", the Public Folder Migrator sends a local replicas request to the Exchange server (the same as the default behavior). |
CR#00000 |
The following is a list of issues known to exist at the time of Public Folder Migrator for SharePoint release.
|
Feature |
Known Issue |
Change Request |
| Configuration
|
If your Windows SharePoint Services are working with locally installed Microsoft SQL Server 2000 Desktop Engine (Windows) (the Typical option was selected in SharePoint Services setup), then Quest Public Folder Migrator for SharePoint should be installed on the same computer. Otherwise - if SharePoint Services are working with SQL Server - you can install the product on a dedicated computer. |
CR#157318, CR#0177766, CR#0166696 |
| If you have once installed the product, use the same installation path for all subsequent installations on this computer. | CR#0167564 | |
| To avoid possible data loss, administrative limit specified for MSMQ must be not less than 4GB (for the agent host). | CR#0174849 | |
| If a root target item (list, document library, or web site) is deleted, the migration job working with this item must be created anew. It is not necessary, if the root target item was restored manually from the recycle bin. | CR#0167832, CR#0175022 | |
| If a root source item (public folder) is renamed, the migration job working with this item must be created anew. | CR#0154149 | |
| SharePoint limitations for uploaded files (file type and file size) are enforced in accordance with the limits set in the XML file. | CR#0161039 | |
| If alerting is turned on for a target list or a document library, an alert notifying of object creation will be generated for every attempt to store an item to that location on target. | CR#0163030 | |
| A user whose account has insufficient permissions to access a migrated item on target will not be able to use the SharePoint Access Request form to request the access rights. | CR#0181265 | |
| If you had selected a folder to exclude from migration, and after that this folder was renamed, then exclusion is cancelled, and the folder will be migrated. | CR#0166070 | |
| Content of source public folders without local replica on the source Exchange Server is not migrated. It is not applicable to the source server running Microsoft Exchange 5.5. | CR#0160735 | |
| Migration agent sends folder content continuously if Prohibit post at value (size limit) is reached for that folder. | CR#0169870 | |
|
If you change the TCP port for the virtual server (hosting the target SharePoint) on your IIS, then you will have to re-create all your migration jobs. |
CR#0183040 | |
| Public Folder Migrator allows to create migration jobs for public folders on an Exchange 5.5 server that have no local replica on this server. You should plan your migration from Exchange 5.5 public folders carefully to avoid possible overload of WAN connections when transferring data from remote public folder replicas. | CRS#32385 | |
|
Source Item Types |
By default, migration is not supported for the source and target items of custom classes (types). |
CR#172244, CR#0169606, CR#0166846 |
| Migration of message with more than 500 recipients is not supported. For more information, see http://support.microsoft.com/?kbid=171907 and http://support.microsoft.com/kb/163202/EN-US/ . | CR#0169637 | |
| Problems may occur when trying to migrate Internet-like public folders (e.g., Internet newsgroups). To resolve the issue, exclude these folders when configuring migrations jobs. | CR#0162687 | |
| If a public folder is excluded from the scope of migration job, all its contents and subfolders are also excluded. | CR#0180225 | |
| If a source message has a link to any source location, then it will not be re-mapped to corresponding location on target after migration. | CR#0163881 | |
| Migration of OLE objects attached to source items fails in a Folder to List migration job. | CR#0182392 | |
| Migration of distribution lists is not supported. | CR#0164781 | |
|
Source items are migrated incorrectly to lists, if attachments in target lists are disabled. |
CR#0181053 | |
|
Names and Character Sets |
Target items cannot be created with the names longer than natively permitted by SharePoint configuration. |
CR#0163956 |
| When using the SharePoint Object Model mode, migration of mail and post items with To and CC field values containing more than 255 characters fails. When using the Direct SQL Database Access mode, migration is not performed correctly because the items are migrated, but these values are truncated. | CR#0171391 | |
| If two public folders with the same names are located on the same hierarchy level on the source, only the first folder's content will be migrated. To resolve the issue, rename one of these source folders. | CR#0160765 | |
| PFM cannot create site from public folders having a dot (".") in the name. | CR#50152 | |
|
If the default language of the migration agent host computer does not match the language of the public folder items, the resulting MSG files might contain question marks instead of non-English characters in the following message fields: Subject, From, To, CC, BCC, Posted To, Conversation, Categories. To avoid this issue, set the default language on the Public Folder Migrator computer to match the language of the public folder content that you want to migrate. For more information refer to Quest Public Folder Migrator for SharePoint User Guide. |
CR#0173700 | |
|
Target Items | ||
| Exceptions (date/time) configured in the Recurring Meetings are not migrated correctly. These exceptions are transferred as Recurring Meeting attachments after being converted to MSG files and can be opened and reviewed using Microsoft Outlook. | CR#0173155 | |
| When a public folders content is migrated using Direct SQL Database Access mode, migration of threads in discussion boards is not supported. | CR#0165729 | |
| This issue is applicable only for computers
running Microsoft Windows SharePoint Services 2.0 SP2 or Microsoft Windows
SharePoint Portal Server 2003 SP2.
After migrating the content of a public folder tree to a document library, the Title field of target items is not handled correctly: it will be removed if Check In or Check Out operation is performed on target item; so this field will be unavailable even if a user's view was configured to display it. To preserve the Title field, select the Edit Item option and then Save and Close before to perform the Check In or Check Out operation on the target item. |
CR#0182392 | |
| Since it is not provided by SharePoint, Public Folder Migrator does not support migration of the Recurring Tasks. | CR#0153742 | |
|
The meetings those are created with the following recurrence patterns: weekday, last day and weekend, are not supported by Microsoft Windows SharePoint Portal Server 2003. |
CRS#18609 | |
| Migration of calendar meeting workspace is not supported. | CRS#21540 | |
| The calendar items are not migrated correctly, if calendar items time zone does not match target SharePoint site time zone. | CR#47024 | |
| Migration of journal and sticknotes items created by Microsoft Outlook Web Access are not supported. | CRS#17715 | |
| Some fields of the tasks items (e.g. the Total Work field, the Actual Work field, the Companies field, etc.) are not migrated by default. | CRS#18318 | |
| When a public folder tree content is migrated to a document library, unnecessary subfolders Forms and Documents appear under the target document library in folder mapping preview. | CRS#21637 | |
| When a public folder tree content is migrated to a site, the name of root public folder in source public folder tree does not match the name of subfolder. Otherwise Public Folder Migrator will not be able to create child sites. | CRS#21880 | |
| When a public folders content is migrated using Direct SQL Database Access mode, migration of items font type and font color to public folder discussion board is not supported. | CRS#22365 | |
| After migrating the content of a public folder tree to a document library using Direct SQL Database Access mode, the custom fields (Follow Up, Importance, Conversation, To, Copy To, Categories, Original Sender) of the migrated office documents (DOC, XLS, PPT files) are not handled correctly: they will be removed if Check In or Check Out or Edit operation is performed on target item; so these fields will be unavailable (set by default) even if a user's view was configured to display it. To preserve the custom fields, select the Edit Item option and then Save and Close before to perform the Check In or Check Out or Edit operation on the target item. | CRS#32387 | |
| After migrating the content using Direct SQL Database Access mode the angle brackets are not removed from the Hyperlink field of target item resulting in wrong URL. To workaround the issue, select the Edit Item option, delete the angle brackets from the Hyperlink field and then Save and Close. | CRS#32640 | |
| The Original Sender column in a target discussion board contains unresolved account from the source Exchange forest when migrating public folder data across the forests. | CRS#30453 | |
| When a public folders content is migrated to a discussion board using Direct SQL Database Access mode, HTML tags in the plain text are not escaped and source message body can be lost partly in the view. | CRS#40505 | |
| Field "Last Updated" is not preserved during migration and set equal to the time of migration of the last reply item. | CRS#40527 | |
| When a calendar public folders content is migrated using Direct SQL Database Access mode, migration of the "All day event" items can be incorrect. The date of the items will always overlap. | CR#00000 | |
| When public folders content is migrated to a document library using Direct SQL Database Access mode, the Move operation from the document library Explorer view might not work properly with the migrated documents. | CRS#48339 | |
|
Redirection | ||
| If the Show home page by default for this user checkbox is configured Per User in the folder properties in Microsoft Outlook, and a user who is granted sufficient rights has cleared this checkbox, then this user can ignore the redirection and continue using this public folder (instead of corresponding item on SharePoint). | CR#0162512 | |
| Outlook Web Access users, as well as IMAP and NNTP clients cannot be redirected to SharePoint. | CR#0162515, CR#0163572 | |
| Redirection is not supported for Microsoft Outlook 97 users. | CR#0184695 | |
| Redirection via home page is not performed correctly in Microsoft Outlook 2000/XP. | CR#0184700 | |
|
Permissions |
Increased permissions when migrating a folder tree to a document library: Edit Items Own -> Edit List Items, Delete Items Own -> Delete List Items. |
CR#0181072,CRS#18777 |
| Users who were granted Folder visible permission on source items will not be able to access them on target after migration; access permissions should be granted manually. | CR#0182097 | |
| Permissions for Anonymous Access are not migrated. | CR#0181109, CRS#19092 | |
| If user was granted the Create Subfolder permission on source, then after Folder Tree to Document Library migration this user will be granted the Add List Items permission. | CR#0181684 | |
| If user was granted the Edit Own and Delete All (or Edit All and Delete Own) permissions on source, then after Folder Tree to List migration this user will be able to edit and delete all items (the Edit All/Delete All permissions will be granted). | CR#0182988 | |
| If user was granted the Folder Owner permission on source public folder, then after the migration this user will obtain the extra permission to Read Items as well. | CRS#19034 | |
| Because of using HTTP to create the SharePoint objects (lists, document libraries and sites), it is strongly recommended to turn off the Anonymous Access for the target top-level site to perform the migration process. | CRS#18955 | |
|
If the name of user-created permission level matches the name of pre-set Public Folder Migrator permission level, then it will be used for migrating permissions. This may result in increasing or decreasing the user permissions on the target. |
CRS#18869 | |
| Quest custom list templates are not available when migrated user creates a new list on the SharePoint target. To allow users to create new lists using custom list templates, grant users the rights on the List Template Gallery. | CRS#18879 | |
| Users of trusted domain can not be resolved as Associated external account. | CRS#19433 | |
| When Public Folder Migrator tries to add an Active Directory domain administrator group like "DomainName\Administrators" to SharePoint, the error "The user does not exist or is not unique" occurs, because SharePoint doesn't allow you to add this group to the SharePoint User Information List. | CR#44466 | |
|
When the SharePoint API migration mode (default) is used and permissions migration is enabled, it is not recommended to have more than 3 migration jobs running simultaneously on a single SharePoint server. Exceeding this limit may result in poor migration performance, time-outs and unexpected SharePoint errors. You can use the following options to avoid simultaneous execution of too many migration jobs on a SharePoint server: schedule migration jobs to run at non-overlapping time intervals or distribute migration jobs across multiple Public Folder Migration installations on different SharePoint servers in the farm. |
CR#44467 | |
| Migration of security permissions is not supported in deployments running Exchange 5.5. | CRS#32384 | |
|
SharePoint API mode |
SharePoint Object Model mode is used by default and can not be changed during product setup. Please contact to Quest Support if you want to change the applying mode to Direct SharePoint database access mode. | CRS#00000 |
|
Source items attachments (EXE files) blocked from the Web site by the server administrators are not migrated. |
CRS#21256 | |
| By default public folder to a list migration is not supported if target list is not based on the Quest custom list templates. | CRS#21194 | |
| Using of SharePoint API for migration requires the migration agent to be installed locally on SharePoint 2007 (Microsoft Office SharePoint Server 2007 and Microsoft Windows SharePoint Services 3.0). | CRS#00000 | |
| Migration of the public folder content to the SharePoint 2007 through front-end SharePoint Web server may fails, if an internal incoming URL to Default Zone for this front-end server is not added in Alternate Access Mapping. | CRS#22746 | |
| Importing a job | If a user provides an incorrect name of the root public folder in the CSV file, the folder will not be processed by the Source Agent. | CRS#40519 |
| By default Public Folder Migrator uses the “,” delimiter to import a job from a CSV file. This is the default list separator on the English locale. To change the Public Folder Migrator delimiter, contact to Quest Support. | CR#00000 | |
| When importing a job, the Retain Authorship option is on by default and is non-configurable. | ||
|
Miscellaneous |
Post item duplicates are not prevented from being created on target after the Post is modified on source. To avoid duplication, open the existing Post item, select Edit\Revise content, modify the item's body, then click Save. |
CR#0162045 |
| This issue is applicable only for computers
running Microsoft Windows SharePoint Services 2.0 SP2 or Microsoft Windows
SharePoint Portal Server 2003 SP2.
After the migration, daily recurring events occurring every weekday are not displayed in the Calendar view. |
CRS#17503 | |
|
You may occasionally see the Security Apply Exception error in the Migration Issues Tool, which does not correspond to any actual permission migration errors and can be ignored. |
CR#44406 | |
| If you add new messages to a public folder after some messages from the folder failed to be migrated, and the number of new items equals or exceeds the number of failed messages, the migration agent will migrate new messages and the job will be completed. | CR#0180193, CRS#22425 |
To upgrade Public Folder Migrator for SharePoint from versions 1.5, 1.6, 2.0, 2.1 or 2.1.1, 2.1.2, 2.1.3 to 2.2, wait until the current migration job is completed and then run the setup program and complete the installation.
Before installing Public Folder Migrator for SharePoint, ensure your system meets the following minimum hardware and software requirements:
| Platform | Intel x86 (500MHz or higher) |
| Operating System | Microsoft Windows Server 2000 or later |
| Additional Software & Services |
Either of the following:
|
| Platform | Intel x86.(500MHz or higher) |
| Operating System | Microsoft Windows Server 2003 SP1 or later |
| Additional Software & Services | Either of the following:
Either of the following:
|
| Memory | 1 GB recommended |
| Platform | Intel x86, x64 (500MHz or higher) |
| Operating System | Microsoft Windows Server 2003 SP1 or later |
| Additional Software & Services | Either of the following:
Quest Site Administrator for SharePoint 1.6 |
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation. This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
The Public Folder Migrator for SharePoint CD contains the following products:
For installation instructions, refer to Quest Public Folder Migrator for SharePoint User Guide.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.
This document 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.
© 2008 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
The information in this document is provided in connection with Quest 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 products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST 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 BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest 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 does not make any commitment to update the information contained in this document.