Maybe try to change your quotes, or no quotes...
Main Topics
Browse All TopicsI 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!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes - psexec is running it under 'your' credentials.
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...
Business Accounts
Answer for Membership
by: jared_lukerPosted on 2009-04-03 at 09:44:25ID: 24061901
Error code 0 means that it thinks it completed successfully. I think the problem that your having is with psexec and not the batch file