Exchange 2007 to 2013 Migration Outlook Anywhere keeps asking password

Hi all, 
i'm migrating an Exchange 2007 Server with all roles installed on a Windows Server 2008 R2 to 2 Exchange 2013 SP1 Servers (1 Cas and 1 Mailbox) installed on Windows Server 2012 R2.
I installed Exchange 2007 SP3 RU13 for coexistance and everything was ok until i switched to the new 2013 CAS. 
After that the client using Outlook Anywhere started asking for password. 
I configured the Outlook Anywhere with these settings:
Exchange 2007:
OA Hostname mail.domain.com
Client Authentication NTLM
IISAuthenticathion Basic, NTLM
SSL Required True
Exchange 2013
OA Hostname mail.domain.com
Client Authentication NTLM (Both internal and external)
IISAuthentication Basic, NTLM
SSL Required True (both internal and external)
Before switching to 2013 Cas everything works smoothly and the Outlook clients receive NTLM as HTTP Proxy authentication.
After switching to 2013 Cas, test users migrated on 2013 Mailbox Server are ok, but Outlook users on Exchange 2007 Server get Basic as HTTP Proxy authentication and continue asking for credentials. 
In the Exchange 2007 server i configured the host file to resolve servername and servername.domain.local with the ipv4 address to avoid issues regarding IPv6 with OA in Exchange 2007. 
Using Microsoft Connectivity Test i receive the error "RPC Proxy can't be pinged - The remote server returned an error:
(500) Internal Server Error"
Any Ideas?
Thanks for your Help

Run this and post the result
https://testconnectivity.microsoft.com/
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.

Similar Messages

  • Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

    Exchange 2013 Migration issues
    I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
    Environment:
    Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
    http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
    Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
    Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
    I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
    to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
    Here is a Get-OutlookAnywhere cmdlet...
    ServerName                         : EXCHANGE2007SVR
    SSLOffloading                      : False
    ExternalHostname                   : legacy.domain.com
    InternalHostname                   :
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Basic
    IISAuthenticationMethods           : {Basic}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : False
    MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
    Path                               : C:\WINDOWS\System32\RpcProxy
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 8.3 (Build 83.6)
    Server                             :
    EXCHANGE2007SVR
    AdminDisplayName                   :
    ExchangeVersion                    : 0.1 (8.0.535.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                         Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                         Groups,CN=DOMAIN,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
    Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
    Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
    ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 12/31/2013 4:08:04 PM
    WhenCreated                        : 7/18/2008 10:56:46 AM
    WhenChangedUTC                     : 12/31/2013 9:08:04 PM
    WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
    OrganizationId                     :
    OriginatingServer                  : DC1.domain.local
    IsValid                            : True
    ObjectState                        : Changed
    ServerName                         :
    EXCHANGE2013SVR
    SSLOffloading                      : True
    ExternalHostname                   : webmail.domain.com
    InternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
    Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 15.0 (Build 775.38)
    Server                             : EXCHANGE2013SVR
    AdminDisplayName                   :
    ExchangeVersion                    : 0.20 (15.0.0.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                         Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                         Groups,CN=DOMAIN,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
    Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
    Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
    ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 1/7/2014 11:29:05 AM
    WhenCreated                        : 12/31/2013 1:17:42 PM
    WhenChangedUTC                     : 1/7/2014 4:29:05 PM
    WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
    OrganizationId                     :
    OriginatingServer                  : DC1.domain.local
    IsValid                            : True
    ObjectState                        : Changed
    ISSUE 1
    Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
    [email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
    I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
    to say "CONNECTED", but it works regardless.
    No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
    ISSUE 2
    Migrated user is unable to open Public folders from Exchange 2007.
    Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
    This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
    ISSUE 3
    Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
    2010). I'm assuming that isn't supported.
    In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
    When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
    Current workaround is just disabling them through OWA.

    Hello,
    In order to avoid confusion, we troubleshoot a issue per thread usually.
    For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
    Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
    For the second issue and third issue, please create a new post.
    If you have any feedback on our support, please click here
    Cara Chen
    TechNet Community Support

  • How to migrate from exchange 2007 to 2013 step by step tutorials please

    Hi
    I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
    We have 800 mailbox in total
    Our domain controllers are
     Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
    I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
    Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
    I currently only have 1 exchange server 2007, with all the roles on the one server.  I would like to keep that same as
    well with exchange 2013.
    Thanks

    Exchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
    You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
    migration task in more secure way.

  • Free/Busy not working Exchange 2007 and 2013 co-existence

    Hi,
    I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
    works correctly, but between Exchange 2007 and 2013 it's not working.
    I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
    The internal and the external URLs are set to https://legacy.mydomain.com/....
    What am I missing?
    Thanks & Kind Regards,
    Jürgen

    Hi,
    According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
    1. Does the issue happen to all users or specific users?
    2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
    3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
    create a new Outlook profile
    to have a try.
    4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
    Virtual directories settings in Exchange 2007:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Certificate and Virtual directories settings in Exchange 2013:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
    5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
    If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2007 and 2013 coexistence

    Hi,
    we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server)  i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
    I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
    Thanks

    Hello,
    Please check your DNS configuration and ISA/TMG rules.
    We recommend you use TMG or UAG.
    You can refer to the "TMG rules" section in the following article:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Cara Chen
    TechNet Community Support

  • Exchange 2013, Outlook 2007 clients Problems with Outlook Anywhere connection

    Hi everyone,
    I have a mail system Exchange 2013 SP1, on Windows Server 2012 R2.
    I have only one mail server with the Client Access and Mailbox roles Server. 
    I have a Wildcard certificate type *. Mydomain.com. 
    All connections to the Outlook Anywhere Outlook 2010, Outook 2013 work correctly. 
    The ActiveSync connections are working properly, too. 
    But Outlook 2007 clients connecting with Outlook Anywhere asking for credentials continuously fail continuously. 
    How can I solve this? 
    thank you very much
    Microsoft Certified IT Professional Server Administrator

    Hi,
    Based on my experience, we need to set Outlook provider with the domain name if it's wildcard certificate:
    Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
    http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
    Thus, I recommend you try the above configuration and test the Outlook connection again.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Can only access emails through OWA after migration from exchange 2007 to 2013

    can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
    needed RCA ... plz help..

    Hi,
    From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
    In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • Issue moving remote user from exchange 2007 to 2013

    have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
    during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.  
    outlook was working connecting to both servers, and OWA was working on both servers.
    couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
    but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
    if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
    when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
    could this have caused my outlook connectivity issue?
    I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    any suggestions?

    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    Hi,
    Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
    According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
    Please try to logon OWA to check whether this user works.
    If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
    Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
    Please try to run Outlook under safe mode to avoid AVs and add-ins.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Legacy Namespace for Exchange 2007 to 2013 co-existence

    We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
    are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
    need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
    I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
    Thanks in advance for your help.

    In coexistence with exchange 2013 and legacy version the request happens in 2 types.
    For Exchange 2010 –
    Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
    For Exchange 2007 –
    Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
    Certificates:
    All the required SAN entries for UM,webservices and activesync should be created.
    Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
    Exchange 2013 only then owa redirection will work.
    You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
    Existence.
    Following change needs to be done in Firewall
    External OWA URL should be directed to exchange 2013 Internet Facing CAS.
    External EWS URL should be directed to  exchange 2013 Internet Facing CAS.
    External Autodiscover URL should should be directed to  Exchange 2013 CAS.
    External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
    External UMvirtualDirectory should be directed to  Exchange 2013 CAS.
    Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
    a mailbox on Exchange 2007.
    External and Internal DNS settings
    Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
    exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
    Example:
    Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
    Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
    facing exchange 2013 CAS FQDN
    Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
    Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
    address
    The internal DNS records should point to the internal host name and IP address of your Exchange
    2013 Client Access server
    Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
    Authentication Settings:
    This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
    Set the owa virtual directory authentication only to  Basic in exchange 2007.
    In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
    Things to check:
    If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
    Virtual Directories doesn’t have it configured.
    If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
    For further references you can refer my article below
    http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
    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 Thanks Sathish (MVP)

  • Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

    I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
    as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
    Symptoms:
    Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
    from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
    URL to connect to my proxy server for Exchange: webmail.domain.com
    Connect using SSL only: Checked
    Only connect to proxy servers that have this principal name in their certificates: Unchecked
    On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
    On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
    After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
    first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
    Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
    Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
    domain: blank
    username: their AD username
    server: webmail.domain.com
    After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
    begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
    for mobile users in the same way that it's been working for us with Exchange 2010?
    Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

    Hi,
    Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
    Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
    fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
    Please restart the following Exchange service to have a try:
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Mailbox Replication
    Restart IIS service by running IISReset in a Command Prompt window.
    Then check whether the Outlook client can connect to Exchange 2013 or not.
    As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
    Regards,
    Winnie Liang
    TechNet Community Support

  • ActiveSync in Exchange 2007 and 2013 Coexistence

    Hi,
    I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
    owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
    autodiscover works well for users on both 2007 and 2013
    I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
    I have A records configured for both names on my public DNS and internal DNS
    THE ISSUES
    testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
    New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
    Existing users on exch2007 can no longer receive mails on their mobile devices
    URLs
    Exchange 2007
    Exchange 2013
    Internal owa
    mydomain.com/owa
    mail.mydomain/owa
    External owa
    legacy.mydomain.com/owa
    mail.mydomain.com/owa
    AutoDiscover
    mail.mydomain.com
    mail.mydomain.com
    EWS
    legacy.mydomain.com
    mail.mydomain.com
    ECP
    mail.mydomain.com
    Internal ActiveSync
    legacy.mydomain.com
    mail.mydomain.com
    External ActiveSync
    $null
    mail.mydomain.com
    OutlookAnywhere
    legacy.mydomain.com
    mail.mydomain.com
    I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
    Any help on this would be much appreciated ..
    Richard ..
    ..forever is just a minute away*

    You don't need to use a legacy URL for ActiveSync in Exchange 2013.  It will proxy ActiveSync for Exchange 2007 just fine.  In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition.  I recommend
    you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Icloud keeps asking password in iPhone

    Absolutely exasperating.
    On iPhone 5, since a week iCloud keeps asking passwords, and telling me password is incorrrect.
    Then, it says account is unavailable. Then it says it cannot retrieve mail.
    On Macs, all accounts perform flawlessly.
    But, previously, I had a problem with password since many weeks being not recognized by iCloud even from Macs.
    Passwords ARE correct.
    I tried everything (close iCloud, suppressing/recreating account, reinitializing password, reinitializing iPhone,
    reinstalling iOS, etc.).
    I saw many threads related, since a year or so, and no apparent solution.
    Apple is not often annoying, but here they really need to clean their act with this.

    If you've restored the iPhone to factory settings without a backup, re-added the iCloud account on the device and still have those issues, I'd recommend you call AppleCare

  • Can't sign into apps tore account. keep asking password. help

    hai, guys.. mine is pro 10.8.3. the beginning was had problem with previous purchase. then, can't sign into my account and neither the billing info. endless loop. keep asking password. what should i do?
    thank u in advance

    iTunes 9.0.2.
    Trouble logging in for a couple of days.
    1. Always have logged in with my username only.
    2. Now requires me to login with my [email protected]
    3. When I log in with my [email protected] my account details (top-right hand corner of iTunes store) states [email protected]
    4. All my previous purchases state in Info that my Account name is just username.
    5. Now logging in with [email protected] ([email protected]) any new purchase list the Account name as [email protected]
    6. My account two days ago (just username) had credit on it. Now its gone because I can no longer log in under that account.
    7. All purchases under that account that have updates are not available because I cannot log in.
    ITunes & iPhone error message:
    This Apple ID is not available.
    Also, tried logging in to send this reply and I received the message This Apple ID has been disabled for security reasons. Why???
    So I reset my password - to the same password and had a few teething problems, but have now managed to login.
    Note: me.com has not been affected. There has been no issues with my login for my me.com account.
    But wait there is more....
    I just thought I would try it again, because I had just reset the password through Apple Discussions, and I can now login with just my username in iTunes. All seems to be working as per usual.
    Why there has been an issue with iTunes and Apple Discussion, and not with logging in to http://www.me.com - I don't know???
    Perhaps this will fix your problem as well - reset your password.
    Weird!

  • Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

    Hi
    We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
    I'm now testing with a few test users I've migrated from 2007 to 2013.
    Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
    Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
    When I start Outlook, I get the error Unable to open the default mail folders
    When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
    When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action" 
    Thanks for any help you could provide
    Martin

    Changed the
    ExternalClientAuthenticationMethod  for the 2007 server.
    Output for  Get-OutlookAnywhere | fl *method*
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
    asking for credentials.
    If I dig further and try to manually configure server settings:
    If I specify the Exchange 2013 server and try a 'Check
    Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
    If I specify the Exchange 2007 server and try a 'Check
    Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
    Any other thoughts on this issue?
    Thanks,
    Martin

Maybe you are looking for

  • Production order q's

    Hi all , 1) What should be the selection criteria in COOIS  for open production order list for the one month frame ? 2) How can we know that for a production order Overhead , Varience, Settlement has been carried out if the production if the order is

  • Windows SDK Import Libraries

    Hi, I am trying to use win32 calls that are not included in kernel32.lib, gdi32.lib and user32.lib thus I have to add import libraries to the project. Reading cvi\sdk\sdkfuncs.txt I determined that the three functions I need (cmc_logon, cmc_logoff an

  • My droidx is stuck in an infinite loop at the start-up

    Hello, I turned my droidx on yesterday and it can't get past the red eye. It freezes on the redeye then goes back to displaying "droid" then back to the redeye and it just continues this loop indefinitely. Anyone know how to fix this? Thanks in advan

  • Call procedure question

    Dear all, Is there any different from calling PL/SQL Function, PL/SQL Package and PL/SQL Procedure in Jdev. by using "getDBTransaction().createCallableStatement"? Because it works when I call the function but does not work in package. Why? Any sugges

  • Coldfusion 4.5 and Windows Server 2003

    We have to move a web site to a Windows 2003 Server. The site was developed using CF 4.5 and SQL Server 2000. The new server will have Windows 2003 Server along with SQL Server 2005. Will CF4.5 work on the new environment or will an upgrade be necess