search for: kb3170455

Am 09.09.2016 um 19:26 schrieb Geert Lorang via samba: > Hi, > > Since recently printer deployment is broken on Windows 7 (and above?) > due to KB3170455. This is probably the same problem > https://lists.samba.org/archive/samba/2016-August/202078.html on Win 10. > > After a lot of reading and investigating it appears that we now (after > KB3170455) need: > > - A Point & Print Restriction GPO enabled with FQDN of all Print &...

Hi, Since recently printer deployment is broken on Windows 7 (and above?) due to KB3170455. This is probably the same problem https://lists.samba.org/archive/samba/2016-August/202078.html on Win 10. After a lot of reading and investigating it appears that we now (after KB3170455) need: - A Point & Print Restriction GPO enabled with FQDN of all Print Servers and "Do not show...

Hi Louis, no all driver work (brother, kyocera, hp) I installed the driver but I get the same message with trust. It seems not work without remove the security patches. When I remove security patches it seems not important which driver are installed. In theory it should work with the driver but it seems not. Greetz, Sven -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at

I run a samba 4.1.17-Debian DC (and secondary, same version) and a print server (same samba version, CUPS 1.7.5). I can log in to the domain from all Linux and Windows machines. I can print through the print server from all Linux and WinXP machines (not member!). I recently have trouble printing from a Win7 Ultimate VM. This may be due to a reboot of the whole cluster after a power fail.

Hi Louis, Hi Achim, on windows 10 i removed the 3176493 which is on windows 7 / 8 3177725. It has no effect on restriction. Its always restricted. Sven -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Achim Gottinger via samba Gesendet: Montag, 15. August 2016 18:39 An: samba at lists.samba.org Betreff: Re: [Samba] Windows 10 point and print

Ok, quick rely, i got a memory freshup.. The samsung driver in the xml, is not package aware. See: KB3170455 (w7) KB3163912 (w10) which is the cause of this problem. Now removing these KB's is not option. So we are back to : https://docs.microsoft.com/en-us/windows-hardware/drivers/print/constructing-a-package-aware-driver-with-updated-core-drivers Read it, but this is what we are hitting again....

...and-Print recent Windows (tested with Windows 10 1607) asks the user to confirm the driver installation. An appropriate Policy [1] is set up so that no user interaction should be required for the driver installation. There are similar reports [2,3] that identify updates KB3163912, KB3172985 and KB3170455 causing these issues. However, Windows 10 1607 seems to ship with these changes. Reports suggest, that a "packaged" driver should be used to allow driver deployment with Point-and-Print. It is not possible to install a "packaged" driver to a Samba server. Although a registry...

Ok you probely have hit : KB3163912 and KB3172985 problems. ( win 10 ) For win 7 you can have trouble due (KB3170455) Some good info here. http://blog.vectranetworks.com/blog/microsoft-windows-printer-wateringhole-attack Here are some tips to fix this also. - Remove the KB ( start with KB3172985) , but thats not my advice. - Setup the point and print restrictions as followed. Computer Configuration > P...

which printer brand/model and which driver? > Op 14 aug. 2016 om 13:25 heeft Vogel, Sven via samba <samba at lists.samba.org> het volgende geschreven: > > Hi, > > it seems there is a problem/bug in windows 10 that point and print restriction dont work and gpo are ignored. I don't know. When I use windows 7 there o problems. technet article they speak about packaged

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,