Exact is one of the few companies that tells you how to virtualize their application. But Exact’s own guide for App-V sequencing is (a bit of) crap. It is really outdated. So I’ve made my own.
First. Install al your prequisites. Install the version of Microsoft Office that is used in production. I’ll presume your using a local installation, because of all the interactions with other programs. Also Exact uses an Excel plugin. If Excel isn’t installed, the plugin wil not be installed either.
We’ll need to Install the Microsoft MSQM Server core as Exact uses this. The Exact installation will install this to, but I don’t want this in the sequence. In my opinion, Windows features belong in the build so they can be patched.
If you sequence on a Windows 7 machine, add the MSMQ in the sequence and use the App-V it on Windows 2008(r2) the MSMQ part doesn’t work. If you have a VMWare machine to sequence, make a snapshot, so if you screw it up, it will save you a bit of time.
Change all the package settings as you prefere. Naming convention is personal.
Fill in the protocol, dependent of your environment. Make sure the check boxes are checked as the screenshot. Make sure the path is correct. This also depends on your own situation.
Clean up the registry and files. I assume (and hope) this would be no problem for someone packaging software. With virtualization, a lot of people think this is not necessary but I have a lot of bad experiences troubleshooting package that where created with a next – next finish procedure.
Save the package and you’re done.
If you need the Nova PDF part, install it locally with the msi installer. This cannot be virtualized with App-V 4.6 as it is using a driver.