cancel
Showing results for 
Search instead for 
Did you mean: 
2 Replies

Re: Crazy Behavior with V4 PS Drivers on Server 2016 Queue - Secure Print, Crashes, Blank Pages

Hi,

Same kind of issues on my end using a pcl6 v4 or ps v4 with our altalink c8170 shared from a w2k12 print server.
We are deploying with GPO multiple different Xerox copiers using the V4 drivers and using pdqdeploy to deploy Xerox Desktop Print Experience onto our workstations. So far its almost running perfectly. Lately im am running in all kinds of trouble with the Altalink c8170.
Just like you the properties of that colier becomes unresponsive on some windows 10 21h2 and 22h2 and we are unable to print while others can. If i uninstall the copier and try to reinstall it i am getting some errors about the driver pcl6 v4 cannot be found on the server …. Unable to reinstall the copier. If I log the user who has problems on their actual
Laptop somewhere else, the gpo deploy and the copier is accessible again. After troubleshooting this for days, the only work around is the re image the user’s laptop….. or use a V3 driver… im still working on finding a solution:-/
0 Kudos
Joe Arseneau
Valued Advisor
Valued Advisor

Re: Crazy Behavior with V4 PS Drivers on Server 2016 Queue - Secure Print, Crashes, Blank Pages

Remove the Xerox Print Experience (Comes from MS store) and try the Desktop Print Experience (comes from Xerox direct)

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe Arseneau
0 Kudos
jvanabra
New Member
New Member

Crazy Behavior with V4 PS Drivers on Server 2016 Queue - Secure Print, Crashes, Blank Pages

Product Name: AltaLink C8030 / C8035 / C8045 / C8055 / C8070 Color Multifunction Printer
Operating System: Windows 10 x64

We have seven C8070s that are about nine months old. All seven are shared from a Windows server to Windows 10 1803 clients. About a month ago, I migrated all seven queues from Server 2008R2 using the V3 GPD to Server 2016 using V4 model-specific PS drivers. All clients have the "Xerox Print Experience" installed. Concurrently with moving the queues, I began observing the following behaviors:

1. When select Print Properties from various applications, but ESPECIALLY from Nuance Power PDF v2 and v3, the "Xerox Print Experience" dialog hangs and never loads. Windows logs an appcrash every time this happens. Sometimes rebooting helps, sometimes removing and reinstalling the printer helps, sometimes nothing helps.

2. All printers are using Secure Print, "enforced" via Printing Defaults on the server. Clients have a VERY difficult time getting PINs to "stick" on the local machine. Some computers have no problems, but numerous clients find their PINs resetting to some unknown number at random intervals. Checking the registry key at HKEY_CURRENT_USER\Software\Classes\Local Settings\Printers\PropertyBags\Manufacturers\Xerox\DefaultSecurePrintPasswordMin4Max10 I can observe the PIN changing. At first I thought perhaps the GPO set to "update" was causing the problem with GPO refreshes, but after changing it to "create" (which should only run once) I see no improvement.

3. Sometimes Secure Print jobs come out blank. Changing the job type to "Normal" results in a normal print.

4. Two machines in particular have become incredibly unstable - the diplay on the machine becomes unresponsive, or it stops releasing Secure Print jobs, or you can't log into it. Rebooting or power cycling the device tends to bring it back for a period of time - minutes or hours - but these two affected machines are permanently unstable.

This can't all be coincidence. These machines worked "perfectly" (they've always been a bit iffy, especially vs. the WorkCentres they replaced) for months - it's only since switching drivers we've had all of these problems. We are running three different firmwares now (an older one, the last general release, and a SPAR release) to see if that helps, but it doesn't. The only thing I can specifically observe that seems off is that the server hosting the queues shows the driver is specifically "Xerox AltaLink C8070 V4 PS" but every single client shows the driver is "Xerox AltaLink C8030 V4 PS." Although *most* of the driver componets are similar, a couple GPD files are model-specific, and are wrong. I'm not sure if referencing the wrong GPD could cause this, but I thought I'd throw it out there. I cannot find any way to enforce clients choosing the right GPD.

I'm at my wits end, our vendor (a Xerox corporate branch) has been unable to cure these issues. We're a print-heavy business (hence seven 70ppm MFPs) and need this to work. Does anyone have any ideas?

0 Kudos