Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outlook anywere settings

Status
Not open for further replies.

people3

Technical User
Feb 23, 2004
276
GB
HI,

We have just installed exchange 2007.

We have enabled outlook anywere which works but only if i remove the tick from

"only connect to proxy servers that have this principal name"

I belive this is due to an issue with my cert.

I have a certificate (purchased not a self cert) installed thats has the common name owa.domain.com it also has server.domain.local

Autodiscover is set up and works if i run the test email auto configuration in outlook it report no errors

Any pointers in the right direction would be great.

We do not use ISA server.


 
HI,

The problem apears to be my "issued to" name on my cert.

my cert says its issued to domain.com

Yet i access outlook anywere through
I came accross this command

From the Exchange Command Shell:

Set-OutlookProvider EXPR -Server $null -CertPrincipalName msstd:internal.company.local

howerver all the examples i see have a internet.domain.loacl or owa.domain .local

Will it cause me any issues if i set the CertPrincipalName to just domain.com

I also came accross this command

Set-OutlookProvider EXPR -Server $null -CertPrincipalName none

This removes autodiscover from ticking the proxy box on outlook anywere however it is not recomended, does anyone know why this is.

Many Thanks



Many Thanks
 
Your certification should have a common name, such as mail.domain.com (or whatever you use for OWA), and a subject alternative name for autodiscover, such as autodiscover.domain.com. I talked about this in great detail in the CAS chapter of Exchange Server 200: The Complete Reference.

This allows for the best operation, including a secured OWA, secured access for mobile devices, and proper functioning of autodiscover.

No other names need to be added other than those two.

Using a single name cert, multiple certs, wildcard certs, etc just leads to frustration and a lot more work.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Hi Pat,

My cert has a common name of OWA.domain.com

and sans for

autodiscover.domain.com
server.domain.local
mail.domain.com

The issue appears to be the "issued to" name when i view my cert.

Is there a way to check the comman name on the cert?

Many Thanks
 
Hi Pat,

Sorry my fault - my common name is

Domain.com

With SAN's of

owa.domain.com
autodiscover.domain.com
server.domain.local
mail.domain.com

What is the best way of resolving the outlook anywere issue

do you think

Set-OutlookProvider EXPR -Server $null -CertPrincipalName msstd:company.local

will work.

I connect to outlook anywere and web mail through owa.domain.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top