samba - Feb 2023 - Unable to add Point and Print printers to clients with Windows 8.1 and up

Hi Thomas

Am 27.02.23 um 23:10 schrieb Thomas Keppler:
> Hi Stefan,
> 
> thanks for the idea! Indeed, I didn't have the third GPO[1] of the
bunch, just the two present in the Samba Wiki.
> However, applying the third to the client doesn't change the situation.
> 
> I've also resorted to use a Domain Admin and Local Admin account to
conduct these tests to rule out any permission problems in the first place.
> 
Did you "disable" the the GPO! Normaly you set GPOs to
"enable" to set
what the GPO should do, here it must be "disabled" What I also
noticed,
not all printer drivers are working :-( When I set up a prnit server in 
my classes I only uses a PCL6 driver. I know that it's nearly impossible 
to get Lexmark printers working. So maybe you try a standard driver to 
see if the problem is the driver and not your settings. I did a tutorial 
on 2021 SambaXP about printserver setup
https://www.kania-online.de/veroeffentlichungen/
search for SambaXP 2021
There you can download my Vagrant setup and the driver I'm using is also 
included. But it was before printnightmare so the GPO no.3 is not there, 
but everything else works, just add the third GPO

> --
> Sincerely
> Thomas Keppler
> 
> --
> [1] HKLM\Software\Policies\Microsoft\Windows
NT\Printers\PointAndPrint\RestrictDriverInstallationToAdministrators = 0
> 
> P.S. This is a double post to Stefan, I've missed to reply to the
mailing list as well in my original reply... Sorry for the noise.
>

Hi all,

thank you Stefan for your suggestions. At least the idea with trying a different
driver for once seems to have lead me somewhere!
> On 28. Feb 2023, at 09:04, Stefan Kania via samba <samba at
lists.samba.org> wrote:
> Did you "disable" the the GPO! Normaly you set GPOs to
"enable" to set what the GPO should do, here it must be
"disabled"
Yep, that's what I did. I did so by setting the value in the Registry
myself, just to be extra 100% sure it is what it should be per the article.
Even though it shouldn't make any difference as per my last email -- I was
working as a Domain and Local Admin the entire time on purpose to rule this kind
of stuff out.
> So maybe you try a standard driver to see if the problem is the driver and
not your settings.

This seems to have hit it on the head. When I use one of the Brother or HP
drivers inside your bundle, everything works again like nothing was ever
wrong...
Matter of fact: It really just works with either driver and really just
doesn't with the Sharp one. Like for the other person asking on the mailing
list in 2021.

What I find a little suspicious: For any driver I have provided in the past
(included the Sharp one) it opened a dialog box where it copied the driver onto
the client's disk.
It didn't do that for either driver you provided and said "Downloading
driver..." instead without additional dialog boxes. Now, could this mean it
installed drivers from Windows Update instead? "Downloading" for
"copying over the network" sounds a little dated, even for Microsoft.
Maybe I'm just being too paranoid and grasping at straws... "It's
doing my head in!" :-)

Does the Sharp driver specifically not working narrow it down to some other GPO
and/or setting I can take so that my newer clients will accept it? Keep in mind:
The environment in use right now is using Windows 7 and that continues to work
like a charm - A very insecure, outdated charm, of course. Replacing the MFC
soon is also out of the question.

Any other suggestion?

Thanks for all the help so far.

--
Sincerely
Thomas Keppler