Scripting

Hi,

I would actually recommend to not sequence it all. What you say makes it sound easy, but it's really not. Even though it is technically possible doesn't make it a good decision to actually do it this way. In my opinion it's best to stick with the Adobe Customization Wizard for this product.

This is not meant in a bad way, but if you don't know what to look for in the vendor MSI this is definately not the right package to start with. You'll run into a lot more complications than simply extacting some driver files.

Hi Rheuvel,

Thanks for the response. I am also same impression not to sequence Printer drivers applications. Will check with my company.

Normally the printer drivers goes in the location C:\WINDOWS\System32\spool\drivers\w32x86 and C:\WINDOWS\System32\spool\drivers\w32x86\3 for x86 based system. You can check before installation and after installation screenshot , this will let you know which files are there.Also pay attention to hklm\system\currentcontrolset\control\print\printers hive..

if you need a printer to always be available then virtualising isnt the way forward. equally appv doesnt work well with print drivers or drivers in general. so as the dudes above said it's not a good app to virtualise.

I know this coz i had the same problem previously;) Good luck

Take the challenge:
Quick guide:
1. Package the drivers utilising the Diffx mergemodule for printer driver installation to create the msi
2. Virtualise the main application (make sure driver is installed before monitoring starts)
3. Choose how to install the driver; either install msi or call the install from the osd via a Prelaunch script
test then test again. Once you are happy "TEST" again

And yes it Psssssss me off people saying just because it has drivers you cant sequence. With a combination of packaging technologies anything can be packaged for the corporate enviroment.

Well, I agree that with the right combination of technologies you can "sequence" an application with, but I would not do it for Adobe products. That to me sounds like re-inventing the wheel. The reason for not virtualizing printer drivers is that the PC used to sequence might give the "printer" Device_ID 0, if it has no printers installed, but once you deploy, this will replace any printer with the same device number in the client computers. The best practice IS to sequence the app, and install printer drivers separately. This does not mean, you have to do it manually, you can create an MSI and use it as a dependency when deploying the app.

ORIGINAL: Rheuvel

Hi,

I would actually recommend to not sequence it all. What you say makes it sound easy, but it's really not. Even though it is technically possible doesn't make it a good decision to actually do it this way. In my opinion it's best to stick with the Adobe Customization Wizard for this product.

This is not meant in a bad way, but if you don't know what to look for in the vendor MSI this is definately not the right package to start with. You'll run into a lot more complications than simply extacting some driver files.


Great response. simple yet so practical. I've ran into the same dilemma but now I know what to do. Thanks for the advice.

i have the same problem, i have sequenced adobe acrobat X pro, when i click create pdf and i browse doc file it gives error saying unable to find Adobe PDF resources repair adobe acrobat..

But i create pdf out of text file it works fine. The problem is just while creating PDF from doc files.

Ny help on dis??