- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
What is allowed via the Scheduler service?
What types of executable content can be run via the Scheduler service? The File Browser allows you to select any file, but errors out for me when I select a functional vbscript file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I haven't tried specifically launching a VB Script from the scheduler, but I can say that Batch files and .EXEs work fine.
As corny as it sounds, perhaps try putting the .vbs into a .bat file and schedule the .bat file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
While that sounds like a reasonable solution, there are a couple of issues:
1) Passing in arguments starts becoming very challenging. Every type of script has its own requirements for parsing them.
2) No one writes exe's to run custom code.
3) Batch files need to die.

Any chance this is documented somewhere?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thanks!
1) That is definitely true. Static parameter data generally works best, but do you have a specific use case where you are passing in variables? Maybe this could be a good enhancement.
2) That's also true, but I was was simply mentioning the types of files I knew to work. The most common .exe to run from the scheduler is lsmaint - clearly not a piece of custom code.
3) well... I'll leave that one to be argued by the executable file scholars
I'm checking around to see if there is a documented list - there is definitely nothing in the Help file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
So far there appears to be no formally documented list.
It does seem that anything that should be viewed as executable by the OS should be able to be launched from there.
In the case of something like a Perl Script, you'd probably have to make a reference to the interpreter, but based on what feedback I've gotten so far it seems a VBscript should work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
