Networknet archive Blog

App-V: Office 365 ProPlus and SAP EPM COM add-in loading issue

Originally published Last updated 1 comment

Over the past few months, I have been helping build a Windows 10 1709 image, update core applications and upgrade App-V packages. Client migrations from Windows 7 to Windows 10 are now underway, and several issues have appeared. The new Office 365 ProPlus installation needs to integrate with App-V. From Windows 10 version 1703, if I remember correctly, the App-V client is part of the operating system and needs to be enabled through PowerShell/SCCM.

Getting Excel add-in support working with Office 365 ProPlus has been the biggest challenge so far. SAP Business Objects EPM client 10 is one example. Its Excel add-in had been sequenced with the App-V 5.1 Sequencer, but it did not work.

The EPM ribbon was missing

Excel opened from the published App-V shortcut, but the EPM add-in ribbon was missing.

Enabling AllowJitvInAppvVirtualizedProcess in the registry resolved the issue. With the setting enabled, the App-V add-in loaded successfully.

Code5 lines
1
2
3
4
5
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClickToRun\OverRide]
"AllowJitvInAppvVirtualizedProcess"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\ClickToRun\OverRide]
"AllowJitvInAppvVirtualizedProcess"=dword:00000001

EPM-Fix-Office-365

Starting Excel from the command line

Code1 line
1
"C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE" /appvve:8907bc2b-870a-4eaa-af7a-247563912121_5f3e0f2c-030a-4506-b441-9f45ac9c254d

Use Get-AppvClientPackage in PowerShell to retrieve the PackageID and VersionID.

This registry setting resolved a major dependency in our Windows 10 project. It may also help with other Office integration packages, although that remains to be seen.

1 comment

Comments from the original WordPress site, kept read-only.