Hello Louis,
Am 08.04.2014 08:46, schrieb L.P.H. van Belle:> but im seeing messages like.
>
> [2014/04/08 08:39:29.804575, 0]
../source3/rpc_server/rpc_ep_register.c:136(rpc_ep_register_loop)
> Failed to register endpoint 'spoolss'!
>
>
> [2014/04/07 16:52:12.100752, 0]
../source3/printing/nt_printing_ads.c:116(nt_printer_guid_get)
> Failed to get GUID for printer MyTestPrinter
> [2014/04/07 16:52:12.101056, 0]
../source3/rpc_server/spoolss/srv_spoolss_nt.c:4847(_spoolss_GetPrinter)
> _spoolss_GetPrinter: failed to construct printer info level 7 -
WERR_BADFILE
>
> [2014/04/07 16:46:17.540795, 0]
../source3/rpc_server/spoolss/srv_spoolss_nt.c:8302(_spoolss_AddPrinterDriverEx)
> _spoolss_AddPrinterDriverEx: level 8 not yet implemented
Don't worry about them.
> I do need to setup the trusts
>
https://wiki.samba.org/index.php/Samba_as_a_print_server#Setting_up_a_GPO_for_trusting_printer_drivers
If you don't want your users always to accept the warning when
connecting to a printer, you should configure it. :-)
> How mature is this new spoolssd?
> since im reading here :
http://wiki.samba.org/index.php/Samba_as_a_print_server
> Note: Some features of spoolssd were broken before 4.0.17 and 4.1.7.
That's why it is recommended to use at least this versions!
It was planned, that 4.0.17 and 4.1.7 would be released last week.
That's why I already put that versions into to the HowTo. But are
delayed for a few days now.
The reason for at least this versions are, that they will include two
patches for bugs I found:
1. In previous versions you have to configure the endpoint mapper, too.
Otherwise spoolssd wouldn't start. Even if it's not a dependency. (Bug
#10474)
2. But more serious was a bug that prevents uploading and assigning
drivers, when spoolssd was enabled (Bug #10481).
So if you want to use spoolssd, you should wait for the next release or
use the git version.
> and how is the experiance at others with samba and cups printing, with the
new spoolssd.
If you have a large number of printers, spoolssd should be an
improvement. But before the HowTo, there was no documentation, so I
guess nobody used it, even if it's included since 4.0. That's why it may
still contain bugs. But it's easy to disable in the config and then you
are back at the traditional stuff.
It would be nice if more people would try spoolssd and report their
experiences (and possible bugs to get them fixed soon).
Regards,
Marc