Most printers won’t require a certificate. Let’s dive in… Import Certificateįirst thing’s first: certificates.
I’ve found this method to execute correctly even as SYSTEM user, so it’s what I’m still using for my printer installs today. My latest method involves using PRINTUI.DLL with RUNDL元2.EXE which are also native Windows tools. SYSTEM is fine for most executions, but some of the aforementioned visual basic scripts will not complete when ran as the SYSTEM user ( see post Run Command Prompt as NT AUTHORITY\SYSTEM to test SCCM Applications to learn how to test such things). When installing applications for the entire system (all users), SCCM will run installs as the Windows built-in SYSTEM user. My current issue with these is a result of my use of System Center Configuration Manager. I was previously a fan of the prndrvr.vbs, prnmngr.vbs, and prncnfg.vbs scripts that have existed natively in Windows for many years. I’ve used several methods to accomplish this.
Installing printers from Windows command line can be tricky, especially if you are attempting to keep things silent. Successfully Tested On: Windows 7 Enterprise SP1, Windows 10 Enterprise versions 1507 - 22H1, Windows 10 Long-Term Servicing Branch (LTSB) versions 1507 & 1607, Windows 10 Long-Term Servicing Channel (LTSC) versions 2015 - 2019, Windows 11 version 22H1
0 kommentar(er)
