Allow Non Admin Users to Add Printers At Home

Adding the users to the lpadmin group should do the trick.

I was reading about the lpadmin group, but could use some clarification.
This would allow them to add a printer from home but not allow them to enter ip addresses for network printers? Is there more to it than that?

Also, I appreciate the response!

Thanks!

Check this...

https://www.jamf.com/jamf-nation/discussions/8666/unlockaddprinter-sh

I'm not sure you can limit the user to adding printers without IP. Most home/personal use printers are Wi-Fi based and the easiest way to set those up is via IP.

On another note, this is what we use in house...

#!/bin/bash

# Allow staff to add printers and manage print queue without administrative rights
/usr/sbin/dseditgroup -o edit -a everyone -t group lpadmin

exit 0

We use -

#!/bin/bash
# Workaround as shown in https://www.jamf.com/jamf-nation/discussions/19050/add-wifi-networks-without-admin-privileges
# Allows non-admin users to add printers and manage their WiFi configuration.

#For WiFi

/usr/bin/security authorizationdb write system.preferences.network allow
/usr/bin/security authorizationdb write system.services.systemconfiguration.network allow

#For printing

/usr/bin/security authorizationdb write system.preferences.printing allow
/usr/bin/security authorizationdb write system.print.operator allow
/usr/sbin/dseditgroup -o edit -n /Local/Default -a everyone -t group lpadmin
/usr/sbin/dseditgroup -o edit -n /Local/Default -a everyone -t group _lpadmin

exit 0;

#!/bin/bash
# Workaround as shown in https://www.jamf.com/jamf-nation/discussions/19050/add-wifi-networks-without-admin-privileges
# Allows non-admin users to add printers and manage their WiFi configuration.

#For WiFi

/usr/bin/security authorizationdb write system.preferences.network allow
/usr/bin/security authorizationdb write system.services.systemconfiguration.network allow

#For printing

/usr/bin/security authorizationdb write system.preferences.printing allow
/usr/bin/security authorizationdb write system.print.operator allow
/usr/sbin/dseditgroup -o edit -n /Local/Default -a everyone -t group lpadmin
/usr/sbin/dseditgroup -o edit -n /Local/Default -a everyone -t group _lpadmin

exit 0;

Perfect solution, Thanks @dsavageED !

#!/bin/bash

# Allow staff to add printers and manage print queue without administrative rights
/usr/sbin/dseditgroup -o edit -a everyone -t group lpadmin

exit 0

This worked great for me, Thanks

All the suggestions don't work on Ventura, and probably Monterey and Big Sur.

I'm running MacOS Ventura and Jamf 10.45.1, and there is a solution.

In Jamf Configuration Policies, under Printing, click Allow user to modify printer list, AND Allow printers that connect directly to the user's computer.

After checking those two boxes and making sure the affected computers have picked up the new profiles, the standard and mobile users are now able to add printers.

Is there any other solution for macOS Sonoma version 14.4 and higher?
Since version 14.4. our users get the admin prompt again...
We use the same profile settings, @boblauterbach provided.

Has anyone been able to get this to work on Sonoma 14.4 and higher. We are being asked for admin rights..

I tested the script and the profile posted above by @dsavageED and @boblauterbach 

 and neither option works on my Sonoma 14.4 test Macs.

One note- it's a Configuration Profile- not a Policy.  But it >is< in there- thanks!!

This microsoft guide might work, havent tried yet...
https://learn.microsoft.com/en-us/universal-print/macos/universal-print-macos-guide-remove-admin-requirement?tabs=original#instructions

By default, installing printers on macOS requires users to be administrators. This default is controlled by the policy settings in /etc/cups/cupsd.conf and can be changed.

1. Update the <Limit> directive on line 59 to add CUPS-Add-Modify-Printer. This tag is the default access group with no Require clause, so making this change allows any user to install/delete/modify printers.
2. Update the <Limit> directive on line 75 to remove CUPS-Add-Modify-Printer. This access group requires @system11 permissions, so we want to remove that requirement.

The Jamf Configuration Profile worked for us on Sonoma...

Yep- the Jamf Configuration Profile worked for us on Sonoma...  Create a new Config Profile and edit the printing option...

Oh, and it worked for us on Sonoma.

I have this setup on my system as a configuration profile, however it is still asking for administrators name to allow adding a printer

Weird- you sure it is scoped to your test device?  I had the same issue to solve today and it's working on two machines.  If you can't get it to work, I'd open a support ticket with JAMF

Good Day

I like to try this config on our macbooks: Allow non-administrator users to install printers on macOS | Microsoft Learn

but when you are talking about config profile. Which config profile should it be. When i am trying to paste this config file from microsoft in jamf pro Application & Custom Settings - Upload it seems not to work. Its not a plist. So maybe a dumb question, but how to replace the cupsd.conf on the local system with jamf pro and a configuration profile?

Read to fast the article here the last time. 

Have tried now the CP from Jamf and its working flawless and M1/M2/M3 MacBooks on Sonoma 14.5

Tried Configuration Profile method, but it doesn't work...

Hi there,
Has someone tested the solution from @JBPiper https://learn.microsoft.com/en-us/universal-print/macos/universal-print-macos-guide-remove-admin-requirement?tabs=original#instructions
and can help me here with this. I want try this out but what is the best way to change the settings in the original cupsd.conf?
Are you guys creating completely a new file and replacing it with the original with some script?

Creating a pkg with composer with the changed file?

Or just some script which writes the correct code in the existing cupsd.conf file?

With the configuration profile from jamf i am not sure, how i can proceed and prohibit the installation of printer drivers on a macbook when its connected via airprint. 
This for the reason, i am unsure if the non admin user can update the drivers later or uninstall. And when the drivers are no more compatible with for example the next major upgrade for macos i need to react. This is not what we want.