Click to select the Define these policy settings check box, and then click Add User or Group to add the Power Users domain group.Locate and then double-click Load and unload device drivers.In Group Policy Object Editor, locate and then click the Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment folder.Click the Group Policy tab, click the GPO that you want to modify, and then click Edit.In the navigation pane, right-click your domain name, and then click Properties.Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.Configure the Load and unload device drivers policy setting for the Power Users group.To do this, use one of the following methods. To resolve this issue, modify the Group Policy settings for the Group Policy object (GPO) that has printer policies defined for the domain users on the domain controller. Print a test page from the printer as a standalone to check if it prints fine before troubleshooting the issue further. Please ensure the printer is working as a copier, While you respond to that, here's a few things to do: Have you followed all the links mentioned in the same thread by the other experts? (Ensure you do not share any of your personal information such as serial, phone number, email ID, etc.). What is the product number of your device? Use this link to find it:
Thank you for posting your query, I'll be more than glad to help you outĪs I understand you are not able to connect to your printer due to the error message,ĭon't worry as I'll be glad to help, however, to provide an accurate resolution, I need a few more details: This is a great place to get support, find answers and tips, Microsoft's security bulliten about the update:Ī helpful thread on Reddit which also addresses this to HP Forums, My own post about the issue, describing the problems I was having in detail: But even still, it's good to finally know what the root cause of this issue actually is. I'll have to play around a little, though, even now that I know that this problem was caused by a security update, because the vulnerabilities this update intends to address are certainly valid - and, my network being that of a public school district, it's certainly always "at risk" for attacks from students who would like to test their "hacking" abilities. I have been looking for a fix for this issue for over a month, and could hardly find any info which seemed relevant to the situation.
0 kommentar(er)
