Exchange 2007 upgrade to 2010
My question relates to Outlook Anywhere. I have a 2007 server holding CAS, HUB, and Mailbox roles. I am deploying a 2010 server to replace it, but I suspect I'll need to run in coexistence for a bit. I have a public DNS record for owa.company.com that points to exch1.company.com which NATs to exch1.company.local through an ASA. My cert Principle Name is exch1.company.com. My problem is with the Outlook Anywhere setting the client to only connect to a cert with msstd:exch1.company.com. My plan was to point owa.company.com to exch2.company.com but this client setting gets me endless login prompts. I am assuming I'll need to uncheck that box on all the clients (connects when I do), but am unsure of the best way to prevent autodiscover from re-populating it. A few solutions I read are to change Set-OutlookProvider to server $null and certprincipalname to none (not recommended) or server $null and certprinciplename to the exch2.company.com. Why is solution 1 not recommended? Security issue? If I go with solution 2, how will clients still on 2007 server connect? I also read the default is to set server and certprincipalname to $null.....is this the best solution? I am currently testing in a lab w/ self signed certs so I want to make sure I am clear before buying a public cert. Thanks in advance for any clarification you can give me.....
November 10th, 2010 12:56am

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

Other recent topics Other recent topics