1. It is seemed that we can use
rundll32 printui.dll,PrintUIEntry /ge /c\\MyPcName
to display all printers of my computer on the console. But I don't know how to do. Could you help me?
2. I don't know what is the "/ge" mean. Whatever printers I have installed, such as local, and shared, and a printer from other computer's sharing, I can't see any priner in the window.
At machine A, there is only one printer named "Deli 888-D".I store the printers by
Printbrm -B -F D:\888d.printerExport -NOBIN -NOACL
At machine B, I install the driver of the printer name "Deli 888-D".
As the administrator, I want to restore the printer with
Printbrm -R -F XYZ\888d.printerExport
But it told me some error
Operation mode: restore Target server: local machine Target file path: D:\888d.printerExport. Queue publish mode: none Overwrite mode: keep existing settings Queue ACL mode: restore ACLs from backup LISTING PRINT QUEUES 888D LISTING PRINTER DRIVERS Deli DL-888D, Windows x64, None Restoring Printer Drivers... Restored printer driver Deli DL-888D, Windows x64, 3 Restoring Printer Ports... Restoring Print Processors... ************ 50% ************ The following objects failed to install: LISTING PRINT QUEUES 888D Error: 0x80004005 Unspecified error Check the eventlog for detailed information about the error which occurred. The following error occurred: 0x80070005. Access is denied. Check if you are an administrator or member of the administrators group. Check if you executed the tool with elevated permission. Check the eventlog for detailed information about the error which occurred.
Here is something from eventvwr
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-PrintBRM" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" EventSourceName="PrintBrm" /> <EventID Qualifiers="49154">71</EventID> <Version>0</Version> <Level>2</Level> <Task>4</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-08-16T11:50:57.000000000Z" /> <EventRecordID>549</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>lida</Computer> <Security /> </System>
- <EventData><Data Name="param1">C:\Users\Test\AppData\Local\Temp\0DA25D74-7319-4F06-B8D8-5FFC645F3427\PRTPROCS\Windows x64\winprint.dll</Data> <Data Name="param2">C:\Windows\system32\spool\PRTPROCS\x64\winprint.dll</Data> <Data Name="param3">0x5. Access is denied.</Data> </EventData></Event>Indeed, there is no dir named
C:\Users\ADMINI~1\AppData\Local\Temp\0DA25D74...
perhaps it is the reason, I guested.
I can restore it at machine A. The machine A and B are the same os
6.1.7601
perhaps machine B is lack of some windows patch, I guested.
Could you teach me how to restore printer at machine B? Thank you very much!
Dear all,
I need your kindly help in order to create a report that contains the amount of print jobs per months per queue on a server that host 600 queues, for the moment I manage to setup printing logs on the event logs in order to get all jobs.
at this point this is what I have construct:
$Results = Get-WinEvent -FilterHashTable @{LogName="Microsoft-Windows-PrintService/Operational"; ID=307;} -ComputerName $Computer
FOr the moment I anly got to know how many jobs for the hold server, now I need to get the amount per queue.
Thanks in advance for your help
Greetings all,
We're doing a network migration at my small office and now have a problem with our file & print server. Whenever I send a job (such as test page) to our Win2012R2 print server, the job never actually prints at the print device. The print queue on the print server shows the job is "Printing", and then "Restarting", and continues to loop indefinitely. I am pretty sure the problem is with the print server, because I print directly to the device (in this case a Xerox C60) at the new IP address. Drivers are current for our Windows 10 workstations. We are using the "Type 4 User Mode" drivers on the print server. Troubleshooting steps taken so far are:
0. Verified the print server can ping / reach the print device.
1. Created a new port at the new IP address. Mapped the printer to the new port. Same problem.
2. Deleted the share, device, and port. Recreated the printer and port. Same problem, and identified an additional one: when I attempt to share the printer, I get an error msg which says, "Sharing is not supported for this type of printer". Printer does not appear in the list of shared folders or devices when I run a net view\\servername.
Everything worked perfectly before I changed the IP address of the printer.
Any suggestions?
Hey folks, I have 600 printers that I must network map which are located across 6 print spoolers within our organization. These printers need to be mapped to this single server allow an application to push print jobs. Unfortunately
I don't think Windows 2008 R2 was ever designed to have this many printers mapped via network simultaneously. Once it reaches about 350 - 500 printers I start to experience problems after I restart the spooler. Examples include, the spooler crashing or the
logs showing that printers are being deleted with no explanation, driver errors... etc. Originally the design never had the print management service, however I'm looking for other options and now that I have it installed, i noticed that I can add other print
servers.
We went ahead and tested to see if simply adding the server to the print management screen would work for us. I deleted all printers that I had mapped via network, restarted the machine, added the print servers and attempted
a test. The results I got back shows that the printer was added via network, job was pushed and then the printer was automatically deleted. It worked!
My question is, is this the intended design? Is it sustainable? When we upgrade to 2k12 servers, is this something I can consider.
Alternatively we are looking at the ability to just go head and install the printers locally as non-shared printers by migrating the 600 printers from the other print servers... basically creating one massive private print server that is exclusive to the applications use.
Also note that when i'm referring to logs above, i'm referring to Event Viewer PrintService Operational logs.
Hi,
I`ve just got new work-laptop with windows 10 and wanted to connect to shared printers in my job. I am trying to select printer by name but it doesn`t work. Instantly there is an error message: "Windows cannot connect to the printer" - error:""0x00000520". I am pretty sure that the name is correct as it worked well on my previous laptop with Windows 8. Any suggestions?
Best,
behappy04
Hello,
The SPOOLER service doesn't start.
I can't kill the SPOOLSV.exe service : access denied.
I have "start pending".
How to fix the issue.
ID : 7034
The Print Spooler service terminated unexpectedly. It has done this 6 time(s).
I also plan to restart the server.
Regards,
One of our customers, an elementary school, would like to allow certain (trusted) instructors to manage the print queues of Windows Server-managed laser printers. I have two questions about two different aspects of this:
1) Rights: Is making them members of the Print Operators group a sane choice, or is there a more "tailored" way to do this that's more appropriate?
2) Managing the queues: what tool(s) do I give them to actually allow them to manage the queues, without letting them on the server? Should I install the Print Management snap-in on each instructor's PC? Or just install the printers that are going to be managed on each instructor's PC, and have them use the same queue management utility that ships with Windows that they'd use to manage a locally-hosted printer?
I have just changed photocopiers from one manufacturer to another and deployed by gpo from print server but when i look at forms from client pc it is looking at local forms and not forms from the print server. How do i make client machines view forms from
print server. We have a lot of custom forms on the print server and can view them from print management on the server but cannot find a way to point clients to view from server instead of locally.
server 2012r2
clients windows 10
full domain
We are consolidating several application servers and consolidating into a single windows server 2012 R2 standard. We have 10 source servers each having 200+ printers installed on them.
We have been tasked to migrate all the printers from these 10 older servers (Windows server 2008 R2 and Windows Server 2012 R2) and install onto a single instance of Windows server 2012 R2.
We know how to migrate the printers, there is no problem and we have been doing that already. However, going forward we would like to understand MS recommendations as to how many printers can a server hold/manage. I can see, the server responding too slow when accessing Devices & Printers.
Any MS recommendations, limitations or documentation link may be helpful in understanding how we can optimize the server load and performance.
Thanks in advance.
Durga Pathak
Hi all,
I'm migrating from Server 2003 to a new server running 2008 R2. I've recreated all of my printers and shared them, and installed both 32-bit and 64-bit drivers. I'm able to install these printers on the client, and the users can print. However when i look at the properties of the installed printers on the client PC's none of the available profile's in the Profile's tab are there. It's completely blank. Also the Default Printer settings i specified on the server (one of which is a profile choice) are not being enforced, and another option of our Printers (Canon iRC2380i's) is that users print to mailboxes. None of these are available also to choose from, meaning the users are unable to print to their own mailbox.
If i install the drivers on my own client PC, where i have Admin rights on the PC, they install just fine, and all of the options are available. This is also true of my backup server, i can install the drivers on this just fine and get all of the options i require on the Printer Properties pages. But on ordinary users PCs they simply don't appear in the Printer Properties (users don't have Admin rights on PC's, but prior to using Server 2008 R2 i didn't have this problem).
I've even tried importing the printers from file from the old server to the new one, but this made no difference - the problem still remains.
Anyone any clue on this? Thanks all.
Hi All,
I have recently migrated my main file and print server from 2008R2 to 2012R2, I wasnt able to import/export my printers as I was experiencing the import hanging and crashing, so gave up on that and decided to set the printers up from scratch.
I only use 10 printers and of various different models of HP Laserjet network printers.
I decided to setup my first Laserjet 6040MFP so downloaded the most recent PCL6 driver from HP website for Server 2012R2 64bit..... when attempting to setup the printer and use this driver I would receive "the remote procedure call failed - unable to install printer"..... so I tried various other drivers such as PCL5 and old PCL6 but all experienced the same error or just hung and crashed the Print Manager.
I then tried to let "windows choose the best driver" which installed successfully with the type 4 "HP Color LaserJet CM6040 MFP PCL6 Class Driver".... but on all the client machines (mix of windows 7 and 10 32bit and 64bit) they were unable to print with this driver and got a generic "unable to print, start troubleshooter".
Any suggestion on how I should be setting my printers up or how to troubleshoot further? I have not been able to setup any printer successfully so far on the new 2012 server.
had this in event viewer when the manual pcl6 driver failed to install.
Faulting application name: PrintIsolationHost.exe, version: 6.3.9600.17415, time stamp: 0x54504ed1can I enable Microsoft-Windows-PrintService/Operational logging enabled by GPO for domain controller?
Jimmy Wang
I had my Printer driver checked by HP yesterday and Printer checks out. When I try to activate Printer Properties it will not open up so that I can change ink from normal to best or change type of paper in the printer options. I cannot open printer properties across programs. I think this occurred with one of the Windows 10 updates as I know this feature was working several months back. What do I do to correct this?
Thank you
We can't seem to get any sort of acceptable printer management working via Windows technologies. I've come here looking to see what we did wrong, what we can do or fix to get this working, before we start homebrewing a solution.
Our Setup:
We currently have over 10 remote desktop session host terminal servers, servicing over 100 staff. Printers are physically located around the office, typically 8 staff to a printer. Staff are not assigned terminal servers in a geographical manner, so printers
must be managed on a user-by-user basis, not by computer.
We have a single 2008r2 print server with 20 or so printers.
Everything's in a single Active Directory domain, Domain and Forest functional level "Windows Server 2012 R2".
What we have tried:
Custom Group Policy:
We tried making group policies for each printer, defining "User Configuration>Preferences>Control Panel Settings>Printers". Action=replace, default=yes. Assign users to the security filtering to have this printer configured for them on login to whatever terminal server they were assigned.
Problems:
Default printer would not always be set. Some programs would "lose" this printer, and we'd have to reconnect the printer for it to show in these programs again.These group policies would sometimes lock up the Group Policy Client Service, causing entire terminal servers to refuse logins until restarted.
Deploy with Group Policy:
We tried the standard "Deploy with Group Policy" context menu option direct from the print server Print Management pane.
Problems:
Printer would often be created as "Unspecified" device, and would be unusable. If printer was configured correctly, it would create a new, duplicate print spool after every login, which would not go away until the "Print Spooler" service was restarted. (You'd see several identical options under the "See what's printing, Set as default printer" context menu options for a single printer)
Neither of these deployment strategies are acceptable. So, what can I do to get working printer management working?