MM&M UG UK

In my testing environment I have found that the following commands are NOT mutually exlusive as they should be.

Set-PublicFolder -PostStorageQuota -StorageQuota

AND

Set-PublicFolder -UseDatabaseQuotaDefaults $true

I seem to be able to set a poststoragequota and storagequota with the usedatabasequotadefaults parameter set to true.

I have Exchange 2007 SP1, and this is confirmed in the Public Folder Management MMC. The UseDatabasedefaults is ticked and the Issue Warning and ProhibitPost are greyed out yet set and active.

Is this an oddity in my testing environment?

Many Thanks

Shaun

In a real environment, if there are 'per public folder' quota limits established, it would not be possible to simply recursively iterate through all folders and change status of -UseDatabaseQuotaLimits to $true because it appears that if the limit settings are applied on a per public folder, they take precedence over the -UseDatabaseQuotaLimits.

Any thoughts?

Thanks

Shaun

Hi,
Interesting!!

Let me see what I can find out.
Cheers
Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

Normal 0 false false false EN-GB X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}

Hi,

Here is a comment I got from a friend;

I’d question the “active” part of that statement. The same thing is true of a mailbox. You can set explicit quotas and then set the mailbox to use the database defaults. The quotas are still visible and their “IsUnlimited” property is false, but the mailbox’s UseDatabaseQuotaDefaults is set to  $true.

 

You can see the same thing looking at a “Legacy Mailbox” even though the Exchange 5.5 UI doesn’t show the values they’re still there. If you use LDP or ADSIEDIT you can see them.

 

Public folders are a bit different in that you can’t see the information in the AD. I’d guess that if you use PFDAVADMIN you’d find the quotas still set on the PF in 5.5 (but not displayed in the ESM UI).

Is that any help?

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

Hi Nathan,

Thanks for the reply.

It just strikes me as a little confusing because it seems that you can be in a situation where there are public folders all with differently set 'explicit' quota values, and even though you are able to set the value for UseDatabaseQuotaDefaults to true, the public folders in question will STILL use the explicitely set quotas.

I would have expected that if the EMC shows your explicitely set quotas greyed out and the 'UseDatabaseQuotaDefaults' ticked that the database defaults would be the winner of that battle but I guess not?

I think I'll go and revisit this one myself, because I maybe missing something.

Thanks again

Shaun

I've just run a test.

I have a public folder called 'c'.

I run the following commands, results as below:

Get-PublicFolderDatabase | fl *quo*

ProhibitPostQuota : 1000KB
QuotaNotificationSchedule : {Sun.00:00-Sat.23:45, Sat.23:45-Sun.00:00}
IssueWarningQuota : 5KB

Get-PublicFolder \c | fl *qu*

PostStorageQuota : 22KB
StorageQuota : 21KB
UseDatabaseQuotaDefaults : True

Get-PublicFolderStatistics \c | fl *Size*

TotalAssociatedItemSize : 0B
TotalDeletedItemSize : 0B
TotalItemSize : 38272B

Now, I am using OWA and trying to post an item and it says my storage limit has been reached and I am unable to post.

I would have expected to be able to post because the ProhibitPostQuota is 1000KB (the Default limit for DB), and the public folder is only 37.38KB by my calculations.

Shaun

In comparison, the Mailbox settings appear to behave in the expected manner.

Get-Mailbox -anr Shaun | fl *quo*

ProhibitSendQuota : 1KB
ProhibitSendReceiveQuota : 2KB
UseDatabaseQuotaDefaults : True
IssueWarningQuota : unlimited
RulesQuota : 64KB

Get-MailboxDatabase | fl *quo*

ProhibitSendReceiveQuota : 2355MB
ProhibitSendQuota : 2GB
QuotaNotificationSchedule : {Sun.02:00-Sun.02:15, Mon.02:00-Mon.02:15, Tue.02:0
0-Tue.02:15, Wed.02:00-Wed.02:15, Thu.02:00-Thu.02:
15, Fri.02:00-Fri.02:15, Sat.02:00-Sat.02:15}
IssueWarningQuota : 1945MB

Get-MailboxStatistics -Identity Shaun | fl *size*


TotalDeletedItemSize : 0B
TotalItemSize : 871097B


In this scenario it is considered that I have not reached my quota limits and I can still send/receive via OWA, which makes sense as the DB defaults are far higher than my current mailbox size (although my mailbox size is larger than the explicitly set quota values).

Shaun