Running Windows 10 v1809
Latest UEM, App Volumes and Horizon
Created a golden image with Office, Project and Visio 2019 with following template:
<Configuration ID="ac9b36d8-c80c-4d74-ba56-6bb7ed7b9ec0">
<Add OfficeClientEdition="64" Channel="PerpetualVL2019" SourcePath="C:\Office2019" AllowCdnFallback="FALSE" ForceUpgrade="FALSE">
<Product ID="ProPlus2019Volume">
<Language ID="nl-nl" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="OneNote" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="FALSE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="FALSE" />
<Display Level="FULL" AcceptEULA="TRUE" />
<Logging Level="Standard" Path="C:\Office2019\logs" />
</Configuration>
For Project and Visio the XML is a bit different as it targets different Product IDs of course.
After loggin in to a desktop all applications are functional and activated using KMS, but what we are seeing is a couple of the following 2 errors in Application Log:
Script failed
Details:
Event: desktop_message
Error: 1314
Source: svservice
Launched script
Details:
Sending user popup
Message: Svoffice failed. Please collect log files for VMware support.
Source: svservice
Besides this we also have the following error in "cv_startup_postsvc.log" which doesn't make sense to me:
2019-04-02 13:50:46.180 svoffice Invalid Office 365 product ID ProjectPro2019Volume
2019-04-02 13:50:46.255 svoffice System.SystemException: Application aborting
2019-04-02 13:50:46.255 svoffice bij svoffice.AbortApp()
2019-04-02 13:50:46.255 svoffice bij svoffice.ParseXMLFile(String sFileXML, XML_PARSED& xmlParsed)
2019-04-02 13:50:46.255 svoffice bij svoffice.cmd_writableshellstart(String[] args)
2019-04-02 13:50:46.255 svoffice bij svoffice.Main(String[] args)
Anyone have any idea?