F
FirstClassCleaners
Due to several factors, some of our systems must print to shared printers via a local port pointing at the network shared printer. After a machine that is hosting a shared printer installs Feature Update to Windows 10. Version 2004 - this no longer works.
Previously after a major update (one that replaces the windows folder), I'd have to set some permissions on the spooler folder, and turn off password protected sharing. But after this update, the machine with the printer share is unable to print when the job comes via the above method. Works fine if printed as a traditional shared printer.
What does happen is the receiving spooler gets the print job but does not print. The sending spooler shows an error on the print job, but then retries the print job over and over and then a never-ending quantity of duplicate print jobs are created on the receiving print spooler and the sending spooler queue shows just the one job.
I turned off bi-directional support on both systems. no effect.
Both systems have the same OS build (19041.685) and experience pack (120.2212.551.0)
The issue appears to be on the receiving machines as no matter what OS, whether updated or not, a print job is sent as a local port, the results on the receiving PC are identical. This occurs in the same way on every W10 machine that installs this update.
Additionally it will happen on any printer that is shared on an affected system regardless of make, model, or driver version.
Any ideas?
Continue reading...
Previously after a major update (one that replaces the windows folder), I'd have to set some permissions on the spooler folder, and turn off password protected sharing. But after this update, the machine with the printer share is unable to print when the job comes via the above method. Works fine if printed as a traditional shared printer.
What does happen is the receiving spooler gets the print job but does not print. The sending spooler shows an error on the print job, but then retries the print job over and over and then a never-ending quantity of duplicate print jobs are created on the receiving print spooler and the sending spooler queue shows just the one job.
I turned off bi-directional support on both systems. no effect.
Both systems have the same OS build (19041.685) and experience pack (120.2212.551.0)
The issue appears to be on the receiving machines as no matter what OS, whether updated or not, a print job is sent as a local port, the results on the receiving PC are identical. This occurs in the same way on every W10 machine that installs this update.
Additionally it will happen on any printer that is shared on an affected system regardless of make, model, or driver version.
Any ideas?
Continue reading...