Sanity check: Print Server upgrade
-
Could be any number of reason. Normally you can install Windows 7 x64 drivers on a Server 2012R2 box though.
-
@Carnival-Boy said:
@Dashrender said:
Do you really want 20+ people calling you because the supplies are low when it pops up on their screen?
I'm not responsible for toner luckily. But in theory, the message should prompt them to order new toner from our stationary department. I don't think it does in practice, because I've heard them complain that they've run out and can't print, even though the printer has been telling them for 2 weeks that they're running low and need to order some more. So I believe the stationary department now keeps them in stock.
To help the stationary department, you could install the HP full drivers directly onto their machines so they get the notices. Hopefully they would then take this information and use it to make their lives better.
Like you, we keep an extra toner on hand for each printer, then order a replacement once we pull the one off the shelf.
-
Update:
I've setup a print server and installed two printers and pushed them out to myself via group policy. It's taken me 2 hours, from installing the VM to sending a print from my workstation. Not bad for a relative newbie on Server 2012R2, print serving and group policy.
However, I've hit a snag already
A Konica Minolta MFP seems fine, but an HP Laserjet P3011 has a couple of critical problems. Firstly, it takes about 6 seconds to connect to the printer, compared with the Konica which is pretty much instaneous. Secondly, when I change any of the properties (eg changing the paper size or the number of copies), it doesn't throw an error but it doesn't save my changes. So I change the number of copies to 2, hit print, and then only one copy is actually printed. This is using the universal print driver. This driver works fine when using the old print server.
On the plus side, it does still display a popup to say that the toner is low.
Any ideas? It was going so well
-
I'm not sure what you mean by it takes 6 seconds to connect? Are you saying it takes 6 seconds for the GPO to push the printer?
Or each time you try to print it takes 6 seconds before the printer starts to do anything?
-
I mean if I select the printer in Word (for example), it takes 6 seconds to connect to. Whilst it's connecting, it displays a message "connecting to printer..." as per screenshot:
-
@Carnival-Boy said:
I mean if I select the printer in Word (for example), it takes 6 seconds to connect to. Whilst it's connecting, it displays a message "connecting to printer..." as per screenshot:
Are you spooling on the local machine or on the print server?
-
I've chosen "render print jobs on client computers", if that's what you mean.
-
@Carnival-Boy said:
I've chosen "render print jobs on client computers", if that's what you mean.
Ok.
-
@Carnival-Boy said:
I mean if I select the printer in Word (for example), it takes 6 seconds to connect to. Whilst it's connecting, it displays a message "connecting to printer..." as per screenshot:
That's normal. It's connecting directly to the printer to get data about it's status, ink/toner levels. if there's a jam or something etc. All of ours do that. It doesn't stop you from printing before that just means it won't show "Ready" under it until it checks.
-
@Carnival-Boy when users used the old print server, did the users get low supplies messages?
-
@Dashrender said:
@Carnival-Boy when users used the old print server, did the users get low supplies messages?
Yes.
-
Interesting - seems like there has been a change, but I can't tell you what it is.
What happens if you hit the print button while it says connecting? Does the print job seem to have any delay in actually being printed?
-
@thecreativeone91 said:
That's normal. It's connecting directly to the printer to get data about it's status, ink/toner levels. if there's a jam or something etc. All of ours do that. It doesn't stop you from printing before that just means it won't show "Ready" under it until it checks.
It's not normal to take 6 seconds. As I mentioned, the other printer I setup on the new print server connects immediately (about half a second), and this HP printer connects in immediately on the old print server. I only mention it because I wonder if it is related to the other problem I'm having....
-
@Dashrender said:
Interesting - seems like there has been a change, but I can't tell you what it is.
What happens if you hit the print button while it says connecting? Does the print job seem to have any delay in actually being printed?
It's definitely slower. Maybe 3 seconds versus 1 second on the old print server.
-
@Carnival-Boy said:
@thecreativeone91 said:
That's normal. It's connecting directly to the printer to get data about it's status, ink/toner levels. if there's a jam or something etc. All of ours do that. It doesn't stop you from printing before that just means it won't show "Ready" under it until it checks.
It's not normal to take 6 seconds. As I mentioned, the other printer I setup on the new print server connects immediately (about half a second), and this HP printer connects in immediately on the old print server. I only mention it because I wonder if it is related to the other problem I'm having....
It is normal when you have the computer spooling locally and directly sending to the printer. Each computer has to pull that information from the printer individually and adds to the time, rather than just the server pulling the the information.
-
Just to clarify, I have the same printer set up on two print servers. Both use the same universal print driver (version 6.0.0.18849). Both render jobs on the client. They appear identical. However, the new server takes 6 seconds to connect to and 3 seconds to print, whilst the old server takes 0.5 seconds to connect to and 1 second to print.
-
Are both servers on the same VM host? If not, are they on same physical switch? Same IP range i.e. subnet?
-
@Dashrender said:
Are both servers on the same VM host? If not, are they on same physical switch? Same IP range i.e. subnet?
Same IP range. Probably different switch. Different host.
-
It would be interesting to see what happens when you install the driver and print direct from a VM on the VM host that's having a problem.
-
It's super fast.
Here's another odd thing. If I print from the client using Excel, it does save my preferences. It's only if I print from Word that it doesn't work. Why would Word and Excel behave differently? Both are still slow, but this might be a red-herring. Some of my preferences are being saved (the copy count for example, even though I said earlier that it wasn't - my mistake), but the Job Storage tick box isn't being saved. Maybe it is just that one setting, I'll need to check.
