RPC over HTTP Certificate, Exchange & ISA setup Question
Hi I have what I can only hope is an easy question...
I look after a site where clients have been using OWA and RPC over HTTP for almost 2 years now but the Certificate has now expired and I need to create a new one. The problem I have is that I cant remember how too&.
I have logged into https://{Server}/certsrv and created a new Web Server certificate with the friendly name of {companyname}.homeip.net. When I go to export the certificate it shows up in the MMC with Issued To {Servername} & Issued by {Servername}. Last year the certificate showed as Issued To {companyname}.homeip.net & Issued by {Servername}.
Also once this certificate is imported the into ISA 2006 server we use I cannot assign it to a web listener as the Validity is Invalid .
Has any one got time to give me a quick step by step how to setup the certificates on an Exchange 2003 server so that we can use OWA & RPC over HTTP with ISA 2006? I do know the Issued To name is normally the external URL address but I dont seem to be able to issue a Certificate to that address&
I hope someone out there has the time to help as its driving me crazy now. Thanks in advance.
I look after a site where clients have been using OWA and RPC over HTTP for almost 2 years now but the Certificate has now expired and I need to create a new one. The problem I have is that I cant remember how too&.
I have logged into https://{Server}/certsrv and created a new Web Server certificate with the friendly name of {companyname}.homeip.net. When I go to export the certificate it shows up in the MMC with Issued To {Servername} & Issued by {Servername}. Last year the certificate showed as Issued To {companyname}.homeip.net & Issued by {Servername}.
Also once this certificate is imported the into ISA 2006 server we use I cannot assign it to a web listener as the Validity is Invalid .
Has any one got time to give me a quick step by step how to setup the certificates on an Exchange 2003 server so that we can use OWA & RPC over HTTP with ISA 2006? I do know the Issued To name is normally the external URL address but I dont seem to be able to issue a Certificate to that address&
I hope someone out there has the time to help as its driving me crazy now. Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When it comes to client work, I ask them what my time is worth.
An SSL certificate costs US$30/year from GoDaddy. How many hours will be required to change all of the clients to use the new certificate?
-M
An SSL certificate costs US$30/year from GoDaddy. How many hours will be required to change all of the clients to use the new certificate?
-M
ASKER
You pointed me ion the right direction. The site wont spend out on true certificate and the company that host the doamin is a pain when it comes to dns records, hence why we used DYNDNS.
I managed to resolve this issue by going into IIS looking at the Directory Security fro the Default Web Site and then running through the "Server Certificate" wizard asking it renew the existing. All I then had to do was install the certificate into ISA.
I believe the clients will have to reinstall the certificate but thats what they get for not spending money.
The Points are alls your as you helped me to the answer I was after, and you response is really the right way to do it.