How to setup a Windows Print Server and deploy printers using Group Policy 

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

Thanks for watching!

To deploy the printer to a computer directly so all users who login can print to it, I would do basically the same thing but instead change the group policy configuration slightly. 1. Add the computer objects to the printer security group in Active Directory. 2. Link the 'printers' group policy object to the workstation organisational unit. 3. Add the shared printer under the Computer Configuration section of the GPO and setup item-level targeting to point to the printer security group, but select the 'Computers in group' setting in the targeting editor. 4. After a reboot of the workstation, the printer should then appear for all users that login to the computer listed in the security group. I hope that makes sense. Thanks for watching!

@@danny_moran Ok, thanks, i think i will test this. Cause i dont want to use Loopback processing

Usually, we just use MFP printers that have scan to email or scan to a file share functionality. This way you don't have to mess around with scanner drivers. If it's a desktop printer, than I just install the scanner drivers manually. Thanks for watching!

Thanks for watching!

Thanks for watching!

It depends. If the driver shows as 'packaged' in the driver list, then it should install automatically, even if the user is not a local admin. Thanks for watching!

I use a server that is not a domain controller to host the print server role. Thanks for watching!

No, this method can't be used for password printing, or scanning, unfortunately. Thanks for watching!

Yes, that's what I do in this guide. I use item-level on the shared printer in the GPO to filter who gets the printer. Thanks for watching!

@@danny_moran Oh, I actually didn't understand it completely... :) Thank you very much for this video.

I don't think Microsoft support print server clustering any more. I think their guidance is to host the print server virtual machine on a high availability hypervisor cluster. Thanks for watching!

@@danny_moran is it possible to make a video on hyperv clustering of print server

I do plan on making some Hyper-V guides, however, I don't have the hardware to do so at the moment.

I just right-clicked and copied them from my local computer to the downloads folder on the server. Thanks for watching!

I would recommend downloading the latest drivers from the printer manufacturer's website. Thanks for watching!

@@danny_moran Ok I've done everything you did, but in group policy management, which OU do i link my GPO to? I only need to deploy to 3 servers. So shall I just link the GPO to the whole domain but only target the security group i made containing the 3 servers in it?

You will need to link it to the OU that has your users in it, as the printer settings are setup within the user configuration.

If the "packaged" value is false, then you might have difficulty deploying the driver. I'm not sure why this is the case, however, it's something I've also just discovered a few weeks ago. I don't have a solution at this time. I've found this is only with older drivers, and the newer drivers "packaged" values are true.

This guide is adding a print server to an existing Active Directory domain. Thanks for watching!

Are you using a type 3 or type 4 printer driver? If you are using a type 3 driver, then this is likely what's causing the credential popups. Thanks for watching!

I use Hyper-V to have multiple virtual machines running at the same time. Thanks for watching!

I just prefer to do the three steps manually. It makes no actual difference. Thanks for watching!

I just noticed you also mentioned the deployment of the printers. The reason I do it all through group policy, and not through the print management console, is so that I can just have a single printer gpo use item-level targeting and specify who gets each print based on which active directory security groups a user is in.

@@danny_moran cheers mate, was just after more info - nice to learn different ways of doing things ;) I have my departments as OU's in Users and in Computers so in the printer deployment I just point them at those OU's that need that printer. Basically does the same as what you do in the end ;) My biggest bugbear with printers is when a printer driver updates and all of a sudden it's prompting everyone for Local Admin access to install the driver ... a real pain in the backside ;) Cheers for the great videos - really enjoy your content mate ;)

It will work fine to have them both on the same server. I recommend having different servers for different functions. This is better for security as well as being easier to manage, as one application is less likely to impact another. Thanks for watching!

I don't recall seeing that error before when installing printers using GPO. You might be best to do an internet search for the error to see if anyone else has come across this error and has found a solution. Thanks for watching!

If you're using a Type-4 driver, then it works fine with the PrintNightmare security updates and mitigations. If you're using a Type-3 driver, then it works most of the time. I've had a small number of drivers this method didn't work for and couldn't figure out why, but, most seem to work. Thanks for watching!

I never automatically assigned default printers and just let the user do this themselves, as I never had a situation where everyone was printing on the same printer. Thanks for watching!

I use Hyper-V to have multiple virtual machines running at the same time. Thanks for watching!

If the "packaged" value is false, then you might have difficulty deploying the driver. I'm not sure why this is the case, however, it's something I've also just discovered a few weeks ago. I don't have a solution at this time. I've found this is only with older drivers, and the newer drivers "packaged" values are true.

@@danny_moran Thanks for the info. I'll have to do further research on this matter.

Check the network settings on the printer and it should tell you what IP address it has been given. Usually, you can print out a status page from the printer which will give you information about the printer and usually it contains the IP address. You could also check your DHCP server and see if it's been given a DHCP address. Thanks for watching!

I'm not sure what you mean?