You can download your root chain from http://CAServerName/certsr
Main Topics
Browse All Topicsrecieving error "This certificate cannot be verified up to a trusted certification authority" from a website hosted on iis7.0 and server 2008.
When browsing to the site on a client browser (non-domain member), i get a certificate prompt that This certificate cannot be verified up to a trusted certification authority. When clicking ont he certificate path, sure enough, i see the site cert, but our root ca is not listed above it.
The certificate details explain that the cert is issued by our root CA.
How i obtained the cert:
-within the iis7.0 console, i clicked on my host.
-in the home payne, i selected server certs
-then i selected "create domain certificate"
-entered all the details, and slected our root CA as the authority.
-then i edited the bindings on the site so 443 was using the requested cert
The reason this is a pressing issue is that the new CRM 4.0 outlook client is throwing an error that the ssl cert can't be verified.
I would like to be able to install the root ca on a non domain PC, and be able to launch the site without a cert prompt & get the crm outlook add in to connect via ssl. If i am obtaining the certificate incorrectly, please let me know the process.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You can download your root chain from http://CAServerName/certsr
thanks, at least that gets me going in the right direction. When i browse to my rootCA page i get the following error..
Error
The certificate enrollment page you are attempting to access cannot be used with this version of Windows. To enable Web certificate enrollment for clients running Windows Vista, your administrator must update all Windows CA Web enrollment pages. To learn more about this issue and the steps needed to update Web enrollment pages to support all versions of Windows, see:
http://support.microsoft.c
It is easier if you have a box running pre-Vista (i.e. XP, 2003, etc.) to pull up that URL. These would have the expected versions of things. Certificates Services got a big overhaul in Vista/2008.
The article the error points you to is a good place to start if you really want to/ need to go through that.
After you get it you can still deploy via GPO to the Vista/2008 boxes or manually if needed.
Business Accounts
Answer for Membership
by: ParanormasticPosted on 2008-09-05 at 13:24:22ID: 22403406
The problem comes down to trusting a new root CA. Just because you created one does not mean that the rest of the world will automatically accept it.
Within your own domain, you can publish the root certificate chain via GPO or other common distribution methods.
For non-domain (public) users, you need to convince them that they need to install your root chain and that it is actually trustworthy. For this, you could publish the root chain on one of your web servers (do not expose your issuing CA to the internet if you can possibly help it - if you need to lock it down as hard as you can! Consider 2 CA's if this is needed - one dedicated to external and another for internal functions, both under the same offline root. Consider smartcards/usb tokens for external users, if possible). You can then include this URL in any documentation that you ship out, email it (in a zip file as many filters will clean .crt files), ship via CD, etc. You can create a custom error page so that if they do not have it root chain that the error page will redirect to your FAQ about installing it - along with having an FAQ on how to do it of course:)
The other method might be to just get a commercial CA certificate for your site that would already have their root cert in the client's certificate store - Verisign, Comodo, RapidSSL, GoDaddy, etc. there are plenty to choose from. This would reduce the problems outright, but does cost money vs. your own CA which just costs the stuff to install it. If you want to know more about this, visit one of these companies' sites and they have general info on their types of products.