1. How Heritage Oaks Bank Migrated from Exhange to GroupWise ® Eric Welch Manager of Engineering Services ewelch@novacoast.com Geoff Gilbert Manager of Engineering Serives ggilbert@novacoast.com Novacoast, Inc.

2. © March 17, 2004 Novell Inc. 2 Agenda Introduction Novacoast, Inc. The Challenge History and Motivation To Upgrade Exchange Reasons to Upgrade...Or to Migrate Reason to Migrate Migration Steps Questions and Answers

3. Introduction Novacoast, Inc.

4. © March 17, 2004 Novell Inc. 4 Novacoast, Inc. Company Facts Founded in 1996 Based in Santa Barbara, California Named Novell “Partner of the Year” for 2002 Professional Services company with practice areas that have been built around key engineers who specialize in a given technology Offices in California, Utah, Arizona, Texas and Oregon National resource for Novell Consulting Receiving our fourth Novell Service Excellence Award

5. The Challenge: History and Motivation

6. © March 17, 2004 Novell Inc. 6 History and Motivation… In 2000, Heritage Oaks Bank installed Exchange 5.5 For Office Integration with mail client – Outlook Most users were familiar with Outlook. Growth and adminitrastrative issues drove the staff to re-consider their email implementation. These issues included....(next page)

7. © March 17, 2004 Novell Inc. 7 History and Motivation… Need for Collaboration features Password Management/Syncronization Primary NOS integration Security concerns regarding direct internet access to a security challenged application. Patch Management. Keeping Current with technology Compatibility with other bank's calloboration software

8. © March 17, 2004 Novell Inc. 8 History and Motivation… The solutions for these issues could be resolved by installing additional middleware applications. This would lead to more administration for the IT staff.

9. To Upgrade

10. © March 17, 2004 Novell Inc. 10 Upgrade considerations Security Concerns Virus Issues Integration with Primary NOS Cost of Upgrading to Exchange 2000/2003 Upgrade all Windows NT servers to Windows 2000/2003 Upgrade all Exchange 5.5 servers to Exchange 2000/2003 Design and deploy Active Directory System management training

11. ...Or to Migrate

12. © March 17, 2004 Novell Inc. 12 Advantages of Migrating Security enhancements Lack of Virus Propagation Integration with Primary NOS Cost of Migrating eDirectory already deployed Server OS compatibility User-centric licensing Cost of management Familiar with management utilities

13. The Migration Process

14. © March 17, 2004 Novell Inc. 14 Migration Procedure Prestage the Installation Installing Groupwise Installing Novell's Exchange Connector and Gateway Migrate Users and User's mail - MIGRATE.EXE Migrate Contacts using the groupwise utility – OLAB2GW Migate Calendar items using the groupwise utility - CVOlook.exe Migrate Tasks and Notes using the the Exchange Migration Archive utility

15. © March 17, 2004 Novell Inc. 15 Migration Procedure Client Environment Primary authenticating network – Netware 5.1 Eight WAN sites Single resource NT Domain Approximately 120 Users Single 5.5 Exchange servers

16. © March 17, 2004 Novell Inc. 16 Migration Procedure Installing Groupwise 6.x Setup Single Domain, Post office, GWIA All on single server in “Main” facility. Consider creating a dedicated OU=Mail to place all groupwise objects. Training the IT staff on the features of Groupwise client Allow the IT staff time to install Groupwise client on all workstations and train end users

17. © March 17, 2004 Novell Inc. 17 The Migration Process Installing Novell's Groupwise Gateway for Microsoft Exchange Consider the Requirements Gather necessary information Install the Gateway software Setting up the Gateway in Groupwise Starting the Gateway

18. © March 17, 2004 Novell Inc. 18 The Migration Process The Gateway Requirements Hardware/SoftwareMin ReqRec Req Processor486Pentium Hard Disk80 MB80 MB or more Memory32 MB64 MB or more Windows NT Server4.04.0 or newer Exchange ServerVerson 4.0Version 5.5 GroupWiseVersion 5.1Version 5.2+

19. © March 17, 2004 Novell Inc. 19 The Migration Process Gathering the necessary information The name of the Microsoft Exchange Server on which the gateway is to be installed. NTSERVER1 The Microsoft Exchange site that the above server services. o=Exch-SITE The display name for the gateway. This refers to how you would view the gateway object in the Microsoft exchange Adminstrator program. GWISE The name of the network account that provides you with Microsoft Exchange administrator privileges. Administrator

20. © March 17, 2004 Novell Inc. 20 The Migration Process Gathering the necessary information The GroupWise primary domain under which you will install the gateway. DOMAIN The gateway directory under the domain where you would like the gateway to be installed in the GroupWise system. M:\GRPWISE\DOMAIN\WPGATE\EXCHANGE The context for the GroupWise domain object which is needed for configuring the gateway through Netware Administrator. o=FIRSTO,ou=MAIL The name by which the gateway is referred to in GroupWise EXGATE

21. © March 17, 2004 Novell Inc. 21 The Migration Process Installing the Gateway software 1. Download and decompress GWEXGATE.EXE 2. Run “SETUPEX.EXE” 3. Click on “CONTINUE”

22. © March 17, 2004 Novell Inc. 22 The Migration Process Installing the Gateway software 1. Click on the “Install” button

23. © March 17, 2004 Novell Inc. 23 The Migration Process Installing the Gateway software 1. Click on the “Gateway” button

24. © March 17, 2004 Novell Inc. 24 The Migration Process Installing the Gateway software 1. Type in the name of the Microsoft Exchange Server

25. © March 17, 2004 Novell Inc. 25 The Migration Process Installing the Gateway software 1. Select the appropriate Microsoft Exchange site

26. © March 17, 2004 Novell Inc. 26 The Migration Process Installing the Gateway software Directory Display Name: Refers to how the gateway will appear in the Microsoft Exchange Administrator. Administrator Account Name: If you have logged in using the account name that is displayed in this field, do not change the name. Domain Directory Path: The path to the GroupWise domain directory, such as M:\GRPWISE\DOMAIN. You can also specify the Domain Directory in UNC format, such as, \\SERVER\VOLUME\DOMAIN. GW Home Directory Name: Used to physically create a directory under the GroupWise directory hierarchy, such as Exchange. Install Directory Box: Displays the full path to the GroupWise gateway directory. This cannot be edited.

27. © March 17, 2004 Novell Inc. 27 The Migration Process Installing the Gateway software

28. © March 17, 2004 Novell Inc. 28 The Migration Process Setting up the Gateway in Groupwise In ConsoleOne, right click on the GroupWise domain where you want to install the gateway, select “New, Gateway”

29. © March 17, 2004 Novell Inc. 29 The Migration Process Setting up the Gateway in Groupwise Fill in the fields based on the following definitions: Gateway Name: Enter the name by which you want to refer to the gateway. This name can be different from the display name you provided while configuring the Microsoft Exchange side and will not affect gateway functioning in any way. Gateway Home Directory: Use the same name as the GW Home Directory name you specified while configuring the Microsoft Exchange system. Language: Select the language. Time Zone: Select the time zone. Platform: Select NT/OS2. Database Version: Select 6 Select Exchange as the gateway type. Leave the check boxes unchecked.

30. © March 17, 2004 Novell Inc. 30 The Migration Process

31. © March 17, 2004 Novell Inc. 31 The Migration Process After clicking on “OK”, the NDS Gateway object is done

32. © March 17, 2004 Novell Inc. 32 The Migration Process Enable Directory Synchronization

33. © March 17, 2004 Novell Inc. 33 The Migration Process Starting the Gateway To start the gateway: Click on Start, Run, type in CMD In the command window, change to the drive where the groupwise domain directory exists. Change to the following subdirectory: M:\GRPWISE\DOMAIN\WPGATE\EXCHANGE Type in “EXGATE.EXE”

34. © March 17, 2004 Novell Inc. 34 The Migration Process Starting the Gateway At this point, the gateway is running and your exchange users can send email directly to the groupwise users and vice verca

35. Migrating the Users

36. © March 17, 2004 Novell Inc. 36 Migrating Users Migrating Users and Mail - Running MIGRATE.EXE Located in \wpgate\Exchange Allows Migration of Individual Users Recipient Containers Entire Sites Including Messages

37. © March 17, 2004 Novell Inc. 37 Migrating Users Pre-requisites to running the migration tool Either use the exchange service account or assign at least view only admin rights to a Windows NT account Setup a MAPI profile with privileges to log in to the recipient mailboxes.

38. © March 17, 2004 Novell Inc. 38 Migrating Users Assigning view only Admin Rights to the Windows NT Account 1. Start the MS Exchange Administrator 2. Select the MS Exchange site for which the NT Account needs the Admin rights 3. Select File > Properties to display the Properties page of the site. 4. Click the Permissions tab. 5. Select the user who needs the Admin rights 6. Click ADD. 7. Click OK. The user you have selected will appear in the Windows NT Accounts with Permission list box. 8. Select View Only Admin from the Role drop-down list. 9. Click OK.

39. © March 17, 2004 Novell Inc. 39 Migrating Users

40. © March 17, 2004 Novell Inc. 40 Migrating Users Creating a Profile for the Windows NT Account 1. From the Control Panel, double-click the Mail icon 2. Click SHOW PROFILES

41. © March 17, 2004 Novell Inc. 41 Migrating Users From the PROFILES window, click ADD to create a new profile. Enable the Microsoft Exchange Server option, click NEXT

42. © March 17, 2004 Novell Inc. 42 Migrating Users Type in an appropriate profile name, click NEXT

43. © March 17, 2004 Novell Inc. 43 Migrating Users Type in the name of Exchange server, MailBox ID, click NEXT

44. © March 17, 2004 Novell Inc. 44 Migrating Users Complete the wizard by accepting all defaults and click FINISH

45. © March 17, 2004 Novell Inc. 45 Click CLOSE To complete the profile Migrating Users

46. © March 17, 2004 Novell Inc. 46 Migrating Users Running the MIGRATION tool From a command window, type: M:\GRPWISE\DOMAIN\WPGATE\EXCHANGE\MIGRATE.EXE

47. © March 17, 2004 Novell Inc. 47 Migrating Users

48. © March 17, 2004 Novell Inc. 48 Migrating Users EXAMPLE of migrating a USER Where Container DN (distiguished name): is o=Exch-ORG/ou=Exch-SITE/cn=Recipients Where Recipient Name: is user alias> as listed in the Microsoft Exchange Administrator Where Admin Profile: is MAPI Profile created earlier UserName: Groupwise name for the recipient Post Office: Name of existing Groupwise Post Office where new account is to be created Domain: Name of existing Groupwise Domain where Post Office resides Default user Password: Optional and case sensitive

49. © March 17, 2004 Novell Inc. 49 Migrating Users EXAMPLE of migrating a Container Where Container DN (distiguished name): is o=Exch-ORG/ou=Exch-SITE/cn=Recipients Where Admin Profile: is MAPI Profile created earlier Post Office: Name of existing Groupwise Post Office where new account is to be created Domain: Name of existing Groupwise Domain where Post Office resides Default user Password: Optional and case sensitive

50. © March 17, 2004 Novell Inc. 50 Migrating Users EXAMPLE of migrating a Container Where Admin Profile: is MAPI Profile created earlier Post Office: Name of existing Groupwise Post Office where new account is to be created Domain: Name of existing Groupwise Domain where Post Office resides Default user Password: Optional and case sensitive

51. © March 17, 2004 Novell Inc. 51 Migrating Users In Console One, before Migrating site

52. © March 17, 2004 Novell Inc. 52 Migrating Users During the Migration – The GateWay

53. © March 17, 2004 Novell Inc. 53 Migrating Users After the Migration – Console One Newly created un-associated Groupwise accounts

54. © March 17, 2004 Novell Inc. 54 Migrating Users After the Migration – Exchange Administrator Newly created Custom Recipients

55. © March 17, 2004 Novell Inc. 55 Migrating Users Associating the non-associated Groupwise objects with NDS accounts 1. Graft the Users into user container 2. Convert the newly created external entities to NDS objects

56. © March 17, 2004 Novell Inc. 56 Migrating Users Grafting the users into the appropriate user container 1. From Console One, navigate to the target user container. Click on TOOLS>GroupWise Utilities>GW/NDS Association>Graft Groupwise Objects

57. © March 17, 2004 Novell Inc. 57 Migrating Users Grafting the users into the appropriate user container 2. Select Users, resources, and distribution lists. Click Next

58. © March 17, 2004 Novell Inc. 58 Migrating Users Grafting the users into the appropriate user container 3. Select the appropriate Groupwise Domain and Post Office. Click Next

59. © March 17, 2004 Novell Inc. 59 Migrating Users Grafting the users into the appropriate user container 4. Select the target organizational unit for the Resources, Distribution Lists, and Libraries. Click Next

60. © March 17, 2004 Novell Inc. 60 Migrating Users Grafting the users into the appropriate user container 5. Click on the ADD button to select a container where the search for NDS accounts should match

61. © March 17, 2004 Novell Inc. 61 Migrating Users Grafting the users into the appropriate user container 6. Enable the option to “Create these users as GroupWise external entities on the Unmatched Users list

62. © March 17, 2004 Novell Inc. 62 Migrating Users Grafting the users into the appropriate user container 7. Select the target context for the newly created external entities – soon to be NDS accounts.

63. © March 17, 2004 Novell Inc. 63 Migrating Users Grafting the users into the appropriate user container During the GRAFT

64. © March 17, 2004 Novell Inc. 64 Migrating Users Grafting the users into the appropriate user container After the GRAFT – ConsoleOne

65. © March 17, 2004 Novell Inc. 65 Migrating Users Converting grafted entities to NDS accounts 1. With all the newly created external entities created, click on TOOLS>GroupWise Utilities>GW/NDS Association>Convert External Entity

66. © March 17, 2004 Novell Inc. 66 Migrating Users Converting grafted entities to NDS accounts 2. Answer “Yes ALL” to the Convert External Entity dialogue box

67. © March 17, 2004 Novell Inc. 67 Migrating Users Newly created NDS accounts

68. Converting the Un-Migratable

69. © March 17, 2004 Novell Inc. 69 Converting the Un-Migratable We have migrated 1. Users 2. Mail messages What did NOT migrate cleanly 1. Contacts 2. Calendar items 3. Tasks and Notes

70. © March 17, 2004 Novell Inc. 70 Converting the Un-Migratable In order to migrate Contacts, Calendar items, Tasks, and NOTES, the following utilities will be used: 1. Exchange Migration Archive Utility (GWEXARCH.EXE) from http://support.novell.com – TID2953527 – Used to convert PST files to Groupwise Archive Files. 2. OLAB2GW - http://www.slewis.org/software/ - Used to convert CSV files to GroupWise Address Bookhttp://www.slewis.org/software/ 3. CVLOOK - http://www.slewis.org/software/ - Used to convert CXV files to GroupWise appointmentshttp://www.slewis.org/software/

71. © March 17, 2004 Novell Inc. 71 Converting the Un-Migratable The following environment was established on one “conversion” Workstation. 1. Map a drive letter to server volume - V:\V:\ 2. Create three subdirectories V:\ARCHIVE V:\PST V:\CSV 3. Under the V:\ARCHIVE and V:\CSV directories, create one directory for each user.V:\ARCHIVEV:\CSV

72. © March 17, 2004 Novell Inc. 72 Converting the Un-Migratable Next – On the “Conversion Workstation” 1. Install the Exchange Migration Archive Utility a. Execute GWEXARCH.EXE to decompress the Utility Installation files b. Run C:\GWEXARCH\SETUPEXAR.EXE to install the utility. 2. Verify that the default MAPI profile is set to the newly created GroupWise profile “Novell Default Profile”. Click on Start, Settings, then Control Panel, double click on the mail applet, then click on Show Profiles.

73. © March 17, 2004 Novell Inc. 73 Converting the Un-Migratable

74. © March 17, 2004 Novell Inc. 74 Converting the Un-Migratable After launching Outlook, click on TOOLS>OPTIONS From the options applet, click on Mail Services and select the option for “Prompt for a profile to be used”. From this point on, launch Groupwise first, then Outlook. Following these procedures allows you to run both programs at the same time and still access the two different mail systems (Exchange and Groupwise mail server).

75. © March 17, 2004 Novell Inc. 75 Converting the Un-Migratable Converting the Contacts 1. Launch Outlook 2. Click on View, then enable the Folder List view, highlight the Contacts folder, the click on File, Import and Export

76. © March 17, 2004 Novell Inc. 76 Converting the Un-Migratable Select Export to File, click on Next

77. © March 17, 2004 Novell Inc. 77 Converting the Un-Migratable Select Comma Separated Values (Windows), click Next

78. © March 17, 2004 Novell Inc. 78 Converting the Un-Migratable Verify that the CONTACTS folder is selected, click NEXT

79. © March 17, 2004 Novell Inc. 79 Converting the Un-Migratable Type: V:\ARCHIVES\ \CONTACTS.CSV, click NEXT

80. © March 17, 2004 Novell Inc. 80 Converting the Un-Migratable Next, make sure you have started the GroupWise client as the target user. Then execute the conversion utility OLAB2GW.EXE. Type the path of the contacts.csv file into the file File field. Click on the “Convert File” button to start the process

81. © March 17, 2004 Novell Inc. 81 Converting the Un-Migratable Switch over to the GroupWise client, click on the Address Book icon You should now see a tab representing the “From Outlook” contacts.

82. © March 17, 2004 Novell Inc. 82 Converting the Un-Migratable Migrating Calendar items using CVOLOOK.EXE Using the same procedure as outlined above to export the contacts to a contacts.csv file, export the calendar items to v:\archives\ \calendar.csv. The utility that you will use to import the calendar items into GroupWise is CVOLOOK.EXE

83. © March 17, 2004 Novell Inc. 83 Converting the Un-Migratable Type “V:\Archives\ \calendar.csv” into the File field, leave the proxy field blank, then click on the Convert File button

84. © March 17, 2004 Novell Inc. 84 Converting the Un-Migratable The next step is to bring the Tasks and Notes from Outlook to GroupWise. For this to work, GroupWise needs to have the archive directory setup for the target user. To setup the GroupWise archive directory, launch GroupWise as the target user, click on Tools, Options

85. © March 17, 2004 Novell Inc. 85 Converting the Un-Migratable Then double click on the Environment icon

86. © March 17, 2004 Novell Inc. 86 Converting the Un-Migratable Click on the File Location tab and type “V:\Archive\ into the Archive Directory field. Click on OK then CLOSE to close the options

87. © March 17, 2004 Novell Inc. 87 Converting the Un-Migratable The next step involves exporting the Tasks and Notes into PST files from Outlook. First, launch Outlook, then select Tasks (Notes) from the Folder List View. From the File menu select “Import Export”, the select “Export to File”, click on Next.

88. © March 17, 2004 Novell Inc. 88 Converting the Un-Migratable Select “Personal Folder File (pst)” Click on Next. Verify TASKS (NOTES) is selected, click on Next. Type in “V:\Archive\ \Tasks.pst” (Notes.pst) into “Save exported file as” field

89. © March 17, 2004 Novell Inc. 89 Converting the Un-Migratable The next step is to use the Exchange Archive Migration utility. This utility converts PST files to GroupWise which then can be un-archived into GroupWise.

90. © March 17, 2004 Novell Inc. 90 Converting the Un-Migratable To run the program, click on “START> PROGRAMS> Microsoft Exchange Archive Migration> Migrate”

91. © March 17, 2004 Novell Inc. 91 Converting the Un-Migratable

92. © March 17, 2004 Novell Inc. 92 Converting the Un-Migratable On the “Exchange Archive Details” screen, click on the Browse button and browse to the V:\Archive\ directory. You should see the TASKS.PST (NOTES.PST) file listed. Click on OK to select that directory. This will take you back to the “Exchange Archive Details” screen with the PST file(s) listed. For all other PST files except TASKS.PST (NOTES.PST), select the pst file under the File column, then click on the Remove button. This does not delete the files, it only removes the entry in the migration utility. Do this until only tasks.pst and notes.pst are listed. Select tasks.pst (notes.pst) so that is is highlighted, click on Ne xt.

93. © March 17, 2004 Novell Inc. 93 Converting the Un-Migratable Type the target user name in the User ID field, type in appropriate IP address into the TCP/IP address field, type in 1677 into the Port field, then type in v:\archive\ into the “Archive Path” field. Click on Next

94. © March 17, 2004 Novell Inc. 94 Converting the Un-Migratable Click on the Start button to start the process.

95. © March 17, 2004 Novell Inc. 95 Converting the Un-Migratable Next, launch Groupwise as the target user then click on File, Open Archive.

96. © March 17, 2004 Novell Inc. 96 Converting the Un-Migratable Next, open the cabinet folder, you should see a new TASKS folder.

97. © March 17, 2004 Novell Inc. 97 Converting the Un-Migratable After opening the Tasks folder on the left, you should now see all the imported Tasks items. Select all tasks that you wish to un-archive, right click on them and un-check the archive option.

98. © March 17, 2004 Novell Inc. 98 Converting the Un-Migratable Next, click on File, Open Archive to un-check the Open Archive option. This will close the archive items.

99. © March 17, 2004 Novell Inc. 99 Converting the Un-Migratable You should now be able to view your newly imported Tasks by click on the Tasks List folder on the left.

100. © March 17, 2004 Novell Inc. 100 Converting the Un-Migratable That is it. Don’t forget to follow the same steps to bring in Notes

101. Questions and Answers

103. © March 17, 2004 Novell Inc. 103 General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. Novell, Inc., makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.