We have a Windows Server 2012 print server which around 80 network printers on it.  Occasionally (for reasons unknown) a job will get stuck in a print queue, not normally a problem, but just recently this has started to stop any of the printers from printing until the stuck job is deleted.

When the stuck job causes everything to stop, submitted print jobs just have a status of "Printing".

Does anybody know why a stuck job in one queue in having an affect on all other print queues?

Hi

I have a Windows 2012 r2 server print server, with 60 shared printers across about 1200 machines running a mixture of Windows 7 (32 and 64bit) using a locked down mandatory profile

All printers are deployed via group policy.

Users are informing me that printers have not installed, even if they were working fine the day before. When I try to add the printers manually, I get the following message

‘Windows cannot connect to the printer. The specified port is unknown’

It seems to be completely random

I have seen suggestions it might be to do with the maximum number of open TCP connections.

Any ideas what this could be and how I can fix it.

Windows 2008 R2
Windows 7 Enterprise

Topology: Central network with about 50 users/computers and 5 servers. 25 remote sites, 2-4 users/computers per site (no servers at the sites). Each site also has one network printer.

Currently all sites have the same IP scheme (we use DirectAccess for file access so unique subnets are not required). All of the printers are the same model and have the same static IP. So no matter what site a roaming user goes to printing works with no confusion.

Some new technology is being implemented that will require us to make unique subnets (which is actually desirable for obvious reasons). At the same time we will be implementing site-to-site VPNs, so there will be full connectivity to AD/central site.

So, here in lies the problem. Our super simple printing solution, now will not work. Some users roam to a dozen sites or more, will they have to have that many printers? Then they have to make sure to print to the one that is online/ready? Is there a GPO setting to hide offline printers or something? I wouldn't care if there were 25 print queues as long as only available printers were displayed. I see that there is some location aware printing features of AD/W7, but I am concerned all the offline printers will confuse users.

Any ideas?

We have had this problem for a few months... we had server 2003 standard and were running 4 physical servers 1 domain controller, 1 SQL server and 2 terminal services servers for 60 RDP users thru VPN at remote locations. After having no success solving the printer issues and under multiple recommendations we purchased a new monster server and run the 4 as virtual servers all running server 2012 r2 standard, the physical server being used only as hyper-v host (per MS licensing)

We still have the same printer issue since deployment. I understand that server 2012 r2 offers some added power where printing is concerned so my question is how we can best utilize the print server role of server 2012 r2.

1. Run another virtual server for just the print server role... we have 10 locations and 18 printers.

2. Currently we have the printers installed on the Remote desktop session servers but do not have the print server role installed on any of the servers.

3. would the print server role add too much overhead on the domain controller if deployed on it.

Additional info: we have 192GB ram and 2-8core xeon physical processors offering 32 virtual processors. We also use solid state drives in a raid 10 config. Our 10 locations are busy retail locations and often print reports at the same times in am (opening) and pm (closing) as well as receipts throughout the day.

Finally and least popular with the owner is the high availability printing option that would require another high end physical server and an upgrade to all the workstations for windows 8.1 functionality.

Any help and advise would be appreciated. Thanks. ~Doc 

Doc

We have 3 servers set up as RDS Servers and all 3 are identical to each other Running Windows Server 2012 R2. Our DC is running 2008R2 which is also a print server. All employees are using only RDS to work. Nobody work on domain computers.

We have about 10 printers on print server and they are located in 3 different sites. These printers are mapped via group policy preferences of user configuration straight on RDS servers. Nobody can print from domain computers.

Issue 1

When user logs in for the first time, he/she can see every single printer under devices and printers, but when he/she try to print a word (or any) document and goes to file - print, he/she can see only printers that are mapped to their account via Group policy Preferences.

Issue 2

When user goes to file - print, he/she can see 2 printer with same name but one printer named as Printer1 on printservername and second printer is appearing as printer1 on printservername.doaminname.

Issue 3

Intermittently when user try to print it will throw an error message saying there is no printer installed. If user log off and log back on it will print fine. Sometime user may have to log off and log back on few times before it starts printing.

Can someone please suggest anything?

Title pretty much says it all. I have a print server that has an HP Color LaserJet 4600N printer installed on it, the driver is HP Color LaserJet 4600 PS Class, a type 4 driver I was offered from Windows Update several months back when I installed it. Today I want to move it to another Windows 2012R2 print server, so I tried to add it there, and upon checking Windows Update, I don't see any of the "Class" Type 4 drivers.  Looking through the Microsoft Update catalog confirms most are gone.

What's going on here?  Are HP type 4 drivers being abandoned and no longer offered?   

Hi friends,

Today I added a new driver to our print server which I have done many times before, only this time in adding the new driver, all other printers of the same manufacturer (Canon) stopped working, with the device on everyone's computer showing "Driver update needed".

The new driver was for an iDV-ADV C5250. The printers which stopped working are all C5051's. The driver was added but at this point, no other action was taken, the driver was not used for a printer (hardware hasn't arrived yet) so the very simple step of adding a new driver in preparation for a new printer causes a major issue.

To resolve it on the Windows Server 2008 R2 print server, I selected any one of the existing Canon printers and set the driver to the new driver I added. Of course this did NOT work however then setting the driver back to what it was originally did resolve the issue... kind of. ALL users were then required to delete and re-add the printer(s) on their computers. You can see this was not a popular fault.

Although I resolved it, I really want to understand why this occurred. Can anyone help? I really need to make sure this doesn't happen again. I thought maybe printer isolation might help but you can't set a driver to isolated until after it's added can you?

Thanks.

Hi All

I have got script which reads data from CSV file and create print queue using add-printer and Add-PrinterPort on 2012 R2 print server. however when it gets created all printers' status is offline.

any help would be appreciated.

Hello,

We have a Windows 2012 domain and we are currently deploying printers via Group Policy. We have one printer and have set up a mono and colour driver for the printer. The idea is that everyone can print to the mono printer and selected users can print to the colour printer. Both printers are deployed via the same User GPO. All standard stuff so far.

To stop unauthorised users printing to the colour printer, under the security settings the everyone group has been removed and replaced with the 'Colour Users' group with allow print selected.

The issue we are seeing is that the colour printer will not deploy to any users, even those in the Colour Users group. Event viewer states that permission is denied when applying the group policy. I have added the 'Domain Computers' to the colour printers ACL with Allow Print permissions and the printer will now deploy, but everyone is able to print to it.

Is anyone able to offer any advice on how to deploy a printer via group policy but is restricted to only certain users. Ideally we do not want to create a separate GPO object for just the Colour Printer and restrict that to Colour Users. We just aim to deploy all printers via one GPO and limit who can print via the printer security settings.

Thanks,

Mark

We have a Terminal Server running Windows Server 2012. There is shared usb printer connected to workstation on the same domain as the terminal server. As the administrator, i can add/connect to the that usb printer in the terminal server and print.  The problem is, when i log in as another user  on terminal server, that particular printer is not available/listed. even if i log in as another administrator account.

But when we add another printer (ie, a network printer via IP). It is available/visible to the other users/profiles in the terminal server.

The work around at the moment it for the other user to log in and add that shared usb printer themselves on their terminal server profile.

Is this the way its supposed to be? or can there be a way for this share usb printer be automatically visible to all users?

Thanks

Hi all,

i have an issue, and i'm not sure what i want is even possible.

We have a application running on a RD server from which users need to print. The problem is that the settings of the application only allow us to select 1 printer for everyone on the server (no per-user settings available).

So i thought: OK, we need to install printers per user under the same name.

User A has been assigned \\printserver\printerA by policy
User B has been assigned \\printserver\printerB by policy

No we need a script that renames the mapped printer on login from "\\printserver\printerA" to "printer" and vice versa for user B.

is this even possible?

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!

Hello, I have the task of migrating this server.

Right now we have a 2003R2STD SP2 (I believe is x86) and the idea is to install a 2008R2x64STD SP1.

All the users have either Windows XP SP3 or Windows 7x64.

I couldn't get the import to create all the printer queues on 2008R2 (Error 0x80070705. The printer driver is unknown) therefore I'm install each printer manually. When I add the printer on the Print Management MMC only the x64 drivers are being shown; why is this? does this mean that when I map a printer on XP the server will provide the info from the 64-bits driver? could I delete, then, the x86 drivers?

Currently we have HP and Brother printers, is it better to have all the specific drivers for both versions or can I use anUniversal Driver (for HP) / Generic Driver (for Brother)?

Although I have the exported file with all the drivers installed on the 2003 Print Server, can I backup individually the drivers that are being used? how can I identify them?

And to finish: this server will have two roles: Print Server and WSUS, will these roles conflict in any way? do you have any suggestions or things I should look for?

Thanks.

Somehow all my printers were erased from the server last night.

Today I've tried to set them up again (Dell 3115 network printers - set up using TCPIP port).

But when I try to print now, then I get this error:

"The document Print Document, owned by administrator, failed to print on printer TAA_Print_1. Try to print the document again, or restart the print spooler. 
Data type: RAW. Size of the spool file in bytes: 197242. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\SVFREJA. Win32 error code returned by the print processor: 5. Access is denied."

Where do I start?

Thanks.

I work in a Domain environment where we have hundreds of printers on about a Dozen Print Servers. Some are 2003 and others are 2008. The Server I'm working with is 2003. The client work stations are Windows 7. We have several printers not mapping to the designated clients. All installation of printers are controlled via scripts through GPO and based on what security group they belong in. 

As far as I can see the computers are in the proper AD security group. But as students and staff log into the desktops, none of the printers show up. And when I try to manually connect the printer by going to the UNC path \\XXX-XX\printer_name it gives me the "Windows cannot connect to printer"..... with a code of 0x00...2 (there are a bunch of zeros in there). 

Now we have other printers that are mapped and are available to everyone. Its just those that are connected via a security group. So if a machine is in Room 123 and in the 123 group, they should get a color printer and a B&W printer for that room. 

For some reason the color printer is not showing up, but the B&W is. Outside that group, other teachers can connect via their laptop, or other desktop. But All the computers that the students use, cannot map the printer. 

I've tried the registry fix to clear drivers, I've renamed the "3" folder and that didn't work. I've tried applying Hotfixes but the ones I was given stated that they were designed for my version of windows. Even though the fix was for Windows 7. 

I'm getting frustrated. Simple Printer 101 tricks aren't working. I think this is a level up higher and could be script or Domain related. Any thoughts?

Thanks,

James C. August II
A+, Net+ Certified

Hi!

We have updated a driver on our Windows 2008 printserver, the new driver are
causing issues on the clients and we need to rollback the driver to the old version.

The only way I have yet found to do this is by deleting the driver on the clients using the
"Remove driver package" option or else the client will go back using that new version although
the new version is removed from the printserver itself.

Is there any easier way to do this?

Hi.

Im sitting on a Windows Server 2003 R2 32-bit and i have a printer here with 32 and 64 bit drivers.

I want to remove the 64-bit driver form the printer, can't find any way to do that. Do not want to remove the printer and set it up all again.

Tried to connect the printer on a 64-bit server to add a new 64-bit driver but that didnt work.

Good day,

I am migrating my printers from a Windows 2003 R2 (32 bit) server to a Windows 2008 R2.

Almost all printers went well (was able to install both 32 and 64 bit drivers), except for the EPSON LQ-590.

I was able to install the 64 bit driver for the Epson but when I tried installing the 32 bit, it prompts me for the following driver file :

{5E437618-1C5B-40FD-932C-B629FEA04258}.

Both driver file names are exactly the same "EPSON LQ-590 ESC/P 2 Ver 2.0".

The 32 bit driver was taken from a Windows 7 computer.

Can anyone share some lights on how to get this done or what would be a workaround to implement?

Thank you.