![]() ![]() Microsoft has privately acknowledged in a support case that “the admin/install prompt for already-installed drivers and already-installed printers is unexpected behavior.” It went on to say, “We have received new reports that this is also affecting customers where the drivers/printers, etc. Getting to the heart of the print problem Reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint" /v RestrictDriverInstallationToAdministrators /t REG_DWORD /d 0 /fīut doing so exposes you to publicly known vulnerabilities, and neither Microsoft nor I recommend it. Those who do want to make the registry change can open a Command Prompt window with elevated permissions and enter the following: Given that firms are likely to keep users without administrator rights to limit lateral movement (and quite frankly because Microsoft has told us over the years that running with administrator rights was a bad thing), we’re now having to decide to give users local administrator rights, make a registry key adjustment that weakens security, or roll back the patch until Microsoft figures out what went wrong. We’re also seeing that when the patch is on the workstation and not on the server, it’s triggering a reinstallation of the print drivers. More precisely, when the print server is on a Server 2016 server, the printers are pushed out via Group Policy, and the printer driver from the vendor is a V3 driver, it is triggering the reinstallation of print drivers. However, what we’re seeing over on the list is that anyone with a V3 style of print driver is having their users be prompted to reinstall drivers or install new drivers. Update existing printer drivers using drivers from remote computer or server”. ![]() Install new printers using drivers on a remote computer or server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |