hello
I have Print Server 2012 on the same server as AD 2012
I want to keep all documents that is printed in all printers attachet to this print server.
I checked and in directory C:\Windows\System32\spool\PRINTERS files are not in readable format.
If someone wants to print for example pdf file i want to keep this pdf file in print server.
Is it possible?
best regards
jan
Hi,
I have successfully migrated all the printers to a new server(VM).
The only other issue i have is, keeping everyone's default printers and the printers they currently have in their "Devices & Printers". The names of the printers are staying the same.
I want to have these ports moved over to the new server and users never knew i migrated these printers.(Scenario: Migration is done, user's printers that have already been added before in "Devices & Printers" stay the same and is able
to print from the printer they already had in "Devices & Printers".)
I noticed that there is an option to export printer ports in Print Management GUI. Does this apply to also keeping the same printers in the users "Devices & Printers" or is this something else?
Also, Is there a way to transfer users printer in "Devices & Printers" that are NOT set to defaults? Basically transition existing printers in "Devices & Printers" to the same ones added but essentially in the "background",
they are different. The ports are pointing to the server, but i now need to point users printers back to the new printer.
How can i make this happen? It is not ideal for us to have users re-add all the printers in "Devices & Printers".
To add further to this...
We are now taking into consideration using GPO's for this instead of scripting this, as it seems to be more practical.
Do you know if and when we apply GPO's to re-map the printers ports to the users workstation, what stage is this GPO applied? Is this applied when the user restarts the computer? Is this a computer policy or a user policy to achieve this? Also, is this applied
before login or after login if it is a user GPO. If its computer, does this apply to users ONLY connected to the subnet once in the office, or will this work for users that are not in the office as well? Can this GPO be applied on VPN?
I appreciate you help.
Thank you,
Jonathan
We have a 2012 Print Server with 20+ printers shared for our domain. When we connect a Server or PC to a Ricoh shared on the Print Server (Accounting Ricoh C5502) - the printer name only shows up as "Ricoh Printer" in Devices & Printers on the client.
This is happening with several different Ricoh models, and different OS like Server 2012 and Windows 7. All other printers show up as the Share Name in Devices & Printers: "Accounting HP 3010 on PS01" and "Admin HP 3005 on PS01" for example.
Any ideas why the Ricoh's won't display the share name?
A client is no longer able to see outgoing faxes after upgrading to Windows 10 (their own or anyone else's.) This is creating issue as they are unable to tell when a fax is having trouble going through.
This was working correctly with Windows 7 and Windows 8, and Domain Users have full permissions. This is the only user who upgraded to Windows 10 and the only user experiencing issue.
Is there any known solution?
Client: Windows 10
Server: Windows 2003 R2 Standard
Mathew Neill
There were print cluster set up under windows 2008 r2 server and some print queue built there.
I found that some document get sucked on specified print queue, i try delete those document but got no luck.
After further check, i found the related files to that sucked document are located in "spool" folder. I try delete them but there were warning message stated that it were accessed by print spooler services.
I did not want to stopped the print spooler service to clear those sucked print job as all print queue on the print cluster server would got affected.
Therefore, i would like to know if there were any alternative way to clear those sucked print job without the print spooler service restarted/stopped on server side.
Thanks for any suggestion.
I can map printers on our company network fine with windows 7 clients, but some Windows 10 clients struggle to resolve the print server by name when trying to map printers. When using the IP address of the printer server it works fine. (i.e.'192.168.0.5\printername' works fine, yet 'PrintServerName\printername' does not work)
The clients can all ping the print server using its name, so its not a name resolution issue with DNS.
Has anyone else seen any issues with windows 10 clients mapping printers via the print servers name?
thanks,
Dan.
Hello, here in the past week or so I'm starting to see a trend where a few Windows 7 x64 clients are running into printing issues, getting this error in their PrintService event log:
"Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0xbc8, HRESULT 0x80070bc8. See the event user data for context information."
Event 215
Our setup is a Windows 2012 R2 print server with several type 3 and type 4 driver shared print queues using the "computer" directed "deploy with group policy" feature. Our current setup has been running smoothly for months. As you can imagine from the error the problem queues in question are the type 4 using the client side Microsoft enhanced Point and Print compatibility driver. The symptoms that the user sees are when they go to print to the printer they are presented with dialog boxes that indicate that the driver is not installed, such as, do you trust this printer or they are prompted to install a driver.
The only real issue I've had with our setup since it was first built was when I ran Windows updates on the print server back in July and I installed KB2962409 (June 2014 update rollup). Immediately after installing this update (other updates were installed as well but I suspected this one as causing the issue since this was the only update that was ran where printing was mentioned in the description) pretty much all v4 print driver users stated calling about having issue printing to v4 queues and they were being prompted to update their Microsoft enhanced Point and Print compatibility driver. Fortunately removing KB2962409 immediately resolved the issue.
Fast forward to a couple of weeks ago I ran Windows updates and installed KB2975719 & KB2984006 (Aug & Sept update rollup) among the other standard Windows updates. While no issues were noticed right away, we have had a small handful of computers show these symptoms since. Not sure if those updates are related at all, but wanted to throw that out there. Has anyone seen these issues before? Anyone know what's causing this? Or even know how to fix it once the client computer is in this state? I don't see anyway of repairing or reinstalling or updating the built in Microsoft enhanced Point and Print compatibility driver. The only fix I've found for this is reimaging the computer, which works perfect, but not the most ideal solution considering we don't know what's causing it, and if this issue will start to grow larger.
Thanks!
Hi,
We want to send FAX from a C# application using windows FAX API to a MFP (supporting FAX).
We have SHARP MX-5141N MFP connected in our client office network. This MFP supports faxing.
Our Application is able to send FAX to FAX server installed on the server PC (running Window server 2008).
But, we are having an issue in configuring the SHARP MX-5141N MFP as FAX device in the FAX server.
As SHARP MX-5141N MFP is not connected to server PC directly but connected through LAN, it is not showing up in Device pane of FAX server in Windows Server Manager console.
Is there a way we can configure MFPs in LAN to be a FAX device of a FAX server?
Regards
Balaji
We have a 2012 Print Server with 20+ printers shared for our domain. When we connect a Server or PC to a Ricoh shared on the Print Server (Accounting Ricoh C5502) - the printer name only shows up as "Ricoh Printer" in Devices & Printers on the client.
This is happening with several different Ricoh models, and different OS like Server 2012 and Windows 7. All other printers show up as the Share Name in Devices & Printers: "Accounting HP 3010 on PS01" and "Admin HP 3005 on PS01" for example.
Any ideas why the Ricoh's won't display the share name?
I've was trying to read print service logs and save them in a database to improve manager.
I've made a lot of tests and it looks there is some value missing in log EventID 805 or EventID307 or a wrong count.
To do the test I used document PDF with 2 pages.
1) print_3_pages_collate_unique.pdf
EventID 805
- <UserData>
- <RenderJobDiag xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<JobId>25</JobId>
<GdiJobSize>993496</GdiJobSize>
<ICMMethod>1</ICMMethod>
<Color>2</Color>
<XRes>600</XRes>
<YRes>600</YRes>
<Quality>600</Quality>
<Copies>1</Copies>
<TTOption>3</TTOption>
</RenderJobDiag>
</UserData>
EventID 307
- <UserData>
- <DocumentPrinted xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<Param1>25</Param1>
<Param2>print_3_pages_collate_unique.pdf</Param2>
<Param3>administrator</Param3>
<Param4>SERVER</Param4>
<Param5>PDFCreator</Param5>
<Param6>pdfcmon</Param6>
<Param7>694616</Param7>
<Param8>3</Param8>
</DocumentPrinted>
</UserData>
Copies: 1
PagesPrint: 3
Total: (1 x 3) = 3 (OK)
2) print_3_pages_not_collate_unique.pdf
EventID 805
<UserData>
- <RenderJobDiag xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<JobId>26</JobId>
<GdiJobSize>874020</GdiJobSize>
<ICMMethod>1</ICMMethod>
<Color>2</Color>
<XRes>600</XRes>
<YRes>600</YRes>
<Quality>600</Quality>
<Copies>1</Copies>
<TTOption>3</TTOption>
</RenderJobDiag>
</UserData>
EventID 307
- <UserData>
- <DocumentPrinted xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<Param1>26</Param1>
<Param2>print_3_pages_not_collate_unique.pdf</Param2>
<Param3>administrator</Param3>
<Param4>SERVER</Param4>
<Param5>PDFCreator</Param5>
<Param6>pdfcmon</Param6>
<Param7>601176</Param7>
<Param8>3</Param8>
</DocumentPrinted>
</UserData>
Copies: 1
PagesPrint: 3
Total: (1 x 3) = 3 (OK)
3) print_3_pages_collate_2_copies.pdf
EventID 805
- <UserData>
- <RenderJobDiag xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<JobId>27</JobId>
<GdiJobSize>874020</GdiJobSize>
<ICMMethod>1</ICMMethod>
<Color>2</Color>
<XRes>600</XRes>
<YRes>600</YRes>
<Quality>600</Quality>
<Copies>2</Copies>
<TTOption>3</TTOption>
</RenderJobDiag>
</UserData>
EventID 307
- <UserData>
- <DocumentPrinted xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<Param1>27</Param1>
<Param2>print_3_pages_collate_2_copies.pdf</Param2>
<Param3>administrator</Param3>
<Param4>SERVER</Param4>
<Param5>PDFCreator</Param5>
<Param6>pdfcmon</Param6>
<Param7>874020</Param7>
<Param8>6</Param8>
</DocumentPrinted>
</UserData>
Copies: 2
PagesPrint: 6 (The value correct must be 3 and not 6 or should have a parameter in log to identify if the pages were printed collated or not)
Total: (2 x 6) = 12 (Not OK) (value correct should be: 2 x 3 = 6)
4) print_3_pages_not_collate_2_copies.pdf
EventID 805
<UserData>
- <RenderJobDiag xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<JobId>29</JobId>
<GdiJobSize>874020</GdiJobSize>
<ICMMethod>1</ICMMethod>
<Color>2</Color>
<XRes>600</XRes>
<YRes>600</YRes>
<Quality>600</Quality>
<Copies>2</Copies>
<TTOption>3</TTOption>
</RenderJobDiag>
</UserData>
EventID 307
<UserData>
- <DocumentPrinted xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<Param1>29</Param1>
<Param2>print_3_pages_not_collate_2_copies.pdf</Param2>
<Param3>administrator</Param3>
<Param4>SERVER</Param4>
<Param5>PDFCreator</Param5>
<Param6>pdfcmon</Param6>
<Param7>601176</Param7>
<Param8>3</Param8>
</DocumentPrinted>
</UserData>
Copies: 2
PagesPrint: 3
Total: (2 x 3) = 6 (OK)
Anyone has the same problem?
Best Regards
Wanderlei
I am trying to isolate the cause of this error message on a terminal server running Server 2012. When it crashes there is about a 20% chance that it will freeze up the whole print queue and the printer spooler service has to be restarted to allow it to continue.
If I am reading this error message correctly it says that a printer drive is faulting, and KMUU6MR1.DLL is a Kyocera printer driver. I have since updated all Kyocera printers to the latest version but it is still faulting.
Any ideas?
Faulting application name: PrintIsolationHost.exe, version: 6.2.9200.16384, time stamp: 0x50109d59
Faulting module name: KMUU6MR1.DLL, version: 6.1.8.26, time stamp: 0x521ba6ee
Exception code: 0xc0000005
Fault offset: 0x0000000000168d2f
Faulting process id: 0x7a90
Faulting application start time: 0x01d1b2374f38a7f7
Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\KMUU6MR1.DLL
Report Id: 8d416fed-1e2a-11e6-98d4-000c29e3df68
Faulting package full name:
Faulting package-relative application ID:
Hi,
We are using Streamserve with print management solution. the issue is that print management is seeing the printed jobs are done by services account. I went through many article and I found that print management can identify the user by usingWin32_PrintJob - Owner. but I don't know how to implement it. please help!
Please note that we are running Windows 2012 r2 in both servers.
Hi everyone,
One of my customers is running Windows Server 2008 R2 on a machine and he's trying to hook up a multi-function printer (Brother DCP7055) to it.
By way of forcing the drivers, I can get the driver for the printer to work but the scanner part is never recognized.
I was thinking of creating a VM running an OS that will actually support the scanner and forwarding the USB port over to that one so I can install the driver. Any ideas on this? I remember having done this with VMWare player a long time ago by editing the usb file and putting in the USB device details in there, but to be honest it's been so long I don't even remember how to.
Thanks,
Daniel
Hi,
I have a Windows 2008 R2 (RDS enabled) Server where installed a application client and a fax server client (as a printer for printer fax services).
The application have ability to identify which copy should prints to printer and which copy to fax printer.
However, when a Windows 7 pro remote client connected to server via RDP, it is unable to drop fax to fax server printer by server application if fax printer is not set default printer.
Please help.
Dicky
Branch Office Direct printing sounds great but I have a question I couldn't find the answer to despite reading and searching a lot on the net.
If a printer in print management is enabled for Branch Office Direct (and the various pre-requisites that could cause fall back server side rendering are not triggered), does every single job sent from ANY client end up printing directly or only those deemed somehow to be 'in a Back Office'? For BrachCache there is a latency parameter that determines if the content should be cached. Is there some trigger that says clients should print directly or will even local to the print server clients end up going direct if Branch Office Direct is enabled?
Thanks,
Chris Ransdell
I have attempted to use the package installer, I have attempted to add the drivers manually via the print store add driver function, both result in an error message stating:
unable to install FX DocuPrint C3055DX PCL6, Type 3 usermode, x64 driver
a problem was encountered while attempting to add the driver to the store.
There was a notification that the driver is unsigned, however this should not be an
At the bottom of the event properties it states teh OpCode is spooler operation failed.
I am logged in as a domain admin and have full access to the server
Any assistance would be appreciated as I have not been able to find any workaround, and the vendor has not been of assistance.
Hello, here in the past week or so I'm starting to see a trend where a few Windows 7 x64 clients are running into printing issues, getting this error in their PrintService event log:
"Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0xbc8, HRESULT 0x80070bc8. See the event user data for context information."
Event 215
Our setup is a Windows 2012 R2 print server with several type 3 and type 4 driver shared print queues using the "computer" directed "deploy with group policy" feature. Our current setup has been running smoothly for months. As you can imagine from the error the problem queues in question are the type 4 using the client side Microsoft enhanced Point and Print compatibility driver. The symptoms that the user sees are when they go to print to the printer they are presented with dialog boxes that indicate that the driver is not installed, such as, do you trust this printer or they are prompted to install a driver.
The only real issue I've had with our setup since it was first built was when I ran Windows updates on the print server back in July and I installed KB2962409 (June 2014 update rollup). Immediately after installing this update (other updates were installed as well but I suspected this one as causing the issue since this was the only update that was ran where printing was mentioned in the description) pretty much all v4 print driver users stated calling about having issue printing to v4 queues and they were being prompted to update their Microsoft enhanced Point and Print compatibility driver. Fortunately removing KB2962409 immediately resolved the issue.
Fast forward to a couple of weeks ago I ran Windows updates and installed KB2975719 & KB2984006 (Aug & Sept update rollup) among the other standard Windows updates. While no issues were noticed right away, we have had a small handful of computers show these symptoms since. Not sure if those updates are related at all, but wanted to throw that out there. Has anyone seen these issues before? Anyone know what's causing this? Or even know how to fix it once the client computer is in this state? I don't see anyway of repairing or reinstalling or updating the built in Microsoft enhanced Point and Print compatibility driver. The only fix I've found for this is reimaging the computer, which works perfect, but not the most ideal solution considering we don't know what's causing it, and if this issue will start to grow larger.
Thanks!
Hi,
We want to send FAX from a C# application using windows FAX API to a MFP (supporting FAX).
We have SHARP MX-5141N MFP connected in our client office network. This MFP supports faxing.
Our Application is able to send FAX to FAX server installed on the server PC (running Window server 2008).
But, we are having an issue in configuring the SHARP MX-5141N MFP as FAX device in the FAX server.
As SHARP MX-5141N MFP is not connected to server PC directly but connected through LAN, it is not showing up in Device pane of FAX server in Windows Server Manager console.
Is there a way we can configure MFPs in LAN to be a FAX device of a FAX server?
Regards
Balaji