Skip to main content

Deploying ScrewDrivers with Microsoft Intune

You can deploy ScrewDrivers components to your endpoints using Microsoft Intune (also called Microsoft Endpoint Manager). This guide walks you through creating Win32 application packages and configuring the necessary SQL driver dependencies for successful deployment.

Creating the ScrewDrivers Win32 Package​

Start by creating a Win32 .intunewin package using the default settings. Follow Microsoft's packaging instructions carefully, ensuring that the ScrewDrivers install file is the only file in the source directory and is also specified as the setup file.

Configuring SQL Driver Dependencies​

ScrewDrivers requires two Microsoft SQL drivers to function properly: the Microsoft ODBC Driver for SQL Server and the Microsoft OLE DB Driver for SQL Server. You'll need to package these as separate Intune applications and configure them as dependencies.

Here's how to set up each driver:

  1. Download both MSI files from Microsoft (or from the Tricerat download links if provided).
  2. Create an .intunewin package for each driver and add them as new Win32 applications in Intune.
  3. For the ODBC driver's install command, add the parameter IACCEPTMSODBCSQLLICENSETERMS=YES (note the "ODBCSQL" in the parameter name).
  4. For the OLE DB driver's install command, add the parameter IACCEPTMSOLEDBSQLLICENSETERMS=YES (note the "OLEDBSQL" in the parameter name).
  5. Once both driver packages are created, add them as dependencies for your ScrewDrivers Win32 application.

This dependency configuration ensures that Intune installs the required SQL drivers before deploying ScrewDrivers to your endpoints.

Troubleshooting​

If you encounter installation issues, check the MSI logs that Windows Installer creates during deployment. You'll find these logs in %windir%\Temp (typically C:\Windows\Temp). Sort the directory by date and look for files matching the pattern MSI*.log.

During a ScrewDrivers installation, you'll typically see two log files: one from the EXE launcher and another from the msiexec process itself. If you've configured SQL driver dependencies, you'll also find separate log files for those installations. These logs provide detailed information about what succeeded and what failed during the deployment process.