HI there, we currently have a HUGE issues with our exchange servers. exchange 2007 was our primary mail server until we installed 2010 in our domain for testing. we've enabled Outlook Anywhere and this were working fine (still connecting to 2007). when we start moving some mailboxes over to 2010, stuff starting to fall apart. people whose mailbox reside in 2010, will give an error, complaining something about mismatched certificate name: http://blogs.technet.com/b/danielkenyon-smith/archive/2010/05/13/the-name-on-the-certificate-is-invalid-or-does-not-match-the-name-of-the-site-part-2.aspx for new user starting their outlook for the first time, it can't get the settings automatically and needs to specify the server settings manually. when arranging a meeting request, free/busy is not viewable anymore; only via web access AND for people on 2010. automatic replies can't be set up anymore, saying something about "... server is currently unavailable", but this seems to work via web access. I think all this happening when we were modifying the certificate/internal/external/autodiscover/etc ... so now, we hold the mailbox migration and trying to work out how to fix these. here's some info: for both exchange 2007 and 2010, we use a different name when accessed from external: Exchange 2007 internal url: exch07.domain.com external: mail07.domain.org Exchange 1020 internal url: exch10.newdomain.com external url: mail.newdomain.org for the above, we've applied 2 registry change as instructed here: http://ilantz.wordpress.com/2011/01/12/configure-static-fake-server-names-for-rpc-over-https/ running test email autoconfiguration (ctrl + right-click on outlook icon) fails log says everything fail, the most frequent error code: 0x80004005 except the one that says srv record look up 0x8004010F testing through https://www.testexchangeconnectivity.com/ for: - Outlook Anywhere: works, but need to specify the server settings manually - Outlook Autodiscover: all fail running outlook from outside the network with RPC over HTTPS works ok, but Out of Office Assistant still not working Unless ... 2007 can't play nice with 2010?Andrew P.

It seems you are using new urls in e2k10 instead of using existing e2k7 urls. That would cause the issue. Basically you need to have a certifcate with legacy.domain.com which will point to e2k7 and mail.domain.com which will map to e2k10. You missed this. You might take a deep look into the following blog which will help you identify & fix the issue. Transitioning Client Access to Exchange Server 2010 http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspxPlease "Mark As Answer" if this helps you. Thank you. Sathish Kumar Elango | MCSE 2003 & MCSA Messaging | http://msexchangehelp.wordpress.com

thanks for that, we're still studying the article. one thing that concerns us is that in the article, the domain name still the same. while in our case, we're using a new domain name: as I pointed out earlier (with some fixing to the typo to make it more clearer): Exchange 2007 internal url: exch07.domain.com external url: mail07.OldCompanyName.org Exchange 2010 internal url: exch10.domain.com external url: mail.NewCompanyName.org note that both of the internal url have the same domain.com ... this is internal only and not accessible to external people. for the external url, to reflect our new name, we want to use the mail.NewCompanyName.org and (possibly in the next week or two) removing any reference to mail07.OldCompanyName.org completely. this is when we got confused ... Andrew P.