Skip to Content Information Center
Scan to OCR

Scan to OCR

Windows print and driver installation and deployment primary escalation requirements

Requirements

Before proceeding, make sure to fill out the Main escalation information requirement and gather the Windows Print and Driver primary escalation requirements.

Gather the primary requirement for Windows Print and Driver Installation and Deployment‑related issues.

Requirement and relevanceHow to obtain

How are they installing/deploying the Lexmark driver? Is it through Silent Install / Uninterrupted Installation? Batch Deployment? Single Installation?

Info is used for simulation and analysis.

End user provided

Driver Type and Version used

Info is used for simulation and analysis.

  1. Go to Start > Control Panel > Printers / Devices and Printers.

  2. Right-click the Printer Object being used, and then click Properties.

  3. Go to About Tab, and then take a screenshot.

Or, from the Printing Preferences > Help > About Tab and take a screenshot.

Driver Setup (Point-and-Print, Direct IP, or Local port, indicate what port type)

Info is used for simulation and analysis.

End user provided

Customer's printing environment,

Info is used for simulation and analysis.

  • Operating System involved
  • Server and Client Information (Complete with Name, Service Pack & System Type)

Example: Windows Server 2008 Enterprise R2 SP2 x64 with Windows 7 Professional SP1 x86 clients

  1. Click on Start > Run.

  2. Type “msinfo32”, and then click OK.

  3. Click on File > Save.NFO

Screenshot of the error / message prompt that they are seeing

Info is used for simulation and analysis.

End user provided

Event Viewer file when the error occurs(.evtx files)

This info can help determine the cause of the error.

  1. Click on Start > Control Panel.

  2. Select System and Security (if you are in Category view) > Administrative Tools > Event Viewer.

  3. Select Windows Logs > right-click on Application, and then select Save All Events As... to save the .evtx file.

  4. Do the same for Windows Logs > System.

Setupapi log

This provides useful info for troubleshooting device installation problems.

For Windows 7, type %SystemRoot%\inf in the Run box or navigate to C:\Windows\inf.

The name of the log file is setupapi.dev.log. For Windows XP, type %systemroot% or navigate to C:\Windows.

Note:  The name of the file is setupapi.log.

LEGACY ID: FA869

Was this article helpful?
Top