I have a test workstation on which I write and test my scripts, but when I move them to production on a server, all the paths to the Microsoft Windows 2000 Server Resource Kit or Microsoft Windows NT Server 4.0 Resource Kit and other text input files are different, so I have to change the code.

Your setup isn't the optimal way to go. On my desktop PC, I store my scripts in a folder structure in which each script is in its own folder. I duplicate this folder structure on a production server. Inside each folder are old versions of the script, text input files that the script parses, log or other output files that the script creates, and any other nonĀ­resource kit .exe files that the script calls. I installed the resource kit in the same location on both my desktop PC and the production server. (Note that installing the resource kit to a location with no spaces in the path prevents future problems. The default NT 4.0 resource kit installation path has no spaces, but the default Win2K installation path has spaces.)

After I test and verify that a script is ready for production, I copy the script-folder contents to the production server. If the script performs a task that should take place at regular intervals, I schedule the task in Task Scheduler. Alternatively, you can use Microsoft Visual SourceSafe (VSS) to deploy a script, if VSS is set up in your environment.