It seems that printers are here to stay for a long time. You will have to suffer the irritating burden of frequent attendant jams, empty trays, and incessant thirst for toner and ink. However, if you are using Windows 8, then Windows 8 drivers offer some amazing assistance in configuring and managing these contraptions. This assistance is in the form of 13 PowerShell cmdlets.
Among the many new PowerShell nouns which are now used, are printerdriver, printjob and printer, amongst Windows 8 and Windows Server 2012. For connecting the printer to a PC, you require either a cable, probably USB or a network connection, between the two devices, and a printer driver. Actually, printer drivers enable the creation of printers (the software object type), and then printers create print jobs, and the print jobs then create the desired print output.
To manage Print drivers
Initially, you require managing printer drivers just the way you do the other Windows 8 drivers, Power Shell’s get-printerdriver, add-printerdriver, get-printerdriver, and remove-printerdriver can do that. For doing this you require local administrative powers for adding or removing printer drivers with these cmdlets.
A driver name should exactly match a known driver; otherwise, you will certainly get errors .It is possible to uncover a driver’s “magic name” quite easily either by typing get-printerdriver on a PC that already has that driver loaded, or going inside the .inf file associated with any printer driver. When you browse for the file, you would see some code written as below:
;
; Model sections.
[DELL]
"Dell Color Laser 1320c" = DLHSNZP1,LPTENUM\DellColor_Laser_132010D5
"Dell Color Laser 1320c" = DLHSNZP1,USBPRINT\DellColor_Laser_132010D5
This goes on a bit longer, but you can then see that there is a string after the vendor name, and this is most of the time the “magic name” for the driver.
Another feature is Add-printerdriver. As per the documentation, you can load a driver that is not already there in your computer system driver store with the -infpath option:
add-printerdriver -name "Waxtronic 320" -infpath "c:\drivers\waxtronic\wi949.inf"
However, the world’s largest software maker is so sure of this capability that the –infpath option and the driver name are built in as positional parameters, allowing you to enter the above code as: add-printerdriver "Waxtronic 320" "c:\drivers\waxtronic\wi949.inf"
The problem is, neither formulation seems to work. However, the much older Pnputil command seems to work. This provides wonderful driver management help, including the ability to install any given driver. Here is the command:
pnputil –i –a "c:\drivers]waxtronic\wi949.inf" (c drive or whichever drive your OS is installed.)
That was some information on managing the printer drivers in your system. For further assistance, get in touch with our support team.
Among the many new PowerShell nouns which are now used, are printerdriver, printjob and printer, amongst Windows 8 and Windows Server 2012. For connecting the printer to a PC, you require either a cable, probably USB or a network connection, between the two devices, and a printer driver. Actually, printer drivers enable the creation of printers (the software object type), and then printers create print jobs, and the print jobs then create the desired print output.
To manage Print drivers
Initially, you require managing printer drivers just the way you do the other Windows 8 drivers, Power Shell’s get-printerdriver, add-printerdriver, get-printerdriver, and remove-printerdriver can do that. For doing this you require local administrative powers for adding or removing printer drivers with these cmdlets.
A driver name should exactly match a known driver; otherwise, you will certainly get errors .It is possible to uncover a driver’s “magic name” quite easily either by typing get-printerdriver on a PC that already has that driver loaded, or going inside the .inf file associated with any printer driver. When you browse for the file, you would see some code written as below:
;
; Model sections.
[DELL]
"Dell Color Laser 1320c" = DLHSNZP1,LPTENUM\DellColor_Laser_132010D5
"Dell Color Laser 1320c" = DLHSNZP1,USBPRINT\DellColor_Laser_132010D5
This goes on a bit longer, but you can then see that there is a string after the vendor name, and this is most of the time the “magic name” for the driver.
Another feature is Add-printerdriver. As per the documentation, you can load a driver that is not already there in your computer system driver store with the -infpath option:
add-printerdriver -name "Waxtronic 320" -infpath "c:\drivers\waxtronic\wi949.inf"
However, the world’s largest software maker is so sure of this capability that the –infpath option and the driver name are built in as positional parameters, allowing you to enter the above code as: add-printerdriver "Waxtronic 320" "c:\drivers\waxtronic\wi949.inf"
The problem is, neither formulation seems to work. However, the much older Pnputil command seems to work. This provides wonderful driver management help, including the ability to install any given driver. Here is the command:
pnputil –i –a "c:\drivers]waxtronic\wi949.inf" (c drive or whichever drive your OS is installed.)
That was some information on managing the printer drivers in your system. For further assistance, get in touch with our support team.
No comments:
Post a Comment