The scripts that you convert into exe files, do not require FastTrack Scripting Host to execute. You can try these exe files without having FastTrack Scripting Host installed.
 | Help Desk Application Exe File Executable version of the script file converted in the movie above - and in this article.
Be aware that Active Directory operations will be performed, if you select a menu item and fill in the information. | | Backup Assistant Exe File Executable version of the backup assistant presented in this article.
Be aware that the backup operation will be performed, if you select a source and destination. |
A FastTrack Scripting Host script can be either compiled into a stand-alone exe file or if FSH.Exe is present, the script itself can just be executed. Select "Getting Started Wizard" from the "Help" menu in the editor for more information on executing regular scripts.
The drawback of creating an executable file over a regular script execution is that it's larger than the script file: A 10kb script file will be a little over 1MB as an exe file. And another drawback is that the original script must be kept as the source code for future editing, because the original script can never be retrieved from the exe file.
In a situation where a copy of FSH.Exe is already on target computers, or can be easily placed there, there is no reason to create an exe file. If you are compiling your script only to protect the content, you get the same level of protection simply by encrypting your script. For instance if you are already using FastTrack Logon, FSH.Exe is already installed on clients. And if you are creating a batch job for a server, it might be a better idea to just place a copy of FSH.Exe in the same directory as the script, to be sure you always have the original script for future editing.
On the other hand, there are many scenarios where a single exe file is the best choice. An exe file can run on any computer without including an FSH.Exe and FSH.Lic file and can simply be served on a network drive, usb stick, CD, DVD, from an intranet server or zipped in an email. And you have the option of packing additional files into your exe files (see next section), so an exe conversion would be useful in scenarios such as: - You have installation scripts in a relatively public area and you want to ensure the users do not copy the installation files.
- Your scripts are in a relatively public area, like an education center, and you have concerns that external users may copy your license key.
- Others administrators also have your private key and you want to make sure no one else can edit your scripts.
- You are a consultant writing scripts for a customer.
- You have little or no control over executing computers.
- Executing computers are not accessible for servicing.
Note that whether producing an exe file or using the original script it makes no difference to licensing requirements. Any compiled exe file will be compiled with license information of the creator and licensing rules remain the same. Download a 21-day trial:  Or register for our monthly Webinars to see FSH in action:  |
