Skip to main content

Enabling Diagnostic Logging in ScrewDrivers v6

Overview​

When troubleshooting printing issues in ScrewDrivers v6, enabling diagnostic logging provides detailed information about component behavior and helps identify the root cause of problems. This guide shows you how to enable logging for each ScrewDrivers v6 component through registry configuration.

Log File Location​

All ScrewDrivers v6 diagnostic logs are written to:

C:\ProgramData\Tricerat\Logs

Enabling Logging on the App Server (Session Host/VDI)​

The App Server (also called Session Host or VDI Server) runs multiple ScrewDrivers components that handle printer creation and print job processing. You'll need to enable logging for three registry keys:

ScrewDrivers Driver UI v6​

This component handles the printer driver user interface.

Registry Path:

HKEY_LOCAL_MACHINE\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Driver UI v6

Value to Set:

  • Name: Mode
  • Type: REG_DWORD
  • Value: 1

ScrewDrivers Driver v6​

This component handles core driver functionality.

Registry Path:

HKEY_LOCAL_MACHINE\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Driver v6

Value to Set:

  • Name: Mode
  • Type: REG_DWORD
  • Value: 1

ScrewDrivers Port v6​

This component handles the print port and job routing.

Registry Path:

HKEY_LOCAL_MACHINE\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Port v6

Value to Set:

  • Name: Mode
  • Type: REG_DWORD
  • Value: 1

PowerShell Script for App Server​

You can enable all three App Server logging components with this script:

# Enable ScrewDrivers v6 App Server logging
$basePath = "HKLM:\SOFTWARE\Tricerat\Simplify Logging\Logs"

# Driver UI
New-ItemProperty -Path "$basePath\ScrewDrivers Driver UI v6" `
    -Name "Mode" -Value 1 -PropertyType DWORD -Force

# Driver
New-ItemProperty -Path "$basePath\ScrewDrivers Driver v6" `
    -Name "Mode" -Value 1 -PropertyType DWORD -Force

# Port
New-ItemProperty -Path "$basePath\ScrewDrivers Port v6" `
    -Name "Mode" -Value 1 -PropertyType DWORD -Force

Write-Host "App Server logging enabled. Logs will be written to C:\ProgramData\Tricerat\Logs"

Enabling Logging on the Print Server​

The Print Server component routes print jobs to physical printers.

Registry Path:

HKEY_LOCAL_MACHINE\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Print Server v6

Value to Set:

  • Name: Mode
  • Type: REG_DWORD
  • Value: 1

PowerShell Script for Print Server​

# Enable ScrewDrivers v6 Print Server logging
New-ItemProperty -Path "HKLM:\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Print Server v6" `
    -Name "Mode" -Value 1 -PropertyType DWORD -Force

Write-Host "Print Server logging enabled. Logs will be written to C:\ProgramData\Tricerat\Logs"

Enabling Logging on the Client​

Client-side logging captures information about printer enumeration and print job creation on the endpoint device. The registry path differs depending on your connection protocol.

RDP Clients​

For RDP connections, use the standard registry path:

Registry Path:

HKEY_LOCAL_MACHINE\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Client v6

Value to Set:

  • Name: Mode
  • Type: REG_DWORD
  • Value: 1

Citrix Clients​

For Citrix connections, client components run as 32-bit processes on 64-bit systems, so they use the WOW6432Node path:

Registry Path:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tricerat\Simplify Logging\Logs\ScrewDrivers Client v6

Value to Set:

  • Name: Mode
  • Type: REG_DWORD
  • Value: 1

PowerShell Script for Clients​

This script enables logging for both RDP and Citrix clients:

# Enable ScrewDrivers v6 Client logging

# RDP path
New-ItemProperty -Path "HKLM:\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Client v6" `
    -Name "Mode" -Value 1 -PropertyType DWORD -Force

# Citrix path (WOW6432Node for 32-bit processes on 64-bit OS)
New-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\Tricerat\Simplify Logging\Logs\ScrewDrivers Client v6" `
    -Name "Mode" -Value 1 -PropertyType DWORD -Force

Write-Host "Client logging enabled. Logs will be written to C:\ProgramData\Tricerat\Logs"

After Enabling Logging​

Once you've enabled logging:

  1. Reproduce the issue: Perform the action that's causing the problem (print a document, connect to a session, etc.)
  2. Collect the logs: Navigate to C:\ProgramData\Tricerat\Logs and collect the newly created log files
  3. Disable logging when done: Set the Mode value back to 0 or delete the value to prevent excessive log file growth in production

Disabling Logging​

To disable logging, you can either:

Option 1: Set Mode to 0

Set-ItemProperty -Path "HKLM:\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Print Server v6" `
    -Name "Mode" -Value 0

Option 2: Delete the Mode value

Remove-ItemProperty -Path "HKLM:\SOFTWARE\Tricerat\Simplify Logging\Logs\ScrewDrivers Print Server v6" `
    -Name "Mode"

Best Practices​

  • Enable logging only when troubleshooting: Diagnostic logging can generate large files and impact performance slightly
  • Be specific: Enable logging only on the component you're troubleshooting (App Server, Print Server, or Client)
  • Reproduce once: Capture one clear instance of the problem rather than letting logs accumulate
  • Clean up: Disable logging and archive or delete log files after collecting diagnostic information
  • Provide to support: When working with Tricerat support, compress and send all log files from the relevant component