X hits on this document

223 views

0 shares

0 downloads

0 comments

26 / 75

user1@domain.com user2@domain.com

then name your individual folders:

user1@domain.com user2@domain.com

Allow Read and Write permissions on each individual PST file so that the utility can write migration-related metadata to those files.

Note: If you are using an exported or archived PST file, it is not possible to identify the primary root folder for Calendar and Contacts. Therefore, all calendars are migrated as “additional calendars” into Google Apps Calendar, instead of any default calendar. You can avoid this by using PST migration for mails only, and use Exchange server migration for migrating calendars.

Set up access to your Microsoft server

®

Exchange or IMAP

Microsoft® Exchange Server

Google Apps Migration for Microsoft® Exchange supports the following version of Microsoft Exchange Server: 2000, 2003, 2007 (Service Pack 3 recommended), and 2010.

®

Google Apps Migration for Microsoft® Exchange requires one administrator account on your Microsoft® Exchange Server with the following:

  • A mailbox for the administrator account

Sufficient permission to read each user’s mailbox (the Microsoft Receive As is sufficient for this task)

®

Exchange permission

IMAP server

Google Apps Migration for Microsoft® Exchange supports the following IMAP servers:

Microsoft Exchange, Novell

(TM)

G r o u p w i s e ® , G m a i l , C y r u s , C o u r i e r , D o v e c o t , S u n M a i l , a n d

Zimbra.

There are no special permissions required to migrate from an IMAP server. Connections to the IMAP server are made based on the user name/password information you provide in the list of users you are migrating (see “Create user lists” on page 23).

26

Google Apps Migration for Microsoft

®

Exchange Administration Guide

Document info
Document views223
Page views223
Page last viewedFri Dec 09 10:13:28 UTC 2016
Pages75
Paragraphs1452
Words14930

Comments