Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 158
  • Last Modified:

Misbehaving Roamcache!

I have a user who we have switched from exchange (on an SBS2008 domain) to Hosted exchange

The user is still attached to the domain where the previous exchange server still resides but does not use the email facility of that mail server. Instead the domain MX records have been pointed to an external mail server supporting POP3 and Hosted Exchange.

His email is working fine on hosted exchange, he can access from multiple devices no problem. However on his main office PC his Autocomplete feature is behaving weirdly - Everytime he tries to send email to an internal user the message is returned undelivered. The bounce message indicates it is trying to send through the previous exchange server.

I've tested the Roamcache file using some software called nk2edit and I can see that the internal addresses are stored under EX instead of SMTP - Even if I delete these out (there are only 10-15) and save the Roamcache file next time we try to send to an internal user again it overwrites the Roamcache with the previous version and all EX users return.

I think the obvious answer is that for some reason the previous mail server is interfering, is there a way I can remove that mail server from the equation without losing it as an archive?
0
MadPC
Asked:
MadPC
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
If Exchange is installed then it will try and get involved with email. Due to the way that Autodiscover works, it queries the domain first and only if a record does not exist will it try to use external DNS records.

You could try changing the value of

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

to match the host name used for external Autodiscover. That should force the clients to go out to the external host even if they do find the internal Autodiscover entry.

Realistically though, unless you were in a Hybrid with Office365 you should remove the on premise Exchange server.

Simon.
0
 
MadPCAuthor Commented:
Hi Simon thanks for the advice

I was thinking the same thing here and I've found a 'disable server' option within the Exchange console which might be easier as we don't need it any more but would be good to keep a copy in case needed.

I did have a read through this thread which offers an alternative process (albeit controversial) but I would rather click a button and turn it all off if that can be done?

Image attached, can anyone confirm if that's the right setting? I don't want to 'disable server' if it's going to knock my main server offline and not the Exchange server as we hope?

thanks
0
 
MadPCAuthor Commented:
Can't see the attachment so trying again...exchange disable button?
0
 
Simon Butler (Sembee)ConsultantCommented:
There is no "disable server" option in Exchange. I was curious what you had found. The screenshot explains everything.

That option is to disable the Receive Connector - all that will do is stop the server from receiving email. My previous advice still stands.

Simon.
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

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