OutlookSize
Do you have to support Outlook end-users?? Do you educate the end-users to monitor their own .PST files not to exceed 2GB or a certain file size to prevent .PST corruption?? Do you end up with having to monitor the users’ .PST file size by yourself since no users will do the monitoring by themselves??
OutlookSize was initially developed to answer those questions above.
OutlookSize allows you to specify the .PST size in two levels: Warning and Stop. Normally, Warning size is smaller than Stop size. For example, you may want to specify 1200 for Warning size and 1600 for Stop size (note: the size number is in Megabytes).
There are 4 possible actions when a particular .PST size exceeds the defined (Warning/Stop) size:
- Send Windows message (NET SEND) to specific workstations/users
- Send E-mail message to specific recipients
- Rename the .PST file, so that it becomes inaccessible by the users
- Run a specific program
You can set the configuration in OutlookSize.ini, as follows:
[Setup]
MaxSizeWarn=1200
MaxSizeStop=1500
CloseIfEmptyDelay=10
SmtpServer=smtp.mydomain.com
SmtpSender=outlooksize@mydomain.com
SmtpUsername=outlooksize
SmtpPassword=outlooksize
[WarnActions]
SendEmail=support@mydomain.com
SendMessage=technician01, technician02
RunProgram=
RenamePst=No
[StopActions]
SendEmail=support@mydomain.com, itmanager@mydomain.com
SendMessage=technician01, technician02, sysadmin
RunProgram=
RenamePst=Yes
Then you can modify the login script to run this program automatically when the user logged in.
Notes:
- OutlookSize may need to be modified to support future versions of Microsoft Outlook
- OutlookSize will check the .PST files opened in Outlook previously. To save time, it will not scan your harddisk to search your .PST files
- OutlookSize can only check the file size correctly if the .PST file is not opened at that time
- If you do not implement SMTP Authentication, then you do not have to supply SmtpUsername and SmtpPassword in OutlookSize.ini
I hope OutlookSize will help you in some areas. Your inputs and feedbacks are always welcomed.
