Wildcard cert with Exchange 2007

I have just had a new firewall installed and the config is using port forwarding and reverse proxy as i don't have many public IP addresses.

I have purchased a godaddy wildcard for HTTPS inbound requests and it works fine.

The issue i have is that connecting to exchange now uses the wildcard cert and not the exchange's UCC cert.  The installers said 'just install the wildcard on the Exchange server and that's it'.

Having looked at various posts, most state don't use wildcards on Exchange.(Outlook anywhere, autodiscover and activesync issues)  

Some others suggest it can be easily remedied by running "Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com

Should i tell them to sort out another method of forwarding requests and keep my UCC cert on Exchange?  Or just access Exchange using HTTP internally?

I'm not fully sure of my options, which i why i paid them to configure their firewall!

Any help appreciated
LVL 13
leegclystvaleAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
Terminate the secure connection on the reverse proxy with the reverse proxy backend going unsecure to exchange.

Or use internally issued certificate between reverse proxy and exchange.
0
leegclystvaleAuthor Commented:
cheers Arnold,

so you're saying a wildcard cert will be fine?   and be ok on all the incoming exchange services, IIS OWA IMAP Autodiscovery outlookanywhere etc?
0
arnoldCommented:
You would need to terminate all those connections on the reverse proxy

                                                                                                      Each port is mapped to the internal host On the appropriate port
Client <=> reverse proxy (port group) with wildcard cert<

All TCP! Should work with pass through connections .

Test first a port at a time.

You may have to run individual reverse proxy instances for each port.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jmcgOwnerCommented:
Some others suggest it can be easily remedied by running "Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
I think that's the method I used when I used a wildcard cert with Exchange. It worked fine.
0
leegclystvaleAuthor Commented:
I've opted for the wildcard cert on exchange. Having issues there so will post another question. Thanks for your help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.