Migrator for GroupWise

GroupWise migration to Exchange and Exchange Online with ZeroIMPACT

Simplify Migrator for GroupWise, reducing downtime and data loss.

Migrator for GroupWise simplifies and accelerates the transition process and mitigates the risk of data loss. It quickly and accurately migrates your users’ email, calendars, tasks, personal address books, frequent contacts, archives, recurring meetings and more.

Migrator for GroupWise helps you finish your migration faster by enabling you to migrate multiple mailboxes simultaneously, transition data directly to hosted platforms, automate administrative tasks, and collect mailbox and archive information for pre-migration planning.

Most importantly, Migrator for GroupWise preserves the integrity of each user's mailbox, ensuring accurate migration from Novell GroupWise to Exchange. In fact, it is the only solution capable of preserving GroupWise recurring and custom recurring appointments as a recurring series in Exchange.

Features

  • Pre-migration assessmentCollect mailbox and archive information for more accurate migration planning.
  • Prerequisite checker – Easily scan your environment to determine if the required software and settings, connectivity, permissions, and access rights are in place - before you begin.
  • Finish fast – Transition multiple mailboxes simultaneously with a multi-threaded migration engine to reduce project costs and timelines. You can also install multiple migration consoles to increase scalability.
  • Auto process – Automate administrative tasks, such as mailbox creation, and advanced mail routing options to reduce IT work time and ensure migration tasks occur in proper sequence.
  • Self-service desktop migrator – Enable end users or administrators to silently migrate personal data, such as local GroupWise archives, to Exchange or Outlook personal stores, without data loss.
  • Mailbox integrity – Preserve valuable email information, including dates, times, formatting and attachments. GroupWise Migrator for Exchange provides a complete address translation, enabling users to reply/reply all to migrated messages without editing addresses. You can also preserve proxy and folder rights while accurately migrating shared folders, personal address books and folder structures, maintaining a familiar messaging experience for end users.
  • Quick cloud – Migrate GroupWise mailbox content directly to the cloud, including Office 365, instead of through an intermediary data center, mitigating the risk of data loss and ensuring a quick and secure migration.

Specifications

Platforms supported:

  • GroupWise 6.0-7.0.4, 8.0.0-8.0.3, and GroupWise 2012
  • Exchange 2007, 2010, 2013, Office 365,  and hosted Exchange

Before installing MFG 4.5, ensure that your system meets the following minimum hardware and software requirements.

All machines

  • Must have network access.

On the GroupWise server

Must be Novell GroupWise version 6.0–7.0.4, or 8.0.0–8.0.3, or GroupWise 2012.

  • Note: Migration from a pre-2012 GroupWise source via a MFG migration server running Windows 7 or Win Server 2008 requires a source GroupWise version that supports a connection from a GroupWise 2012 client (which is required on a MFG migration server running on Windows 7 or Win Server 2008).
  • Important: Dell’s CMG supports GroupWise versions 7.0.2–7.0.4 and 8.0.0– 8.0.3, and GroupWise 2012, but not versions 6.0–7.0.1. If you want to use CMG for coexistence, the source GroupWise server must be version 7.0.2–7.0.4 or 8.0.0–8.0.3, or GroupWise 2012.

On the Exchange server

Supported Target Environments:

  • Proprietary Exchange 2013, with or without CAS Arrays.
  • Proprietary Exchange 2010 (GA, SP1, SP2 or SP3), with or without CAS Arrays.
  • Proprietary Exchange 2007 (GA, SP1 or SP2).
  • Microsoft Office 365.

On each migration server (running MFG admin applications)

Windows operating systems supported for migration to various Exchange target types:

 

Exchange 2013 or 2010

Exchange 2007

Office 365

Win Server 2003 x86 SP1

 

Ÿ •

 

Win Server 2003 x86 SP2

Ÿ•

•Ÿ

Ÿ•

Win Server 2003 R2 x86 SP1

Ÿ

Ÿ •

 

Win Server 2003 R2 x86 SP2

•Ÿ

Ÿ•

Ÿ•

Windows XP x86 SP2

 

Ÿ •

 

Windows XP x86 SP3

Ÿ•

•Ÿ

•Ÿ

Win Vista* Enterprise Ed x86 SP1 or SP2

Ÿ•

Ÿ•

Ÿ•

Win Server 2008 **

•Ÿ

Ÿ•

•Ÿ

Win Server 2008 R2 **

•Ÿ

 

Ÿ •

Windows 7 or 8 **

Ÿ•

•Ÿ

Ÿ•

Win Server 2012 **

•Ÿ

Ÿ•

Ÿ•

* Windows Vista Caution: Heap corruption may occur (rarely) when using MFG running on Windows Vista to migrate ACLs. If this becomes a problem in your environment, set [General] ACLs=0.
** For Win Server 2008, 2008 R2 and 2012, and Windows 7 and 8, note:

  • ACL migration is supported only from a GW 2012 source. A GroupWise 6, 7 or 8 source requires [General] ACLs=0.
  • Migration to Exchange 2007 requires a 32-bit OS.

Important: MFG requires the English-language edition OS/PowerShell on the admin workstation.
Note: To accelerate large-scale migrations, MFG can be run on multiple migration servers running in parallel.
Note: When Migrating to Exchange 2013, Outlook on the migration server must be running the latest service pack and have all applicable updates installed.

Required on Each MFG migration server:

  • Must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange, with these minimum hardware requirements:
    • 1+ GHz processor, 1GB memory, 20GB free disk space.
  • Recommended for improved performance, especially for high-volume migrations:
    • 3+ GHz processor, 2GB memory, 1 Gbps NIC.
    • 1 Gbps or faster network connections among all migration workstations and the Exchange and GroupWise servers.
  • The Novell NetWare Administrator (NWAdmin or ConsoleOne) must be installed. MFG Directory Exporter has the same prerequisites as the NetWare Administrator.
  • The Novell client for NetWare (client version 4.7 or higher, 4.91 SP2 recommended) must be installed. When migrating from GroupWise 7 running on a SUSE Linux server, the NetWare client must be logged into eDirectory. If migrating from a Netware server, the NetWare client must be logged into NetWare.
  •  A GroupWise client (version 6.0–7.0.4 or 8.0.0–8.0.3 or GroupWise 2012) must be installed, and a Novell GroupWise profile must be set as the default profile. Note: A GroupWise 2012 client is required if running Windows 7 or 8, or Win Server 2008 or 2012.
  • Outlook 2003, 2007, 2010 or 2013 (32-bit ver only) must be installed. The Admin Account Pooling Utility requires Outlook 2010 or 2007 (not Outlook 2013 or 2003). If migrating to Exchange 2013, Microsoft requires the Outlook client be one of these:
    • Outlook 2013 (15.0.4420.1017)
    • Outlook 2010 SP1 w/Nov 2012 update (14.0.6126.5000)
    • Outlook 2007 SP3 w/Nov 2012 update (12.0.6665.5000)

IMPORTANT: The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange 2007 "server" MAPI.

  • Required for all scenarios: Microsoft .NET Framework 4.0 (available here) and Windows Management Framework 2.0 (available here) must both be installed.
  • Required for migration to Exchange 2013 or 2010, or MS Office 365: Windows PowerShell 2.0 (a component of Windows Management Framework, required as noted above).
  • Required for migration to Exchange 2007: Exchange 2007 RTM, SP1 or SP2 Management Tools (32-bit version, US English only), which in turn requires: Microsoft Management Console (MMC), and Windows PowerShell. The 32-bit version of Exchange 2007 Management Tools is available (at this writing) at this Microsoft link, and see also Microsoft’s installation instructions.
  • Required for migration to Office 365 if using MFG’s Account Pooling: MFG’s Account Pool Utility uses Microsoft Office 365 cmdlets to issue commands to Office 365, and these cmdlets must be installed before MFG can use account pooling. Note these requirements before you can install the cmdlets:
    • You can install the cmdlets on a Windows 7 or Windows Server 2008 R2 computer.
    • Windows PowerShell 2.0 and the .NET Framework 3.5.1 must be enabled.
    • You must install the MSOL Sign-in Assistant. Download and install one of the following from the Microsoft Download Center: 32-bit version — or — 64-bit version

To install the cmdlets:

  • Download the MSOL Module for Windows Powershell: 32-bit version — o r — 64-bit version
  • To install the cmdlets, double-click the AdministrationConfig.msi file.

The installer adds the program to your Start menu, and adds a shortcut to your desktop.

On user desktops (if running MFG’s SSDM)

  • Windows operating systems supported for migration to various Exchange target types:

 

Exchange 2013 or 2010

Exchange 2007

Office 365

Win Server 2003 x86 SP1

 

Ÿ •

 

Win Server 2003 x86 SP2

•Ÿ

Ÿ•

•Ÿ

Win Server 2003 R2 x86 SP1

 

Ÿ •

 

Win Server 2003 R2 x86 SP2

Ÿ•

Ÿ•

Ÿ•

Windows XP x86 SP2

 

Ÿ •

 

Windows XP x86 SP3

Ÿ•

Ÿ•

Ÿ•

Win Vista* Enterprise Ed x86 SP1 or SP2

Ÿ•

Ÿ•

Ÿ•

Win Server 2008 **

Ÿ•

•Ÿ

Ÿ•

Win Server 2008 R2 **

Ÿ •

 

Ÿ •

Windows 7 or 8 **

Ÿ•

Ÿ•

Ÿ•

Win Server 2012 **

Ÿ•

Ÿ•

Ÿ•

* Windows Vista Caution: Heap corruption may occur (rarely) when using MFG running on Windows Vista to migrate ACLs. If this becomes a problem in your environment, set [General] ACLs=0.
** For Win Server 2008, 2008 R2 and 2012, and Windows 7 and 8, note:

  • ACL migration is supported only from a GW 2012 source. A GroupWise 6, 7 or 8 source requires [General] ACLs=0.
  • Migration to Exchange 2007 requires a 32-bit OS.
  • Must be running a GroupWise client version 6.0–7.0.4, or 8.0.0–8.0.3, or GW 2012.
    Note: ACL migration is supported only from a GW 2012 source. A GroupWise 6, 7 or 8 source requires [General] ACLs=0.
  • Must be running Outlook 2003, 2007, 2010 or 2013 (32-bit version only). If migrating to Exchange 2013, Microsoft requires one of these Outlook clients:
    • Outlook 2013 (15.0.4420.1017)
    • Outlook 2010 SP1 w/Nov 2012 update (14.0.6126.5000)
    • Outlook 2007 SP3 w/Nov 2012 update (12.0.6665.5000)