Exchange 2010

We are considering creating AD security groups and then adding them into Exchange to manage Quota's. We have a few questions: How does this affect the local setting for the person in the management console? Is the option to set persons quota individually grayed out? If more is defined in the console, does that take precedence over what is defined in AD security groups? Any other problems encountered? Pros and cons?
colmisdivAsked:
Who is Participating?
 
Simon Butler (Sembee)ConsultantCommented:
You cannot manage quotas with groups.

The only thing that you can use groups for is to have a group of users that you apply quotas to - ie the command takes the members of the group, applies an individual setting to them. Unless you run a script on a schedule to keep changing/setting the quota, it is a one time thing. Changing the group membership will not change the quota.

Quotas are only set at the database or mailbox level, as already stated. Nowhere else. Even if you set them at the database level the settings are still available within the user account to be set individually.

Simon.
0
 
AmitIT ArchitectCommented:
Where you read security group option? As far as I know, you can set at db level or mailbox level.
0
 
colmisdivAuthor Commented:
Here is a script I found. I want it to reflect a 250MB quota with a warning at 200MB. Not sure what the numbers should be.

Get-ADGroupMember "Exchange Quota 5GB" | select @{l="identity";e={$_.distinguishedname}} | Get-user| set-mailbox -IssueWarningQuota 4864000000  -ProhibitSendQuota 5017600000 -ProhibitSendReceiveQuota 5242880000 -UseDatabaseQuotaDefaults $false
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
colmisdivAuthor Commented:
Tried this script and didn't work:
Get-ADGroupMember "GroupMail_100MB" | select @{l="identity";e={$_.distinguishedname}} | Get-user
| set-mailbox -IssueWarningQuota 80000000  -ProhibitSendQuota 100000000 -ProhibitSendReceiveQuota 100000000 -UseDatabaseQuotaDefaults $false

Error below:

The term 'Get-ADGroupMember' is not recognized as the name of a cmdlet, function, script file, or operable program. Che
ck the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:18
+ Get-ADGroupMember <<<<  "GroupMail_100MB" | select @{l="identity";e={$_.distinguishedname}} | Get-user
    + CategoryInfo          : ObjectNotFound: (Get-ADGroupMember:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
The ActiveDirectory module needs to be imported into PowerShell prior to using its cmdlets, at least with PS 2 (3+ should import automatically).
0
 
ChrisCommented:
as simon says you can't manage like that with the powershell you have import the ad management cmdlets and then add a for each loop in there. you could manage it this way with a scheduled task
haven't tested this but it should be pretty close to something that will work

import-module Activedirectory
$mbxgroups = Get-ADGroupMember "GroupMail_100MB" | select @{l="identity";e={$_.distinguishedname}}
 Foreach ($user in $mbxgroups) { set-mailbox -IssueWarningQuota 80000000  -ProhibitSendQuota 100000000 -ProhibitSendReceiveQuota 100000000 -UseDatabaseQuotaDefaults $false}
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.