Outlook 2013 Exchange 2007 and 2003

I have a client who has Outlook 2013. He needs to connect to a 2007 server and a 2003 server . I have not issues with connecting to the 2007 server.  What would be the best way to connect the 2003 server?  I have tried connecting the domain directly
but I get an error about setting up the ost file. The system connect to the 2007 domain.
Should I use pop3 or imap to connect?  Can you send me an article for configuring the server for either of these?
Thank you for your help.
BW
Bonnie Whalon

Hi,
Outlook 2013 is not supported on Exchange 2003.
Please refer to the following article:
System requirements for Office 2013
Specific requirements for Outlook 2013
Component  
Requirement  
For integration with Exchange
Be sure to connect Outlook 2013 to   the supported versions of Exchange: Exchange 2007, Exchange 2010, or Exchange   Server 2013. Outlook 2013 is not
supported on Exchange 2003.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

  • Unable to share calendars - This sharing message is not valid - Outlook 2013 Exchange 2007

    Running Exchange 2007 latest and greatest service pack and rollup with Outlook 2013 fully patched. When users attempt to share their calendar, the recipient receives an email that says "This sharing message is not valid. All action buttons have been
    disabled" and "(Sender not verified) - Calendar".
    We're not using IMAP or POP. Was working in the past and stopped working.

    Hi,
    Is Exchange account the default account in Outlook?
    Does this issue occur on all users? (If no, please try to recreate problematic user’s profile to check this issue)
    Please check the following setting:
    Open AD users and computers.
    Right-click on problematic user to properties.
    Under General tab, check if the E-mail field is right.
    Best Regards.
    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]
    Lynn-Li
    TechNet Community Support

  • Free/Busy not working Exchange 2007 and 2013 co-existence

    Hi,
    I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
    works correctly, but between Exchange 2007 and 2013 it's not working.
    I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
    The internal and the external URLs are set to https://legacy.mydomain.com/....
    What am I missing?
    Thanks & Kind Regards,
    Jürgen

    Hi,
    According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
    1. Does the issue happen to all users or specific users?
    2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
    3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
    create a new Outlook profile
    to have a try.
    4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
    Virtual directories settings in Exchange 2007:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Certificate and Virtual directories settings in Exchange 2013:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
    5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
    If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
    Regards,
    Winnie Liang
    TechNet Community Support

  • ActiveSync in Exchange 2007 and 2013 Coexistence

    Hi,
    I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
    owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
    autodiscover works well for users on both 2007 and 2013
    I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
    I have A records configured for both names on my public DNS and internal DNS
    THE ISSUES
    testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
    New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
    Existing users on exch2007 can no longer receive mails on their mobile devices
    URLs
    Exchange 2007
    Exchange 2013
    Internal owa
    mydomain.com/owa
    mail.mydomain/owa
    External owa
    legacy.mydomain.com/owa
    mail.mydomain.com/owa
    AutoDiscover
    mail.mydomain.com
    mail.mydomain.com
    EWS
    legacy.mydomain.com
    mail.mydomain.com
    ECP
    mail.mydomain.com
    Internal ActiveSync
    legacy.mydomain.com
    mail.mydomain.com
    External ActiveSync
    $null
    mail.mydomain.com
    OutlookAnywhere
    legacy.mydomain.com
    mail.mydomain.com
    I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
    Any help on this would be much appreciated ..
    Richard ..
    ..forever is just a minute away*

    You don't need to use a legacy URL for ActiveSync in Exchange 2013.  It will proxy ActiveSync for Exchange 2007 just fine.  In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition.  I recommend
    you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2007 and 2013 coexistence

    Hi,
    we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server)  i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
    I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
    Thanks

    Hello,
    Please check your DNS configuration and ISA/TMG rules.
    We recommend you use TMG or UAG.
    You can refer to the "TMG rules" section in the following article:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Cara Chen
    TechNet Community Support

  • I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    Hi,
    From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
    Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
    http://support2.microsoft.com/kb/2997209
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2007 and outlook 2010 frequent disconnects

    Hi,
    Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
    Every so often users disconnect and outlook then requires them to put there password in but if you restart outlook all is fine till the next time its random aswell.
    I have checked in IIS if windows and basic authentication are enabled which they are.
    If i dont use outlook anywhere i still get this problem.
    I have looked on the internet but everything i try doesnt seem to help me any ideas ?
    Thanks

    Hi,
    Before going further, would you please let me confirm whether all users (with all Outlook) encounter this same
    issue? Did you install any update or any third-party application on the server before this issue occurred?
    à
    Im having issues on SBS 2008 with exchange 2007 and outlook 2010.
    Would you please let me confirm whether installed Exchange Server 2007 SP2 (or SP3)? Did you install all necessary
    Update Rollups for the Exchange Server 2007?
    Please type
    outlook.exe /safe in RUN to start Outlook in Safe Mode, then check if this issue still exists. Meanwhile, please navigate to the website which contains Exchange Virtual Directories in IIS Manager, then enable kernel-mode authentication for each directory
    and monitor the result.
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Difference between Exchange 2007 and 2010

    Hello, 
    I want to know what are the differences between Exchange 2007 & 2010, i mean what was missing in 2007 which is addresses in 2010. Both from Administrator point of view and client point of view. How admins are going to benefit from 2010 and how clients
    will see changes in their outlook 2010 because of Exchange 2010? 
    Hasan

    Hello,
    Can you Please help me out, what is the Difference? 
    Difference between Exchange 2003 and 2007
    Difference between Exchange 2007 and 2010
    Thanks 

  • Getting UConn 8.5 to work with both Exchange 2007 and 2010

    According to the document below, I should be able to set up one Unified Messaging service to access mailboxes on both Exchange 2010 and Exchange 2007 servers.  I setup my service to point to 2010 CAS servers and I can access 2010 mailboxes, but testing 2007 mailboxes comes up with an http 200 error.  If I setup the CAS server as 2007, I can access 2007 mailboxes, but get an error on 2010 mailboxes.  This will be a real pain if I can't do this with one service.  I don't want to have to keep Unity Connection updated as users get moved from 2007 to 2010!  Anyoe know how to do this?
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html#wp1198171        

    I got this to work!  My Unified Messaging Service was originally setup to Specify an Exchange Server.  That is where I had put the  DNS name of the  CAS server (and that DNS entry pointed to several CAS servers).  I changed the Service to Search for Exchange Servers instead and used that same DNS name in the Active Directory DNS Domain Name.  When I do the test of this service, it tells me it Failed to locate a Domain Controller via DNS, but that is just informational.  It also says it successfully connected to the Exchange CAS server with the autodiscover.xml.  Now my mailboxes on both Exchange 2007 and 2010 are able to receive voicemail messages with this one Service configured.

  • I am trying to use sync outlook 2013 with icloud and am receiving this error - Setup can't continue because Outlook isn't configured to have a default profile.  Check your Outlook settings and try again - can anyone help me out

    i am trying to sync outlook 2013 with icloud and am receiving this error - Setup can't continue because Outlook isn't configured to have a default profile.  Check your Outlook settings and try again - can anyone help me out

    Here are two threads you may want to review. I'm sure there are others. Good luck!
    https://discussions.apple.com/thread/3427840?start=0&tstart=0
    http://www.slipstick.com/outlook/icloud-outlook-problems-syncing-calendar/

  • I have to use microsoft office 2007 and 2003 for windows and I'm using a macbook pro, How i can get the on mac?

    I have to use microsoft office 2007 and 2003 for windows and I'm using a macbook pro, How i can get the on mac?

    You can either use Office for Mac 2011 or use Boot Camp to run Windows or use a VM, such as Parallels Desktop to run Windows. Running Windows, you'd be able to use MS Office for Windows.
    Clinton

  • Exchange 2010 and 2003 Co-Existence Help

    Hi All,
    Hopefully someone out there can help me out.
    As the subject says i have exchange 2010 and 2003 in a co-existence mode. I have configured public folder replications and plan to use the following guide to move the public folders:
    http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
    I was about the use the MoveAllReplicas.ps1 powershell script when I had the idea to dismount the legacy (2003) public folder mail store as a test to ensure the public folders had replicated. I noticed under the 'Queues' of the legacy exchange emails were queuing
    up withing 'Messages awaiting directory lookup'.
    All other mail stores were dismounted, as a test I mounted a database (non public folder), did a force connection and refresh. All the emails disappeared from this list.
    So my questions are:
    1. Why would my exchange 2010 sever still be routing emails via the legacy server?
    2. Why would the legacy exchange require a mailstore to be mounted for mail flow to work coming from the 2010 server?
    Thanks

    Thanks for the feedback.
    The issue I am facing is that the emails I am seeing queued are not related to the public folder replications. Emails for the public folder replications normally have a subject line of: 'Backfill' or 'Folder Content'.
    When all mail stores are dismounted on the legacy server some of the outbound emails sent by users who reside on the primary server (2010) are being sent to the legacy server. I can then see these emails queued and they will not be sent until a remount at
    least one mail store.
    E.g. All mailbox stores are dismounted on the legacy exchagn, John Smith's account is located on primary exchange (2010). John sends an email and I see it stuck in the queue on the legacy server  'Messages
    awaiting directory lookup'. 
    NOTE: This does not happen for all users, It seems to happen at Random.
    I also attempted to fix the issue by creating a new 'Send Connector' with a lower cost and defining the 'Source server as the primary server (2010)
    So the question still remains why are some outbound emails still being sent out via the legacy server even though these users are on the primary exchange?
    With regards to the public folders, I used the following to add the replicas between the legacy and primary exchange:
    .\AddReplicaToPFRecursive.ps1 -TopPublicFolder “\” -ServerToAdd “Exchange2010″
    When i dismount the public folders all the public folders are accisable via the 2010 server so it seems the replications have worked.
    Would the above command not have added the replicas to all the public folders including the system public folders?

  • Exchange 2007 and 2010 with Unity Connection 8.6

    Hi all,
    We have unity connection 8.6 and exchange 2007 currently in place and runnign fine. I am ready to start migrating mailboxes over to our new exchange 2010 farm and as such we will be in co-exsistance with exchange 2007 and 2010 for awhile. What are the steps or procdures to also include exchange 2010 with the 2007 in unity connections? Currently under Smart Host is the IP address of our exchange 2007 server.
    Thank you.

    Hi,
    This depends on how you plan on performing the migration. I would suggest the following:
    -Creating a new unified messaging service for Exch 2010. You can re-use the same service account name as long as you completed the configuration steps for that integration.
    -As you move over user's mailboxes from 2007 to 2010, you can delete the 2007 UM service and add the new 2010 UM service. If you want to change many users at a time you'll need to use bulk administration to change them. If you use BAT to change accounts, see the link below where I have listed them out for another CSC user.
    -You can change the Smart Host setting once you have configured the Exch 2010 enviornment to handle your main corporate mail (changing the MX records to point to a 2010 Edge Transport).
    Changing the UM service with BAT:
    https://supportforums.cisco.com/message/3572200#3572200
    Good luck.

  • Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

    Hi
    We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
    I'm now testing with a few test users I've migrated from 2007 to 2013.
    Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
    Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
    When I start Outlook, I get the error Unable to open the default mail folders
    When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
    When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action" 
    Thanks for any help you could provide
    Martin

    Changed the
    ExternalClientAuthenticationMethod  for the 2007 server.
    Output for  Get-OutlookAnywhere | fl *method*
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
    asking for credentials.
    If I dig further and try to manually configure server settings:
    If I specify the Exchange 2013 server and try a 'Check
    Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
    If I specify the Exchange 2007 server and try a 'Check
    Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
    Any other thoughts on this issue?
    Thanks,
    Martin

  • Exchange 2007 and 2013 coexistent

    Hi
    Ive installed exchange 2013 in my domain where exchange 2007 is installed. The servers can see each other and mailbox migration works.
    The problems im having is with owa, outlook and activesync. When going (internally) to exchange2013/owa site and login in with a user thats on 2007 i have to log in twice, once on each owa site. I belive that the same will happen with activesync and thus
    not work?
    the users ive move to exchange 2013 are getting promted to type in user and pass every time!
    my setup is exchange 2007 sp3 ru11 and exchange 2013 without any cu
    thanks for the help

    The most common problem that I have seen has caused by having the wrong authentication methods configured for Outlook Anywhere on both the new and legacy server. You might want to start a new thread for that problem.
    Martina Miskovic

Maybe you are looking for