Exchange 2013 - Proxy through client access server not working

Hello All -
I recently migrated our company to Exchange 2013 and noticed that our email was leaving through the mailbox server. I put a check mark in the Send Connector where it says "Proxy through Client Access Server" and my mail is still coming from the
mailbox server. How can I go about fixing this problem?
Environment:
1 CAS Server
1 Mailbox Server
Both server are behind the firewall with only port 25 opened to the CAS. The CAS has a Send Connector to a smart host for all messages.
Thank you!
Ryan

Hi,
Please check if the outbound messages without smart host are coming from CAS . 
I doubt it send to the smart host directly if you configure smart host, and not use proxy thogh CAS.
If you have any feedback on our support, please click
here
Wendy Liu
TechNet Community Support

Similar Messages

  • Exchange 2013 - 2007 coexistence - activesync 2007 does not work correctly

    Exchange 2013 SP1.  On going Saga-  Last night we cut over to full co-existence with DNS changes for use of legacy namespace and had to roll back again. We had only two issues but one was considered a show stopper.
    The main issue was that Active Sync would not work correctly for 2007 users. It failed the exchange connectivity test and would only work on a device if the domain was entered - or if the legacy namespace was entered manually. That would have meant
    chaos for several thousand users so we rolled back. (It worked perfectly for 2013 users).
    The error given by the test was "foldersync failed" when I drilled down into the detail. It found autodiscover but failed after the initial handshake. (All other tests passed for 2007 and 2013 users)
    We tried:
    1. Populating both Autodisover internal and external urls with the legacy namespace
    2. Populating only the internal url and leaving the external blank (both 1 and 2 had the same result)
    3. Leaving both URLs blank to force 2013 to proxy to the 2007 cas (totally broke it- would not resolve at all)
    I don't know if this is related but SSO is failing for 2007 OWA - two prompts.
    Environment notes- all internal co-existence is working and the internal LTM F5's are working. Externally we use 2 GTM F5 to the LTM f5's to Ex2013. 2007 has SSL being passed through all the way to the CAS. Servers are split into CAS and MBX over 2 DC's.
    Everything else externally was working when we cut over.
    any and all help appreciated
    Tony

    Hi,
    Glad to know that you have found the solution.
    Thanks for your generous sharing.
    Have a nice day : )
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • SCAN (Single Client Access Name) not working properly

    We are in the process of upgrading to 11.2.0.1.0 RAC (4 nodes) running Grid Infrastructure and SCAN via DNS. The setup went great as did the data pump. However when trying to connect to the SCAN address I am getting an ORA-12154 error. My TNS entry is as follows:
    FMRQ=
    (DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=TCP)
    (HOST=ncc1701rac-scan.dsd-k12.net)
    (PORT=1521)
    (CONNECT_DATA=
    (SERVER=shared)
    (SERVICE_NAME=fmrq)
    If I change my Service_Name to be fmrq1, fmrq2, fmrq3, or fmrq4 which just so happen to be the SID's for each of my nodes I am able connect. I'm sure that I have missed something simple, but due to the lack of detailed documentation about how SCAN works I am not able to troubleshoot this on my own. Help is most definitely needed.

    Thank you for the reply. I have been trough that document several times trying to see if I missed anything. This all seems very straight forward which is why I am so confused as to why it isn't working. I have noticed that when I run "lsnrctl status" I see
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.6.22.41)(PORT=1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.6.22.51)(PORT=1521)))
    Services Summary...
    Service "+ASM" has 1 instance(s).
    Instance "+ASM1", status READY, has 1 handler(s) for this service...
    Service "fmrq" has 1 instance(s).
    Instance "fmrq1", status READY, has 2 handler(s) for this service...
    The command completed successfully
    but when I run "lsnrctl status fmrq" I see:
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER_SCAN4)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.6.22.34)(PORT=1521)))
    Services Summary...
    Service "fmrq" has 4 instance(s).
    Instance "fmrq1", status READY, has 2 handler(s) for this service...
    Instance "fmrq2", status READY, has 2 handler(s) for this service...
    Instance "fmrq3", status READY, has 2 handler(s) for this service...
    Instance "fmrq4", status READY, has 2 handler(s) for this service...
    The command completed successfully
    So by this should my service_name "fmrq" work correctly?

  • Exchange 2013 - Cleaning UP logs files (Client Access Server)

    I have to client access server and it is running out of space
    Is there anywhere in the C:\ drive where I can delete some space (e.g. log files)

    Hello,
    If you refer to C:\inetpub\logs\LogFiles, you can delete them manually or use a Powershell script to delete them.
    Here is the similar thread for your reference.
    http://social.technet.microsoft.com/Forums/exchange/en-US/703dc324-721e-4c52-b43a-263b5543cfda/how-to-control-iis-logs-on-cas-server?forum=exchange2010
    If you refer to other log files, please free let me know.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

    Hi all,
    I could really do with your help!
    We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site.  Site C has links to both sites A & B, but the link is a lot slower.
    We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites.  Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
    however we can have both roles on the same server if required.
    What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
    From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
    I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
    Has anyone else come across this situation and how did you get round it?
    Thanks in advance :)

    Hi Johnson,
    Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
    Please check whether the CAS server that in site C is healthy.
    If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
    Also found a useful blog for your reference:
    Exchange 2013 Client Access Server Role
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • EWS - Office 365 - "One or more subscriptions in the request reside on another Client Access server. GetStreamingEvents won't proxy in the event of a batch request."

    Hello
    My goal is to subscribe for streaming notifications for multiple users in the same time.
    One way to do that is to create multiple  StreamingSubscriptionConnections each one should contain one  StreamingSubscription for each user. The problem with this method is that in Office 365 the maximum
    number of connections opened is 20.
    Another method to solve this problem is by creating one StreamingSubscriptionConnection and then all StreamingSubscriptions for each user to the connection. This method solves the maximum number of connections
    problem and it works fine with exchange onPrimises. But when trying it with Office 365 it will result with the SubscriptionError:
    "One or more subscriptions in the request reside on another Client Access server. GetStreamingEvents won't proxy in the event of a batch request."
    Can anyone help me here ? 

    With Office365 you need to Group your subscriptions and set the Affinityheaders see
    http://msdn.microsoft.com/en-us/library/office/dn458789(v=exchg.150).aspx and
    http://blogs.msdn.com/b/mstehle/archive/2013/07/17/more-affinity-considerations-for-exchange-online-and-exchange-2013.aspx . Take note of the restrictions on the Group and other throttling restrictions if your using only one service account.
    Cheers
    Glen

  • Office 365 Streaming Notifications, "One or more subscriptions in the request reside on another Client Access server."

    Hello all,
    I am maintaining a part of our product that requires monitoring mailboxes for events.  This is currently being done by using streaming connections for getting the notifications.  Our solution has been successful for situations with smaller numbers
    of mailboxes, ~200 or less.  However we are seeing some issues when scaling up to say, 5000 mailboxes.
    The error and the sequence leading up to it are as follows:
    Make an Exchange Service Account.
    exchSvc.ConnectionGroupName = someGroupName;
    add to the httpheaders ("X-AnchorMailbox", userSmtp) and ("X-PreferServerAffinity", "true");
    create a new impersonated UserId for the userSmtp address that is our anchor mailbox.
    set the Exchange Service account ImpersonatedUserID to the one we just made.
    ExchangeServiceAccount.SubscribeToStreamingNotifications(new FolderId[] { WellKnownFolderName.Inbox }, _mailEvents);
    to this point everything was successful, saw no error messages.
    we create a second impersonated UserID for a different mailbox, and repeat the process above from that step forward.  Upon the final step, subscribing to the streaming notifications we get the error:
    Exception: Microsoft.Exchange.WebServices.Data.ServiceResponseException: One or more subscriptions in the request reside on another Client Access server. GetStreamingEvents won't proxy in the event of a batch request.
    This is only the second subscription that we are trying to add to this connection, and it is to a different mailbox than the first.
    Can anyone please help point me to where this is going wrong?

    >> Is there a good way to verify the number of subscriptions in a group?
    Not that I know of you should be tracking this in your code there are no server side operations in EWS to even tell you if there are active subscriptions on a mailbox.
    >>The error I am getting is on the second subscription in a new group, just after doing the anchor mailbox so I don't think we are hitting the 200 limit. 
    It's hard to say without seeing your code but it sounds like there is problem with your grouping code. One way to validate this is that with every request you make with the EWS managed API there is a
    RequestId header http://blogs.msdn.com/b/exchangedev/archive/2012/06/18/exchange-web-services-managed-api-1-2-1-now-released.aspx
    you should be able to give that RequestId to the Office365 support people and they should be able to check the EWS Log on the server and tell you more about what's happening (it maybe server side bug). Something doesn't quite add up in that the X-BackEndOverrideCookie
    is what ultimately determines what server the request ends up at and the error is essentially telling you its ending up at the wrong server (have you looked at the headers on the error message?). Is it always one group of users that fails have
    you tried different groups and different combinations etc.
    Cheers
    Glen

  • Exchange 2013 Give domain Admin access to all users inbox

    In the old 2007 exchange server we had domain admin access to everyones mailbox so we could open anyones email box using outlook client.
    But in 2013 exchange the mailbox delegation does not give us the option to add a "group" to the full access area, old allows to add a "user" who has a mailbox setup in exchange. I see there is Exchange Server group listed under Full Access
    , but it does not work added our domain Admin user to that group rebooted exchange and the test machine but did not work.
    Only option that works to allow mounting of xyz users mailbox via abc admin user is to actually add that abc admin user to the xyz mailbox under mailbox delegation > Full Access.
    Is  there a work around this, so we can simply have a group ABCD with user ABC or DEF etc. etc. so they can access everyones mailbox instead of going in and changing all users mailbox delegation one by one for the new user etc. ?

    Have you tried using the Exchange Management Shell?
    Get-Mailbox | Add-MailboxPermission -User Name_of_Group -AccessRights FullAccess -InheritanceType All
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    I did i tried get-mailboxpermission and other than NT Authority and the end user the Deny was set to True for all inheritance rights. I tried your command, added user to the group i wanted under Enterprise OU in AD and restarted transport on exchange and
    logged in on the test machine again.
    Still no go, the user I am trying to add when using get-mailboxpermission shows up as Denied for fullaccess so is that overriding the group permissions ?
    RunspaceId      : 2xxxxxxx0
    AccessRights    : {FullAccess}
    Deny            : True
    InheritanceType : All
    User            : domain\abc
    Identity        : domain/Users/xyzuser
    IsInherited     : False
    IsValid         : True
    ObjectState     : Unchanged
    And for the group i just added with the above abc user inside it:
    RunspaceId      : 2xxxxxxxxx0
    AccessRights    : {FullAccess}
    Deny            : False
    InheritanceType : All
    User            : domain\newgroupadded
    Identity        : domain/Users/xyzuser
    IsInherited     : False
    IsValid         : True
    ObjectState     : Unchanged
    So is the users deny is causing this ? Not really sure why ABC domain admin/enterprise admin is the only one listed as no deny, there are other mailbox users that do not show up, I am assuming I have to create a new user a domain local user and that might
    work ? I wanted the Domain/Enterprise Manager/admin to have access so we would not have to keep toggling between users just to access someones inbox.
    Also further down the list of mailboxpermission i see the user abc (the user i want to add to the group to have access) is listed with Full access and Deny flag is set to False instead of True.
    So have two entries for user abc one with deny flag set to true and one with deny flag to false.
    AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
    Deny            : False
    InheritanceType : All

  • Can i upgrade exchange 2007 to exchange 2013 on same small business server 2008 machine?

    Hi,
    I have small business server 2008 with exchange 2007 installed in my organization,
    Now I need to upgrade exchange 2007 to exchange 2013 on same small business server 2008 standard edition.
    I already tried to upgrade but not successful.
    can i upgrade exchange 2007 to exchange 2013 on same small business server 2008 machine or any alternate through which it is possible.
    Please share any MS article if it not possible. 
    Thank you in advance
    Regards
    arun av

    Hi Arun,
    Its really great that you want to move and upgrade old Exchange to new Exchange server. The manual steps and guide is already recommended to you.
    Moreover, I would like to recommend you to use an automated tool to upgrade your Exchange server 2007 to exchange 2013.  I have tried and test tool to do Exchange Migration 2007 to 2013. You can follow the link 
    http://www.exchange2007to2013migration.exchangemigrationtool.com/. It will also help you to do Intra-Cross forest migration if you required.
    Hopefully my recommendation will surely help you.
    Thanks,
    Walter

  • Client Access Server per AD Site?

    In a single forest, single domain, multi AD site environment, can users in Site-B using Outlook 2010 clients connect to Client Access array /OWA, Hub, Maibox in Site-A without the need to install a Client Access server in Site-B? or Do I actually
    have to install a Client Access server in Site-B?
    I've read this thread, but I am still a little confused
    http://social.technet.microsoft.com/Forums/exchange/en-US/03b835b4-7ecb-47ee-9b34-20cb2f70c3d4/client-access-server-active-directory-site?forum=exchangesvradminlegacy
    Per MS.."You must install the Client Access server role in every Exchange organization and every Active Directory site that has the Mailbox server role installed"
    http://technet.microsoft.com/en-us/library/bb124915(v=exchg.141).aspx.   My Site-B does not have a Mailbox server, so I don't really need to have a Client Access in Site-B, if I understand this correctly.
    Greatly appreciated if anyone can provide some clarification.
    Thanks!
    Note:  Right now, there's only a single, default site in AD (Site-A). I am planning to add a Site-B in AD and add a domain controller in Site-B, but a little confused about the exchange.  Just want to make sure that once I add Site-B to AD,
    users would still be able to access Outlook/Exchange properly.

    yes you don't need to. Your site B users will connect directly to the CAS on the Site-A, make sure the link speed is good enough.
    Where Technology Meets Talent

  • Exchange 2013 user cann't access exchange 2013 public folder

    Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
    problem, thanks.
    belows are information about outlook anywhere in our exchange.
    exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
    exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
    Identity                           : SHCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHCAS02\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : WXCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL04\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}

    Hi,
    I have found an article said that we need to set the external host name the same. See more details in the following link:
    http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
    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. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
    The following configuration is set on each Exchange 2007 server:
    The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
    Sent By
    Silver

  • Exchange 2010 MP : Some Client Access test cmdlets failed to run

    Hi all,
    This error is triggered in SCOM 2012 R2 about a single Exchange 2010 SP3 server :
    Exchange 2010 MP : Some Client Access test cmdlets failed to run.
    When I dig into the error context, I can see it's about the cmdlet "Test-CalendarConnectivity -TestType:External".
    The TechNet
    https://technet.microsoft.com/en-us/library/hh377605(v=exchg.140).aspx proposes to verify that the URL for the external virtual directory can be accessed by running the Test-OwaConnectivity.
    OK.
    But what sould I specify for the parameter -MailBoxCredential required for Test-OwaConnectivity -URL my_url -MailBoxCredential ?
    Thank you.
    Have a good day.
    FXE

    Hi,
    Under Administration, run as configuration, profiles, you can check Default action account.
    Local system is the account account for agents by default, you can change to use another account.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Alternate Access Mapping not working for Zone : Intranet

    One of our client want to set Alternate Access Mappint (intranet) with url "intranet.theirDomain.com" with local IP address.
    is it possible?
    subsequest to my previous question (
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/3f39711e-301a-40e8-aa7a-855fa2c268b1/alternate-access-mapping-not-working?forum=sharepointadmin )
    I want to ask one more question
    Can we configure "intranet.theirDomain.com" with local IP address for any other zone?
    or
    If there is ".com" within the url then it can't be configured for InTRAnet?
    Thanks
    S H A J A N

    The names for the zones don't matter. You could use the 'extranet' zone for another intranet name if you wanted, the names are just to make it a bit more friendly for beginners.
    What you describe sounds routine, you create a web application with a name, then use an AAM to allow users to access it with a more friendly name. Frequently you end up creating
    http://intranet.domain.com and
    http://intranet as an AAM, or vice versa.
    You can use .com for an intranet site, you would need to add the site as an A Host record in your DNS server so that traffic is sent to your internal server rather than out into the wider world.

  • Force encryption on SQL Server not working?

    Hello Everyone,
    I'm running SQL Server 2008 64-bit. I've installed a self-signed cert on the box and set  "Force Encryption"  and restarted SQL server. 
    I setup a client machine to trust the authority of the cert installed on the server. When I connect to that SQL server from SSMS from a client machine and select the "encrypt connection" option in the client Connection properties, SSMS correctly complains
    that the cert on the server does not match the computer name I asked to log into . This is because, although the cert is trusted, the dns name dos not match the CN in the cert <- Perfect, exactly what I am expecting.
    When I connect to the same SQL server from the same client but  UNCHECK "encrypt connection" on the client, I'm able to login. Considering I've checked the "Force Encryption" on the server, the server should have rejected the connection. Why not?
    Ameer Deen

    Hi all,
    We are implementing a Merge Synchronization solution which involves three SQL Servers located on three Azure locations worldwide and one on-premises location. We need to secure communications between all servers. We are evaluating the encryption of all server
    communications through SSL:
    http://technet.microsoft.com/en-us/library/ms191192.aspx
    When we configure one server (let’s call it server A) to accept only encrypted connections (with Force Encryption=Yes) we still can connect from other server (let’s call it server B) that do not have the certificate installed. We would expect the server
    B to fail in the attempt of connect as server A should only accept encrypted communications and those should need the certificated to encrypt/decrypt everything (commands and data).
    We have also review the following forum post that is very similar to this one:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bde679d9-ff83-4fa7-b402-42e336a97106/force-encryption-on-sql-server-not-working
    In all cases the Microsoft answer is:
    “When the
    Force Encryption option for the Database Engine is set to YES, all communications between client and server is encrypted no matter whether the “Encrypt
    connection” option (such as from SSMS) is checked or not. You can check it using the following DMV statement”
    When we run the provided DMV statement to check if encryption is enabled:
    -- To check whether connections are encrypted between server and clients
    SELECT encrypt_option
    FROM sys.dm_exec_connections
    We get “TRUE”. So theoretically encryption is enabled.
    Then:
    Why can we run SQL statements against server A from server B (with SSMS) without any certificate?
    Are we wrong when we expect server A to refuse any client that do not have the right certificate?
    How can server B, without any certificate, decrypt the data encrypted by server A?
    Our intention is to encrypt all server in the same way so all of them will accept only encrypted communications. We are assuming that the Merge Agent will be able to communicate with the Publisher and the Subscriber through this encrypted environment. May
    anyone please confirm ti?
    Thanks for your help.
    Best Regards
    Benjamin Moles

  • Sharepoint 2013 list view quick edit does not work with out remote API permissions

    sharepoint 2013 list view quick edit does not work with out remote API permissions.
    When I give Use Remote Interfaces  -  Use SOAP, Web DAV, the Client Object Model or SharePoint Designer interfaces to access the Web site it works which is not an ideal situation..
    MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

    This is true. If you use Fiddler to watch the requests from the list view quick edit you can see CSOM calls. For example when changing a value in a cell, when you tab out you will see the SetFieldValue and Update method calls on the list item.
    Blog | SharePoint Field Notes Dev Tools |
    SPFastDeploy | SPRemoteAPIExplorer

Maybe you are looking for