https://kb.stonegroup.co.uk/index.php?View=entry&EntryID=619
Најлакши начин да решите проблем није преко ГПО или деинсталирањем несрећног апдејта КБ3170455, већ употребом регистри базе у којој треба да пронађете реч:
PrinterDriverAttributes
а потом да измените кључ у њој на непаран број већи за један од тренутног парног или нуле, то је све, врло једноставно решење проблема.
На кога утиче овај проблем, односно где се јавља и када ?
Јавља се обично на новом Виндовс 10 после најновијих апдејта и несрећног поменутог.
А утиче на кориснике новијих матричних ЕПСОН принтера, на пример: EPSON LX-350.
https://www.reddit.com/r/sysadmin/comments/50gw1b/solved_deploying_nonpackaged_print_drivers_after/
Solved: Deploying Non-Packaged print drivers after KB3170455
Since KB3170455 we need to enable point and print restrictions and specify our print servers in the GPO. For most of our printers there were no issues, however a couple of printers were not being pushed out by Group Policy Prefs since the update, even though the print server was listed in the point and print GPO.
Browsing the print share and trying to connect the printer manually would result in the "Do you trust this printer" pop up which will then prompt for admin creds to install the driver. Looking at Print Management on the server in question shows that the problem printer drivers have a "Packaged" status of false.
Now apparently if you are pushing out printers via GP or GP Prefs and they are of Non-Packaged type you will always get a prompt to install, ignoring the point and print GPO, which will obviously cause the install to fail.
A solution to this is a registry edit on the print server - obviously test this first before putting it into production.
HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\...\Driver name\PrinterDriverAttributes
Change the value from 0 to 1, and reboot the print server.
Back in Print Management you will see the Packaged status is now change to true, and the printer will now deploy.
Obviously if you can find packaged print drivers then use those, but some manufacturers haven't bothered.
EDIT: The value for other print drivers may not be 1, but to make this work the value needs to be set to an odd number.
https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb3163912-breaks-point-and-print-restrictions-gpo-settings?forum=winserverGP
Најлакши начин да решите проблем није преко ГПО или деинсталирањем несрећног апдејта КБ3170455, већ употребом регистри базе у којој треба да пронађете реч:
PrinterDriverAttributes
а потом да измените кључ у њој на непаран број већи за један од тренутног парног или нуле, то је све, врло једноставно решење проблема.
На кога утиче овај проблем, односно где се јавља и када ?
Јавља се обично на новом Виндовс 10 после најновијих апдејта и несрећног поменутог.
А утиче на кориснике новијих матричних ЕПСОН принтера, на пример: EPSON LX-350.
https://www.reddit.com/r/sysadmin/comments/50gw1b/solved_deploying_nonpackaged_print_drivers_after/
Solved: Deploying Non-Packaged print drivers after KB3170455
Since KB3170455 we need to enable point and print restrictions and specify our print servers in the GPO. For most of our printers there were no issues, however a couple of printers were not being pushed out by Group Policy Prefs since the update, even though the print server was listed in the point and print GPO.
Browsing the print share and trying to connect the printer manually would result in the "Do you trust this printer" pop up which will then prompt for admin creds to install the driver. Looking at Print Management on the server in question shows that the problem printer drivers have a "Packaged" status of false.
Now apparently if you are pushing out printers via GP or GP Prefs and they are of Non-Packaged type you will always get a prompt to install, ignoring the point and print GPO, which will obviously cause the install to fail.
A solution to this is a registry edit on the print server - obviously test this first before putting it into production.
HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\...\Driver name\PrinterDriverAttributes
Change the value from 0 to 1, and reboot the print server.
Back in Print Management you will see the Packaged status is now change to true, and the printer will now deploy.
Obviously if you can find packaged print drivers then use those, but some manufacturers haven't bothered.
EDIT: The value for other print drivers may not be 1, but to make this work the value needs to be set to an odd number.
https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb3163912-breaks-point-and-print-restrictions-gpo-settings?forum=winserverGP
No comments:
Post a Comment
Beogradsko programiranje=