ODBC

With this feature you can roll out ODBC DSN configurations and ODBC driver files to remote computers.

Choose the System DSN (Data Source Name) that you would like to copy to the remote machines. Only System DSN can be copied at this time.

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.

Check this box if you would like AutoAdministrator to attempt to copy the driver file that is associated with the ODBC driver as well.

Why "attempt"? Unfortunately, many ODBC drivers (e.g. MS SQL Server) consist of dozens of files (mostly DLLs) that make up the ODBC driver, all of which depend on other ODBC DLLs. Copying the driver like these using AutoAdministrator will not produce the desired result since AutoAdministrator doesn't know which files to copy. If you know which files to copy please read the Copy Additional Driver Files section below.

The good news is that some ODBC drivers (e.g. MySQL) only consist of one file (the file referenced in the ODBC configuration) and can therefore be easily copied and rolled out with AutoAdministrator.

The file that will be copied when using this option is the one specified by the Driver value in the HKLM\Software\ODBC\ODBCINST.INI\<Driver> registry key, where <Driver> is the name of the referenced ODBC driver.

Use this option only if you know exactly what you are doing as overwriting system files can destabilize parts (e.g. ODBC) of or the entire Operating System. NETIKUS.NET ltd cannot be held responsible for any damage you are inflicting on systems if incorrect files are copied and/or replaced. Use this option with caution.

If the ODBC driver you would like to roll out consists of more than one file (e.g. MS SQL Server) and you know exactly which files belong to this particular ODBC driver, then you can copy these files to the remote servers. All files you specify here will be copied to the remote %systemroot%\system32 directory, regardless of their original location.

If the files you are trying to copy are locked by the Operating System, then you can check this box to have them replaced with your version during the next reboot. In this case the files will be copied to the remote %systemroot% directory first and then be moved to the %systemroot%\system32 directory when the machine is rebooted.