Comments on: Exchange 2010 & GoDaddy UCC certificate walkthrough

By: Babul A. Mukherjee

Babul A. Mukherjee — Sat, 22 Oct 2011 05:44:33 +0000

Andy – I couldn’t agree more!

By: Andy

Andy — Mon, 08 Aug 2011 18:38:23 +0000

Too bad you still can’t import an Exchange exported (UCC) certificate (issued by GoDaddy) into the Cisco SA500 series routers, which apparently is how you’re supposed to install ucc certificates on other servers/devices. For servers it works, just not the Cisco 500 series routers! I wish Cisco would get their act together and listen to their customers’ complaints!

By: Wallacetech

Wallacetech — Thu, 25 Nov 2010 20:02:52 +0000

Hello.

After i change the the generated code and add the $data info as per you notes i get the following

At line:1 char:12

+ Set-Content <<<< Generated CSR CODE HERE

+ CategoryInfo : InvalidArgument: (:) [Set-Content], ParameterBindingException

+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand

Any ideas?

Thanks in advance

By: Babul A. Mukherjee

Babul A. Mukherjee — Wed, 01 Sep 2010 07:22:19 +0000

hyl -

You are correct. You can do as you say, or set your OutlookProvider property.

To set your OutlookProvider certificate principal name correctly see instructions here: http://technet.microsoft.com/en-us/library/dd439371(EXCHG.80).aspx

By: hyl

hyl — Tue, 31 Aug 2010 01:24:36 +0000

Great instructions, though I should point out that in terms of getting Outlook Anywhere to work, using just your top level domain as the cert common name (ie montopolis.com) will cause a failure if Outlook’s RPC/HTTP settings by default point to a given host (ie msstd:mail.montopolis.com)

By: Babul A. Mukherjee

Babul A. Mukherjee — Sat, 28 Aug 2010 06:38:44 +0000

Bobby -

Thanks for the feedback!

Yes the internal server names has bitten me before too (and cost me $$$ ).

Exchange 2010 has a nice wizard in “Server Configuration” to help with the certificate request which helps prevent that also. I prefer that wizard now to DigiCert’s online wizard

By: Babul A. Mukherjee

Babul A. Mukherjee — Sat, 28 Aug 2010 06:34:41 +0000

Ashwin -

Thanks for the feedback!

Autodiscover or authentication prompts become problematic if your CN is just your TLD (top level domain) as I outlined in the post.

First make sure your GoDaddy Intermediate Certificates are installed correctly per the instructions here: http://help.godaddy.com/topic/742/article/4877

Then make sure your OutlookProvider certificate principal name is configured correctly, as shown here: http://technet.microsoft.com/en-us/library/dd439371(EXCHG.80).aspx

Then run all of the connectivity tests from here https://www.testexchangeconnectivity.com/ to make sure all is correct!

Hope that helps!

By: Bobby

Bobby — Fri, 09 Jul 2010 20:59:26 +0000

Thank you so much for this write up. I was working on deploying Exchange 2010 and i was having problems with my 3rd party certificate displaying an error of “The name of the security certificate is invalid or does not match the name of the site” when users started Outlook 2010. It turned out the problem wasn’t on my end, but when i created the certificate with godaddy, i neglected to add my internal server’s name to the SANs and this caused the certificate to be accepted on outlook web access, yet it couldn’t be verified internally.

Your walk through helped me a ton.

By: Ashwin

Ashwin — Wed, 30 Jun 2010 02:08:35 +0000

Thank you for the helpful writeup. I encountered an issue with XP clients using autodiscover. If you CN is different from SAN’s, XP clients have trouble authenticating. Vista/W7 do not have this issue.

By: Tweets that mention Exchange 2010 & GoDaddy UCC certificate walkthrough | Ramblings from The Montopolis Group -- Topsy.com

Thu, 14 Jan 2010 12:45:24 +0000

[...] This post was mentioned on Twitter by Babul A. Mukherjee and Babul A. Mukherjee, TMG SupportDesk. TMG SupportDesk said: New Blog Post: Exchange 2010 & GoDaddy UCC certificate walkthrough http://ow.ly/16kH6E [...]