mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into dh-servicing-sandbox
This commit is contained in:
Dani Halfin
commit
050c74d66c
@ -36,6 +36,7 @@
|
||||
#### [Using a room control system](use-room-control-system-with-surface-hub.md)
|
||||
### [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
|
||||
### [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)
|
||||
## [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
|
||||
## [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
## [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
|
||||
## [Change history for Surface Hub](change-history-surface-hub.md)
|
||||
@ -14,6 +14,12 @@ localizationpriority: medium
|
||||
|
||||
This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
|
||||
|
||||
## February 2017
|
||||
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
| [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | New |
|
||||
|
||||
## January 2017
|
||||
|
||||
| New or changed topic | Description |
|
||||
|
||||
@ -1,22 +0,0 @@
|
||||
---
|
||||
title: Device reset (Surface Hub)
|
||||
description: You may wish to reset your Microsoft Surface Hub.
|
||||
ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
|
||||
redirect_url: https://technet.microsoft.com/itpro/surface-hub/device-reset-surface-hub
|
||||
keywords: reset Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -31,9 +31,11 @@ Initiating a reset will return the device to the last cumulative Windows update,
|
||||
- Configurations from MDM or the Settings app
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Performing a device reset may take up to 2 hours. Do not interrupt the reset process. Interrupting the process will render the device inoperable, requiring warranty service to return to normal functionality.
|
||||
> Performing a device reset may take up to 6 hours. Do not turn off or unplug the Surface Hub until the process has completed. Interrupting the process will render the device inoperable, requiring warranty service to return to normal functionality.
|
||||
|
||||
After the reset, Surface Hub restarts the [first run program](first-run-program-surface-hub.md) again.
|
||||
After the reset, Surface Hub restarts the [first run program](first-run-program-surface-hub.md) again. If the Surface Hub displays a Welcome screen, that indicates that the reset encountered a problem and rolled back to the previously existing OS image.
|
||||
|
||||
If you see a blank screen for long periods of time during the **Reset device** process, please wait and do not take any action.
|
||||
|
||||
|
||||
## Reset a Surface Hub from Settings
|
||||
|
||||
@ -60,7 +60,8 @@ If the default values shown are correct, then you can click **Next** to go on. O
|
||||
|
||||
### What happens?
|
||||
|
||||
>**Note** Once the settings on this page are entered, you can't come back to this screen unless you reset the device (see [Device reset](device-reset-suface-hub.md)). Make sure that the settings are properly configured before proceeding.
|
||||
>[!NOTE]
|
||||
> Once the settings on this page are entered, you can't come back to this screen unless you reset the device (see [Device reset](device-reset-surface-hub.md)). Make sure that the settings are properly configured before proceeding.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
author: jdeckerMS
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -19,25 +19,12 @@ Documents related to deploying and managing the Microsoft Surface Hub in your or
|
||||
|
||||
## In this section
|
||||
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md) | This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.|
|
||||
| [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | This topic explains the differences between the operating system on Surface Hub and Windows 10 Enterprise. |
|
||||
| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security. |
|
||||
| [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide. |
|
||||
| [Change history for Surface Hub](change-history-surface-hub.md) | This topic lists new and updated topics in the Surface Hub documentation. |
|
||||
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Topic</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)</p></td>
|
||||
<td align="left"><p>This guide covers the installation and administration of devices running Surface Hub, and is intended for use by anyone responsible for these tasks, including IT administrators and developers.</p></td>
|
||||
</tr>
|
||||
<tr><td>[Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md)</td><td>This topic explains the differences between the operating system on Surface Hub and Windows 10 Enterprise.</td></tr>
|
||||
<tr><td>[How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)</td><td>This topic provides guidance on Wi-Fi Direct security risks, how the Surface Hub has addressed those risks, and how Surface Hub administrators can configure the device for the highest level of security. </td></tr>
|
||||
<tr><td>[Change history for Surface Hub](change-history-surface-hub.md)</td><td>This topic lists new and updated topis in the Surface Hub documentation.</td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -24,10 +24,10 @@ Review these dependencies to make sure Surface Hub features will work in your IT
|
||||
|-------------------------------------------------------|-------------------------------------------------------|
|
||||
| Active Directory or Azure Active Directory (Azure AD) | <p>The Surface Hub's uses an Active Directory or Azure AD account (called a **device account**) to access Exchange and Skype for Business services. The Surface Hub must be able to connect to your Active Directory domain controller or to your Azure AD tenant in order to validate the device account’s credentials, as well as to access information like the device account’s display name, alias, Exchange server, and Session Initiation Protocol (SIP) address.</p>You can also domain join or Azure AD join your Surface Hub to allow a group of authorized users to configure settings on the Surface Hub. |
|
||||
| Exchange (Exchange 2013 or later, or Exchange Online) and Exchange ActiveSync | <p>Exchange is used for enabling mail and calendar features, and also lets people who use the device send meeting requests to the Surface Hub, enabling one-touch meeting join.</p>ActiveSync is used to sync the device account’s calendar and mail to the Surface Hub. If the device cannot use ActiveSync, it will not show meetings on the welcome screen, and joining meetings and emailing whiteboards will not be enabled. |
|
||||
| Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing. |
|
||||
| Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing.</br></br>If screen sharing on a Surface Hub fails and the error message **An error occurred during the screen presentation** is displayed, see [Video Based Screen Sharing not working on Surface Hub](https://support.microsoft.com/help/3179272/video-based-screen-sharing-not-working-on-surface-hub) for help. |
|
||||
| Mobile device management (MDM) solution (Microsoft Intune, System Center Configuration Manager, or supported third-party MDM provider) | If you want to apply settings and install apps remotely, and to multiple devices at a time, you must set up a MDM solution and enroll the device to that solution. See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for details. |
|
||||
| Microsoft Operations Managmement Suite (OMS) | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. |
|
||||
| Network and Internet access | <p>In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred.</p><p>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</p>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. |
|
||||
| Microsoft Operations Managmement Suite (OMS) | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. |
|
||||
| Network and Internet access | <p>In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred.</p><p>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</p>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. |
|
||||
|
||||
Additionally, note that Surface Hub requires the following open ports:
|
||||
- HTTPS: 443
|
||||
|
||||
36
devices/surface-hub/surface-hub-downloads.md
Normal file
36
devices/surface-hub/surface-hub-downloads.md
Normal file
@ -0,0 +1,36 @@
|
||||
---
|
||||
title: Useful downloads for Microsoft Surface Hub
|
||||
description: Downloads related to the Microsoft Surface Hub.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerMS
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Useful downloads for Microsoft Surface Hub
|
||||
|
||||
This topic provides links to useful Surface Hub documents, such as product datasheets, the site readiness guide, and user's guide.
|
||||
|
||||
| Link | Description |
|
||||
| --- | --- |
|
||||
| [Surface Hub Site Readiness Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-site-readiness-guide) | Make sure your site is ready for Surface Hub, including structural and power requirements, and get technical specs for Surface Hub. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/27/aa/27aa7dd7-7cb7-40ea-9bd6-c7de0795f68c.mov?n=04.07.16_installation_video_01_site_readiness.mov) |
|
||||
| [Surface Hub Setup Guide (English, French, Spanish) (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-setup-guide) | Get a quick overview of how to set up the environment for your new Surface Hub. |
|
||||
| [Surface Hub Quick Reference Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-quick-reference-guide) | Use this quick reference guide to get information about key features and functions of the Surface Hub. |
|
||||
| [Surface Hub User Guide (PDF)](http://download.microsoft.com/download/3/6/B/36B6331E-0C63-4E71-A05D-EE88D05081F8/surface-hub-user-guide-en-us.pdf) | Learn how to use Surface Hub in scheduled or ad-hoc meetings. Invite remote participants, use the built-in tools, save data from your meeting, and more. |
|
||||
| [Surface Hub Replacement PC Drivers](https://www.microsoft.com/download/details.aspx?id=52210) | The Surface Hub Replacement PC driver set is available for those customers who have chosen to disable the Surface Hub’s internal PC and use an external computer with their 84” or 55” Surface Hub. This download is meant to be used with the Surface Hub Admin Guide , which contains further details on configuring a Surface Hub Replacement PC. |
|
||||
| [Surface Hub SSD Replacement Guide (PDF)](https://www.microsoft.com/surface/en-us/support/surfacehubssd) | Learn how to replace the solid state drive (SSD) for the 55- and 84-inch Surface Hub. |
|
||||
| [Microsoft Surface Hub Rollout and Adoption Success Kit (ZIP)](http://download.microsoft.com/download/F/A/3/FA3ADEA4-4966-456B-8BDE-0A594FD52C6C/Surface%20Hub%20RASK.zip) | Best practices for generating awareness and implementing change management to maximize adoption, usage, and benefits of Microsoft Surface Hub. The Rollout and Adoption Success Kit zip file includes the Rollout and Adoption Success Kit detailed document, Surface Hub presentation, demo guidance, awareness graphics, and more. |
|
||||
| [Unpacking Guide for 84-inch Surface Hub (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-unpacking-guide-84) | Learn how to unpack your 84-inch Surface Hub efficiently and safely. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/75/2b/752b73dc-6e9d-4692-8ba1-0f9fc03bff6b.mov?n=04.07.16_installation_video_03_unpacking_84.mov) |
|
||||
| [Unpacking Guide for 55-inch Surface Hub (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-unpacking-guide-55) | Learn how to unpack your 55-inch Surface Hub efficiently and safely. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/a9/d6/a9d6b4d7-d33f-4e8b-be92-28f7fc2c06d7.mov?n=04.07.16_installation_video_02_unpacking_55.mov) |
|
||||
| [Wall Mounting and Assembly Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-wall-mounting-assembly-guide) | Detailed instructions on how to safely and securely assemble the wall brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/bf/4d/bf4d6f06-370c-45ee-88e6-c409873914e8.mov?n=04.07.16_installation_video_05_wall_mount.mov) |
|
||||
| [Floor-Supported Mounting and Assembly Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-floor-supported-mounting-assembly-guide) | Detailed instructions on how to safely and securely assemble the floor-supported brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/ed/de/edde468a-e1d4-4ce8-8b61-c4527dd25c81.mov?n=04.07.16_installation_video_06_floor_support_mount.mov) |
|
||||
| [Rolling Stand Mounting and Assembly Guide (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-rolling-stand-mounting-assembly-guide) | Detailed instructions on how to safely and securely assemble the rolling stand, and how to mount your Surface Hub onto it. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/1f/94/1f949613-3e4a-41e3-ad60-fe8aa7134115.mov?n=04.07.16_installation_video_04_rolling_stand_mount.mov) |
|
||||
| [Mounts and Stands Datasheet (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-mounts-and-stands-datasheet) | Specifications and prices for all Surface Hub add-on stands and mounts that turn your workspace into a Surface Hub workspace. |
|
||||
| [Surface Hub Stand and Wall Mount Specifications (PDF)](https://www.microsoft.com/surface/support/surface-hub/surface-hub-stand-and-wall-mount-specs) | Illustrated specifications for the 55” and 84” Surface Hub rolling stands, wall mounts, and floor-supported wall mounts. |
|
||||
| [Surface Hub Onsite Installation and Onsite Repair/Exchange Services FAQ (PDF)](https://www.microsoft.com/surface/en-us/support/surface-hub/onsite-installation-repair-faq) | Get answers to the most common questions about Surface Hub onsite service offerings and delivery. |
|
||||
|
||||
|
||||
|
||||
|
||||
@ -81,10 +81,11 @@ Before you deploy Office by using App-V, review the following requirements.
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Packaging</p></td>
|
||||
<td align="left"><ul>
|
||||
<td align="left">
|
||||
<ul>
|
||||
<li><p>All of the Office applications that you want to deploy to users must be in a single package.</p></li>
|
||||
<li><p>In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.</p></li>
|
||||
<li><p>If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project).</p></li>
|
||||
<li><p>If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -102,12 +103,7 @@ Before you deploy Office by using App-V, review the following requirements.
|
||||
<li><p>Project Pro for Office 365</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>You must enable [shared computer activation](http://technet.microsoft.com/library/dn782860.aspx).</p>
|
||||
<p>You don’t use shared computer activation if you’re deploying a volume licensed product, such as:</p>
|
||||
<ul>
|
||||
<li><p>Office Professional Plus 2016</p></li>
|
||||
<li><p>Visio Professional 2016</p></li>
|
||||
<li><p>Project Professional 2016</p></li>
|
||||
</ul></td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -154,9 +150,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
|
||||
Complete the following steps to create an Office 2016 package for App-V 5.0 or later.
|
||||
|
||||
**Important**
|
||||
In App-V 5.0 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
|
||||
|
||||
>**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
|
||||
|
||||
@ -190,13 +184,12 @@ The computer on which you are installing the Office Deployment Tool must have:
|
||||
</table>
|
||||
|
||||
|
||||
**Note**
|
||||
In this topic, the term “Office 2016 App-V package” refers to subscription licensing and volume licensing.
|
||||
>**Note** In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
|
||||
|
||||
|
||||
### Create Office 2016 App-V Packages Using 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 Volume Licensing or Subscription Licensing.
|
||||
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.
|
||||
|
||||
@ -206,6 +199,7 @@ Office 2016 App-V Packages are created using the Office Deployment Tool, which g
|
||||
|
||||
1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
|
||||
|
||||
>**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: \\\\Server\\Office2016
|
||||
@ -237,8 +231,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
**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.
|
||||
>**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 above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
|
||||
|
||||
@ -269,13 +262,14 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Product element</p></td>
|
||||
<td align="left"><p>Specifies the application. Project 2016 and Visio 2016 must be specified here as an added product to be included in the applications.</p></td>
|
||||
<td align="left"><p>Specifies the application. Project 2016 and Visio 2016 must be specified here as an added product to be included in the applications.
|
||||
|
||||
For more information about the product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](https://support.microsoft.com/kb/2842297)
|
||||
</p></td>
|
||||
<td align="left"><p><code>Product ID ="O365ProPlusRetail "</code></p>
|
||||
<p><code>Product ID ="VisioProRetail"</code></p>
|
||||
<p><code>Product ID ="ProjectProRetail"</code></p>
|
||||
<p><code>Product ID ="ProPlusVolume"</code></p>
|
||||
<p><code>Product ID ="VisioProVolume"</code></p>
|
||||
<p><code>Product ID = "ProjectProVolume"</code></p></td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Language element</p></td>
|
||||
@ -286,7 +280,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
<td align="left"><p>Version (attribute of Add element)</p></td>
|
||||
<td align="left"><p>Optional. Specifies a build to use for the package</p>
|
||||
<p>Defaults to latest advertised build (as defined in v32.CAB at the Office source).</p></td>
|
||||
<td align="left"><p><code>15.1.2.3</code></p></td>
|
||||
<td align="left"><p><code>16.1.2.3</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>SourcePath (attribute of Add element)</p></td>
|
||||
@ -303,7 +297,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
|
||||
After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2016 applications will be saved onto, you can save the configuration file, for example, 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. Below is an example command with description of details:
|
||||
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. Below is an example command with a description of details:
|
||||
|
||||
``` syntax
|
||||
\\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml
|
||||
@ -346,41 +340,35 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
- 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 or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
|
||||
- Create an Office App-V package for 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 for the licensing model you’re using. 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 Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Product ID</th>
|
||||
<th align="left">Volume Licensing</th>
|
||||
<th align="left">Subscription Licensing</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Office 2016</strong></p></td>
|
||||
<td align="left"><p>ProPlusVolume</p></td>
|
||||
<td align="left"><p>O365ProPlusRetail</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Office 2016 with Visio 2016</strong></p></td>
|
||||
<td align="left"><p>ProPlusVolume</p>
|
||||
<p>VisioProVolume</p></td>
|
||||
<td align="left"><p>O365ProPlusRetail</p>
|
||||
<p>VisioProRetail</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Office 2016 with Visio 2016 and Project 2016</strong></p></td>
|
||||
<td align="left"><p>ProPlusVolume</p>
|
||||
<p>VisioProVolume</p>
|
||||
<p>ProjectProVolume</p></td>
|
||||
<td align="left"><p>O365ProPlusRetail</p>
|
||||
<p>VisioProRetail</p>
|
||||
<p>ProjectProRetail</p></td>
|
||||
@ -412,9 +400,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ProductID</p></td>
|
||||
<td align="left"><p>Specify the type of licensing, as shown in the following examples:</p>
|
||||
<ul>
|
||||
<li><p>Subscription Licensing</p>
|
||||
<td align="left"><p>Specify Subscription licensing, as shown in the following example:</p>
|
||||
<pre class="syntax" space="preserve"><code><Configuration>
|
||||
<Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail">
|
||||
@ -446,44 +432,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p></p></li>
|
||||
<li><p>Volume Licensing</p>
|
||||
<pre class="syntax" space="preserve"><code><Configuration>
|
||||
<Add SourcePath= "\\Server\Office2016" OfficeClientEdition="32" >
|
||||
<Product ID="ProPlusVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration></code></pre>
|
||||
<p>In this example, the following changes were made to create a package with Volume licensing:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>SourcePath</strong></p></td>
|
||||
<td align="left"><p>is the path, which was changed to point to the Office applications that were downloaded earlier.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Office was changed to <code>ProPlusVolume</code>.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Visio was changed to <code>VisioProVolume</code>.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p></p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<p></p>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ExcludeApp (optional)</p></td>
|
||||
<td align="left"><p>Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.</p></td>
|
||||
@ -492,13 +441,8 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
<td align="left"><p>PACKAGEGUID (optional)</p></td>
|
||||
<td align="left"><p>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 manage them by using the App-V Server.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
>**Note** Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -531,7 +475,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>/packager</strong></p></td>
|
||||
<td align="left"><p>creates the Office 2016 App-V package with Volume Licensing as specified in the customConfig.xml file.</p></td>
|
||||
<td align="left"><p>creates the Office 2016 App-V package with the type of licensing specified in the customConfig.xml file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>\\server\Office2016\Customconfig.xml</strong></p></td>
|
||||
@ -552,8 +496,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
- **WorkingDir**
|
||||
|
||||
**Note**
|
||||
To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
**Note** To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
|
||||
|
||||
|
||||
@ -563,7 +506,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
|
||||
|
||||
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V 5.0
|
||||
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V
|
||||
|
||||
|
||||
Use the following information to publish an Office package.
|
||||
@ -629,8 +572,6 @@ To manage your Office App-V packages, use the same operations as you would for a
|
||||
|
||||
- [Managing Office 2016 package upgrades](#bkmk-manage-office-pkg-upgrd)
|
||||
|
||||
- [Managing Office 2016 licensing upgrades](#bkmk-manage-office-lic-upgrd)
|
||||
|
||||
- [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project)
|
||||
|
||||
### <a href="" id="bkmk-enable-office-plugins"></a>Enabling Office plug-ins by using connection groups
|
||||
@ -641,16 +582,15 @@ Use the steps in this section to enable Office plug-ins with your Office package
|
||||
|
||||
1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
|
||||
|
||||
2. Sequence your plug-ins using the App-V 5.0 Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
|
||||
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
|
||||
|
||||
3. Create an App-V 5.0 package that includes the desired plug-ins.
|
||||
3. Create an App-V package that includes the desired plug-ins.
|
||||
|
||||
4. Add a Connection Group through App-V server, System Center Configuration Manager, or a 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.
|
||||
>**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.
|
||||
|
||||
|
||||
|
||||
@ -672,8 +612,7 @@ Use the steps in this section to enable Office plug-ins with your Office package
|
||||
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, 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.
|
||||
|
||||
**Note**
|
||||
To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
|
||||
>**Note** To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
|
||||
|
||||
|
||||
**To disable an Office 2016 application**
|
||||
@ -752,36 +691,17 @@ To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a
|
||||
|
||||
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, x.x.x.x for example, 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 that the Office version itself has changed. 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.
|
||||
|
||||
>**Note** Office App-V packages have two Version IDs:
|
||||
<ul>
|
||||
<li>An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.</li>
|
||||
<li>A second App-V Package Version ID, x.x.x.x for example, 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 that the Office version itself has changed. 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.</li>
|
||||
</ul>
|
||||
|
||||
|
||||
2. Globally publish the newly created Office 2016 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2016 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
|
||||
|
||||
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.
|
||||
|
||||
### <a href="" id="bkmk-manage-office-lic-upgrd"></a>Managing Office 2016 licensing upgrades
|
||||
|
||||
If a new Office 2016 App-V Package has a different license than the Office 2016 App-V Package currently deployed. For instance, the Office 2016 package deployed is a subscription based Office 2016 and the new Office 2016 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
|
||||
|
||||
**How to upgrade an Office 2016 License**
|
||||
|
||||
1. Unpublish the already deployed Office 2016 Subscription Licensing App-V package.
|
||||
|
||||
2. Remove the unpublished Office 2016 Subscription Licensing App-V package.
|
||||
|
||||
3. Restart the computer.
|
||||
|
||||
4. Add the new Office 2016 App-V Package Volume Licensing.
|
||||
|
||||
5. Publish the added Office 2016 App-V Package with Volume Licensing.
|
||||
|
||||
An Office 2016 App-V Package with your chosen licensing will be successfully deployed.
|
||||
|
||||
### <a href="" id="bkmk-deploy-visio-project"></a>Deploying Visio 2016 and Project 2016 with Office
|
||||
|
||||
@ -802,7 +722,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<tr class="odd">
|
||||
<td align="left"><p>How do I package and publish Visio 2016 and Project 2016 with Office?</p></td>
|
||||
<td align="left"><p>You must include Visio 2016 and Project 2016 in the same package with Office.</p>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow [Deploying Microsoft Office 2010 by Using App-V](../appv-v5/deploying-microsoft-office-2010-by-using-app-v.md).</p></td>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How can I deploy Visio 2016 and Project 2016 to specific users?</p></td>
|
||||
@ -848,17 +768,11 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
## Additional resources
|
||||
|
||||
|
||||
**Office 2016 App-V 5.0 Packages 5.0 Additional Resources**
|
||||
|
||||
[Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
||||
|
||||
[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
|
||||
|
||||
**Office 2013 and Office 2010 App-V Packages**
|
||||
|
||||
[Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md)
|
||||
|
||||
[Deploying Microsoft Office 2011 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
|
||||
[Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
|
||||
|
||||
[Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
||||
|
||||
**Connection Groups**
|
||||
|
||||
@ -868,7 +782,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
|
||||
**Dynamic Configuration**
|
||||
|
||||
[About App-V 5.0 Dynamic Configuration](about-app-v-50-dynamic-configuration.md)
|
||||
[About App-V 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md)
|
||||
|
||||
## Got a suggestion for App-V?
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
---
|
||||
---
|
||||
title: Deploying Microsoft Office 2016 by Using App-V
|
||||
description: Deploying Microsoft Office 2016 by Using App-V
|
||||
author: jamiejdt
|
||||
@ -47,7 +47,7 @@ Use the following table to get information about supported versions of Office an
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Planning for Using App-V with Office](planning-for-using-app-v-with-office51.md#bkmk-office-vers-supp-appv)</p></td>
|
||||
<td align="left"><p>[Supported versions of Microsoft Office](planning-for-using-app-v-with-office.md#bkmk-office-vers-supp-appv)</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Supported versions of Office</p></li>
|
||||
<li><p>Supported deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), pooled VDI)</p></li>
|
||||
@ -55,13 +55,14 @@ Use the following table to get information about supported versions of Office an
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Planning for Using App-V with Office](planning-for-using-app-v-with-office51.md#bkmk-plan-coexisting)</p></td>
|
||||
<td align="left"><p>[Planning for Using App-V with coexsiting versions of Office](planning-for-using-app-v-with-office.md#bkmk-plan-coexisting)</p></td>
|
||||
<td align="left"><p>Considerations for installing different versions of Office on the same computer</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-pkg-pub-reqs"></a>Packaging, publishing, and deployment requirements
|
||||
|
||||
Before you deploy Office by using App-V, review the following requirements.
|
||||
@ -80,10 +81,11 @@ Before you deploy Office by using App-V, review the following requirements.
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Packaging</p></td>
|
||||
<td align="left"><ul>
|
||||
<td align="left">
|
||||
<ul>
|
||||
<li><p>All of the Office applications that you want to deploy to users must be in a single package.</p></li>
|
||||
<li><p>In App-V 5.1 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.</p></li>
|
||||
<li><p>If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project).</p></li>
|
||||
<li><p>If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -101,12 +103,7 @@ Before you deploy Office by using App-V, review the following requirements.
|
||||
<li><p>Project Pro for Office 365</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>You must enable [shared computer activation](http://technet.microsoft.com/library/dn782860.aspx).</p>
|
||||
<p>You don’t use shared computer activation if you’re deploying a volume licensed product, such as:</p>
|
||||
<ul>
|
||||
<li><p>Office Professional Plus 2016</p></li>
|
||||
<li><p>Visio Professional 2016</p></li>
|
||||
<li><p>Project Professional 2016</p></li>
|
||||
</ul></td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -153,10 +150,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
|
||||
Complete the following steps to create an Office 2016 package for App-V 5.1 or later.
|
||||
|
||||
**Important**
|
||||
In App-V 5.1 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
|
||||
|
||||
|
||||
>**Important** In App-V 5.1 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
|
||||
|
||||
@ -182,23 +176,20 @@ The computer on which you are installing the Office Deployment Tool must have:
|
||||
<td align="left"><p>Supported operating systems</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>64-bit version of Windows 10</p></li>
|
||||
<li><p>64-bit version of Windows 8 or later</p></li>
|
||||
<li><p>64-bit version of Windows 8 or 8.1</p></li>
|
||||
<li><p>64-bit version of Windows 7</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
>**Note** In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
|
||||
|
||||
|
||||
**Note**
|
||||
In this topic, the term “Office 2016 App-V package” refers to subscription licensing and volume licensing.
|
||||
### Create Office 2016 App-V Packages Using Office Deployment Tool
|
||||
|
||||
|
||||
|
||||
### Create Office 2013 App-V Packages Using 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 Volume Licensing or Subscription Licensing.
|
||||
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.
|
||||
|
||||
@ -206,11 +197,9 @@ Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the
|
||||
|
||||
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:
|
||||
|
||||
1. Download the [Office 2-16 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
|
||||
|
||||
> [!NOTE]
|
||||
> You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.
|
||||
1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
|
||||
|
||||
>**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: \\\\Server\\Office2016
|
||||
@ -242,12 +231,9 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
</Configuration>
|
||||
```
|
||||
|
||||
**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.
|
||||
>**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 above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
|
||||
The above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -276,13 +262,14 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Product element</p></td>
|
||||
<td align="left"><p>Specifies the application. Project 2016 and Visio 2016 must be specified here as an added product to be included in the applications.</p></td>
|
||||
<td align="left"><p><code>Product ID ="O365ProPlusRetail"</code></p>
|
||||
<td align="left"><p>Specifies the application. Project 2016 and Visio 2016 must be specified here as an added product to be included in the applications.
|
||||
|
||||
For more information about the product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](https://support.microsoft.com/kb/2842297)
|
||||
</p></td>
|
||||
<td align="left"><p><code>Product ID ="O365ProPlusRetail "</code></p>
|
||||
<p><code>Product ID ="VisioProRetail"</code></p>
|
||||
<p><code>Product ID ="ProjectProRetail"</code></p>
|
||||
<p><code>Product ID ="ProPlusVolume"</code></p>
|
||||
<p><code>Product ID ="VisioProVolume"</code></p>
|
||||
<p><code>Product ID = "ProjectProVolume"</code></p></td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Language element</p></td>
|
||||
@ -298,21 +285,19 @@ The XML file that is included in the Office Deployment Tool specifies the produc
|
||||
<tr class="even">
|
||||
<td align="left"><p>SourcePath (attribute of Add element)</p></td>
|
||||
<td align="left"><p>Specifies the location in which the applications will be saved to.</p></td>
|
||||
<td align="left"><p><code>Sourcepath = "\\Server\Office2016"</code></p></td>
|
||||
<td align="left"><p><code>Sourcepath = "\\Server\Office2016”</code></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Branch (attribute of Add element)</p></td>
|
||||
<td align="left"><p>Optional. Specifies the update branch for the product that you want to download or install.</p><p>For more information about update branches, see Overview of update branches for Office 365 ProPlus.</p></td>
|
||||
<td align="left"><p>Optional. Specifies the update branch for the product that you want to download or install. </p><p>For more information about update branches, see Overview of update branches for Office 365 ProPlus.</p></td>
|
||||
<td align="left"><p><code>Branch = "Business"</code></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2016 applications will be saved onto, you can save the configuration file, for example, 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. Below is an example command with description of details:
|
||||
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. Below is an example command with a description of details:
|
||||
|
||||
``` syntax
|
||||
\\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml
|
||||
@ -355,41 +340,35 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
- 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 or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
|
||||
- Create an Office App-V package for 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 for the licensing model you’re using. 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 Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Product ID</th>
|
||||
<th align="left">Volume Licensing</th>
|
||||
<th align="left">Subscription Licensing</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Office 2016</strong></p></td>
|
||||
<td align="left"><p>ProPlusVolume</p></td>
|
||||
<td align="left"><p>O365ProPlusRetail</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Office 2016 with Visio 2016</strong></p></td>
|
||||
<td align="left"><p>ProPlusVolume</p>
|
||||
<p>VisioProVolume</p></td>
|
||||
<td align="left"><p>O365ProPlusRetail</p>
|
||||
<p>VisioProRetail</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Office 2016 with Visio 2016 and Project 2016</strong></p></td>
|
||||
<td align="left"><p>ProPlusVolume</p>
|
||||
<p>VisioProVolume</p>
|
||||
<p>ProjectProVolume</p></td>
|
||||
<td align="left"><p>O365ProPlusRetail</p>
|
||||
<p>VisioProRetail</p>
|
||||
<p>ProjectProRetail</p></td>
|
||||
@ -421,9 +400,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ProductID</p></td>
|
||||
<td align="left"><p>Specify the type of licensing, as shown in the following examples:</p>
|
||||
<ul>
|
||||
<li><p>Subscription Licensing</p>
|
||||
<td align="left"><p>Specify Subscription licensing, as shown in the following example:</p>
|
||||
<pre class="syntax" space="preserve"><code><Configuration>
|
||||
<Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
|
||||
<Product ID="O365ProPlusRetail">
|
||||
@ -455,59 +432,17 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p></p></li>
|
||||
<li><p>Volume Licensing</p>
|
||||
<pre class="syntax" space="preserve"><code><Configuration>
|
||||
<Add SourcePath= "\\Server\Office2016" OfficeClientEdition="32" >
|
||||
<Product ID="ProPlusVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
<Product ID="VisioProVolume">
|
||||
<Language ID="en-us" />
|
||||
</Product>
|
||||
</Add>
|
||||
</Configuration></code></pre>
|
||||
<p>In this example, the following changes were made to create a package with Volume licensing:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>SourcePath</strong></p></td>
|
||||
<td align="left"><p>is the path, which was changed to point to the Office applications that were downloaded earlier.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Office was changed to <code>ProPlusVolume</code>.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Product ID</strong></p></td>
|
||||
<td align="left"><p>for Visio was changed to <code>VisioProVolume</code>.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<p></p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<p></p>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ExcludeApp (optional)</p></td>
|
||||
<td align="left"><p>Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access.</p></td>
|
||||
<td align="left"><p>Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PACKAGEGUID (optional)</p></td>
|
||||
<td align="left"><p>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 manage them by using the App-V Server.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
>**Note** Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -540,7 +475,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>/packager</strong></p></td>
|
||||
<td align="left"><p>creates the Office 2016 App-V package with Volume Licensing as specified in the customConfig.xml file.</p></td>
|
||||
<td align="left"><p>creates the Office 2016 App-V package with the type of licensing specified in the customConfig.xml file.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>\\server\Office2016\Customconfig.xml</strong></p></td>
|
||||
@ -553,14 +488,15 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
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.
|
||||
After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
|
||||
|
||||
- **WorkingDir**
|
||||
- **App-V Packages** – contains an Office 2016 App-V package and two deployment configuration files.
|
||||
|
||||
**Note**
|
||||
To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
- **WorkingDir**
|
||||
|
||||
**Note** To troubleshoot any issues, see the log files in the %temp% directory (default).
|
||||
|
||||
|
||||
|
||||
@ -570,7 +506,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
|
||||
|
||||
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V 5.1
|
||||
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V
|
||||
|
||||
|
||||
Use the following information to publish an Office package.
|
||||
@ -636,8 +572,6 @@ To manage your Office App-V packages, use the same operations as you would for a
|
||||
|
||||
- [Managing Office 2016 package upgrades](#bkmk-manage-office-pkg-upgrd)
|
||||
|
||||
- [Managing Office 2016 licensing upgrades](#bkmk-manage-office-lic-upgrd)
|
||||
|
||||
- [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project)
|
||||
|
||||
### <a href="" id="bkmk-enable-office-plugins"></a>Enabling Office plug-ins by using connection groups
|
||||
@ -648,16 +582,15 @@ Use the steps in this section to enable Office plug-ins with your Office package
|
||||
|
||||
1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
|
||||
|
||||
2. Sequence your plug-ins using the App-V 5.1 Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
|
||||
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
|
||||
|
||||
3. Create an App-V 5.1 package that includes the desired plug-ins.
|
||||
3. Create an App-V package that includes the desired plug-ins.
|
||||
|
||||
4. Add a Connection Group through App-V server, System Center Configuration Manager, or a 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.
|
||||
>**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.
|
||||
|
||||
|
||||
|
||||
@ -677,11 +610,9 @@ Use the steps in this section to enable Office plug-ins with your Office package
|
||||
|
||||
### <a href="" id="bkmk-disable-office-apps"></a>Disabling Office 2016 applications
|
||||
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, add the Office 2013 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.
|
||||
|
||||
**Note**
|
||||
To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, 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.
|
||||
|
||||
>**Note** To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
|
||||
|
||||
|
||||
**To disable an Office 2016 application**
|
||||
@ -734,11 +665,11 @@ You may want to disable shortcuts for certain Office applications instead of unp
|
||||
<Extension Category="AppV.Shortcut">
|
||||
<Shortcut>
|
||||
<File>[{Common Programs}]\Microsoft Office 2016\Access 2016.lnk</File>
|
||||
<Target>[{AppvPackageRoot}])office15\MSACCESS.EXE</Target>
|
||||
<Target>[{AppvPackageRoot}])office16\MSACCESS.EXE</Target>
|
||||
<Icon>[{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico</Icon>
|
||||
<Arguments />
|
||||
<WorkingDirectory />
|
||||
<AppuserModelId>Microsoft.Office.MSACCESS.EXE.16</AppUserModelId>
|
||||
<AppuserModelId>Microsoft.Office.MSACCESS.EXE.15</AppUserModelId>
|
||||
<AppUsermodelExcludeFroeShowInNewInstall>true</AppUsermodelExcludeFroeShowInNewInstall>
|
||||
<Description>Build a professional app quickly to manage data.</Description>
|
||||
<ShowCommand>l</ShowCommand>
|
||||
@ -760,36 +691,17 @@ To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a
|
||||
|
||||
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, x.x.x.x for example, 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 that the Office version itself has changed. 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.
|
||||
|
||||
>**Note** Office App-V packages have two Version IDs:
|
||||
<ul>
|
||||
<li>An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.</li>
|
||||
<li>A second App-V Package Version ID, x.x.x.x for example, 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 that the Office version itself has changed. 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.</li>
|
||||
</ul>
|
||||
|
||||
|
||||
2. Globally publish the newly created Office 2016 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2016 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
|
||||
|
||||
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.
|
||||
|
||||
### <a href="" id="bkmk-manage-office-lic-upgrd"></a>Managing Office 2016 licensing upgrades
|
||||
|
||||
If a new Office 2016 App-V Package has a different license than the Office 2016 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2016 and the new Office 2016 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
|
||||
|
||||
**How to upgrade an Office 2016 License**
|
||||
|
||||
1. Unpublish the already deployed Office 2016 Subscription Licensing App-V package.
|
||||
|
||||
2. Remove the unpublished Office 2016 Subscription Licensing App-V package.
|
||||
|
||||
3. Restart the computer.
|
||||
|
||||
4. Add the new Office 2016 App-V Package Volume Licensing.
|
||||
|
||||
5. Publish the added Office 2016 App-V Package with Volume Licensing.
|
||||
|
||||
An Office 2016 App-V Package with your chosen licensing will be successfully deployed.
|
||||
|
||||
### <a href="" id="bkmk-deploy-visio-project"></a>Deploying Visio 2016 and Project 2016 with Office
|
||||
|
||||
@ -851,28 +763,21 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Additional resources
|
||||
|
||||
|
||||
**Office 2016 App-V Packages Additional Resources**
|
||||
[Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md)
|
||||
|
||||
[Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
|
||||
|
||||
[Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
||||
|
||||
[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
|
||||
|
||||
**Office 2013 and Office 2010 App-V Packages**
|
||||
|
||||
[Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v51.md)
|
||||
|
||||
[Deploying Microsoft Office 2011 by Using App-V](deploying-microsoft-office-2010-by-using-app-v51.md)
|
||||
|
||||
**Connection Groups**
|
||||
|
||||
[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
|
||||
|
||||
[Managing Connection Groups](managing-connection-groups51.md)
|
||||
[Managing Connection Groups](managing-connection-groups.md)
|
||||
|
||||
**Dynamic Configuration**
|
||||
|
||||
|
||||
@ -29,7 +29,10 @@ Use the following procedure to view and configure default package extensions.
|
||||
|
||||
5. To edit other application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog box, click **Overwrite** to complete the process.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
>**Note** If the upload fails and the size of your configuration file is above 4MB, you will need to increase the maximum file size allowed by the server. This can be done by adding the maxRequestLength attribute with a value greater than the size of your configuration file (in KB) to the httpRuntime element on line 26 of C:\Program Files\Microsoft Application Virtualization Server\ManagementService\Web.config. For example, changing'<httpRuntime targetFramework="4.5"/> ' to '<httpRuntime targetFramework="4.5" maxRequestLength="8192"/>' will increase the maximum size to 8MB
|
||||
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -287,11 +287,6 @@ MBAM supports the following versions of Configuration Manager.
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft System Center 2012 R2 Configuration Manager</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft System Center 2012 Configuration Manager</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
@ -301,13 +296,9 @@ MBAM supports the following versions of Configuration Manager.
|
||||
<td align="left"><p>Microsoft System Center Configuration Manager 2007 R2 or later</p></td>
|
||||
<td align="left"><p>SP1 or later</p></td>
|
||||
<td align="left"><p>64-bit</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Although Configuration Manager 2007 R2 is 32 bit, you must install it and SQL Server on a 64-bit operating system in order to match the 64-bit MBAM software.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
</div></td>
|
||||
|
||||
>**Note** Although Configuration Manager 2007 R2 is 32 bit, you must install it and SQL Server on a 64-bit operating system in order to match the 64-bit MBAM software.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -349,29 +340,15 @@ You must install SQL Server with the **SQL\_Latin1\_General\_CP1\_CI\_AS** coll
|
||||
<td align="left"><p>Standard, Enterprise, or Datacenter</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft SQL Server 2014</p></td>
|
||||
<td align="left"><p>Standard, Enterprise, or Datacenter</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft SQL Server 2012</p></td>
|
||||
<td align="left"><p>Standard, Enterprise, or Datacenter</p></td>
|
||||
<td align="left"><p>SP2</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft SQL Server 2012</p></td>
|
||||
<td align="left"><p>Standard, Enterprise, or Datacenter</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>SP3</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft SQL Server 2008 R2</p></td>
|
||||
<td align="left"><p>Standard or Enterprise</p></td>
|
||||
<td align="left"><p>SP1, SP2, SP3</p></td>
|
||||
<td align="left"><p>SP3</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -306,7 +306,7 @@ This procedure will demonstrate how to deploy the reference image to the PoC env
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
|
||||
|
||||
[Default]
|
||||
_SMSTSORGNAME=Contoso
|
||||
OSInstall=YES
|
||||
@ -362,7 +362,7 @@ This procedure will demonstrate how to deploy the reference image to the PoC env
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
|
||||
|
||||
[Default]
|
||||
DeployRoot=\\SRV1\MDTProd$
|
||||
UserDomain=CONTOSO
|
||||
@ -417,12 +417,16 @@ This procedure will demonstrate how to deploy the reference image to the PoC env
|
||||
Disable-NetAdapter "Ethernet 2" -Confirm:$false
|
||||
```
|
||||
|
||||
>Wait until the disable-netadapter command completes before proceeding.
|
||||
|
||||
|
||||
2. Next, switch to the Hyper-V host and open an elevated Windows PowerShell prompt. Create a generation 2 VM on the Hyper-V host that will load its OS using PXE. To create this VM, type the following commands at an elevated Windows PowerShell prompt:
|
||||
|
||||
```
|
||||
New-VM –Name "PC2" –NewVHDPath "c:\vhd\pc2.vhdx" -NewVHDSizeBytes 60GB -SwitchName poc-internal -BootDevice NetworkAdapter -Generation 2
|
||||
Set-VMMemory -VMName "PC2" -DynamicMemoryEnabled $true -MinimumBytes 720MB -MaximumBytes 2048MB -Buffer 20
|
||||
```
|
||||
|
||||
>Dynamic memory is configured on the VM to conserve resources. However, this can cause memory allocation to be reduced past what is required to install an operating system. If this happens, reset the VM and begin the OS installation task sequence immediately. This ensures the VM memory allocation is not decreased too much while it is idle.
|
||||
|
||||
3. Start the new VM and connect to it:
|
||||
@ -452,24 +456,24 @@ This completes the demonstration of how to deploy a reference image to the netwo
|
||||
|
||||
This section will demonstrate how to export user data from an existing client computer, wipe the computer, install a new operating system, and then restore user data and settings. The scenario will use PC1, a computer that was cloned from a physical device to a VM, as described in [Step by step guide: Deploy Windows 10 in a test lab](windows-10-poc.md).
|
||||
|
||||
If the PC1 VM is not already running, then start and connect to it:
|
||||
|
||||
1. If the PC1 VM is not already running, then start and connect to it:
|
||||
|
||||
```
|
||||
Start-VM PC1
|
||||
vmconnect localhost PC1
|
||||
```
|
||||
|
||||
1. Switch back to the Hyper-V host and create a checkpoint for the PC1 VM so that it can easily be reverted to its current state for troubleshooting purposes and to perform additional scenarios. Checkpoints are also known as snapshots. To create a checkpoint for the PC1 VM, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
2. Switch back to the Hyper-V host and create a checkpoint for the PC1 VM so that it can easily be reverted to its current state for troubleshooting purposes and to perform additional scenarios. Checkpoints are also known as snapshots. To create a checkpoint for the PC1 VM, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
|
||||
```
|
||||
Checkpoint-VM -Name PC1 -SnapshotName BeginState
|
||||
```
|
||||
|
||||
2. Sign on to PC1 using the CONTOSO\Administrator account.
|
||||
3. Sign on to PC1 using the CONTOSO\Administrator account.
|
||||
|
||||
>Specify **contoso\administrator** as the user name to ensure you do not sign on using the local administrator account. You must sign in with this account so that you have access to the deployment share.
|
||||
|
||||
3. Open an elevated command prompt on PC1 and type the following:
|
||||
4. Open an elevated command prompt on PC1 and type the following:
|
||||
|
||||
```
|
||||
cscript \\SRV1\MDTProd$\Scripts\Litetouch.vbs
|
||||
@ -477,13 +481,13 @@ If the PC1 VM is not already running, then start and connect to it:
|
||||
|
||||
**Note**: Litetouch.vbs must be able to create the C:\MININT directory on the local computer.
|
||||
|
||||
4. Choose the **Windows 10 Enterprise x64 Custom Image** and then click **Next**.
|
||||
5. Choose the **Windows 10 Enterprise x64 Custom Image** and then click **Next**.
|
||||
|
||||
5. Choose **Do not back up the existing computer** and click **Next**.
|
||||
6. Choose **Do not back up the existing computer** and click **Next**.
|
||||
|
||||
**Note**: The USMT will still back up the computer.
|
||||
|
||||
6. Lite Touch Installation will perform the following actions:
|
||||
7. Lite Touch Installation will perform the following actions:
|
||||
- Back up user settings and data using USMT.
|
||||
- Install the Windows 10 Enterprise X64 operating system.
|
||||
- Update the operating system via Windows Update.
|
||||
@ -491,15 +495,15 @@ If the PC1 VM is not already running, then start and connect to it:
|
||||
|
||||
You can review the progress of installation on SRV1 by clicking on the **Monitoring** node in the deployment workbench. When OS installation is complete, the computer will restart, set up devices, and configure settings.
|
||||
|
||||
7. Sign in with the CONTOSO\Administrator account and verify that all CONTOSO domain user accounts and data have been migrated to the new operating system, or other user accounts as specified [previously](#configure-the-mdt-production-deployment-share).
|
||||
8. Sign in with the CONTOSO\Administrator account and verify that all CONTOSO domain user accounts and data have been migrated to the new operating system, or other user accounts as specified [previously](#configure-the-mdt-production-deployment-share).
|
||||
|
||||
8. Create another checkpoint for the PC1 VM so that you can review results of the computer refresh later. To create a checkpoint, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
9. Create another checkpoint for the PC1 VM so that you can review results of the computer refresh later. To create a checkpoint, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
|
||||
```
|
||||
Checkpoint-VM -Name PC1 -SnapshotName RefreshState
|
||||
```
|
||||
|
||||
9. Restore the PC1 VM to it's previous state in preparation for the replace procedure. To restore a checkpoint, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
10. Restore the PC1 VM to it's previous state in preparation for the replace procedure. To restore a checkpoint, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
|
||||
```
|
||||
Restore-VMSnapshot -VMName PC1 -Name BeginState -Confirm:$false
|
||||
@ -507,7 +511,7 @@ If the PC1 VM is not already running, then start and connect to it:
|
||||
vmconnect localhost PC1
|
||||
```
|
||||
|
||||
10. Sign in to PC1 using the contoso\administrator account.
|
||||
11. Sign in to PC1 using the contoso\administrator account.
|
||||
|
||||
## Replace a computer with Windows 10
|
||||
|
||||
@ -557,10 +561,10 @@ At a high level, the computer replace process consists of:<BR>
|
||||
```
|
||||
3. Complete the deployment wizard using the following:
|
||||
- **Task Sequence**: Backup Only Task Sequence
|
||||
- **User Data**: Specify a location: **\\SRV1\MigData$\PC1**
|
||||
- **User Data**: Specify a location: **\\\\SRV1\MigData$\PC1**
|
||||
- **Computer Backup**: Do not back up the existing computer.
|
||||
4. While the task sequence is running on PC1, open the deployment workbench console on SRV1 and click the **Monitoring* node. Press F5 to refresh the console, and view the status of current tasks.
|
||||
5. Verify that **The user state capture was completed successfully** is displayed, and click **Finish** when the capture is complete.
|
||||
5. On PC1, verify that **The user state capture was completed successfully** is displayed, and click **Finish** when the capture is complete.
|
||||
6. On SRV1, verify that the file **USMT.MIG** was created in the **C:\MigData\PC1\USMT** directory. See the following example:
|
||||
|
||||
```
|
||||
@ -585,18 +589,24 @@ At a high level, the computer replace process consists of:<BR>
|
||||
```
|
||||
Disable-NetAdapter "Ethernet 2" -Confirm:$false
|
||||
```
|
||||
|
||||
>As mentioned previously, ensure that you disable the **external** network adapter, and wait for the command to complete before proceeding.
|
||||
|
||||
|
||||
3. Start and connect to PC3 by typing the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
|
||||
```
|
||||
Start-VM PC3
|
||||
vmconnect localhost PC3
|
||||
```
|
||||
|
||||
4. When prompted, press ENTER for network boot.
|
||||
|
||||
6. On PC3, ue the following settings for the Windows Deployment Wizard:
|
||||
6. On PC3, use the following settings for the Windows Deployment Wizard:
|
||||
- **Task Sequence**: Windows 10 Enterprise x64 Custom Image
|
||||
- **Move Data and Settings**: Do not move user data and settings
|
||||
- **User Data (Restore)**: Specify a location: **\\SRV1\MigData$\PC1**
|
||||
- **User Data (Restore)**: Specify a location: **\\\\SRV1\MigData$\PC1**
|
||||
|
||||
5. When OS installation has started on PC1, re-enable the external network adapter on SRV1 by typing the following command on SRV1:
|
||||
|
||||
```
|
||||
@ -606,7 +616,9 @@ At a high level, the computer replace process consists of:<BR>
|
||||
|
||||
8. When PC3 has completed installing the OS, sign in to PC3 using the contoso\administrator account. When the PC completes updating, click **Finish**.
|
||||
|
||||
9. Verify that settings have been migrated from PC1, and then shut down PC3 in preparation for the next procedure.
|
||||
9. Verify that settings have been migrated from PC1. This completes demonstration of the replace procedure.
|
||||
|
||||
10. Shut down PC3 in preparation for the [next](windows-10-poc-sc-config-mgr.md) procedure.
|
||||
|
||||
## Troubleshooting logs, events, and utilities
|
||||
|
||||
|
||||
@ -131,7 +131,6 @@ This following is a full list of BCD settings with friendly names which are igno
|
||||
| 0x15000052 | all| graphicsresolution|
|
||||
| 0x15000065 | all| displaymessage|
|
||||
| 0x15000066| all| displaymessageoverride|
|
||||
| 0x15000081 | all| logcontrol|
|
||||
| 0x16000009 | all| recoveryenabled|
|
||||
| 0x1600000b | all| badmemoryaccess|
|
||||
| 0x1600000f | all| traditionalkseg|
|
||||
|
||||
@ -32,6 +32,7 @@ The following sections provide a comprehensive list of BitLocker Group Policy se
|
||||
|
||||
The following policy settings can be used to determine how a BitLocker-protected drive can be unlocked.
|
||||
|
||||
- [Allow devices with Secure Boot and protect DMS ports to opt out of preboot PIN](#bkmk-hstioptout)
|
||||
- [Allow network unlock at startup](#bkmk-netunlock)
|
||||
- [Require additional authentication at startup](#bkmk-unlockpol1)
|
||||
- [Allow enhanced PINs for startup](#bkmk-unlockpol2)
|
||||
@ -85,6 +86,55 @@ The following policies are used to support customized deployment scenarios in yo
|
||||
- [Allow access to BitLocker-protected fixed data drives from earlier versions of Windows](#bkmk-depopt4)
|
||||
- [Allow access to BitLocker-protected removable data drives from earlier versions of Windows](#bkmk-depopt5)
|
||||
|
||||
### <a href="" id="bkmk-hstioptout"></a>Allow devices with Secure Boot and protect DMS ports to opt out of preboot PIN
|
||||
|
||||
This policy setting allows users on devices that are compliant with InstantGo or the Microsoft Hardware Security Test Interface (HSTI) to not have a PIN for preboot authentication.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Policy description</strong></p></td>
|
||||
<td align="left"><p>With this policy setting, you can allow TPM-only protection for newer, more secure devices, such as devices that support InstantGo or HSTI, while requiring PIN on older devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Introduced</strong></p></td>
|
||||
<td align="left"><p>Windows 10, version 1703</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Drive type</strong></p></td>
|
||||
<td align="left"><p>Operating system drives</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Policy path</strong></p></td>
|
||||
<td align="left"><p>Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption\Operating System Drives</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Conflicts</strong></p></td>
|
||||
<td align="left"><p>This setting overrides the <b>Require startup PIN with TPM</b> option of the [Require additional authentication at startup](#bkmk-unlockpol1) policy on compliant hardware.
|
||||
|
||||
</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>When enabled</strong></p></td>
|
||||
<td align="left"><p>Users on InstantGo and HSTI compliant devices will have the choice to turn on BitLocker without preboot authentication.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>When disabled or not configured</strong></p></td>
|
||||
<td align="left"><p>The options of the [Require additional authentication at startup](#bkmk-unlockpol1) policy apply.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
**Reference**
|
||||
|
||||
The preboot authentication option <b>Require startup PIN with TPM</b> of the [Require additional authentication at startup](#bkmk-unlockpol1) policy is often enabled to help ensure security for older devices that do not support InstantGo.
|
||||
But visually impaired users have no audible way to know when to enter a PIN.
|
||||
This setting enables an exception to the PIN-required policy on secure hardware.
|
||||
|
||||
### <a href="" id="bkmk-netunlock"></a>Allow network unlock at startup
|
||||
|
||||
This policy controls a portion of the behavior of the Network Unlock feature in BitLocker. This policy is required to enable BitLocker Network Unlock on a network because it allows clients running BitLocker to create the necessary network key protector during encryption. This policy is used in addition to the BitLocker Drive Encryption Network Unlock Certificate security policy (located in the **Public Key Policies** folder of Local Computer Policy) to allow systems that are connected to a trusted network to properly utilize the Network Unlock feature.
|
||||
|
||||
@ -22,9 +22,9 @@ This policy setting determines whether the Lightweight Directory Access Protocol
|
||||
|
||||
Unsigned network traffic is susceptible to man-in-the-middle attacks, where an intruder captures packets between the server and the client device and modifies them before forwarding them to the client device. In the case of an LDAP server, this means that a malicious user can cause a client device to make decisions based on false records from the LDAP directory. You can lower the risk of a malicious user accomplishing this in a corporate network by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPsec) Authentication Header mode, which provides mutual authentication and packet integrity for IP traffic, can make all types of man-in-the-middle attacks extremely difficult.
|
||||
|
||||
This setting does not have any impact on LDAP simple bind or LDAP simple bind through SSL.
|
||||
This setting does not have any impact on LDAP simple bind through SSL (LDAP TCP/636).
|
||||
|
||||
If signing is required, then LDAP simple bind and LDAP simple bind through SSL requests are rejected.
|
||||
If signing is required, then LDAP simple binds not using SSL are rejected (LDAP TCP/389).
|
||||
|
||||
>**Caution:** If you set the server to Require signature, you must also set the client device. Not setting the client device results in loss of connection with the server.
|
||||
|
||||
|
||||
@ -26,8 +26,8 @@ This section addresses issues that might arise as you use the Windows Defender A
|
||||
If you encounter a server error when trying to access the service, you’ll need to change your browser cookie settings.
|
||||
Configure your browser to allow cookies.
|
||||
|
||||
### Data is missing on the portal
|
||||
If data is missing on the Windows Defender ATP portal it’s possible that proxy settings are blocking it.
|
||||
### Elements or data missing on the portal
|
||||
If some UI elements or data is missing on the Windows Defender ATP portal it’s possible that proxy settings are blocking it.
|
||||
|
||||
Make sure that `*.securitycenter.windows.com` is included the proxy whitelist.
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ In Windows 10, version 1607, the following Group Policy settings apply only to W
|
||||
| **Start layout** | User Configuration\Administrative Templates\Start Menu and Taskbar | For more info, see [Manage Windows 10 Start layout options and policies](windows-10-start-layout-options-and-policies.md) |
|
||||
| **Turn off the Store application** | Computer Configuration > Administrative Templates > Windows Components > Store > Turn off the Store application<br><br>User Configuration > Administrative Templates > Windows Components > Store > Turn off the Store application | For more info, see [Knowledge Base article# 3135657](https://support.microsoft.com/kb/3135657). |
|
||||
| **Only display the private store within the Windows Store app** | Computer Configuration > Administrative Templates > Windows Components > Store > Only display the private store within the Windows Store app<br><br>User Configuration > Administrative Templates > Windows Components > Store > Only display the private store within the Windows Store app | For more info, see [Manage access to private store](manage-access-to-private-store.md) |
|
||||
| **Don't search the web or display web results** | Computer Configuration\Administrative Templates\Windows Components\Search\Don't search the web or display web results | For more info, see [Cortana integration in your enterprise](manage-cortana-in-enterprise.md) |
|
||||
| **Don't search the web or display web results** | Computer Configuration\Administrative Templates\Windows Components\Search\Don't search the web or display web results | For more info, see [Cortana integration in your enterprise](cortana-at-work-overview.md) |
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user