Migrar de Novell GroupWise a Microsoft Exchange Server

Presentación del tema: "Migrar de Novell GroupWise a Microsoft Exchange Server"— Transcripción de la presentación:

1 Migrar de Novell GroupWise a Microsoft Exchange Server
This section covers migration of Novell GroupWise to Exchange Server -- specifically the high level process and the resources/tools available.

2 Lo que vamos a cubrir Descripción general del proceso de migración
Preparación Coexistencia Migración Herramientas Recursos Experiencia del cliente: Capgemini Benelux

3 Herramientas de Exchange Server 2003:
Novell GroupWise Connector Conector de calendario Asistente para la migración Se incluye en Exchange Server 2003 También están disponibles herramientas de terceros Exchange Server 2003 ships with connectors and migration tools for GroupWise, Lotus Notes and POP/IMAP based . Some organizations may not need the connectors if they will migrate quickly, which typically are smaller organizations with fewer mailboxes to move. For other orgs, co-existence must be part of the migration strategy since it will most likely happen over a few weeks and must be scheduled accordingly. Specifically for Novell GroupWise 4.x and 5.x, we ship a connector for directory synchronization from Novell eDirectory to Windows Server Active Directory (AD). AD is used by Exchange, Live Communication server, along with other Msft products and the directory -- AD is LDAP compliant and can interoperate with other LDAP compliant directories and services. The GW connector also enables messaging between GW and Exchange. We also have a calendar connector for free/busy and calendar sharing between GW and Exchange. Finally, we have a migration wizard that moves Novell GW users to Windows Active Directory and Exchange, this includes mailboxes and directory info for each mailbox. Beyond this, there are 3rd party tools, which we'll cover at the end. For Novell NetWare migration, such as File/Print apps, Windows for NetWare is available.

4 Proceso general Probar, evaluar, aprender y preparar
Proporcionar un buen fundamento para la migración Proporcionar una coexitencia entre el sistema heredado GroupWise y Exchange Coexistencia de los directorios Coexistencia de los mensajes Coexistencia del calendario Ejecutar una migración fácil From a high level, the overall process is 3 basic steps: 1. Build a solid GW and Windows/Exchange foundation prior to the migration. Make sure you're existing GW environment is fully functional and that you fully understand your GW environment, including servers, clients, topology and unique applications in it. Likewise the "target" or new home, being Windows Server, AD, Exchange and Outlook must be working stand alone without any problems -- sending/receiving etc. Pilot users, many times members of the IT dept, will have mailboxes in Exchange first to validate a fully functional environment, and to learn more about it -- get comfortable with Exchange, Outlook and Windows first. 2. For most med and large org's who will not be able to migrate overnight or over a weekend, then you'll need co-exist as you phase the migration of users and mailboxes to Exchange Server, so we much co-exist directories (Novell directory and Windows AD), messaging and calendaring (GW and Exchange). 3. Finally you execute the migration in a phased approach.

5 Construir sobre un cimiento sólido
Conocer el sistema GroupWise Estructura del dominio, Post offices que se deben migrar, requisitos del usuario Instalar un sistema Exchange sólido Servidor/sitio de destino listo y funcionando Correo de Internet y otros conectores instalados Soportar infraestructura Se cuenta con la estrategia del cliente Step 1 Build a solid foundation before migration: Make sure you're existing GW environment is fully functional and that you fully understand your GW environment (and have it documented), including servers, clients, topology and unique applications in it. Likewise the "target" or new home, being Windows Server, AD, Exchange and Outlook must be working stand alone without any problems -- sending/receiving etc. Pilot users, many times members of the IT dept, will have mailboxes in Exchange first to validate a fully functional environment, and to learn more about it -- get comfortable with Exchange, Outlook and Windows first. Also get training for Windows Server & Exchange for your Admins who don't have these skills yet -- this can be done via formal training classes or reading Msft documentation. Also consider the end user impact, training maybe planned especially as users translate from an GW client to an Outlook client.

6 Herramientas de coexistencia
Conector para Novell GroupWise Herramienta para sincronizar directorios y migración Transporte de mensajes bidireccional Solicitudes de reuniones bidireccionales Conector de calendario Consultas bidireccionales sobre libre/ocupado en el calendario Step install the Exchange Server GroupWise connectors -- this ships with Exchange 2003 (and 2000) and is installed when Exchange 2003 is installed -- if you have Exchange installed, but not the connectors, grab the original Exchange CD and update your Exchange installation with the connectors. As we mentioned, we support co-existence, with a directory synch tool, messaging transport for 2 way message flow between GW & Exchange, plus the meeting connector for 2 way flow of meeting requests & accepts. Also get the Calendar connector up & running so that we can have both GW and Exchange orgs share free/busy schedules.

7 Conector de Exchange para Novell GroupWise 4.x, 5.x y 6.x
Disponible con Exchange 2003 Instalar desde el CD de Exchange 2003 Basado en la API Gateway 4.1 de Novell GroupWise El mensaje en el cuerpo del correo electrónico es en texto simple Los mensajes y las solicitudes de reunión reciben soporte con la generación completa de informes, incluyendo entrega, aceptación, rechazo, etc. Soporte para GroupWise 6.x What do the connectors do? In essence: they support 2 Way Synchronization between GroupWise and Active Directory and support messaging/calendaring. From GroupWise: Creates Contact Objects in AD for GroupWise mailboxes in selected container From Active Directory: Creates GroupWise “Foreign” mailboxes based on objects in AD that are mail enabled The Directory synch is bi-directional -- from either GW or from Exchange, users will be able to see each other in their respective directories. These connectors are built using the Novell API GW for GW 5.x -- therefore, a Novell GW server will be the "interface" server to the new Windows/Exchange environment, and vice versa. Body of s will be converted to simple text, HTML body is not supported currently (limitation of the NOVELL GroupWise API). But other functions are fully supported including meeting requests.

8 Instalar las herramientas de GroupWise desde el CD de Exchange Server 2003

9 Conector de Exchange para Novell GroupWise
Instale la API Gateway 4.1 de GroupWise con el Patch 2 Instale el cliente de NetWare para Windows, el cliente de GroupWise y NetWare Admin Exchange Exchange y Windows Server Búsqueda de Free/Busy Sincronización de directorio Solicitudes de mensajes / reuniones API Puerta de enlace de GW GroupWise NetWare Server EL Ruteador Here's a high level view of the architecture that shows the connection between Exchange and GW. Again, directory Synch, Messaging/Meeting flow and Free/busy search are supported both ways. As shown, here are the major components of the connector. There are 3 core pieces: Directory Synch, Messaging/Meeting requests and the Free/busy search. There are 2 API -- GroupWise API Gateway and the Exchange Router. On the Exchange side, the Exchange Router talks to GroupWise GW API and drops off objects (e.g. Mail, or user). Going the other way the GroupWise API drops off objects to the Exchange Router, which then delivers it to the right component on Exchange.

10 Compartir el directorio
Exchange Exchange y Windows Server Búsqueda de Free/Busy Sincronización de directorio Solicitudes de mensajes / reuniones API Puerta de enlace de GW GroupWise NetWare Server EL Ruteador Let's look a little bit deeper in how the 2 Way Directory Synchronization between GroupWise and Active Directory is supported. Active Directory is the directory used for Exchange 2003 and Reminder Let's discuss the Synch control available. 1.WHEN - Scheduling: We can control the timing of the synch based upon a schedule (e.g. 1AM everyday) or force replication to happen immediately. 2. WHAT - We can control Synchronization of specific items with granular filters that are adjustable: We can filter and decide which AD Containers get exported to Novell GroupWise -- maybe you don't need the entire AD, but want to be very selective on which items get synched to the GW directory. We also can filter by specific users and Resources, for example, any resource with a specific attribute doesn't get synched, or users in dept B, will not get synched. Also you can enable or disable contacts and groups to be synchronized -- possibly only want to move mailboxes and not contacts and groups, you can control this also. You can also use the Directory Synch to pre-populate user accounts for GW users. For example, you can move 100 GW users to AD with Dir Synch, which will automatically create WS03 accts, enabling users to log-on, use print and file share resources in windows, and also bring over rich user information to AD such as phone numbers, office location, fax numbers, etc.

11 Sincronización de directorio
Sincronización de directorio de dos vías entre GroupWise y Microsoft Active Directory Selección del contenedor para exportarlo desde AD Opciones de sincronización programada o inmediata Desde GroupWise Crear objetos de Contacto en Active Directory (AD) para los buzones de GroupWise en el contenedor seleccionado Desde Microsoft Active Directory Crea buzones “foráneos” de GroupWise con base en los objetos en AD que están habilitados para correo Soporte opcional para crear cuentas activas y no activas en AD para los buzones de GroupWise The Directory Synchronization Module supports 2 way directory synch. Remember, Exchange 2000 and 2003 uses the Active Directory in Windows Server - other MS products also leverage AD such as Live Communications Server GroupWise Directory and Microsoft Active Directory (Exchange 2000 and 2003 leverage the AD for it's directory) Create objects in AD for GW mailboxes Likewise for GW, GroupWise foreign mailboxes are in AD that are mail enabled. This includes user mailboxes, groups, resource mailboxes, etc from AD and creates them in the GroupWise directory.

12 Sincronización de directorios entre
GroupWise y Active Directory/Exchange2003

13 Configurar el Conector para GroupWise en Exchange System Manager

14 Sincronizar cuentas de Windows Active Directory para usuarios de GroupWise - Contactos de Windows habilitados para correo - Cuenta de usuario de Windows - Cuenta de usuario de Windows deshabilitada Disabled Windows user accounts   Create disabled Windows user accounts if your Novell GroupWise users are not in your Active Directory environment yet, but will be after migration to Exchange 2003. New Windows user accounts   Create enabled Windows accounts for Novell GroupWise users who work in your Active Directory environment before migration. Windows contacts   Create Windows contacts for Novell GroupWise users who are not in your Active Directory environment. The Exchange Migration Wizard can convert these contact objects to user accounts during the migration process.

15 Programar la sincronización de directorios

16 Programa personalizado para la sincronización de directorios
Screenshot of Directory Synch Schedule options -- shown here is to have the Directory Synch to start at Mid-night every night.

17 Correlacionar los atributos de sincronización de directorios
Los archivos de las reglas para la definición y correlación del esquema se encuentran en el directorio \ProgramFiles\Exchsrvr\Conndata\Dxagwise y tienen los siguientes propósitos GWAMAP.TBL - Especifica los atributos del esquema de GroupWise a sincronizar. MAPMEX.TBL - Determina la correlación de atributos de Exchange 2003 a Novell GroupWise. MEXAMAP.TBL - Especifica los atributos del esquema de Exchange a sincronizar. MAPGWISE.TBL - Determina la correlación de atributos de Novell GroupWise a Exchange 2003. Note    You can customize the control files in Notepad to change the attribute mapping. Remember to stop the connector services before you edit these files to ensure that the directory synchronization is not active. In addition, there are control files for the connector to check for address updates that require synchronization (EXTERNAL.TBL, GWPCTA.TBL, MEXPCTA.TBL). Do not edit these files manually.

18 Usuarios de GroupWise en Active Directory
This is GroupWise Container inside AD, and the users in the container -- we created this initially when we first installed the Exchange GW connector. This would be destination of migrated accounts from GroupWise -- these are now new contacts in AD, that are mail enabled -- they have addresses listed here, which means that they can receive from any Exchange user, they can also receive from GroupWise and internet users.

19 Usuarios de Exchange en el directorio de GroupWise
Now this is looking at it from the other way -- this is the GroupWise Admin screen, and we can see the Exchange users represented on the GW side. What we see is that there is a foreign Domain called "Exchange" -- this is how GW designates objects outside of its environment -- called a foreign domain. Under this foreign domain called Exchange, we've created postoffices - one called Redmond and one called Seattle. Users from Exchange have been synched into the GW directory, and they appear as GW users to the GW Administrator from a management view, and for all GW users, they will show up in their address book as a normal GW user.

20 Mensajes y reuniones… GroupWise Exchange EL Ruteador NetWare Server
Exchange y Windows Server Búsqueda de Free/Busy Sincronización de directorio Solicitudes de mensajes / reuniones API Puerta de enlace de GW GroupWise NetWare Server EL Ruteador OK, now that we got directory synch working. Next let's talk about how message and meeting requests flow between GW and Exchange. The connector module that supports message and meeting request accepts messages from Exchange (originated from a user), and would hand off the message to the Router. The router interfaces to the GroupWise API Gateway, which then delivers it to the right end user. And likewise the other way from GW to Exchange -- the GroupWise API GW accepts GroupWise user messages and meetings requests and hands it to the Router, which then delivers it to Exchange and to the final end users. From an end user view point, a user will be able to type in an address or look-up the address book name -- because the directories are synching, it looks like just another user on either system. Likewise the recipient would be able to reply. You can also mix/match users -- it is totally transparent to the users. Similarly it applies to meeting requests being sent from GW to Exchange or vice versa. The Experience becomes totally transparent from an end user perspective.

21 Mensaje originado en GroupWise enviado a Exchange
Here’s the GroupWise client initiating a new to an Exchange user -- the To addresses appear in the GroupWise Directory just as if they were on GroupWise -- end users won't be able to know if this is an GroupWise or Exchange end user.

22 Mensaje recibido por usuario de Outlook/Exchange
On the receiving end of the same message, the Outlook/Exchange users would simply read, reply, reply-all, forward and they wouldn't know that the originator was a GroupWise user. There is no indication that came from a GW user -- you can see that the attachment also comes across as you would expect. Also replying/replying -- again, there is no indication that he originator is an GroupWise user.

23 Solicitud de Reunión originada en Outlook/Exchange
Next, we have a meeting request -- this time we start from the Exchange side. We create the meeting and starting typing the To: line attends we'd like to invite, in this case some of the users are on GroupWise and some are on Exchange, but from the end-user's perspective he/she doesn't know -- it looks like everyone is on the same system -- that's the most important point.

24 Solicitud de reunión recibida por el cliente de GroupWise
Here what it looks like from GroupWise receiving end of the meeting request -- this person looks at his/her GroupWise calendar and sees a new meeting request, again, no indication if this was GroupWise or Exchange originated meeting request. They can accept, decline, propose new time just as they can normally would.

25 Reuniones (pantalla 3) Here's the details of that meeting request in GroupWise Client -- note that the meeting attributes are preserved. If there is an accept or decline, this info is passed back to the Exchange user. All of this works the other way also (GroupWise originated meeting requests to Exchange).

26 Conector de Exchange para Novell GroupWise
Exchange y Windows Server Búsqueda de Free/Busy Sincronización de directorio Solicitudes de mensajes / reuniones API Puerta de enlace de GW GroupWise NetWare Server EL Ruteador OK, we have directory and message flow. Next comes the 3rd component of the connector -- this is the Free/Busy search module which enables sharing of free/busy information for meeting requests -- again, doesn't matter which end you start from, Exchange or GroupWise, you can schedule and see free/busy schedule both GW and Exchange users -- totally transparent for end users. This works natively in both the Outlook Client and the GroupWise Client -- not desktop touch is required.

27 Conector de calendario Detalles…
API NetWare Server GroupWise Exchange Server Cliente Outlook EL Ruteador Proveedor de GroupWise Motor del conector de calendario Almacén de Exchange Carpeta Free/Busy MAPI Proveedor de MAPI

28 Configurar el Conector de calendario
In the Number of days of free/busy information to request from foreign calendars box, enter the number of days that users are able to see free/busy information for users on the foreign messaging server. Free/busy information beyond the number of days specified is not retrieved by Calendar Connector and appears as free, even if meetings are scheduled during this time. Remember that the maximum value for GroupWise is 389 days. In the Maximum age in minutes of foreign free/busy data in Exchange that can be used without querying the foreign calendar box, enter the age limit for free/busy information in minutes. If the free/busy information is beyond the specified number of minutes and a user requests the information, Calendar Connector queries the non-Exchange messaging system for updated data. If the free/busy information is within the specified number of minutes, Calendar Connector uses the current free/busy information. In the Maximum number of seconds to wait for response from foreign calendars box, enter the number of seconds that you want Calendar Connector to wait for a response after it requests an individual user's free/busy information. Set this to a low number, because each recipient on a meeting request is handled in turn, and a long response interval can cause the mail client to stop responding as it proceeds down the list of recipients. FiguraB.23Configurar la conexión al calendario a Novell GroupWise

29 Conector de calendario (Instalación 1)

30 Conector de calendario (Instalación 2)

31 Calendarización Free/Busy… Free/Busy

32 Configurar el Servicio del conector de calendario
In the Number of days of free/busy information to request from foreign calendars box, enter the number of days that users are able to see free/busy information for users on the foreign messaging server. Free/busy information beyond the number of days specified is not retrieved by Calendar Connector and appears as free, even if meetings are scheduled during this time. Remember that the maximum value for GroupWise is 389 days. In the Maximum age in minutes of foreign free/busy data in Exchange that can be used without querying the foreign calendar box, enter the age limit for free/busy information in minutes. If the free/busy information is beyond the specified number of minutes and a user requests the information, Calendar Connector queries the non-Exchange messaging system for updated data. If the free/busy information is within the specified number of minutes, Calendar Connector uses the current free/busy information. In the Maximum number of seconds to wait for response from foreign calendars box, enter the number of seconds that you want Calendar Connector to wait for a response after it requests an individual user's free/busy information. Set this to a low number, because each recipient on a meeting request is handled in turn, and a long response interval can cause the mail client to stop responding as it proceeds down the list of recipients.

33 Tiempo de seguir adelante… Usar el Asistente para migración
Herramienta administrativa para una migración en bloque Soporta GroupWise 4.x, 5.x 6.x Migraciones en uno o dos pasos Se conservan los mensajes, calendarios y carpetas La extracción se realiza usando el cliente GroupWise Y GroupWise Proxy OK, we have directory, messaging, meetings and free/busy working in our co-existence model -- now thee day has come to migrate users -- you've even done some end user training with Outlook, and have Outlook up and running on the first batch of user's desktops -- today is their lucky day to migrate to Exchange. The GroupWise migration tools ships with the Exchange 2003 CD, and can be installed at any time. It does have some bulk migration tools, and supports GW 4.x and 5.x users. The migration process can be done in 1 or 2 steps and almost everything gets moved, specifically Messages, Meetings/calendar items and folders come across. One important thing, we use a Novell GroupWise Proxy, something that enables a "user" to do the extraction -- as administrator, the GroupWise Proxy is what authorizes you to access and migrated other people's mailboxes. Important point - prior to migration, all GroupWise end users need to grant access to the administrator to do this.

34 El cliente GW otorga al Adminsitrador derechos proxy

35 Arquitectura para la migración del servidor
Extractor de fuente GroupWise 4.x Formato neutro GroupWise 5.x Extractor de fuente Función para importar This is how the migration works. The migration wizard supports GW 4.x/5.x and other system such as Lotus Notes and IMAP/LDAP based system. You have the option to do in 1 step: extract everything from GW and import into Exchange -- this would require 2 servers (1 source server GroupWise and 1 target server Exchange). To do it in 2 steps: extract from GroupWise and put into a neutral format on a temporary server, shut down the source GroupWise Server and upgrade it to a Windows/Exchange Server and then import the GW data to the new platform from the temporary server. Steps to migrate: 1. Input GW information - this is GW Domain name, user name and passwords, It will then connect into GW and show all users in GW 2. Next select the users that you want to migrate and select the messaging options: messages, phone messages, Calendar Appts, Notes. 3. Filter based upon migration options. Example: you can filter based upon a date range for messages and calendar items -- for example, maybe you don't want to migrate anything before July 1st. 4. Select Active directory account options: Every GroupWise mailbox will be associated with an ‘Active’ account in the Windows AD -- the Migration Wizard will check for you. For example, if a GW mailbox exists for Joe Smith, it will search AD for Joe Smith and will mail enable that AD acct. If it can't find a user, it will create a NEW account in Active Directory for you. Existing Contacts will be Removed From AD and Attributes Merged. The migration wizard will execute and bring the mailboxes over. Extractor de fuente Lotus Notes, IMAP/LDAP

36 Proceso del asistente para migración
Proceso básico de migración Información para conectarse a GroupWise Seleccionar los buzones a migrar Seleccionar las opciones de migración de los buzones Seleccionar las opciones de cuenta del directorio Migrar Elegir el proceso en uno o dos pasos What would it look like if we walked through the Migration Wizard? First basic info username/password, GW server information Which mailboxes to move? You must choose all or selected ones. What type of mailbox migration options? Finally, directory acct info is selected along with choosing the 1-step or 2-step process One-step migrations vs. two-step migrations The Migration Wizard gives you the option to perform your migration in either one or two steps. If you choose to migrate in one step, data is extracted and imported to the Exchange Server organization during one session of the Migration Wizard. If you choose to migrate in two steps, you will use two sessions of the Migration Wizard. Lightweight Directory Access Protocol (LDAP) and Internet Message Access Protocol 4 (IMAP4) migration functions work in conjunction with each other. The first step is to extract a user list from the LDAP directory. Then run the wizard a second time and use the list you extracted in the first step to extract the IMAP4 mail data. The Migration Wizard contains a list that shows you what type of mail systems the wizard can migrate from. Most of the procedures that are true for migrating from one type of mail system are true for another. However, there is an important exception when you are performing a two-step migration from Microsoft Mail for PC Networks. In most two-step migrations, you use the Import from Migration Files function for the second step. However, in a two-step migration from MS Mail, you must use the MS Mail for PC Networks function for both the first and second step. In the first step, MS Mail migration extracts only the directory to an Intermediate File Format (IFF) file and none of the mail data. When you import, the MS Mail data is written directly to Exchange by means of a direct MAPI interface. For all other mail systems that the Migration Wizard extracts from, the wizard first writes the user and mail data to IFF files, and then imports it to Exchange from the IFF files. Intermediate File Format The Migration Wizard uses Intermediate File Format (IFF) files in all kinds of migrations that it performs. The data is written to these IFF files as it is extracted from the source mail system. If you are extracting a large post office that contains gigabytes of data, your IFF files will also be gigabytes in size. Except for MS Mail, every byte of information you extract is written to an IFF (MS Mail only writes user information to IFF; mail information is written directly to the Exchange information store without ever being written to an IFF file). There are three types of IFF files, and you can tell the difference between them by their file extensions: Packing List or .pkl files, Primary or .pri files, and Secondary or .sec files. IFF files are comma-separated-value (CSV) files that you can view in a plain text editor, such as Notepad, or in a spreadsheet program such as Microsoft Excel. The .pkl file is a list or inventory of all the other IFF files. The wizard uses this list as a database about all the IFF files that are involved in the migration. When you perform the second step of a two-step migration, the Migration Wizard requires the .pkl file to start. There is one .pri file for each user and one .pri file for the directory information of all users. If you are migrating five users, six .pri files are created. The Directory.pri file is a list of the users and their properties (such as display name, alias, and addressing). The other .pri files contain the user's mail messages and are named in numbered sequence such as pri, pri, and so on. The .sec files are used to hold large amounts of data, such as the body of a message or message attachments. The .pri files contain pointers to data in the .sec file. In other words, a user's .pri file contains message properties such as To, From, Cc, Subject, Date, and Time. It also has a pointer that says to look in this .sec file beginning at this byte to obtain the body for this message. Any data amount in a message that exceeds 256 bytes is put in the .sec file, and a pointer to this data takes its place in the .pri file (some parts of messages, such as the body, are always put in the .sec file, even if they are shorter then 256 bytes).

37 Migration Wizard screen -- GroupWise information

38 Select Mailboxes to move

39 Opciones del Asistente para migración
La migración puede incluir los siguientes tipos de mensajes: Mensajes Mensajes telefónicos Citas en el calendario Notas Filtrar la migración con base en Rangos de fechas tanto para mensajes como para eventos del calendario

40

41 Asistente para la migración
Todo buzón requiere una cuenta activa de AD asociada Opción 1: encontrar una cuenta existente en AD que esté habilitada para correo Opción 2: crear de una cuenta nueva en AD Los contactos existentes se quitarán de AD y se fusionarán los atributos Migration may search through AD to find if an existing acct is there, if there is, then the Migration Wizard will mail enable the account. Option 2 a new acct will be required. Any new contact objects will be automatically removed.

42 Migration Wizard showing the directory options -- two choices: new Windows account or an existing acct is found, and simply becomes main enabled.

43

44

45

46 Pasos posteriores a la migración
Verificar los archivos de registro Importar los archivos del calendario El Asistente para la migración genera un correo electrónico con un archivo adjunto *.sc2 para cada usuario migrado El usuario guarda el archivo *.sc2 como archivo y lo importa a Outlook Verificar todas las funciones ¿Es el último usuario migrado? ¿Cuánto tiempo hay que mantener el Conector? ¿Cuánto tiempo hay que mantener los servidores GroupWise?

47

48 Soluciones de los socios de negocios
Quizás quiera revisar las herramientas de los socios de negocios para elementos que no se migran con las herramientas de ES03 GroupWise: Libretas de direcciones personales Archivo Derechos o firmas de proxy Importación directa del calendario desde GW a Exchange Revisar las herramientas de migración de los socios Wingra Compusven There are some items that the existing Exchange GW Connector/Migration Wizard doesn't support such as Personal Address Books, Archives and Proxy rights/signatures -- partners solutions are available to help here such as Wingra and Compusven. There are also Partners that offers services to do the migration for you -- we'll show the url to the Exchange partner page last.

49

50

51 Resumen Probar, evaluar, aprender y preparar
Contar con un plan de contingencia Contar con una estructura estable para empezar Usar las herramientas de coexistencia Conector para GroupWise para directorio, mensajes y calendarios Conector de calendario para libre/ocupado Facilitar la migración El Asistente para migración de Exchange Server 2003 para GroupWise GroupWise 5.x Summary of steps.

52 Un ejemplo real Capgemini Benelux
Más de 8000 buzones de GroupWise 6 (+300 GB) Más de 5000 archivos locales 11 Oficinas de correo en 6 servidores, 2 servidores POP3 y 2 servidores Webmail Política de la compañía para estandarizar a la tecnología Microsoft Capgemini Benelux 8000+ GroupWise 6 Mailboxes 12 Postoffices on 6 servers Company policy to standardize on Microsoft technology

53 Cómo hicimos la migración
Fase de prueba (4 meses) Se creó un gran ambiente de prueba que era similar al de producción Fase de coexistencia del piloto (3 meses) Migración en línea de los buzones (un fin de semana largo) Uso de herramientas de terceros Archivos de clientes (kit de herramientas de automigración para empleados, se utilizó en los siguientes dos meses) Herramientas de terceros y muchísimas secuencias de comando hechas a la medida

54 Nuestra experiencia Integrar un entorno nuevo fue bastante fácil
Los escenarios de coexistencia están bien documentados El proceso de migración puede complicarse Problemas con el firewall El entorno de GroupWise no es consistente

55 Los beneficios que observamos
Consolidamos de 12 a 3 ubicaciones de buzón El costo total por buzón bajó un 30-35% al año El Administrador de buzones es más fácil Se simplificó el proceso de recuperación de desastre / recuperación del buzón Exchange 2003 y Active Directory se habilitan para otras tecnologías, tales como Smartphones, Exchange ActiveSync y LCS

56 Sugerencias Las Notas de producto de Microsoft son de buena calidad
Se requiere un conocimiento profundo de GroupWise Incorporar a alguien de vbs Evaluar las herramientas de migración de terceros, tales como Wingra o Compusven Probar los datos reales y los escenarios reales El flujo de correo interno y externo requiere muchísima atención Nunca suponga nada … RFC1925: Bueno, bonito y barato: Elija dos Use the Microsoft Whitepapers on building a migration and coexistence environment Deep knowledge of GroupWise is needed Get a vbs guy/girl on board Evaluate 3rd party Migration tools like Wingra or Compusven Test with real data and real scenario’s Internal & external mail flow needs a lot of attention Never assume anything … RFC1925: Good, Fast, Cheap: Pick any two

57 Resumen Prepárese para perderse en varios “problemas”
Requiere muchísima preparación y prueba Las herramientas de terceros le pueden ahorrar mucho tiempo y problemas Migrar GroupWise a Exchange es algo fácil y divertido de hacer Summary of steps.

58 Recursos Información técnica sobre migración
Documentación técnica para la migración de GroupWise a Exchange Recursos para la migración de GroupWise a Exchange Recursos para la migración de NetWare a Windows Sitio Web de Exchange Socios de Exchange

59 © 2004 Microsoft Corporation. Todos los derechos reservados
© 2004 Microsoft Corporation. Todos los derechos reservados. Este documento es sólo para fines informativos. MICROSOFT NO OFRECE GARANTÍA ALGUNA, EXPRESA O IMPLÍCITA, EN ESTE RESUMEN.