changing MX records for legacy name in 2007->2010 Migration
OK, this is what I think you could do (and if someone else who has performed more of these migrations can confirm or correct, please go right ahead): Let's say you currently have the following IP/DNS...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Interesting. I hadn't considered that, obviously. My public and internal domain name are the same, though we have an old NETBIOS name that doesn't match. I saw a little bit about that being...
View Articlechanging MX records for legacy name in 2007->2010 Migration
First, I would use A records here, not CNAME, at least for the MX records. http://exchangepedia.com/blog/2006/12/should-mx-record-point-to-cname-records.html When I've practiced (granted, with one...
View Articlechanging MX records for legacy name in 2007->2010 Migration
You've got it. The records are pointing to the server(s) using 1-to-1 NAT. It looks like this. Server1 A 1.2.3.4 mail CNAME Server1 mail mx 10 Now I add: Server2 A 1.2.3.5 legacy CNAME Server1 And...
View Articlechanging MX records for legacy name in 2007->2010 Migration
What is the current setup exactly? --------------------------------------------------------------------------------- MX record: contoso.com MX preference = 10, mail exchanger = mail.contoso.com A...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Right, the problem is the HT and CAS server are the same. Therefore, you access the CAS server using the same name as the MX record/HT server name. So, if I change the DNS record for the CAS server,...
View Articlechanging MX records for legacy name in 2007->2010 Migration
I believe the legacy domain name is for the CAS role only, so, in a state of coexistence, the E2K10 CAS can redirect clients with a mailbox on an E2K7 MBX server to the E2K7 CAS. The E2K10 CAS uses the...
View Articlechanging MX records for legacy name in 2007->2010 Migration
I have an HT/CAS/mailbox server, so OWA and the MX record use the same DNS name. When I install the 2010 CAS server and move the DNS name to that server, I assume I also need to add an MX record for...
View Articlechanging MX records for legacy name in 2007->2010 Migration
FWIW - it seems my Outlook Anywhere issue was because the new Ex2010 server had a default authentication type of Basic and the original server was NTLM. Set the new server to NTLM and the problem went...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Sorry, I would mark this as the answer, but I still haven't gotten it working. I rekeyed my wildcard certificate so I could get the private key on the 2010 server and now all of my Outlook Anywhere...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Sorry, I would mark this as the answer, but I still haven't gotten it working. I rekeyed my wildcard certificate so I could get the private key on the 2010 server and now all of my Outlook Anywhere...
View Articlechanging MX records for legacy name in 2007->2010 Migration
FWIW - it seems my Outlook Anywhere issue was because the new Ex2010 server had a default authentication type of Basic and the original server was NTLM. Set the new server to NTLM and the problem went...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Sorry, I would mark this as the answer, but I still haven't gotten it working.I rekeyed my wildcard certificate so I could get the private key on the 2010 server and now all of my Outlook Anywhere...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Sorry, I would mark this as the answer, but I still haven't gotten it working.I rekeyed my wildcard certificate so I could get the private key on the 2010 server and now all of my Outlook Anywhere...
View Articlechanging MX records for legacy name in 2007->2010 Migration
OK, this is what I think you could do (and if someone else who has performed more of these migrations can confirm or correct, please go right ahead):Let's say you currently have the following IP/DNS...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Interesting. I hadn't considered that, obviously.My public and internal domain name are the same, though we have an old NETBIOS name that doesn't match. I saw a little bit about that being considered...
View Articlechanging MX records for legacy name in 2007->2010 Migration
First, I would use A records here, not CNAME, at least for the MX records.http://exchangepedia.com/blog/2006/12/should-mx-record-point-to-cname-records.htmlWhen I've practiced (granted, with one server...
View Articlechanging MX records for legacy name in 2007->2010 Migration
You've got it. The records are pointing to the server(s) using 1-to-1 NAT. It looks like this.Server1 A 1.2.3.4 mail CNAME Server1 mail mx 10Now I add:Server2 A 1.2.3.5 legacy CNAME Server1And change...
View Articlechanging MX records for legacy name in 2007->2010 Migration
What is the current setup exactly?---------------------------------------------------------------------------------MX record:contoso.com MX preference = 10, mail exchanger = mail.contoso.comA...
View Articlechanging MX records for legacy name in 2007->2010 Migration
Right, the problem is the HT and CAS server are the same. Therefore, you access the CAS server using the same name as the MX record/HT server name.So, if I change the DNS record for the CAS server,...
View Article
