Solved

xp - using outlook 2010 with exchange 2013

Posted on 2014-02-13
6
419 Views
Last Modified: 2014-02-22
I have been battling the following issue for a few days now.  We have xp machines with outlook 2010 connecting to an exchange 2013 server.

I have it set to auto-discover (microsoft actually setup for us).

When i set the following settings on the xp to msstp:*.domain.com it automatically reverts back to the below putting owapp in its place. without the * it will not connect.

not working
is there a way to prevent the settings from being changed? I have another xp box that works just fine and the settings stay at *.domain.com

Thanks!
0
Comment
Question by:bbimis
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 37

Assisted Solution

by:Jamie McKillop
Jamie McKillop earned 500 total points
ID: 39856771
Hello,

Run the following command in the Exchange Management Shell

Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com

-JJ
0
 

Author Comment

by:bbimis
ID: 39856982
tried that doesn't work.
0
 

Author Comment

by:bbimis
ID: 39856998
can it somehow in the registry be forced not to change?
if i have msstd:*.domain.com in there it works fine. thats how i get it to work by changing it to a *
but it will work for a while then revert. however other xp machines seem to work just fine.
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 39857054
You may need to wait for a bit for that change to take effect. It gets that value from the autodiscover service. If it is still changing, the autodiscover service isn't aware of the new value yet.

-JJ
0
 

Accepted Solution

by:
bbimis earned 0 total points
ID: 39857231
i found that if i added autodiscover.outlook.com to the registry it works just fine
the broken machines only have autodiscover-s.outlook.com in there
0
 

Author Closing Comment

by:bbimis
ID: 39879008
this worked on most but not all still having issue but changing the star works
0

Featured Post

Office 365 Training for Admins

Learn how to provision tenants, synchronize on-premise Active Directory, and implement Single Sign-On with these master level course.  Only from Platform Scholar

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question