Main Nav

Hello all!

I apologize in advance for the length of this email, but I am hoping someone has dealt with this issue before and the details will help with explaining what I am missing.

We are entering our final stages of our Google Apps transition from Exchange and are getting ready to test some users.  We would like to make this transition in blocks (ie: test group 1 (a few IT folks), test group 2 (the rest of IT and select Staff and Faculty), then Staff, Faculty, and Students, most likely spread over a few days).

That being said, we will need to keep our Exchange Servers up and running for a few weeks while this is done, and I am having a rough time getting the mail flow to work correctly.  Here is what I have configured, so far:

  • Using GAPS and GADS, Google Apps is mirroring our AD structure.  All users  have accounts, both in AD/Exchange and Google Apps
  • We configured Receiving Routing, per OU, to forward email back to Exchange (and not keeping a copy).  We thought it would be good to change over the MX records while both services were up and running, and that it would be easier to change routes within Google to throw the switch when we are ready to move the users.
  • Changed external MX records to point to Google.  
  • Changed internal MX records to point to Google.

With all of that done, everything still works, and our users have no idea we've done any of this.  Now, time to do some testing.

I have created a test user, in a test OU, that mail is NOT forwarded to Exchange.  When email comes from the outside world, it gets delivered to Gmail, as would be expected.  Of course, in Exchange as it currently is set up, delivers internal messages to the existing mailbox.  To remedy this, I have changed the Accepted Domain from Authoritative to Internal Relay and have tried to add Send Connectors that point to Google.  I have tried Internet, Internal, and Custom connectors that point using the FQDN or the MX records, but I seem to be having no luck. 

I'm sure someone out there with more Exchange experience than I have has done this before and I am hoping they can point me in the right direction.  Thanks, in advance, for your help.

Jesse Safran
Sr. Desktop Supervisor/Assist. Network Admin
Green Mountain College
1 Brennan Circle
Poultney, VT 05764
802-287-0105 (Cell)
802-287-8264 (IT Computer Support Line)
safranj@greenmtn.edu
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

Comments

Last I worked with Exchange (Exchange 2007), an address on mailbox/user object would cause Exchange to deliver there regardless of routing settings. The routing only came in when the recipient was not a proxyAddress on any mailbox enabled object. To get around the issue we set up an additional alias domain on our Google side (in our case mail.bethel.edu in addition to bethel.edu), created a forwarding contact for each user as we migrated them, and put that object DN in the altRecipient on the mailbox-enabled user object.

So as an example, my google mailbox would be 
j-mooney@mail.bethel.edu (automatic alias - only used for routing)

And AD:
cn=jmooney,OU=... (user)
 proxyAddresses: SMTP:j-mooney@bethel.edu
                       smtp:jmooney@bethel.edu
 altRecipient: cn=fwd-jmooney,OU=...

cn=fwd-jmooney,OU=... (contact)




Jeremy (and everyone else),

Looks somewhat reasonable.  Makes me wonder if you could do it the other way around.  For example, within Exchange, move the mailboxes into an already existing internal domain (say internal.domain.edu) and make sure there are no email routes in or out for that domain (we just want the mailboxes to exist for access until we have verified everything transferred OK with GAMME).  If the users already belong to that subdomain (and in my case, they do), they should be able to access their old mailboxes, without any new email being delivered... or at least not email out or email in).  If the send connectors are configured correctly, all domain.edu email should then be forwarded to Gmail.

Am I missing something?


Yes, that should work. I think the issue would be if they send something to another Exchange user the address will be out there. Could probably reject those with routing policy though. Also if someone picks them from the GAL (assuming you don't hide them) it'd still end up in the old mailbox or bounced by routing policy. Either case would be something to at least document well for the sake of helpdesk and other support staff.


Close
Close


Annual Conference
September 29–October 2
Register Now!

Events for all Levels and Interests

Whether you're looking for a conference to attend face-to-face to connect with peers, or for an online event for team professional development, see what's upcoming.

Close

Digital Badges
Member recognition effort
Earn yours >

Career Center


Leadership and Management Programs

EDUCAUSE Institute
Project Management

 

 

Jump Start Your Career Growth

Explore EDUCAUSE professional development opportunities that match your career aspirations and desired level of time investment through our interactive online guide.

 

Close
EDUCAUSE organizes its efforts around three IT Focus Areas

 

 

Join These Programs If Your Focus Is

Close

Get on the Higher Ed IT Map

Employees of EDUCAUSE member institutions and organizations are invited to create individual profiles.
 

 

Close

2014 Strategic Priorities

  • Building the Profession
  • IT as a Game Changer
  • Foundations


Learn More >

Uncommon Thinking for the Common Good™

EDUCAUSE is the foremost community of higher education IT leaders and professionals.