Heisenberg Posted March 8, 2016 Posted March 8, 2016 I'm puzzled here. Having an issue with printing in Win10 x64... but only at the initial login, logins after that work fine. We have one of two main printers that is added by GPO, never had a problem with it before, and only recently noticed prints seem to spool on the local machine and just never come out the printer. Logging out of the machine and then back in fixes the issue... Bit of a PITA as it should work straight off the bat on the initial login (when profile is created) Can't be a driver issue otherwise it wouldn't work at all.. bit of a strange one that's for sure! So... Where do I start!?
Michael Posted March 8, 2016 Posted March 8, 2016 You'd be surprised, it could still be a driver issue. I presume you've checked the manufacturer's website?
Heisenberg Posted March 9, 2016 Author Posted March 9, 2016 You'd be surprised, it could still be a driver issue. I presume you've checked the manufacturer's website? Tried the latest print driver from Xerox and still the same issue. Found out it's not the initial login, it's simply the first job sent to the queue from that newly created profile. Clearing the job from the print queue and printing again works, then continues to work without issue, as long as people use the same machine it isn't a problem - but that's not always the case because we have a few hotdesks... PITA to troubleshoot!
sted Posted March 9, 2016 Posted March 9, 2016 what happens if you add it via script or deploy printers rather than gpp?
Michael Posted March 9, 2016 Posted March 9, 2016 Another possibility is your printer itself may need a firmware update, as Windows 10 renders print jobs differently to Windows 7 for example. In some situations, without the firmware updated, jobs can get stuck in the spooler and/or not print at all. A good example of this was the RISO 7150.
Heisenberg Posted March 9, 2016 Author Posted March 9, 2016 Another possibility is your printer itself may need a firmware update, as Windows 10 renders print jobs differently to Windows 7 for example. In some situations, without the firmware updated, jobs can get stuck in the spooler and/or not print at all. A good example of this was the RISO 7150. I updated the printers firmware last week to the latest version - This was to fix an issue with network scanning and has not fixed / affected the printing issue
Heisenberg Posted March 10, 2016 Author Posted March 10, 2016 Another possibility is your printer itself may need a firmware update, as Windows 10 renders print jobs differently to Windows 7 for example. In some situations, without the firmware updated, jobs can get stuck in the spooler and/or not print at all. A good example of this was the RISO 7150. As an update to this thread I've noticed the printers are actually added but come up as "device setup in progress" and that's why people couldn't print immediately, this normally takes 5-10 mins to setup x3 printers - Why does Win10 have to do this for every profile? I would assume the drivers are already on the machine, so not sure what other setup is required?
Heisenberg Posted March 15, 2016 Author Posted March 15, 2016 We sorted this in the end... Win10 was looking for the correct icon to display the printer and it must have been blocked by our proxy so it was taking 10+mins then installing the printer anyway. We disabled the printer icons by policy and they install straight away now. How odd!
Pollewops Posted June 30, 2016 Posted June 30, 2016 We sorted this in the end... Win10 was looking for the correct icon to display the printer and it must have been blocked by our proxy so it was taking 10+mins then installing the printer anyway. We disabled the printer icons by policy and they install straight away now. How odd! Hi...could you explain which policy setting does solve your issue with the printer icons ?
matt_isda_bomb Posted September 20, 2016 Posted September 20, 2016 HI All, I too have hit this issue with Windows 10. Setting printer icons to be retrieved automatically through Group Policy - dave.harris.uno The link above describes a HKLM registry entry to disable the feature.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now