I had posted a script that reports all users with their mailbox storage limits set individually on the user account properties in my earlier post titled “SCRIPT: Show mailbox limits“.
I have just added another script to that post that will reset those mailboxes (with storage limits set individually). Once the script resets storage limits on the account, the account will get any mailbox storage limit policies.
Readme from the script:
This script will look for all user accounts that have their mailboxstorage size modified individually.
This includes accounts that have **any** following attributes:- Use mailbox store defaults is unchecked- Issue warning at (KB) is set- Prohibit send at (KB) is set- Prohibit send and receive at (KB) is set
Usage: resetmailboxlimits.vbe
Options:
/s:y will run script in silent mode (make sure you use the /f option to save output to a file if you’re using silent mode
/f:[path to output file.txt] – will save output in a text file
/help
This example runs the script in silent mode and saves output in output.txt in c:\somedir
resetmailboxlimits.vbe /s /f:c:\somedir\output.txt
{ 8 comments… read them below or add one }
This is a great tool! Do you have anythign to reset the Delivery Restrictions?
It seam the script is encripted and modification are not possible. Is there any posibility to change the script for my need. I want thant only change acount on one specified OU.
It seem the script are encripted. I wand to modify the script for my needs. I only want to modify one OU. Is it posible to get plain version of this script.
Thanks
[email protected]
Hi,
I run the SHOWMAILBOXLIMITS.vbs script and it is working fine. I run from the same machine using the same user this script and i have this error:
resetmailboxlimits.vbe (94, 21) (null): 0x80005000
Can you please help me in identiying the problem?
Running these 2 scripts on a virtual machine both are working very fine.
Thanks a lot,
Razvan
Hi, Do you have a script that will reset send/receive limits that are set at individual mailboxes so global send/receive limits can then be applied?
Thanks!
Why would this one script be encrypted? This is a little more dangerous script, as it actually makes modifications to active directory, rather than only report information – so why would it be encrypted, rather than open to review in order to verify that the actions it is taking are not insidious or unexpected and harmful in some way? Making a disclaimer is fine for protecting the author – but when the author hides what is going to happen?? And how does this extend our knowledge of scripting?
@Anonymous from Aug 27: Not sure what the thought process was >3 years ago when this script was posted. I stand by my disclaimer of not using scripts/code downloaded from the internet without adequate testing. However, there are plenty of other binaries we download and use, and have no clue what the source really does.
My apologies for not working to extend your knowledge of scripting in this one instance – iirc most other scripts posted here are not encrypted. :)
@Anonymous from Oct. 2 9:36 AM: Thanks for the heads up on broken link. Updated.