Thanks again for your answer. Office 2010 is already part of the parent image. The only office products not on the parent image are Visio and Project. For those, three AppStacks have been cre...
See more...
Thanks again for your answer. Office 2010 is already part of the parent image. The only office products not on the parent image are Visio and Project. For those, three AppStacks have been created, one Visio, one Project, one with both installed, as per VMware recommendation. However, the current Adobe Problem also occurs, when no other AppStacks are attached. The Adobe Pro install is an SCCM installation packet, which is being installed by triggering the msi and the all users option set to 1. I am not an application packager – but I believe this option does what it is supposed to do, as the start menu entries are being pushed from “%ProgramData%\Microsoft\Windows\Startmenu\Programs”. At least that is what I believe, as I cannot inspect the location of the start menu items on my profile. The Target just says Adobe Acrobat XI Pro. I also want to point out, Adobe Pro XI is working perfectly. It starts up and works the way it is intended. However, it (or AppVolumes) causes MS Word 2010 to reconfigure. As stated in my previous post, if I install Adobe Pro on the capture machine without the VM being in provisioning mode, the installation works. Adobe as well as MS Word work exactly the way they are intended, i.e. No reconfiguration required. The issue only occurs, once the capture machine is in provision mode. The issue is then reproducible once the AppStack gets assigned to other VMs as well.