Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Wed, 30 Jan 2008 09:36:05 -0800,    group: microsoft.public.exchange.connectivity        back       


Exchange 2007 Certificate issues - internal domain name causes pro   
Background:
I have an exchange 2007 server that is setup and working correctly, however 
I am looking at options for a SSL certificate to help ease connectivity 
issues.  The biggest problem is the former IT guy has given their internal 
domain name an external domain name that they do not own.  (someone else has 
it and will not sell).  They do own an external domain name but it is not 
referenced to the internal network.

I have tried using a GoDaddy UCC certificate but was never able to get it to 
install properly because the private key was not included on the returned 
certificate.  I even got with Microsoft to verify I was sending the private 
key out.  I am grateful that GoDaddy did refund the money.  

Question:
What is the best possible solution to getting the signed SSL certificate 
working in this environment? 

I would also like to get the autodiscover working for both internal and 
external computers.  

Anyone have any suggestions?
date: Wed, 30 Jan 2008 09:36:05 -0800   author:   Craig_96

Re: Exchange 2007 Certificate issues - internal domain name causes pro   
>>I have tried using a GoDaddy UCC certificate but was never able to get it 
>>to
>>install properly because the private key was not included on the returned
>>certificate.

- The server's private key is never included in certificates. It is 
generated on your server during the certificate request and stays there. The 
Public Key is what is sent to the CA and included in the certificate issued 
by it.
- Not relevant to your situation, but the only time you need a cert with a 
private key is when you're moving the certificate to another computer (or 
backing up, rebuilding the server, etc... ). This is an option when you 
export the certificate from your computer.
-- 
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------



"Craig_96"  wrote in message 
news:EC7AE614-396C-415D-AE2A-EC410AC27E0A@microsoft.com...
> Background:
> I have an exchange 2007 server that is setup and working correctly, 
> however
> I am looking at options for a SSL certificate to help ease connectivity
> issues.  The biggest problem is the former IT guy has given their internal
> domain name an external domain name that they do not own.  (someone else 
> has
> it and will not sell).  They do own an external domain name but it is not
> referenced to the internal network.
>
> I have tried using a GoDaddy UCC certificate but was never able to get it 
> to
> install properly because the private key was not included on the returned
> certificate.  I even got with Microsoft to verify I was sending the 
> private
> key out.  I am grateful that GoDaddy did refund the money.
>
> Question:
> What is the best possible solution to getting the signed SSL certificate
> working in this environment?
>
> I would also like to get the autodiscover working for both internal and
> external computers.
>
> Anyone have any suggestions?
>
>
date: Wed, 30 Jan 2008 10:43:01 -0700   author:   Bharat Suneja [MVP]

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us