Server 2008 R2 SP1 with Remote Desktop Services.

Redirected printers settings are not saved after log off. 

Is it possible to save redirected printers settings between sessions ?

I have printers being deployed with Group Policy Preferences to areas of computers.  In most areas I dont set a default printer in the policy as there is multiple printers in the area and depending on which room they are in they all may want a different default printer.  In this case, what we are finding is the windows automatically sets the default printer as the first one alphabetically.  This is causing problems for users as they have to keep changing their default printer.  Is there a way to disable this feature or let the user set default printer stick?

Thanks!

Hi

I've been racking my brains over this for a while... we have the following setup:

Windows Server 2008 - sharing multiple printers out to a variety of clients.

Clients - xp, windows 7.

Problem: The XP clients are fine, all of the time. SOME of the windows 7 clients, have an issue: their printers (all mapped to this server, local printers are ok) are occasionally (once a day or so) showing as offline.

In this state it is not possible to remove and re-add the printers; the only way we have been able to temporarily solve it for each user, is to restart the (client side) print spooler service. Note that the service does not stop, all appears normal but the printers show as offline until the spooler service is restarted. there are no errors in the event logs.

any clues as to how one might nail down the source of this problem?

thanks

I have multiple Windows Server 2008 R2 print servers (member servers in a single domain). Several are new and I set up the default print server security properties according to "Assigning Delegated Print Administrator and Printer Permission Settings in Windows Server 2008 R2" (http://technet.microsoft.com/en-us/library/ee524015%28v=ws.10%29.aspx). I added an Active Directory global group called "PrintQueueMgr" which contains all of our help desk support staff accounts. To this group I gave permission to Manage Documents.

I added several hundred shared printers which are published in Active Directory. End users are connecting to these print servers and printing. Call these print servers PRT01 PRT02 PRT03. Our help desk support staff can open Print Management console, add the aforementioned print servers PRT01 PRT02 PRT03 and see all printers (several hundred printers on 3 print servers). They can manage print jobs on those print servers. All is good.

However, we also have a couple of Windows Server 2008 R2 application servers which also have the Print and Document Services role. Call these print servers APP01 APP02. A different sysadmin added local printers (they are not shared). The application generates print output on behalf of users of the application also running on this server. I am not familiar with the application setup, but the printers are very ordinary using a Standard TCP/IP port and built-in print drivers (a variety of Windows Server 2008 R2 print drivers, mostly for HP LaserJet models).

Knowing I would need to grant the AD group PrintQueueMgr with permission to Manage Documents, I did that at the print server security tab on both APP01 and APP02. Also realizing that this permission is not inherited, I selected a sample printer and added the same permission. I restarted the print spooler service. I also added a new local printer with Standard TCP/IP port. I noted that the new printer inherited the Manage Documents permission for the PrintQueueMgr AD group. I did not share the new local printer.

The help desk support staff can add the application servers APP01 and APP02 to their Print Management console. But they cannot see any printers! They can see print drivers, forms, and ports for APP01 and APP02. There is one shared printer on APP01 (not sure why) and that printer is the only printer that is displayed in the Print Management console.   From an RDP console session on APP01 I can PING the computer which the help desk support staff is logged onto (so yes, the host (A) record does exist and is resolvable by the DNS server configured for APP01).

Does the Print Management console only manage shared printers? I don't find this limitation in the documentation. We do not wish to share the application server's printers. Only the application running on APP01 and APP02 should create job output for the printers.

When I, a domain administrator, logon to the same Windows 7 workstation used by the help desk support user account, I can see all of the printers on APP01 and APP02!

What else can I try?

Hello everybody !

I have a problem with the "Windows fax and scan" utility in Windows server 2008. I use RemoteApp because, when I have installed the Windows 2008 fax server, other fax clients of my Workgroup can't log in, and I use Linux. Therefore, I prefere use RemoteApp, that's all for explications "Why you use RemoteApp fo this ?". My problem is, when I use RemoteApp with a standard user permission. I launch windows fax and scan utility and setup a fax account. I get "You do not have security permissions to do this operation. Contact your fax Administrator for this operation." I have added my standard user in the fax group and the security tab of Fax server control. I change the account type to Administrator too, but no success...

Any ideas ? Thanks for your help !

Sorry for bad english, I'm french :) (And 14 years old)

I'm trying to install 32 bit printer drivers on our Windows Server 2008 R2 print server for various printers including Xerox copiers and some older HP printers.  The 64 bit versions (universal printer drivers for HP and Xerox) of the drivers install without problems for the most part but I get stuck on the 32 bit install.  It wants the 32 bit NTPRINT.INF/NTPRINT.DLL files from the I386 directory of our Windows XP SP3 which has been copied to the local server directory.  It asks for the files in D:\I386 or C:\I386 but when I browse to those directories and select the NTPRINT files and click OK it just keeps asking for the same file.  I have no choice but to abort the driver install. 

We're in the process of moving to AD this summer and eventually moving to Windows 7 Enterprise 64 bit but in the mean time, we still have a boatload of Windows XP systems on campus that still need 32 bit printers in order to print.  Any ideas?

We are having problems very similar to the issues described in

http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/e2acb625-027d-47a9-b4a7-1616e270bcbc

Every day we are having 8-15 users calling saying they are unable to print. The local Spoolsv.exe service is changing the registry key entry for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PS (v5.2) or for what ever their default printer is. We have tried with a different version of the driver and it will happen with our Xerox as well if that is their default. The problem itself is easy enough to fix by deleting the corrupt key, reinstalling the default printer and restarting the print spooler so they can print again. The problem is that it may happen again to them the next day, or it may be a month later. The specific entries being modified are string values forDependant Files, Help File and Monitor.

The errors in event log show:

The document Untitled - Notepad, owned by USERNAME, failed to print on printer {GUID}. Try to print the document again, or restart the print spooler.
Data type: NT EMF 1.008. Size of the spool file in bytes: 5332. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\COMPUTERNAME. Win32 error code returned by the print processor: 5. Access is denied.

We are printing to a Win2008 R2 Server, We have Printer Driver Isolation Set on All machines for all drivers as well on the Print Server. KB2467753 has been applied to all the machines as well as our print server.

http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/19bb64cc-249e-4f36-a02d-2b43703d5a0d

Suggests that we turn off CSR (Client-Side Rendering) for all of our printers. This simply by passes the problem that the local drivers are being corrupted, it will tax our print server much more and will take longer to print. We need to find out WHY this registry key is being modified in the first place by the spoolsv.exe process and not try to bypass local rendering.

As a weird side note even with this driver corruption you are still able to print from adobe reader, they must be using their own driver files.

Hello All,

I am having a strange issue with a handful of our windows 7 clients.

What we have:

Recently I have setup a new 2008 R2 x64 server to hosts the printers in our school district. I have tried to keep things simple by using global print drivers that are available.  I only have the lastest hp global driver, the lastest xerox global driver, a dell printer driver, and a minolta driver. All of out client machines are running windows 7 enterprise and are both x64 and x86.

The Problem:

A handful of windows 7 machines seem to be missing the dependent files that should be listed under the properties of the driver in "print server properties". It has happened on x64 and x86 clients and pretty much prevents the clients from using any functionality of the printer they are connected to. At first I thought it may have been a xerox driver issue, but after seeing the issue on a few hp printers I am thinking its a problem with point and print somewhere? Any information that may help us resolve this problem would be greatly appreciated, thanks for your support! :D

Hi,

I'm facing an issue with a print driver on client PC being broken.

Problem Description:

During normal operation of some client PCs, the HP Universal Printer driver becomes non functional due to the registry for that driver being modified. All users on an affected client are unable to print to a queue that uses that driver. The problem is per-machine rather than per-user. Printers either produce no output, or garbaled characters on many sheets of paper.

Where the workaround listed below is enacted, there are no known re-occurences of this issue have been observed in our environment (at the time of writing).

Environment: 
 Server - Windows 2008 R2 Enterprise, SP1 + Updates, Dedicated Print Server
 Affected PRinter Driver - HP Universal Printer Driver PCL6 (v5.4)
 Client PCs - Windows 7 x64 Enterprise Edition SP1 + Updates
   
Troubleshooting undertaken:

Viewing the properties of the printer driver shows that dependant files, printer monitor and help file information is missing. Auditing has been enabled on a specific registry key to locate the process that has modified the associated registry values. No readily identifiable commonalities between machines have been identified as yet.

Workarounds known:

Removal of the printer driver and package from an affected client, followed by a reinstall from the server resolves the problem. In some cases, the driver continues to be listed as in use.  In these instances delting the registry key "SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.4)" and restarting the spooler allows for the driver to be downloaded from the print server again.

Does anyone have any thoughts on the source of this issue?  It does seem similar to http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/e2acb625-027d-47a9-b4a7-1616e270bcbc - though that has been marked as answered ande there is no solution to the issues we see in that thread.

Supporting Information:

Auditing of the HP printer driver registry key has revealed:
Windows Registry Audit Logs
========================= RECORD STARTS =========================
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          28/05/2012 15:28:39
Event ID:      4657
Task Category: Registry
Level:         Information
Keywords:      Audit Success

Description:
A registry value was modified.
 
Subject:
                Security ID:                         SYSTEM
               
              
                Logon ID:                             0x3e7
 
Object:
                Object Name:                    \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.4)
                Object Value Name:       Monitor
                Handle ID:                           0x634
                Operation Type:                               Existing registry value modified
 
Process Information:
                Process ID:                          0x56c
                Process Name:                  C:\Windows\System32\spoolsv.exe
 
Change Information:
                Old Value Type:                                REG_SZ
                Old Value:                           HPPMOPJL
                New Value Type:                             REG_SZ
                New Value:                       
 
========================== RECORD ENDS ==========================

========================= RECORD STARTS =========================
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          28/05/2012 15:28:39
Event ID:      4657
Task Category: Registry
Level:         Information
Keywords:      Audit Success

Description:
A registry value was modified.

Subject:
                Security ID:                         SYSTEM
               
              
                Logon ID:                             0x3e7

Object:
                Object Name:                    \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.4)
                Object Value Name:       Help File
                Handle ID:                           0x634
                Operation Type:                               Existing registry value modified
 
Process Information:
                Process ID:                          0x56c
                Process Name:                  C:\Windows\System32\spoolsv.exe
 
Change Information:
                Old Value Type:                                REG_SZ
                Old Value:                           unidrv.hlp
                New Value Type:                             REG_SZ
                New Value:                       
 
========================== RECORD ENDS ==========================

========================= RECORD STARTS =========================
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          28/05/2012 15:28:39
Event ID:      4657
Task Category: Registry
Level:         Information
Keywords:      Audit Success
Description:
A registry value was modified.
 
Subject:
                Security ID:                         SYSTEM
               
              
                Logon ID:                             0x3e7
 
Object:
                Object Name:                    \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.4)
                Object Value Name:       Dependent Files
                Handle ID:                           0x634
                Operation Type:                               Existing registry value modified
 
Process Information:
                Process ID:                          0x56c
                Process Name:                  C:\Windows\System32\spoolsv.exe
 
Change Information:
                Old Value Type:                                REG_MULTI_SZ (New lines are replaced with *. A * is replaced with **)
                Old Value:                           hpcui118.dll*hpcpe118.dll*hpcdmc64.dll*hpbcfgre.dll*hpcpu118.cfg*hpc6r118.dll*hpcsm118.gpd*hpc6m118.gpd*hpcst118.dll*hpcur118.dll*hpcpn118.dll*hpcu1186.hpx*hpcsc118.dtd*hpcev118.dll*hpchl118.cab*hpcu118.dem*hpmux118.dll*hpmur118.dll*hpmpm081.dll*hpmpw081.dll*hpmsn118.dll*hpmsl118.dll*hpcsat20.dll*hpcu118u.ini*hpcu1186.xml*hpcls118.dll*hpcss118.dll*pjl.gpd*pclxl.gpd*stdnames.gpd*FxCompChannel_x64.dll*cioum.dll*cioum64.msi*hpcpn118.dll*hpcpp118.dll*pclxl.DLL*unires.dll*unidrvui.dll*stddtype.gdl*stdschem.gdl*stdschmx.gdl*hpcc6118.dll*HPDRVJCT.dll*hppdcompio.dll*hpbuio64.dll*hpfxcomw.dll*hpfie118.dll*hpsysobj.dll*HPSecurePrint64.dll*hpspw118.dll
                New Value Type:                             REG_MULTI_SZ (New lines are replaced with *. A * is replaced with **)
                New Value:                       
 
========================== RECORD ENDS ==========================

========================= RECORD STARTS =========================
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          28/05/2012 15:28:39
Event ID:      4663
Task Category: Registry
Level:         Information
Keywords:      Audit Success

Description:
An attempt was made to access an object.

Subject:
                Security ID:                         SYSTEM
               
              
                Logon ID:                             0x3e7
 
Object:
                Object Server:   Security
                Object Type:      Key
                Object Name:    \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.4)
                Handle ID:           0x634

Process Information:
                Process ID:          0x56c
                Process Name:  C:\Windows\System32\spoolsv.exe
 
Access Request Information:
                Accesses:            Set key value
                                                               
                Access Mask:     0x2
 
========================== RECORD ENDS ==========================

Print Spooler Admin Logs
======================= RECORD STARTS =========================
Log Name:      Microsoft-Windows-PrintService/Admin

Source:        Microsoft-Windows-PrintService

Date:          28/05/2012 15:28:50

Event ID:      372

Task Category: Printing a document

Level:         Error

Keywords:      Classic Spooler Event,Document Print Job

Description:

The document <FILENAME>, owned by <USERNAME>, failed to print on printer {01B96CA1-1C5A-497B-A667-28239E442049}. Try to print the document again, or restart the print spooler.

Data type: NT EMF 1.008. Size of the spool file in bytes: 434804. Number of bytes printed: 0. Total number of pages in the document: 2. Number of pages printed: 0. Client computer:\\<MACHINENAME>. Win32 error code returned by the print processor: 5. Access is denied.

========================== RECORD ENDS ==========================

Good Afternoon,

I am trying - and failing - to install x64 drivers onto a x32 Server 2008 print server. After reading other posts, I think that I know the problem. My x64 driver does not have the same name as the x32 driver. Specifically the x32 is called: HP LaserJet 4250 PCL 6, while the x64 is called: HP LaserJet 4250 PCL6 (there's no space between "PCL" and "6"). From what I've read, they need to have the exact same name (please correct me if I'm wrong).

So I know that you can change the name by accessing the vendor's inf file. The problem is, I can't locate the inf file for this driver. It's not in %windir%\inf, nor is it in c:\windows\system32\spool\drivers\x63\3 where the primary driver files are located.

Any help or ideas would be greatly appreciated!

I'm noticing in my Remote Desktop Session Host 2008 R2 servers that files being queued for printing are sometimes labeled " [Compatibility Mode] ."

What does that mean?

The print queue is pointed to a Xerox Phaser 5500 who's queue is on a Windows Server 2008 R2 print server.

I have deployed network printers using Print Management.  If I log onto a users PC as an admin I can see the printers, however if I log back in as a user I can not.  So I know that the PC is getting the printers, I just can't figure out how to get the user to see them.  Users are not local Admins on their PC's.  The PC's in question are Windows 7.  The server is Win Server 2008 R2.  

My GPO has Add Printer Wizard - Network Scan Page (Managed Network) as Enabled.  I also have Point and Print Restrictions set to Enabled, with Users Can Only Point and Print to These Servers:  "our print server".  Do Not Show Warning Or Elevation Prompt is set for installing drivers for a new connection, and updating drivers for an existing connection.  

I feel that I have missed something on the local PC, if the regular user can't see the printers but a logged in admin can.  

Thanks!

Here's my situation.

I used to have 2 nodes cluster in a windows 2008 environment. We configured DHCP and Print services as part of the clustered services. Then later we moved to VMWare and we virtualized 1 of the 2 servers leaving on the new environment a 1 node cluster. We didn't see a reason to virtualize both nodes. Now I want to stop the failover service but my question is if the 2 services will continue to work (The DHCP and Print services) or I will need to migrate those 2 services to another server.

I hope my qestion is not so confusing.

Dear all,

It’s already a couple of days since I ‘m trying to resolve the following problem. We have a Windows 2008 R2 application server with RDS installed. Remote clients connect to the server to run an application. They use printer redirection to print out of the application. This works fine for a number of them but one. This particular client runs a 32 bit Windows XP workstation to connect and has a HP LaserJet 4050 attached locally. The printer is not being redirected and the Event 1111 is logged on the RDS server stating “Driver HP LaserJet 4050 Series PCL required for printer HP LaserJet 4050 Series PCL is unknown. Contact the administrator to install the driver before you log in again.”.  

My search led me to MS KB 2004736. (http://support.microsoft.com/kb/2004736)

The proposed resolution states: “Install a printer on the local client that has a matching driver on the Server. If there is a matching driver on both the server and the client, this error will not be logged.”

Now is the question – How?

I have a 32 bit Windows XP Client and a Windows Server 2008 R2 server. How can I install matching driver? Do I think in a wrong direction? Do I understand this wrongly?

1. In the article relating to Windows Server 2008 you are recommended to      do the following steps:
       
        On the terminal server, clickStart,      click Run, typecontrol printers, and then click OK.
2. On the File menu, clickServer Properties.

Note: If theFile menu is not visible, right-click an empty area of the Printers dialog box, and then click Server Properties.

3. Click the Drivers tab.
4. Click Add, and then follow the instructions in the Add Printer      Driver Wizard to install the printer driver .inf file.

This option is not available in the R2 edition anymore, as far as I can see. How can I add a driver to my server when Printing Services role is not installed? Shall I installPrint Management additionally?

 Please help. Thank you.

I have a number of printers that are redirected when users log into the Win 2008 remote Server.

However, when they need  to go into Printer Properties, the options are greyed out.

I ave tired lots of things, such a login in as Domain Admin, and this does not resolvable the-problem.

On their machine they have permission to amend the settings - it is the redirecrted printer that is the issue.

It is using the correct printer driver on the remote server - identical to the local one. Iam  at a loss what to look at next!

After setting up my new print server i went ot install some pritners.  The server is server 2008 R2.  I use the print management tool and follow these steps

1.  Right click printers

2.  add new printer using any of the options listed so it doesn't matter what option i use.

3.  install a new driver and once again ti doesn't matter what option i choose.

4.  then i choose my driver and it doesn't matter if it is 32 or 64 bit.

5.  I then go through and fidn my driver and click next. 

6.  on the completing the network pritner installation wizard i get the following error

Unable to install printer.  Operation could not be completed.  (error 0x00006d9)

What am i doing wrong?  Thanks.  

We maintain dedicated print servers on our enterprise using a older platform (Win2k3, 32 bit).  The networked print queues are installed directly on the system drive under Printers and Faxes on the host server, and all queues can be viewed and connected to by direct UNC connection to the host server (ex:\\printserver). I back up the networked print queues to .cab files using PrintMig.

My question (and it's probably has really simple answer that I'm just missing)...

Where are the print queues stored on the system drive? They are not on the admin share (\\printserver\C$) so I figure they must be contained in a sub folder or directory, but I'm having difficulty pinpointing the location. My guess is that the print queues are stored somewhere under the Windows directory or the Windows\System32 directory. PrintMig is drawing the backup data from a local source,  but I can't seem to find the relevant folder. Does anyone know the filepath?

Thank you TechNet community!

Hi,

I have a Workgroup of Server 2008 R2 and W7 Pro/Ent (the current option that we need to use) that I wish to allow anonymous printing to specific printers for guest access (W7 & XP). My Workgroup clients can connect fine as their local logons also exist on the server with the same passwords.

If i enter the URL on a guest machine to the path of the printer shared on the server i get 'logon failure: the user has not been granted the requested logon type at this computer'

I have added the Anonymous Group to the printer that is shared but the error persists.

Any advice would be appreciated.

Cheers

DS

hi all,

I have added a printer to my server, the driver is configured for single sided printing.

BUT when I connect to this printer from a client on the network and I look at the configuration I can see that it is set to print double sided. How is this possible? The driver on the server is set to single sided.

when I initially configured the printer on the server I configured it with double sided but I changed it to single sided. Why wont the client take the settings of the printer on the server? I have about 50 people wanting to use it so I cant go round them all and manually change it.

does windows 7 have a cache of previously used printers?

thanks