[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Exchange 2010 - Autodicover / Mac not working after upgrade.

Posted on 2013-01-04
8
Medium Priority
?
586 Views
Last Modified: 2013-01-11
I had a 2007 SBS server that was messed up (wouldn't take updates).

I install a new 2007 server, moved all the mail over, and force the old 2007 exchange server down.

Then I installed exchange 2010 and moved all the mail to that server.

That seems to be working ok, but something is up with autodiscover and remote access and I'm getting a lot of calls from remote users.

I can get Iphones, win phones and Win Outlook to work.  but not Outlook on Mac.


I found some articles that maybe my auto discover was messed up so I tried the following and got an error.
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity CAS_Server_Name -AutodiscoverServiceInternalUri https://mail.ext.com/autodiscover/autodiscover.xml
The operation couldn't be performed because object 'CAS_Server_Name' couldn't be found on 'OLDEXCHANGE.domain.local'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-ClientAccessServer], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : 5C904EB3,Microsoft.Exchange.Management.SystemConfigurationTasks.SetClientAccessServer



If you notice the error is spitting the name of the original exchange server (the one that is now shut down).


Any ideas on what to do next?
0
Comment
Question by:erikwhiteway
[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 Comments
 
LVL 23

Expert Comment

by:Stelian Stan
ID: 38745241
0
 
LVL 12

Expert Comment

by:aindelicato
ID: 38745343
Did you create new certificates for autodiscover?
0
 

Author Comment

by:erikwhiteway
ID: 38745388
clonyxlro: I've already run the commands from that article and I get the errors above.

Aindelicato: I loaded a new UCC SSL with remote.ext.com, mail.ext.com, autodiscover.ext.com server.domain.local
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38746537
The reason you are getting the old Exchange server in the error isn't because it was Exchange, but because it was a domain controller. When Exchange is installed on a DC, the only DC that Exchange will use is that one.

Therefore I expect that you still have references to the old server in the domain.
You said that you forced the server down - what exactly did you do? Did you DCPROMO the server out? Exchange and AD are very sensitive and if you don't remove everything then you will get a mess. You are going to have to clean up the domain before everything will settle down correctly.

Simon.
0
 

Author Comment

by:erikwhiteway
ID: 38749213
I got those commands to run (turns out I didn't replace the server name in both places on the command).

so I've run all the commands.

I've installed a NEW SSL with Mail.ext.com as the main name.

Outlook and everything else is still fine. but MAC outlook will still not connect.  It does the initial setup, but then spits a generic error when it tries to open.
0
 

Author Comment

by:erikwhiteway
ID: 38749291
Also - I ran all the tests on the MS exchange test web site come back with no errors.
0
 

Accepted Solution

by:
erikwhiteway earned 0 total points
ID: 38749426
Found the answer:  the EWS folder in IIS did not have basic authentication turned on.
0
 

Author Closing Comment

by:erikwhiteway
ID: 38766434
change permission in IIS console - just enable basic authentication, and I added the default domain in the options.
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

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

I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
To show how to create a transport rule 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 Mail Flow >> Rules tab.:  To cr…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…
Suggested Courses

656 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