01-02-2018 06:50 AM
It seems there is a problem with the global print driver and the latest version of Windows 10 (1709)
I've tried the latest version and the version before that of the global printer driver, but the issue is the same.
Basically shared printers settings, don't transfer to clients from server, for example, we have some printers set to default paper size A3, however on clients with Windows 10 version 1709, it always shows A4 as default, while Windows 10 version 1703 clients show A3 as set.
I've done some testing, and for an example a client with Windows 10 (1703) will be working fine, and the upgrading said client to version 1709, will result in the setting not being transfered and the printers which had default A3 paper size selected will now be A4.
We are using version 5.585.13.0 (5582.1300.0.0)
01-02-2018 01:28 PM
Odd, the version you state has been the one known to fix the problem, did you do a complete removal and then install or just update? Try at least installing it with the version specific GPD
01-03-2018 04:55 AM
Well it did fix the problem, of users with version 1709, not being able to print from Microsoft Edge, that works fine now after updating to version 5.585.13.0, but the problem with not getting the settings from the server remains.
I will test installing the version specific GPD, since we currently not using that one, we are using "Xerox Global Print Driver PS" on the server and see how that goes.
01-03-2018 09:45 AM
We are also experiancing this problem AGAIN after upgrading to 1709. We had it in 1607 then it was fixed in 1703 and now the same problem is happening in 1709.
Microsoft has confirmed that this is an issue in 1709.
Guess we will just have to wait for an update...
01-03-2018 11:41 AM
Yes we also had the exact same problem with 1607, annoying to have to deal with this again, but like you said, I guess the only thing we can do is wait for an update, patch tuesday is in a few days, one can be hopeful.
02-13-2018 04:22 AM
Amazing that this issue was reported back in november and there is still no fix...
Has anyone found a workaround or heard anything from Microsoft?