similar to: unable to upload printer driver

Please ignore the recommendation, such an driver can not be assigned to an printer. Am 06.06.2017 um 14:54 schrieb Achim Gottinger via samba: > I can install Kyocera Universal KPDL drivers once i delete the sections: > > [PrinterPackageInstallation.x86] > PackageAware=TRUE > CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} > > [PrinterPackageInstallation.amd64]

Hi Achim, thank you for your effort! I did a couple of tests, from W8.1 with x64 driver which where rather old and therefore disignated for W7x64. But this went stale as well. Therefore I'll give it a try by using a W7-WS for uploading the drivers. Franz >>> Achim Gottinger <achim at ag-web.biz> 06.06.2017 15:27 >>> Hmm after another try an windows 7 client 32 and

I can install Kyocera Universal KPDL drivers once i delete the sections: [PrinterPackageInstallation.x86] PackageAware=TRUE CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} [PrinterPackageInstallation.amd64] PackageAware=TRUE CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} in the OEMSETUP.inf file. But editing the file invalidates signing. Am 06.06.2017 um 12:59

Hmm after another try an windows 7 client 32 and 64 bit can install such an driver now. Sorry for the noise. :-) Am 06.06.2017 um 15:10 schrieb Achim Gottinger via samba: > Please ignore the recommendation, such an driver can not be assigned > to an printer. > > Am 06.06.2017 um 14:54 schrieb Achim Gottinger via samba: >> I can install Kyocera Universal KPDL drivers once i

Hello Franz, Out of curisoity I tried to install the old Kyocera Universal drivers we use since a few years on an other samba server (4.6.5). Found the old version here https://www.rz.uni-osnabrueck.de/fileadmin/user_upload/Campuscard/Drucken/Treiber/win8/KyoceraClassicUniversalDriversCertified130315.zip. It also fails now and the OEMSETUP.INF file also contains an

In an AD environment one may also sign an modified driver package https://technet.microsoft.com/en-us/library/eb9b35a3-64e9-4cd4-8393-9d8f5966f9c2 and deploy the certificate via an GPO https://technet.microsoft.com/de-de/library/cc770315(v=ws.10).aspx Am 07.06.2017 um 14:48 schrieb Achim Gottinger via samba: > Hello Franz, > > Out of curisoity I tried to install the old Kyocera

Waarschuwing: Er zijn 1 of meer bijlagen uit dit bericht verwijderd Waarschuwing: (KyUHCa.chm, KyUHlp.chm, KyUHPt.chm, KyUHDe.chm, KyUHFr.chm, KyUSNM.exe, KyUHSe.chm, KyoClassicUniversalPCL5_v3.0_Samba_WHQL.zip, KyUHSp.chm). Waarschuwing: Lees de "Bazuin-en-Partners-Attachment-Warning.txt" bijlage voor meer informatie. Hai Franz and Achmin. Attached in this mail is a driver made by

Hi, I'm currently working on evalutating a AD-Domain for my Department. Since I have a couple of year experince in running a NT-Style Domain, my choice is samba - nowadays AD-DS. Now I'm stuck, and I would really appreciate some more thoughts and a push in the right direction. :-) Thank your in advance Franz The facts: A quick test installation is working as expected - Debian Jessie,

> Op 1 jun. 2017 om 15:20 heeft Franz Gansberger via samba <samba at lists.samba.org> het volgende geschreven: > > Hi all, > > according to this thread, I ran into the same situation: > > [2017/06/01 10:35:46.909754, 0] ../source3/rpc_server/spoolss/srv_spoolss_nt.c:8476(_spoolss_AddPrinterDriverEx) > _spoolss_AddPrinterDriverEx: level 8 not yet implemented >

On Fri, 19 May 2017 11:49:26 +0200 Franz Gansberger via samba <samba at lists.samba.org> wrote: > Hi, > I'm currently working on evalutating a AD-Domain for my Department. > Since I have a couple of year experince in running a NT-Style Domain, > my choice is samba - nowadays AD-DS. > > Now I'm stuck, and I would really appreciate some more thoughts and a > push

Hi everybody! I've got a problem with downloading printerdrivers from my win2k box. Successfully added printer with cupsaddsmb-tool (as root, after failing as printer admin!!?!?!). The W32X86 and WIN40 directories have been created as they should and also did the PPD files. But if I connect to the printer from Win (as printer admin) I get the message that no driver could be found. RPCclient

hi everybody, after some trouble i an know able to upload and set printerdrivers via cupsaddsmb and windows apw. but there are two errors. - i cant use the driver on a windows xp 32, if does not get installed as root previously. - i have a Oki Execution series 7411 and used the PS Driver. when printing to that printer i get in smb.log Unable to print file to es7411 -

Hello list, I upgraded from Samba3.0.1 to Samba3.0.2rc1 and got now following problems: LaserJet printers 6MP (sorry, we have no other LaserJet printermodels) now couse the application to crash. With Samba3.0.1 there was no probem with that kind of Printers. I use the RPM's from ftp.sernet.de for SLES8. Printingsystem is CUPS, with raw printing and serverbased printerdrivers. Has anyone

Hello, been googling this for a while. Read GD's presentation on why printing is such a pain... Anyway, I'm using 3.4.8 on Freebsd 8.1 I've tried a few combinations - best luck is with 3.2.5, but I'd like to move forward a bit. So, I've got the ADS part working pretty good. happy with how that's going. my problem is when I attempt to load printer drivers.

Hello, Does anyone have done a setup of the samba server in such way that the user on a Windows NT4 client must enter his/her username/password to use a printer service ? Is that possible? I manage to have this working with Win95 with the option public=no but it does not seems to work for NT. The goal is to have a control of the printer usage. (accounting) I'm controlling the samba servers

Hi, i learned a lot about cups, samba and printerdrivers the last few days and hours. I found a lot of mistakes but i can't change the following situation: I CAN NOT delete printjobs! I can connect to the printers, automatic download the driver, print, stop the printer, start the printer. Any tips, links, hints would be nice. My setup: Debian Sarge - Samba 3.0.14a - Cups 1.1.23. nss_ldap

Hello, I have set up a Samba printserver at a school. The server is a standalone server, connected to no domain. I have installed printers with Cups, and uploaded Windows printerdrivers to the shared driver folder. I can add the shared printers in a Windows 10 Pro client, without any hassle. When I try the same in any Win 10 Home edition, I get Windows error messages like "error

Hi, Our Samba/CUPS based printserver loses the info of which driver belongs to a certain printer. The server is running Samba 3.2.7 on Solaris 9. Out of the blue, users complain they cannot print. Looking at 'printers and faxes' from a Windows machine shows no info in the 'Model' field. In normal situations this field lists the driver/model name. Weird thing is: nobody is

Hello, I want to know at which time the tdb-File of a printer located at /var/lib/samba/printing will be updated? I have my printerdrivers! After this I looked at the directory and the files untouched. I have done some changes with the windows panels, but there are no changes of the timestamps? How does it work? regards Franz

Hello, i use Serverside printerdrivers, and since 2.2.5 it seems to work well, but on problem remains: I installed a driver for the HP 750 Designjet with cupsaddsmb. This drivers works well, but only up to A2. The Printer Properties don't let me choose larger paper sizes than A2 (I need definitly A1 and A0 ). I tried to create new forms trough server properties, but it does not work. Is