Exchange 2007 / Outlook 2013 "Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable"

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!

Similar Messages

Outlook 2013: Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable

When I configure the Outlook profile manually then receive warning "Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable" when clicking "Automatic Replies (Out of Office)".
However if I use Autodiscover to configure the Outlook profile the above does not occur and "Automatic Replies (Out of Office)" works fine.
Client: Outlook 2013 Click-to-Run version 15.0.4551.1011 on Windows 7 Pro SP1.
Server: Exchange 2007 SP3 on Windows SBS 2008 SP2.

Hi,
First of all, please make sure you have installed this Outlook 2013 hotfix package (December 10, 2013):
http://support.microsoft.com/kb/2825652/en-us
It may fix the issue.
If the hotfix doesn't help, please note, this problem can occur after your primary SMTP address changes. The problem occurs because your previous primary SMTP address is cached in the Windows registry under your Outlook profile and this information does
not get refreshed for 24-48 hours after the SMTP address change.
So please make sure you have configured smtp address correctly, or, we can find some workarounds from the link below:
http://support.microsoft.com/kb/2693800/en-us
Regards,
Melon Chen
TechNet Community Support

Outlook 2010 "Your automatic reply settings cannot be displayed because the server is unavailable" error

Hi,
We recently introduced a Exchange 2010 server into our Exchange 2003 enviroment but had to stop migrating users over to it after it became appartent that users using Outlook 2010 could not switch on their Out Of Office, getting an "Your automatic reply settings
cannot be displayed because the server is currently unavailable" error. However users on the new 2010 can set OOF if they use OWA or Outlook 2003!
Running the Test E-mail AutoConfiguration shows no errors with the Log tab showing Autodiscover succeeded and the Results tab showing all the correct values, including a OOF URL of
/Autodiscover/Autodiscover.xml">https://<servername>/Autodiscover/Autodiscover.xml into IE gives a XML file with a 600 error code.
I have looked at loads of 'solutions' on the Internet but cannot get this working, anyone have any suggestions?
Thank you,
Craig

Please verify IIS
settings:
======================
On Exchange CAS
server, open IIS console,
Go to default web site, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Click Autodiscover, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Click EWS, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Click OAB, double click “SSL
Settings”, make sure Client Certificates is set to “Ignore”
Please run IISRESET command to load the changes.
Thanks.
Tony Chen
TechNet Community Support

Out of Office error: 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.'

Hi,
This is my first post in the forums. Please forgive me if it's in the wrong category or if it's not posted correctly in any way.
I'll try and give you below as much information about the problem we have here as I can.
What we have:
- an on-premises Windows 2012 Standard server that is the PDC, DNS and DHCP server;
- a second Windows 2012 Standard server with the sole purpose of hosting our Exchange 2013 CU7 server;
- Windows 7 PCs with Office Home and Business 2010 v.14.0.7143.5000 (32-bit);
- Outlook 2010 connects through Outlook Anywhere (mail.ourdomain.com).
The problem:
If trying to set up Out of Office through Outlook on the client PCs, we'd get an error message: 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.' Interestingly, it does work normally for some users.
It works fine for all users if done through OWA.
Tests performed:
User 1 on PC1 has the problem. User 2 on PC2 doesn't have the problem. Both users are members of the same security groups.
- setting up User 2 on PC 1: the problem exists;
- setting up User 1 on PC 2: the problem exists;
- setting up a second Outlook profile on PC2 within User 2's domain account (the one that works), for the same User 2: the problem still exists!
I haven't been able to set up an Outlook account that works since this issue was discovered, although there are existing Outlook accounts that do not have the issue.
Let me also point out we have another issue we are working on and which may or may not be related: the Autodiscover function in Outlook doesn't work. Test E-mail AutoConfiguration results in 'Autoconfiguration was unable to determine your settings!'.
I can see postings in the Internet of other people having the same problem with OoO, but couldn't see a solution that fits my case: some existing accounts in Outlook are fine, other are not and newly created profiles of aforementioned working accounts do not
work. The majority of the articles/threads I read suggest recreating the Virtual Directories in Exchange, but we did that just a month ago (when troubleshooting the Autodiscover problem) and besides if the problem is in the Virtual Directories, I would expect
it to affect all accounts.
Any help in resolving this problem would be greatly appreciated. Please let me know if you need other details.
Apologies if the posting is not in the right place or not done properly - I'm still learning.

The IIS log files on the CAS might tell you something. Depending on how your proxy server handles NAT the IP address of your connection might be from the proxy server instead of your client.
In any case, a tool like Fiddler (http://www.telerik.com/fiddler) can be extremely helpful in working on problems like this because it can decode the SSL traffic on the client and you can see what's being sent
and what's being received.
Another thing to check (although it's unlikely to be your case) is whether or not your browser (when you try connecting to the autodiscover URL) thinks it's in the "Internet" zone. the "Local intranet", or at a "Trusted" site.
The domain names you use on machines on your LAN should be excluded from being proxyed. Anything with "." in the name will be set, unless excluded, to the proxy server.
Is the time correct on the client machine? Is it more than 5 minutes different to the Exchange machines and domain controllers? That'd be something that would cause Kerberos to fail.
A certificate can be a problem if its expired or if it doesn't have the correct names. But I wouldn't worry about the uglog.com domain just yet. Until you get the Autodiscover working with the SCP you have bigger problems.
If you've never used a WPAD file then don't worry about it. It's very useful if you have a complex network and you want to manage how browsers connect to servers. For example, if you have multiple proxy servers the each manage a different set of names, an/or
if some names should bypass proxy servers entirely and just connect directly. If run a strictly Microsoft network with only Microsoft product that you can manage with GPOs (and you can enforce those GPOs on every machine -- even the BYOD ones) you probably
don't need a WPAD.
--- Rich Matheisen MCSE&I, Exchange MVP

Automatic reply settings cannot be displayed (O365 -Exchange 2013)

Good afternoon,
I am currently having a problem with one employee who uses the automatic replys when he is away from work.
The error I get when trying to turn his replies on or off from outlook 2013 is "your automatic reply settings cannot be displayed because the server is currently unavailable. However I can have him log into OWA from his phone and web browser where he can
enable to disable the settings. But I need him to be able to do this quickly from his computer.
Ive done quit a bit of research and below are the things Ive tried.
- Checked Exchange 2013 and user profiles nothing setup there.
- Check for Windows Update KB2837618, it is not installed.
- Deleted profile from mail settings from control panel.
- This is an internal connection to the server and his machine is setup just like everyone elses. But yet he is the only user who is having problems.
- We just upgraded to 2013 exchange about 2 months ago, and we just updated from office 2010 to office 365 about 2 weeks ago.
Anyone who is able answer this question thanks in advance!

From the user machine, can you confirm that he is able to access the out of office config URL?
Should be something like;
https://external.fqdn/ews/exchange.asmx
You can find it by running the 'The E-mail AutoConfiguration' tool by CTRL+RightClick on the Outlook icon in the system tray.

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

Microsoft Outlook 2010 & 2013 cannot set automatic reply settings

Hello,
We cannot seem to set automatic reply's within outlook 2010 & 2013. We have an exchange server 2010. We
can setup automatic reply through OWA absolutely fine. The error that we receive is 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.
However we can setup out of office on any other office version below 2010 fine. We have run through
a number of tests and have come to the conclusion that the auto discover service is not configured correctly. I have been told to run through the following
"We need to make sure the IIS service is assigned to the certificate which includes mail.mydomainname.co.uk
name:
Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services
POP,IMAP,SMTP,IIS
Then restart IIS service
to apply the changes.
If the user is connect
to mailbox from external environment as your test results, it is recommended to add the autodiscover.mydomain.co.uk name in your certificate with IIS service. If so, the autodiscover
service can be accessed successfully in your posted second steps(https:/autodiscover.mydomain.co.uk/autodiscover/autodiscover.xml). Alternatively, if you don’t want to change your certificate configuration, we need to create a new SRV record for mail.mydomainname.co.uk
to make your autodiscover succeed in last steps of Srv Record lookup method".
So I followed this and opened Exchange Managemnet Shell and ran the following.....
'Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services POP,IMAP,SMTP,IIS'
The following output was displayed:
"VERBOSE: Connecting to SERVER2011.EXCHANGE.local
VERBOSE: Connected to SERVER2011.EXCHANGE.local.
[PS] C:\Windows\system32>Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services POP,I
MAP,SMTP,IIS
WARNING: This certificate will not be used for external TLS connections with an FQDN of 'SERVER2011.EXCHANGE.local'
because the CA-signed certificate with thumbprint '71ADF367E190E269C1036BBF4A09C55E62536791' takes precedence. The
following receive/send connectors match that FQDN: Default SERVER2011.
WARNING: This certificate will not be used for external TLS connections with an FQDN of
'mail.companyname.co.uk' because the CA-signed certificate with thumbprint
'67ECB1A383CBD05424C58F6A5E753C9377F49D3D' takes precedence. The following receive/send connectors match that FQDN:
Windows SBS Internet Receive SERVER2011, Fax/Printer.
Confirm
Overwrite the existing default SMTP certificate?
Current certificate: '67ECB1A383CBD05424C58F6A5E753C9377F49D3D' (expires 09/08/2015 09:06:17)
Replace it with certificate: '62C247B3BD081D0A8B074D4A928A76E6DA3BABBA' (expires 06/08/2015 17:05:22)
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):"
I opened up 'Internet Information
Services (IIS) Manager to find 2 Server Certificates issues to 'mail.companyname'
with the certificate hash' 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA' and '71ADF367E190E269C1036BBF4A09C55E62536791'.
I opened up the Exchange Management
Console to confirm that the IMAP, POP, IIS, and SMTP services are bound to both of the certificates for 'mail.companyname'.co.uk
I need to know if it is okay to proceed in replacing the certificate and running this
command.
Thank you

Hi,
We have this problem with some of our users, in that they get the server unavailable error when trying to activate the out of office.
In our case this is because the Proxy is blocking the connection from the PC to the Exchange, so we just go to Internet Options - Connections - LAN Settings - Advanced (under proxy server) then just add *.domain.com into the Exceptions box at the bottom.
This seems to resolve the issue and allow them to set their out of office. The only reason this reoccurs for these users is because their roaming profile for some reason won't save the proxy settings, which is a different issue.
Hope this helps.

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.

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

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)

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

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

Exchange 2007 to 2013

hello
i am trying to migrate exchange 2007 to exchange 2013 but what a bout spam filtring feature which installed in hub and cas server
how can i enabled in exchange 2013 and copy all configuration
what a bout accepted domain how can i migrate it ?
Receive connectors ? how can i migrate it?
MCP MCSA MCSE MCT MCTS CCNA

I see a lot of confusion here - both in the way the questions are asked, and in the incorrect and misleading answers.
The anti-spam feature in Exchange 2013 is performed by the Connection Filtering agent. It is not available in the Exchange 203 CAS or MBX roles. Exchange 2013 SP1 re-introduced the EDGE server role (about a year and a half after the RTM) and the
missing connection filtering agent (the anti-spam feature or module as DareDevil says).
Hence, you have the following options:
1. Install and configure an Exchange 2013 EDGE server.
2. Install a 3rd party Anti-Spam product.
3. Use the Anti-Spam services of an external company - all inbound e-mail should go through the servers of this company.
4. Install and use a linux server in the DMZ for the Anti-Spam filtering (that works amazingly well, and you'll be surprised how many companies are using this option).
As a matter of fact, Yasser, you've asked four questions, not just one. The accepted domains, that are already configured in you existing Exchange 2007 organization, are configured automatically on the Exchange 2013 servers - you don't have to perform this
task manually.
Depending on your deployment - [CAS+MBX] or separate [CAS] and [MBX] servers, you'll have the minimum required receive connectors configured as well. If you have custom receive connectors, you'll have to re-create them manually. The same way, if you
have custom transport rules,you'll have to export/import them manually as well.
You'll have to create manually the Exchange 2013 Internet send connector(s) or add the Exchange 2013 CAS to the existing one(s).
By default, the Anti-Malware feature is enabled when you install Exchange 2013, but if you are planning to use a third party product, you can disable it.
Step by Step Screencasts and Video Tutorials

Exchange 2010 / Outlook 2013 - Mailflow Issues

Hi everybody,
Some time ago I've configured a SBS2011 server for one of my customers.
The SBS2011 has exchange and sharepoint, these services work fine.
The exchange server is only being used for the calendars, no e-mail flow.
The company uses IMAP through an external hosting-server.
So in Outlook 2013 we configure 2 accounts, one exchange account and one IMAP account.
Configuring the clients isn't a problem, and all seems fine, the calendar works.
But when the e-mail flow starts, users wil receive the same email multiple times and it seems the system is in a loop. E-mail flow will stop or the users get the same e-mails multiple times.
I've checked multiple solution regarding Win8+Outlook 2013 and IMAP, (issue about an update and setting the right root folder), but nothing seems to help.
We installed Outlook 2007 on the clients and configured them with both of the accounts and the system works like a charm! E-mail and the calendar are working like it should.
But the company bought about 20 Office 2013 licenses, so we need to get this to work on the new Outlook.
I don't think there is a problem in the Exchange Server, but in Outlook 2013, possible because both of the accounts share the same OST file.
Does anyone know how to solve this problem? Been running my mind for months.
With kind regards,
Tim Grave

Hi,
This doc may help you a lot.
http://office.microsoft.com/en-in/outlook-help/introduction-to-outlook-data-files-pst-and-ost-HA102749465.aspx
Install Only one Outlook Ex :- Outlook 2007 / 2010 / 2013
And if you want to create a *.pst file you need to go to
1. File > Account Settings > Account Settings.. > Data Files > Add > Create a new PST as you want.
Regards, Koustov Choudhury

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.
Thanks

Exchange 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.

Exchange 2007 / Outlook 2013 "Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Unavailable"

Similar Messages

Maybe you are looking for