Re: ssl certificate error/warning with rpc over http (outlook anywhere) 2007 exchange/outlook...
- From: "andy webb" <awebb@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 6 Oct 2007 10:23:08 -0500
You don't need a wildcard cert, but you do either need a SAN (subject alternate name) cert with multiple names on it, or you need to set up another IIS virtual server and use a normal cert with the autodiscover name.
"markm75" <markm75c@xxxxxxx> wrote in message news:1191633079.946240.305610@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I registered discover.domain.com on our public dns, so that OAB
functionality would work with rpc over http clients.. its working
fine, except that users get a certificate warning about a mismatch on
the name on the ssl..
I have no interest at this point in getting a wildcard ssl
certificate.. but basically just want it to work..
Is there a command i'm sposed to run in the shell to fix this?
The basic warning is something like discover.domain.com doesnt match
wan1.domain.com.
Anyone fixed this without getting a wildcard ssl?
Thanks much..
.
- Follow-Ups:
- References:
- Prev by Date: Re: WM6 UNC Paths and ActiveSync
- Next by Date: Messaging Records Management - Display the following comment when the folder is viewed in Outlook
- Previous by thread: ssl certificate error/warning with rpc over http (outlook anywhere) 2007 exchange/outlook...
- Next by thread: Re: ssl certificate error/warning with rpc over http (outlook anywhere) 2007 exchange/outlook...
- Index(es):
Relevant Pages
|