Navigation: Features >
Update ODBC DSN configurations and driver files on remote hosts.
The System DSN (Data Source Name) that for the action. The drop-down list is initialized from the local system.
The selected System DSN will be copied to the remote system.
The selected System DSN will be removed from the remote system. The options to copy additional files are unavailable.
The selected DSN will be will be queried and information about the driver and database will be displayed. The options to copy additional files are unavailable. This is action is non-destructive.
Attempt to Copy Driver Files
Check this box if AutoAdministrator should attempt to copy the driver file that is associated with the ODBC driver as well.
Why "attempt"? Many ODBC drivers (e.g. MS SQL Server) consist of dozens of files that make up the ODBC driver, all of which may depend on other ODBC DLLs. Copying drivers like these using AutoAdministrator will not produce the desired result since AutoAdministrator doesn't know which files to copy. Copy additional driver file(s) can be used to specify additional extra files (see below).
Some ODBC drivers (e.g. MySQL) only consist of one file (the file referenced in the ODBC configuration) and can therefore easily be copied and rolled out with AutoAdministrator.
Always Overwrite Existing Settings
By default, AutoAdministrator does not overwrite existing settings and files. If the specified DSN name does already exist on the remote machine then the configuration will not be copied. This also applies to files that already exist on the remote machine.
Activate this option to force AutoAdministrator to always copy the ODBC settings (and files), regardless to whether they exist on the remote machine or not.
Copy Additional Driver Files
This option provides a mechanism to copy extra files in cases where the ODBC driver consists of more than a single file. Files specified here will be copied to %systemroot%\system32, regardless of their original location. See File Copy for a description of file dialog controls.
Replace locked files during next reboot
This option can be used to schedule the replacement of files that are locked by the operating system (e.g. the file is currently in use). The files will be copied to %systemroot% and moved to %systemroot%\system32 when the machine is rebooted. AutoAdministrator can be used to schedule a subsequent reboot on remote machines, see Shutdown / Reboot.