Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

xp - using outlook 2010 with exchange 2013

Posted on 2014-02-13
6
Medium Priority
?
436 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
  • 4
  • 2
6 Comments
 
LVL 37

Assisted Solution

by:Jamie McKillop
Jamie McKillop earned 2000 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
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In my humble opinion (IMHO), TouchDown from Symantec is the best in class for this type of application, but Symantec has end-of-lifed it and although one can keep using it, it will no longer be supported or upgraded.  Time to look for alternatives t…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses
Course of the Month10 days, 18 hours left to enroll

572 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