I just hung up on support as they are useless to try and discuss an known issue with. The staff member argued with me instead of listening to the ticket details. I don't understand how they can charge so much and do so little investigation. To add to this rant before I even get to documenting the issue (since they can't be bothered to on the phone) - I joined the forum today. Tried to set a complex password and guess what? The site can't handle special characters in the password. Is it 2005?
Server 2012 R2 running as DC with the global print driver of two variants:
Selected preferences and printing defaults on the share: BW conversion, disable job ID, double sided.
Clients machines running windows 10 1511 and previous connect to the shared printer, download and install the driver shared by the server and inherit the desired settings from the device.
Client machines on 1607 and subsequent updates wipe out the inherited settings, going to the driver default not set by the server (not converting to BW, enabling job ID and printing single sided).
I was told by the rep on the phone a few things:
1) that he hears of this issue a lot lately
2) that they have no intention of fixing it 'as it's a client configuration issue'
3) They think it's a firewall issue (really...?)
4) There is no expected ETR
5) To update the driver (which I had already done and tested before I called)
6) To set the client machines settings by hand at each worstation.
I'm sure like many of you that setting that by hand is unreasonable task in a corporate environment. This issue needs to be diagnosed as either windows side or Xerox driver issue and rectified with one or both parties. If there is another thread that I can pile on, please link me.
Solved! Go to Solution.
It's a known issue.
It's a Microsoft issue and Microsoft is working at fixing it. Xerox is working with them
Xerox has sparred it. CQGbl01004099 is the spar number, you should have been put in as a child spar to that one when you called.
PM me your log number (and or Serial number) from when you called, if able, I will have yours added as a child spar to that one so you get notification from Xerox if and when a fix is available from Xerox, but it will likely be coming from MS since it affects non-Xerox drivers too. Add your email address to the PM as a contact method. I can't promise anything though since I don't know what kind of printer you have, contract details, country of origin etc etc)
Adding to the other threads won't help unless you have something to add as a workaround. This is a peer-to-peer forum, not official support. So the Xerox Engineers and developers don't view or maintain it. I do indeed work for Xerox, and I do work in 2nd level (there are many teams though) but Xerox doesn't pay me to work here on the customer side of the forum, I do so on my own.
As for the forum password thing. The forum is "Powered by Lithium".
I've asked, but was never given a response as to the low security password.
Thank you for your post.
That's literally what I asked them to do - but in different terms. "IF you know this is an issue, can you add me to the master ticket?". I instead received more arguments.
I understand that the forum is user to user. Still, look at the reaonable, thought out reply I got here versus my experience with them on the line. Insanity.
Your efforts here are not unnnoticed. If I find a work around in my spare time, I will be sure to offer it.
I'll PM my details for the serial number after lunch.
Thanks, SPAR is a Xerox term, and depending on where you were calling (what product in what country) it may not be used.
My statements about the forum were not to put it down by any means, just a notification as it were, that Xerox Corporate and the Engineers and developers and even the support teams don't officially actively monitor it.
Once I have your info in the PM, I promise I will try and do whatever I can to get you added. I will have to email you directly to get a configuration report from the device if it is in the USA, it is a requirement of the spar process (Even though the issue is the driver and not a printer)
For those in the future wondering why I accepted this as solution? At this time it's an open master ticket. Getting my name on the list for updates is a reasonable spot to be in based on the widespread nature of this. I'll be sure (or feel free to harass me if I don't) to post the updated solution if even a link to an update later.