The ‘running package scripts’ step does take a while and Installer is not able to accurately suggest how long this step will take. My guess is it wasn't ‘hung’ but you didn't wait long enough at that step — it can take numerous minutes and is working hard. Scripts provide a lot of flexibility. They may change registry keys or perform file modifications based on the machine or server configuration. You can use the Package Support Framework (PSF) to run one PowerShell script before a packaged application executable runs and one PowerShell script after the application executable runs to clean up. Use the Create Package and Program wizard In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node. In the Home tab of the ribbon, in the Create group, choose Create Package.

Applies to: Configuration Manager (current branch)

Configuration Manager continues to support packages and programs that were used in Configuration Manager 2007. A deployment that uses packages and programs might be more suitable than an application when you deploy any of the following tools or scripts:

• Administrative tools that don't install an application on a computer
• 'One-off' scripts that don't need to be continually monitored
• Scripts that run on a recurring schedule and can't use global evaluation

Tip

Consider using the Scripts feature in the Configuration Manager console. Scripts may be a better solution for some of the preceding scenarios instead of using packages and programs.

When you migrate packages from an earlier version of Configuration Manager, you can deploy them in your Configuration Manager hierarchy. After migration is complete, the packages appear in the Packages node in the Software Library workspace.

You can modify and deploy these packages in the same way you did by using software distribution. The Import Package from Definition Wizard remains in Configuration Manager to import legacy packages. Advertisements are converted to deployments when you migrate from Configuration Manager 2007 to a Configuration Manager hierarchy.

Note

Use Package Conversion Manager to convert packages and programs into Configuration Manager applications. Package Conversion Manager is integrated with Configuration Manager. For more information, see Package Conversion Manager.

Packages can use some new features of Configuration Manager, including distribution point groups and monitoring. You can't deploy Microsoft Application Virtualization (App-V) applications with packages and programs in Configuration Manager. To distribute virtual applications, create them as Configuration Manager applications. For more information, see Deploy App-V virtual applications.

Create a package and program

Use the Create Package and Program wizard

1. In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node.

2. In the Home tab of the ribbon, in the Create group, choose Create Package.

3. On the Package page of the Create Package and Program Wizard, specify the following information:

   • Name: Specify a name for the package with a maximum of 50 characters.

   • Description: Specify a description for this package with a maximum of 128 characters.

   • Manufacturer (optional): Specify a manufacturer name to help you identify the package in the Configuration Manager console. This name can be a maximum of 32 characters.

   • Language (optional): Specify the language version of the package with a maximum of 32 characters.

   • Version (optional): Specify a version number for the package with a maximum of 32 characters.

   • This package contains source files: This setting indicates whether the package requires source files to be present on client devices. By default, the wizard doesn't enable this option, and Configuration Manager doesn't use distribution points for the package. When you select this option, specify the package content to distribute to distribution points.

   • Source folder: If the package contains source files, choose Browse to open the Set Source Folder dialog box, and then specify the location of the source files for the package.

     Note

     The computer account of the site server must have read access permissions to the source folder that you specify.

     Windows limits the source path to 256 characters or less. This limit applies to package source as well as applications. For more information, see Naming Files, Paths, and Namespaces.

   • Starting in version 1906, if you want to pre-cache content on a client, specify the Architecture and Language of the package. For more information, see Configure pre-cache content.

4. On the Program Type page of the Create Package and Program Wizard, select the type of program to create, and then choose Next. You can create a program for a computer or device, or you can skip this step and create a program later.

   Tip

   To create a new program for an existing package, first select the package. Then, in the Home tab, in the Package group, choose Create Program to open the Create Program Wizard.

Create a standard program

1. On the Program Type page of the Create Package and Program Wizard, choose Standard Program, and then choose Next.

2. On the Standard Program page, specify the following information:

   • Name: Specify a name for the program with a maximum of 50 characters.

     Note

     The program name must be unique within a package. After you create a program, you can't modify its name.

   • Command Line: Enter the command line to use to start this program, or choose Browse to browse to the file location.

     If you don't specify an extension for a file name, Configuration Manager attempts to use .com, .exe, and .bat as possible extensions.

     When the client runs the program, Configuration Manager searches for the file in the following locations:

     • Within the package
     • The local Windows folder
     • The local %path%

     If it can't find the file, the program fails.

   • Startup folder (optional): Specify the folder from which the program runs, up to 127 characters. This folder can be an absolute path on the client. It can also be a path that's relative to the distribution point folder that contains the package.

   • Run: Specify the mode in which the program runs on client computers. Select one of the following options:

     • Normal: The program runs in the normal mode based on system and program defaults. This mode is the default.

     • Minimized: The program runs minimized on client devices. Users might see installation activity in the notification area or on the taskbar.

     • Maximized: The program runs maximized on client devices. Users see all installation activity.

     • Hidden: The program runs hidden on client devices. Users don't see any installation activity.

   • Program can run: Specify whether the program runs only when a user is signed in, only when no user is signed in, or regardless of whether a user is signed in to the client computer.

   • Run mode: Specify whether the program runs with administrative permissions or with the permissions of the user who's currently signed in.

   • Allow users to view and interact with the program installation: Use this setting, if available, to specify whether to allow users to interact with the program installation. This option is only available if the following conditions are met:

     • Program can run setting is Only when no user is logged on or Whether or not a user is logged on
     • Run mode setting is to Run with administrative rights

   • Drive mode: Specify information about how this program runs on the network. Choose one of the following options:

     • Runs with UNC name: Specify that the program runs with a Universal Naming Convention (UNC) name. This setting is the default.

     • Requires drive letter: Specify that the program requires a drive letter to fully qualify its location. For this setting, Configuration Manager can use any available drive letter on the client.

     • Requires specific drive letter: Specify that the program requires a specific drive letter that you specify to fully qualify its location. For example, Z:. If the client is already using the specified drive letter, the program doesn't run.

   • Reconnect to distribution point at log on: Indicate whether the client reconnects to the distribution point when the user signs in. By default, the wizard doesn't enable this option.

3. On the Requirements page of the Create Package and Program Wizard, specify the following information:

   • Run another program first: Identify a package and program that runs before this package and program runs.

   • Platform requirements: Select This program can run on any platform or This program can run only on specified platforms. Then choose the OS versions that clients must have to install this package and program.

   • Estimated disk space: Specify the amount of disk space that the program requires to run on the computer. The default setting is Unknown. If necessary, specify a whole number greater than or equal to zero. If you set a value, also select units for the value.

   • Maximum allowed run time (minutes): Specify the maximum time that you expect the program to run on the client computer. The default value is 120 minutes. Only use whole numbers greater than zero.

     Important

     If you use maintenance windows on the same collection to which you deploy this program, a conflict could occur if the Maximum allowed run time is longer than the scheduled maintenance window. If you set the maximum run time to Unknown, the program starts to run during the maintenance window. It then continues to run as needed after the maintenance window is closed. If you set the maximum run time to a specific period that's greater than the length of any available maintenance window, then the client doesn't run the program.

     If you set this value to Unknown, Configuration Manager sets the maximum allowed run time as 12 hours (720 minutes).

     Note

     If the program exceeds the maximum run time, Configuration Manager stops it if the following conditions are met:

     • You enable the option to Run with administrative rights
     • You don't enable the option to Allow users to view and interact with the program installation

Install Microsoft Office Running Package Scripts

Create a device program

1. On the Program Type page of the Create Package and Program Wizard, select Program for device, and then choose Next.

2. On the Program for Device page, specify the following settings:

   • Name: Specify a name for the program with a maximum of 50 characters.

     Note

     The program name must be unique within a package. After you create a program, you can't modify its name.

   • Comment (optional): Specify a comment for this device program with a maximum of 127 characters.

   • Download folder: Specify the name of the folder on the device in which it will store the package source files. The default value is Temp.

   • Command Line: Enter the command line to use to start this program. To browse to the file location, choose Browse.

   • Run command line in download folder: Select this option to run the program from the download folder.

   • Run command line from this folder: Select this option to specify a different folder from which to run the program.

3. On the Requirements page, specify the following settings:

   • Estimated disk space: Specify the amount of disk space that's required for the software. The client displays this value to mobile device users before they install the program.

   • Download program: Specify information about when the mobile device can download this program. You can specify As soon as possible, Only over a fast network, or Only when the device is docked.

   • Additional requirements: Specify any additional requirements for this program. Users see these requirements before they install the software. For example, you could notify users that they need to close all other applications before running the program.

Deploy packages and programs

1. In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node.

2. Select the package that you want to deploy. In the Home tab of the ribbon, in the Deployment group, choose Deploy.

3. On the General page of the Deploy Software Wizard, specify the name of the package and program that you want to deploy. Select the collection to which you want to deploy the package and program, and any optional comments.

   To store the package content on the collection's default distribution point group, select the option to Use default distribution point groups associated to this collection. If you didn't associate this collection with a distribution point group, this option is unavailable.

4. On the Content page, choose Add. Select the distribution points or distribution point groups to which you want to distribute the content for this package and program.

5. On the Deployment Settings page, configure the following settings:

   • Purpose: Choose one of the following options:

     • Available: The user sees the published package and program in Software Center and can install it on demand.

     • Required: The package and program is deployed automatically, according to the configured schedule. In Software Center, you can track its deployment status and install it before the deadline.

     Note

     If multiple users are signed into the device, package and task sequence deployments may not appear in Software Center.

   • Send wake-up packets: If you set the deployment purpose to Required and select this option, the site first sends a wake-up packet to computers at the installation deadline time. Before you can use this option, configure computers for Wake On LAN. For more information, see How to configure Wake on LAN.

   • Allow clients on a metered Internet connection to download content after the installation deadline, which might incur additional costs

   Note

   When you deploy a package and program, the option to Pre-deploy software to the user's primary device isn't available.

6. On the Scheduling page, configure when to deploy this package and program to client devices.

   The options on this page vary depending on whether you set the deployment action to Available or Required.

   For Required deployments, configure the rerun behavior for the program from the Rerun behavior drop-down menu. Choose from the following options:

   Rerun behavior	Description
   Never rerun deployed program	The client won't rerun the program. This behavior happens even if the program originally failed or if the program files are changed.
   Always rerun program	The client always reruns the program when the deployment is scheduled. This behavior happens even if the program has already successfully run. It's useful with recurring deployments when you update the program.
   Rerun if failed previous attempt	The client reruns the program when the deployment is scheduled, only if it failed on the previous run attempt.
   Rerun if succeeded on previous attempt	The client reruns the program only if it previously ran successfully on the client. This behavior is useful with recurring deployments when you routinely update the program, and each update requires the previous update to be successfully installed.

7. On the User Experience page, specify the following information:

   • Allow users to run the program independently of assignments: Users can install this software from Software Center regardless of any scheduled installation time.

   • Software installation: Allows the software to be installed outside of any configured maintenance windows.

   • System restart (if required to complete the installation): If the software installation requires a device restart to finish, allow this action to happen outside of any configured maintenance windows.

   • Embedded devices: When you deploy packages and programs to Windows Embedded devices that are write-filter-enabled, you can specify that they install packages and programs on the temporary overlay and commit changes later. Alternately, commit the changes on the installation deadline or during a maintenance window. When you commit changes on the installation deadline or during a maintenance window, a restart is required, and the changes persist on the device.

     Note

     When you deploy a package or program to a Windows Embedded device, make sure that the device is a member of a collection that has a configured maintenance window. For more information about how maintenance windows are used when you deploy packages and programs to Windows Embedded devices, see Creating Windows Embedded applications.

8. On the Distribution Points page, specify the following information:

   • Deployment options: Specify the action that a client when it uses a distribution point in its current boundary group. Also select the action for the client when it uses a distribution point from a neighbor boundary group or the default site boundary group.

     Important

     If you configure the deployment option to Run program from distribution point, make sure to enable the option to Copy the content in this package to a package share on distribution points on the Data Access tab of the package properties. Otherwise the package is unavailable to run from distribution points.

   • Allow clients to use distribution points from the default site boundary group: When this content isn't available from any distribution point in the current or neighbor boundary groups, enable this option to let them try distribution points in the site default boundary group.

9. Complete the wizard.

View the deployment in the Deployments node of the Monitoring workspace and in the details pane of the package deployment tab when you select the deployment. For more information, see Monitor packages and programs.

Monitor packages and programs

To monitor package and program deployments, use the same procedures that you use to monitor applications as detailed in Monitor applications.

Packages and programs also include a number of built-in reports, which enable you to monitor information about the deployment status of packages and programs. These reports have the report category of Software Distribution – Packages and Programs and Software Distribution – Package and Program Deployment Status.

For more information about how to configure reporting in Configuration Manager, see Introduction to reporting.

Manage packages and programs

In the Software Library workspace, expand Application Management, and select the Packages node. Select the package that you want to manage, and then choose a management task.

Create Prestage Content File

Opens the Create Prestaged Content File Wizard, to create a file that contains the package content. Use this file to manually import the package to a remote distribution point. This action is useful when you have low network bandwidth between the site server and the distribution point.

Create Program

Opens the Create Program Wizard, to create a new program for this package.

Export

Opens the Export Package Wizard, to export the selected package and its content to a file. Use this file to import the file to another hierarchy.

Deploy

Opens the Deploy Software Wizard, to deploy the selected package and program to a collection. For more information, see Deploy packages and programs.

Distribute content

Opens the Distribute Content Wizard, to send the content for a package and program to selected distribution points or distribution point groups.

Import

Opens the Import Package Wizard, to import a previously exported package from a .zip file.

Tip

Starting in version 2010, when you import an object in the Configuration Manager console, it now imports to the current folder. Previously, Configuration Manager always put imported objects in the root node.

Update distribution points

Updates distribution points with the latest content for the selected package and program.

Next steps

Applies to: Windows 10, version 1607

Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see Deploying Microsoft Office 2013 by using App-V. For information about using App-V to deliver Office 2010, see Deploying Microsoft Office 2010 by using App-V.

What to know before you start

Before you deploy Office 2016 with App-V, review the following planning information.

Supported Office versions and Office coexistence

Use the following table to get information about supported versions of Office and running coexisting versions of Office.

Packaging, publishing, and deployment requirements

Before you deploy Office with App-V, review the following requirements.

Excluding Office applications from a package

The following table describes the recommended methods for excluding specific Office applications from a package.

Creating an Office 2016 package for App-V with the Office Deployment Tool

Complete the following steps to create an Office 2016 package for App-V.

Important

In App-V 5.0 and later, you must use the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.

Review prerequisites for using the Office Deployment Tool

The computer on which you are installing the Office Deployment Tool must have the following:

Note

In this topic, the term “Office 2016 App-V package” refers to subscription licensing.

Create Office 2016 App-V packages with the Office Deployment Tool

You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with subscription licensing.

Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.

Download the Office Deployment Tool

Office 2016 App-V packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation, follow these steps:

1. Download the Office 2016 Deployment Tool for Click-to-Run.

   Important

   You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.

2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.

   Example location: ServerOffice2016

3. Check that the setup.exe and configuration.xml files exist and are in the location you specified.

Download Office 2016 applications

After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.

The XML file included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.

1. Customize the sample XML configuration file: Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:

   1. Open the sample XML file in Notepad or your favorite text editor.

   2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file:

   Note

   The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To uncomment these lines, remove the <! - - from the beginning of the line, and the -- > from the end of the line.

   The previous example of an XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the serverOffice2016 location where Office applications will be saved. Note that the Product ID of the applications will not affect Office's final licensing. You can create Office 2016 App-V packages with various licensing from the same applications by specifying licensing in a later stage. The following table summarizes the XML file's customizable attributes and elements:

   Input	Description	Example
   Add element	Specifies which products and languages the package will include.	N/A
   OfficeClientEdition (attribute of Add element)	Specifies whether Office 2016 32-bit or 64-bit edition will be used. OfficeClientEdition must be set to a valid value for the operation to succeed.	OfficeClientEdition='32' OfficeClientEdition='64'
   Product element	Specifies the application. Project 2016 and Visio 2016 must be specified here as added products to include them in the applications. For more information about Product IDs, see Product IDs that are supported by the Office Deployment Tool for Click-to-Run.	Product ID ='O365ProPlusRetail' Product ID ='VisioProRetail' Product ID ='ProjectProRetail'
   Language element	Specifies which language the applications support.	Language
   Version (attribute of Add element)	Optional. Specifies which build the package will use. Defaults to latest advertised build (as defined in v32.CAB at the Office source).	16.1.2.3
   SourcePath (attribute of Add element)	Specifies the location the applications will be saved to.	Sourcepath = 'ServerOffice2016'
   Channel (part of Add element)	Optional. Defines which channel will be used to update Office after installation. The default is Deferred for Microsoft 365 Apps for enterprise and Current for Visio Pro for Office 365 and Project Desktop Client. For more information about update channels, see Overview of update channels for Microsoft 365 Apps for enterprise.	Channel='Current' Channel='Deferred' Channel='FirstReleaseDeferred' Channel='FirstReleaseCurrent'

After editing the configuration.xml file to specify the desired product, languages, and the location where the Office 2016 applications will be saved to, you can save the configuration file under a name of your choice, such as 'Customconfig.xml.'2. Download the applications into the specified location: Use an elevated command prompt and a 64-bit operating system to download the Office 2016 applications that will later be converted into an App-V package. The following is an example command:

serverOffice2016setup.exe /download serverOffice2016Customconfig.xml

The following table describes the example command's elements:

Convert the Office applications into an App-V package

After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.

What you’ll need to do

• Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10 computers.

• Create an Office App-V package for either Subscription Licensing package by using the Office Deployment Tool, and then modify the Customconfig.xml configuration file.

  The following table summarizes the values you need to enter in the Customconfig.xml file. The steps in the sections that follow the table will specify the exact entries you need to make.

Note

You can use the Office Deployment Tool to create App-V packages for Microsoft 365 Apps for enterprise. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.

How to convert the Office applications into an App-V package

1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:

   • SourcePath: Change to the location where you saved the Office applications you downloaded during setup.

   • ProductID: Specify the type of licensing, as shown in the following example:

     • Subscription Licensing:

       This example made the following changes to create this Subscription Licensing package:

     • SourcePath was changed to point to the Office applications that were downloaded earlier.

     • Product ID for Office was changed to O365ProPlusRetail.

     • Product ID for Visio was changed to VisioProRetail.

   • ExcludeApp (optional): Lets you specify Office programs that you don’t want included in the App-V package created by the Office Deployment Tool. For example, you can exclude Access.

   • PACKAGEGUID (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages created by the Office Deployment Tool, and then manage your published packages with the App-V Server.

     An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.

     Note

     Even if you use unique package IDs, you can still deploy only one App-V package to a single device.

2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.

   The following is an example packager command:

   The following table describes each element used in the example command:

   Element	Description
   serverOffice2016	This is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is Customconfig.xml.
   Setup.exe	This is the Office Deployment Tool.
   /packager	This command creates the Office 2016 App-V package with the license type specified in the Customconfig.xml file.
   serverOffice2016Customconfig.xml	This passes the configuration XML file that has been prepared for the packaging stage. In this example, the file is Customconfig.xml.
   servershareOffice2016AppV	This specifies the location of the newly created Office App-V package.

   After you run the /packager command, the following folders appear up in the directory where you specified the package should be saved:

   • App-V Packages—contains an Office 2016 App-V package and two deployment configuration files.
   • WorkingDir

   Note

   To troubleshoot any issues, see the log files in the %temp% directory (default).

3. Verify that the Office 2016 App-V package works correctly:

   1. Publish the Office 2016 App-V package that you created globally to a test computer and verify that the Office 2016 shortcuts appear.
   2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.

Publishing the Office package for App-V

Use the following information to publish an Office package.

Methods for publishing Office App-V packages

Deploy the App-V package for Office 2016 by using the same methods as the other packages that you've already deployed:

• Microsoft Endpoint Configuration Manager
• App-V Server
• Stand-alone through Windows PowerShell commands

Microsoft Script Center

Publishing prerequisites and requirements

How to publish an Office package

Microsoft Office Package

Run the following command to publish an Office package globally:

• You can add permissions to a group of computers instead of just a user group through the Web Management Console on the App-V Server. This lets packages be published globally to the computers in the corresponding group.

Customizing and managing Office App-V packages

To manage your Office App-V packages, use the same operations as you would for any other package, with a few exceptions as outlined in the following sections.

Enabling Office plug-ins by using connection groups

The following steps will tell you how to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that only contains the plug-ins (you can't use the Office Deployment Tool to create the plug-ins package). After that, create a connection group that contains the Office package and the plug-ins package.

Enable plug-ins for Office App-V packages

1. Add a Connection Group through App-V Server, Microsoft Endpoint Configuration Manager, or a Windows PowerShell cmdlet.

2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer that will be used to sequence the plug-in. We recommend that you use Microsoft 365 Apps for enterprise (non-virtual) on the sequencing computer when sequencing Office 2016 plug-ins.

3. Create an App-V package that includes the plug-ins you want.

4. Add a Connection Group through the App-V Server, Configuration Manager, or a Windows PowerShell cmdlet.

5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.

   Important

   The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.

6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match published Office 2016 App-V package's global settings.

7. Verify that the plug-in package's Deployment Configuration file has the same settings as the Office 2016 App-V package.

   The Office 2016 App-V plug-in package's settings must match those of the operating system to allow for integration. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both 'InProcessEnabled' and 'OutOfProcessEnabled' match the settings of the Office 2016 App-V package you published.

8. Open the Deployment Configuration File and set the value for Objects Enabled to false.

9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.

10. Ensure that the Connection Group you created on your desired computer is enabled. The Connection Group created will be shown as 'pending' if the Office 2016 App-V package is being used while the Connection Group is enabled. If that happens, you'll have to reboot the computer to successfully enable the Connection Group.

11. After you successfully publish both packages and enable the Connection Group, verify the plug-ins you published on the Connection Group work as expected.

Disabling Office 2016 applications

You can also disable specific applications in your Office App-V package. For example, if you don't want to use Access, you can disable Access while leaving all other Office applications available. When you disable an application, the user will no longer see its shortcut icon. You don't need to re-sequence the application to do this. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, just save the changes and add the Office 2016 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.

Microsoft Office Running Package Scripts

Note

To exclude specific Office applications when you create the App-V package with the Office Deployment Tool, use the ExcludeApp setting.

Disable an Office 2016 application

1. Open a Deployment Configuration File with a text editor such as Notepad and search for “Applications.'

2. Search for the Office application you want to disable, for example, Access 2016.

3. Change the value of Enabled to false.

4. Save the Deployment Configuration File.

5. Add the Office 2016 App-V Package with the new Deployment Configuration File.

6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.

Disabling Office 2016 shortcuts

You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.

Disable shortcuts for Office 2016 applications

1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.

2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. The following example shows how to delete the Microsoft Access shortcuts while keeping the subsystems <shortcut> </shortcut> intact.

3. Save the Deployment Configuration File.

4. Republish the Office 2016 App-V Package with the new Deployment Configuration File.

Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.

Managing Office 2016 package upgrades

To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the steps outlined in the following section.

How to upgrade a previously deployed Office 2016 package

1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.

   Note

   Office App-V packages have two Version IDs:

   • An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
   • A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.

2. Globally publish the newly created Office 2016 App-V Packages onto the computers you want to apply the new updates to. Since the new package has the same lineage as the older Office 2016 App-V Package, publishing will be fast, as publishing the new package with the updates only applies the new changes to the old package.

3. Upgrades will be applied in the same manner of any globally published App-V packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.

Microsoft Office Os X Running Package Scripts Stall

Deploying Visio 2016 and Project 2016 with Office

Microsoft Office Install Running Package Scripts

The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.

Microsoft Office Stuck At Running Package Scripts

Related topics