Jump to content

Recommended Posts

Posted

would have thought using GPO would have been easier?

used it for manual rollouts when i was updated rooms which were not gpo applied so to speak.

i used this:

rundll32 printui.dll PrintUIEntry /dl /n "printername" /c\\pc-name

rundll32 printui.dll PrintUIEntry /dd /m "Kyocera FS-3920DN KX" /c\\pc-name

rundll32 printui.dll PrintUIEntry /dd /m "Kyocera FS-3920DN KX" /c\\pc-name

rundll32 printui.dll PrintUIEntry /if /F "R:\knew\OEMSETUP.inf" /b "a14-fs3920" /r "\\servername\pcname" /m "Kyocera FS-3920DN KX" /c\\pc-name

 

this was removing a couple of old drivers as well so the /if /F line is actually installing a new printer dont see why you couldint drop this into a login script tho i have never used it like that

  • Thanks 1
Posted
would have thought using GPO would have been easier?

 

Have heard stories of printers not mapping when using gpo and GPP.

May have to look into it.

Posted

ive heard that as well, however having used it myself it does work well and saves aggro from a managment point of view.

people who have had the problems end up removing and then readding the printer as part of the policy but ive never found a problem with it

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...