<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Times New Roman","serif";
font-weight:bold;}
p.pb1body1, li.pb1body1, div.pb1body1
{mso-style-name:pb1_body1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Folks:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m hoping someone can share their experience with the Cisco recommended method for removing EWS limits on Exchange 2010 SP2 RU4 and higher. In earlier releases of Ex2010 the process of setting a throttling policy applied only to the UM
service account, and any throttling performed would be applied to that service account and not to the target mailbox. Please correct me if my understanding is incorrect, but with E2010 SP2 RU4 and higher, the policy is to be applied to every target mailbox,
which seems like it would impact all other EWS applications impersonating these target mailboxes.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:10.5pt;margin-right:0in;margin-bottom:5.25pt;margin-left:0in;background:white">
<b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#336666">Removing EWS Limits from Exchange 2010 SP2 RU4 and Later<o:p></o:p></span></b></p>
<p class="MsoNormal" style="mso-margin-top-alt:.75pt;margin-right:0in;margin-bottom:4.5pt;margin-left:0in;background:white">
<span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Microsoft has enabled the client throttling policy feature by default. If there is no throttling policy already configured, Microsoft Exchange applies a default policy to all users.
The default throttling policy is tailored for end user's load and not for an enterprise application like, Cisco Unity Connection using impersonation</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#C00000">. If any Cisco Unity Connection
users who are configured for unified messaging have mailboxes in Exchange 2010, configure the Exchange 2010 EWS limits for the unified messaging users mailbox by creating and applying a new mailbox policy to the unified messaging user mailbox account.
</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">If you do not configure EWS limits, messages may not be synchronized, and status changes (for example, from unread to read), changes to the subject line, and changes to the priority
may not be replicated. In addition, attempts to access Exchange calendars and contacts may fail.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>The MS KB referring to the throttling policy change</b>: <a href="http://support.microsoft.com/kb/2713371">
http://support.microsoft.com/kb/2713371</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Perhaps my understanding is wrong, but it seems like a backwards move. Has anyone seen any adverse effects of applying the Cisco recommended throttling values as the system default? Perhaps any problems where applying the throttling policy
to the target mailbox impacts other EWS apps like BlackBerry Enterprise? Are you applying the throttling policy for every single UM enabled mailbox, individually, via management shell?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">- Dan<o:p></o:p></p>
</div>
</body>
</html>