Solved

How to list which users are assigned to a throttling policy

Posted on 2012-03-26
9
4,260 Views
Last Modified: 2012-03-31
We just removed Blackberry from our environment and I'm going through and doing the cleanup of settings we had to put on for BES.  I want to delete the throttling policy assoicated with BES, but I can't because some users are still assigned to it.  What is the cmdlet that I can use to view which users are assigned to a certain throttling policy?

Also, what would the following line actually do?  I accidentally ran it and I want to make sure it didn't affect anything.
get-mailbox | throttlingpolicy
0
Comment
Question by:jpletcher1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 3

Expert Comment

by:cfletch1980
ID: 37768161
You can use the Get-ThrottlingPolicyAssociation cmdlet for mailboxes within your org
0
 
LVL 3

Accepted Solution

by:
cfletch1980 earned 500 total points
ID: 37768163
I would of course export results out to a csv file so that you can sort accordingly
0
 

Assisted Solution

by:jpletcher1
jpletcher1 earned 0 total points
ID: 37768192
I figured out how to do it using this:

Get-Mailbox | where-object {$_.ThrottlingPolicy -eq "BESPolicy"}


I'm still not sure what running this command did exactly:
get-mailbox | throttlingpolicy

Did that assign users to no throttling policy?  I meant to put a fl in there but missed it.
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 
LVL 3

Assisted Solution

by:cfletch1980
cfletch1980 earned 500 total points
ID: 37768228
This will work also...probably not the cleanest and if you think you will have over 1000 results you need to add -resultsize unlimited

Really the only user that should have the policy assigned directly at a user level should be your besadmin mailbox. So if you havent deleted that mailbox yet that is your problem user.

get-mailbox -Filter {ThrottlingPolicy -ne $null} | fl name, alias, Throttlingpolicy
0
 

Author Comment

by:jpletcher1
ID: 37768258
Thanks.  We did have less than 1000 mailboxes and it was just the besadmin user that had the policy assigned.

Can you tell me what running "get-mailbox | throttlingpolicy" did when I accidentally ran it?

Also, should most users have the default policy assigned, or no policies assigned for throttlingpolicy?
0
 
LVL 3

Expert Comment

by:cfletch1980
ID: 37768277
yeah that works also your other command didn't do anything as you didn't use a set cdmlet
0
 

Author Comment

by:jpletcher1
ID: 37768291
What would that command do exactly?  Because I did get a bunch of return errors..

Do you know if all users by default get the default throttling policy or no throttling policy?
0
 
LVL 3

Expert Comment

by:cfletch1980
ID: 37768388
All users by defualt should have no throttling policy assigned to them..

you can do a spot checks on user accounts using

get-mailbox -id useralias | fl name,Throttlingpolicy


You probably got a bunch of errors because you just had | throttlingpolicy...where it is looking for an object before that to sort, filter, etc....
0
 

Author Closing Comment

by:jpletcher1
ID: 37790425
There were a couple ways to accomplish this and one of my posts also worked to get the information I was looking for.
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question