beautypg.com

Prepare your microsoft® windows client machines, What is/isn’t migrated, Prepare your microsoft – Google Apps Migration for Microsoft Exchange Administration Guide User Manual

Page 30: Windows client machines

background image

30

Google Apps Migration for Microsoft

®

Exchange Administration Guide

Prepare your Microsoft

®

Windows client machines

Each client machine that runs the migration utility needs to have the following minimum
configuration:

Microsoft

®

Windows: Windows XP SP3, Windows Vista Business SP1 or later, Windows

Server 2003 SP 2 or later

Note:

We have seen increased performance in terms of the number of simultaneous

threads you can run with

Microsoft

®

Windows Server 2003 and up. Current testing

indicates that 25 simultaneous threads is an optimal number with this
configuration.

In all cases, we recommend you upgrade to the latest patches for your version of
Microsoft

®

Windows.

Microsoft Outlook® 2003 or 2007 (required only if you are migrating from Microsoft

®

Exchange Server or PST files). Be sure to upgrade to the latest service packs and patches
for Outlook, especially if you see any 0x80040900 or Missing Property errors.

Memory: 512 RAM

CPU: 2 GHz +

Minimum Disk Space: 8 GB of Disk Space

Keep in mind that the migration process is multi-threaded, which can consume a lot of
resources, and that data for each user being processed are loaded into memory. Given that,
we recommend that you opt for dedicated machines with more robust CPU and memory,
increasing the resources with the number of users you plan to process simultaneously on each
machine.

In order for 2-Legged OAuth to function properly, you need to make sure the time on each
client machine is set accurately to the current time for the local time zone.

What is/isn’t migrated

During the migration, contacts and then calendar data are processed first, followed by email.

The following tables outline which aspects of mail, calendar, and contact data are and are not
migrated from Microsoft

®

Exchange to Google Apps. For example, messages with .exe

attachments are not migrated.

Any data that fails to migrate is identified in the log files by account name, entry ID, and
location. Log files are located on each client machine in the following location:

Windows Vista:

C:\Users\user-name\AppData\Local\Google\Google Apps

Migration\Tracing\ExchangeMigration

Windows XP: C

:\Documents and Settings\user-name\Local Settings\Application

Data\Google\Google Apps Migration\Tracing\ExchangeMigration

user-name

in the path identifies the administrator who logged in and ran the utility.