Skip to main content

Enabling Diagnostic Logging in ScrewDrivers v7

Overview​

ScrewDrivers v7 simplifies diagnostic logging with user-friendly applications instead of registry editing. When troubleshooting printing issues, you can enable logging through the ScrewDrivers Logs app on servers and the ScrewDrivers Endpoint Client on client devices.

Log File Location​

ScrewDrivers v7 diagnostic logs are written to:

C:\ProgramData\Tricerat\Logs

Enabling Logging on Server/VDI​

The Session Host or VDI server runs the ScrewDrivers Logs application, which provides targeted logging options based on the type of issue you're troubleshooting.

Using the ScrewDrivers Logs Application​

  1. Open ScrewDrivers Logs: Find the application in the Start menu under Tricerat or ScrewDrivers
  2. Enable logging: Check the box next to "Enable"
  3. Select issue-specific logging: Choose the appropriate logging category for your issue

Logging Categories​

The ScrewDrivers Logs app offers several issue-specific logging options:

Printers Don't Build Enable this when printers aren't appearing in the user's session at all. This captures information about printer enumeration, profile application, and Session Agent communication.

Printers Build Slowly Enable this when printers appear but take too long to become available. This logs timing information and identifies bottlenecks in the printer creation process.

Print: No Output Enable this when print jobs are submitted but nothing comes out of the printer. This captures job submission, spooling, and communication with the Print Server.

Print: Bad Output Enable this when print jobs produce incorrect or corrupted output. This logs driver behavior, rendering, and data transmission.

Best Practices for Server Logging​

  • Select the most specific category: Choose the category that best matches your issue rather than enabling all options
  • Reproduce once: After enabling logging, perform the action that causes the issue once, then disable logging
  • Multiple issues: If you're experiencing multiple problems, troubleshoot them one at a time with targeted logging

Enabling Logging on the Print Server​

The Print Server component routes print jobs to physical printers.

Using the ScrewDrivers Logs Application​

  1. Open ScrewDrivers Logs: Launch the application on the Print Server
  2. Enable logging: Check the box next to "Enable"
  3. Select ScrewDrivers Print Server: Enable the Print Server logging category

This captures information about:

  • Job receipt from Session Hosts
  • Job routing to physical printers
  • Driver selection and rendering
  • Communication with network printers
  • Error conditions and retries

Enabling Logging on the Client (Endpoint)​

Client-side logging captures information about local printer enumeration and endpoint client behavior.

Using the ScrewDrivers Endpoint Client​

  1. Open ScrewDrivers Endpoint Client: Find the application in the system tray or Start menu
  2. Navigate to Logging Tab: Click the "Logging" tab in the client application
  3. Enable logging: Check the box next to "Enable"
  4. Select Endpoint Client: Enable the Endpoint Client logging category

What Client Logging Captures​

Client logging records:

  • Local printer discovery and enumeration
  • Printer driver information
  • Communication with the Session Agent
  • Client-side print job creation
  • Authentication and connection events

After Enabling Logging​

Once you've enabled logging on the appropriate component:

  1. Reproduce the issue: Perform the action that's causing the problem

    • For printer building issues: Disconnect and reconnect to the session
    • For printing issues: Submit a test print job
    • For client issues: Restart the endpoint client or reconnect

  2. Collect the logs: Navigate to C:\ProgramData\Tricerat\Logs and collect the newly created log files

  3. Disable logging: Return to the ScrewDrivers Logs app or Endpoint Client and uncheck "Enable" to prevent excessive log file growth

Interpreting Log Files​

ScrewDrivers v7 log files are text-based and include:

  • Timestamps for each event
  • Component identifiers
  • Severity levels (Info, Warning, Error)
  • Detailed diagnostic messages

When working with Tricerat support, provide the complete log files rather than excerpts. The support team uses correlation between events to diagnose issues.

Common Troubleshooting Scenarios​

Scenario: Printers Not Appearing in Session​

  1. Enable "Printers Don't Build" on the Session Host
  2. Enable "Endpoint Client" on the client device
  3. Disconnect and reconnect to the session
  4. Collect logs from both locations

Scenario: Print Jobs Not Printing​

  1. Enable "Print: No Output" on the Session Host
  2. Enable "ScrewDrivers Print Server" on the Print Server
  3. Submit a test print job
  4. Collect logs from both servers

Scenario: Slow Printer Creation​

  1. Enable "Printers Build Slowly" on the Session Host
  2. Enable "Endpoint Client" on the client device (optional)
  3. Disconnect and reconnect to the session
  4. Collect logs and note the timestamps

Best Practices​

  • Enable logging only when troubleshooting: Diagnostic logging can generate large files
  • Be specific: Use the most targeted logging category for your issue
  • One issue at a time: If multiple problems exist, troubleshoot them separately
  • Reproduce cleanly: Clear old logs, enable new logging, reproduce once, collect logs
  • Provide complete logs: When working with support, send all log files from the affected components
  • Disable when done: Remember to disable logging after collecting diagnostic information

Differences from Version 6​

If you're familiar with ScrewDrivers v6 logging, note these improvements in v7:

  • GUI-based configuration: No registry editing required
  • Issue-specific categories: Targeted logging reduces log file size
  • Endpoint Client integration: Logging controls built into the client application
  • Improved log formatting: More readable and easier to correlate events