We have encountered a problem were we are unable to use both Office 2016 (MSI installer) and the latest versions of Project and Visio 2016 from MSDN. Within the Technet forum thread Office 2016 (MSI installer) volume license incompatible with Visio/Project 2016 from MSDN (Click to run installer) a user wrote. contacted me a couple of days before and drew my attention to a Technet forum post, that addresses this issue. Parallel installation will work after all… msi install is used to distribute MS Office, standalone Click'n'Run packages can't be installed on those machines. Some admins told me, that Access or Visio and Project 2016 are only available as Click'n'Run via Microsoft Imagine. This causes some administrators to run into problems in business environments. ![]() However, Microsoft does not allow/support a parallel installation of these two product variants. The advantage: You have the installation files for the Office package on a DVD or on your hard disk and can install in one go, without downloading. However, there is also an Office Professional version for business environments, that can be installed via. Only works as long as Microsoft offers the download. A web installer then pulls all components of Office and sets them up on a target system. We also had a MS office patch break the Volumes, but rolling back the patch resolved the "setup" issue with the existing stack.Microsoft usually offers its Office suite as a click-to-run installation. ![]() After a successful capture, we had to uninstall/reinstall Office on the Parent image (longer separate story regarding MS patching) and it broke the existing AppVolumes for Visio and Project. If ANY change is made to the Parent Image installation of Office, you may need to repeat the process to capture a matching AppStack. I needed to create a CI for each pool that needed Visio and Project resulting in multiple AppStack versions specific to each pool. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |