Hey Experts. I have a mid-sized (150'ish users) gov agency that uses many printers, roughly 70. This is due to the nature of our office (legal) and the sensitive material printed which can't go to a "public" printer.
To make this design work, I created AD groups (ie, LEG1 and LEG1-D) that we could assign users to and when they would login, our login script would run and install printers based on group membership. The -D made the printer the default which was the trigger for the script to move on to the next section.
However, the latest MS patches that were released broke our printing design and in the short-term, I had to uninstall KB5005031 and 5005103 so that I could get printing running again.
Many recommendations are to use GP's to assign/install printers which is a great concept but I'm not sure I completely grasp its application in all environments. If I understand correctly, I would create a GP for the printer (LEG1), assign users to it and the GP would install that printer.
Based on that idea, would I need to create 70'ish GP's? Surely that can't be the case and I'm not understanding how to use GP's to deploy printers.
What I'm looking for here are 1) suggestions/guidance of putting a methodology in place that will work with the latest KB's and 2) if GP's can satisfy #1, how to use those but not if it requires a GP for each printer.
Thanks in advance for your help!
ASKER
ASKER
ASKER
ASKER
Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.
TRUSTED BY
ASKER
As for the two group creation, yes, strictly for the login script to process which printers should be installed for that user and which to make the default.