JSI Tip 7001. When you press Finish in the Windows Server 2003 Add Print Wizard, you receive 'Unable to Install Printer. The printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 drivers'?

Kernel mode drivers are monolithic drivers that hook into the operating system at the kernel level. Poorly written drivers can cause blue screen STOP errors.

Windows Server 2003 does NOT support Kernel mode print drivers by default, but an administrator can disable the policy.

If you encounter the subject message, I strongly advise you to find a non-Kernel mode driver, and install it locally for a remote network printer:

01. Control Panel / Printers and Other Hardware / Printers and Faxes / Add Printer.

02. Press Next in the Add Printer Wizard.

03. Select Local print and clear the Automatically detect and install box.

04. Press Next.

05. Select Create a new port and toggle Local Port.

06. Type the printer path into the Port name using the \\ServerName\PrinterShareName syntax, and press OK.

07. Press Next.

08. Select a Windows Server 2003 or Windows 2000 driver for the printer.

09. Press Next and follow the instructions to complete the wizard.

NOTE: When the driver is updated on the server, you will NOT get the updated driver.



Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.