Solved! Go to Solution.
At this time it can't. The issue has been reported to both Microsoft and Xerox. There is no ETA on a fix.
Workaround is to install it locally and all will be well for those who need specific preferences.
It is also unknown if it relates to the massive defaults issues seen in build 1607.
There isn't much, Xerox developers are looking into it.
If you have a contract (maintenance agreement) with Xerox, call in, get to 2nd level support and ask them to do a "child spar" (They will understand the terminology), and have it tied to the Parent Spar CQGbl01004099.
I found a workaround, but it isn't pretty. The instructions below will help you create a registry item in a GPO that will add printer preferences per user via registry.
If you want to clean it up, you can cut and paste the DevMode item into the top-level Registry folder under preferences.
Now this will apply preferences every time Group Policy is applied to a PC.
thnx for the workaround
but i hope xerox/microsoft fixes the issue soon
dont understand why its taking so long
i have applied the workaround but appearnlty it does not create the registry key. i have applied it exactly as you have explained. i tried with Action Replace, Create and Update.
is there any other way to apply the preferences?
i found this KB https://support.microsoft.com/en-in/kb/3201130
and tested it yesterday on my 2008 R2 Server, but i my case it doesn´t solve the problem.
i connected a printer to a client with other printers installed, and tested it with a new installed pc Win10 1607.