Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

We are in the process of migrating from 2010 to 2013.  Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
alex serdyukov

Hi Alex,
As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
Cumulative Update 8 for Exchange Server 2013
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Similar Messages

  • 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

  • List of exchange users with mailbox size per database.

    Hello Friends,
    Need small help i need to take out the list of users start with Alphabet A, B , C till Z per database along with their mailbox size limit so is there any simple way to get the list.
    Thanks
    Amit

    Hi,
    How about this?
    http://help.outlook.com/en-us/140/gg576861.aspx
    EDIT: Or maybe this:
    $out = @()
    $users = Get-Mailbox -ResultSize Unlimited
    ForEach ($user in $users) {
    $userMailboxStatistics = Get-MailboxStatistics $user
    $props = @{
    Username = $user.SamAccountName
    DisplayName = $user.DisplayName
    Database = $user.Database
    OrganizationalUnit = $user.OrganizationalUnit
    'Quota Status' = $userMailboxStatistics.StorageLimitStatus
    TotalItemSize = $userMailboxStatistics.TotalItemSize
    $out += New-Object PsObject -Property $props
    $out | Sort-Object Database,DisplayName | Export-Csv .\mbxDetails.csv -NoTypeInformation
    Adjust the $props hash as needed to add/remove properties to the output object.
    Don't retire TechNet! -
    (Don't give up yet - 12,420+ strong and growing)

  • Exchange 2010 CAS Proxy not working

    The internet facing CAS server has internal and external url as
    https://mail.domain.com/owa
    The non internet facing CAS server has internal url
    https://servername.domain.com/owa, with windows integrated authenticaion set. No external url set.
    When I try to use OWA to access a user's mailbox that is active on a mailbox server in the non internet AD site using
    https://mail.domain.com/owa , I get the following error:
    The mailbox you're trying to access isn't available
    No Client Access server or front-end server with a matching version was found to handle the request.
    Exception message: The CAS server is most likely not configured for SSL (it returned a 403)
    However, All Exchange servers are running the same version.
    If I try to access the user's mailbox using
    https://servername.domain.com/owa it works fine
    Anand_N

    Hi,
    Check the event viewer application logs.
    I have seen the same issue and the resolution is given in the event logs.
    I think you might have to change the SSL settings on the non-internet facing CAS or there is some regisrty settings.
    AllowProxyingWithoutSSL
    Also, check below link
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26671364.html
    http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.setup/2013-02/msg00000.html

  • Exchange 2010 public folder not showing on exchange 20003 mailbox

    Hi,
    I have public folder on exchange 2003 and separate public folder on exchange 2010. On exchange 2010 user mailbox, I can see both 2003 and 2010 public folders. On exchange 2003 user mailbox, I can only see 2003 public folders. It is not the permission issue
    as I have given the user "owner" right and see not able 2010 public folder inless i move 2003 user mailbox to 2010 exchange.
    Appreciate if anyone could help me if to point me to directions or any hotfix I can run?
    Thank you very much.
    Pwint

    Are you using OWA or Outlook to view the public folders?
    If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
    If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
    It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
    like authentication.

  • Some errors in creating AD user with mailbox enabled

    Dear adler Steven / all,
    I followed all your posts and able to create AD user with mail box enabled, Now i am able to send and receive mails for this user.
    But the user in AD is disabled , that is it is not with the icon of an enabled user but it has an icon of user with a cross marked in Red.
    i have given the successful coding below:
    attrs.put("cn","chngcode");
    attrs.put("instanceType","4");
    attrs.put("objectCategory","CN=Person,CN=Schema,CN=Configuration,DC=csindia,DC=com");
    attrs.put("objectClass","top");
    attrs.put("objectClass","person");
    attrs.put("objectClass","organizationalPerson");
    attrs.put("objectClass","user");
    attrs.put("mailNickname","chngcode");
    attrs.put("mail","[email protected]");
    attrs.put("sAMAccountName","chngcode");
    attrs.put("msExchHomeServerName","/o=CYGNUS_O/ou=CSINDIA/cn=Configuration/cn=Servers/cn=CSISERVER2");
    attrs.put("objectCategory","CN=Person,CN=Schema,CN=Configuration,DC=csindia,DC=com");
    attrs.put("userPrincipalName","[email protected]");
    attrs.put("distinguishedName","CN=chngcode,CN=Users,DC=csindia,DC=com");
    attrs.put("instanceType","4");
    attrs.put("mDBUseDefaults","TRUE");
    attrs.put("name","chngcode");
    attrs.put("replicatedObjectVersion","0");
    attrs.put("legacyExchangeDN","/o=CYGNUS_O/ou=CSINDIA/cn=Recipients/cn=chngcode");
    attrs.put("givenName","chngcode");
    attrs.put("displayName","chngcode");
    // Create the context
    Context result = ctx.createSubcontext(userName, attrs); Help me on further process :
    -How to solve the above bottle neck , Is any thing missed for above?
    - I have not set the password thru codings. what to do on this ?
    -When/where to use the homeMDB attributes ( Is it necessary to use this homeMDB ? )
    -How to create the mailbox with in a store ? (Presently i have created the mail box in Recipients container for this AD user)
    Expecting your early enlightening on this..
    Advanced thanks for your efforts.
    By,
    Softeek.

    If you refer to the post titled "JNDI, Active Directory (Creating new users & demystifying userAccountControl)" at http://forum.java.sun.com/thread.jspa?threadID=582103&tstart=15 you wil notice that because of the stricter security in Windows Server 2003 Active Directory, user accounts created with null passwords are automagically disabled.
    To enable new user accounts you must assign a password (that meets the security policy !) and then enable the account.

  • Exchange 2010 SP1 Update Rollup 6 to Exchange 2010 SP3

    Hi there,
    I am planning to install Exchange 2010 SP3 next week and after reading some of the related comments on this site I got a little worried.
    Our current Exchange environment consists of the following:
    1 x CAS/HT Server
    2 x Mailbox Server (members of a DAG)
    The OS of the 3 servers is Windows Server 2008 R2 SP1. All servers are running Exchange 2010 SP1 Update Rollup 6.
    The Execution Policies on our Exchange servers are set as follows:
    – CAS/HT Server:
      Scope ExecutionPolicy
      MachinePolicy Undefined
      UserPolicy Undefined
      Process Undefined
      CurrentUser Undefined
      LocalMachine Unrestricted
    – Mailbox Servers:
      Scope ExecutionPolicy
      MachinePolicy Undefined
      UserPolicy Undefined
      Process Undefined
      CurrentUser Undefined
      LocalMachine RemoteSigned
    Please note that we do not have any Group Policies that defined the PowerShell script execution policy.
    I would be very grateful if you (or any of the kind readers) could help me with following questions:
    1- Do I have to change the execution policy on our Exchange servers before installing SP3? If I have to change a policy, what should I change? And how would you recommend I should do this?
    2- After installing SP3 on a server, can I install the latest rollup update on this server before moving to the next server? For example, can I do the following:
      i. Install SP3 followed by RU 5 on the CAS/HT server -> Apply the our custom settings
      ii. Install SP3 followed by RU 5 on the first mailbox server
      iii. Install SP3 followed by RU 5 on the second mailbox server
    Many thanks,
    M

    Hi Amit,
    Many thanks for the swift reply.
    That's correct.  We didn't set the Powershell execution policy via Group Policy.  We only configured the execution policy of "LocalMachine" to "Unrestricted" on the CAS/HT server using the "Set-ExecutionPolicy" command on the server.
    The mailbox servers' execution policies have not been changed and are set to those values by default.
    I must admit, I go event more confused when I read the "http://support.microsoft.com/kb/2668686" and "http://support.microsoft.com/kb/2810617" articles.
    But it looks like I shouldn't worry as our current Powershell execution policies shouldn't affect the upgrade. Right?

  • Exchange 2010 - Outlook is dropping connections to Exchange servers

    Hello Everyone,
    I need some help in an urgent case that I'm dealing with.
    We are running Exchange 2010SP3 with RU4, using external load balancer (F5).
    This morning we got complains from any single user on our system telling that their Outlook clients is showing "Disconnected" or "Trying to connect" status.
    First thing that we checked was if their mailboxes are accessible from OWA - the answer is yes.
    Connection status is starting with "Connecting" then dropped.
    We thought maybe it is coming from one of the CAS servers, so we started by removing each of the two servers at a time, but this helped only for few minutes, OWA was accessible and Outlook could connect to the servers, after few minutes, the connection was
    dropped again.
    MS Remote Connectivity checks are passing so it is even unclear because we are failing to see what and where is the real issue.
    No errors on the hosts.
    Any advice here? We have 300 disconnected users.

    Do the Outlook clients connect through the F5 as well?
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 (SP3 - withn SBS2011) OWA seach not working

    I know such issues have been reported many times in the past, but I haven't found any report for SP3 (which actually thought would resolve this for good).
    I had the same problem repeatedly with SP1, with SP2, with various rollups, I have tried the various vix solutions (re-touching AD schema, rebuilding the indexes etc.) and indeed they fix the problem... for a while.
    Or until the next update.
    Can someone help me reach a more stable solution?
    Or is it a common issue that Microsoft actually cannot solve for good???
    Right now I have the problem (again) after installing SP3. So I am open to all proposals.
    NLS

    Hi NLS,
    I'm researching the issue and will update it soon.
    By the way, for SBS issue, you can also seek the solution in the SBS forum, thanks:
    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/threads
    Frank Wang
    TechNet Community Support

  • SBS 2011 Exchange 2010 Server Error in '/owa' Application

    I have some configuration issues somewhere and haven't been able to track down the culprit. I get the 
    Server Error in '/owa' Application
    runtime error after I log into the remote website and click on email. Activesync is working fine, email though a client works fine. If I just go straight to remote.landisoffice.com/owa I am prompted for credentials, when I enter them, I get a webpage cannot
    be found error in IE. I get the same result when I try to browse from the exchange server. are there iis logs that might help me track down the cause? I've found several threads on this error, but none seem to be the same issue. I am running rollup 7 for sp3
    already.
    I've also noticed that if I go to http://remote.landisoffice.com/owa I get the page not found, but if I go to https://remote.landisoffice.com/owa I get the above mentioned error page.

    Hi Rodge,
    Please use
    SBS BPA and Exchange BPA, then check if find some relevant issues.
    Meanwhile, please run
    Test-OwaConnectivity |FL command in the EMS. Any find?
    Please also navigate to:
    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET File and check if find owa directory. If find, please change it to owa.old, then restart IIS and monitor the result.
    à
    Server Error in '/owa' Application
    By the way, would you please let me know the complete error message that you can get. Or provide a screenshot
    of it (please hide all proteted or private information).
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

    Hi guys (and girls)!
    Hear me up. The idea is like this:
    A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
    doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
    Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
    because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
    One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
    with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    bostjanc

    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    already answered by PS CL above
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    Just install the Edge Transport Server and make sure you install ADLDS services.
    as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
    Where Technology Meets Talent

  • Deleting mailbox without removing user object? Exchange 2010

    In Exchange 2010, How can I delete a mailbox but keep the User Object since this user still access the network??

    Caution: Horror story ahead:
    Yeah, well, the earlier bits of Exchange 2010 don't let you remove Exchange without first removing the mailbox from the mailbox database... this is according to MSFT documentation.  So I highlighted all the users at a customer's 130 user site and clicked
    remove.  S.O.A.B.!!!!  Only to find out one of the other senior techs did the same thing at a 10 user site but didn't tell anybody.
    The worst thing here is that there were no backups of AD.  We were able to restore the deleted user accounts via the aduser tool from sysinternals, but it only got the sam name and the SID, no group memberships, no passwords, not even first name, lastname
    or UPN.  Since AD comes with the recycle bin disabled (dumb because you don't know you have to enable it until you need it.) and the new Windows Server Backup doesn't let you take system state backups without lots of hassle dedicating drives and backup
    locations, we found ourselves royally um... humped.  Still dealing with the after math after restoring the objects for over 6 hours.
    Thanks for the egg on my face MSFT!

  • Can't manage distribution group from Outlook with Exchange 2010 or Exchange 2013 mailbox

    Hi All,
    In my environment we are using exchange 2010 that contains the distribution groups which has been migrated from exchange 2003 environment .On that one of the distribution group is having an problem for the user who had an access to manage DL'S via outlook
    but he can't able to manage it.When we add the new user to manage same DL and the new user tries to manage the DL via outlook it happens without any issues. 
    issue occurs only for the user who has already have the manage access permission on the DL where the group was on exchange 2003 before migrated to exchange 2010.
    Reffered blog : http://support2.microsoft.com/kb/2586832?wa=wsignin1.0
    We have done all the settings defined on the above mentioned link but still we are facing the issue.
    In addition to that , we have forcefully upgraded the DL too by using the below mentioned command.
    set-distributiongroup -identity "name of the problematic DL" -forceupgrade
    Please all of you provide your valuable suggestions to overcome this issue .
    Error message :
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

    Hi S.Nithyanandham,
    From your description, I would like to verify if the problematic manager user is a member of security group. If yes, this issue will occur. In Exchange 2010, distribution groups can't be managed by groups, only individual users can manage groups. But in
    Exchange 2003, it is possible to use groups to manage a distribution group.
    For more information, here is a blog for your reference.
    How to manage groups with groups in Exchange 2010
    http://blogs.technet.com/b/exchange/archive/2011/05/04/how-to-manage-groups-with-groups-in-exchange-2010.aspx
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2010 users cant change password in OWA when Cas server is Exchange 2013 cu3

    Running Exchange 2010 and 2013 in mixed mode.  users who is still on Exchange 2010 cant change password in OWA. It worked when it was clean Exchange 2010 installation. Password change is working for users migrated to 2013
    LS

    Hi
    Please follow the below blog which will help you in solving this issue
    http://technet.microsoft.com/en-us/library/bb684904.aspx
    Note: Be careful while modifying the registry settings.
    Please 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.
    Regards,
    Sathish

  • 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

Maybe you are looking for