Esko Logo Back to Esko Support
Choose your language for a machine translation:


Set up MediaBeacon database authentication using Windows authentication.

IMPORTANT: Once Windows authentication is configured, keep in mind that Java updates will uninstall the jTDS JDBC driver and a new installation will be required each time an update is made.


Microsoft SQL server authentication can be handled by either the database server or a Windows domain server. MediaBeacon uses Microsoft SQL server to handle authentication by default, using the database username and password configured for connection to MediaBeacon software.

To use a Windows domain server to handle the authentication instead of Microsoft SQL, the (jTDS) JDBC driver must be installed in the Java Classpath on each server being used for the MediaBeacon system. In this case, leave the "User" and "Password" fields blank in the Enterprise Tab of the  MediaBeacon Server-Side GUI App.


This guide assumes that MediaBeacon has already been installed, configured, and is running. This means that a database has already been created, connected with the MediaBeacon software, and that SQL server authentication is already being used.

Setting up Windows authentication prior to an installation is possible and will require fewer steps. For setting up Windows authentication prior to an installation, follow the directions below, taking care to remove any instruction regarding shutting down and restarting services. 

Download and Installation of JDBC Driver:

Installation of the jTDS JDBC driver onto each server running MediaBeacon software is required to allow for Windows authentication from MediaBeacon to MSSQL.

  1. Download the driver from this website:
    1. You will need to download the version of the driver as the jTDS.jar file packaged with MediaBeacon, version 1.3.1.
  2. The zip archive containing the files needed for the installation is: jTDS
  3. Unzip the folder and locate the DLL file located here within the downloaded folder: x64\SSO\ntlmauth.dll.
    1. Note that there are x64 and x86 folder paths, most of the time x64 is used. Ensure that the folder path matches the architecture of the server’s Java Runtime Environment (JRE).
  4. Copy the ntlmauth.dll file to the desktop on each server running a piece of MediaBeacon software. This includes Core, Preview, Webhead, and any Research nodes. The MSSQL database does not need this DLL file installed.
  5. Locate the Java native library folder path of the JRE installed on the  MediaBeacon server. For example: Program Files\Java\jre1.8.0_151\bin\.
  6. Move the ntlmauth.dll file from the server’s desktop to this bin folder.
  7. Shut down all MediaBeacon software, MediaBeacon services that are running, and any Java Virtual Machines (JVMs).
  8. Repeat this process for each server requiring the installation of the ntlmauth.dll file.
  9. Do not restart the MediaBeacon software components until completing the next sections.

Configuration of MediaBeacon User in MSSQL Database:

Once the jTDS JDBC driver is installed on the appropriate servers, configure the Windows user account . This is the account (typically "Administrator") used to install each MediaBeacon service as an admin in the database being used by MediaBeacon.

If the same Windows user account was used to install MediaBeacon during the setup of the MSSQL database, this user should already be added to the MSSQL database. Ensure that this user is configured as an administrator.

If the Windows user account has not been added as a user in the MediaBeacon database, add the account and ensure it is configured as an administrator.

Completing Configuration and Restarting MediaBeacon:

  1. Switch back to the MediaBeacon Core server and start the service.
  2. Under the Enterprise tab in the MediaBeacon Server-Side GUI App, remove the username and password, leaving them blank. All other fields are unchanged.
  3. Click Apply.
  4. Switch to the Admin tab, and click Start.
  5. The MediaBeacon system will now start and connect with the MSSQL database via Windows authentication rather than SQL authentication.
Article information
Applies to

MediaBeacon 8.5



Last revised


Author ZASC
Case Number