Exchange 2013 mailboxes not accessible in outlook

Hi,
In the middle of migration from one exchange 2010 server to 2013 server and thought things were going well.  However migrated mailboxes to exchange 2013 are not accessible through outlook although they are through OWA most of the time.
I ran test connectivity comandlet on 2013 server on mailboxes and they tested okay.
However when you connect to mailbox it says exchange unavailable.  
I have a new ucc certificate on the exchange 2013 server that includes mail.contoso.com and autodiscover.contoso.com.  These are both setup to point to 2013 server with split brain dns.  The 2010 server has a certificate for mail.contoso.com.
The SC for autodiscovery right now for both the exchange 2010 and 2013 servers are https://mail.contoso.com/autodiscover/autodiscover.xml
When I run outlook connectivity test I get the following failure: 
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exg:6004.
The attempt to ping the endpoint failed
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 24085 ms
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exg:6004.
The attempt to ping the endpoint failed.
 <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl07_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 24085 ms

Hi
Did you migrate your DNS to point to the new Exchange 2013 Server?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

    Hi,
    We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
    Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers.  Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
    When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
    problems or the Exchange server is down for maintenance".
    Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM.  Everything is setup as per the Tech-net recommendations.
    Checked both these articles but still it is not working:
    http://support.microsoft.com/kb/2839517
    http://support.microsoft.com/kb/2834139
    Please let me know if there are any other ideas.
    Raman

    Hi,
    I recommend you refer to the following articles to troubleshoot the issue:
    Troubleshooting Mailbox Auto-Mapping : Autodiscover
    Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
    correctly
    Troubleshooting Mailbox Auto-Mapping : Permissions
    When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
    are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
    Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 mailbox takes a long time to connect with Outlook 2010

    We just installed a 2013 CAS/Mailbox server in our Exchange 2007 environment and are running in coexistence while we migrate users over. So far I have only moved one 2007 mailbox over, a new account used for testing. Everything is working fine, OWA,
    ECP, ActiveSync, etc... When connecting Outlook to a 2007 mailbox autodiscover takes a couple seconds and Outlook opens fine. The problem is when connecting Outlook to a mailbox on the 2013 server. Autodiscover takes about a minute before it finally finds
    the settings and the mailbox takes about 30 seconds to open everytime. It generally times out, I click retry and the mailbox opens. Once in everything is good but the initial loading always takes a long time, double the time when opening Outlook with a shared
    mailbox attached. All autodiscover is autodiscover.domain.com, Exchange 2007 is all legacymail.domain.com aside from the components that need to point to 2013. We do not have any certificate issues, well that's not true, at some time in the last couple years
    someone applied a 3rd party cert to our domain.com root but not sure if that would cause this issue. Also, these are internal clients we are trying to get going with the 2013 mailbox, not external. I just applied a registry change that helped someone else
    out there by disabling IPv6 for all components but that did not work for us MS KB929852. Any suggestions? Right now I am thinking of changing the internalURI for autodiscover to the FQDN of the server but wanted to see if anyone had any ideas.
    Jeremy

    Hi Angela, thanks for the response. I cannot post links or pictures as my account has not been verified?
    The autoconfiguration tests passed, I will paste the xml below. Ping times were all under 1ms. When I entered the IP for the 2013 serve I received errors that the connection to Exchange is unavailable followed by another one that the name cannot be resolved.
    I did this test by removing the Outlook profile and creating one manually without Autodiscover. I am able to ping the server by all names from the command prompt. 
    Our autodiscover.domain.com points to our 2013 server and the name is resolvable both internally and externally. Our certificates cover the internal server name fqdn as well as external names. I am doing all testing in the internal network.
    Pinging 2013server.fqdn.com [172.16.xx.xx] with 32 bytes of data:
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Reply from 172.16.xx.xx: bytes=32 time<1ms TTL=127
    Ping statistics for 172.16.xx.xx:
        Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    <?xml version="1.0" encoding="utf-8"?>
    <Autodiscover xmlns= removing link for post, points to the schema . microsoft . com ... 2006
      <Response xmlns= removing link for post, points to the schema . microsoft . com ... 2006a
        <User>
          <DisplayName>2013user</DisplayName>
          <LegacyDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=91d6299a8d1440e6b80fcc854dc3f860-2013user</LegacyDN>
          <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
          <DeploymentId>565c12be-83dc-44c7-a843-37b9bf26b9db</DeploymentId>
        </User>
        <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <MicrosoftOnline>False</MicrosoftOnline>
          <Protocol>
            <Type>EXCH</Type>
            <Server>[email protected]</Server>
            <ServerDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
            <ServerVersion>73C082C8</ServerVersion>
            <MdbDN>/o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
            <PublicFolderServer>webmail.company.com</PublicFolderServer>
            <AD>SMS-AD1-SRV11.domain.ca</AD>
            <ASUrl>https://webmail.company.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://webmail.company.com/ews/exchange.asmx</EwsUrl>
            <EmwsUrl>https://webmail.company.com/ews/exchange.asmx</EmwsUrl>
            <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.ca</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=domain.ca</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-extinstall>
            <OOFUrl>https://webmail.company.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://webmail.company.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
            <ServerExclusiveConnect>off</ServerExclusiveConnect>
          </Protocol>
          <Protocol>
            <Type>EXPR</Type>
            <Server>webmail.company.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Basic</AuthPackage>
            <ASUrl>https://webmail.company.com/EWS/Exchange.asmx</ASUrl>
            <EwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EwsUrl>
            <EmwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EmwsUrl>
            <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.ca</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=domain.ca</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-extinstall>
            <OOFUrl>https://webmail.company.com/EWS/Exchange.asmx</OOFUrl>
            <UMUrl>https://webmail.company.com/EWS/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
            <ServerExclusiveConnect>on</ServerExclusiveConnect>
            <EwsPartnerUrl>https://webmail.company.com/EWS/Exchange.asmx</EwsPartnerUrl>
            <GroupingInformation>Acheson</GroupingInformation>
          </Protocol>
          <Protocol>
            <Type>WEB</Type>
            <Internal>
              <OWAUrl AuthenticationMethod="Basic, Fba">https://2013server.domain.ca/owa/</OWAUrl>
              <Protocol>
                <Type>EXCH</Type>
                <ASUrl>https://webmail.company.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </Internal>
            <External>
              <OWAUrl AuthenticationMethod="Fba">https://webmail.company.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXPR</Type>
                <ASUrl>https://webmail.company.com/EWS/Exchange.asmx</ASUrl>
              </Protocol>
            </External>
          </Protocol>
          <Protocol>
            <Type>EXHTTP</Type>
            <Server>webmail.company.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Ntlm</AuthPackage>
            <ASUrl>https://webmail.company.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://webmail.company.com/ews/exchange.asmx</EwsUrl>
            <EmwsUrl>https://webmail.company.com/ews/exchange.asmx</EmwsUrl>
            <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.ca</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=domain.ca</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-extinstall>
            <OOFUrl>https://webmail.company.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://webmail.company.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
            <ServerExclusiveConnect>On</ServerExclusiveConnect>
          </Protocol>
          <Protocol>
            <Type>EXHTTP</Type>
            <Server>webmail.company.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Basic</AuthPackage>
            <ASUrl>https://webmail.company.com/EWS/Exchange.asmx</ASUrl>
            <EwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EwsUrl>
            <EmwsUrl>https://webmail.company.com/EWS/Exchange.asmx</EmwsUrl>
            <EcpUrl>https://webmail.company.com/ecp/</EcpUrl>
            <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-um>
            <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.ca</EcpUrl-mt>
            <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-ret>
            <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-sms>
            <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=domain.ca</EcpUrl-publish>
            <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-photo>
            <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.ca</EcpUrl-extinstall>
            <OOFUrl>https://webmail.company.com/EWS/Exchange.asmx</OOFUrl>
            <UMUrl>https://webmail.company.com/EWS/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://webmail.company.com/oab/8a3774fa-6f23-40c7-8106-707cc5b7b1b6/</OABUrl>
            <ServerExclusiveConnect>On</ServerExclusiveConnect>
          </Protocol>
        </Account>
      </Response>
    </Autodiscover>
    Thanks,
    Jeremy

  • Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

    Hi Team,
    I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
    Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
    open and throws an error of some "cannot open set of folders".
    Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
    Kindly share some KB or tip. Any help is appreciated. Thank You.
    Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

    I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
    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 2013 mailbox added to the CAS array

    We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
    installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
    in the array. When installing the mailbox role, we did not choose the client access role but after
    the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
    we did not choose the client access role. How does this happen, and to proceed ?

    I see the same thing in my lab:
    Get-ClientAccessArray | FL
    RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
    ExchangeLegacyDN  : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                        tlook.wingtiptoys.ca
    Fqdn              : Outlook.wingtiptoys.ca
    Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
    SiteName          : Default-First-Site-Name
    Members           : {EXCH-2010, EXCH-2013}
    AdminDisplayName  :
    ExchangeVersion   : 0.1 (8.0.535.0)
    Name              : Outlook.wingtiptoys.ca
    DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                        ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
    Identity          : Outlook.wingtiptoys.ca
    Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
    ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
    ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
    WhenChanged       : 4/12/2014 12:51:18 PM
    WhenCreated       : 4/12/2014 12:51:18 PM
    WhenChangedUTC    : 4/12/2014 7:51:18 PM
    WhenCreatedUTC    : 4/12/2014 7:51:18 PM
    OrganizationId    :
    OriginatingServer : DC-1.wingtiptoys.ca
    IsValid           : True
    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.

  • Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

    We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
    add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
    Orange County District Attorney

    This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
    Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

    I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
    for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
    the following command:
    Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
    The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
    how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
    Many thanks.

    Hi Dennis,
    Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
    Please check your connection authentication. We can  run the following command to set your Outlook Anywhere for Exchange 2013:
    Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
    In Outlook side, please ensure the following settings in Account Settings:
    In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

    Hello guys,
    I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
    When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
    When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
    We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
    What should I check and configure to make it work?

    Hi,
    I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact  EMC supplier to improve it.
    By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
    A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    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]
    Jim Xu
    TechNet Community Support

  • How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

    Hi All,
    we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013  and i have to add the 2013
    servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
    Thanks, Venkatesh. &quot;Hardwork Never Fails&quot;

    For a step by step follow the deployment assistant
    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 Mailbox Role Installation Error

    Hi All,
    I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
    Error:
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
    . HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
       at System.DirectoryServices.DirectoryEntry
       at System.DirectoryServices.DirectoryEntry.Bind()
       at System.DirectoryServices.DirectoryEntry.RefreshCache()
       at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
       at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Any views on this is appreciated.
    Regards
    Boniface
    Senior Systems Administrator

    Hi,
    After uninstalling the IIS, please run the following command to install prerequisites.
    Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
    Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
    Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
    Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
    In addition, please disable any third-part software for troublwshooting.
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Performance counters for exchange 2013 mailbox & cas servers?

    what are the Performance counters for exchange 2013 mailbox & cas servers?
     similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013. 

    Hi,
    Please see this:
    Ask the Perf Guy: Sizing Exchange 2013 Deployments
    http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
    Hope it is what you need.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 calendar not showing on outlook 11 Mac

    Exchange 2010 calendar not showing on Outlook 11 Mac on my iMac. It shows fine on iPhone and OWA. 

    Since this question is about a Microsoft product, you might have more luck getting suggestions if you ask in Microsoft's own forums.
    Regards.

  • Outlook 2010 prompt for credential when connecting to Exchange 2013 mailbox

    I have 4 server Exchange 2010 with DAG and one server Exchange 2013, i've migrated some mailbox to the new 2013 server.
    I'm having a problem with some Outlook 2010 that sometimes (not always) requires credential to connect to mailbox in a server Exchange 2013, but only
    when Cache mode is enabled.
    The client ask for credential and dont connect to mailbox until I change in online mode.
    In Online Mode, everything works fine.
    I don't have Public Folders, so the check box Download Public Folder is not selected and the authentication mode is "Negotiate".
    Thanks in advance.
    Elisa

    Hi,
    As far as I know, by default, shared mail folders not public folders are downloaded in Cached mode in Outlook 2010 and Outlook 2013:
    http://support.microsoft.com/kb/982697/en-us
    Please check if there is shared folder in the problematic Outlook 2010 client and try to check if the issue still exists with the same account on other Outlook client.
    Best regards,
    Angela Shi
    TechNet Community Support

  • Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

    Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
    I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
    "Could not find a valid mailbox migration for this organization"
    Do you know that you can be?
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi,
    From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
    Migration.8f3e7716-2011-43e4-96b1-aba62d229136
    If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
    Hope this can be helpful to you.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 mailbox auditing command with showdetails parameter in ps1 script is not working via task scheduler

     
    Hi All ,
    In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
    We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the  ps1 script  in exchange management shell ,i can able to get the relevant output.
    CMDLETS in powershell script :
    Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
    Note : we are having only the above commands in ps1 script , apart from that we don't have anything in it .
    Sametime i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it . 
    Steps handled on my side to run the powershell script in task scheduler: 
    1.when i remove the parameter showdetails in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
    The Difference what i have seen between exchange 2010 and exchange 2013 
    when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
    I am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
    program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Add arguments : -PSConsoleFile "E:\Program Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
    I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
    Error message : "the requesting account does not have permission to access the audit log"
    Please help me out to resolve this case .
    Thanks 
    S.Nithyanandham

    Hi All ,
    In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
    We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the  ps1 script  in
    exchange management shell,i can able to get the relevant output.
    CMDLETS in powershell script :
    Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
    Note : we are having only the above commands in ps1
    script , apart from that we don't have anything in it .
    In case, if i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it . 
    Steps
    handled on my side to run the powershell script in task scheduler: 
    1.when i remove the parameter showdetails
    in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
    The
    Difference what i have seen between exchange 2010 and exchange 2013 
    when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
    I
    am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
    program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Add arguments : -PSConsoleFile "E:\Program
    Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
    I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
    Error message : "the requesting account does
    not have permission to access the audit log"
    Please help me out to resolve this case .
    Thanks 
    S.Nithyanandham

Maybe you are looking for

  • How much can i get Final Cut Studio 2?

    Hi, *in fact, i love this program so so much and i will get it to make tutorials in my blog or website as well but i can't buy it because it is so expensive for me and i'm student too,now i have some questions:-* *1-is there discount for this program

  • I cannot map a windows 2008 shared drive into mac 10.5.8

    Hi Support, I have tried to map a shared drive from windows 2008 x64 on to Mac 10.5.8. however, it is unsuccessful and it prompts "the file server is running on your machine.Please access the volumes and files locally." after i clicked ok, it prompts

  • Problem with A300, Ask for help

    Hello from Bulgaria! In the beginning I want to apologize if I bother you at the wrong place. This was the only place i found in all your sites at "Contact us" menu. If I'm in mistake please redirect me to the right e-mail or topic. I have extremely

  • Unable to access Login Items for Accounts in System Preferences

    I've created an image for computers at my school. When I go into System Preferences>Accounts, and authenticate, I am unable to access the Login Items tab. The tab isn't grayed out or anything. It's just that when I click on it, nothing happens. It st

  • Problem printing with Lightroom using Vista

    I just recently upgraded my XP system to a Vista 64 bit system. I print digital photos using Adobe Lightroom 1.4. With my XP system, I had a good match between my calibrated monitor (NEC 2690) and my printer (HP B9180) working in the ProPhoto RGB col