Link to home
Start Free TrialLog in
Avatar of pflook
pflook

asked on

Autodiscover does not seem to work for wildcard certificates

I was using a certificate autodiscover.companyname.com for the autodiscover function for external users. this worked fine, I then bought a wildcard certificate for my servers to use as my autodiscover cert had expired.

I use my exchange to host a number of customers email and used the method outlined in http://technet.microsoft.com/en-us/library/bb332063.aspx usine senario 3. I first set this up with the auto discover cert.

Since using the wildcard the auto discover only seems to work for users who have thier primary smtp the same as the wildcard, users with the primary smtp that is different different with a CName on their DNS no longer work.

Whilst I can live with this - I have just tried to setup users on a windows XP machine with SP3 installed now when I setup the users the certificate warning appears and continues to do so evey time they log onto outlook.

Is there somethng I can do to stop this and make the wildcard work or is it easier to just buy the autodicover cert?
ASKER CERTIFIED SOLUTION
Avatar of Chris Dent
Chris Dent
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pflook
pflook

ASKER

I will accept this as the answer. My users can still use exchange remotely but configuring autodiscover to work with CNames using wildcard certifactes does not seem to work I will be reverting to a dedicated cert for autodiscover. still cheaper to use http://www.ipsca.com/ for wildcard and a couple of designated certs if trying to host a couple of domain on exchange and apps.