I ran into a pretty rare situation. I have a client that has 2 packages for different office applications:

1. Access 2013: Installated locally/unattended installation
2. Access+Excel 2003: In one package, virtualized with App-V 5.0.

The first package works fine, but as soon as I publish the second package (without even starting it), there is a repair triggered every time Access 2013 starts. I suspect there are some registry keys set by the App-V client to handle FTA's, which conflict with Access 2013. I tried removing all FTA's from the second package, but no luck so far.

Does anyone have an idea how to solve this? Would it be possible to disable the repair in the Access 2013 package?

0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Answer this question or Comment on this question for clarity