Testing the GPD 5.585.13.0 with Server 2016 and Windows 10 1709 + updates yields the same results as the Server 2012R2 and Windows 10. Settings do not carry to user computers over sharing.
This is still an issue into 2018. Testing the MSFT workaround with Windows server 2012 R2 and Windows 10 Pro x64 1709 (and follow up patches) - yields settings that refuse to apply on the server side share. Ex: Server side, follow the MS KB to fix 1607 issues - make a change in advanced - printing defaults - set device to Xerox Black and white. Apply, OK to exit. Go back in server side - settings will have been reset back to default (Colour).
Quality Xerox, as usual.
yes, last time with 1607 also xerox had the greatest impact
lots of our customers are having mixed drivers, hp and others were still working as intended, also with universal drivers
strange though, but i think its the architecture of the GPD
What I also found was that the prefs are not saved or shown consistently throughout the different applications.
Changing Saved setting in eg. Adobe prefs. to "Driver defaults" does not reflect what was set in the prefs. tab on the printer.
I have also tested with a HP UPD and it does keep the settings across apps. as set on the driver.
So it appears that it is related to Xerox (and maybe also Microsoft).
Thanks for all the feedback!
Found out that the settings generally get saved when saving the preferences as a distinct name in the "Saved Settings" drop down.
So instead of using eg. "Adobe Reader Defaults"
save them as eg. "my_defaults"
It appears, that using the given "defaults" for each application (Adobe, Notepad, Word, etc) it does not save them consistently.
Will continue testing
I know about a ticket with MS about Edge browser crashing after the update.
I also know of the one with pointing multiple drivers at one printer (that you are referencing there)
I don't have a spar for the printing prefs thing though, but that doesn't mean there isn't one. But I cannot replicate it either, mine works just fine. That isn't saying there is no issue, just that personally I haven't replicated it, and as you are fully aware, I am not officially here on the forum, I just hang out here, while my links are 100% real and while I have access to a vast amount of stuff not available to the typical user, I do not in any way speak for Xerox officially here.
Joe, this issue seems to be back, xerox is already aware and opened a ticket with microsoft, its happening again with 1709 redstone
more info from xerox :
1402517.Print Queues are reverting to a Single PDL after Win 10 update
- Microsoft has changed its specifications for Redstone 3. If multiple drivers are installed sharing one hardware ID, those drivers are listed in “Driver Stage”. After upgrading Windows to Redstone 3, the print queues use the print driver that is listed at top in “Driver Stage”.
I have a customer complaining of this same problem. They claim the problem started after they upgraded their to Win 10. It appears that MS has confirmed this is a known problem according to this link: https://support.microsoft.com/en-in/help/3201130/printing-preferences-from-the-print-server-don-t-sy...
The link mentions the print server being involved in this problem but from what I am finding online the same symptoms appear when a server is not invloved.
I just installed the driver, set some oddities in the preferences (Tabloid, flip short edge, print to useless left tray, high res)
Opened Adobe Reader DC.
File > Print (shows the 2 sided short edge I selected)
Then opened the properties and verified nothing was different than the preferences, even opened them side by side
So it certainly isn't an issue with the latest GPD PCL6 locally installed on Winodws 10 build 1709 (x64) in all applications.
I can't test Word (Don't have it on the Win 10 box) or Acrobat for the same reason as Word.
And yes, I could for whatever reason simply have changed the settings to match what should be there in order to show the screenshots matching, but it would be rather pointless to do so.
If a reinstall doesn't fix it after a complete driver removal, I'd call Xerox to get it sorted out. I'm not too sure on how we will be able to replicate it since I already tried and failed here, but it may be a scenario where the update to 1709 broke it, not the act of having 1709 with the latest GPD. If that is the case, and it will take a lot of testing (Windows fresh installed to an older release, driver added, then Windows updated, it would be a full shift if not more, only to prove MS is at fault)
If you do call Xerox, and are in the US, and go through to 2nd level support, update this post with the log number so I can look into it further.
Please note, my Win 10 box is my personal one, Xerox has more and will have Word and Acrobat to test against, I'm just using my personal toy here because the forum isn't my job, I do it on the side