Windows 10: Network Printer Not Showing When Installing via Command Line

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!

:)

 

Computer settings to allow printing using either wireless or USB for a HP 8620 printer

Using Windows 10. Printer works when connected via USB but need to enable 'network' access to print via wireless

Printer shows wireless connection and both computer/printer have same wireless connection

 

hp photosmart c8180 printer .

Installed window 10 now my printer shows as off line, not true. I am on a wireless network and when i run trouble shoot and fix , I get and error message 0x803c010b. Any solutions?

 

Go here and look at this page. It tells you how to do it via the .vbs scripts that are provided by Microsoft. I have never gotten the RUNDll32 option to work in Windows 7. What I normally do for printer installs is install all the printers that your organization/workgroup on one workstation until they are all installed they you want them to do and they all work. Then I start the program "printbrmui.exe" (Run it as an Administrator...even if you are logged in as an administrator). Then export all the printers to a file. Then goto the next workstation and then run an import (you can do this via Remote Desktop too). Anyway, hope this helps.

 

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?

I'll try your method as well. Thanks