Outlook 2013 randomly loses connection to Exchange 2007 server
Hello everyone,
I have received complaints from some of our users over the past couple of months about them not receiving mails or about sending mails which do not get delivered. A little bit of investigation into the matter showed me that Outlook 2013 had lost its connection
to the Exchange server. (Which is Exchange 2007 SP3 running on Windows Server 2008 / SBS2008, in case it matters.)
Which is bad enough in itself - none of our users running Outlook 2007 and 2010 had that problem - but it also does so in a rather inconspicuous manner, so the users did not notice. Closing and restarting Outlook helped every single time, but the users did
not notice when this happened, and telling them to just restart Outlook every hour or so does not seem like an overloy practical idea.
All of the clients encountering the problem are running Outlook 2013 on Windows 8/8.1 Pro. We do not have any clients running older versions of Outlook on Windows 8, so I cannot tell for sure if this problem originates in the OS or if it is an Outlook problem.
The first couple of times I encountered the problem, it was on laptops, so I suspected some power management issue initially. I made sure Outlook connected to the server via HTTPS, which it already did. Then I did not hear of the problem for about two months,
but recently, two of our users have run into the problem again, and while these were still Windows 8.1 machines, running, of course, Outlook 2013, they are plain desktop computers, not laptops, and I already toned down their power management settings, so I
do not think that it has to do with the problem.
Has anybody encountered a similar problem or even - more importantly - a solution? This problem is really frustrating, because our users are very sensitive to problems with their email, and the fact that this problem only occurs randomly and - all in all
- rather rarely, makes it very hard to track down.
Thank you all very, very much for any insights you might be able to share with me!
Hi,
Please ensure that Outlook 2013 clients retain their connection with the Exchange server using HTTP:
Have the Outlook 2013 user check the settings under FILE -> Account Settings -> Account Settings -> E-mail tab -> Select the account and click Change -> More Settings -> Connection tab -> Exchange Proxy Settings -> Make sure both
"On fast networks, connect using HTTP first, then connect using TCP/IP" and "On slow networks, connect using HTTP first, then connect using TCP/IP" are selected -> OK.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Similar Messages
-
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanksHi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang -
Unrecognized certificate when Outlook 2010 tries to connect to Exchange 2007 on SBS 2008
Hi all,
I believe this is a security issue rather than a connectivity or configuration problem.
Running Outlook 2010 on Windows 7 trying to connect to Exchange 2007 on SBS 2008, I receive the following error:
"The name of the security certificate is invalid or does not match the name of the site"
When I view the certificate I see that it was issued to "zx-server" by "zx". This is NOT my domain CA nor is it a certificate I recognize. I use a self-issued certificate (i.e. issued by the SBS box). I also receive this certificate error when I browse to
the internal website (companyweb). No other computers on the network are seeing this behaviour.
I have checked the certificate stores in certmgr and I can't find any such certificate or CA. I have also searched the entire hard drive with no luck. I have run Kaspersky AV, Malwarebytes and MS Security Essentials several times but I can't find any malware.
I also recently installed Comodo Firewall (the problem began after this).
I need to find and remove the certificate and prevent it from being presented to me every time I try to connect to the server. All help, advice and suggestions appreciated.
AideHi,
It’s really a common issue.
This issue occurs if the following conditions are true:
You replace the default self-signed Exchange Server 2007 or Exchange Server 2010 certificate with a different certificate.
Note The Setup program in Exchange Server 2007 or in Exchange Server 2010 creates a default self-signed certificate when Exchange Server 2007 or Exchange Server 2010 is installed.
The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
o
The Service Connection Point object for the Autodiscover service
o
The
InternalUrl attribute of Exchange 2007 Web Service (EWS)
o
The
InternalUrl attribute of the Offline Address Book Web service
o
The
InternalUrl attribute of the Exchange unified messaging (UM) Web service
By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the
following URL is stored:
https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml
This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate
may have an FQDN that resembles the following FQDN:
mail.contoso.com
This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook
2007 to the mailbox.
For more detailed information about the procedures to fix the issue, please refer to the following KB article:
Title: Security warning when you start Outlook 2007 and then connect to a mailbox
that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of the site"
URL:
http://support.microsoft.com/kb/940726
Regards,
James
James Xiong
TechNet Community Support -
Cannot connect to Exchange 2007 server on OS 3.1
Hi
Since I've upgraded to OS 3.1 on my iPhone 3GS I cannot connect to my Exchange 2007 server. The phone simply tells me "The connection to the server failed.".
What could this be? I've read the problems that 3G people are experiencing, but I've got the 3GS.
Is there anyway to debug this? The Exchange server works fine in Outlook and I can even connect to the web interface through Safari on the iPhone.
Any suggestions?
Best regards,
Thomas René SidorHi,
Seems you have found the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/5b7d250e-c995-4322-b1e7-5ad14ace81c5/cannot-connect-to-exchange-2013-server-prompt-for-username-and-password-that-are-not-accepted?forum=exchangesvrgeneral#d266273b-e04c-45a9-8b0f-8b48bf647a86
I'm post the answers here so that it will benefit for other community members who have similar qustions:
Install the
November
2012 Update for Outlook 2007 SP3 to resolve the problem.
Thanks for our MCC steve siyavaya.
Cheers,
Steve Fan
TechNet Community Support -
Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected
Hi there,
We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
===
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
===
I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
with the installation or something else needs to be done first?
Thanks in advance.I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
That would be a huge disaster!
Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
setup /PrepareAD /IAcceptExchangeServerLicenseTerms -
Outlook 2013 Constantly Prompting For Credentials - Exchange 2007 - Small Business Server 2008
Hello, I am having a problem using Windows Small Business Server 2008 and Exchange 2007 with Outlook 2013. The issue is that a credentials box appears in Outlook 2013 when using there exchange account whilst connected to the domain. The box will randomly
prompt for user credentials, once the user credentials are entered it will either pop back up again and if you enter the details in again it will continue to pop up for around 4 or 5 times before accepting the credentials. It will then pop back up within 15
minutes and do the same thing, if you click "Cancel" on the box it will also go away and remain connected to exchange however a popup in the bottom right will appear asking for a password even though you can send / receive from the mailbox.
I have looked into this issue for hours and hours and still can not find a resolution, I have tried re-installing Office 2013 and re-creating the Outlook Profile as-well as as the Windows 7 Profile. I have checked through all the SSL certificates in IIS
and everything appear to be correct.
Is this a common issue? Is there anything I can do to further diagnose or fix this issue without having to try to re-install both the server and machine?Hi James_wilson,
Any update?
Just additional, would you please let me know whether have installed all updates for Outlook 2013? If hasn’t, please install and then monitor the result.
Please also check if you enable
Always prompt for logon credentials setting in Outlook 2013.
If you enable this setting, please uncheck and check if this issue still persists. Meanwhile, please remove the old credential in
Credential Manager, then add again. Then monitor the result
By the way, please run the Exchange BPA on the SBS 2008 server and check if can find some issue.
Hope this helps.
Best regards,
Justin Gu -
Outlook 2013 can't connect to Exchange server
Trying to set up Outlook 2013 on my new work laptop. I have the correct Exchange server name and emaill address, but get the error message "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this
action." In fact, I'm online and connected to the internet. When I open up a "CMD" window, I can ping the server, so I know my computer can see the server, only Outlook can't. My laptop is running Windows 7, 64-bit. The Office/Outlook 2013 is
64-bit as well. I've tried with my firewall both on or off, and it doesn't seem to make any difference.
btw - I have essentially the same configuration set up on my iPhone, and can send and receive emails with no issue.
Does anyone have any suggestions on how to resolve this issue.Hi
As per the information and details provided by you, to connect the Outlook 2013 from Exchange server please follow these steps: -
1. Open Outlook 2010 or Outlook 2013. If the Outlook startup wizard appears, on the first page of the wizard, click Next. Then, on the Email Accounts page, click Next to set up an email account.
If Outlook startup wizard does not appear, on the Outlook toolbar, click the File tab. Then, just above the Account Settings button, Click Add Account.
2. On the Auto Account Setup page, Outlook may automatically fill in the Your Name and Emil Address settings based on how you are logged on to your computer. If the setting is filled in and they are correct, click Next to
have Outlook finish setting up your account. If the settings on the Auto Account Setup page are not filled in or are not correct, do the following steps: -
• If the settings on the Auto Account Setup page doesn't fill in, type the correct settings based on the information that was provided to you by the person who manages your email account.
• If the name in the Your Name box is not correct, you may need to reset the options on the Auto Account Setup page before you can edit your name. To reset the options, click the option button next to manually configure
server settings or additional server types, and then click the option button next to Email Account.
3. After you click Next on the Auto Account Setup page, Outlook will search online to find your email server settings. You will be prompted to enter your user name, password during this search. Make sure that you enter your
full email address as your user name.
If Outlook is able to set up your account, you will see the following text: Conguratulations, Your email account is successfully configured and ready to use. Click Finish.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G -
Outlook 2013 can't connect to Exchange 2013 SP1
Hello,
I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain) with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
Thank you in advance,
MichaelHi,
When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
"Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support -
The CEO of one of our clients has 2 workstations we'll call them Old and New Dells.
He'd RDP into his new Dell and Outlook will not connect to Exchange and eventually stops responding. His old Dell work just fine.
We restarted the new Dell and the problem persists. I tried pinging the Exchange server and don't get a response. I ping the other servers in the network and I get responses from all of them. On the new Dell I tried going OWA and the website failed to load.
The old Dell has no such issues. Not sure what's going on and could use some guidance. I tried disabling the firewall and that didn't work. It looks like it's only affecting his new Dell, I have not heard of any other users reporting problems. Any ideas?Hi,
Since you can't ping the Exchange server, it's more likely a server side issue. This forum is for general questions and feedback related to Office client side issues, it's better to post your question to the Exchange server forum to get further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected] -
Outlook 2010 Will Not Connect to Exchange 2007 on SBS 2008 Server
Good Morning,
I have a user who cannot connect to the exchange server on SBS 2008 with outlook 2010. When they start outlook, it shows disconnected and will not connect for a minimum of 20 minutes to an hour. Any suggestions on how to fix this would be appreciated.
I have rebuilt their profile, but that does not fix the issue.
Thank you,
Lee F.
Lee Feldman SMB ConsultantHi,
Thanks for posting in the forum.
Regarding the current issue, since you have recreated the user profile without any issue, I suspect that it’s mainly caused by the network issue. At this time, please first check the TCP/IP
configurations as Larry mentioned. Then, please also refer to the article below for details about how to troubleshoot Outlook connectivity issue.
Troubleshooting Microsoft Exchange: Outlook Connectivity Issues
http://blogs.technet.com/b/mspfe/archive/2011/04/12/troubleshooting_2d00_microsoft_2d00_exchange_2d00_outlook_2d00_connectivity_2d00_issues.aspx
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support -
Outlook Mac Loses Connection to Exchange Server
Hi All,
I've had this problem pretty since deployment a couple of weeks ago, so I'm hoping some one can point me in the right direction. I'm running Exchange 2013 on a Server 2012 Standard box with the DC running on a different box, every thing up to date.
Mac clients running Outlook 2011 (14.4.2).
Periodically throughout the day, Outlook loses connection to Exchange server. After several minutes, it will connect back up, and seems to operate normally. During the down time, I am able to connect to OWA, and ActiveSync seems to work as well.
If I run the Remote Connectivity Analyzer while Outlook is responding, I get no errors and the "Connectivity Test Successful" message. However, if I run it while Outlook is NOT responding, I get the following:
Exchange Web Services synchronization, notification, availability, and Automatic Replies.
Not all tests of Exchange Web Services tasks completed.
Creating a temporary folder to perform synchronization tests.
Failed to create temporary folder for performing tests.
Exception details:
Message: The request failed. The operation has timed out
Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
Stack trace:
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
Elapsed Time: 100141 ms.
Nothing I've attempted to do so far as had any meaningful impact, and I am fairly new to Exchange.
Following the adice I've seen online so far, I've:
I've made sure the auto discover in DNS points to the Exchange server.
I've disable auto-discover on the client, manually adding accounts, tried using their FQDN, local IP, LAN IP.
I've made exceptions to the proxie on the client.
Just not sure where to look next? Appreciate any advice out there.
Thanks,
MichaelHi,
Before we go further, I'd like to confirm if your Outlook clients can work well when your Outlook MAC clients come across the issue.
If the issue only happens on your Outlook MAC clients, we can check the IIS log and confirm if there is any error releted to EWS. And you can recreate your EWS virtual directory to have a test.
Thanks,
Angela Shi
TechNet Community Support -
Upgraded to Exchange 2010 now outlook 2013 can't connect externally
Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
Any suggestions?
ICHCHi ICHC,
Just as Ed said, we should create new rule on TMG during the upgrading.
Found an blog for your reference:
Upgrade from Exchange 2007 to Exchange 2010 - Part II
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software of information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Outlook 2013 Issues with Connecting to Gmail Exchange
Outlook 2013 will not connect with Gmail account on cas_array.yourhostedexchange.com server.
Error message below appears each time I try to set up the account:
The action cannot be completed. The connection to microsoft exchange is unavailable. Outlook must be online or connected to complete this action.
Occasionally it will set it up, then it reverts to 'Trying to Connect' .... maybe lasts a day working fine at the most.
Have attempted to use Outlook 2010 as never had issue when using this platform previously - also failed. Bigpond email as pop account is working fine.
Suggestions?Hi,
According to your description, there is connectivity issue about your Gmail account. If I misunderstanding your meaning, please feel free to let me know.
If yes, I recommend you contact with Gmail support for more professional help.
If it’s Exchange account, I recommend you firstly check the connectivity by using Test Email AutoConfiguration:
http://social.technet.microsoft.com/Forums/en-US/54bc6b17-9b60-46a4-9dad-584836d15a02/troubleshooting-and-introduction-for-exchange-20072010-autodiscover-details-about-test-email?forum=exchangesvrgeneral
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support -
Windows XP SP3 and Outlook 2010 can't connect with Exchange 2010 or Exchange 2013
XP+SP3+Outlook 2010 can't connect to Exchange 2010&2013 in the internal network without safe mode.
Hi,
Did you get any error messages?
Do you have Outlook Anywhere and autodiscovery set up properly?
Can you ping the Exchange server?
Please use Test Email AutoConfiguration
to test if the Autodiscover service is configured properly. See:
https://hosting.intermedia.net/support/kb/default.asp?id=2150
We can also use the remote connectivity analyzer to troubleshoot the issue:
https://testconnectivity.microsoft.com/
In addition, turn off your firewall and anti-virus to check the result.
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support -
Outlook 2013 won't start with Exchange 2003 on the network
Hello All,
I have outlined my problem below, If someone could please help me that would be great!
Environment
==========
SBS 2003 Server Running AD and Exchange 2003
Clients are Windows 7 with Office 2013 and Outlook 2007 (to connect to existing 2003 Server)
Issue
=====
I am in the process of Migrating off of SBS 2003 to Office 365. The situation is that my customer needs to keep the SBS 2003 server until end of life where they will at that time determine a upgrade path. They however do not want to use Exchange
anymore. I have migrated their mailboxes successfully to Office 365.
The problem that I am running into is with Outlook 2013. Because Exchange 2003 server still exists in the network I am unable to launch Outlook 2013. I get a Message
"The Resource that you are trying to use is located on an unsupported version of Microsoft Exchange Contact your e-mail administrator for assistance"
I have tried to create a new Outlook profile. However since the exchange server exists still it auto discovers the server for the account.
Questions
========
1. What is the best workaround for this situation? My customer still needs to keep their SBS sever for their domain and plans on retiring the server before Server 2003 End of Life this coming server. (Upgrade is not an option, nor is getting
rid of the Domain, they are a small company).
2. If I disabled the Exchange services on the server would this work? Would outlook 2013 not detect Exchange
2003 on the network?
Basically I need to force Outlook 2013 to look at Office 365.
3. Configuring Outlook 2013 to manually connect to Office 365? The problem here is that how do I locate the server name for the manually connection? I have found some blogs that say to use Remote Connectivity Analyzer https://testconnectivity.microsoft.com/
but I cant seem to get that to work.
Any ideas?
Thanks!Hi,
Please refer to the following article to check your migration steps from Exchange 2003 to Office 365:
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
If all mailboxes are moved to Office 365, Outlook 2013 would use Autodiscover service to connect to your Office 365. Please make sure your Autodiscover service is configured correctly in Office 365. Also
verify that all the DNS records and Public Folder are updated and pointed towards Office 365 services. If there is any question about migration to Office 365,
we can ask a question in Exchange Online forum for more suggestion:
https://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Regards,
Winnie Liang
TechNet Community Support
Maybe you are looking for
-
CAN NOT UPDATE iPOD. file or directory being corrupted.. help me!!
I have no idea why my iPod won't sync, but when I try to sync it this message error comes up: The iPod "myiPodname" cannot be updated. The file or directory is corrupted and unreadable. Can you please help? I'm so confused. :/
-
Hi I run the following code on the p900 device. this application connects to a url and gets a simple text message then displays it. ( this code is a modified example from the core j2me site examples ...) it doesn't work. on nokia 6310i device it work
-
What is the Process of Back to Back Order ?
Hi, I want to know the Whole Process of Back to Back Order of an Item ! And plz reply my Question .......................? Sir
-
Sales order Request delivery date map with PO delivery date
Hi I have an requirement. While run the MRP to create PR from Sales order. We need take the delivery date in the sales order to PO delivery date. How to configure Pl advice Regards, Kumar
-
Internal error : depeep 2