Converse agora com nosso suporte
Chat com o suporte

Migrator for Notes to SharePoint 7.1 - Release Notes

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Notes Rich Text -> HTML Conversion - In the case where you are converting a Notes document that is stored in a Lotus' native rich text (CD) format to HTML for storing in SharePoint, there are currently some limitations in the HTML that is generated. Certain features are not supported in SharePoint HTML. In particular:

The following features are not yet supported at all:

N/A

Extracting Embedded OLE Objects - If you migrate object types that are not listed below, a default conversion behavior is applied and the migrated files will have the .obj extension.

N/A

All data are conducted in the time zone of the local machine. All Notes date/time values in Notes documents will be correctly converted to "local" time and saved as such in SharePoint, but the time zones used in the original Notes documents are lost. A workaround for this would be to use @formulas to retrieve time zone information separately.

N/A

When using a class rule to automatically assign SharePoint Target Sites, it is possible to end up with multiple databases targeting the same site URL, and thus the same SharePoint site. This is perfectly legal as far as our tool is concerned and is sometimes very useful, but it may or may not be what you intended. In the most extreme case, you could have several entire QuickPlaces/Quickrs (each with multiple lists and sub-rooms) all being merged into a single SharePoint site.

In particular, the default Class Rule for QuickPlace/Quickr sites uses Application Name to generate Relative URLs for the corresponding Site Creation plans. Thus, if two QuickPlaces/Quickrs have the same name (or names that differ only by the case of the characters) this could result in the above condition. Possible workarounds are:

N/A

When migrating to document sets, the uniqueness of document sets is completely determined by the data that is mapped to the document set Name property. For example, if you map the Notes “Subject” to the document set Name property, two documents with the exact same Subject will get merged into the same document set! In future releases, we will detect such name collisions and append a sequence number when needed, as we currently do with generated documents, etc. For now, the user is responsible for mapping a value that will uniquely identify the document (for example a document ID number or a value that is computed with a formula) to the Name property.

N/A

The Front-End Services solution (part of the full Services installation) contains a SharePoint Feature called the “Migrator for Notes to SharePoint Link Redirector”. The installation program attempts to automatically activate this Feature on all existing site collections, there some environments where this does not work. Also, the feature is not automatically activated when new site collections are created. In both cases, you may need to go to Site Settings -> Site Collection Features and manually activate the “Migrator for Notes to SharePoint Link Redirector” feature.

N/A

When generating PDF documents, the font specified in Notes will be used to render rich text in the PDF documents. When we detect that the installed font does not support all the characters required by the content being migrated, we substitute the “Arial Unicode MS” font instead. This allows us to handle most extended character sets you are likely to encounter, it may not be the highest fidelity choice for a given situation. Also this font (which is part of Microsoft Office), may not be installed on all migration workstations without a copy of MS Office installed.

N/A

If a table cell contains content too lengthy to fit on a single page, it is not split and continued on the next page. In these cases, the page height is extended to accommodate the content of this cell.

N/A

The installation program prompts the user for the Notes program and data directories using values derived from registry settings on the local computer. Because the registry settings on the local machine may not be set correctly, please double check them and correct them manually if needed. There is no directory browser available to assist the user in locating these directories.

N/A

If SharePoint is removed from the machine before removing Migrator for Notes to SharePoint, the Migrator for Notes to SharePoint Services will not uninstall properly. Uninstall Migrator for Notes to SharePoint before uninstalling SharePoint.

CR57655

When running Lotus Notes on Vista, you may receive the following error in the Setup Wizard when the Console is launched for the first time: 'Can't initialize Notes session'

Below are the links to the IBM documents describing the support for Notes on Vista:

http://www-01.ibm.com/support/docview.wss?uid=swg21252343

http://www-01.ibm.com/support/docview.wss?uid=swg21269041

CR61026

When connecting to SharePoint servers using Claims-based authentication, the authentication cookies that the tool stores may expire in the middle of a migration job.

N/A

After Quickr 8.5 forums migration, SharePoint 2013 Community Categories tile shows 0 replies when replies are actually migrated.

Git# 8

You cannot migrate documents 500 MB or greater using Web Services.

Workaround: Use the Import Service Mode.

Git# 9

MS-Word 97 documents cannot be embedded to a word document by Aspose.

Git# 282

When documents are migrated to SharePoint by Web Services of SharePoint 2010, the count of the documents shown in a list view cannot exceed a threshold limit set by SharePoint, even if views are set in SharePoint to allow this. Migrator for Notes to SharePoint must query the entire list/library to check for duplicates.

There are two workarounds to this limitation:

1) Use the Import Service Mode.

2) Index the NotesUNID column using the SharePoint Server API.

Git# 337

When migrating a multi-user field in a Notes attachment to a multi-user field in SharePoint, users are not added if the attachment has Office 2007 format files.

Workaround: Use the PowerShell script to disable document parsing in the SharePoint web site during Notes document migration, as follows:

Enable parsing after migration.

Git# 352

You cannot edit a document that contains a table in Word Online.

Git# 114

Link Finalization service does not support several migrations of the same content. Only links in documents from the latest migration will be finalized.

Git# 63

Migration will fail when using Import Service with the target template is "Page Library 2010/2013" and the template of the Site Collection is "Publishing Portal”.

Workaround: Use Web Services.

Git# 138

A time out exception is occasionally reported when migrating using Azure Turbo mode.

Workaround: None. All documents are migrated successfully.

Git# 424

Limitations

The following are limitations to Quest® Migrator for Notes to SharePoint:

System requirements

Before installing Migrator for Notes to SharePoint 7.1.0, ensure that your system meets the following minimum hardware and software requirements.

 

Client Hardware and Software

Notes Data Extraction

Privileges

Lotus Notes or Domino

Migrator for Notes to SharePoint Console

Database

SharePoint Data Load using web services

SharePoint Data Load using Import Service

System path

Content migration

Hardware Requirements

Processor

Intel Core i7

Intel Core i9, X-Series or higher

Memory

16GB

32GB

Disk Drives

Dual hybrid disk drives

C: OS and Program Files

D: Data Files

Dual SSD drives

C: OS and Program Files

D: Data Files

Network Card

100 Mbps

1Gbps

 

Server Hardware and Software/SharePoint

Same prerequisites as those required by SharePoint.

For a list of requirements for SharePoint 2013, see http://technet.microsoft.com/en-us/library/cc262485.aspx.

For a list of requirements for SharePoint 2016, see https://technet.microsoft.com/en-us/library/cc262485(v=office.16).aspx.

For a list of requirements for SharePoint 2019, see

https://docs.microsoft.com/en-us/SharePoint/install/hardware-and-software-requirements-2019

Database

Installation Privileges

Privileges to run Migrator for Notes to SharePoint

SharePoint Privileges

Import Services

Configuration Privileges

Link Tracking Service

Content migration

For upgrading Migrator for Notes to SharePoint Client from a version previous to 6.3.x to version 7.1.0, uninstall your current version of Migrator for Notes to SharePoint. Then follow the Installation instructions in this document.

If you are upgrading from Migrator for Notes to SharePoint 6.9.1, you need to run the license upgrade tool after installing the new version to make your license consumption data available in the License Status dialog box. The tool is located at <MNSP_Home>\bin\UpgradeLicenseData.exe, you can run it by double clicking or from a command prompt window.

If you are upgrading from a 5.0 Repository database and you need the new Quickr classification rules, you may open both your Repository database and the QuestRepository.ntf template in Notes and copy the documents containing the Quickr classification rules from the template to your Repository database.

For upgrading Migrator for Notes to SharePoint client from version 6.3.x to version 7.1.0, you can do an in-place upgrade.

For upgrading Migrator for Notes to SharePoint services from a previous version to 7.1.0, uninstall your current version first.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação