Wscript.Controller gives you access to a method called Create Script, which you can use to create processes outside the script you're working with. Essentially, this method lets you launch another available script locally or on a network share.
Using this method, you don't have to launch a script from the machine you want to run it on, but you can point to it programmatically. (The default is to run the remote script on the local machine.) This also means that your script, the one starting the process, can end without interfering with the remote script object's execution.
Since the script doesn't run until the Execute method in the launching script executes, this is also a good way to delay a script's execution or make it conditional on some other set of circumstances. The circumstance can be something as simple as the person running the original script typing "Go."
Scripting School: Find objects with Windows Scripting Host
Windows Scripting Host objects
Network resources and user/computer identity
Running external scripts
Working with the environment
Read Christa's previous columns:
Beginner's guide to scripting
It's time to increase your scripting expertise
Scripting: Connect users to network resources
Scripting School: More on connecting to network resources
|ABOUT THE AUTHOR:|
When Christa Anderson began working with Windows Server operating systems in 1992, she became increasingly interested in finding more efficient and flexible ways of performing routine tasks. Christa has written extensively about administrative scripting and taught technical sessions on the subject at conferences such as Comdex and CeBIT, helping people who had never done any scripting to write their own scripts in half a day. In addition to her interest in scripting Windows management, Christa is an authority on server-based computing and the program manager for Terminal Services licensing in Longhorn. If you have a scripting question for Christa, please e-mail her at scripting@SearchWinSystems.com.