What’s next, painting blue/white over all the yellow boxes? I might start selling yellow stickers for Kemp units. Seems SP1 introduced come compliance regulation which requires the Kemp to change the default setting.īy the Way, if Kemp is reading this blog: I really don’t like the new blue/white color scheme at all! I know your company psychologists told you it’s a neutral color, but that means all software will become blue? Haven’t we had enough blue in Citrix, Windows and all the other big companies? I liked the contrast especially in the status column, that was very obvious. To have a server check if the request could be accepted based on the request’s headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).” Synchronization, Notification, Availability, and Automatic Replies These tests walk through many basic Exchange Web Services tasks to confirm theyre working. If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. This test simulates the steps a mobile device uses to connect to an Exchange server using Exchange ActiveSync. “100 Continue: This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent for example, a POST request). ![]() ![]() A description of the “100 Continue” rule states I’m not sure if the 7.1-26 has this setting as I already upgraded, so you might have to upgrade to a more current version. So we started troubleshooting and after a load of tests, Kemp suggested setting the L7 Configuration “100 Continue Handling” to “RFC-7231 Compliant” and the error disappeared.įor reference, this was tested with Exchange 2013 CU2, CU3 and CU10 on Windows 2012 R2, Kemp 7.1-26 and 7.1.-30 and 2 different templates (pre/post Exchange2013Core_1.7.122). ![]() ![]() The test of the FolderSync command failed.Īt ()Īt .() But after an upgrade to CU3 (SP1) and higher (to CU10) the RCA gave an error Īttempting the FolderSync command on the Exchange ActiveSync session. We always use the excellent tool Remote Connectivity Analyzer (RCA) to test the connectivity of our Exchange servers and all was well in our Exchange 2013 CU2 setup with Kemp Loadbalancers in place. So this should be a fairly short blogpost, but it took a lot of time troubleshooting so let’s share this so it might save you some time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |