How to increase Quota for Outlook Rules on Exchange Server

If many rules are created, or rules with long names are used, the quota storage on the Exchange Server may no longer be sufficient, the default size is limited to 64 KB.

If you try to enable the rules that are disabled, you receive the following error message:

One or more rules couldn’t be uploaded to Exchange server and have been deactivated. This could be because some of the parameters aren’t supported or there’s insufficient space to store all your rules.

The RulesQuota can be extended with the following cmdlet from the Exchange Management Shell.

Set-Mailbox joe@banana.org -RulesQuota:256kb

Query current RulesQuota with the following cmdlet

Get-Mailbox joe@banana.org | FL displayname, rulesquota

Note. If rules are created to move to local PST files, advanced options – only on this computer must be enabled. These rules are also uploaded to the server. But they are not run online because PST folders are only present locally on the computer.

Exchange Server Rules Limitation

Microsoft Exchange server, including Office 365 Exchange Online and Outlook.com, as well as on-prem Exchange servers, limit the number of rules a user can have in an Exchange mailbox. The limit is based on total size, not number of rules, so one user might have 20 rules while another has 30.

Exchange 2003 and older limited

Exchange 2003 and older were limited to just 32 KB worth of rules. The limit was increased beginning with Exchange Server 2007, to 64KB by default and configurable up to 256KB. Later versions of Exchange dropped the lower default setting and gave everyone the maximum 256KB. This includes Office 365 Exchange and Outlook.com accounts.

Microsoft Dynamics AX 2012 projects typically take place across multiple AOS instances

The configuration is created using the Microsoft Dynamics AX configuration utility for the corresponding Application Object Server instance, and the Configuration button stores the Windows Communication Foundation (WCF) configuration in the registry. Visual Studio 2010 Ultimate now reads the connection from the registry.

When processing SSRS reports from Visual Studio, there is often the situation that reports must first be deployed in a developer instance before they can be transferred to the test and then to the productive instance.

So that developers have the certainty in which instance they are currently deploying the report, it is best to go via the Visual Studio Application Explorer and go to the SSRS Reports -> Reports and open a report for editing, here it is AccountantInvestmentAnalysis, on the right side of the Solution Explorer window you select ReportModel(#), so that at the bottom of the Properties window in the Repository field the server and the SQL server instance as well as the AOS, application object server instance appears.

Now the report can be provided, everything is fine with the report, the report can be integrated via Application Object Tree (AOT) of the next AOS instance.