Adminstudio device driver wizard

Click Here to learn more about how we use cookies. Robin Level 3. Printers and MSI Hi has someone created a MSI including printer's driver to deploy printers? All information about the printers deployment from MSI created by adminstudio are welcome Best regards. All forum topics Previous Topic Next Topic. Neeru Level 4. No, you shouldn't need to write a custom action, the Device Driver Wizard will incorporate the DIFx merge module into your package.

The merge module already contains the necessary custom actions. You don't have to write any custom action.. Everything is automated in Device Driver Wizard Just select.

Sign up today to participate, stay informed, earn points and establish a reputation for yourself! Log in. My doubt is that do we need to write any custom action for this? Asked 9 years ago views. Prevents you from capturing Repackager files —By repackaging on a clean system, you are ensuring that you do not inadvertently capture Repackager files during repackaging.

Ensures that you capture all of the necessary setup files —If you do not repackage on a clean system, you may not capture all of the necessary files for the setup because the files may already be installed on the system. Launch Repackager Remotely —You could install Repackager on a shared network drive and then launch Repackager remotely from the clean machine.

See Launching Repackager Remotely. Install Repackager on clean machine —You could install a copy of Repackager onto the clean machine. While it is preferable to launch Repackager remotely from the clean machine, if you do not have network access to an installation of the AdminStudio client tools, this is your best option.

See Installing Repackager on a Clean Machine. If you make changes to a Windows Installer package, vendors will no longer provide support for that product. If you repackage a Windows Installer package, the component codes within the package are not retained and hence future patching or upgrades will not work. Traditionally, repackaging tools will ignore the Windows Installer-specific data in the Registry.

This will result in an incomplete package.