I can manually install a printer driver on a server and that shows up as a configured printer just like on a workstation. However there are applications where I can provide a UNC name to a printer and the system will just print to that printer without installing a printer driver.

How is the system able to print to a printer without actually installing a printer driver?


The Windows Server 2003 Resource Kit Tools has the utility PRINTDRIVERINFO.exe This will show details about installed printer drivers.

Run it without any command line parameters to get a list of all installed drivers.

The command line switches:

  • /S = server name to look at a remote server
  • /P = printer name to look at a specific printer
  • /D = driver name to look at a specific driver
  • /F = file name of a driver to look at a specific file

The resource kit can be downloaded here: Windows Server 2003 Resource Kit


An application printing to a UNC path could be doing one of two things.

  1. It could be spooling a raw print file which bypasses the printer driver.

  2. It could be mapping the printer in the background without you realising, in this case the driver will be downloaded and the printer mapped automatically.


I can use the Powershell CmdLet Get-PrinterDriver now. Like:

Get-PrinterDriver -Name * -ComputerName "SERVER"


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.