Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
COURSE of the MONTH
10 days, 21 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Exchange 2010 - Autodicover / Mac not working after upgrade.
Posted on 2013-01-04
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-Cl
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], ManagementObjectNotFoundEx
+ FullyQualifiedErrorId : 5C904EB3,Microsoft.Exchang
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?
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-Cl
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], ManagementObjectNotFoundEx
+ FullyQualifiedErrorId : 5C904EB3,Microsoft.Exchang
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?
[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
-
5
- +1
8 Comments
Follow this steps here: http://smarthost.blogspot.ca/2008/12/configuring-autodiscover-for-exchange.html
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
Aindelicato: I loaded a new UCC SSL with remote.ext.com, mail.ext.com, autodiscover.ext.com server.domain.local
Active 3 days ago
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.
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.
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.
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.
Featured Post
Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article describes how to import Lotus Notes Contacts into Outlook 2016, 2013, 2010 and 2007 etc. with a few manual steps. You can easily export and migrate Lotus Notes contacts into Microsoft Outlook without having to use any third party tools.
New style of hardware planning for Microsoft Exchange server.
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: …
Many of my clients call in with monstrous Gmail overloading issues with Outlook. A quick tip is to turn off the All Mail and Important folders from synching. Here is a quick video I made to show you how to turn off these and other folders in Gmail s…
Suggested Courses
Course of the Month10 days, 21 hours left to enroll
770 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.