Windows 10 Printer Deployment Not Working

Windows 10 Printer Deployment Not Working

Remember when adding Printers to domain computers were nice, simple addition to easy to make? No, I did not. however the item was never as difficult as the element now appears to be with Windows 10. Specifically speaking build 1511. Do not get me wrong, I sold on Windows 10. The item of fast, efficient addition I use the item in all of my computers. that does not change the fact that there are many problems when using the element on large networks.

I help to manage two major domains than three sites within the educational establishment. One for Admin Staff except one for students. We have thousands of customers in addition to several hundred printers. During the summer after months of testing we made the move coming from Windows 7 to Windows 10 (1511) on the Student network. We have always added our printers by Group Policy. This particular makes the item easier to add printers to every PC without having to go around each one individually. Up until then we had used a batch file in GP to copy a VBS script to the start-up folder on the client which subsequently added the printer via command line. the item wasn’t perfect, nevertheless the item worked.
With Windows 10 we found This particular to be very unreliable during the early testing stage in addition to decided the item was time to move to the ‘correct’ way of connecting clients to printers via Group Policy. nevertheless how? There are at least 7 ways to do This particular using GPP (Group Policy Preferences) or Deployment in various combinations. We have printers associated with specific rooms in addition to the students move coming from one classroom to another. which ruled out for us adding the Printers via User.
For months I experimented with all methods available in addition to came to one conclusion. which they are all as bad, inconsistent in addition to as unreliable as each various other. inside the end we decided to use the deployment method. The main reason being was which there were alterations to be made at the server end which I will get to later. When these alterations are made using the deployment method, they are automatically picked up by the client. If you use GPP, the printer needs to be removed in addition to re-added for them to work. Deployed printers are controlled by the print server. GPP locally. Something worth remembering.
After numerous experiments in addition to even more failures I commenced to scrape together information of what can be required to get This particular to work. There are so many blogs in addition to walkthroughs in addition to forums giving advice, nevertheless NONE of them carry the full story. Here can be everything I had to do get over 100 printers attached to the 1000 student clients inside the correct rooms, every time a brand-new user logged in in addition to of course have them printing correctly.
Step 1: Prepare your environment.
So you have your computers nicely imaged with Windows 10 in addition to your old, reliable print server hasn’t changed. You may even have gotten a printer to appear on the odd client. nevertheless some clients simply refuse to add them. Some, there are no errors at all. Others complain about drivers in addition to print processors.
Here can be what you need to do:
You will find This particular answer on every webpage dedicated to This particular issue. Disable Point in addition to Print, Disable Point in addition to Print they say. This particular can be not the full story, even if they have been kind enough to tell you how to actually do the item. I found Point in addition to Print has to be enabled to work! Use Group policy to enable This particular feature in addition to then disable the restrictions. This particular will enable the client logged in as a user to install printer drivers on the quiet, without prompts or any user intervention.
The trick here as well can be to create TWO separate Group Policies. One for Computer Configuration (see above) in addition to one for User Configuration. Attach the computer policy to the top of your client hierarchy in AD in addition to the user policy to the top of your Users OU. The fun doesn’t stop there. To enable Point in addition to Print to work properly with Windows 10 you may have to make alterations to your Print Server. NOTE: We have three Print Servers. Each can be currently running a different operating system. Server 2008, Server 2008 R2 in addition to Server 2012 R2. These fixes worked on all three.
Reconfigure your Print Server:
This particular isn’t as scary or as intrusive as the item sounds. nevertheless there are some significant alterations to be made. I will say to first backup in addition to/or snapshot your server before you begin. The first can be drivers: Please note here which Windows 10 does NOT like TYPE 4 drivers, so avoid these if you can (we were lucky in addition to didn’t have any). Older versions of Print Management as I found on 2008 do not list Driver Types in addition to can make things harder to identify. I got around This particular by managing which server as yet another print server on the 2012 R2 box. I was getting an error in my event log: Error code “0x80070bcb. The specified printer driver was not found on the system in addition to needs to be downloaded”. This particular can be what Print in addition to Point can be supposed to do for us.
However: Print in addition to Point with Windows 10 does NOT like ‘unpackaged’ drivers. On your Print Server expand your server name in addition to select the drivers section. You are looking for the column labelled “Packaged”. If the print driver for the printer which you are trying to deploy can be marked as “False”, then the item can be most likely NOT appearing at all on the client.
The obvious fix here can be to download a brand-new driver for Windows 10 coming from the printer a new. nevertheless if your printer can be a little older or you already hold the latest driver This particular won’t help much. Have no fear there can be a nice, simple work around inside the form of a registry fix which got me out several deep, dark holes where printers didn’t exist.
Open Regedit on the Print Server:
Navigate to: HKLMSystemCurrentControlSetControlPrintEnviroments[Windowsx64]
or [Windowsx86]Drivers...[Driver name]
You are looking for an entry called “PrinterDriverAttributes” on the right hand side in addition to will probably be set having a value of “0”. I had one set to “4”, nevertheless the item made no difference. Change This particular to “1”.
right now close regedit, reboot your Print Server in addition to open Print Management again. See, your Print Driver can be right now marked as “True” under the Packaged column.
What This particular change has done can be create a CAB file containing the driver, in addition to all the various other information about your printer which Point in addition to Print can send to the Windows 10 client. Windows 10 likes the CAB file in addition to adds the Printer. Everybody’s happy. You get the nasty business of your print driver inconsistencies out of the way in addition to you find some printers are still not appearing on your clients. Only This particular time you get the error: "Unable to install printer. The print processor does not exist" in your event log. This particular can be exactly what the item says on the tin. The Print Processor can be simply a DLL file which isn’t present. the item can’t be just copied over in addition to registered either. the item can be fixed with This particular workaround: Open the properties of the Printer (right click) on the Print Server, select the Advanced tab in addition to click the Print Processor button at the bottom:
See This particular HP 1505n can be using its own Print Processor. However, unlike Windows 7 (or below) This particular can be NOT always available on Windows 10. When you install a driver the item copies everything you need including the PP to the C:WindowsSystem32spoolprtprocsx64 folder. At least the item should. I found This particular to not always be the case. Simply changing This particular to Windows Own PP seems to do the trick. Change This particular to winprint – RAW. Winprint can be available by default on ALL Windows 10 installations.
Click ok, reboot your client in addition to test the Printer. I did find on some which they printed garbled symbols until the Print Spooler was restarted inside the Print Server. I will add here which This particular can be one of the alterations which does NOT work straight away on the client if the printer has been added as a local or TCP/IP printer. This particular can be because in which case the client can be managing the Print Processor in addition to the printer will need to be removed in addition to re-added coming from the server. If you are using deployed, the item should just work.
Step Two: Deploy your Printers.
Create your Group Policies:
With your server’s setup the item can be right now time to deploy your printers if you haven’t already done so. This particular can be done to users or computers. As I mentioned before, we had to use Computer Policy. I will add which we tried Local Printers via User Policy with Loopback enabled. I won’t go into the details; I just don’t recommend the item. Save yourself a lot time in addition to premature baldness by not going down which route.
Create a brand-new policy, name the item in addition to Navigate to: Computer configuration > Policies > Windows Settings > Deployed Printers
Right click, select deploy printer, type inside the printer path in addition to click ADD. Repeat This particular for all printers for which policy.
Click OK in addition to you’re done.
The same can be done by deploying directly coming from the Print Server to Group Policy by right clicking the printer in addition to following the wizard.
Step Three: Check your Clients:
You’re set up ready to go in addition to maybe some of your clients are right now printing away merrily. nevertheless what if they are not? Here are a couple of things to check in addition to one fix you won’t see coming.
Obviously network connectivity can be a must. Check your printer can be connected in addition to switched on. You may wish to run a GPUpdate /force on troublesome clients in addition to make sure the item can be also connected to the domain in addition to the item’s computer account can be inside the correct OU with the GPO attached (in addition to enabled).
There have been numerous Windows Updates curtesy of Microsoft which have broken Point in addition to Print settings. Even set up correctly your clients will refuse to pull down a driver in addition to add the printer to the client if these patches are installed. They are:
kb3163912 – Windows 7
kb3172985 can be the patch we had problems with. the item can be a cumulative update which carries one or more of the various other KB’s in which list. Uninstalling This particular coming from the Windows 10 client in addition to rebooting had an immediate effect. This particular can be done manually or via script using Group Policy.
%windir%system32wusa.exe /uninstall /kb:3172985 /quiet /forcerestart
Above can be the uninstall command for removing windows updates silently (just change the KB number). nevertheless: KB3172985 seems to have problems with This particular in addition to ignores the /quiet switch. This particular can be due to how the KB has been signed. I found the only way to get This particular to work was to download the MSU in addition to run the commands against which coming from a server.
%windir%system32wusa.exe /uninstall \[File Path]windows10.0-kb3172985-x64_006b20fc4c418499afa25248edacff2ef7dab963.msu/quiet /forcerestart
TIP: Run This particular out of hours. YouWILL need the /ForceRestart switch. If Windows doesn’t reboot right after running the command the patch will NOT remove probably in addition to you will have to be done again. By right now you are probably a little cheesed off in addition to heaving a sigh of relief as you printers start to appear in addition to your users are printing to their hearts content. Until… yes, someone logs in in addition to shock, horror there can be no printer available. This particular was a problem I hadn’t seen coming at all. I found an error inside the event logs on the client claiming which the printer could not be added as the Print Spooler (on the client) had not commenced in a timely fashion in addition to could not contact the print server. I checked in addition to the service was running away happily. nevertheless still no printer. As far as I can tell This particular can be just another Windows 10 inconsistency in addition to annoyance. What’s happening can be which the GPO can be applying before the Print Spooler service has finished starting; therefore, failing. We are probably talking a microsecond difference in addition to we have had This particular in more rooms than I care to count. As far as I could see there was only one thing for the item: Restart the Print Spooler! Easy. Back to Group Policy again.
This particular can be where we get clever:
Create another GPO. We experimented at first in just a couple of problem rooms in addition to linked the item to their OU’s then moved the item higher up the OU hierarchy. Navigate to:Computer Configuration > Preferences>Control Panel Settings > Scheduled Tasks
Create a brand-new Scheduled Task (At Least Windows 7)
Call the item whatever you like: “Restart PrintSpooler” worked for me.
Set the item to run as NT AUTHORITYSYSTEM in addition to tick the “Run with highest privileges” box.
I set the item to run a batch file coming from a server containing the following commands:
net stop spooler net start spooler
which’s the item. right now the clever bit. We know which by the time the user has logged inside the Print Spooler has commenced in addition to the GPO has attempted to connect the printer. Upon testing if the Print Spooler service was restarted manually at which time I could see the printer reconnecting without having to log off or reboot etc.
  • Set the schedule to run 30 seconds after any user logs on to the client by changing the dropdown box at the top in addition to ticking delay task (set to 30 seconds) at the bottom.
  • OK everything, reboot (in addition to/or GPUpdate) your clients in addition to watch the magic happen.
A Note on Default Printers:
We get a lot of questions regarding default printers in addition to Windows 10. Firstly, if you are connecting your printers by Computer Configuration in Group Policy, default printers CANNOT be specified there. In addition, you can’t do This particular with Deployed printers on User Configuration either. Next, Windows 10 sets its own default printer. the item will either be the Last Printer Used or the Last Printer added. If you have more than one printer to add via GP, separate then into different GPO’s in addition to order them accordingly. The last to apply will become default.
This particular feature can be disabled on Windows 10 either on the client or in GP.
Windows 10 (1608 Anniversary Build):
Preliminary testing has found some of these issues to have enhanced. Although which maybe because we have very few clients running which build. the item can be something which must be tested before rolling out the anniversary update. which can be another set of problems entirely. To conclude, our printers are still not 100%. nevertheless using these methods has reduced complaints in addition to we are gradually pulling ourselves out of a pit of printing despair. I wish my trials in addition to tribulations into the globe of Windows 10 printer deployment will help some various other poor the item analyst’s soul suffering the same fate. I feel your pain! right now go forth in addition to print.
Since I wrote This particular (This particular morning), two more problems have raised their ugly heads inside the complicated realm of Windows 10 Printing. The first can be where a printer does connect to the client nevertheless errors upon printing. We found This particular to be a driver issue on the client after creating alterations on the server (so try to get these all in place before you deploy). To correct the problem, we needed to remove the driver. This particular can be not as simple as just removing the printer in addition to requires some split second timing. Load Print Management on the client.
Load the Services MMC.
Expand the drivers section of Print Management in addition to find the driver in question. You need to place these windows side by side.
Restart the Print Spooler service inside the services MMC. Before This particular finishes, right click the driver in Print Management in addition to select “Remove Driver Package”. Time This particular right in addition to the driver will uninstall. You may need to try This particular a few times to get the item right. Once the item has gone, reboot the client, let the Group Policy reapply in addition to your printer should be back up in addition to running on the client.
Next we had a very strange problem where some printers wanted to install an App coming from the Windows 10 App store.
A store which we block access to (with Group Policy). Regardless of which, the drivers required are on the Print Server in addition to clients should be working fine with those. various other printers of the same type in addition to configuration are working correctly in addition to I have found in some cases these do too. In others the item can be best to simply remove the deployment coming from the Group Policy in addition to re-add the item. The next time the Clients reboot they seem to pick up the printer without further issue.

Subscribe to receive free email updates:

0 Response to "Windows 10 Printer Deployment Not Working"

Post a Comment