What you could do is created a Response Transform, selecting the primary feature and the other feature you want.
That means putting much more of the application local, which can defeat the purpose of sequencing in the first place. In some cases, you may discover that if the driver is not installed by the primary feature, the installer will not allow you to install with only the feature you want, you might have to install with the primary feature AND the driver you want which is useless. In which case, Add a scrip to the MachineScripts of your App-V application Deployment Configuration file to install the driver as above. msiexec /I FoxitPhantomPDF706_Business_enu_Setup.msi ADDLOCAL=FX_Evernote You might be able to just install the MSI with the ADDLOCAL= parameter with the Feature e.g. You can then open the MSI and go to the Feature table and find the name of the feature you want: If you go to the custom setup option during the install, you can usually tell if such an option exists. If you are lucky enough, your application install may have an optional feature in it.
In a few cases, you may notice during an install of a vendor supplied MSI, there may be a feature for the actual driver install, if it’s optional. I’d love if this was the standard but it’s not! If you run the install you may find a Drivers folder or Drivers MSI in the extracted installer under %temp%įor a great example, check out Nicke Kallens great blog post HERE In some glorious cases, vendors actually split out their drivers into separate packages. Like I said in my previous post, vendors are not consistent with how they deliver their applications, so I may not cover absolutely every possibility but these are examples of some that I have. This is really just me relaying my experience in dealing with applications that contain drivers.
0 kommentar(er)
