Google apps not validating mx records
Ideally, you will have everyone on board after explaining the IT and cost benefits of switching.Let everyone know what’s coming Be sure to provide ample communication well ahead of the migration about service disruptions, client-side hardware changes, and the forthcoming software changes.Give this a read-through and you’ll have a solid idea of what’s in store for you as you make the transition to Google Apps.Gooru’s GAMME Guide features some light technical descriptions, but please see the linked Google support resources for more detailed technical information whenever necessary.Prepare your Microsoft Windows computer to run GAMME Go ahead and download Google Apps Migration for Microsoft Exchange and install it on your client computer/server.You’ll also need the user list you exported when provisioning your users.If you use Microsoft Active Directory or another LDAP server, you can use Google Apps Directory Sync.
Provide access to a Microsoft Exchange admin account You’ll need the login information to an admin account with its own mailbox, and at least Receive As permissions for all other accounts on the domain.
Log in to your account with your registrar, and add the following MX records and priorities: If there is a Time To Live (TTL) option, set it to 300 seconds (5 minutes) Delete the old MX records, and be sure to save your changes. However, it may take up to 48 hours for these changes to take full effect.
It is best to perform your migration over the weekend to avoid disruptions as these modifications propagate through the Internet.
This is a step-by-step guide to migrating to Google Apps from a Microsoft Exchange Server using Google Apps Migration for Microsoft Exchange (GAMME).
GAMME is a free tool provided by Google to perform a server-side migration to Google Apps.