We help IT Professionals succeed at work.

Certificate problem

simpson-it asked
Last Modified: 2012-05-07
I have a working Exchange 2007 system here in the States. I build a new Ex2k7 system in Europe and imported a wildcard cert. When my users log on locally, they get a certificate error. Shouldn't a wild card cert cover the server there?
Watch Question

What is the SCP URL set on the CAS box  and what is the domain name mentioned in the cert .. That should match..
YOu can check the INternalUri by running
Get-ClientAccessServer |fl


Here is my output. The 46 site is my European site. All reference to 29 is my US stie. Only my US site hosts OWA.


Your Wild card cert should cover this server as well.
Try accessing this URL https://46caht1.simpsonmfg.com/Autodiscover/Autodiscover.xml from the client and see if you are able to browse it or not. You should some kind of CODE (600).


<?xml version="1.0" encoding="utf-8" ?>
- <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="20:06:59.7648473" Id="2084522505">
  <Message>Invalid Request</Message>
  <DebugData />

When you get the CERT error what is the URL it is reffering Also at the same time click on view certificate and see which certificate is showing there.
Unlock this solution and get a sample of our free trial.
(No credit card required)


Should it match the OWA gateway for the organization then?

All your internal URl on the virualdirectory should match to https://46caht1.simpsonmfg.com/ (asper the article) as your SCP value is set to the same FQDN


Right, but my actual OWA address filters through another server. Does that matter?

That must be for etxernal I guess. we just need to change the internal url's.. or I am quite not understanding that ...


I'm not certain that I quite understand either. I have a CAS/HT server and MB Server in each location. Here in the states, I have a CAS/HT NLB Cluster. All of my external clients access OWA through https://secure.simpsonmfg.com/exchange which routes to 29cahtc (my CAS/HT cluster). I obviously needed a CAHT server in each AD Site, so I added 46caht1. 46caht1 should only be a cas proxy to my 29 site. That being said, I used a wildcard cert for *.simpsonmfg.com for the 46caht1 server ONLY for internal SSL connections to 29cahtc. Does that help to explain the problem at all? Sorry about not spilling all this out originally. :)

Thats fine you can try what was suggested earlier.

All your internal URl on the virualdirectory should match to https://46caht1.simpsonmfg.com/ (asper the article) as your SCP value is set to the same FQDN on 46aht server. You can use the article 940726 for further understanding


Ok, i applied these changes and now when I try to access https://46caht1.simpsonmfg.com/exchange, I get the login screen and then this:

Outlook Web Access is not available. If the problem continues, contact technical support for your organization and tell them the following: There is no Microsoft Exchange Client Access server that has the necessary configuration in the Active Directory site where the mailbox is stored.

Did you chnage  any url for OWA Vdir .. of yes we don't have ,, settings the URL as per the article willnot effect OWA


I changed all three VDirs as described in the article.
Let me understand the scenario first...

We have 2 sites: US and Europe.
You had an E2k7 CAS,HUB,MBX setup in US site.
You now have setup E2k7 CAS, HUB,MBX in the Europe site.

You then exported the wildcard certificate from the US CAS server to the EUROPE CAS Server.

Now when your users who have Mailbox in the Europe site are connecting with Outlook, they get a certificate error.

Now if you click on the 'View Certificate' option, what certificate shows up?
Also if you run Test Email Auto Configuration, what results does it give. Check the URL's that it returns for OAB, EWS and autodiscover.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.