OutlookProvider EXCH/EXPR questions for 2007/2013 CoExistence, Outlook connectivity issue

Hi Everyone-
Can anyone give me advice on how to configure my Outlook providers for my environment?
Single 2007 Server in coexistence with separate CAS/MBX 2013 Sp1.
It currently looks like this:
I changed the EXPR CertPrincipleName after coexistence due to a cert pop-up that was occurring in Outlook (2010) while connected to a 2007 mailbox.  
All connectivity and mail flow is working fine, EXCEPT, connecting Outlook to a 2013 mailbox.  It finds the user/mb but fails at login.
Thank you for your time!

Hi Andrew
There is nothing much complicated to think if we use Exchange Server Deployment assistant as it an perfect guide.
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-EgBEAgAAQAAAAQECAQAAAAg%7e
To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure Outlook Anywhere on all of the Exchange 2007 servers in your organization. 
Users with mailboxes still on 2007 will be connecting to CAS 2013 and then will be proxied to CAS 2007
Exchange 2013 will coexist easily with 2007 mailboxes by using ActiveSync.  As soon as the DNS entry for 2007 CAS points to the 2013 Client Access Server, 2007 mailboxes that use ActiveSync will be able to sync through the 2013 Client Access server without
any configuration changes.  This is assuming that if the 2007 CAS Servers are using a default configuration such as SSL (443) with basic authentication. Integrated authentication by default should remain enabled on the Proxy folder that is located beneath
the Microsoft-Server-ActiveSync Folder.
During coexistence the 2013 OAB will be the default OAB.Run below command to check
get-mailboxdatabase | fl identity,*offline*
Run below command to change Activesync virtual directory
Get- ActiveSyncVirtualDirectory –Server “Exchange 2013 ServerName” | Set-ActiveSyncVirtualDirectory -InternalUrl "https://abc.com/Microsoft-Server-ActiveSync" –ExternalUrl "https://abc.com/Microsoft-Server-ActiveSync"
Run below command to change the autodiscover url
Get-ClientAccessServer –Identity “2013 Server name” | Set-ClientAccessServer –AutodiscoverServiceInternalUri “https://abc.com/autodiscover/autodiscover.xml”
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

Similar Messages

  • Outlook anywhere in 2007/2013 coexistence

    Hi!
    I have a multitenant exchange 2007 at a single server setup and I’m trying to do migration to exchange 2013. I’m testing this in my lab environment before I go the production. I’m quite far and for example the owa redirection to exchange
    2007 works. Also I can connect with outlook anywhere the exchange 2013 server when the mailbox is transferred.
    Problem is that the exchange 2013 proxy redirection to 2007 server isn’t working. My Outlook 2010 just keeps asking username and password. Outlooks are configured to connect with basic authentication.
    I have done a lot of googling about the issue and there is a lot of discussion about it. I have tried a lot of things and I’m quite lost now.
    I have tried to configure the externalclientauthenticationmethod, internalauthenticationmethod and IISauthenticationmethods with different kind of setups but can’t get it to work. Also tried to change the internal and external hostnames.
    My outlook anywhere setup at 2007 server is:
    RunspaceId                        
    : 714f0d1a-c0f0-4694-aefe-8cf6218521ea
    ServerName                        
    : EXCHANGE07
    SSLOffloading                     
    : False
    ExternalHostname                  
    : exchange07.xxx.fi
    InternalHostname                  
    : legacy.xxx.fi
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods          
    : {Basic, Ntlm}
    XropUrl                           
    ExternalClientsRequireSsl      
       : True
    InternalClientsRequireSsl         
    : True
    MetabasePath                      
    : IIS://wcn-exchange07.welcomnet.fi/W3SVC/1/ROOT/Rpc
    Path                              
    : C:\WINDOWS\System32\RpcProxy
    ExtendedProtectionTokenChecking   
    : None
    ExtendedProtectionFlags           
    ExtendedProtectionSPNList         
    AdminDisplayVersion               
    : Version 8.3 (Build 83.6)
    Server                            
    : WCN-EXCHANGE07
    AdminDisplayName                  
    ExchangeVersion                 
      : 0.1 (8.0.535.0)
    Name                              
    : Rpc (Default Web Site)
    ObjectClass                       
    : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                       
    : 14.5.2014 20:56:18
    WhenCreated          
                 : 14.10.2008 12:33:07
    WhenChangedUTC                    
    : 14.5.2014 17:56:18
    WhenCreatedUTC                    
    : 14.10.2008 9:33:07
    Exchange 2013 outook anywhere setup:
    RunspaceId                        
    : 714f0d1a-c0f0-4694-aefe-8cf6218521ea
    ServerName                        
    : EXCHANGE13
    SSLOffloading                     
    : False
    ExternalHostname                  
    : exchange07.xxx.fi
    InternalHostname                  
    : exchange07.xxx.fi
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods          
    : {Basic, Ntlm}
    XropUrl                           
    ExternalClientsRequireSsl         
    : True
    InternalClientsRequireSsl         
    : True
    MetabasePath                      
    : IIS://exchange13.xxx.fi/W3SVC/1/ROOT/Rpc
    Path 
                                 : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking   
    : None
    ExtendedProtectionFlags           
    ExtendedProtectionSPNList         
    AdminDisplayVersion             
      : Version 15.0 (Build 847.32)
    Server                            
    : WCN-EXCHANGE13
    AdminDisplayName                  
    ExchangeVersion                   
    : 0.20 (15.0.0.0)
    Name                       
           : Rpc (Default Web Site)
    ObjectClass         
                  : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                       
    : 14.5.2014 20:55:56
    WhenCreated                       
    : 2.4.2014 0:57:19
    WhenChangedUTC                    
    : 14.5.2014 17:55:56
    WhenCreatedUTC                    
    : 1.4.2014 21:57:19
    Any help would be appreciated.

    Hi,
    Firstly, I'd like to explain, only in Exchange 2013, internal and external Outlook clients use Outlook Anywhere. Thus,in Exchange 2007, Outlook Anywhere settings can only include the external host name.
    And based on my experience, the credential issue is related to connectivity issue, authentication issue or public folder access.
    So I'd like to confirm the following information to understand more about the issue:
    1.  Does the issue happens on all users? users on Exhcange 2007 or 2013? internal users or external users?
    As far as I know, redirection and proxy don't happen on Outlook clients:
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    2. Which IP address do your host name points to? legacy.xxx.fi, exchange07.xxx.fi?
    3. Check the Outlook Anywhere connectivity of the problematic users by ExRCA:
    https://testconnectivity.microsoft.com/
    If you have any question, please feel free to let me know.
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Outlook 2007-2013 doesn't connect in non-cached mode to Exchange 2013.

    Hello!
    I have organization Exchange 2010 + Exchange 2013 in one AD site (hybrid organization) 
    Mailboxes based on Exchange 2010 servers work fine. But after moving one of mailboxes to
    Exchange 2013 database, Outlook doesn't connect to mailbox in
    non-cached mode. If I turn on cached mode this mailbox is connecting perfectly (OAB, Folders, PublicFolders, Addresslists).
    I cleaned parameter "PublicFolderDatabase"  for Exchange 2013 database,  but the problem didn't solve.
    In CAS
    RpcHttp
    log:
    2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=BeginRequest;S:AuthType=Negotiate;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?MBXDB13.DOMAIN.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
    2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=PostAuthorizeRequest;S:UserName=DOMAIN\MBXDB13.domain.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
    Exchange Server 2013 Cumulative Update 7 (CU7)
     are installed.

    Hi Allen!
    Thank you for reply!
    Outlook cannot connect to all mailboxes on Exchange 2013 server.
    >Get-OutlookAnywhere | FL Name,*auth*,*host*Name                               : Rpc (Default Web Site)
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic}
    ExternalHostname                   : exchange2010.contoso.com
    InternalHostname                   :
    Name                               : Rpc (Default Web Site)
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic}
    ExternalHostname                   : exchange2010.contoso.com
    InternalHostname                   :
    Name                               : Rpc (Default Web Site)
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic}
    ExternalHostname                   : exchange2013.contoso.com
    InternalHostname                   : cas1302.domain.local
    Name                               : Rpc (Default Web Site)
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic}
    ExternalHostname                   : exchange2013.contoso.com
    InternalHostname                   : cas1301.domain.local
    Outlook error message:
    "Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt log on to Microsoft Exchange has failed."
    This error reproduced even in new profile. Repair does not help.

  • Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

    Hi,
    After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
    same. Outlook was working fine before the upgrade.
    Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
    Already applied the transport fix.
    Thanks in advance!

    Hi,
    According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
    To narrow down the issue, I’d like to recommend the following troubleshooting:
    1. Check if the issue happens on all Outlook users
    2. Check the Outlook Anywhere connectivity by using ExRCA:
    https://testconnectivity.microsoft.com/
    Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
    If you have any question , please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Azure Visual Studio 2013 Integrated Sign Connectivity Issues

    I am having periodic VS2013 Ultimate and Azure tools 2.3 connectivity issues. I'd say it's all related to session timing out but it causes VS to crash sometimes and other times when using some Azure feature, right clicking 'Web Role' I get 'Object....null
    reference' messages.
    I can ask studio to connect to Azure, via right clicking Azure node of Azure branch in server explorer and it always tells me I'm currently signed in as the correct\current user but this seems to prevent the issue from occurring if I do this first thing
    everyday.
    How can I properly resolve the Visual Studio crashes and such? I'd say I've had Visual Studio 2013 crash more in the last 6 months than all prior VS crashes across my DEV lifetime....and I started developing long before Visual Studio was born :>)

    Hi,
    It's hard to reproduce this issue, please try to update your vs, then see whether this issue exist or not. You could also use another computer to do the same operation, if you encounter the same issue, please contact with azure support to
    get further help:  http://www.windowsazure.com/en-us/support/contact/
    Best Regards,
    Jambor
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • HTTP 500 error when opening a legacy shared mailbox in OWA 2013 (Exchange 2007/2013 coexistence environment)

    Hi,
    Our Exchange 2013/2007 coexistence environment is set up and all is working apart from this:
    Mailbox A has full permissions to Mailbox B. Mailbox A is migrated to Exchange 2013, but Mailbox B remains on Exchange 2007. If I login to Outlook Web App 2013 as Mailbox A and then "Open another mailbox..." and select Mailbox B, a new window opens
    up saying "HTTP 500 Internal Server Error". The URL it is trying is :
    https://webmail.ourdomain.com/owa/[email protected]/?offline=disabled
    ( I can open Mailbox A in Outlook 2010 and do "Open Other users's folder.." and Mailbox B opens up just fine. )
    Our legacy CAS server's External and Internal URLs are set to :
    https://legacy.ourdomain.com/owa
    and the Exchange 2013 CAS server's External and Internal URLs are set to :
    https://webmail.ourdomain.com/owa
    We have FBA enabled on both the E2K7 and E2K13 OWA
    In the IIS logs:
    2015-03-02 16:36:50 <E2K13_IP> POST /owa/service.svc action=SubscribeToNotification&UA=0&ID=-25&AC=1&CorrelationID=c2899211-568d-4da4-a163-351a8621c9fd_142531419466924;&cafeReqId=7ffae082-a96f-42fd-85f8-bf23775ed5de; 443 ourdomain.com\MailboxA
    <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
    https://webmail.ourdomain.com/owa/#path=/mail 200 0 0 109
    2015-03-02 16:36:50 <E2K13_IP> GET /owa/ offline=disabled&CorrelationID=<empty>;&cafeReqId=7c8e137f-cdb7-4449-9cb8-f36f94539244; 443 ourdomain.com\MailboxA <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
    - 500 0 0 265
    In the OWA HTTP Proxy logs:
    2015-03-02T16:36:50.096Z,7c8e137f-cdb7-4449-9cb8-f36f94539244,15,0,913,7,,Owa,webmail.ourdomain.com,/owa/,,FBA,True,ourdomain.com\MailboxA,ourdomain.com,[email protected],Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
    .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0),<LoadBalancer_IP>,<Exchange2013ServerName>,500,,ServerNotFound,GET,,,,,ExplicitLogon-SMTP-Header,,,,0,,,,40,9,,0,7;,7,,0,7,,0,46.8643,0,,,,,,,,,1,10,0,,10,,50,50,?offline=disabled,,BeginRequest=2015-03-02T16:36:50.049Z;CorrelationID=<empty>;ProxyState-Run=None;ServerLocatorRefresh=beebf732-0f99-47a0-9f36-d266573f1510;RefreshingCacheEntry=CacheEntry(BackEndServer
    <Exchange2007ServerName>.ourdomain.com~1912832083|ResourceForest |LastRefreshTime 2015-03-02T16:01:29.3265514Z|IsSourceCachedData False);ProxyState-Complete=CalculateBackEnd;EndRequest=2015-03-02T16:36:50.096Z;I32:ADS.C[<DC_Name>]=1;F:ADS.AL[<DC_Name>]=6.6401;I32:ATE.C[<DC_Name>.ourdomain.com]=1;F:ATE.AL[<DC_Name>.ourdomain.com]=0,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
    The server <Exchange2013ServerName>.ourdomain.com was not found in the topology. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: The server <Exchange2013ServerName>.ourdomain.com was not found in the topology.   
    at Microsoft.Exchange.Data.Storage.ServiceTopology.GetSite(String serverFullyQualifiedDomainName)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetServiceTopologyWithSites(String serverFqdn  ServiceTopology
    topology)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer
    mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox  BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1
    operationToTrack  Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass3b.<OnCalculateTargetBackEndCompleted>b__3a()   
    --- End of inner exception stack trace ---;
    Hoping that somebody can help ?
    Thanks

    Hi Ansev,
    Thank you for your question.
    By my testing, user who was migrated to Exchange 2013 cannot access mailbox on Exchange 2007 with 500 error, although user account have “Full Access Permission” to mailbox on Exchange 2007.
    I suggest we migrate account which has “Full Access Permission” for other user  to Exchange 2013.
    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

  • ActiveSync 500 error and Exchange 2007/2013 coexistence

    Hello,
    We have Exchange 2007, and we've deployed Exchange 2013 and coexistence appears to be working.  We have done a small pilot migration of 11 users, and I have 2 of those users that are not able to get iPhone/ActiveSync working.  OWA and Outlook access
    work without a problem.  https://testconnectivity.microsoft.com/ is telling me "The test of the FolderSync command failed." and "Exchange
    ActiveSync returned an HTTP 500 response (Internal Server Error)"
    The error I'm receiving on the mailbox server event log is:
    An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case,
    Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. 
    URL=
    --- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: A null value was received for the NTSD security descriptor of container CN=ExchangeActiveSyncDevices,CN=LASTNAME\, FIRSTNAME.,OU=XXX,OU=People,DC=DOMAIN,DC=local. 
    Most articles I've found with this issue say to confirm that "Inherit parent permissions" is check on the AD object, but that is already checked?
    The funny thing is that most of our pilot users don't have this issue.  It is only for some of them.
    Any help is appreciated.

    An update here, I was able to get the 2 pilot user's iPhone/ActiveSync access working by adding the following permissions by hand:
    Add Exchange Servers, in Apply onto select
    msExchActiveSyncDevices objects (note it's plural) and selecting
    Full Control.  
    Once I did this, my problems went away.
    So the big question is why aren't these permissions in place already?  Isn't this something that the adprep/domain prep should have taken care of?
    Thanks!

  • Exchange 2013 2007 co-existence Outlook Anywhere issues

    Sorted out all other issues (apart from a SSO issue- another thread) . Activesync, autodiscover etc all working- but Outlook Anywhere does not work for Exchange 2007 external mailboxes. It does work for 2013 mailboxes internally and externally-
    and 2007 mailboxes internally.
    Exchange 2013 SP1. Exchange 2007 Sp3 RU10. Legacy namespace is in use and on certificate. Outlook Anywhere IIS Authentication is set to Basic and NTLM on both 2007 and 2013 servers.  Outlook Anywhere external client authentication is set to Basic.
    Any sugestions what to look at next?

    Tony,
    I apologize for the stupid question, but was Outlook Anywhere working on Exchange 2007 before you started the upgrade?
    When you open command prompt on Exchange 2007 and ping the Exchange 2007 internal FQDN or NetBIOS name, do you get an IPv4 address or you get the IPv6 one?
    Step by Step Screencasts and Video Tutorials

  • VS 2013 Community - Outlook 2010 issue

    I recently installed VS 2013 Professional Community on a Windows 7 Home Premium machine.  Now every time I start Outlook 2010 I get a "Windows Installer - Preparing to install" dialog, followed by a few "Microsoft Visual StudioProfessional 2013"
    dialogs that says "Please wait while Windows configures Microsoft Visual StudioProfessional 2013. . .".  I have the same installation on my laptop & it doesn't happen there.
    Anyone have any idea why, or how to resolve?
      

    Hello Scott,
    Do you have any add-ins registered for Outlook? If so, try to disable them. Does it help?

  • Outlook client requirements and Exchange 2010/2013 coexistence

    Good morning!
    A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
    I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
    including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
    Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
    Thanks in advance!

    Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • HT5312 How to reset my security questions for my Invoice2go

    How to reset my security questions for my Invoice 2go

    Apple ID security issues -
    Call Apple Care and ask for the Account Security Team. They can assist you with your issue.

  • Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

    Hi Guys,
    I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
    3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
    1 Exchange server MBX role For journlaing Exchange 2010
    1 CAS for internet owa access Exchange 2010
    Now i will be  installing exchange 2013 CAS on 2 box and MBX on 3 box 
    will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
    will keep the Journaling server as it is will not be decomming it as of now.
    My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
    to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
    Please suggest on the same.
    BR/Deepak

    Hi TheLearner,
    Thank you for your question.
    Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010  could communicate
    with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
    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

  • Outlook 2007 intermitent loss of connection at remote VPN Site

    We have some remote sites connected by IPSEC site-to-site VPN. Users run Outlook 2007 connected to Exchange 2007 at the main site.
    It is common for Outlook to go through periods of  losing and regaining connections: Outlook displays constantly connection messages. The error occurs on an intermittent basis and does not effect all users at the remote site, the problem usually
    disappears after a day. Users can get access to e-mails through OWA and this does not have the same outage errors.
    Not sure if it is related to other traffic running over VPN link but I cannot find any obvious cause.

    Hi,
    The intermittent Outlook connection issue can be caused by the following factors:
    1. Network issue.
    2. Exchange Server performance issue.
    3. Outlook client side issues.
    What’s your Exchange environment? How many Exchange servers and Server Roles?
    In Exchange 2007, Outlook directly connect to Mailbox Server. So, if you have multiple Mailbox Servers, please confirm whether the problematic users are all on the same Mailbox Server.
    You can take a performance monitor to check whether the RPC request is too high:
    http://blogs.technet.com/b/mikelag/archive/2008/05/02/perfwiz-replacement-for-exchange-2007.aspx
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • 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

Maybe you are looking for

  • Items not appearing on desktop

    I am having problems with items not showing up on the desktop. The main problem I am having is that I have a Moto Q Cell phone, which I use Missing Sync software with. It was mounting on the desktop and then stopped. Everything else works with it on

  • Can I use backup from iMac on Mac mini?

    My iMac just went into the Apple Store shop today for a new disk drive. I have a cloned backup of it from Super Duper, on an external drive. Is there any way I can boot from that drive on my Mac mini? Thanks.

  • Flash buttons problems when screen text set to medium in Windows 7

    Anyone else have this problem that when users have set windows 7 to Medium 125% screen size (not screen resolution), the clickable area on all buttons in a flash menu/file are off. It's like the area to click for the button is not resized with the gr

  • Accessing videos from other apps

    I have two questions concerning videos. 1) I have videos that I transferred using iTunes from my computer to my iPad and videos that I downloaded using a free video app.  The native Apple video app can't see the downloaded videos and conversely the f

  • Current quarter and four future quarters

    Hello Forum Members, I have a config table with the following data: Quarter Config Rep_date Q1-2006|1|1/1/2006 Q2-2006|32|4/12/2006 Q3-2006|321|7/15/2006 Q4-2006|897|12/14/2006 Q1-2007|10|2/12/2007 Q2-2007|10|5/12/2007 Q4-2007|50|11/12/2007 Q1-2008|3