Direkt zum Hauptbereich

Exchange 2010 Client Access Throttling.

Environment:


Exchange 2010 – RU1 – Single Box ( All Roles )
Windows 2008 R2

Outlook 2003 Service Pack 3 Clients


Issue:


During normal working hours users randomly was unable to access their mailboxes when they launched their Outlook client.

The users were receiving the following Outlook message:

Outlook error

“Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.”


It was also reported that some users had issues expanding additional mailboxes. (Delegate Mailboxes )

The following Outlook message appeared.

set of folders

“Unable to expand the folder. The set of folders could not be opened.”



Troubleshooting:


Started Exchange powershell

Ran the following powershell command

Get-LogonStatistics –Identity | fl applicationid


We counted the number of occurrences of “ ApplicationID : Client=MSExchangeRPC “

Result: 20


Resolution:


We corrected this by creating a New-ThrottlingPolicy. And setting the RCAMaxConcurrency to a greater value then 20.

Finally assigning this new throttlingPolicy to the specific mailboxes that were experiencing the issue described.


Steps to create and apply a throttling policy:

New-ThrottlingPolicy –name

Set-ThrottlingPolicy –identity –RCAMaxConcurrency

Set-Mailbox –Identity “Username” –ThrottlingPolicy


What is Throttling?

Understanding Client Throttling Policies
http://technet.microsoft.com/en-us/library/dd297964.aspx

Exchange 2010 introduces a new feature called Throttling.
This feature was introduced to prevent a single user or groups of users from using up all the Exchange resources and causing a denial of service attack.

The throttling policy is group settings that can be used to control how much resources that a user or connection can use against Exchange organization. Throttling polices can only be used against users that are using Exchange 2010 servers. They do not apply to previous versions of Exchange.

Throttling policies are stored in the following location in active directory.

CN=Global Settings, CN= Exchange Org, CN= Microsoft Exchange , CN=Services, CN= Configuration, DC= Domain, DC = COM.


Using ADSI Edit you can see your DefaultThrottlingPolicy here

Adsi


Using Powershell to list the
Default Throttling Policy


Get-ThrottlingPolicy | ft name

get-thrott

As per best practices.

Instead of editing the Default Policy create a new one and assign it to the appropriate Mailbox.


Throttling Policy Settings

· Exchange ActiveSync

· Exchange Web Services

· IMAP

· Outlook Web Application

· POP3

· Powershell Commands

· Outlook client (MAPI/RPC)connections


Get-ThrottlingPolicy

image

Since my case was about Outlook RPC connections i am adding this table information.

Outlook ( RPC)

Parameter

Default Value

Description

RCAMaxConcurrency

20

The RCAMaxConcurrency parameter specifies how many concurrent connections an RPC Client Access user can have against a server running Exchange 2010 at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if the user goes offline). If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. TheRCAMaxConcurrency parameter has a valid range from 0 through 100 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.

RCAPercentTimeInAD

Null

The RCAPercentTimeInAD parameter specifies the percentage of a minute that an Outlook user can spend executing directory requests. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question.

RCAPercentTimeInCAS

Null

The RCAPercentTimeInCAS parameter specifies the percentage of a minute that an Outlook user can spend executing CAS mailbox requests. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question.

RCAPercentTimeInMailboxRPC

Null

The RCAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an RPC Client Access user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question.

More information:

New-ThrottlingPolicy
http://technet.microsoft.com/en-us/library/dd351045.aspx

Set-ThrottlingPolicy
http://technet.microsoft.com/en-us/library/dd298094.aspx

Set-Mailbox
http://technet.microsoft.com/en-us/library/bb123981.aspx

Kommentare

Beliebte Posts aus diesem Blog

Microsoft Office 2013 aktivieren via Kommandozeile

Wie man das neue Microsoft Office 2013 aktiviert via Kommandozeile, das werde ich euch in dem folgenden Beitrag Schritt für Schritt erklären. Gerade in grösseren Systemumgebungen in welchen die Clients und Standard Software automatisiert installiert werden, kann das sehr hilfreich sein und erspart einem viel Arbeit nach der Installation des Clients. Das Ziel sollte sein, möglichst viel zu automatisieren und soweit möglich, wenig noch händisch zu konfigurieren. Da kommt dieser Beitrag sicherlich nicht ungelegen. Die folgenden Befehle könnte man beispielsweise ganz einfach in eine MDT (Microsoft Development Toolkit) Umgebung mit einbeziehen oder auch mit anderer Software benutzen. Wichtig zu wissen ist, dass dies nur dann funktioniert, wenn Microsoft Office 2013 über das Internet aktiviert wird. Hat man einen eigenständigen Aktivierungsserver (KMS), funktioniert dies nicht. Zudem müssen die Befehle alle mit Administrator Rechte ausgeführt werden. Normale Benutzerberechtigungen genügen …

Windows Domain Controller: Es sind momentan keine Anmeldeserver zum Verarbeiten der Anmeldeanforderung verfügbar

Zurzeit häuft sich (warum auch immer) das Problem dass nach einem Neustart eines Windows Domain Controllers bei der Anmeldung die Fehlermeldung „Es sind momentan keine Anmeldeserver zum Verarbeiten der Anmeldeanforderung verfügbar“ kommt und eine Anmeldung so nicht möglich ist Das Problem ist hierbei das der Domain Controller im Active Directory Reperatur Modus (Abgesicherter Modus) startet. Am einfachsten lässt sich dieses Problem folgendermaßen beheben: 1) Anmeldung mit dem DSRM (Directory Services Restore Mode) / Verzeichnisdienstwiederherstellungskennwort Falls die Anmeldung nicht funktioniert kann man einen Workaround wie hier beschrieben durchführen. 2) Systemkonfiguration mittels msconfig.exe aufrufen

WSUS won’t uninstall or re-install

Hat heute ein Problem mit WSUS unter Windows Server 2008 R2 bei einem Kunden. Das Problem - die Clients konnten keinen Verbindung zum WSUS Server herstellen. Die Deinstallation wurde unerwartet beenden mit folgender Fehlermeldung: Attempt to un-install Windows Server Update Services failed with error code 0x80070643. Fatal error during installation  Die Lösung: I don’t like Windows Server Update Services (WSUS), but it’s the free alternative many companies select over the higher cost alternatives like Intune or Systems Center. So, today I had to repair a damaged WSUS installation. Turns out someone uninstalled SQL Server 2005 Express not realizing WSUS was using it. Now firing up the WSUS console just yielded an error complaining about the missing SQL database. So like any good troubleshootin IT guy the first thing I tried was to uninstall WSUS…sadly, however the product would not uninstall or re-install. Here’s how I finally got rid of it: [the problem] WSUS 3.0 SP2 is missing SQL serv…