Consider the following scenario:

• You run a Remote Desktop session on a computer that is running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2.
• The Use Remote Desktop Easy Print printer driver first policy is enabled. This policy redirects the print function to a client printer first.
  Note: By default, the Use Remote Desktop Easy Print printer driver first policy is enabled on a computer that is running Windows 7 or Windows Server 2008 R2.
• The printer on the client computer uses a driver that defines a custom form size.
  Note: A custom form size is a custom paper size.

In this scenario, the client printer may print the printout by using an incorrect paper size.

The PushPrinterConnections.exe utility reads the printer connection settings from Group Policy and then adds the appropriate printer connections to the client computer. However, this utility has only a 64-bit version that is built into Windows Server 2008 x64 Edition. When you try to use this utility and Group Policy to deploy printer connections to a client computer that is running an x86 version of a Windows operating system, the following event log is logged on the client computer:

Event Type: Error Event Source: UserInit Event Category: None Event ID: 1000 Date: <Date> Time: <Time> User: N/A Computer: <Computer Name> Description: Could not execute the following script PushPrinterConnections.exe. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

This update provides a 32-bit printer driver and the PushPrinterConnections.exe utility for Windows Server 2008.

When you try to add one or more 32-bit printer drivers on a 64-bit printer server, you receive the following error message:

The folder you specified doesn’t contain a compatible software driver for your device.

Changing a printer driver from a Printer Properties, Advanced Tab, Driver drop down list, can have unexpected results if a non-compatible driver is selected. This method of changing a driver is not the recommended method for changing printer drivers.

While viewing the properties of a printer on a Windows 2003 Print Server from a Vista or XP client, you modify the Printer Properties several times rapidly in succession, you may see a pop-up message with the following error:

“An unexpected error occurred in the print driver. Close the current driver window and retry the operation.”

Consider the following scenario:

You have a printer driver installed on the system. You attempt to install a newer version of the driver. Both the new driver and the old driver have the same name (i.e. “ABC Model 1000″). After you install the driver, the old driver’s files may still be used when printing, or the driver may no longer function correctly because registry entries for the driver are inconsistent.

You try to remotely view the printer Security tab on a print server that is running an x86-based edition of Windows Vista or of Windows Server 2008 from one of the following client operating systems:

• Windows 7, x64-based editions
• Windows Server 2008 R2, x64-based or IA-64-based editions

When you do this, you receive the following error message on the Security tab:

The requested security information is either unavailable or can’t be displayed.

Note: You do not receive this error when you remotely view the printer Security tab on a print server that is running an x86-based edition of Windows 7.

On a Windows Vista or Windows Server 2008-based computer, you configure the printer item in Group Policy Preferences. When you try to configure the printer item for printers that use third-party drivers, Group Policy Preferences stops responding (hangs).

When this problem occurs, you cannot perform other operations and you cannot log off the computer.

In a network environment, you disconnect from a Remote Desktop session on a terminal server that is running Windows Vista or Windows Server 2008. Then, when you log on to the terminal server from a console, the default printer setting on the terminal server is changed.

When this problem occurs, you may notice that there is no default printer or that the default printer is changed to another printer.

On a computer that is running Windows Vista or Windows Server 2008, you view a Web site and then try to print to an Internet Printer Protocol (IPP) printer. However, the print job fails.

When this issue occurs, in the System event log, you see the following text:

Log Name: System
Source: Microsoft-Windows-PrintSpooler
Event ID: 6161
Level: Error
Keywords: Classic
Description: The document document name, owned by user name, failed to print on printer printer name. Try to print the document again, or restart the print spooler.
Data type: date type.
Size of the spool file in bytes: size.
Number of bytes printed: bytes.
Total number of pages in the document: page number.
Number of pages printed: page number.
Client computer: computer name.
Win32 error code returned by the print processor: error code

This issue occurs if all of the following conditions are true:

• The protected mode of Internet Explorer is enabled for the Web site that you are trying to print from.
• The printer driver that you use does not support Enhanced Metafile (EMF) printing.