We have both Office 2013 & Office 2016 setup in Microsoft APP-V, and would like to use UEM for the configurations.
If we configure DirectFlex, using the app.exe name, not full path (default method) it throws the following errors.
[ERROR] DirectFlex executable configuration: Reference to 'WINWORD.EXE' found in both generic config files 'Microsoft Office 2013\Word.INI' and 'Microsoft Office 2016\Word.ini' -- ignoring reference from 'Microsoft Office 2013\Word.INI'
[WARN ] DirectFlex executable configuration: Generic config file 'Microsoft Office 2016\Excel.ini' refers to fully-qualified path 'C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE', and generic config file 'Microsoft Office 2013\Excel.INI' refers to just 'EXCEL.EXE'. This may cause confusion if 'EXCEL.EXE' is launched from another path than 'C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE'.
I thought about combining the Office.ini files into a single .ini file...but figured there is most likely another method.
Can someone let me know the proper method?
Hi JohnTwilley,
I'm afraid you'll have to specify the absolute "native" paths to each of those binaries, in both the C:\ProgramData\Microsoft\AppV\Client\Integration\package ID and C:\ProgramData\App-V\package ID\version ID folder. Not ideal, but we need something to distinguish those identically named binaries (hence the need for absolute paths), and unfortunately the App-V client presents us with different paths for the launch and the exit of an App-V application (hence the need to specify both the version-agnostic and the version-specific path).
I'm not an App-V expert, but creating a single Flex config file to deal with both virtualized Office versions won't work, I think. That would result in "polluting" the Office 2013 virtual environment with Office 2016 settings, and vice versa.
:\ProgramData\Microsoft\AppV\Client\Integration\12E99E09-6766-41E9-BEA3-6A16323B4ED8\Root\vlc.exeC
Hi JohnTwilley,
I'm afraid you'll have to specify the absolute "native" paths to each of those binaries, in both the C:\ProgramData\Microsoft\AppV\Client\Integration\package ID and C:\ProgramData\App-V\package ID\version ID folder. Not ideal, but we need something to distinguish those identically named binaries (hence the need for absolute paths), and unfortunately the App-V client presents us with different paths for the launch and the exit of an App-V application (hence the need to specify both the version-agnostic and the version-specific path).
I'm not an App-V expert, but creating a single Flex config file to deal with both virtualized Office versions won't work, I think. That would result in "polluting" the Office 2013 virtual environment with Office 2016 settings, and vice versa.
:\ProgramData\Microsoft\AppV\Client\Integration\12E99E09-6766-41E9-BEA3-6A16323B4ED8\Root\vlc.exeC
I was afraid that would be the case...
Not a big deal to configure, just a pain to remember as APP-V updates/upgrades change the full path in the future.
Thanks for your help.
John
For those interested, I'll share what I ended up using for my configuration. I have a Mixed environment of Office 2013 & 2016, both installed in the base image and using APP-V.
Here's the configuration, using Word as an example.
Our UEM setup for Office 2013:
DirectFlex (with App-V 5.o support enabled)
Executables:
%LOCALAPPDATA%\Microsoft\AppV\Client\Integration\D24C3BDD-8FAD-44D3-998C-933F8F053682\Root\Office15\WINWORD.EXE
C:\Program Files (x86)\Microsoft Office\Office15\winword.exe
Our UEM setup for Office 2016:
DirectFlex (with App-V 5.o support enabled)
Executables:
%LOCALAPPDATA%\Microsoft\AppV\Client\Integration\EB51A3D4-B87F-4676-AD01-5D583ABE053C\Root\Office16\WINWORD.EXE
C:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE
I guess you technically could add the ProgramData path, but we are publishing per user, not globally.
i.e. C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\603AEED5-1406-4859-BDDE-A8B0A203AB2B\Root\Office15\winword.exe
Thanks JohnTwilley!
Just to make sure: with these settings, does the DirectFlex export take place once you exit the application, or do you have these config files set to "export at logoff"?
I do "export at logoff" for all of these.
