Network Printer Not Showing When Installing via Command Line

[krdell]

I am attempting to add a printer via the command line using a batch file as an admin (to eventually deploy via SCCM TS on Win10):

rundll32 printui.dll,PrintUIEntry /in /ga /n"\\my network printer"

The command appears to run successfully but I am not able to find any trace of this printer in my printer list, print management, or in the registry (HKEY_LOCAL_MACHINE → SYSTEM → CurrentControlSet → Control → Print → Printers)

When I attempt to run it a second time I get the error message "Unable to add the per machine printer connection. Another printer or printer share with this name already exists. Please use another name for the printer."

Any ideas? Thanks in advance!

[GarthMJ]

 

I am attempting to add a printer via the command line using a batch file as an admin (to eventually deploy via SCCM TS on Win10):

rundll32 printui.dll,PrintUIEntry /in /ga /n"\\my network printer"

The command appears to run successfully but I am not able to find any trace of this printer in my printer list, print management, or in the registry (HKEY_LOCAL_MACHINE → SYSTEM → CurrentControlSet → Control → Print → Printers)

When I attempt to run it a second time I get the error message "Unable to add the per machine printer connection. Another printer or printer share with this name already exists. Please use another name for the printer."

Any ideas? Thanks in advance!

 

 

Printer are a user setting, not a system setting. TS will run as the local system account, therefore you are adding the printer to the local system account and not the computer itself.

[krdell]

After more troubleshooting I've narrowed it down to this: using script with 2 different printers on 2 diff print servers, I've discovered that this script works for all domain users on windows 7. It works for all domain users on windows 10 when using one printer but not the other.

 

So, it looks like the issue has to do with one particular queue on Windows 10 only but not sure why...doesn't make much sense. Any ideas?

[GarthMJ]

After more troubleshooting I've narrowed it down to this: using script with 2 different printers on 2 diff print servers, I've discovered that this script works for all domain users on windows 7. It works for all domain users on windows 10 when using one printer but not the other.

 

So, it looks like the issue has to do with one particular queue on Windows 10 only but not sure why...doesn't make much sense. Any ideas?

 

How exactly are you deploying this? With what settings?

[krdell]

Right now I am manually applying the script above via batch file for testing purposes. My intention is to deploy it via sccm task sequence as we have done with no problem for years. I am only now having this problem with Windows 10

[GarthMJ]

You should do your testing as CM will deploy it. Therefore once you solve it using the psexec trick, it will work for CM too.

https://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/