Hey Everyone - Super Strange Issue!
We deploy printers using GP prefs (to users on 2012R2 Terminal Servers). We recently migrated to a 2012R2 print server (from 08R2). I can't seem to get the 'Set Default' option working when users log in. However, if I manually run a gpupdate /force after the users log in, the default sets properly as expected.
In the event logs, I get one of two messages when a user logs in (Event ID 4098 -- Error applying 'Default Printer for Accounting' -- 0x80070bc4 No printers were found), or (Event ID 4098 - Error Applying 'Default Printer for Accounting' -- 0x8007000a The environment is incorrect').
I have tried using all CRUD options (create, replace, update), and neither have an effect.
I have tried with and without item level targeting, no luck.
I have tried 'running in logged on users security context', no luck.
I have tried re-creating the GPO, re-scoping it, etc, still no luck setting default. RSOP shows the GPO is applying properly, and other items in the policy are applying properly. Setting default is the only thing that's not working.
I have tried using \\printer-server\Printer1 as the printer name, as well as \\print-server.company.local\Printer 1, no luck. I have tried removing spaces from the printer names (eg Printer1 instead of Printer 1), no luck.
I have tried different print models and print drivers, no luck. I can't get any printer to set as default properly (eg. HP, Xerox, different drivers).
I tried sharing a printer from another 2012R2 server, and same thing happens - it will add the printer, but wont set it as default. If I share a printer from a 2008R2 server, it sets the default properly, and sets it every time (eg if I change the default manually, logout and login, the default is set properly every single time). So this only seems to happen when the shared printer is on a 2012R2 box.
I've tried setting up a brand new RDS server, still no luck. Tried deleting all RDS profiles and loggin in with new users, no luck. Have also tried setting 'wait for network' before processing GPO (not to mention the server is usually on 24x7 and network connectivity should already be established.
I've literally tried everything, and am tempted to open a ticket with MS. No matter what I try, I get one of the two error messages above in the event logs. As a temporary workaround, I have 'gpupdate /force' running in a login script, but that's kinda silly and I shouldn't have to.
Ideas?