I am trying to create a batch that closes outlook "correctly" on client machines from the server. I know killing outlook would be easy enough, but i don't want outlook scanning files every morning when my users open it up because it was not closed properly.
I found a vbscript that closes outlook, and I am now trying to execute it from a batch. I am currently testing on 2 XP machines, to determine if this is going to work. So far, no luck.
Here is the script that closes outlook:
On Error Resume Next
Set Outlook = GetObject(, "Outlook.Application")
If Err = 0 Then
Outlook.Quit()
End If
When I execute this locally, it works fine.
Here is the test batch that I have created to run remotely:
psexec \\station1812 cscript "c:\test\testscript.vbs"
When I run this from a remote computer I get the following error "cscript exited with error code 0"
Any suggestions? Thanks in advance!
Since the outlook session is running under another user's context, you won't be able to get to it using psexec.
Probably a better idea would be to set up a logon script for the user(s) that adds a schedule task (if they have rights to create a task) under their credentials to occur at a specific time of day...