SetupBatcher
Top  Previous  Next


SetupBatcher makes repetitive setup and management operations easy - carry out a single command on many machines, or a large number of commands on one or many machines at once.

To use SetupBatcher you need a script. A script is a clear text file divided into sections that contains data - instructions of what to do, and a list of machines to carry out instructions on.
 
·Data: The data - i.e. list of items - names, accounts, passwords, directories, registry entries, files etc. - to process by SetupBatcher - can be imported from a file, the clipboard or from a remote FTP or E-mail server. When working with existing accounts or files, the list can be created automatically by a SetupBatcher data extraction command. Account properties can also be exported from SetupExplorer.  
·Commands: SetupBatcher has about 190 built-in commands and functions. The functionality can be extended by calling any local or remote DOS utility or program via the command line, or by calling VBscript commands.  
·Machines: Contains NetBIOS names of NT based (NT, 2000, XP or 2003) machines. A list of all currently visible machines in a domain can be created by using the action menu. (The machine list is not used for Linux or Novell servers.)  

Scripts can be started in GUI mode, called from the command line by other applications, or executed by the schedule service at a specific time every day. You can write scripts in the built-in editor, or with any clear text editor like notepad. This manual includes many examples that you can modify and build your own scripts from.

Resume scripts: It is possible to interrupt a script, save it, and continue later at the exact position where it was interrupted.

Auto-retry scripts: When errors occur in a scripts that runs across many Windows machines, SetupBatcher can automatically continue with next machine and retry with problematic machines in a couple of minutes, see the auto retry function.

Error handling: Unlike many other tools, SetupBatcher verifies that all commands are executed correctly; successful commands are marked in the script, errors are logged, and it is possible to retry, ignore or abort commands that fails. The standard SetupBatcher error handling can be replaced with your own code that is executed when an error occurs, this is useful for example to send a message somewhere if there are problems in a scheduled script.