MX records, mobile/remote Outlook users
I've gotten Exchange 2007 up and running and coexisting with Exchange 2003. I have some test accounts on Exchange2007 and mail seems to be routing correctly between the 2 servers. The only externally facing MX record I have defined is for our Exchange 2003 server, and it seems to be happily taking incoming email and passing it to the Exchange 2007 server. i.e. I have an account on the Exch2007 server bob@bob.com. When I send email to that address from a gmail account it gets received by the Exch2003 server, then delivered to the mailbox on the 2007 server (as there is no existing MX record for Exch2007). I have CCR mailbox servers, and 2 separate servers running the HUB and CAS roles. Yee haw. The questions: 1. Ultimately I want to go through the process of decomissioning the Exch2003 server. So I will create an MX record pointing to each of my HUB servers, correct? Is it correct to have the MX records point to the HUB servers? (Currently we do not have an Edge Transport server) 2. After I moved the test mailboxes from the Exch2003 server to 2007, outlook did correctly redirect itself to the new server. However, the entity that Outlook now looks at is the CMS, not the CAS server. I'm thinking about mobile users who use Outlook via https on their laptops. Should I setup the mobileusers' Outlook to point to the CAS servers via https? Is OutlookAnywhere a better option? What's the best way to allow mobile/remote users to connect using Outlook? Thanks very much. Input is GREATLY appreciated.
October 18th, 2008 4:19am

Hi, 1.) You can redirect your current MX record to one of your HUB transport servers (I assume that you are doing some nat'ing in your firewall) and you can add another MX record for the other HUB transport server. Configure the MX records with the same priority as this should load balance the mail flow. 2.) Outlook in mapi mode will connect directly the the mailbox server (in your case the CMS). If you configure Outlook to use HTTPS (which is outlook anywhere) it will connect to a CAS server. Outlook connections from the internet can be either outlook anywhere or VPN - depends on what you prefer. Leif
Free Windows Admin Tool Kit Click here and download it now
October 18th, 2008 2:44pm

This is great. Thank you very much! A couple more questions: My knowledge about reverse lookups is limited... 1) In my experience in the past when creating a reverse lookup record, the server namespecified inthe reverse lookup record has to match the name of the server that responds. i.e. if I create a reverse lookup record for mail.mydomain.com, I can use my DNS tool to run a reverse lookup, and the server is supposed to respond with the name mail.mydomain.com. Correct? But I don't want to expose the actual internal name of my Exchange server. So how do I define a reverse lookup record contianing a name that is different from the internal name of my server, and have the server respond with that name? 2) With regard to Exchange Server 2007, for which entity should I define the reverse lookup record? I'm assuming it should be the HUB Transport servers? Are those questions clear? Sometimes I have a hard time clearly defining what I'm asking. Thanks again very much for the input.
October 18th, 2008 10:44pm

Hi, 1.) You don't specify a name in a PTR record. You specify an IP address, so you just create a PTR record for the IP address your MX record points to. 2.) The MX record(s) as explained in 1. Leif
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2008 10:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics