This resulted in an AppStack that is usable ONLY on the desktop pool that was created with the same provisioning machine as the AppStack. MSI but DO NOT run the actual application.ĭO NOT run any re-arm or licensing commands. (not sure if a factor, but I always do it to avoid capturing a new user profile)ħ) Run. The steps I followed were:ġ) Clone the Parent image used for the specific Desktop Pool that the AppVolume will be attached to.ī) Remove (In this specific sequence!) AppVolumes Agent, UEM Agent, Horizon Client.Ĭ) Ensure MS Feb' 2019 Update is removed (actual KB referenced in the chain above)ĥ) Create new AppVolume and use the new CI as the provisioning machineĦ) log in as the local admin account to CI, NOT a domain user account. I was able to successfully create the Visio and Project App Stacks. This seems to work except for Visio attachments won't open directly from Outlook. without the Office suite installed I captured Visio using the same Click-To-Run package but used this config: Then on the same clean provisioning machine i.e. This was done on a clean provisioning machine. I have MS Office 365 installed in an appstack installed with the click-to-run package with this config: Does anyone know if an actual KMS server is required? ADBA authenticates Visio 2016 Pro as a non-AppStack install just fine.įrom the instant clone Application event logs, I can see install errors involving language packs, but both Office and Visio are configured with the exact same settings (Install All from Desktop).Īre you using MSI installers for the Office and Visio install or Click-to-Run? You can't mix and match as far as I know. Lastly, we use Active Directory-Based Authentication, not KMS server. I have tried capturing the AppStack off the golden image for the instant clone pool, but the Visio installation fails to run with the same missing files errors. If I close Visio, wait for set-up to revert itself and stop, I can re-open Visio and be functional, but it will not activate and de-activates Office 2016 Pro. But, when attaching to the instant clone, it launched into set-up and then fails with "can't find necessary file" type errors. I have tried installing with Office 2016 Pro+ on the provisioning machine and without it. Trying to capture Visio 2016 Pro and Project 2016 Pro. and have used the VMware Knowledge Base for the capture. Running AppVolumes 2.15, Office 2016 Pro+ on the golden image of Win10 LTSC 2019 instant clone pool (Horizon 7.7)Ĭapture machine is a clean build of Win10 LTSC 2019. Under Licensing and activation, select the Multiple Activation Key (MAK) option, type the volume license key that's specific to the product, switch the Autoactivate slider to On, and then select Next.I have the same issue. Under Upgrade options, indicate whether you have to keep any of the products that are already installed on the device, as necessary, and then select Next. Under Update and upgrade > Update and upgrade options, select the options that match your requirements, as necessary. Under Installation, select the options that match your requirements, as necessary, and then select Next. Under Language, select the primary language, and then select Next. Under Apps, use the toggles to determine which apps will be installed, and then select Next. Under Update channel, Office LTSC 2021 Perpetual Enterprise will be listed as the Update Channel. Under Products, select the products that you want to deploy. For more information, see Choose between the 64-bit or 32-bit version of Office.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |