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.
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Outlook 2007 /2010 cannot connect to exchange 2010 server after migration from SB2003 server
Posted on 2013-01-03
We recently migrated from SB 2003 with exchange to SB Server 2008. Since the migration, we have not been able to get our Outlook programs to connect to exchange. OWA works but we need Outlook to work. We are running different versions of outlook, predominently 2007 and 2010. How can we get Outlook functioning again?
[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
3-
2
10 Comments
Active 2 days ago
Are all the services running for Exchange on the new sbs box?
This is internal outlook users?
This is internal outlook users?
Yes, all services are running on the new server as best I can tell. And yes, we are internal outlook users.
Active 2 days ago
Any errors when you try to connect?
Is the 2003 box still around or disconnected?
Can you ping the Exchange server by fqdn?...
Is the 2003 box still around or disconnected?
Can you ping the Exchange server by fqdn?...
To be certain that all services are running on the server run in exchange power shell :
>Test-ServiceHealth
If everything is OK you should see "True" for all installed roles
However its is probably a DNS issue.
Can you try to create a brand new user or recreate an existing Outlook profile?
Do you see 3 green check marks ? (Do not select to "manually" create the profile.)
Check if the client is using the SBS2010 as a DNS server (might check your DHCP settings)
On you SBS open the DNS console and remove any left-over reference of your old GC2003
Also run Run the Fix My Network Wizard
http://technet.microsoft.com/en-us/library/cc546095(v=ws.10).aspx
>Test-ServiceHealth
If everything is OK you should see "True" for all installed roles
However its is probably a DNS issue.
Can you try to create a brand new user or recreate an existing Outlook profile?
Do you see 3 green check marks ? (Do not select to "manually" create the profile.)
Check if the client is using the SBS2010 as a DNS server (might check your DHCP settings)
On you SBS open the DNS console and remove any left-over reference of your old GC2003
Also run Run the Fix My Network Wizard
http://technet.microsoft.com/en-us/library/cc546095(v=ws.10).aspx
I ran Test-ServiceHealth in the exchange management shell and found several services are not running. MSExchangeRPC, MSExchangeSA, and MSExchangeEdgeSync are not running... Our IT guy cant work on our server right now. are these services easily started? is there any reason they should not be running? I am not an IT person... I know enough to be dangerous :)
Yes just run again in the power shell the following :
>net start MSExchangeRPC
>net start MSExchangeSA
>net start MSExchangeEdgeSync
Then run again Test-ServiceHealth to verify that everything is now showing "TRUE"
The first 2 services are really required in order your Exchange server to function normally
It happens quite often that some services are not started when the exchange is running on a domain controller and when rebooting the server.
Please check here for this know issue:
http://blogs.technet.com/b/sbs/archive/2011/03/24/exchange-services-may-not-start-automatically-after-a-reboot.aspx
The use method 2 and/or method 3 from the following KB to fix the problem :
http://support.microsoft.com/kb/940845
>net start MSExchangeRPC
>net start MSExchangeSA
>net start MSExchangeEdgeSync
Then run again Test-ServiceHealth to verify that everything is now showing "TRUE"
The first 2 services are really required in order your Exchange server to function normally
It happens quite often that some services are not started when the exchange is running on a domain controller and when rebooting the server.
Please check here for this know issue:
http://blogs.technet.com/b/sbs/archive/2011/03/24/exchange-services-may-not-start-automatically-after-a-reboot.aspx
The use method 2 and/or method 3 from the following KB to fix the problem :
http://support.microsoft.com/kb/940845
Featured Post
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.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …
- Microsoft Office
- Office 365
- Outlook
- Office / Productivity
- Microsoft Word
- Microsoft PowerPoint, Microsoft Excel, *Office 2013, *office 2010, *Office 2016
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month4 days, 13 hours left to enroll
636 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.