Window 8.1 lost connectivity to Exchange 2013 (started today)

I've done a few searches for the errors we are getting, but things that I have tried (corrupt user profiles, registry edits on the client pc, etc) have all been unsuccessful.
Our environment mainly consists of Windows 7 machines.  We have three Windows 8.1 machines (there are only three on our network) that we have been testing with before we roll them out.  These Windows 8.1 machines have been talking to Exchange 2013
for months (since our roll out in Summer 2014).  One Windows 8 machine is connected to the domain, the other two are not.  Starting today, all three computers have started prompting for passwords.  Nothing has changed (no patches/config changes,
etc) on the server and its last reboot was three weeks ago.  The Windows 8.1 machine that is joined to the domain has Office 2007.  The Other Windows 8 machines have Office 2013.  We have many Windows 7 machines running both Outlook 2007 and
2013 with no problems at all.  
The user account can log into OWA.  We can set up the profile on a Windows 7 box with no problem.  The only common thing is Windows 8.1.  iPhones/iPads/Android devices still work, too; with the tested user account (three accounts).
I ran through most tests on the Microsoft Connectivity Analyzer and everything passes.  
I've turned on Outlook logging, but since it doesn't get past authentication, the logs really do not help much (if I'm looking in the right "outlook logging" folder under the AppData/temp directory.
I've tried looking at the HTTP logs on the exchange server, but they do not seem to point me in a direction.
I'm grasping at straws and not sure what to look for next.  I'm going to install patches on the Exchange Server this weekend and reboot it, but I'm really thinking something on the Windows 8.1 client is causing the issues.  Any thoughts or directions?
Regards,
JA

Hi,
According to your description, I noticed that the issue only happens to three Windows 8 and Windows 8.1 users. And the issue doesn’t occur when setting up the problematic user’s Outlook profile on a Windows 7 machine.
If that is the case, the configuration in Exchange server side should be OK because the client user can connect to mailbox in Windows 7 machine. Please check the following settings in Windows 8 machine:
a. Start Microsoft Outlook.
b. Click File > Account Settings, click Account Settings.
c. Click the E-mail tab, click the Exchange account, and then click Change.
d. Click More Settings, and then click the Connection tab.
e. “Connect to Microsoft Exchange using HTTP” should be checked, then click Exchange Proxy Settings.
f. Note the checkbox for fast network and slow network should be both checked:
g. Make sure the Proxy authentication settings is set to NTLM Authentication.
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]
Winnie Liang
TechNet Community Support

Similar Messages

  • Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

    Dear All,
    I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
    The 2013 environment are:-
    2 X CAS server with MS NLB configured
    2X MBX server with DA
    Internal NLB/licent access: excas2013.int.my.domain
    External access (current set on 2010 as well): webmail.my.domain
    Certificate with valid subject name has been import to 2013 and 2010:
    CN: webmail.mydomain
    SAN: excas2013.int.my.domain
    SAN: excas.int.my.domain (for 2010)
    I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
    the process looks good:-
    Establish network connection (checked)
    Searching for [email protected] server settings (checked)
    Log on to server
    The process stop at "Log on to server" and a windows prompt, saying:
    The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
    Clicked OK, I can see:-
    MS Exchange Server:
    [email protected]
    Mailbox:
    =SMPT:[email protected]
    WHen I click "Check Name", it said The name cannot be resolved.
    I have no idea of what is going on. Just want some help~

    I have checked the iis log:-
    2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
    2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
    15
    2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
    2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
    2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
    2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
    80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 64 78
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 109
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 64 15
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 31
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 0 15
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 46
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 0 31
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 46

  • Unbale to install November update on Outlook 2007 SP3 for connecting to Exchange 2013

    Hi
    I was trying to upgrade my outlook 2007 clients for connecting to Exchange 2013 environment. First I have installed Office SP3 (kb2526086). Outlook version after that is 12.0.6607.1000. Later I  tried to install nNovember 2012 update which is a
    prerequisite for connecting to Exchange 2013 clients (support.microsoft.com/kb/2687404/en-us) but it shows me a message "Expected version of the product was not found on the system". No idea  how to proceed now, expecting help.

    I recommend that you post this in the Outlook Forum:  http://social.technet.microsoft.com/Forums/en-US/outlook/threads
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • 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
    thanks

    Hi,
    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

  • Outlook 2007 SP3 can't connect to Exchange 2013

    Outlok 2007 with latest hotfixes
    Freshly migrated mailboxes
    Gives the error 
    Can't open outlook-The set of folders cannot be opened
    Cert has internal FQDN name. Encryption is disabled
    Any pointers?

    Does the certificate have the server name?
    That was apparently the solution here:
    http://social.technet.microsoft.com/Forums/exchange/en-US/1ae67f48-d1ba-44b5-a3c7-4e9a5e955f3e/outlook-2007-cannot-connect-to-exchange-2013?forum=exchangesvrclients
    Please 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.

  • Outlook 2010 connected to Exchange 2013 prior to coexistence

    I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config).  I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning).  Why would Outlook connect to the new
    Exchange 2013 server like that?  Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

    Hi,
    By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
    According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
    If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
    I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
    Thanks
    Mavis 
    Mavis Huang
    TechNet Community Support

  • Connecting to Exchange 2013 Server and Server name is weird

    Hello
    When I connect to my Exchange 2013 Lab Server with a Outlook 2010 Client something shows wrong.
    The Name of the Exchange server that I type in changes from EX01 to !"¤"&#/25278596"&¤%/¤%/.
    What can be the problem?

    Hello
    When I connect to my Exchange 2013 Lab Server with a Outlook 2010 Client something shows wrong.
    The Name of the Exchange server that I type in changes from EX01 to !"¤"&#/25278596"&¤%/¤%/.
    What can be the problem?
    Are you sure that you don't see something like this: [email protected]
    That is what you should see when connecting to Exchange 2013.
    Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of
    mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP address.
    See:
    Whats new in Exchange 2013 - Architecture section.
    Martina Miskovic

  • On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

    I have a new install of Windows 2012.  I have two physical servers.  One is a W2012 std Domain Controller ("DC").  The Second is configured as W2012 HyperV  ("HV").  Under HV I have
    two VMs.  One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS").  All systems are behind a firewall appliance.  Exchange is working via Outlook and OWA internally and externally.  The self
    created SSL must be installed manually on external machines since it comes up as an untrusted certificate.  Once installed remote outlook works and OWA works.  I have configured the terminal server and I am able
    to login remotely as various users under my "TS group".  The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
    on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
    for alias@ domain, then fails the logging on to the mail server)  The error reads:  "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."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC.  I have
    tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command.  I have also tried to use the guid via "Get-Mailbox
    ALIAS | fl name, exchangeguid.  Keep in mind all desktop users on the network are connecting to Outlook without issue.
    I would appreciate any thoughts on solving this issue.

    Hi,
    According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
    Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
    open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
    Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
    autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook clients on Windows XP not connecting to Exchange 2013

    Previously outlook on XP machines were working fine with a SAN certificate having the mail.company.com as common name. Since we're moving to Exchange Hybrid we reissued  the certificate and made company.com as the common name after that change all Outlook
    on XP machines are not able to connect to the Exchange 2013. It is always asking for password. Outlook clients on windows 7 and 8 have no problem. 
    I wanted to run the below commands but I'm worried that it may break the connections of the Windows 7 and 8 machines:
     Set-OutlookProvider
    EXCH -CertPrincipalName msstd:mail.XXX.com
      Set-OutlookProvider
    EXPR -CertPrincipalName msstd:mail.XXX.com
    Is it safe to run the commands or I should just reissue again the certificate and make the mail.company.com as the common name? Will there be any issues with Exchange 2013 hybrid if I do this?

    I just reissued the certificate and all Outlook on windows xp are working now.

  • Lync 2013 on Windows Phone 8 cannot connect to Exchange via TMG

    Hi,
    I've found that the latest Lync 2013 client on WP8 cannot connect to our Exchange Server 2010 via TMG and the problem is related to autodiscovery. Based on detailed log analysis the symptom is the following:
    1. The client is sending a request:
    GET
    https://autodiscover.neostratus.com/autodiscover/autodiscover.xml
    2. It gets a TMG logon form and then tries to POST here:
    POST
    https://autodiscover.neostratus.com/cookieauth.dll?getlogon?curl=z2fautodiscoverz2fautodiscover.xml&reason=0&formdir=9
    <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
    <Request><EMailAddress>[email protected]</EMailAddress>
    <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>
    </Request></Autodiscover>
    </SentRequest>
    The URL is wrong and it fails of course. This is the situation with Lync credentials and manually configured Exchange credentials as well.
    Other clients (PC, iOS) can connect fine and all test tools confirm that our autodiscovery setup is correct. I can POST the above XML using basic authentication to the correct URL and get a correct response. And the same autodiscovery process works fine
    when setting up an email account on the same WP8 device.
    Is this a known WP8 Lync 2013 client bug and is there a workaround?
    BR,
    Andras

    Hi,
    The lync client should be able to sing in Lync Server and just lost calendar information if Lync client cannot connect to Exchange. Please double check if the device is able to connect to the EWS URL.
    Kent Huang
    TechNet Community Support

  • How can I script out automatic mail profile connection to Exchange 2013

    We use a program called Desktop Authority 9.1 that is a fully featured kixstart based logon user profile customization tool.  It does a full gamout of things like map drives, folder redirection, import registry edits, run silent application installers,
    and of course create the Outlook profile.
    There's no issues with this tool creating an outlook profile internally to mail.domain.com, and even detecting laptops and configuring it for outlook anywhere to webm.domain.com and cached mode.
    Issue I'm having is trying to roll out Exchange 2013.  This tool simply does not seem to create the mail profile.  On a test computer I have the hosts file pointed to the new 2013 server from these names: webm, mail, autodiscover.  At log
    on I simply get an error "The name cannot be resolved.  The name cannot be matched to a name in the address list."  When you click OK you get a little confusing dialog box with the exchange server name: mail  and the mailbox: windows
    user ID.
    So I tried to do this manually in the Mail (32-bit) control panel applet.  It doesnt matter if I put in mail, mail.domain.com, webm, webm.domain.com, email (the netbios name of exchange 2013), etc.. I get the same error.  I went into More settings
    > Connection > connect to microsoft exchange using HTTP and in the proxy settings I have webm.domain.com, connect SSL Only, only connect to proxy servers that have the name: msstd:webm.domain.com, and the rest is checked and NTLM Authentication is checked.
    I simply CANNOT manually create an outlook profile at all.  I can surely delete this one, start outlook, click next through the wizard taking all the default options and get Outlook configured that way (via Autodiscover service), but I need a way to
    do it manually so I can have Desktop Authority do it manually.  Why?  Two major reasons:
    1.  If our end users are greeted with an Outlook startup wizard every time they go to a different computer, and have to click next through it, our help desk is going to be overwhelmed with "what is this outlook startup wizzard?" questions.
    2.  Desktop Authority also attaches additional mailboxes.  We need the outlook profile passed through DA's scripting so different users departmental voice mailboxes are attached in their outlook.  IE) Mailbox VM_FAX_Accounting is attached
    to all of the accounting associates Outlook.

    Ok I found another way to get autodiscover to work..
    In Group Policy go to User Configuration > Administrative Templates > Microsoft Office 2010 (and 2013 in my case) > Miscellaneous > Suppress recommended settings dialog > Change to ENABLED.
    Now go to User Configuration > Administrative Templates > Microsoft Outlook 2010 (and 2013 in my case) > Account Settings > Exchange > Automatically configure profile based on Active Directory Primary SMTP address > Change to ENABLED.
    Now for the shared mailboxes,  I guess when we plan to migrate a department, their shared mailbox MUST be migrated from 2007 to 2013 on the same evening, and then we must go into that shared mailbox and ensure each individual user has "Full access
    permissions" to it.
    Now in Desktop Authority we publish this reg file: 
    Windows Registry Editor Version 5.00
    [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers]
    "autodiscover-s.outlook.com"=hex(0):
    "autodiscover.outlook.com"=hex(0):
    "autodiscover.domain.com"=""
    [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers]
    "autodiscover-s.outlook.com"=hex(0):
    "autodiscover.outlook.com"=hex(0):
    "autodiscover.domain.com"=""
    [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover\RedirectServers]
    "autodiscover-s.outlook.com"=hex(0):
    "autodiscover.outlook.com"=hex(0):
    "autodiscover.domain.com"=""
    Why that?  Well it turns out further testing when I added full permission to a new 2013 test shared mailbox, yet another nag screen was presented in Outlook which states "Allow this website to configure [email protected] server settings?  autodiscover.domain.com/autodiscover/autodiscover.xml
    - Your account was redirected to this website for settings.  You should only allow settings from sources you know and trust.  (Allow) (Cancel).  If end users see this, you can bet our helpdesk calls will be out of control.  We undergo security
    awareness training and they will question ANYTHING resulting in redirect or dialog boxes asking about trust, and really that's a good thing.
    That registry should I think handle Outlook 2007, 2010, 2013, and we will just have to maintain it for future versions.
    We maybe have, I dont know less than 5 Outlook 2007 installs and they are on spare laptops, so If I want to cover it all I just have to download the Office 2007 ADMX templates for Group Policy so I can change those two settings above as well.
    The other way I thought was to use powershell and script something out to pull from Exchange the GUID, append the @domain.com and put that into a variable that our Desktop Authority application can plug in at startup.  But thats a little too much custom
    programming whereas I think using GPO's and documented registry keys may be a better fit.
    I just have to do testing to figure out what's going to happen to the users profile if it already exists on 2007, then its migrated to 2013.  Will it be deleted?  Will they lose all of their signatures?  I know for many on network
    PC's they will be going from direct mapi connection to Cached mode.  Is that a good thing?  I would imagine less load on the server and network once the mail is downloaded.
    We would plan on a slow migration on a departmental basis.  Luckily our departments have their own user OU's so applying this group policy can be done in the same manor.

  • Connection beetween Exchange 2013 with outlook client 2007 SP3

    Hi All,
    My company reinstall exchange 2013 when the previous mailbox DB error. When I implemeted a new server. I configured step by step carefully. if we use outlook 2010 connect to exchange server, send/receive work normally. But someone, uses outlook 2007 SP3,
    they have somer error. They work with "cached mode", the connection from outlook to exchange server connected normally, but mail items sometime disappear in outlook client, when i check in the OWA, the mailbox item appear on this. 
    I tested with "online mode", the mailbox items push into outlook.I switched to "cached mode", this items haven't in outlook. Everybody who's meet the problem, please help me the solution can resolve the problem? Many thanks.
    Quoc Dao

    Hi,
    Would you please let me know edition information of the Windows Server? Is it a Windows Server 2012, Windows
    Server 2012 R2 or other?
    On current situation, please refer to following KB and check if can help you.
    Sometimes e-mail messages do not appear in your
    Cached mode Inbox even though they were synchronized down from your mailbox
    By the way. Based on your description, this issue seems to be more related to Outlook 2007. If this issue still
    exists, I suggest that you should post in
    Outlook forum. I believe we will get a better assistance there.
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Unable to connect to Exchange 2013 by the PS Script from Win 8.1

    Good day to all
    There is the  corporate Exchange 2013 server in main office  and  local Windows 8 (and 8.1 too) and Windows 7 Enterprise workstations in regional office in one AD domain.
    I am local admin in this regional office and one of my duty is work with my part of Exchange accounts. So I do it with PowerShell Win ISE environment .
    I make initial connect to Exchange server by this script (running in Win ISE with admin rights)
    $UserCredential = Get-Credential
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://exchange.server/PowerShell/ -Authentication Kerberos -Credential $UserCredential
    Import-PSSession $Session
    On Windows 8 WS it issued an error with a such strange message :
    New-PSSession : [exchange.server] Connecting to remote server exchange.server  failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually
    returned by a HTTP server that does not support the WS-Management protocol.
    But if I try to run this script on Windows 7 Ent workstation in a same environment (Win ISE) I  havent got any errors and I can to connect with corporate server.
    All of these workstations (Win 8, Win 7 ), have got  same versions of PS (4.0) .  There is no firewalls between server ans workstations . Local firewall on Win 8 WS disabled .
    Because I am local admin  I can't  rule by the  Exchange Server console, accordingly to corporate policy. I cant reach it anymore . But I think that problem is deep in Win 8 settings.
    So why I can't connect to ES from Win8 ? Any help would be appreciated .
    Thanks again.

    Hi,
    Since it works fine with same command in Windows 7, this issue may be caused by Windows 8.1 client side.
    According to the error message, I find an blog for Exchange server side. For your reference:
    http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
    Just in case, please open IIS manager and switch to Default Web Site. Right-click Default Web Site, and then click Edit Bindings to double check the configuration for HTTP:
    1. Make sure the value of Hostname is empty.
    2. Ensure the port is 80.
    For your question, I have test this command in Windows 8, it works fine.
    Is there any extra software installed on it? please try to run Windows with clean boot, also we can try this within a new Windows.
    Besides, please try to telnet port 5985 and manually open this port in firewall ports.
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Iphone user can't connect to Exchange 2013

    Hi there,
    i have Exchange 2013 on Windows 2012, PKI and certificate installed.
    I have 4 users that can (must) connect to the server through iPhone. It works for all, except for ONE (the boss :-X)
    I deactivate the mailbox, recreate it without import old mails. It still don't work.
    Any idea?
    Thanks.

    Yes it's the first time on Exchange 2013.
    Yes they have different OS.
    The server just been installed so it never worked.
    BUT I SOLVED MY PROBLEM with this article:
    http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx It concerne Exchange 2003 and 2010 but it worked for my configuration: Windows 2012 and Exchange 2013 and no error HTTP 500.
    Actually my user is member of Administrators group and the inheritance is deactivate. I activate it and it's work!
    Thanks to me and thanks to you for your answers!

  • Connect to Exchange 2013 using IMAP/SMTP from the Internet

    Hello,
    I would like to enable connectivity to my exchange server using imap and smtp. my exchange server is using the default configuration for imap and smtp which are port 143 and 25 respectively. I have two exchange servers both with CAS and MB roles
    installed. I also have an edge server on my DMZ. I have also published my OWA using IIS ARR module. I wonder where I should direct my traffic from my firewall to enable IMAP connectivity taking into considerations my two servers with CAS and MB roles are inside
    my network. I also wonder how I can enable redundancy for IMAP connections. Thanks a lot.
    Regards,
    Pooriya
    Pooriya Aghaalitari

    Hi Pooriya,
    When you install Microsoft Exchange Server 2013, IMAP4 client connectivity isn't enabled. We can do the following steps to configure it:
    1. Start two IMAP services: the Microsoft Exchange IMAP4 service and the Microsoft Exchange IMAP4 Backend service.
    Set-service msExchangeIMAP4 -startuptype automatic
    Start-service msExchangeIMAP4
    Set-service msExchangeIMAP4BE -startuptype automatic
    Start-service msExchangeIMAP4BE
    2. Make sure there is an valid certificate which is assigned with IMAP service. Also confirm the Published Exchange server name (For example: mail.domain.com) has been included in this certificate:
    Get-ExchangeCertificate | FL
    3. Configure the external IMAP connection settings:
    Set-ImapSettings -ExternalConnectionSetting {mail.domain.com:993:SSL}
    4. Configure SMTP settings:
    Get-ReceiveConnector "*\client Frontend*" | Set-ReceiveConnector -AdvertiseClientSettings $true -Fqdn mail.domain.com
    5. You must restart IIS service (running IISReset /noforce from the Command Prompt window) after applying all settings.
    For more information about IMAP in Exchange 2013, please refer to:
    http://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
    Regards,
    Winnie Liang
    TechNet Community Support

Maybe you are looking for