• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 578
  • Last Modified:

Installed UCC Cert for Exchange 2007, now Outlook Anywhere not working

As the title suggests, I've installed a UCC certificate for Exchange 2007, replacing a wild card cert.  My internal and external webmail work fine, and ActiveSync clients are connecting with no problems.  But I can't get an Outlook Anywhere client to connect.  I keep getting prompted for a username/password and it won't accept anything.  I've tried fiddling around with every different setting, and at this point I'm at my wits end and need this resolved ASAP.  

Any suggestions, things to try, I've done some research on here and also other exchange forums but I'm stuck.  Thank you.
0
Sma11T0wnITGuy
Asked:
Sma11T0wnITGuy
  • 4
  • 4
1 Solution
 
MichaelVHCommented:
Hi there,

what type of authentication have you set for Outlook Anywhere?

You can view the settings with Get-OutlookAnywhere from the shell.

Michael
0
 
Sma11T0wnITGuyAuthor Commented:
Output from Get-OutlookAnywhere command:

ServerName                      : LSIEXCHANGE
SSLOffloading                   : False
ExternalHostname                : getmymail.lsisolutions.com
ClientAuthenticationMethod      : Ntlm
IISAuthenticationMethods        : {Ntlm}
MetabasePath                    : IIS://LSIEXCHANGE.lsisolutions.com/W3SVC/1/RO
                                  OT/Rpc
Path                            : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
Server                          : LSIEXCHANGE
AdminDisplayName                :
ExchangeVersion                 : 0.1 (8.0.535.0)
Name                            : Rpc (Default Web Site)
DistinguishedName               : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocol
                                  s,CN=LSIEXCHANGE,CN=Servers,CN=Exchange Admin
                                  istrative Group (FYDIBOHF23SPDLT),CN=Administ
                                  rative Groups,CN=LSI Solutions Inc,CN=Microso
                                  ft Exchange,CN=Services,CN=Configuration,DC=l
                                  sisolutions,DC=com
Identity                        : LSIEXCHANGE\Rpc (Default Web Site)
Guid                            : e07a7d60-fb53-4b20-b535-56ced82af173
ObjectCategory                  : lsisolutions.com/Configuration/Schema/ms-Exch
                                  -Rpc-Http-Virtual-Directory
ObjectClass                     : {top, msExchVirtualDirectory, msExchRpcHttpVi
                                  rtualDirectory}
WhenChanged                     : 3/3/2011 12:41:12 PM
WhenCreated                     : 7/21/2010 9:54:00 AM
OriginatingServer               : lsiadc02.lsisolutions.com
IsValid                         : True


0
 
MichaelVHCommented:
Can you change the authentication from NTLM to basic please?
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
Satya PathakLead Technical ConsultantCommented:
did u rty to ran the https://www.testexchangeconnectivity.com/ and check it .
0
 
Sma11T0wnITGuyAuthor Commented:
Michael-Changing the authentication level does not help

Satya-The test is fine until the final step, Testing SSL mutual authentication with the RPC proxy server.  

The certificate common name lsiexchange.lsisolutions.com doesn't validate against the mutual authentication string that was provided: msstd:*.lsisolutions.com
0
 
MichaelVHCommented:
Your outlook still represents the config for the wildcard cert you had before. You should first of all change the Outlookprovider

first check the Outlookprovider "EXPR" to see what setting it has for the certprincipalname. (probably "*.etc")

You should (if it's set to "*.etc") change it like this:

Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:lsiexchange.lsisolutions.com

Grts,

Michael
0
 
Sma11T0wnITGuyAuthor Commented:
Michael,

I just ran that command, and it looks like I'm able to connect now.  I will try a few other clients as well.  testexchangeconnectivity.com is going through now as well.
0
 
Sma11T0wnITGuyAuthor Commented:
Michael,

Great work, that fixed it up.  My remotes need to VPN in once to get the settings, but its working beyond that.  Thank you again.
0
 
MichaelVHCommented:
You're most welcome.

I'm glad you got it working again.

Grts,

Michael
0
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.

Join & Write a Comment

Featured Post

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now