One quick workaround is to write a small CMD. Put in a "net use" to map your drive and then call "cscript scriptname.vbs arguments". Schedule with an account that has enough access to map the drive and run the script. Use the full paths to be extra safe, i.e. %windir%\system32\cscript.exe and c:\myscriptfolder\scriptname.vbs. It should work. -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Davey B Sent: Tuesday, February 28, 2006 11:17 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Re: Vbscript and scheduled tasks Sorry if this is a duplicate.. being SYN flooded like crazy at the moment.. so not sure if stuff is getting out 100% or not. On 28/02/06, Davey B <db1001ster@xxxxxxxxxxxxxx> wrote: On 28/02/06, Ray at home <listray@xxxxxxxxxx <mailto:listray@xxxxxxxxxx> > wrote: Are you deleting the files from a network share? Yes it is a share it's a permanent mapped drive letter.. if that makes a difference.. which of course it could if the mapping doesn't work if mapping is killed off when no one is logged on... Hmmmm..... Are you scheduling the .vbs file, or cscript.exe with the VBS path as the file to run? just the .vbs (on the desktop).. I'll look at cscript to see what that does. _____