Quest Notes Migrator for SharePoint

1. Quest Notes Migrator for SharePoint Steve Walch, Senior Product Manager Blog: http://notes2sharepoint.org November, 2011 Partner Training Webcast Series - Session 4 Tool Deployment, Domino.Doc and QuickPlace / QuickR

2. Partner Training Webcast Series • Migration Basics with the NMSP Designer Client • Analysis and Automation with the NMSP Migration Console • Advanced Content Migration Jobs • Tool Deployment, Domino.Doc and QuickPlace / QuickR migrations • Migrating Application Designs • Tips and Tricks for Managing Large Migration Projects • Even More Advanced Content Migration Jobs (Product demos using NMSP 6.1 beta)

3. Today’s Agenda Tool Deployment, Domino.Doc and QuickPlace / QuickR migrations • Understanding tool deployment options • Migrating via SharePoint 2010 Web Services • Migrating via the NMSP Import Service • Installing and configuring the Import Service • QuickPlace/QuickR migration jobs • Automated QuickPlace/QuickR migrations • Domino.Doc migration jobs • Automated Domino.Doc migrations

4. Installing the NMSP Clients • NotesMigratorForSharePoint-Clients-6.x.x.x.msi • Client Prerequisites • Windows XP / Vista / 7 / 2003 / 2008 • .NET Framework 3.0 • Lotus Notes 5.04 client or higher (6.x preferred) • Watch out for Windows UAC issues • Windows Vista / 7 virtualizes Program Files folders if UAC enabled • Certain Notes client versions do not handle this well • When possible, install Notes elsewhere (C:\Lotus\Notes) • Additional Migration Console Prerequisites • Microsoft Management Console (MMC) 3.0 • Microsoft Report Viewer 2005/2007 (optional) • Visual Studio Report Designer (optional)

5. Configuring the NMSP Clients • Designer Client • Options button, or Tools -> Options menu • Migration Console • First Time Setup Wizard • Top “NMSP” node -> Advanced Configuration Options • NMSP.EXE (command line) • Set configuration using above clients • All clients share same configuration • <ProgramData>\Quest Software\NMSP\6.0\Options.config • <AppData>\Roaming\Quest Software\NMSP\6.0\UserOptions.config

6. Major Client Configuration Settings • Notes tab • Password, Notes.INI file, Group resolution server, HTTP link resolution • SharePoint tab • Connection types, Credentials, Target site collections • General tab • Logging level, Allow deletion of SharePoint Records • User/Group Mapping tabs (optional for Import Service) • Mapping sources and configuration • Link Tracking tab (optional for Import Service) • Link Tracking database connections • Discovery tab (Migration Console only) • Discovery locations, Excluded users, Preferred server order

7. SharePoint Connection Options • SharePoint 2010 Web Services • Easier to deploy and start migrating • No direct server access required • Supports Forms/Claims Based Authentication • Supports direct Office 365 migrations • NMSP Import Service • Supports SharePoint 2007 and 2010 • Can be over 5x faster in some cases • Supports out-of-band attachment handling • Allows server-side User/Group Mapping and Link Tracking database • Direct Connection • NMSP clients on SharePoint Server (SharePoint 2007, 32-bit only)

8. Migrate via SharePoint 2010 web services Migration Workstation NMSP Clients Notes R5+ DLLs QuickR server Domino server Domino server Link Tracking Database User Mapping Source MS Web Services Front End Servers

9. Installing the NMSP Services • NotesMigratorForSharePoint-Services-64bit- 6.x.x.x.msi • Prerequisites • Windows Server 2003 / 2008 • SharePoint WSS 3.0 or MOSS 2007 or SharePoint 2010 • Installer access • Admin access on the server, farm, site collection • Access to SP config database • Import Service account access • Admin access on the server, farm, site collection • Member of IIS_WPG (on IIS6) and WSS_WPG groups • Access to SP configdatabase and content databases Detailed permissions doc

10. Services Components • Import Service • Stand-alone Web App implements WCF web service • Deployed to IIS with specified host, port, service account • Install on one or more WFE servers • Front-End Services solution • Components that run at part of SharePoint Site • Configuration Pages • Link Redirector Page (QuestLinkTracking.aspx) • Import Service bootstrapping page (NMSPServicesInfo.asmx) • Install on any WFE; Deployed as farm solution automatically • Administration Services solution (optional) • Alternate version of Configuration Pages • Install on any WFE; Deployed to Central Admin servers automatically

11. Configuring the NMSP Services • Settings maintained per Site Collection • Use Configuration Pages in Site Collection Admin or Central Admin • Stored in Site Collection property bag • Clients read options via bootstrapping page (NMSPServicesInfo.asmx) • Configure use of Import Service • Import Service location • Import Service service account identity • Shared Folder for large attachments (optional) • User/Group Mapping options (optional) • Configure use of Link Tracking Service • Location of Link Tracking Service • Link Redirector Page options

12. Migrate via Quest Import Service Migration Workstation NMSP Clients Notes R5+ DLLs QuickR server Domino server Domino server Link Tracking Database NMSP Import Service User Mapping Source Front-End Services: ► NMSPServicesInfo.asmx ► Configpages ► QuestLinkTracking.aspx Admin Services (Optional): ► Config pages WCF Web Service Front End Servers Central Admin

13. Debugging the NMSP Services • Test Connections link on Options -> SharePoint tab • Test links in service configuration pages • Try these URLs from your browser • <host>:<port>/ImportSession.svc • <sharepoint>/_layouts/NMSPServicesInfo.asmx • <sharepoint>/QuestLinkTracking.aspx • If Import Service not running • Check configuration in IIS Manager • Restart Application Pool • Check IIS logs

14. Migrate via SharePoint 2010 web services (2) Migration Workstation NMSP Clients Notes R5+ DLLs QuickR server Domino server Domino server Link Tracking Database User Mapping Source Front-End Services: ► Config pages ► QuestLinkTracking.aspx MS Web Services Front End Servers

15. Installing the Sandbox Redirector Page • Simplified version of Link Redirector Page • Does not connect to Link Tracking Database • Reduced functionality: Can only redirect to Notes • Intended as a placeholder until links are Finalized • Deploy as a Sandbox-safe solution • May be deployed by any Site Administrator • Site Administration -> Galleries -> Solutions • Allowed on locked down environments (such as Office 365)

16. Migrate via SharePoint 2010 web services (3) Migration Workstation NMSP Clients Notes R5+ DLLs QuickR server Domino server Domino server Link Tracking Database User Mapping Source MS Web Services SandBox Safe Link Redirector (Optional): ► QuestLinkTracking.aspx Front End Servers

17. What’s special about QuickPlace/QuickR? • Similar to SharePoint Team Sites • Different databases implement Places and Sub-Rooms • End-users can easily create their own… and they often create a lot! • Completely data driven • All places/rooms typically use the same Notes design template • Configuration documents describe place organization and features • Customization may be done by end-users • Folders and Lists • Custom Page Types (and columns) • Menus • Place specific Users (not in Domino Directory) • Entirely web based Domino application • Stores HTML instead of native Notes rich text

18. Designing QuickPlace/QuickR Migration Jobs • Specify QuickPlace / QuickR as data source • Select from predefined list of servers • Scope of Migration job is top level room or sub room • Source Data Definition -> Document Selection • Filter by Standard Type • Filter by Published Status • Filter by Form Used (aka Page Types) • Source Data Definition -> Data Fields • Most standard fields are implicitly available • Only specify custom fields • Predefined Source Data Definitions available • Don’t forget to configure HTTP Link Detection!

19. QuickPlace/QuickR Migration Jobs

20. Discovering QuickPlaces in the Migration Console • Database Discovery recognizes standard QuickPlace / QuickR databases as “Unorganized” • Does not read configuration documents • Discover Quickplace / QuickR Organization • Reads configuration documents to determine place/room hierarchy • Organize databases into “Application” node hierarchy • Special syntax for discovering one specific place • <server>;<folder name> • Some rooms may be remain “Unorganized” • Possibly because of access control • Possibly because they are truly orphaned

21. Analyzing QuickPlaces • Discover first (previous slide) • Usage Analysis • Includes place-specific users • Data Analysis • Excludes configuration documents • Design Analysis • Interprets end-user customization • Example: Page Types instead of Domino Designer Forms

22. Automating QuickPlace Migration with Classes • Predefined Technical Classes • Separate classes for “top level” place and sub-rooms • Automatically mirror Place / Sub-room hierarchy • Provision SharePoint sites using standard Team Site template • Enable replacement of QuickLaunch area with QuickPlace menus • Standard Migration jobs for each room • Pages • Calendar • Tasks • Discussion • Welcome page -> Announcement (top level place only)

23. Overall QuickPlace / QuickR Migration Process • Prerequisites • Discover QuickPlace / QuickR Organization • Configure Link Tracking, HTTP Link Detection, User Mapping • Edit QuickPlace / QuickR Technical Class • Assign target site collection URL • Customize desired site settings / migration jobs (next slide) • Apply Class rules for top-level place • Applications -> Place node, Including all children • Customize desired settings for specific rooms • Example: Customize migration job for custom form fields • Run “Migrate to SharePoint” function • Applications -> Place node, Including all children • Including Site Provisioning and Navigation Provisioning

24. NMSP Defaults you may want to change • Site / sub-site names, URLs and site templates • Map site-level permissions • Navigation provisioning (menus) • Migrate welcome page to announcements? • Which migration jobs to run for places vs. sub-rooms? • Migrate “orphan” documents in migration jobs? • Change permission mappings in migration jobs? • Migrate to pages instead of lists? • Map additional columns, etc.

25. What’s special about Domino.Doc? • Similar to SharePoint Document Libraries • Versioning, Check-in / Check-out • Different databases implement Libraries, Cabinets, Binders • Domino.Doc Cabinet similar to SharePoint Library • Domino.Doc Binder similar to SharePoint Folders • Documents are usually single file attachments • Safe to map attachments to Doc Library • Except when they are not! • May contain Notes rich text or multiple attachments • May be better to map to List Items, Document Sets, etc. • Common Customizations • Custom Binder Types • Custom Folder Types • Custom Views

26. Designing Domino.DocMigration Jobs • Specify Domino.Docas data source • Select from predefined list of servers • Scope of Migration job is cabinet • Source Data Definition -> Document Selection • Filter by Major/Minor Versions • Filter by Published Status • Filter by Document Type • Filter by Binder • Source Data Definition -> Data Fields • Most standard fields are implicitly available • Only specify custom fields • Predefined Source Data Definitions available

27. Domino.Doc Migration Jobs

28. Discovering Domino.Doc libraries in the Console • Database Discovery recognizes standard Domino.Docdatabases • Does not read configuration documents • Discover Domino.Doc Organization • Reads configuration documents to determine library/cabinet hierarchy • Organize databases into “Application” node hierarchy • Special syntax for discovering one specific library or cabinet • <server>!<database name>

29. Automating Domino.Doc Migration with Classes • Predefined Technical Classes • Separate classes for Libraries and Cabinets • Automatically mirror Library / Cabinet hierarchy • Provision SharePoint sites for each Library (if desired) • Standard Migration jobs for each Cabinet • Maps attachments to standard Doc Library template • (See earlier caveat!)

30. Overall Domino.Doc Migration Process • Prerequisites • Discover Domino.Doc Organization • Configure Link Tracking, HTTP Link Detection, User Mapping • Edit Domino.Doc Library / Cabinet Technical Class • Assign target site collection URL • Customize desired site settings / migration jobs (next slide) • Apply Class rules for top-level Library • Applications -> Library node, Including all children • Customize desired settings for specific Cabinets • Example: Customize migration job for custom document types • Run “Migrate to SharePoint” function • Applications -> Library node, Including all children

31. NMSP Defaults you may want to change • Provision new site for each library? • Map site-level permissions? • Migrate all versions? • Migrate unpublished documents? • Change permission mappings in migration jobs? • Migrate to lists instead of libraries? • Migrate to document sets? • Map additional columns, etc.

32. Notes Migrator for SharePoint 6.1 Beta Program • Beta in progress now! • Go to http://communities.quest.com/groups/notes-migration-product-beta-group • Sign in with your Quest Community ID • Or register to create a new one • Use corporate email (No gmail or hotmail accounts) • Press the “Ask To Join This Group” button • Once approved, log in and download • Reviewers Guide • Product Installer • Expected release: January 2012

33. Steve’s blog: http://notes2sharepoint.org Product: http://quest.com/notes-migrator-for-sharepoint/