During provisioning and installing O365 (according to the recipe of course) we get an error, Error code is 30015-11 (110).
Already tried Microsoft support and possible solutions but no luck. Same with VMware knowledge bases. I've reported this issue and created a support request at VMware. It is still in investigation.
Installing without provisioning mode went oke, no problems with installation. It only happens in provisioning mode. Creadted a new/clean Provisioning VM but no luck
I wanted to try my luck here and ask if there are more people with this issue or even maybe a solution.
Recently upgraded App Volumes environment to v2.15.0.41. I had no issues with previous version (v2.0.13)
Provisioning VM is Server 2016 (x64). There are no installations/configurations of UEM, Horizon View or any AntiVirus on this VM. It is a clean VM with only Windows updates installed.
If you installed the update rollup for February which Windows 10 does by default it will be a part of that and you probably can't just uninstall the individual KB. The entire February rollup will have to be uninstalled.
This is actually do to a Microsoft update for February KB4487017. If you remove this KB you should then be able to capture the Microsoft Office Appstack properly. It is not necessary to remove it on your actual VDI desktops, just on the provisioning machine for app volumes
Thanks for your reply. KB you mentioned is not installed on the provisioning VM. It only happens in provisioning mode.
If I install Office on the same machine without provisioning mode (not creating an AppStack), no errors. Installation is successful.
You haven't applied the February security updates from Microsoft on your provisioning machine? That KB is part of the February updates.
Edit: And yes, the error will only happen in provisioning mode if you have the security patch installed.
If you installed the update rollup for February which Windows 10 does by default it will be a part of that and you probably can't just uninstall the individual KB. The entire February rollup will have to be uninstalled.
Created a whole new provisioning VM, no February rollup installed, worked fine. Installation is complete without errors!
Thanks for your help, lots of appreciation!!