|
The Name field is used to distinguish between defined SharePoint environments if you have enabled and defined more than one environment. To define more than the standard default, select the Enable multiple SharePoint environments check box. | |||||||||||||||||
|
Use the Type dropdown to control the mode of operation. The Type dropdown has the following options:
NOTE: You can use the Forms-Based Authentication environment type to access Office 365 SharePoint sites. The advantage of using the Office 365 Authentication environment type is that Migrator for Notes to SharePoint can authenticate with SharePoint without user intervention.
| |||||||||||||||||
|
Click this button to define options for your SharePoint environment.
The options for environments using the Microsoft Web Services are:
The options for environments using the Quest Import Service are:
| |||||||||||||||||
| |||||||||||||||||
|
Click the Credentials link to enter your SharePoint user name and password. NOTE: For the Forms Based authentication Type, the Credentials link is not active until you click Add to add the SharePoint site URL to the SharePoint Site Collections list. For all other Types, the Credentials link is active right away.
If you are using single sign-on and want to use Windows authentication in Migrator for Notes to SharePoint to be able to authenticate with Office 365, select the Use Windows authentication radio button.
| |||||||||||||||||
|
Click the Add button to add your particular SharePoint site URL to the SharePoint Site Collections list and test connectivity to those sites. Note that you do not need to specify each sub-site here; Migrator for Notes to SharePoint can discover those automatically. To add a site, enter the site URL, including "http://" or "https://", and click OK in the Add SharePoint Site dialog box. To test a site, select it and click the Test Connections link. | |||||||||||||||||
|
Click the Blocked Files button to configure the maximum allowed file size property and define the list of disallowed file extensions. These settings will be used at Analysis time to report on which databases have blocked files and oversized attachments. They will also be used at migration time to improve performance and memory utilization by not extracting such files from the Notes databases and not sending them to SharePoint. From the Configure Blocked Files dialog box, you can add your own blocked file extension list or use the list from SharePoint by clicking the Set to SharePoint defaults link. |
Migration of data directly to a SQL Server database can be turned on and configured from this tab.
|
To add a server click Add and enter the server name. To edit, select an entry and click Edit. To delete, select and entry and click Delete. Click OK to save changes. To add several servers at once, copy them to your clipboard using a coma, semi colon, or a new line to separate each server name. Click the Paste button to copy them to the list. | |
|
To use link tracking for your migrated SQL Server data, check the Enable Link Tracking for SQL Server records check box. Enter the Link Redirector Url you want to use with the content being migrated to SQL Server. The Database Settings link will take you to the Link Tracking tab where you can edit the Link Tracking database information. | |
|
To perform mappings using the client rather than the server, select this check box. The Mapping Options link will take you to the User Mapping tab where you can edit the user mapping information. |
This tab allows you to enter a root folder to which to migrate data.
|
To use link tracking for your migrated data, check the Enable Link Tracking for files check box. Enter the root folder you want to use with the migrated content. The Database Settings link will take you to the Link Tracking tab where you can edit the Link Tracking database information. |
Server Name: The Domino server to search. Leave blank to search the local address book.
View Name: The view to search in each configured directory database, which should be indexed such that it is sorted by the Notes user name. (The $Users view in standard address book databases do this by default, but you may also specify a customized view to use.)
Item Name: The item that stores the Domain name (typically an Active Directory name) that is used for logging into SharePoint.
Server Name: The Domino server to search. Leave blank to search a local database book.
Database Name: The database to search.
View Name: The view to search in the database, which should be indexed such that it is sorted by the Notes user name.
Item Name: The item that stores the Domain name (typically an Active Directory name) used for logging into SharePoint.
ADSI path: Specify the path to the Active Directory (or other LDAP) server that contains the user mappings. You can actually use any ADSI path here including "GC://" for the global catalog and "WinNT://" for the local metabase.
Query String: Specify a valid query string for finding the user based on the Notes Name. For example, if your policy is to store the Notes Name in the Description field of Person records in Active Directory, you might specify "(&(ObjectClass=Person)(description={0}))" as the Query String. The {0} part is replaced with a formatted version of the Notes Name and the entire Query issent to the directory server. For example, if the Person has a field called "distinguishedName" and was formatted as Windows names (like "PROD\Joe Smith"), then you would use a query like: (&(ObjectClass=Person)(distinguishedName={0}))
Field to use: Indicates the field to use in the directory lookup. By default, the ‘distinguishedName’ property is used. This should work in most cases, especially when the directory you are querying is the same one SharePoint uses. In rare cases, this name will not work. If there is a different directory property (other than ‘distinguishedName’) that contains a more useful version of the name that would work in SharePoint, use this field to indicate the different property.
ADSI login name and ADSI password: Specify authentication credentials. | |||||||||
Format: The mapping file can be formatted as an XML file or a Comma Delimited file. An example of each format is shown below:
<?xml version="1.0" encoding="utf-8"?> <identityMappings> <userMappings> <user notes="Joe Cool/NMSP" sharePoint="NMSP\jcool"/> <user notes="Mike Mulligan/NMSPTest" sharePoint="BUNTING\mike"/> </userMappings> <groupMappings> <group notes="QuickPlaceAdministratorsSUGroup" sharePoint="BUILTIN\Administrators"/> <group notes="Authorized Users" sharePoint="NMSP\Team 101"/> </groupMappings> </identityMappings> Joe Cool/NMSP, NMSP\jcool Max Smart/NMSP, BUNTING\mike Path: The location of the mapping file.
| |||||||||
|
Allows you to define a string to format the output of the user mapping. In the string, "{0}" represents the output of the user mapping. If you want to add "prod\" to each of the mapped names, enter prod\{0} as the format string. To test each of the mapping modes, click the Test User Mapping link. Type in a test Notes name and click Lookup. The resulting mapped user name appears in the After Name Translation and After Name Lookup fields. Click Validate in SharePoint to resolve the name that your configured mapping process produces. This capability is only available when using client-side user mapping and not when configuring server-side mapping in the Import Service. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
