Exchange 2010 co-existence with Exchange 2007 issue NDR size Four Times then we send

Hi All,
I am facing some strange issues of NDR size four times then we send like if I send 1 MB message to internal OR external recipient then we receive 4 MB NDR.
Even we send one black mail with subject Test mail of 4 kb then we receive 16 kb NDR is it due to architecture change or something else.
Everything was fine with Exchange 2007 but facing this issues after we change the mail flow to Ex2010.
Any help really appreciated
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

Hi Anand,
From your description, the NDR size is four times than original message size. I would like to verify the following thing for troubleshooting:
How many people has this issue, only one or all the people?
If only one user has this issue, I recommend you move the user's mailbox to another mailbox database and check the result.
If all the people have this issue, please enable Pipeline tracing and see if there is any hint. If the issue persists, please install the latest Service Pack and Rollup and check the result.
Here is an article for your reference.
Enable Pipeline Tracing
http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 co-existence with Exchange 2010 proxying issue.

    Hello,  
    I am testing Exchange 2010 and Exchange 2013 co-existence in my test lab at the moment, with
    a view to migrating our production environment to 2013 later in the year.  
    The lab is setup, and the problem I'm having is that internal Outlook clients cannot open
    their respective mailboxes once the 2013 CAS server is introduced into the mix.  
     The
    setup is listed below:  
    EXCHANGE 2010 Servers  
    TESTLABEXCH01 - CAS,HT,MBX - Exchange 2010 SP3  
    TESTLABEXCH02 - CAS,HT,MBX - Exchange 2010 SP3  
    Both servers are part of a CAS Array - casarray01.testlab.local  
    Both servers are part of a DAG - DAG01.testlab.local  
    RpcClientAccessServer on all 2010 databases set to casarray01.testlab.local  
    The A record for casarray01.testlab.local points to the IP of the VIP of a load balancer.  
    The loadbalancer serves
    the following ports: 25,80,443,143,993,110,995,135,60200,60201  
    OutlookAnywhere is enabled on both servers:  
    ClientAuthenticationMethod : Ntlm  
    IISAuthenticationMethods   : {Basic, Ntlm}  
    Internal and external mail flow works without issue before the 2013 server is introduced. 
    Internal and external client access works without issue before the 2013 server is introduced. 
    Part Two to follow.....
    Matt

    EXCHANGE 2013 Servers :
    TESTLABEXCH03 - CAS,MBX - Exchange 2013 SP1  
    OutlookAnywhere is enabled on the server:  
    ClientAuthenticationMethod : Ntlm  
    IISAuthenticationMethods   : {Basic, Ntlm}  
    RpcClientAccessServer on all 2013 databases set to casarray01.testlab.local
    (This an inherited setting I assume from the pre-existing 2010 organization)  
    Split DNS is in place and all internal/external URL's point to either:  
    autidiscover.external.com  
    mail.external.com  
    The A record for the mail.external.com points to the IP of the load balancer VIP  
    The CNAME record for autodiscover.external.com points to mail.external.com  
    When the TESTLABEXCH03 is added to the load balancer config,
    and given highest priority this is when the Outlook clients stop working.  
    Any existing profiles in Outlook 2010/Outlook 2013 can no be opened as there is a persistent
    credentials prompt.  
    Upon trying to create a new profile, the process errors when reaching the "Log onto server"
    stage and again prompts for credentials.  
    Running the test-outlookconnectivity cmdlet from
    either of the 2010 servers produces the following results.  
    [PS] C:\Windows\system32>Test-OutlookConnectivity -Protocol:http  
    ClientAccessServer   ServiceEndpoint                         
    Scenario                            Result  Latency  
    TESTLABEXCH02  autodiscover.external.com    Autodiscover:
    Web service request.  Success  343.20  
    TESTLABEXCH02  casarray01.testlab.local       RpcProxy::VerifyRpcProxy.  
    Success    0.00  
    TESTLABEXCH02  casarray01.testlab.local         RFRI::GetReferral.                 
    Failure   -1.00  
    TESTLABEXCH02  casarray01.testlab.local        NSPI::GetProfileDetails.           
    Failure   -1.00  
    TESTLABEXCH02  casarray01.testlab.local        
    Mailbox::Connect.                   Failure   -1.00 
    TESTLABEXCH02  casarray01.testlab.local        
    Mailbox::Logon.                     Skipped   -1.00  
    If remove the 2013 CAS server from the loadbalancer config and
    all connections go directly to the 2010 servers again, all of the above tests pass and Outlook connectivity is also restored.  
    IIS has been reset on all 3 servers incidentally, following any changes made whilst troubleshooting. 
    I'm struggling to see what I'm missing here, if anyone can assist in troubleshooting this
    matter further, or point out any errors in my setup it would be greatly appreciated.  
    Regards  
    Matt 
    Matt

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

    Here is our current scenario,
    Exchange 2007
    2 - Hub Transport Servers
    2 - CAS servers (cluster NLB)
    2 - Mailbox servers (clustered)
    Exchange 2010
    2 - Huib Transport Servers
    3 - CAS servers (array NLB)
    2 - Mailbox servers (1 DAG)
    We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

    Hi,
    As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

    I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
    the Exchange 2010 all incoming external mails were not received. What could be the cause?

    Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
    Sniff the traffic to ensure that it is hitting 2013 directly.
    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 2010 SP3 - RU3 RU4 Public Folders issues ( not refreshing ) when grouping by Categories for "(None)" Group

    After installing Exchange 2010 SP3 RU3, I had an issue in Public Folders, once having group by categories in Outlook, the Group of "(None)" categories is not refreshing when changing flag... I also installed RU4 but nothing changed, any reason
    Thx

    Hi,
    From your description, the group with none categories won’t fresh when changing flag in Category view. If I misunderstood, please point it out.
    As you can in the View tab as below, there is Category as well as Flag: Start date or Due Date. It means that grouping per color categories is more or less different from that
    grouping by flag.
    Should you need more assistance, feel free to tell me.
    Regards,
    Rebecca Tu
    TechNet Community Support

  • ISA 2006 publish Exchange 2010 Outlook Anywhere with KCD/NTLM and IPSEC - Problem

    Hi
    I have setup ISA 2006 to publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation and IPSEC.
    The clients have an IPSEC policy pushed to them via GPO.  The clients are windows 7 laptops and the ISA server is server 2003, so the IPSEC connection is IKE not AuthIP.
    However, it seems that the connection will work for a while, then all of a sudden stop working with zero trace of why.  I cant get the Oakley log to work and I cant see any traffic on the ISA.
    I am wondering if I need to publish the CRL's externally?  Currently we don't, and the Outlook Anywhere uses private certificates (as the whole point of IPSEC is to validate the internal certificate, there is no point in using
    public certificates).
    I have tried using the StrongCRLCheck=0 registry key in the IPsec Policy Agent on the windows 7 machine but it doesn't seem to make a difference.
    Any advice would be appreciated.
    Steven

    Hi,
    Firstly, have you received any related error messages in ISA server or on the clients' side? Besides, as you mentioned IPsec, did you have a VPN connection?
    In addition,
    While ISA 2006 only includes a Client Access Web Publishing Wizard for both Exchange 2003 and Exchange 2007. Which Exchange version you have chosen when publishing Exchange 2010?
    Please also make sure that you have selected the
    External interface for the web listener to listen on.
    Besides, the link below would be helpful to you:
    OWA publishing using Kerberos Constrained Delegation
    method for authentication delegation
    Best regards,
    Susie

  • I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

    Hi,
    From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
    Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
    http://support2.microsoft.com/kb/2997209
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • ISA 2006 publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation

    Hi,
    I have two Exchange 2010 Sp1 CAS with Windows Network Loadbalancing. I set up an alternate Serviceaccount and mapped the http,ExchangeMDB,PRF and ExchangeAB SPNs.
    Then i published the Exchange Services via ISA 2006. OWA is working using Internet -> via NTLM -> ISA(webmail.domain.com) -> via KCD -> CAS-Array(ex2010.domain.com)
    I tried the same with Outlook Anywhere (RPC over HTTP) without success.
    Authentication to the ISA via NTLM works fine, but i think the isa server cannot delegate the Credentials successfully to the CAS-Server.
    The ISA Log looks like:
    Allowed Connection ISA 24.11.2011 15:50:40
    Log type: Web Proxy (Reverse)
    Status: 403 Forbidden
    Rule: Exchange 2010 RPC
    Source: Internal (172.16.251.33)
    Destination: (172.18.10.182:443)
    Request: RPC_OUT_DATA
    http://webmail.domain.com/rpc/rpcproxy.dll?ex2010.domain.com:6001
    Filter information: Req ID: 108b89d8; Compression: client=No, server=No, compress rate=0% decompress rate=0%
    Protocol: https
    So i always get a 403 Forbidden from the CAS.
    I the IIS logfile from the cas server i see this entry:
    2011-11-24 15:51:37 172.18.10.182 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.domain.com:6001 443 - <ISA IP> MSRPC 401 1 2148074254 203
    I use the same Listener for OWA and Outlook Anywhere. Authentication Methods are Basic and Integrated. I forward the request to a webfarm which exists of the two physical CAS. Internal Site Name is set to the NLB name ex2010.domain.com, SPN is set to http/ex2010.domain.com
    Thanks for your support

    Hi, i ran into the same Problem.
    the steps above solved mine too (Creating a custom AppPool which runs under LocalSystem).
    I wonder why they included only the Script: convertoabtovdir.ps1
    http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/thread/dc24ccd3-378a-47cc-bbbf-48236f8fe5b0
    Ist this a supported configuration (changing AppPool of RPC)?

  • Exchange 2010 OWA usage in Exchange 2013

    Hi,
    I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
    Before Migration we want below things to keep in mind...
    1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
    2. Can i use my Existing Exchange certificate to get the above goal done ?
    3. What will be the steps and pre-requsite to achieve the Goal ?
    An Early reply would be appreciated !! 
    Amit

    Hi Amit 
    First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
    Configure external  DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
    Ensure that you are having a seperate name for CAS array from external ews url
    Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
    Authentication for OUtlook Anywhere should be - NTLM
    for OWA exchange 2010 - FBA and windows 
    Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users 
    You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
    Apply a new certificate with all the required site names included in Exchange 2013 CAS.
    Whats more you can refer my blog as well 
    http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
    Cheers :)
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Exchange 2013 co-existence with 2007 can not send from 2013 - receives OK

    2013 SP1  -separate servers for MBX and CAS - 4 of each. Exchange 2007 configured as a CCR
    I am in co-existence mode but have not yet switched on the legacy.domainname.com. I have a new certificate installed on all servers - 2007 and 2013 with the legacy namespace included
    I can receive on the exchange 2013 servers and can send to exchange 2013 users but cannot send to 2007 users or externally. I have enabled protocol logging and I'm seeing:
    2014-04-02T00:57:31.476Z,Outbound Primary,08D1120CF8FEEDBA,0,,10.0.9.1:25,*,,attempting to connect
    2014-04-02T00:57:52.521Z,Outbound Primary,08D1120CF8FEEDBA,1,,10.0.9.1:25,*,,"Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a
    period of time, or established connection failed because connected host has failed to respond 10.0.9.1:25"
    The client has a pair of Axway mailgateway appliances (Tumbleweed). We can Telnet between the exchange 2013 servers and the Axways. There is a firewall between these mail gateways and the exchange servers and the following ports were opened - 25,443,465,995,110
    I used the existing send connectors from 2007 and just added the mailbox servers to them. I created 2 new receive connectors to match 2 specialist 2007 connectors.
    But I still can't send mail. Any suggestions where next to check?

    Hi Tony 
    Based on the protocol logs error looks like there is connectivity problem between Ex2007 and Ex2013
    First you can try dropping an email through Telnet from Exchange 2013 to Exchange 2007 to see the message failure happens at which transit.
    You can add the IP address of Exchange 2013 in Exchange 2007 default receive connector and vice versa.
    Restart the transport service and try sending an email from exchange 2013 to Exchange 2007 and see the results
    Also you can try creating a dedicated receive connector for Exchange 2007 in Exchange 2013 and vice versa if the above step does not work 
    Also try disabling the firewall and see if it helps.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

  • Export Mailbox from Exchange 2010 and Import to Exchange 2007

    Hello,
    I exported mailbox (1GB in size) from Exchange 2010 to *.pst file; I need to import it into
    Exchange 2007 mailbox. Is it supported ?
    The operation completed successfully (no errors) but no items were imported; is it due to unsupported backward compatibility or some other issue ?
    Thank you,
    Luca
    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

    I also have the same issue. Exported mailboxes on Exchange 2010 SP3 latest updates using
    New-MailboxExportRequest and then tried to import into mailbox on Exchange 2007 SP3 with latest updates. The 32-bit client machine used for the import has Outlook 2010 SP1 (SP2 and later updates causes a different error). I used Outlook 2010 because the E2K10
    New-MailboxExportRequest documentation states that you have to use Outlook 2010 or later. The PST files created can be opened and imported via Outlook but not with the
    Import-Mailbox cmdlet (with no error as stated in this thread). Other PSTs, not created from E2K10 export do import just fine. I also ran ScanPST.exe against the exported PST and then ran the import again and it worked, everything got imported. Interestingly
    the test mailbox PST file I was using was 761 KB but after the ScanPST it was 1,257 KB - must be some difference in the PST format that the Import-Mailbox cmdlet can't deal with.
    Does anyone have any other solutions or
    workarounds to this. I've got over 900 mailboxes I need this for due to an
    acquisition? Has anyone tried using Outlook 2013 on the machine used for doing
    the Exchange 2007 imports or does Outlook 2013 also have the same issue as later versions of Outlook 2010 (Exchange Mailbox import failed with error code 2147221233)?

  • Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

    I have exchange 2013 and 2007 set up in a coexist environment.  At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007.  I found an article
    that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.)  I would like someone to confirm
    if the change I am about to make from doing research will help me in my situation.
    Current Setup:
    Exchange 2007 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: NTLM
    IISAuthenticationMethods : {Basic, Ntlm}
    Exchange 2013 OA CAS Settings
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod: Negotiate
    IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
    New Settings I am considering based on research:
    Exchange 2007 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: Basic
    IISAuthenticationMethods : {NTLM}
    Exchange 2013 OA CAS Settings
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod: Basic
    IISAuthenticationMethods : {Basic}
    Will this work and eliminate my popups?

    Hi,
    The following TechNet article indicates that:
    “In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
    Exchange Deployment Assistant. Specifically,
    you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
    Client Connectivity in an Exchange 2013 Coexistence Environment
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 CAS proxy to Exchange 2013 CAS: Use the following link to open this mailbox with the best performance:

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    and moved one mailbox [ Test user ] to Exchange 2013.
    When I login internally through 2013 OWA to access mailboxes on 2010, then proxy works fine.
    When I login internally through 2010 OWA to access mailboxes on 2013, then a message appears:
        Use the following link to open this mailbox with the best performance: with link to 2013 OWA...
    What is wrong ?
    I've checked and changed settings by:
    Get-OwaVirtualDirectory, Set-OwaVirtualDirectory
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex10\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX10
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex10.contoso.com/owa
    ExternalUrl                   : https://ex10.contoso.com/owa
    [PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex13\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*
    Server                        : EX13
    Name                          : owa (Default Web Site)
    ClientAuthCleanupLevel        : High
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
    BasicAuthentication           : True
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    RedirectToOptimalOWAServer    : True
    LegacyRedirectType            : Silent
    Url                           : {}
    SetPhotoURL                   :
    Exchange2003Url               :
    FailbackUrl                   :
    InternalUrl                   : https://ex13.contoso.com/owa
    ExternalUrl                   :
    best regards Janusz Such

    Hi Janusz Such,
    Based on my knowledge, CAS proxy can only from later version to previous version.
    Some like CAS2013 to CAS2010/2007, CAS2013 to CAS2013. 
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • IOS 4.3.1 + Exchange 2010 "was" fine with the mailbox on Ex2007 server

    Hi,
    i had used my iphone with ios 4.3.1 and active sync.
    The mailbox was hosted on the old exchange 2007 server.
    A new exchange 2010 server was running the last 4 weeks and the iphone was connection with activesync against the new exchange 2010 through local wlan and over internet.
    After i moved my profile to the new server i can´t connect anymore to the new server!
    Any idea what happend?

    It was working fine the last weeks with my mail account sitting on exchange 2007.
    Today i moved several mailboxes from exchange 2007 to 2010 SP1.
    I have some domain accounts that are created new and had their mailbox created on the exchange 2010 sp1 system.
    With these accounts i can connect and retrieve mails.
    But with my account (moved from 2007 to 2010) i can´t.
    All i get is a blank mailbox on my iphone.
    I even removed the mail account from my iphone and recreated the account.
    But it won´t retrieve mails.
    I refresh the offline addressbook at the exchange 2010 but nothing will help.
    Message was edited by: juergenb52

Maybe you are looking for