![]() Nothing to stop you from giving it a go though. Varies depending on the printer driver and application software you are using. Mine is boiled down to someone messed up and I needed a way to fix 20 machines in short order. Printing color images using higher print quality settings takes longer. Īlso I should add that I used a variable in the Invoke-Command path, probably to account for spaces in the file path.Įdit 2: Sorry I didn't understand the scope of the original post, my method may not work for your as what i was trying to fix is different from what your issue is. You'll need to install the print driver before hand (edit: do this first if the driver isn't already installed) Invoke-Command Įdit: I just read /u/Nemergal's comment, and thought I should add, that I don't know if it will change on the fly if a user is logged in, I tend to reboot the machine after I run any type of script because. I just did this the other week and can't find my command but I think it was something like this Set-Printer -Name -DriverName If I run the script as an admin it appears that it cannot see the printer when run in that context. I wrote a little script that would delete and reconnect the printer, however, it seems you cannot delete the printer as a regular user as I get access denied. Has anyone done this before? I'm not sure how to accomplish this. It seems this is part of the updates to try to mitigate/prevent PrintNightmare. I still think a PowerShell script that would update the printer driver would be the best solution for my environment. I wish I could do this via Endpoint Manager but we don't license it currently. Microsoft is saying to just type in the admin credentials, or just include the print drivers in your OS image and never update them, or pay Micro$oft $ to use Endpoint Configuration Manager to push out print drivers, or temporarily set a registry key to 0 so you can update the drivers and then switch it back. Currently, the printer is being pushed out via GPO (Computer > Policies > Printer Connections). It seems this is part of the updates to try to mitigate/prevent PrintNightmare. ![]() ![]() I pushed out the latest cumulative patch for Windows 10 last week and now every computer is requesting admin credentials to update the print driver from the print server.
0 Comments
Leave a Reply. |