Great thanks On Wednesday, 7 August 2013, Michael B. Smith wrote:
> Configure the autodiscover endpoint to not use ex1.internal.local?**** > > ** ** > > I haven’t used .local in a cert since 2007 or 2008.**** > > ** ** > > *From:* [email protected] <javascript:_e({}, 'cvml', > '[email protected]');> > [mailto:[email protected]<javascript:_e({}, 'cvml', > '[email protected]');>] > *On Behalf Of *Graeme Carstairs > *Sent:* Wednesday, August 7, 2013 12:12 PM > *To:* [email protected] <javascript:_e({}, 'cvml', > '[email protected]');> > *Subject:* [Exchange] New SSL Certificates with non public names**** > > ** ** > > HI,**** > > ** ** > > TRaditionally when you setup an SSL certificate for an Exchange server you > used a mutliname cert.**** > > ** ** > > example**** > > ** ** > > mail.domain.com**** > > Autodiscover.domain.com**** > > EX1.internal.local**** > > ** ** > > etc**** > > ** ** > > now you are no longer allowe dto have the .local addresses in the SSL > certificate,and as such the first site we have set this up on, their > outlook now reports the name on the certificate is invalid or does not > match the site name ex1.internal.local.**** > > ** ** > > Whats the preferred or recommended way round this?**** > > ** ** > > Thanks**** > > ** ** > > ** ** > > ** ** > > -- > Good news everyone, you have just received an e-mail from me! **** > -- Good news everyone, you have just received an e-mail from me!
