Solved

Exchange 2007 & Outlook Anywhere

Posted on 2009-05-07
12
539 Views
Last Modified: 2012-05-06
Hi,

I have a problem with the autodiscover service changing server names all the time.

My setup:
One domain spread across 3 separate sites each with an exchange 2007 serer and AD server connected via VPN. Each Exchange server has the following roles: HUB Transport, Client Access and Mailbox. I have the correct certificate installed and it can resolve autodiscover.domain.com, site1.domain.com, site2.domain.com and site3.domain.com +mail etc... The autodiscover A record points to site1 both externally and internally.
The problem Im having is that autodiscover works both internally and externally but then at random times it will change clients outlook setting to one of the other servers\sites that there mailbox does not reside on. E.g. A remote user with a mailbox on site1\server1 connects and outlook works and discovers the correct servers site1.domain.com then a week later they will open outlook and it will constantly prompt the user for a password but wont authenticate, if I check the outlook settings I see its been changed to site2.domain.com instead of site1.domain.com where there mailbox sits. If I change it back to site1.domain.com then they can work again as normal. There is no pattern to when it changes and which servers it will change to, sometimes its site 1, then site3 then site1 again or site2...
 
Is there away to specify that a user on a certain mailbox store always connects to that server? Or remove a rule to say that they can use any server name within outlook as they are part of the same domain?

If you require any more info or if I havent made myself clear please let me know. Thanks in advance for your help.
0
Comment
Question by:brad-willson
[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
  • 8
  • 3
12 Comments
 
LVL 1

Expert Comment

by:progjm
ID: 24325466
What is the CN or your certificate? Is that the same value that have have for msstd:?
0
 

Author Comment

by:brad-willson
ID: 24325621
Thanks for your reply. The CN is different to the msstd:
I use a different msstd server for each site that a users mailbox resides on, is that not correct?
0
 
LVL 1

Expert Comment

by:progjm
ID: 24326076
Do you have a test Exchange server you can try this command on

Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:(mail or whatever).domain.com
0
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

 
LVL 1

Accepted Solution

by:
progjm earned 500 total points
ID: 24326144
You can also use this command to keep the value from automatically populating

Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:$null
0
 

Author Comment

by:brad-willson
ID: 24329927
Thanks again, I dont have a test exchage server to run that command on. If I run it on our live server would running that command on only one server affect all 3 servers or would it only change the settings on the exchange server that Im running it on?
0
 
LVL 1

Expert Comment

by:progjm
ID: 24341400
Should only chnage the settings on the one server
0
 
LVL 1

Expert Comment

by:progjm
ID: 24386889
How did this go?
0
 

Author Comment

by:brad-willson
ID: 24394486
Hi,

I made the change Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:$null and it appears to work. Thanks for your help. I would like to leave it for a week or so as the problem seems to be ok and then comes back. If it continues to work I will accept your solution! Thanks again
0
 
LVL 1

Expert Comment

by:progjm
ID: 24396581
Glad I could help, let me know if you need any more assistance
0
 
LVL 1

Expert Comment

by:progjm
ID: 24504769
How is everything working?
0
 
LVL 1

Expert Comment

by:progjm
ID: 24640726
Have not heard back from you, how are things working
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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
Outlook for dependable use in a very small business   This article is about using the Outlook application (part of Microsoft Office) in a very small business, or for homeowners where dependability and reliability are critical requirements. This …
In this video we show how to create a mailbox database 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 >> Data…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

724 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