What is the easiest way to allow normal users to install printers (which are available through a Samba server)? Normally, Windows 2000 and XP need to have a printer installed by the admin first on a given workstation - only the it can be used by the user. I want to allow the user to install own printers. Now, when one trises to right click on a printer on a server and "connect", he is refused to use it (not sufficient privileges). How can I allow non-admin users to install printers? -- Tomek http://wpkg.org
Fabio schrieb:> Users must have SePrintOperatorPrivilege domain right and must be local > machine administrator, I think.Thats the point of my question - how to allow them to install printers without them being administrators. -- Tomasz Chmielewski http://wpkg.org
Hi, I think that if the printer driver is provided with windows or has already been downloaded, there is no need for the user to be local admin. Which means, that you must load the drivers by installing the printer either as local or domain admin, so that when you loggof and another not_local_admin user logs on, the drivers have already been added. I'm afraid that if you update the server drivers, the client won't be able to update them unless you login again as local admin. Hope this helps, Bruno Guerreiro> -----Original Message----- > From: Tomasz Chmielewski [mailto:mangoo@wpkg.org] > Sent: segunda-feira, 9 de Janeiro de 2006 14:12 > To: Fabio; samba > Subject: Re: [Samba] allowing users to install printers > > Fabio schrieb: > > Users must have SePrintOperatorPrivilege domain right and must be > > local machine administrator, I think. > > Thats the point of my question - how to allow them to install > printers without them being administrators. > > > -- > Tomasz Chmielewski > http://wpkg.org > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >
> What is the easiest way to allow normal users to install printersThis isn't really a Samba issue, but a quick Google brought this up: http://www.tech-geeks.org/geeklog/article.php?story=20040123025824412 Cheers, Adam.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tomasz Chmielewski wrote:> What is the easiest way to allow normal users to install > printers (which are available through a Samba server)?There's an XP policy that will allow Users to connect to printers and have the driver installed automatically. Run gpedit.msc on an XP client and you'll see what I mean. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDxYeEIR7qMdg1EfYRAh+RAJ9s5TkRxUQL95Y40aEMY16xqKerFwCeM2Cv Ayse4t3KL/FVVznI4ytx96c=FsSI -----END PGP SIGNATURE-----
> It's not very handy to do so with Samba and 100 clients if you know > what I mean... > > Perhaps some registry entry that can be added in a script?I thought the idea with group policies was that you apply the policy once, and it takes effect on a whole group of machines. If your XP machines are set up properly, you should just be able to apply that policy to all 100 of them in one go. Cheers, Adam. -- I don't recall if the OP said if he had a win PDC or ads or samba pdc. But the full power of group policy is only available to those with a windows domain. JHT mentions this in the happy users chapter of SBE. You can set up a local policy on the machine before deployment as he shows.... Or there are external packages that can do this for you on a samba controlled domain. Tony Earnshaw used to be *quite vocal* ;-) on this list about one of them (Nitrobit?) from memory. You could search for his name and the words group policy in Google..... It may bring you some joy.... Never used it myself. Regards Geoff Scott
Mario Gzuk schrieb:> Am Donnerstag, den 12.01.2006, 09:20 +0100 schrieb Tomasz Chmielewski: > >>Mario Gzuk schrieb: >> >>>Hi, >>>but please dont forget you overwrite all other user-policy settings with >>>this. The system32\grouppolicy\blablaba is the rusult set of your >>>changes through gpedit. So if you have made changes before the file >>>exists. If you overwrite the policy.pol all changes you made before are >>>lost after next reboot (or 20 min I think. thats the standard time >>>windows reload the group policys...) >> >>yeah I know, it just happened I never used it on the clients (as it's >>really hard to do so with Samba). >> >>A way to "merge" the existing policy.pol files would be good to know of >>course :) >>, > > > Just take a look at poledit (no that is not a language joke, there are > no versions of engedit, geredit or something like that.....).I just checked and poledit can't edit .pol files (taken from system32\grouppolicy\blablaba). -- Tomasz Chmielewski http://wpkg.org