Forum Discussion

Paul Bendall's avatar
Paul Bendall
Iron Contributor
Nov 01, 2016

Direct calendar booking across multiple mailboxes

First off I know direct booking is bad and that wherever possible the use of free / busy scheduling should be used.   I have observed a number of our executive assistants who manage the calendar an...
office 365
Matt Karel's avatar
Matt Karel
Brass Contributor
Nov 01, 2016
I am seeing some of the same issues with our Exchange 2016 CUx infrastructure and users who manage multiple calendars.. we also see occasional slowdowns/not respondings when we have clients in online mode. I have an active case with MS open trying ro trackdown our issue.
Paul Bendall's avatar
Paul Bendall
Iron Contributor
Nov 24, 2016

Matt Karel any update on your case with Microsoft? Even if you could share the troubleshooting steps to date. Calendaring remains our number one compliant for migrated users

  • Matt Karel's avatar
    Matt Karel
    Brass Contributor
    Dec 01, 2016
    Sorry, things have been crazy. As of right now we are looking at this from the Exchange side of things. We are seeing some performance issues and network issues on the backend that could be contributing to some if not all of our users. We ran an 11hr Perf collection on our 4 Exchange Servers an we saw several things that may be causing us some pain
    some of the things we are addressing are:
    - Page File Sizes (32GB Max)
    -TCP Reset windows on the server and our load balancers
    -ensuring the Exchange servers don't have more then 96GB of Ram
    -Removing our NIC Team and going to a single Nic on each server
    -Updating Drivers and Firmware (Bios, Storage Ctrl, Drives)

    once all these changes are made this month, we plan to run another 11hr perf collection to see if things have improved.
    • Matt Karel's avatar
      Matt Karel
      Brass Contributor
      Feb 28, 2017

      Paul,

      I dont know if our issue s are exactly the same as we are seeing perf issues when opening mail, caledar and other activites within Outoook. At this point we think the issue is somewere within the MAPI/HTTP stack in IIS or Windows but more debugging would be necessarry to see and we dont have the hours to burn. We have found that if we move the user from using MAPI/HTTP to connect to their mailbox to use RPC/HTTP the issues seem to be resolved.  I would sugesst that you try the same. to do this with in powershell enter Set-CasMailbox -Identity "user Alias" -MapiHttpEnabled $False

      if you find that this helps your issue please if you can open a ticket with Microsoft and ref SR 116102414841137

       

      Thanks

Resources