locked
App-V RunVirtual Question RRS feed

  • Question

  • Windows 7 SP1

    App-V 5 SP3

    Locally installed Office 2010/2013 that uses locally installed Office add-ins.

    I've used RunVirtual with success but is there a solution for mixed environments with local and virtual office add-ins that doesn't involve also virtualizing Office and using connection groups or virtualizing all add-ins?

    I'm going to guess there is not but I wanted to ask.

    Thanks!

    Wednesday, February 18, 2015 3:50 PM

Answers

  • Hi you can mix them. In our envirnoment we have situations with local office addins mixed up with some additional virtualised, no problem.
    At the moment we use custom scripts to dynamically create the connectiongroups with the addins (we are still on SP2). But in your case you can create 1 connectiongroup, add 1 mandatory package (dummy package) and add all other addins as optional package. Configure the Runvirtual key (USER) to the dummy package.

    Just keep in mind that in your virtual package there are some keys which need to merge in stead of overwrite, so pre-sequence, allways start all office apps (word/excel/etc) at least once so the local profile gets created.
    You only challenge will be excel automation addins.

    • Marked as answer by JT_Packager Wednesday, February 18, 2015 6:56 PM
    Wednesday, February 18, 2015 4:13 PM

All replies

  • Yes and No...I don't beleive there's a 'designed' solution BUT I've had locally installed Office Add-ins working with my virtual Office products without issue or without any extra configuration.

    The virtual Office still scans the local machine in the standard Office Add-in directories, so if the vendor has packaged their application correctly. You virtual office should be able to use the locally installed Add-ins.

    If you want to virtualize add-ins and use with local office, like you said, you can use RunVirtual.

    If you want to virtualize office and virtualize add-ins and also have some locally installed add-ins. That may also be possible, just test the add-ins locally installed with office. Even if they don't work, you might be able to get them to work by moving the add-ins to the correct directory.

    Did that cover all bases?


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    • Proposed as answer by Thamim Karim Wednesday, February 18, 2015 5:35 PM
    Wednesday, February 18, 2015 3:59 PM
  • Thanks for the reply!

    The issue I'm having now is I have a locally installed version of Office with a locally installed add-in and a virtual add-in.  RunVirtual allows the virtual add-in to load but then the locally installed add-in does not load, vice-versa.  I've tried every combination of the below settings without any luck:

    <COM Mode="Integrated">

    OutofProcessEnabled=True and InProcessEnabled=True

    Wednesday, February 18, 2015 4:12 PM
  • Hi you can mix them. In our envirnoment we have situations with local office addins mixed up with some additional virtualised, no problem.
    At the moment we use custom scripts to dynamically create the connectiongroups with the addins (we are still on SP2). But in your case you can create 1 connectiongroup, add 1 mandatory package (dummy package) and add all other addins as optional package. Configure the Runvirtual key (USER) to the dummy package.

    Just keep in mind that in your virtual package there are some keys which need to merge in stead of overwrite, so pre-sequence, allways start all office apps (word/excel/etc) at least once so the local profile gets created.
    You only challenge will be excel automation addins.

    • Marked as answer by JT_Packager Wednesday, February 18, 2015 6:56 PM
    Wednesday, February 18, 2015 4:13 PM
  • Like myself and Tiberivs said, that should be possible.

    If you're having an issue with a locally installed Add-in, where is the add-in installed to? Some vendors will install their add-ins under their own Install directory and register for Office. But there's also some standard folder (depending on the product e.g. Excel XLStart)

    If moving the add-in doesn't work, you could try doing a capture of registering the add-in on a VM with a local office and take the reg and file changes and apply them to your setup..


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    • Proposed as answer by Thamim Karim Wednesday, February 18, 2015 5:35 PM
    Wednesday, February 18, 2015 4:26 PM
  • I had forgotten to set those keys to merge instead of override, everything is working as expected, thanks!
    Wednesday, February 18, 2015 6:57 PM
  • Great, always keep in mind that if there are keys in your virtual package, which are also shared by a local package, you need to set them to merge, like in case of COM-addins HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins. In case of automation excel addins (like xlas-files) which are triggered by the OPEN keys under Excel\Options, you need to set the correct order.
    • Edited by Roy Essers Thursday, February 19, 2015 10:59 AM
    Thursday, February 19, 2015 10:58 AM