REVISED 22 JANUARY 2020

BEST PRACTICES FORDELIVERING MS PROJECTAND VISIO WITH VMWAREAPP VOLUMES 2.XOPERATIONAL TUTORIAL

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 2

Table of Contents

Overview

– Introduction

– Purpose

– Audience

Creating AppStacks for Microsoft Project and Visio

– Introduction

– Prerequisites

– Capturing MS Project

– Testing the Microsoft Project Appstack

Troubleshooting Tips

– Introduction

– Error during AppStack provisioning

– Error when starting Microsoft Project

– Microsoft Project license is missing

Summary and Additional Resources

– Summary

– Additional Resources

– About the Author and Contributors

– Feedback

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 3

Best Practices for Delivering MS Project and Visiowith VMware App Volumes 2.x OperationalTutorial

OverviewIntroductionThis operational tutorial provides best practices for anyone deploying App Volumes 2.x to deliver applications such as MicrosoftProject or Microsoft Visio 2016 to their end users. Applications like these can interact with suites such as Microsoft Office, andrequire specific considerations during AppStack provisioning. This tutorial covers best practices to deliver applications and data toyour end users using App Volumes 2.x.

PurposeThis operational tutorial provides best practices for anyone deploying App Volumes 2.x to deliver applications such as MicrosoftProject or Microsoft Visio 2016 to their end users. Applications like these can interact with suites such as Microsoft Office, andrequire specific considerations during AppStack provisioning. This tutorial covers some best practices to create a seamlessexperience for your end-users with App Volumes.

AudienceThis operational tutorial is intended for IT professionals and App Volumes administrators of existing production environments. Bothcurrent and new administrators can benefit from using this tutorial. Knowledge of VMware vSphere®, VMware vCenter Server®,Microsoft SQL Server, and View in VMware Horizon® 7 or VMware Horizon 6 is helpful.

Creating AppStacks for Microsoft Project and VisioIntroductionThe process of capturing Microsoft Project or Visio is not much different from other applications, but before starting this, it is highlyrecommended to go through the prerequisites mentioned below.

If you want to know more about how to capture Microsoft Office products, see Installing and using Microsoft Office Products withVMware App Volumes 2.x.

PrerequisitesMake sure you use the correct media for the Microsoft Project or Visio installation in combination with VMware App Volumes andHorizon.

Retail and OEM versions of MS Office cannot be used and are not supported on VMware Horizon desktops. If you already have anISO of Microsoft Project or Visio downloaded for you, verify them for use with App Volumes, before proceeding with provisioningthe Microsoft Project or Visio AppStacks.

You must have a folder named Admin on your ISO. If there is no such folder, this is not a suitable ISO for App Volumes.1.Check that the name of the folder that has *.ww extension, such as ProPlus.ww, Visio.ww, PrjPro.ww,2.and Standard.ww. If there is a lowercase ‘r’ before the dot, which means retail (such as ProPlusr.ww, Visior.ww),then this is not a suitable ISO.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 4

The operating system (OS) version on your App Volumes provisioning machine should be the same OS version as your3.Horizon pool desktops. This requirement is the same for an RDSH environment. For more information about creating aprovisioning machine for creating AppStacks, see Preparing a Provisioning Machine.If Microsoft Office is installed in the base of your gold image, be sure it is also installed on your provisioning machine.4.Finally, make sure that the Windows Update Service is disabled, and that you do not attempt to capture any Microsoft5.updates while going through this provisioning process.

If all of the above has been verified and everything meets the requirements, you can make a snapshot of the provisioningmachine. Snapshotting the provisioning machine is needed when you plan to provision more applications or update existing ones.After you’ve done that, you can start capturing Microsoft Project or Visio with App Volumes.

You are ready to proceed to the next section to capture Microsoft Project. The same technique and steps used below can be usedfor Microsoft Visio.

Capturing MS ProjectThis section provides an example of how to capture Microsoft Project.

Note: The same technique and steps used below can be used for Microsoft Visio.

In the App Volumes Manager, select Volumes, and under the AppStacks tab, click Create.1.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 5

In the Create AppStacks window, fill in a name for your AppStack, verify that the other settings (such as storage2.location) are correct, and then click Create.

In the Confirm Create AppStack window, click Create to confirm.3.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 6

When AppStack creation is completed, return to the AppStacks window, verify that the empty AppStack is there, and select4.Provision.

Begin the capture of Microsoft Project by selecting the provisioning machine to assign the empty AppStack to, and click5.Provision.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 7

In the Confirm Start Provisioning window, click Start Provisioning.6.

When the dialog box appears on the provisioning machine with the message: “You are now in provisioning mode,” wait. Do7.not click OK yet.

Wait until provisioning finishes, and then click OK.8. You can now start installing Microsoft Project with administrator privileges. The installer gives you the ability to do a default9.installation or to customize the installation if necessary. Follow the online prompts.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 8

After the installation is completed, open the App Volumes pop-up message and click OK.10.

Verify that you have installed Microsoft Project successfully by navigating to the Control panel, Add/Remove Programs11.section.

Caution: At this stage, do not open Microsoft Project, and do not capture any user data that appear when you first openMicrosoft Project. On the provisioning virtual machine, click Yes to proceed. The provisioining VM reboots automatically to finish the12.procedure.

When the reboot is complete, log in with the same user credentials that you used during the provisioning stage. When13.the “Provisioning successful!” message appears, click OK to finish.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 9

Note: If you want to provision another application, make sure you revert the provisioning machine to a clean snapshot. After all the tasks are done on the provisioning machine, switch back to the App Volumes Manager, and click Complete.14.

In the Confirm Provisioning Complete window, click Complete Provisioning to finish the provisioning process.15.

Testing the Microsoft Project AppstackTo test the Microsoft Project AppStack that you just created:

Under the AppStacks tab, select the Microsoft Project AppStack you just created, and press Assign.1.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 10

Find the user you want to test the AppStack with, and select Assign.2.When a Confirm Assign dialog box appears, select the option: Attach AppStacks on next login or reboot.3.

Log in to the desktop with the user credentials that the AppStack was assigned to earlier, and verify that Microsoft Project4.is available on the Start menu:

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 11

Click the shortcut in the Start menu to start Microsoft Project. The application should start without issues.5.

Now your Microsoft Project AppStack is ready and can be assigned to your end-users.

Troubleshooting TipsIntroductionThis section covers some troubleshooting tips.

Error during AppStack provisioningIssue: The following error message appears during provisioning of the AppStack:

The system cannot open the device or file specified.

If you run into the error message “The system cannot open the device or file specified,” during provisioning of Microsoft Project,pressing the Cancel button shows another error message.

Resolution: To resolve the issue:

In the App Volumes provisioning dialog box, stop the provisioning process by clicking OK, and then follow the prompts. The1.

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 12

machine reboots automatically, and you must restart the provisioning process from the beginning, as follows: Log in to the provisioning machine.2. Start Regedit in elevated mode, and browse to the following key:3.

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\svdriver\Parameters Verify that the value HookInjectionWhitelist exists. If not, create the value in Multi-String Value.4. Add *msiexec.exe||* under the HookInjectionWhitelist key in the registry.5.

Reboot the provisioning machine and restart the Microsoft Project provisioning process.6. Verify that the issue is resolved.7.

Error when starting Microsoft ProjectIssue: When starting Microsoft Project, the application shows the configuration Progress and errors out with the followingmessage:

The system cannot open the device or file specified.

The provisioning process of Microsoft Project might have gone successfully, but after assigning the Microsoft Project AppStack andstarting the application, the user is getting one of the following error messages, usually when attempting to auto-activate thelicense using KMS discovery through DNS:

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 13

Resolution: To resolve the issue:

This issue can occur if the AppStack template.vmdk is not default and contains other files than the template delivered by1.VMware. Pollution of an AppStack template can happen if a custom AppStack template is being used to capture theapplication.Recapture Microsoft Project using the default template, delivered with App Volumes.2.

Microsoft Project license is missingIssue: When starting Microsoft Project, the end-user may encounter an unlicensed product issue after launching Microsoft Projectwhile Microsoft Office is licensed.

Resolution: To resolve the issue:

Reprovision the Microsoft Project application but before finishing the provisioning process, run the following command on1.the provisioning machine using an elevated CMD prompt:

C:\Program Files (x86)\Microsoft Office\Office16> cscript.exe ospp.vbs /sethst:kms.fqdn.com

C:\Program Files (x86)\Microsoft Office\Office16> cscript.exe ospp.vbs /setprt:1688

BEST PRACTICES FOR DELIVERING MS PROJECT AND VISIO WITH VMWARE APP VOLUMES 2.X OPERATIONAL TUTORIAL

HORIZON | 14

The sethst parameter is used to specify the Key Management Server (KMS) used within your organization. In the2.example above, replace kms.fqdn.com with the fully qualified domain name of your KMS Server. Microsoft Project canauto-discover the KMS server through DNS and will activate Microsoft Project automatically. The user should see theProduct Information as below after launching the Microsoft Project application.

Summary and Additional ResourcesSummaryThis operational tutorial provided recommended best-practices for provisioning Microsoft Project and Microsoft Visio with AppVolumes.

For more information about VMware App Volumes, see VMware Digital Workspace Tech Zone.

Additional ResourcesFor more information, see the following resources:

VMware App Volumes DocumentationVMware App Volumes product pageInstalling and Using Microsoft Office Products with VMware App Volumes 2.x (2146035)

About the Author and ContributorsThis operational tutorial was written by:

Shrestha Upendra, Sr. EUC Solution Architect, EUC Field Engineering

Additional contributors to this tutorial include:

Raymond Wiesemann, Lead Architect, VMware EUC Field EngineeringStephane Asselin, Sr. Manager, VMware EUC Field EngineeringHarold Stiess, PSO Consultant, VMware

FeedbackTo comment on this paper, contact VMware End-User-Computing Technical Marketingat euc_tech_content_feedback@vmware.com.

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax650-427-5001 www.vmware.com

Copyright © 2019 VMware, Inc. All rights reserved. This product is protected by U.S. and internationalcopyright and intellectual property laws. VMware products are covered by one or more patents listedat http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc.in the United States and/or other jurisdictions. All other marks and names mentioned herein may betrademarks of their respective companies.