scheduled task to delete Outlook Secure Temp files

I have a script to delete outlook secure temp folder and create a scheduled tasked on domain user's machines.  The problem is I have to run this scheduled task as current log on user in order to delete logon user's  in Outlook Secure Temp files.

I created a doman admin user scheduler and run this scheduled task as Scheduler, the script runs but the Outlook Secure Temp files are not deleted.

I would like to delelte outlook secure temp folders using account Scheduler's credential.

How can I achieve it?

thanks,
HemlockPrintersAsked:
Who is Participating?
 
HemlockPrintersConnect With a Mentor Author Commented:
I used group policy to set up scheduled task
0
 
David LeeCommented:
Hi, HemlockPrinters.

Can you share the script so we can see for ourselves what it's doing?
0
 
HemlockPrintersAuthor Commented:
Set oWSH = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")
For Each sKey in Array("11.0","12.0")
 sOutSecTmp = Empty
 On Error Resume Next
 sOutSecTmp = oWSH.RegRead("HKCU\Software\Microsoft\Office\" _
  & sKey & "\Outlook\Security\OutlookSecureTempFolder")
 If Len(sOutSecTmp) > 3 Then
  oFSO.DeleteFile oFSO.BuildPath(sOutSecTmp,"*.*"), True
 End If
Next
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
David LeeCommented:
The script works fine for me.  I'm a little confused which account you're running it under.  Are you running it as the current user (i.e. the person who's logged in to the computer) or under some other account?
0
 
HemlockPrintersAuthor Commented:
no, I run it under local admin (or domain admin), the script runs without error, but it doesn't delete files.
it only works (delete files) under current log in user
0
 
David LeeCommented:
That makes sense.  It's getting the path from HKCU, the current user.  If the script is running under the local admin account, then it's never going to get the path you want it to.  It's going to get the path for the local admin account.  Why not run it under the local user account?
0
 
HemlockPrintersAuthor Commented:
the password for local user's account has to be changed in 6 months, so if I run the scheduled taske uner the local user account, once the user change the password, the task will fail
0
 
David LeeCommented:
It shouldn't unless you store the password with the task which I don't believe is necessary.
0
 
HemlockPrintersAuthor Commented:
there are not other resolutions
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.