Jamestechman
Fri Mar 14 09:53:44 CDT 2008
Here is an example syntax.
New-ExchangeCertificate -DomainName e2k7s04.exchangehosting.dk,
autodiscover.exchangehosting.dk, mobile.exchangehosting.dk -
FriendlyName "Exchange Hosting DK SAN Certificate" -GenerateRequest:
$True -Keysize 1024 -path c:\Exchangehosting.txt -privatekeyExportable:
$true -subjectName "c=3Ddk, o=3DHenrik Walther, CN=3DExchangehosting.dk"
Securing an Exchange 2007 Client Access Server using a 3rd party SAN
Certificate
http://www.msexchange.org/articles_tutorials/exchange-server-2007/mobility-c=
lient-access/securing-exchange-2007-client-access-server-3rd-party-san-certi=
ficate.html
James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com
On Mar 14, 10:15=A0am, "Andrea Caldarone" <andrea.caldar...@poste.it>
wrote:
> > you should consider using an official certification authority as some pd=
as
> > does not allow to import self signed root certificates (i know a few HTC=
> > devices locked by the provider). also - you should consider using a
> > certificate with subject alternative names containing the following name=
s:
>
> > NetBios of your internal Servername
> > FQDN of your internal Servername
> > FQDN of your external Servername
> > autodiscover.yourdomain.com
>
> > BG Christoph
> > --
> > If you dont want the milk to get sour...keep it in the cow
>
> Thank you for the answer. I think that self signed certificate works for m=
e
> because all PDA I have to manage are not locked by their provider. I would=
> be very happy if you can explain me the correct syntax of the cmdshell
> New-ExchangeCertificate, look if I'm right:
>
> New-ExchangeCertificate "c=3DIT, o=3DMy company,
> cn=3Dmail.my-externaldomain.com" -DomainName my-externaldomain.com,
> my-internaldomain.local, my-server-netbiosname,
> autodiscover.my-externaldomain.com
>
> thank you