Exchange 2007 - Outlook 2013 - IMAP - no items downloaded
Hello,
I am facing a weird issue.
I use outlook 2013 and I am trying to get IMAP working from Exchange 2007. Authentication looks right and when receiving mail, outlook takes i little while when "synchronizing". But no mail is ever loaded in any directory. In OWA it looks ok and
mails are visible.
I have tried - download all mails in IMAP config, recreating account in client, view only subscribed folders/not, I don't have problematic KBs that were mentioned on few discussions.
Thanks for any advice.
Hi David,
Please make sure the latest patches and service packs are installed for your Outlook 2013. Please click Send/Receive > Send/Receive All Folders to manually update folders and then check whether all mails are download to Outlook or not.
If there is any Errors shown in the Outlook Send/Receive Process window, please collect the complete error descriptions and post it here for further analysis.
Regards,
Winnie Liang
TechNet Community Support
Similar Messages
-
One of our users is having problems setting replies from Outlook on his local PC. This is an SBS 2008 Server with Exchange 2007. The client PC is running Windows 8 with Outlook 2013. This issue doesn't seem to affect other users but this
is the only client with Outlook 2013.
When trying to set an automatic reply from within Outlook 2013 we get the "Your automatic reply settings cannot be displayed because the server is unavailable". Outlook seems to be connecting and working fine so connection to the server does
exist.
Trying this same operation from owa works without issue. Please let me know what we need to do to find a solution.
Thanks so much!Problem:
IMAP downloads inbox don't work after November patches.
If you install a fresh OS and O2K13 unpatched ,the IMAP works fine.
Fully patched O2K10 works fine too.
It worked for my customer until November patch Tuesday broke the IMAP sync.
Consultant opened case.
Response from Microsoft:
This is with regards to the issue faced by you due to regression caused by November security update. This is further to inform you
that fix is out and below is the download links for 32 bit and 64 bit of the office suites. You need to apply all 3 hotfix. The crash issue and IMAP issue would get resolved
immediately while the issue related to Free / Busy and OOF not getting set would take 24-36 hours to start working once the patch is
applied.
Below
are the KB articles:
Description
of the Outlook 2013 hotfix package (Outlook-x-none.msp): December 10, 2013:
http://support.microsoft.com/kb/2825652
Description
of the Word 2013 hotfix package (Word-x-none.msp): December 10, 2013:
http://support.microsoft.com/kb/2837674
Description
of the Office 2013 hotfix package ( 2013:
http://support.microsoft.com/kb/2849994
Description of the Office 2013 hotfix package ( December 10, 2013:
http://support.microsoft.com/kb/2849994
Issues that this hotfix package fixes
Consider the following scenario:
You have a SharePoint Server environment that has complex workflows.
You implement the ReceiveTimeOut registry entry to increase the global timeout to 90 seconds.
You click Open this task button to open a workflow task in Outlook 2013.
In this scenario, when you click any approval option from the popup dialog box, you receive the following error message:
This task could not be updated at this time.
When you reply or forward an email message by using inline replies, you cannot use the Close and Delete method of Outlook Visual Basic for Application. Additionally, you
receive the following error message:
Run-time error '-2147467259 (80004005)': This method can't be used with an inline response mail
item.
Consider the following scenario:
Assume that User A is located on an on-premises Exchange Server, and User B is located on Cloud.
Both the on-premises Exchange Server and the Cloud enables the Federation Trust.
User A share his own calendar to User B with Full Details permission, and send the sharing invitation to User B.
User B opens the sharing invitation from User A, click Open this Calendar, Outlook browses to the Calendar module and opens
the shared calendar.
In this scenario, the shared calendar does not show any content.
Consider the following scenario:
You install Outlook 2013 on Windows Server 2008 R2 or Windows Server 2012 with Terminal Server Role installed.
You implement the Use Cached Exchange Mode for new and Existing Outlook Profiles Group Policy settings and enable it.
In this scenario, when you open the Outlook Account Settings window, and double-click the Exchange
account, the Use Cached Exchange Mode check box is not checked in the popup dialog box.
Consider the following scenario:
You have an Exchange Server that has Public Folders.
You create the Outlook Security Settings folder under
All Public Folders.
You publish the AdminSecurityMode registry entry and set to a value of 1.
You configure Outlook 2013 to use cached mode.
In this scenario, when Outlook 2013 connects to Exchange Server, Outlook crashes.
Description of the Word 2013 hotfix package (Word-x-none.msp): December 10, 2013:
http://support.microsoft.com/kb/2837674
Assume that you open a meeting request in a separate window in Outlook 2013. When you click
Accept and then click
Send Reply Now, Outlook crashes.
Description of the Outlook 2013 hotfix package (Outlook-x-none.msp): December 10, 2013:
http://support.microsoft.com/kb/2825652
Issues that this hotfix package fixes
Assume that you have a recurring appointment that does not have a subject. You make some changes to one instance of the appointment and then save the instance. When you
try to open or delete the instance, Outlook may crash. Additionally, when you drag-and-drop one instance of the appointment to a different
time in the calendar, Outlook may crash.
When you reply or forward an email message by using inline replies, you cannot use the Close and Delete method of Outlook Visual Basic for Application. Additionally, you
receive the following error message:
Run-time error '-2147467259 (80004005)': This method can't be used with an inline response mail
item.
Consider the following scenario:
Assume that User A has a mailbox that is located on an on-premises Exchange Server, and User B has a mailbox that is located
on Cloud.
Both the on-premises Exchange Server and the Cloud enable the federation trust.
User A share his own calendar to User B with Full Details permission, and send the sharing invitation to User B.
User B opens the sharing invitation from User A, click Open this Calendar, Outlook browses to the Calendar module and opens
the shared calendar.
In this scenario, the shared calendar does not show any content.
Consider the following scenario:
You install Outlook 2013 on Windows Server 2008 R2 or Windows Server 2012 with Terminal Server Role installed.
You implement the Use Cached Exchange Mode for new and Existing Outlook Profiles Group Policy
settings and enable it.
In this scenario, when you open the Outlook Account Settings window, and double-click the Exchange
account, the Use Cached Exchange Mode check box is not checked in the popup dialog box.
Consider the following scenario:
You have an Exchange Server that has Public Folders.
You create the Outlook Security Settings folder under
All Public Folders.
You publish the AdminSecurityMode
registry entry and set to a value of 1.
You configure Outlook 2013 to use cached mode.
In this scenario, when Outlook 2013 connects to Exchange Server, Outlook crashes.
Consider the following scenario:
You have two Active Directory forests (Forest A and Forest B).
User A and User B have their mailboxes that are located on Forest A.
User A share his own calendar with User B with Full Details permission.
User B add the shared calendar and let it sync.
You move User B’s mailbox to Forest B.
In this scenario, the shared data in the shared calendar is removed every second time that User A restarts Outlook. And it is re-synced
when User A browses to the Calendar module.
Unfortunately TechNet isn't coming back, sorry folks :-(
The 3 patches above immediately fixed the issue for me!
Thanks so much! -
Issue moving remote user from exchange 2007 to 2013
have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.
outlook was working connecting to both servers, and OWA was working on both servers.
couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
could this have caused my outlook connectivity issue?
I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
any suggestions?I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
Hi,
Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
Please try to logon OWA to check whether this user works.
If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
Please try to run Outlook under safe mode to avoid AVs and add-ins.
Thanks
Mavis Huang
TechNet Community Support -
Can only access emails through OWA after migration from exchange 2007 to 2013
can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
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ürgenHi,
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 -
Legacy Namespace for Exchange 2007 to 2013 co-existence
We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
Thanks in advance for your help.In coexistence with exchange 2013 and legacy version the request happens in 2 types.
For Exchange 2010 –
Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
For Exchange 2007 –
Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
Certificates:
All the required SAN entries for UM,webservices and activesync should be created.
Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
Exchange 2013 only then owa redirection will work.
You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
Existence.
Following change needs to be done in Firewall
External OWA URL should be directed to exchange 2013 Internet Facing CAS.
External EWS URL should be directed to exchange 2013 Internet Facing CAS.
External Autodiscover URL should should be directed to Exchange 2013 CAS.
External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
External UMvirtualDirectory should be directed to Exchange 2013 CAS.
Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
a mailbox on Exchange 2007.
External and Internal DNS settings
Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN
Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
address
The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server
Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
Authentication Settings:
This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
Set the owa virtual directory authentication only to Basic in exchange 2007.
In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
Things to check:
If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
Virtual Directories doesn’t have it configured.
If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
For further references you can refer my article below
http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP) -
Outlook 2013: Accessing Exchange with Outlook 2013 and OST on mulitple machines?
My organization recently transitioned to off-site Exchange servers. Users were upgraded to Office 365 / Outlook 2013 using OST files (PST files previously
In addition to my work laptop, I have Outlook 2013 available on a personal Surface Pro 3. I cannot find a definitive answer on whether it will be a problem to connect to Exchange via Outlook 2013 using an OST files from both the work laptop and personal
tablet. Will having OST files on separate machines create sync issues? I have access to Outlook Web Access on the Surface, but prefer the Outlook desktop application for quick actions and other tools.Hi,
Typically, when you use a Microsoft Exchange Server account, your email messages, calendar, and other items are delivered to and saved on the server. You can configure Outlook to keep a local copy of your items on your computer in an Outlook data file that
is named an offline Outlook Data File (.ost).
As what Amit says, there would be no issue configuring Exchange account from both the work laptop and personal tablet. The OST file is synchronized with the Exchange computer when a connection is available. It is synced from Exchange server instead of the
Outlook client from your first account computer.
For more information about Outlook Data Files (.pst and .ost), please refer to:
http://office.microsoft.com/en-us/outlook-help/introduction-to-outlook-data-files-pst-and-ost-HA010354876.aspx
Regards,
Winnie Liang
TechNet Community Support -
How to migrate from exchange 2007 to 2013 step by step tutorials please
Hi
I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
We have 800 mailbox in total
Our domain controllers are
Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
I currently only have 1 exchange server 2007, with all the roles on the one server. I would like to keep that same as
well with exchange 2013.
ThanksExchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
migration task in more secure way. -
Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'
I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227) Diagnostic
context: ...... Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN> Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 45169 StoreEc: 0x824
Lid: 50544 ClientVersion: 15.0.847.32 Lid: 52080 StoreEc: 0x824 Lid: 44273 Lid: 49064 dwParam: 0x1 Lid: 37288
StoreEc: 0x6AB Lid: 49064 dwParam: 0x2 Lid: 59431 EMSMDB.EcDoConnectEx called [length=203] Lid: 51239 EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 3460 Lid: 12696 dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1753 Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4 Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN> Lid: 12952 dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 59505 StoreEc: 0x824 Lid: 50544 ClientVersion:
15.0.847.32 Lid: 52080 StoreEc: 0x824 Lid: 36081 Lid: 51152 Lid: 52465 StoreEc: 0x80040115
Lid: 60065 Lid: 33777 StoreEc: 0x80040115 Lid: 59805 Lid: 52487 StoreEc: 0x80040115 Lid: 19778 Lid: 27970
StoreEc: 0x80040115 Lid: 17730 Lid: 25922 StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
JonAny update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required -
Hi Everybody. I have a weird one for you.
I have a user that gets an "operation failed" message whenever trying to use the "resend" option on any email (It's the one right under recall). I had tested up and down on her machine. Exchange 2010 Outlook 2013
Ran in safe mode, recreated her profile, disabled virus scanning, repaired office. (weird, the font just changed sizes on me)
After all of this I tested on other computers, other users seem to be able to "resend" just fine. However her account does not work on any computer I try, internal or external to the network.
It looks more like a profile issue.
She's a very active archivist, so she only has 486MB of space used by her mailbox.
It's well under quota.
It's been really puzzling me.
MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.netHi Timssims,
Since there is only one user in the org has this issue, it seems an issue on the Outlook client side.
I suggest asking Outlook Forum for help so that we can get more professional suggestions.
For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
However I also have some suggestions for your reference:
1. If this issue occur on Cached Mode, I suggest turning to Online Mode for testing.
2. Please also paste the detailed error message if "operation failed" is not the
complete information.
3. If still not works after perform operations above (including suggestions from Outlook Forum), I suggest re-creating a new mailbox for the specific user just as Martin suggested.
Thanks
Mavis
Mavis Huang
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.
ThanksHello,
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 have moved a handful of mailboxes from my Exchange 2007 server to my new Exchange 2013 server. When the users logon to Outlook, usually Outlook 2007 Pro, they have a new default Contacts folder and Junk Email folder that are empty. I
have to copy all the user's contacts into the new default folder and delete the old one. Not sure why this is happening. Any information would be appreciated. Thanks.Are you sure your Outlook 2007 is compatible with Exchange 2013?
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
http://support.microsoft.com/default.aspx?kbid=2687404
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
Outlook cannot connect after mailbox move from Exchange 2007 to 2013
I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
AutoDiscoverInternalRpcClientServer
[email protected]
AutoDiscoverHomeMdbDn
/o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
I've checked and rechecked everything and can't seem to locate my error.
Any thoughts? Thanks.Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
Exchange 2007 to 2013 Migration Outlook Anywhere keeps asking password
Hi all,
i'm migrating an Exchange 2007 Server with all roles installed on a Windows Server 2008 R2 to 2 Exchange 2013 SP1 Servers (1 Cas and 1 Mailbox) installed on Windows Server 2012 R2.
I installed Exchange 2007 SP3 RU13 for coexistance and everything was ok until i switched to the new 2013 CAS.
After that the client using Outlook Anywhere started asking for password.
I configured the Outlook Anywhere with these settings:
Exchange 2007:
OA Hostname mail.domain.com
Client Authentication NTLM
IISAuthenticathion Basic, NTLM
SSL Required True
Exchange 2013
OA Hostname mail.domain.com
Client Authentication NTLM (Both internal and external)
IISAuthentication Basic, NTLM
SSL Required True (both internal and external)
Before switching to 2013 Cas everything works smoothly and the Outlook clients receive NTLM as HTTP Proxy authentication.
After switching to 2013 Cas, test users migrated on 2013 Mailbox Server are ok, but Outlook users on Exchange 2007 Server get Basic as HTTP Proxy authentication and continue asking for credentials.
In the Exchange 2007 server i configured the host file to resolve servername and servername.domain.local with the ipv4 address to avoid issues regarding IPv6 with OA in Exchange 2007.
Using Microsoft Connectivity Test i receive the error "RPC Proxy can't be pinged - The remote server returned an error:
(500) Internal Server Error"
Any Ideas?
Thanks for your HelpRun this and post the result
https://testconnectivity.microsoft.com/
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Maybe you are looking for
-
What's the most efficient way to fade titles on & off
using the basic text generator. wondering if it's more efficient to fade a title on & off using opacity in the motion tab or using a dissolve from the effects menu applied to to the in & out point of the title. it's certainly a lot quicker just addin
-
Hi, I found an interesting tutorial (link) and created a working model, adapting it as needed. So far, when I center the container sprite and rotate it, it appears to first rotate from a 0,0 registration point, instead of from its center. I've tried
-
Abort the current sequence file
Hi, I have a main sequence file (with a number of test cases) calling another 2nd sequence file. I like to abort from my 2nd sequence file if a paremeter returned is certain value (e.g. parameter.result == "1") from TestComplete. What command can I
-
Is there any easier way to multiclip different aspect ratios without exporting footage?
I am using FCP Studio 3 and I have a 3 cam shoot with 3 different HD aspects - 1920x1080, 1440x1080 and 1280x1080 - is there a way to multiclip them without exporting and creating new clips?
-
Headcount for all months and dynamic formula in HR Module
Hi all, I am new to HR module, I had requrement like user will i/p from date and to date for calmonth based upon that i need to create a report i, and in the report i need to calculate the %attrition(leavers rate) I am uploading from a flat file an