search for: packageaware

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] > PackageAware=TRUE > CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} > > in the OEMSETUP.inf file. > > But editing the file invalidates signing. >...

...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] >> PackageAware=TRUE >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} >> >> in the OEMSETUP.inf file. >> >> But editin...

Hi Louis, thank you for your answer. - the link was already there - I followed this hints: https://lists.samba.org/archive/samba/2016-November/204773.html did the chmod 2775 administrator is part of the PrintOperatorGroup net rpc rights list privileges SePrintOperatorPrivilege -U "H955\administrator" getfacl printerdrivers # file: printerdrivers # owner: root # group:

...d it, but this is what we are hitting again. /snap <InfPath>c:\samsunguniversalprintdriver3\printer\upd\us013.inf</InfPath> <DriverName>-</DriverName> <InstallSection>-</InstallSection> <ProcessorArchitecture>Windows x64</ProcessorArchitecture> <PackageAware>Not package aware</PackageAware> <CoreDriverDependencies>-</CoreDriverDependencies> <LastError>0x12</LastError> <HResult>0x80070032</HResult> /snap Sofar, Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Bernhard Dick [mailto:bernhard...

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 schrieb Franz Gansberg...

...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] >> PackageAware=TRUE >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} >> >> in the OEMSETUP.inf file. >> >> But editin...

...n 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] > >> PackageAware=TRUE > >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} > >> > >> in the OEMSETUP.inf...

...;> > 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] >> >> PackageAware=TRUE >> >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} >> >> >>...

...r 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] > >> PackageAware=TRUE > >> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1} > >> > >> in the OEMSETUP.inf...

...6.2.1 . ( 6.0.0 was on all my pc’s already by image, updating to 6.2.1 ) 2 tests, clean pc, without drivers and test with one as imaged. The HP park tools have admx templates to managing the driver settings, use that. If possible use package-aware drivers. Search in the .INF for lines like :  PackageAware=TRUE       Some info: - DriverIsolation : https://msdn.microsoft.com/en-us/library/windows/hardware/ff560836(v=vs.85).aspx - Packaged Driver : https://msdn.microsoft.com/en-us/library/windows/hardware/ff561043(v=vs.85).aspx ‘ - ( new polices for win10 1607 found here: https://www.microsof...

...6.2.1 . ( 6.0.0 was on all my pc’s already by image, updating to 6.2.1 ) 2 tests, clean pc, without drivers and test with one as imaged. The HP park tools have admx templates to managing the driver settings, use that. If possible use package-aware drivers. Search in the .INF for lines like :  PackageAware=TRUE       Some info: - DriverIsolation : https://msdn.microsoft.com/en-us/library/windows/hardware/ff560836(v=vs.85).aspx - Packaged Driver : https://msdn.microsoft.com/en-us/library/windows/hardware/ff561043(v=vs.85).aspx ‘ - ( new polices for win10 1607 found here: https://www.microsof...

Hi all. I have read carefully all your posts and I am glad to see that some of you workaround this new MS surprise... To solve the problem, I understand that : * if you use the "AD way of deploying printers", the workaround is to use the "Computer ConfigurationPoliciesAdministrative TemplatesPrintersOverride Print Driver Compatibility Execution Setting Reported By Print