GPO Printers no longer working after 1511

[grahamd22]

Did any of these ideas fix your issues as we have released Windows 10 1607 for students with massive initial network printer install failure. Once the profile is there with a restart the printer appears. We tried vbs, point and print but with no change. Event ID: 513. Group Policy was unable to add per computer connection \\servername\printername. Error code 0x57. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.

[HereIGoAgain2601]

We have been having similar issues with the second logon solving the problem. Have tried the registry keys above and initial results seem positive will monitor and feedback

[arjanver]

We have been having similar issues with the second logon solving the problem. Have tried the registry keys above and initial results seem positive will monitor and feedback

 

We have some sort of same problem. tried really everything.

http://www.edugeek.net/forums/windows-10/189682-windows-10-group-policy-fail-directly-after-boot-succes-after-relogon-0x80074005.html

 

Bu we solve it by using a Logon script (user)policy which launch gpupdate command. seems a little spartan solution, but for now it works.

[Sheridan]

Printer deployment in Windows 10 is a complete nightmare now. Even a printer we managed to deploy using GPO Computer Preferences now won't update! We simply changed the printer and driver on the printer server, yet all of the PCs still think its using the old driver. If we remove the printer from GPO preferences it still stays in the users Devices and Printers. Its a bug ridden mess compared to the way W7 used to work.

 

This is on 1607, 1703 and 1709.

[Katy]

Printer deployment in Windows 10 is a complete nightmare now. Even a printer we managed to deploy using GPO Computer Preferences now won't update! We simply changed the printer and driver on the printer server, yet all of the PCs still think its using the old driver. If we remove the printer from GPO preferences it still stays in the users Devices and Printers. Its a bug ridden mess compared to the way W7 used to work.

 

This is on 1607, 1703 and 1709.

This. I'm sick of telling people almost daily "restart the computer and if you're lucky your printers will re-appear" when they either fail to map for no reason at logon, or just vanish completely halfway through the day with no trace of where they went in the event log.

[Sheridan]

This. I'm sick of telling people almost daily "restart the computer and if you're lucky your printers will re-appear" when they either fail to map for no reason at logon, or just vanish completely halfway through the day with no trace of where they went in the event log.

 

Yup - I used to user Deployed printers in Windows 7 with few issues, now neither Preferences or Deployed seems to work.

 

Annoyingly in this case the printer had deployed - but it died and I had to replace it and therefore the driver. Despite the driver working on other machines all these are still clinging on to the old driver!

[arjanver]

We have some sort of same problem. tried really everything.

http://www.edugeek.net/forums/windows-10/189682-windows-10-group-policy-fail-directly-after-boot-succes-after-relogon-0x80074005.html

 

Bu we solve it by using a Logon script (user)policy which launch gpupdate command. seems a little spartan solution, but for now it works.

 

I'm using GPP Printer policies with a logon script policy with this script.

Set WshShell = CreateObject("Wscript.Shell")
Result = WshShell.Run("cmd /c echo n | gpupdate /target:user",0,true)
Wscript.Quit(Result)

[Sheridan]

I'm using GPP Printer policies with a logon script policy with this script.

Set WshShell = CreateObject("Wscript.Shell")
Result = WshShell.Run("cmd /c echo n | gpupdate /target:user",0,true)
Wscript.Quit(Result)

 

Crazy that you have to force a gpudate though, isn't that the point of GPOs that they will update when changed!

 

I've given up with this printer - even a brand new fresh login on one of the PCs brings up the printer with the old drivers, somewhere a reference to it can't be removed!

[grahamd22]

It does seem to work I've just added below to a test users student logon script :

 

Set objShell = CreateObject("WScript.Shell")

objShell.Run "gpupdate /force", 0, True

[Sheridan]

It does seem to work I've just added below to a test users student logon script :

 

Set objShell = CreateObject("WScript.Shell")

objShell.Run "gpupdate /force", 0, True

 

In our case the Printers are deployed as a Computer Preference (i.e room based printer deployment) and the machines all show that GPO's have been processed on boot, they just don't seem to be taking effect in the case of the printers.

[arjanver]

In our case Printers are deployed to OU's (rooms) which contains computer objects, and in that room is also the printer.

My user policy is linked to that computer ou with e group policy merge loopback.

[Jobos]

I've given up with this printer - even a brand new fresh login on one of the PCs brings up the printer with the old drivers, somewhere a reference to it can't be removed!

 

Sounds like the ghost print issue from http://www.edugeek.net/forums/windows-10/183649-windows-10-printers-keep-coming-back.html#post1630211

[grahamd22]

Returned to the original gpo's and its now reverted back to the original issue of missing after every 2nd !

It must be something regarding the removal of profiles but why every other time, even after deleting the profile manually everytime makes no sense as we have profiles set to automatically delete after 1 day.