Re: [Declude.JunkMail] WAY OT: software to monitor the size of the local Outlook.pst file

[Darin Cox]

Title: Message

The .NET framework is not needed for VBS scripts or non-.NET executables, only for .NET compiled executables.   So now, the thing is to just find or have someone write the script for you <g>.   If you standardized the location of the PST on every workstation, a simple bat file would do the trick.  If the directory name is different on each workstation, then you would need to pass it a parameter to find the directory and echo the dir info to a network file. Darin.     ----- Original Message ----- From: Sharyn Schmidt To: Declude.JunkMail@declude.com Sent: Wednesday, September 14, 2005 3:23 PM Subject: RE: [Declude.JunkMail] WAY OT: software to monitor the size of the local Outlook.pst file From a server on the network, you would have to have permissions to each machine to do that.  If you run Active Directory it's not a problem, though.  In fact, you could add the script Dave suggested to their startup to compile a report of pst sizes.    I do run an AD domain here.      That would be pretty easy to do with a _vbscript_. Create a FileSystemObject and have it access the file. That exposes most file properties, including filesize, as I recall. The script can send you an email if the file gets too large.  Run the script once a day using the task scheduler.    Scripting writing is not one of my strengths so forgive the stupid question..would I not have to load some sort of .net framework on every workstation in order for this script to run?   I like the idea of using AD to have each workstation run the script as they log onto the domain, but I am not sure how to get this script to work on the individual machines.   Thanks for your time! Sharyn