Google Apps Technical Transition GuideFor Business, Education, and GovernmentGoogle, Inc.1600 Amphitheatre ParkwayMountain View, CA 94043www.google.co
10 Google Apps Technical Transition Guide Each phase is usually four weeks long, although this varies somewhat with the size of your company and the
Transition Overview 11Moving forward after this phase is complete, you should continue to improve the Google Apps experience for your users by teachin
12 Google Apps Technical Transition Guide 13 Set up standalone Google Message Security (optional) (p. 37)Mail Routing14Determine your final mail rou
Transition Overview 13Task Topic1 Begin provisioning users (p. 28) User Account Migration2Set up split delivery (p. 37) Mail Routing3Begin migrating u
14 Google Apps Technical Transition Guide Task Topic1 Finish provisioning users (p. 29) User Account Migration2Finish migrating user mail data (p. 3
Transition Overview 15Transitioning a company of fewer than 250 employeesIf your company has fewer than 250 employees, you may be able to complete you
16 Google Apps Technical Transition Guide Week 1Week 2Task Topic1 Verify your primary domain with Google Apps (p. 25) Domain Management2Add your IT
Transition Overview 17Week 3Week 46 Decide on a go-live date and inform your employees (p. 23)Change Management7Plan your go-live help desk operations
18 Google Apps Technical Transition Guide Note: The remaining chapters of this guide describe the tasks associated with each aspect of your technica
Transition Overview 19
2 Google Apps Technical Transition Guide Part number: GATTG_1.1March 22, 2012© Copyright 2012 Google, Inc. All rights reserved.Google, the Google log
20 Google Apps Technical Transition Guide
21Chapter 2Change ManagementChapter 2Change management is all about ensuring that your Google Apps transition is a smooth process for your users. This
22 Google Apps Technical Transition Guide • Send an announcement email to your company with the transition announcement template.• Customize posters
Change Management 23• Read Supported browsers for information on your browser options.Select your early adoptersLevel of Effort: LowFive to ten percen
24 Google Apps Technical Transition Guide Plan your go-live help desk operationsLevel of Effort: ModerateYou may see an increase in help desk reques
25Chapter 3Domain ManagementChapter 3Core ITVerify your primary domain with Google AppsLevel of Effort: LowYou can’t activate any Google Apps services
26 Google Apps Technical Transition Guide The mail routing configurations you’ll set up during your transition require a subdomain to route email fr
27Chapter 4User Account MigrationChapter 4Core ITAdd your IT team to Google Apps manuallyLevel of Effort: LowYour administrator manually creates Googl
28 Google Apps Technical Transition Guide Early AdoptersBegin provisioning usersYou begin provisioning user accounts for your entire company during
User Account Migration 29Migrate shared contactsLevel of Effort: LowYou should migrate shared contact information for any users and distribution lists
Contents 3ContentsIntroduction... 7Who is thi
30 Google Apps Technical Transition Guide • If your system will continue to use an LDAP server after your transition is complete, you should use Goo
31Chapter 5Mail Data MigrationChapter 5Core ITYou don’t migrate any mail data from your legacy system to Google Apps during this phase. Your company (
32 Google Apps Technical Transition Guide If neither of the recommended tools is suitable for your transition, use one of the following alternatives
Mail Data Migration 33You should migrate shared contact information for any users and distribution lists that you aren’t fully activating in Google Ap
34 Google Apps Technical Transition Guide
35Chapter 6Mail RoutingChapter 6Core ITSet up dual deliveryLevel of Effort: LowYour IT team should use Gmail instead of their legacy mail client as mu
36 Google Apps Technical Transition Guide • Read Configure dual delivery to learn more about setting up dual delivery in your environment.Determine
Mail Routing 37• Read Mail delivery options to determine which mail routing design is appropriate for your company.Set up standalone Google Message Se
38 Google Apps Technical Transition Guide Now that your IT team has been living on Gmail and has had an opportunity to identify and resolve any issu
Mail Routing 39• If your Google Apps solution does not include Google Message Security, read Mail delivery options - split delivery to learn how to se
4 Google Apps Enterprise Pilot Guide Chapter 3: Domain Management... 25Core IT...
40 Google Apps Technical Transition Guide • See the Message Security Administration Guide for more information on updating your mail config.Finalizi
41Chapter 7Calendar MigrationChapter 7Core ITDecide whether to migrate user calendar dataLevel of Effort: LowYou should decide during this phase wheth
42 Google Apps Technical Transition Guide You may choose to provision certain calendar resources (meeting rooms, projectors, and so on) in Google Ap
Calendar Migration 43• If you’re migrating from Lotus Notes, download and install Google Calendar Connector for Lotus Notes.Note: These calendar conne
44 Google Apps Technical Transition Guide
45Chapter 8Mobile ConfigurationChapter 8Core ITWhen connecting to Google Apps, many organizations use Android devices, which sync natively to Google A
46 Google Apps Technical Transition Guide AndroidSet up your Gmail and Calendar apps to sync with your Android device. You can download these apps f
Mobile Configuration 47Transitioning off of BlackBerry (recommended)Level of Effort: ModerateIf BlackBerry support is not critical in your organizatio
48 Google Apps Technical Transition Guide • For more information, read Setting up Google Sync with your iOS device. If your users only want access t
Mobile Configuration 49To simplify the process of setting up the rest of your users’ devices to sync with Google Apps, your IT team should schedule an
Contents 5Early Adopters ... 46Configure Android d
50 Google Apps Technical Transition Guide
51Chapter 9User PoliciesChapter 9Core ITDetermine a web browser policyLevel of Effort: LowBecause Google Apps services are accessed primarily from a b
52 Google Apps Technical Transition Guide • See the YouTube for Schools homepage (www.youtube.com/schools) for an overview of the YouTube for School
53Chapter 10Authentication and AuthorizationChapter 10Core ITDecide whether to add auth servicesLevel of Effort: ModerateGoogle Apps supports authenti
54 Google Apps Technical Transition Guide If you enable 2-step verification in your domain, you and your users benefit from extra login security. Ev
55Chapter 11Post-Transition TopicsChapter 11After your Google Apps transition is complete, take a look at the following resources to learn more about
56 Google Apps Technical Transition Guide Learn more about mobile configurationYou may want to fine-tune your mobile configuration following your tr
6 Google Apps Enterprise Pilot Guide
7IntroductionWho is this guide for?This guide is for you if any of the following applies:• You’ll be helping your company transition to Google Apps fr
8 Google Apps Technical Transition Guide Should I work with a Google Apps partner?In short, yes. Google Apps partners are experts in all aspects of
9Chapter 1Transition OverviewChapter 1Each task associated with your Google Apps transition corresponds to one of three categories: technical configur
Comments to this Manuals