Packaging a PCL 6 Driver Removal
First and foremost, hello everyone! I am new to the boards and looking to endulge in the plethera of knowledge you all have available.
I have performed a search and have yet to yield any results in regards to the issue i have at hand. Through out our enterprise we use a wide variety of applications, we also use alot of citrix. The applications that we have published through citrix HATE any PCL 6 drivers that may be installed. What i am looking to do using Enteo is package up an uninstaller for any PCL 6 driver that may be on that box. Probably an eScript package. We definately have to keep in mind, that if the driver is in fact in use, how will it uninstall? Has anyone run into an issue like this, does anyone have any input in regards to this?
I would greatly appreciate the assistance.
I have performed a search and have yet to yield any results in regards to the issue i have at hand. Through out our enterprise we use a wide variety of applications, we also use alot of citrix. The applications that we have published through citrix HATE any PCL 6 drivers that may be installed. What i am looking to do using Enteo is package up an uninstaller for any PCL 6 driver that may be on that box. Probably an eScript package. We definately have to keep in mind, that if the driver is in fact in use, how will it uninstall? Has anyone run into an issue like this, does anyone have any input in regards to this?
I would greatly appreciate the assistance.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
joedown
14 years ago
You might want to look at using a script to do this. There are tons of scripts and info out there for installing and uninstalling printers and drivers. An msi does not have any native ability to uninstall all PCL6 drivers on a PC. Rather you will probably need to create a custom action that would run a script to do the uninstall. This might get you some more answers now.
Posted by:
anonymous_9363
14 years ago
One of the XP SPs installed a bunch of print control scripts:
prncnfg.vbs
prndrvr.vbs
prnjobs.vbs
prnmngr.vbs
prnport.vbs
prnqctl.vbs
Check these out. Once you have the command line syntax down, run the relevant script as a Custom Action in the Execute Deferred sequence. Remember to condition the CA with REMOVE~="ALL" so that it only runs on uninstallation.
prncnfg.vbs
prndrvr.vbs
prnjobs.vbs
prnmngr.vbs
prnport.vbs
prnqctl.vbs
Check these out. Once you have the command line syntax down, run the relevant script as a Custom Action in the Execute Deferred sequence. Remember to condition the CA with REMOVE~="ALL" so that it only runs on uninstallation.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.