So is that all ?
- Hey Xerox, I have an issue with your printers, can you help ?
- Sure! Have you checked your driver?
- Yes, it's definitely not the driver, I need further help.
- Huh, I guess you should ask somewhere else. 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!
Not the driver, not your problem ?
Since then, we weren't pretty satisfied by Xerox, but the more we try, the worst it gets.
As I stated, We are working on a server environement, I didn't even talk about windows 10...
The fact they share a common backbone, Sorry for giving you an idea of what may be a starting point to troubleshoot.
I downloaded the latest PS driver for windows server like a month or two ago. How can it be the driver ?
My apologies, if you have already figured out the driver itself can't be the issue, I guess Xerox plays no part in your scenario, I had assumed the driver might be the problem since you posted to Xerox.
As I stated, We are working on a server environement, I didn't even talk about windows 10...
I downloaded the latest PS driver for windows server like a month or two ago. How can it be the driver ?
I would start by updating the driver server side.
But there have been issues with unpatched Windows 10 and print drivers for quite a while.
So we have several Workcenters (3655X, 6655, 7830) in our offices. All are installed on a print server with predefined options and preferences for each.
The printers are mapped to our users sessions through GPO.
From time to time, on random user sessions, the printer fail to load the page layout it is supposed to print. Leaving the page layout options blank with no way to put them back.
The user then can't print anything.
Only fix I got working for now is to uninstall the printer and remap it back. But that is not suitable or maintainable as we are working with around 100 users.
The driver in use is the GPD PS V3.8.496.7.0, print server is a Windows server 2012 R2 and the users are working through RDP on Windows server 2012 R2 or Widnows server 2016.
What can possibly cause this ? How to solve it ?