Skip to main content

ScrewDrivers Scanning Client

Pro & Enterprise Only

The scanning client is available exclusively in ScrewDrivers Pro and Enterprise editions. For endpoint printing features available in all editions, see Endpoint Client Application.

The ScrewDrivers Scanning Client application provides the client-side interface for managing scanner configurations in remote sessions. While the Session Agent controls most scanning behavior through session settings, the client app lets users (and administrators) configure scanner priorities, test scanner functionality, manage scanning protocols, and troubleshoot client-side scanning issues. This reference details all functions available in the Scanning Client app across its five main tabs: Scanning Settings, Scanners, Camera, Logging, and About.

Overview​

The ScrewDrivers Scanning Client installs on every workstation that users connect from to access remote sessions where scanning is enabled. Most users won't need direct access to this app for routine scanning—the Session Agent handles configuration automatically based on assigned session settings. However, the app proves invaluable when users need to test scanners, change scanner priority, or troubleshoot scanning issues.

Understanding the Scanning Client app is particularly important for administrators supporting remote scanning deployments. The app provides diagnostic capabilities, scanner testing functions, and configuration options that help you identify and resolve scanning problems quickly.

Opening the Scanning Client App​

To access the application:

  1. Open the Start menu
  2. Navigate to Programs
  3. Click "ScrewDrivers Scanning Client"

The app opens with the Scanning Settings tab active and the tab bar collapsed by default. You can hover over icons on the left side to see tooltips showing tab names, or click the hamburger icon to expand the tab bar and view full tab names.

Common Interface Features​

All tabs except About share these characteristics:

Apply button: After making changes on any tab, click Apply in the upper right corner to save your modifications. The Apply action saves all current values across all tabs—you can't save changes on a per-tab basis.

Close button: Click the X in the upper right corner to exit the app after you've applied all needed changes.

Unsaved changes prompt: If you make changes without applying them, the app prompts you to save before switching tabs or exiting.

Scanning Settings Tab​

The Scanning Settings tab provides configuration options for core scanning session behavior, including RDP encryption and compression, duplex scanning options, and virtual channel settings.

Note: Specific configuration details for this tab should be referenced from the ScrewDrivers Scanning Client documentation or confirmed with Tricerat support. Administrator-configured session settings typically control these options, with the client tab providing visibility into effective settings or allowing user overrides where permitted by session settings.

Scanners Tab​

The Scanners tab displays all scanner drivers detected on the client or client's network that can be used in remote sessions. This is the most important tab for troubleshooting and scanner management.

Scanner List​

The main area shows all available scanners listed by name, with a Type column indicating the protocol each scanner uses: TWAIN, WIA, CAM, or RPOS.

RPOS (Repository) always appears in the scanner list as a special scanner type. RPOS is Tricerat's proprietary protocol that lets you "scan" images that already exist elsewhere—on a USB drive, C: drive, or connected digital camera. This brings existing digital images into your scanning workflow without requiring an actual scanner. Currently, RPOS supports only bitmap (.bmp) images.

Managing Scanner Priority​

Scanners appear in priority order, with the first scanner in the list automatically set as your default scanner for the session. You have complete control over scanner organization:

Changing Scanner Priority: Select a scanner and drag it to a new position in the list. When you move a scanner to the top position, it automatically becomes your default scanner for the session. This proves particularly useful when the default scanner isn't the right choice for your needs or when you need to test different scanners.

Enabling/Disabling Scanners: You can turn individual scanners on or off in the list. When a scanner is enabled, it becomes available during remote sessions. When disabled, it won't appear as an option even if it's installed and functional.

Scanner Information and Testing​

The Scanners tab provides capabilities for viewing scanner details and testing scanner functionality:

Viewing Scanner Information: Select a scanner and click "Test Scanners" to open a detailed dialog box. You'll see the manufacturer's name, product name and family, current version, and which scanning protocol it uses (TWAIN, WIA, CAM, or RPOS).

Testing Scanners: Before starting a scanning session, you can verify that your scanner works properly. When the Test Scanner dialog appears after clicking Test Scanners, click Yes to run a quick test. The results appear in a Test Results dialog box, showing whether the scanner is ready for use. This helps identify driver issues, connection problems, or protocol mismatches before users attempt production scanning.

Tip: It's actually pretty rare for the default scanner to be exactly the right one for your needs, or even to have the correct driver type selected. If you're having trouble with scanning, the first thing to check is whether you've got the right scanner selected with the correct driver type. The Scanning Client app makes it easy to test and switch between options.

Refreshing Scanner Information​

Query Scanners: If you've recently installed a new scanner or made changes to your scanner setup, click "Query Scanners" to refresh the list. This re-scans your system for available scanner drivers and updates the displayed list.

Important: Querying scanners might change the order of scanners displayed, and any scanner driver that fails the query will be automatically turned off to prevent issues during your session. After querying, verify that your preferred scanner is still enabled and in the correct priority position.

Camera Tab​

The Camera tab configures settings for using digital cameras as scanning sources. When you use a camera as a scanning device, this tab lets you manage camera-specific configuration options.

Note: Camera tab configuration details vary by camera type and driver. Consult the ScrewDrivers Scanning Client documentation or Tricerat support for specific camera configuration guidance appropriate to your camera model and connection type.

Logging Tab​

The Logging tab provides diagnostic logging options from the ScrewDrivers Scanning client workstation. This logging information is essential for debugging and problem tracking.

Using the Logging Tab​

Important: Because Tricerat support primarily uses this logging information, you shouldn't change any default values or use any commands on this tab unless Tricerat Support instructs you to do so. Incorrect logging settings can generate excessive log data, impacting client performance and consuming disk space.

The Logging tab typically includes controls for:

  • Log level: Verbosity of logging (Error, Warning, Info, Debug, Trace)
  • Log file location: Where log files are stored on the client
  • Log file size limits: Maximum size before log rotation
  • Category options: Enable/disable specific logging categories
  • Management buttons: Clear logs, open log directory, or export logs for support

Working with Support​

When troubleshooting scanning issues with Tricerat support:

  1. Support will instruct you on which logging level to enable
  2. Reproduce the scanning issue while logging is active
  3. Use the log management controls to locate and export logs
  4. Provide the log files to support for analysis
  5. After resolving the issue, remember to disable detailed logging to prevent performance impacts

About Tab​

The About tab provides information about the ScrewDrivers Scanning Client installation and includes options for managing Citrix plugin registration.

Component Information​

The tab displays all DLLs (dynamically linked libraries) installed for the ScrewDrivers Scanning Client, listed alphabetically by name. For each component, you'll see:

  • Component name
  • Version number
  • Full installation path (hover your mouse pointer over the name to display a tooltip showing the complete path)

This information helps support staff verify correct installation, identify version mismatches, and troubleshoot component-specific issues. When contacting support about scanning problems, having this version information available can speed up troubleshooting.

Citrix Plugin Registration​

The About tab contains options for registering Tricerat's Citrix plugin, either for the currently logged-in user or for all users.

If you must re-register the Citrix plugin, the "For all users" option is generally the better selection—typical end users don't have the correct permissions to execute this action, so user-level registration often fails.

Registration scenarios that might require using this function:

  • After Citrix Workspace updates that affect plugin registration
  • When users report that scanning doesn't work in Citrix sessions (but works in other connection types)
  • Following Citrix Receiver/Workspace reinstallation
  • When instructed by Tricerat support during troubleshooting

Help and Support Resources​

The About tab displays a Help link that provides access to documentation and support resources:

  • Product documentation
  • Knowledge base articles
  • Support contact information
  • Community forums

Client Configuration Deployment​

While users can configure the Scanning Client app manually, administrators can automate configuration for entire organizations by deploying registry settings that mirror the app's configuration. This ensures consistent settings across your environment and removes the need for users to access the app at all.

Registry-based deployment supports:

  • Scanner priority settings
  • Enabled/disabled scanner states
  • Default scanner selection
  • Scanning protocol preferences
  • Session options and preferences

Contact support@tricerat.com for assistance with registry-based deployment, including the specific registry keys and values that correspond to each app setting.

Relationship to Session Settings​

It's crucial to understand that the Session Agent dictates most scanning behavior through Scanning Session Settings assigned to owners. Client settings typically apply only when the Session Agent allows them, or they provide visibility into effective settings rather than control.

This hierarchy ensures administrators maintain control over scanning behavior while giving users visibility and limited flexibility where appropriate. When troubleshooting unexpected scanning behavior, always check both the client configuration and the scanning session settings assigned to the affected owner to understand which takes precedence.

Common Troubleshooting Scenarios​

The Scanning Client app helps resolve several common scanning issues:

Scanner not appearing in remote session: Check the Scanners tab to verify the scanner is enabled and listed. If missing, click Query Scanners to refresh the list. If still missing, the scanner driver may not be installed or compatible with ScrewDrivers Scanning.

Scanning fails with specific scanner: Use Test Scanners function to verify the scanner works. Try changing the scanner's driver type (TWAIN vs. WIA) to see if a different protocol resolves the issue. Check the Logging tab output (if enabled by support) for specific error messages.

Wrong scanner selected by default: Drag your preferred scanner to the top of the list on the Scanners tab. Apply the changes. This makes that scanner the default for your scanning sessions.

Version mismatch errors: Check the About tab to verify the client version. If automatic client updates are enabled in session settings, the Session Agent should synchronize versions automatically. If not, you may need to manually update the client to match the session agent version.