search for: printerdriverattributes

...Samba does not support this(?). For Windows Print Servers there is a workaround[1] around where you can "trick" the print server with a "regular" print driver and making the reg. key HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windows x64\Drivers\...\Driver name\PrinterDriverAttributes odd. When you apply this registry hack the Windows Print Server daemon will package the driver by itself into a single CAB file - this is probably what they call the "Packaged Driver" - and then Printer Deployment actually works. This is what happens on a Windows Print Server now whe...

...?). > > For Windows Print Servers there is a workaround[1] around where you > can "trick" the print server with a "regular" print driver and making > the reg. key > HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windows > x64\Drivers\...\Driver name\PrinterDriverAttributes odd. > > When you apply this registry hack the Windows Print Server daemon will > package the driver by itself into a single CAB file - this is probably > what they call the "Packaged Driver" - and then Printer Deployment > actually works. > > This is what happens...

...= "" Valuename = Print Processor Type = REG_SZ Value = "" Valuename = VendorSetup Type = REG_SZ Value = "" Valuename = Color Profiles Type = REG_MULTI_SZ Valuename = InfPath Type = REG_SZ Value = "" Valuename = PrinterDriverAttributes Type = REG_DWORD Value = 0 Valuename = CoreDependencies Type = REG_MULTI_SZ Valuename = MinInboxDriverVerDate Type = REG_SZ Value = "01/01/1601" Valuename = MinInboxDriverVerVersion Type = REG_SZ Value = "0.0.0.0" Thanks -- -------...

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,