Consider this scenario:
- Windows Server OS with RDS enabled (e.g. Citrix XenApp Platform)
- Office 2010 ProPlus installed locally
- An additional Office 2010 application (e.g. Visio 2010 or Project 2010) is installed as virtualized application.
For this example let's refer to Visio Premium 2010 as virtualized application.
The additional virtualized Office 2010 application is implemented following the guidance for the "Microsoft Office 2010 Deployment Kit for App-V"
KB 2627274 - Prescriptive Guidance for Sequencing Office 2010 in App-V 4.6 SP1
We have seen an issue that the OSPPSVC.exe service may use excessive CPU like 50% CPU and sometimes even spikes to 70% CPU.
This is mainly observed during Application startup of the locally installed 2010 applications.
With only a few users logged on the server, CPU usage for the OSPPSVC.exe process may reach 50% or even higher CPU load.
Things seem to become difficult on the topic of the "licensing flags" for the installation of the OffVirt.msi package.
This is the documented command line from KB 2627274 for adding the :
msiexec /i OffVirt.msi [feature flags][licensing flags]
The [licensing flags] need to match the virtualized products only. If there is a mismatch or even worse an overlap with the locally installed applications this causes the excessive CPU load with OSPPSVC.exe.
Please enable (set to value 1) only the license flags for Office 2010 products which have been sequenced using Microsoft Office 2010 Deployment Kit for App-V to be provided as a virtually streamed application. Do not enable Office 2010 products which are installed locally.
For our example with Viso Premium 2010 as virtualized application and Office 2010 ProPlus installed locally the correct term for the licensing flags is
msiexec /i OffVirt.msi [feature flags] VISIOPREM=1
How to Profile Microsoft Office 2010 for XenApp Application Streaming