Title: Message
Good point...forgot about the environment variables.
 
So, for Sharyn's use, it would be something like...
 
ECHO %1 >> "\\<network path to your server here that every user has write access to>\PSTsize.log"
DIR "%USERPROFILE%\local settings\application data\ etc..." >> "\\<network path to your server here that every user has write access to>\PSTSize.log"
 
Then she just has to put them in every AD profile <g>.  There may be a shortcut for that though...possibly a group policy that would do it.

Darin.
 
 
----- Original Message -----
Sent: Wednesday, September 14, 2005 4:37 PM
Subject: Re: [Declude.JunkMail] WAY OT: software to monitor the size of the local Outlook.pst file

No need for %1
 
There are these varibles available.
 
%COMPUTERNAME%
%USERNAME%
%USERPROFILE%
 
Now, you can't have spaces in the "DIR" Command, so
 
DIR "%USERNAME%\*.*" >> "C:\Pst.Log"
 
Now, that only works in a .cmd file.
 
testing from a command prompt doesn't work.
 
 
----- Original Message -----
From: Darin Cox
Sent: Wednesday, September 14, 2005 4:17 PM
Subject: Re: [Declude.JunkMail] WAY OT: software to monitor the size of the local Outlook.pst file

If you put the username as a parameter to a batch file in every users AD profile, then a simple batch file like
 
ECHO %1 >> \\<network path to your server here that every user has write access to>\PSTsize.log
DIR C:\documents and settings\%1\local settings\application data\ etc... >> \\<network path to your server here that every user has write access to>\PSTSize.log
 
Would give it to you.  Of course you could get fancier with the log file format, but this gives you the fundamental data.
 
Obviously you have to put this individually into each users' profile with their username, so that will take time...

Darin.
 
 
----- Original Message -----
Sent: Wednesday, September 14, 2005 3:43 PM
Subject: RE: [Declude.JunkMail] WAY OT: software to monitor the size of the local Outlook.pst file

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. 
 
 
Heh..I"m working on the "get someone to write it for me" part, that would be my boss who came up with this idea about the size monitoring of the pst files anyway.
 
The directory is the standard directory that Outlooks installs all it's pst files, documents and settings/<username>/local settings/application data/ etc etc
 
So, since everyone's user name is different that would put it in a different directory.
 
 

 

Reply via email to