apprenticearb Posted October 8, 2019 Posted October 8, 2019 Hi All, We have started moving to Windows 10 and noticed users having problems installing printers via GPO when logging on to a computer for the first time. Error in Event Viewer shows: Event ID 513. Print services: Group Policy was unable to add per computer connection \\printserver\Printer Queue. Error code 0xBC4. This can occur if the name of the printer connection is incorrect or if the print spooler cannot contact the print server. and Event ID 4098. Application: The user 'Printer Queue Name' preference item in the 'Printer Queue {######-####-####-####-#########}' Group Policy Object did not apply because it failed with error code '0x80070005 Access is denied.' This error was suppressed. We don't have a problem in Windows 7. We deploy the printers Via user Configuration > preferences > Control Panel Settings > Printers. All linked from our printer server. Hopefully someone can help. Thanks Apprentice!
ShellfishClive Posted October 8, 2019 Posted October 8, 2019 What happens if you try to map the printer manually by going to the share? Does it install?
apprenticearb Posted October 8, 2019 Author Posted October 8, 2019 What happens if you try to map the printer manually by going to the share? Does it install? It does install and the user now has a printer. Thanks Apprentice
ShellfishClive Posted October 8, 2019 Posted October 8, 2019 I'd double check your GPO then, make sure that you are putting the correct share name in the option. You may have typo'd or something.
apprenticearb Posted October 8, 2019 Author Posted October 8, 2019 I'd double check your GPO then, make sure that you are putting the correct share name in the option. You may have typo'd or something. It works for our windows 7 clients, the same GPO and has worked for 3+ years with Windows 7 machines. Problem only occurs on windows 10. Thanks Adam
ShellfishClive Posted October 8, 2019 Posted October 8, 2019 Have you tried mapping it through; User/Computer Configuation > Preferences > Printers That's the way do it through Windows 10, we used to do it the way you did for Windows 7 though. Should be able to do it that way and run gpupdate and it should pull it through.
CHiLL Posted October 8, 2019 Posted October 8, 2019 Printers have been a nightmare in Windows 10 for years, even in Windows 8.1 we had issues, specifically one of the errors you mentioned: The user 'Printer Queue Name' preference item in the 'Printer Queue {######-####-####-####-#########}' Group Policy Object did not apply because it failed with error code '0x80070005 Access is denied.' This error was suppressed. Printers do not add at first log-on, but do for all subsequent logons on that machine. A ballache if you need to run DelProf. I've spent such a long time trying to fix it and even had two external IT support contractors take a look. The problem still exists. We use GPP to deploy printers, but it also happens if you use scripts to deploy printers (PS, VBS, BAT). I don't think there's a way to fix it. There's a huge on-going thread about Windows 10 printer issues here, originally started in 2017: http://www.edugeek.net/forums/windows-10/191185-disappearing-printers.html 1
fredbayker Posted October 9, 2019 Posted October 9, 2019 Make sure the authenticated users group has read and apply on the GPO otherwise your machines will not have the rights
arjanver Posted October 10, 2019 Posted October 10, 2019 this is a problem with all windows 10 versions.....at least we have experienced it. We use redirected startmenu's and i have placed a gpupdate script inside the startup folder within the startmenu, and our printer problems are gone.
tech-man Posted October 10, 2019 Posted October 10, 2019 We had a host of issues getting printers to deploy reliability and ended up using http://www.printermapper.com and since then we’ve had no issues at all. The best money I’ve spent in years! Hi All, We have started moving to Windows 10 and noticed users having problems installing printers via GPO when logging on to a computer for the first time. Error in Event Viewer shows: Event ID 513. Print services: Group Policy was unable to add per computer connection \\printserver\Printer Queue. Error code 0xBC4. This can occur if the name of the printer connection is incorrect or if the print spooler cannot contact the print server. and Event ID 4098. Application: The user 'Printer Queue Name' preference item in the 'Printer Queue {######-####-####-####-#########}' Group Policy Object did not apply because it failed with error code '0x80070005 Access is denied.' This error was suppressed. We don't have a problem in Windows 7. We deploy the printers Via user Configuration > preferences > Control Panel Settings > Printers. All linked from our printer server. Hopefully someone can help. Thanks Apprentice!
Disease Posted October 15, 2019 Posted October 15, 2019 We deploy printers using GPO -> Computer Configuration > Policies > Windows Settings > Printer Connections. Configured to the GPO using Deploy Printer from the print server and selecting the Printer GPO we have attached to the OU the computer is in. Works a treat.
chazzy2501 Posted October 15, 2019 Posted October 15, 2019 I map the printers using 3 methods(script, GPO and GPP), still only a 99% working rate. I've just allowed pupils to add their own printers now.
mrstrong Posted October 16, 2019 Posted October 16, 2019 We also do via User Configuration > Preferences > Control Panel Settings > Printers and we have the action as update. Think at one point it was replace but that caused slow logins.
apprenticearb Posted October 16, 2019 Author Posted October 16, 2019 out of interest anyone use spaces in there share path? Are there issues deploying spaces in your share path over group policy?
CHiLL Posted October 16, 2019 Posted October 16, 2019 out of interest anyone use spaces in there share path? Are there issues deploying spaces in your share path over group policy? Our mapped printers are something like this: \\printserver.local\IT1 Printer So they do contain a space and they do map, just not consistently. I've done testing on whether the spaces make a difference - they do not. The same mapping issues occur with or without spaces in the printer name.
The_Techie Posted October 16, 2019 Posted October 16, 2019 We use item level targeting in GPO and that seems to work
apprenticearb Posted October 16, 2019 Author Posted October 16, 2019 Our mapped printers are something like this: \\printserver.local\IT1 Printer So they do contain a space and they do map, just not consistently. I've done testing on whether the spaces make a difference - they do not. The same mapping issues occur with or without spaces in the printer name. Funny, I created a new printer queue with a different share. It all works now, this new printer share with no spaces. Pretty much the only change I have made.
jonnykewell1 Posted October 16, 2019 Posted October 16, 2019 @themightymrp - one for you to follow here.
themightymrp Posted October 17, 2019 Posted October 17, 2019 I've been battling with this for the past month. I seem to now have a stable method trialing in one IT suite. I have a vbs script stored in a sub-folder of the NETLOGON share. On the machine GPO that I apply to the room (which I normally use to deploy a printer using GPP), I have instead enabled user loopback processing on the policy. Then in the user side of configuration, pointed to my vbs script as a logon script. So it only applys this logon script in this room. Seems long winded but I've just gone my first full day without issues!
themightymrp Posted October 18, 2019 Posted October 18, 2019 Looks like I spoke too soon, had an issue again this morning Anybody have a fool proof 100% working method? I want students to only see the printer(s) in the room they log into. All clients are Windows 10.
apprenticearb Posted October 30, 2019 Author Posted October 30, 2019 what security perrmissions to people use for printer queues? I have attached mine below, wondering if anyone keeps the 'Everyone' group in.
themightymrp Posted October 30, 2019 Posted October 30, 2019 I have the everyone group set on some devices which are available to all users in school. Not sure if that is a bad idea or not? There are certain areas where I specifically only allow groups of users to connect (like colour laser printers). For what it's worth, going back to the topic of this thread, I think I've finally got it sorted. I've spent a full day this half term working in one room, tinkering. This is what I have done: 1) In the GPO for the room, go to Computer config --> Windows Settings --> Printer connections. 2) Add in the printer(s) I need for that room using FQDN i.e. \\server.domain\printer 3) In the same GPO go to Computer config --> admin templates --> system --> Group policy 4) Enable the loopback processing and set it to merge 5) Same GPO again but now in User config --> Windows settings --> Scripts --> Logon 6) A short VB script which is set to wait 15 seconds and then set the default printer 7) In Active Directory, create a security group containing the computer accounts of the PC's in the classroom in question 8) On the printer server, modify the permissions of the shared printer and add the computer account security group with permission to print Adding the printer connections this way seems to have been the most reliable. However it doesn't let you specify which should be the default, hence the rest of the setup. The 15 second wait was added because for some reason immediately after logging in it was erroring the script saying the printer wasn't installed. Even though technically it should have been ready for the logon. Strange. The reason for the computer account security group part is that without this, the Event Logs were showing loads of errors. I tracked these back to the fact the computer account didn't have access to the shared printer pre user logon and so wasn't installing it 1
themightymrp Posted November 6, 2019 Posted November 6, 2019 Still having troubles with this Thought I'd nailed it but then today had about 50% fail in one IT suite. Out of ideas now, any suggestions?
fredbayker Posted November 6, 2019 Posted November 6, 2019 I would try the following two methods, not sure if you have tried it this way already but I use a similar method to achieve our setup and works 99% of the time, very rarely failing but remedies with a forced gpupdate. Method one 1. Enable loop back - merge 2. Deploy the ‘shared’ printer via GPP (user config) Apply to OUs containing Computers (One GPO per OU) Method two 1. No need for loop back for printers 2. Deploy ‘shared’ printers via GPP under user config on the root of the users OU 3. Use Item level targeting by creating machine based security groups or using OUs. (ie only deploy this printer if the PC belongs to machine-groupX or the PC is located in OU-X You could add a ‘delete all printers’ preference item first in both methods to delete existing printers OR (I’m not sure on this but..) set each item to ‘replace’ and tick the ‘remove when no longer required’ checkbox. The replace and delete do affect login times so near that in mind.
apprenticearb Posted November 8, 2019 Author Posted November 8, 2019 Still having troubles with this Thought I'd nailed it but then today had about 50% fail in one IT suite. Out of ideas now, any suggestions? Have you tried creating a brand new printer share and just testing it on that IT suite. I setup a new printer queue set it up pretty much exectly the same as the old one and it works 100% of the time. The most significant change I made was no spaces in my printer sharing name path
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now