Exchange 2013 mailbox is being excluded from provisioning

I have a Exchange 2013 CU4 server on Windows 2012.  I have 2 mailbox databases setup.  One is for journaling and the other is for regular mailboxes.  I set the IsSuspendedFromProvisioning switch to true on the journal DB about 8 months ago. 
Recently, when I go to make a mailbox it says "Load balancing failed to find a valid mailbox database."  Upon Investigating, I discovered that the regular mail DB had its
IsExcludedFromProvisioning switch set to true.  I changed it to false and the mailbox was created fine.  A couple days later, I went to add another mailbox and the same thing happened.  I monitored the mailbox status and determined that
within 30 mins of setting the IsExcludedFromProvisioning switch to true that it switches back to false.  I am unsure of how to correct this.  Any thoughts?

Here is the output from the requested cmdlet.
[PS] C:\Windows\system32>Get-MailboxDatabase MDB01 | Select name,*provision*
Name : MDB01
IsExcludedFromProvisioning : True
IsExcludedFromInitialProvisioning : False
IsSuspendedFromProvisioning : False
IsExcludedFromProvisioningBySpaceMonitoring : True
MailboxProvisioningAttributes :
Recently the only changes made to the Exchange organization has been moving the journal db to a new HDD.  I didn't have any issues or errors.
I notice that the IsExcludedFromProvisioningBySpaceMonitoring  is set to false.  Is this determining how much room is left on the drive.  I looked at the drive and see that there is still 10.7 GB left of the available 149 GB.  I know
that Exchange tends to work on percentages now so is this below the needed available diskspace to provision to automatically?
Thank you for the input.

Similar Messages

  • Prevent OST file from being excluded from workstation backups

    Is there a way to prevent OST files from being excluded from client/workstation backups in WS2012E?
    Thanks,
    Reg
    This is especially a problem for clients that have migrated to Office 365 exchange service as they have no local backup of emails that were deleted and think synced with Office 365.
    Reginald Hook

    OST files are not a local backup, they are a cache of what is in the mailbox.
    https://support.office.com/en-gb/article/Introduction-to-Outlook-Data-Files-pst-and-ost-6d4197ec-1304-4b81-a17d-66d4eef30b78#__toc290027730
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • 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

  • 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. "Hardwork Never Fails"

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

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

  • 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

  • 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 2013 mailbox migration from third party cloud to on premises

    Hi,
    we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes (  intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
    cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
    we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
    Pls suggest the prerequisites,steps, best practices for migration
    Thanks in advance.

    Hi Sumesh,
    1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
    2. Hope you already created the users in your Exchange2013 server and distribution groups for current users 
    3. You plan a weekend for changing your MX records. 
    4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
    5. Export Hosted Exchange data for each user to PST files  using the PST capture tool and move your PSTs to a centralized location.
    6. Change MX and A records to point to on-premises Exchange 2013
    7. Import Hosted Exchange data from PST files into the new Exchange profiles
    Please check these as well
    http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
    http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Accessing Exchange 2013 Mailboxes from Terminal Server hosted on Server 2003 Std - Cert Issues

    We are in the midst of deploying an Exchange 2013 SP1 CU5 environment and have run into some issues.  Currently there is a good coexistence between a single Exchange 2007 server and the 5 2013 servers.  Mail is flowing through 2013 and then being
    relayed to 2007 when necessary.  
    We have a number of Server 2003 Terminal Servers.  On two separate machines, both running the lastest rollups of Outlook 2010, any user with a 2013 mailbox receives a password prompt after launching Outlook.  It is trying to connect to one of the
    two CAS, fills in the user's account, and will not accept any password.  In addition, a window pops up behind stating "There is a problem with the proxy server's security certificate.  the name on the security certificate is invalid or does
    not match the name of the target site mail.pvschemicals.com.  Outlook is unable to connect to the proxy server.  (error code 0)."  2007 mailboxes are not affected.
    We have checked pretty much everything that we can think of.  Virtual Directories are good, certificate is good, etc.  The strange thing is that only happens on 2003 TS machines, so I have to think that it's related.  Our 2008 TS' are just
    find.
    We have applied the 2003 SHA2 certificate hotfix. 

    Hi,
    According to your description, the configurations of Outlook Anywhere are proper. And based on my research, the issue can be related to the version of the terminal server 2003. Thus, please check if your terminal 2003 server is 2003 R2 SP2 or later.
    For more information, you can refer to the following thread:
    http://social.technet.microsoft.com/Forums/exchange/en-US/295bf2bc-584b-4de2-85fb-94096fac52e7/outlook-connectivity-problem-on-2003-term-server-exchange-2013?forum=exchangesvrclients
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

    Hi,
    I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
    Configuration server Exchange 2007 SP3 :
    Domain : test.com
    OS : Windows 2008 server SP2 (not R2)
    Firewall : OFF
    Exchange roles are on separate three  servers : CAS - MAILBOX - HUB.
    Configuration Server Exchange 2013 :
    Domain : new.com
    OS: Windows 2012 R2
    Firewall : OFF
    This environment is on a closed network unable to reach internet.
    I have try to restart the Replication service, but it didn't worked.
    I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
    Anyone ever had this issue?
    Thanks you and have a nice day.

    Hi ,
    Based on my knowledge below things need to checked.
    1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
    2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
    DataMoveReplicationConstraint : None
    Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
    3.Restart the Microsoft exchange mailbox replication service and check the results.
    4. Have you tried moving the same mailboxes to the different databases.
    5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
    Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
    Please feel free to reply me if you have any queries.
    Thanks & Regards S.Nithyanandham

  • 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

  • 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 2007 - Exchange 2013 Mailbox Migration Issues

    Exchange 2013 -  Mail Flow is working.   OWA Access is great.   We have issues connecting Outlook 2010 Clients.  If I create a new user and mailbox Outlook 2010 works fine.   However, if we migrate a user's mailbox to the new Exchange
    2013 server.  Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server"  There is something different about a newly created account and a migrated account.  Any help would be great.   I did check
    inheritance in AD and it was on for these accounts.  This occurs with any account migrated to the new server.

    1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
    generates and provides the correct information.
    2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
    Step by Step Screencasts and Video Tutorials

Maybe you are looking for