mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-24 23:03:42 +00:00
Merge branch 'master' into asr-working
This commit is contained in:
Denise Vangel-MSFT
GitHub
@ -7,7 +7,9 @@
|
||||
"**/*.yml"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**"
|
||||
"**/obj/**",
|
||||
"**/includes/**",
|
||||
"**/shortdesc/**"
|
||||
]
|
||||
}
|
||||
],
|
||||
@ -28,7 +30,10 @@
|
||||
"breadcrumb_path": "/microsoft-edge/deploy/breadcrumb/toc.json",
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.technology": "microsoft-edge",
|
||||
"audience": "ITPro",
|
||||
"ms.topic": "article",
|
||||
"manager": "laurawi",
|
||||
"ms.prod": "edge",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
|
||||
@ -45,7 +45,7 @@ If you're having trouble deciding whether Microsoft Edge is right for your organ
|
||||
|
||||
|
||||
## Configure the Enterprise Mode Site List
|
||||
[Available policy options](includes/configure-enterprise-mode-site-list-include.md)
|
||||
[!INCLUDE [Available policy options](includes/configure-enterprise-mode-site-list-include.md)]
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -3,7 +3,8 @@ author: eavena
|
||||
ms.author: eravena
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
@ -34,7 +35,7 @@ ms.topic: include
|
||||
#### MDM settings
|
||||
- **MDM name:** Browser/[AllowFlash](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser\#browser-allowflash)
|
||||
- **Supported devices:** Desktop
|
||||
- **Supported devices:** Desktop
|
||||
- **URI full path:** ./Vendor/MSFT/Policy/Config/Browser/AllowFlash
|
||||
- **Data type:** Integer
|
||||
|
||||
#### Registry settings
|
||||
|
||||
@ -38,8 +38,9 @@
|
||||
|
||||
### Related Policies
|
||||
|
||||
[Show message opening sites in IE](../available-policies.md#show-message-when-opening-sites-in-internet-explorer): [!INCLUDE
|
||||
[show-message-when-opening-sites-in-ie-shortdesc](../shortdesc/show-message-when-opening-sites-in-ie-shortdesc.md)]
|
||||
[Show message opening sites in IE](../available-policies.md#show-message-when-opening-sites-in-internet-explorer)
|
||||
|
||||
[!INCLUDE [show-message-when-opening-sites-in-ie-shortdesc](../shortdesc/show-message-when-opening-sites-in-ie-shortdesc.md)]
|
||||
|
||||
### Related topics
|
||||
|
||||
|
||||
@ -3,12 +3,13 @@ title: Deploy Microsoft Edge kiosk mode
|
||||
description: Microsoft Edge kiosk mode works with assigned access to allow IT admins to create a tailored browsing experience designed for kiosk devices. To use Microsoft Edge kiosk mode, you must configure Microsoft Edge as an application in assigned access.
|
||||
ms.assetid:
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
author: eavena
|
||||
ms.author: eravena
|
||||
ms.prod: edge
|
||||
ms.sitesec: library
|
||||
ms.sitesec: library
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 10/29/2018
|
||||
---
|
||||
|
||||
@ -5,7 +5,7 @@ ms.pagetype: security
|
||||
description: Use this section to learn about how to turn on Enterprise Mode.
|
||||
author: eavena
|
||||
ms.author: eravena
|
||||
ms.prod: edge, ie11
|
||||
ms.prod: edge
|
||||
ms.assetid:
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -24,10 +24,11 @@
|
||||
"globalMetadata": {
|
||||
"breadcrumb_path": "/internet-explorer/breadcrumb/toc.json",
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.author": "shortpatti",
|
||||
"author": "eross-msft",
|
||||
"audience": "ITPro",
|
||||
"ms.technology": "internet-explorer",
|
||||
"ms.prod": "ie11",
|
||||
"ms.topic": "article",
|
||||
"manager": "laurawi",
|
||||
"ms.date": "04/05/2017",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
|
||||
@ -7,7 +7,8 @@ author: lomayor
|
||||
ms.prod: ie11
|
||||
ms.assetid: 909ca359-5654-4df9-b9fb-921232fc05f5
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
title: Enterprise Mode schema v.2 guidance (Internet Explorer 11 for IT Pros)
|
||||
ms.sitesec: library
|
||||
|
||||
@ -3,10 +3,11 @@ ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
description: How to use the Browsing Options page in the IEAK 11 Customization Wizard to manage items in the Favorites, Favorites Bar, and Feeds section.
|
||||
author: lomayor
|
||||
ms.prod: ie111
|
||||
ms.prod: ie11
|
||||
ms.assetid: d6bd71ba-5df3-4b8c-8bb5-dcbc50fd974e
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
title: Use the Browsing Options page in the IEAK 11 Wizard (Internet Explorer Administration Kit 11 for IT Pros)
|
||||
ms.sitesec: library
|
||||
|
||||
@ -4,10 +4,11 @@ ms.mktglfcycl: plan
|
||||
description: Learn about the version of the IEAK 11 you should run, based on your license agreement.
|
||||
author: lomayor
|
||||
ms.author: lomayor
|
||||
ms.prod: ie11, ieak11
|
||||
ms.prod: ie11
|
||||
ms.assetid: 69d25451-08af-4db0-9daa-44ab272acc15
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
title: Determine the licensing version and features to use in IEAK 11 (Internet Explorer Administration Kit 11 for IT Pros)
|
||||
ms.sitesec: library
|
||||
ms.date: 10/23/2018
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
ms.mktglfcycl: deploy
|
||||
description: The landing page for IE11 that lets you access the documentation.
|
||||
author: shortpatti
|
||||
ms.prod: IE11
|
||||
ms.prod: ie11
|
||||
title: Internet Explorer 11 (IE11) (Internet Explorer 11 for IT Pros)
|
||||
assetid: be3dc32e-80d9-4d9f-a802-c7db6c50dbe0
|
||||
ms.sitesec: library
|
||||
|
||||
@ -1,13 +1,15 @@
|
||||
# [Microsoft HoloLens](index.md)
|
||||
# [What's new in HoloLens](hololens-whats-new.md)
|
||||
# [HoloLens in the enterprise: requirements and FAQ](hololens-requirements.md)
|
||||
# [Set up HoloLens](hololens-setup.md)
|
||||
|
||||
# Deploy HoloLens in a commercial environment
|
||||
## [Overview and deployment planning](hololens-requirements.md)
|
||||
## [Configure HoloLens using a provisioning package](hololens-provisioning.md)
|
||||
## [Enroll HoloLens in MDM](hololens-enroll-mdm.md)
|
||||
|
||||
# Device Management
|
||||
## [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md)
|
||||
## [Install localized version of HoloLens](hololens-install-localized.md)
|
||||
## [Configure HoloLens using a provisioning package](hololens-provisioning.md)
|
||||
## [Enroll HoloLens in MDM](hololens-enroll-mdm.md)
|
||||
## [Manage updates to HoloLens](hololens-updates.md)
|
||||
## [Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md)
|
||||
## [Use the HoloLens Clicker](hololens-clicker.md)
|
||||
|
||||
@ -32,7 +32,8 @@
|
||||
"breadcrumb_path": "/hololens/breadcrumb/toc.json",
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "jdecker",
|
||||
"audience": "ITPro",
|
||||
"manager": "laurawi",
|
||||
"ms.date": "04/05/2017",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
|
||||
@ -102,6 +102,6 @@ Provisioning packages are files created by the Windows Configuration Designer to
|
||||
|
||||
Encryption is silent on HoloLens. To verify the device encryption status:
|
||||
|
||||
- On HoloLens, go to **Settings** > **System** > **About**. **BitLocker** is **enabled** if the device is encrypted.
|
||||
- On HoloLens, go to **Settings** > **System** > **About**. **BitLocker** is **enabled** if the device is encrypted.
|
||||
|
||||
|
||||
|
||||
@ -22,9 +22,9 @@ manager: dansimp
|
||||
For a complete list of Update policies, see [Policies supported by Windows Holographic for Business](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#a-href-idhololenspoliciesapolicies-supported-by-windows-holographic-for-business).
|
||||
|
||||
To configure how and when updates are applied, use the following policies:
|
||||
- [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate)
|
||||
- [Update/ScheduledInstallDay](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallday)
|
||||
- [Update/ScheduledInstallTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstalltime)
|
||||
- [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate)
|
||||
- [Update/ScheduledInstallDay](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallday)
|
||||
- [Update/ScheduledInstallTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstalltime)
|
||||
|
||||
To turn off the automatic check for updates, set the following policy to value **5** – Turn off Automatic Updates:
|
||||
- [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate)
|
||||
|
||||
BIN
devices/hololens/images/hololens2-side-render-medium.png
Normal file
BIN
devices/hololens/images/hololens2-side-render-medium.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1017 KiB |
BIN
devices/hololens/images/hololens2-side-render-small.png
Normal file
BIN
devices/hololens/images/hololens2-side-render-small.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 247 KiB |
BIN
devices/hololens/images/hololens2-side-render-xs.png
Normal file
BIN
devices/hololens/images/hololens2-side-render-xs.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
@ -3,6 +3,7 @@ title: Microsoft HoloLens (HoloLens)
|
||||
description: Landing page for HoloLens commercial and enterprise management.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
ms.assetid: 0947f5b3-8f0f-42f0-aa27-6d2cad51d040
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
ms.topic: article
|
||||
@ -18,7 +19,9 @@ ms.date: 07/14/2019
|
||||
|
||||
<p>Now, with the introduction of HoloLens 2, every device provides commercial ready management enhanced by the reliability, security, and scalability of cloud and AI services from Microsoft.</p>
|
||||
|
||||
</td><td align="left" style="border: 0px"><img alt="HoloLens 2 side view" src="./images/hololens2-side-render.png"/></td></tr>
|
||||
<p>To learn more about HoloLens 2 for developers, check out the <a href="https://docs.microsoft.com/windows/mixed-reality/">mixed reality developer documentation</a>.</p>
|
||||
|
||||
</td><td align="left" style="border: 0px"><img alt="HoloLens 2 side view" src="images/hololens2-side-render-xs.png"/></td></tr>
|
||||
</tbody></table>
|
||||
|
||||
## Guides in this section
|
||||
@ -26,7 +29,7 @@ ms.date: 07/14/2019
|
||||
| Guide | Description |
|
||||
| --- | --- |
|
||||
| [Get started with HoloLens](hololens-setup.md) | Set up HoloLens for the first time. |
|
||||
| [Set up HoloLens in the enterprise](hololens-requirements.md) | Configure HoloLens for scale enterprise deployment and ongoing device management. |
|
||||
| [Deploy HoloLens in a commercial environment](hololens-requirements.md) | Configure HoloLens for scale enterprise deployment and ongoing device management. |
|
||||
| [Install and manage applications on HoloLens](hololens-install-apps.md) |Install and manage important applications on HoloLens at scale. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Get support](https://support.microsoft.com/products/hololens) |Connect with Microsoft support resources for HoloLens in enterprise. |
|
||||
|
||||
@ -27,7 +27,9 @@
|
||||
"breadcrumb_path": "/surface-hub/breadcrumb/toc.json",
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.technology": "windows",
|
||||
"audience": "ITPro",
|
||||
"ms.topic": "article",
|
||||
"manager": "laurawi",
|
||||
"ms.mktglfcycl": "manage",
|
||||
"ms.sitesec": "library",
|
||||
"ms.date": "05/23/2017",
|
||||
|
||||
@ -97,4 +97,4 @@ If you insert a USB thumb drive with a provisioning package into one of the USB
|
||||
|
||||
 <br>
|
||||
|
||||
4. Follow the instructions to complete first time Setup.
|
||||
4. Follow the instructions to complete first time Setup.
|
||||
|
||||
@ -26,6 +26,18 @@ Please refer to the “[Surface Hub Important Information](https://support.micro
|
||||
|
||||
## Windows 10 Team Creators Update 1703
|
||||
|
||||
<details>
|
||||
<summary>June 18, 2019—update for Team edition based on KB4503289* (OS Build 15063.1897)</summary>
|
||||
|
||||
This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
|
||||
|
||||
* Addresses an issue with log collection for Microsoft Surface Hub 2S.
|
||||
* Addresses an issue preventing a user from signing in to a Microsoft Surface Hub device with an Azure Active Directory account. This issue occurs because a previous session did not end successfully.
|
||||
|
||||
Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
|
||||
*[KB4503289](https://support.microsoft.com/help/4503289)
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>May 28, 2019—update for Team edition based on KB4499162* (OS Build 15063.1835)</summary>
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ To get Whiteboard to Whiteboard collaboration up and running, you’ll need to m
|
||||
- Currently not utilizing Office 365 Germany or Office 365 operated by 21Vianet
|
||||
- Surface Hub needs to be updated to Windows 10, version 1607 or newer
|
||||
- Port 443 needs to be open since Whiteboard makes standard https requests
|
||||
- Whiteboard.ms, wbd.ms, \*.onenote.com, and your company's SharePoint tenant domain URLs need to be whitelisted for proxies
|
||||
- Whiteboard.ms, whiteboard.microsoft.com, wbd.ms, \*.onenote.com, and your company's SharePoint tenant domain URLs need to be whitelisted for proxies
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
@ -68,4 +68,5 @@ After you’re done, you can export a copy of the Whiteboard collaboration for y
|
||||
## Related topics
|
||||
|
||||
- [Windows 10 Creators Update for Surface Hub](https://www.microsoft.com/surface/support/surface-hub/windows-10-creators-update-surface-hub)
|
||||
- [Support documentation for Microsoft Whiteboard](https://support.office.com/en-us/article/Whiteboard-Help-0c0f2aa0-b1bb-491c-b814-fd22de4d7c01)
|
||||
|
||||
- [Support documentation for Microsoft Whiteboard](https://support.office.com/article/Whiteboard-Help-0c0f2aa0-b1bb-491c-b814-fd22de4d7c01)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# [Surface](index.md)
|
||||
|
||||
## Get started
|
||||
## [Get started](get-started.md)
|
||||
|
||||
## Overview
|
||||
### [Surface Pro Tech specs](https://www.microsoft.com/surface/devices/surface-pro/tech-specs)
|
||||
|
||||
@ -25,7 +25,9 @@
|
||||
"breadcrumb_path": "/surface/breadcrumb/toc.json",
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"ms.technology": "windows",
|
||||
"audience": "ITPro",
|
||||
"ms.topic": "article",
|
||||
"manager": "laurawi",
|
||||
"ms.date": "05/09/2017",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
|
||||
@ -61,8 +61,8 @@ The following steps show you how to create a deployment share for Windows 10 tha
|
||||
>[!NOTE]
|
||||
>As of SDA version 1.96.0405, SDA will install only the components of the Windows ADK that are required for deployment, as follows:
|
||||
> * Deployment tools
|
||||
> * User State Migration Tool (USMT)
|
||||
> * Windows Preinstallation Environment (WinPE)
|
||||
> * User State Migration Tool (USMT)
|
||||
> * Windows Preinstallation Environment (WinPE)
|
||||
|
||||
> [!NOTE]
|
||||
> As of SDA version 1.96.0405, SDA will install and use MDT 2013 Update 2. Earlier versions of SDA are compatible only with MDT 2013 Update 1.
|
||||
@ -75,11 +75,11 @@ The following steps show you how to create a deployment share for Windows 10 tha
|
||||
|
||||
- **Local Path** – Specify or browse to a location on the local storage device where you would like to store the deployment share files for the Windows 10 SDA deployment share. For example, **E:\\SDAWin10\\** is the location specified in Figure 3.
|
||||
|
||||
- **Share Name** – Specify a name for the file share that will be used to access the deployment share on this server from the network. For example, **SDAWin10** is the deployment share name shown in Figure 3. The local path folder is automatically shared by the SDA scripts under this name to the group **Everyone** with a permission level of **Full Control**.
|
||||
- **Share Name** – Specify a name for the file share that will be used to access the deployment share on this server from the network. For example, **SDAWin10** is the deployment share name shown in Figure 3. The local path folder is automatically shared by the SDA scripts under this name to the group **Everyone** with a permission level of **Full Control**.
|
||||
|
||||
- **Windows 10 Deployment Services**
|
||||
|
||||
- Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](https://technet.microsoft.com/library/jj648426.aspx) for more information about how to configure Windows Deployment Services for PXE boot.
|
||||
- Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](https://technet.microsoft.com/library/jj648426.aspx) for more information about how to configure Windows Deployment Services for PXE boot.
|
||||
|
||||
- **Windows 10 Source Files**
|
||||
|
||||
|
||||
@ -103,39 +103,45 @@ The sample scripts include examples of how to set Surface UEFI settings and how
|
||||
|
||||
### Specify certificate and package names
|
||||
|
||||
The first region of the script that you need to modify is the portion that specifies and loads the SEMM certificate, and also indicates the names for the SEMM configuration package and SEMM reset package. The certificate and package names are specified on lines 56 through 67 in the ConfigureSEMM.ps1 script:
|
||||
The first region of the script that you need to modify is the portion that specifies and loads the SEMM certificate, and also indicates SurfaceUEFIManager version, the names for the SEMM configuration package and SEMM reset package. The certificate name and SurfaceUEFIManager version are specified on lines 56 through 73 in the ConfigureSEMM.ps1 script:
|
||||
|
||||
```
|
||||
56 $WorkingDirPath = split-path -parent $MyInvocation.MyCommand.Definition
|
||||
57 $packageRoot = "$WorkingDirPath\Config"
|
||||
58
|
||||
59 if (-not (Test-Path $packageRoot)) { New-Item -ItemType Directory -Force -Path $packageRoot }
|
||||
60 Copy-Item "$WorkingDirPath\FabrikamOwnerSigner.pfx" $packageRoot
|
||||
61
|
||||
62 $privateOwnerKey = Join-Path -Path $packageRoot -ChildPath "FabrikamOwnerSigner.pfx"
|
||||
63 $ownerPackageName = Join-Path -Path $packageRoot -ChildPath "FabrikamSignerProvisioningPackage.pkg"
|
||||
64 $resetPackageName = Join-Path -Path $packageRoot -ChildPath "FabrikamUniversalResetPackage.pkg"
|
||||
65
|
||||
66 # If your PFX file requires a password then it can be set here, otherwise use a blank string.
|
||||
67 $password = "1234"
|
||||
58 $certName = "FabrikamSEMMSample.pfx"
|
||||
59 $DllVersion = "2.26.136.0"
|
||||
60
|
||||
61 $certNameOnly = [System.IO.Path]::GetFileNameWithoutExtension($certName)
|
||||
62 $ProvisioningPackage = $certNameOnly + "ProvisioningPackage.pkg"
|
||||
63 $ResetPackage = $certNameOnly + "ResetPackage.pkg"
|
||||
64
|
||||
65 if (-not (Test-Path $packageRoot)) { New-Item -ItemType Directory -Force -Path $packageRoot }
|
||||
66 Copy-Item "$WorkingDirPath\$certName" $packageRoot
|
||||
67
|
||||
68 $privateOwnerKey = Join-Path -Path $packageRoot -ChildPath $certName
|
||||
69 $ownerPackageName = Join-Path -Path $packageRoot -ChildPath $ProvisioningPackage
|
||||
70 $resetPackageName = Join-Path -Path $packageRoot -ChildPath $ResetPackage
|
||||
71
|
||||
72 # If your PFX file requires a password then it can be set here, otherwise use a blank string.
|
||||
73 $password = "1234"
|
||||
```
|
||||
|
||||
Replace the **FabrikamOwnerSigner.pfx** value for the **$privateOwnerKey** variable with the name of your SEMM Certificate file on both lines 60 and 62. The script will create a working directory (named Config) in the folder where your scripts are located, and will then copy the certificate file to this working directory.
|
||||
Replace the **FabrikamSEMMSample.pfx** value for the **$certName** variable with the name of your SEMM Certificate file on line 58. The script will create a working directory (named Config) in the folder where your scripts are located, and will then copy the certificate file to this working directory.
|
||||
|
||||
Replace the **FabrikamSignerProvisioningPackage.pkg** and **FabrikamUniversalResetPackage.pkg** values on lines 63 and 64 to define the **$ownerPackageName** and **$resetPackageName** variables with your desired names for the SEMM configuration and reset packages. These packages will also be created in the Config directory and hold the configuration for Surface UEFI settings and permissions generated by the script.
|
||||
Owner package and reset package will also be created in the Config directory and hold the configuration for Surface UEFI settings and permissions generated by the script.
|
||||
|
||||
On line 67, replace the value of the **$password** variable, from 1234, to the password for your certificate file. If a password is not required, delete the **1234** text.
|
||||
On line 73, replace the value of the **$password** variable, from 1234, to the password for your certificate file. If a password is not required, delete the **1234** text.
|
||||
|
||||
>[!Note]
|
||||
>The last two characters of the certificate thumbprint are required to enroll a device in SEMM. This script will display these digits to the user, which allows the user or technician to record these digits before the system reboots to enroll the device in SEMM. The script uses the following code, found on lines 144-149, to accomplish this:
|
||||
>The last two characters of the certificate thumbprint are required to enroll a device in SEMM. This script will display these digits to the user, which allows the user or technician to record these digits before the system reboots to enroll the device in SEMM. The script uses the following code, found on lines 150-155, to accomplish this:
|
||||
|
||||
```
|
||||
144 # Device owners will need the last two characters of the thumbprint to accept SEMM ownership.
|
||||
145 # For convenience we get the thumbprint here and present to the user.
|
||||
146 $pw = ConvertTo-SecureString $password -AsPlainText -Force
|
||||
147 $certPrint = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2
|
||||
148 $certPrint.Import($privateOwnerKey, $pw, [System.Security.Cryptography.X509Certificates.X509KeyStorageFlags]::DefaultKeySet)
|
||||
149 Write-Host "Thumbprint =" $certPrint.Thumbprint
|
||||
150 # Device owners will need the last two characters of the thumbprint to accept SEMM ownership.
|
||||
151 # For convenience we get the thumbprint here and present to the user.
|
||||
152 $pw = ConvertTo-SecureString $password -AsPlainText -Force
|
||||
153 $certPrint = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2
|
||||
154 $certPrint.Import($privateOwnerKey, $pw, [System.Security.Cryptography.X509Certificates.X509KeyStorageFlags]::DefaultKeySet)
|
||||
155 Write-Host "Thumbprint =" $certPrint.Thumbprint
|
||||
```
|
||||
|
||||
Administrators with access to the certificate file (.pfx) can read the thumbprint at any time by opening the .pfx file in CertMgr. To view the thumbprint with CertMgr, follow this process:
|
||||
@ -153,46 +159,47 @@ Administrators with access to the certificate file (.pfx) can read the thumbprin
|
||||
|
||||
### Configure permissions
|
||||
|
||||
The first region of the script where you will specify the configuration for Surface UEFI is the **Configure Permissions** region. This region begins at line 202 in the sample script with the comment **# Configure Permissions** and continues to line 238. The following code fragment first sets permissions to all Surface UEFI settings so that they may be modified by SEMM only, then adds explicit permissions to allow the local user to modify the Surface UEFI password, TPM, and front and rear cameras:
|
||||
The first region of the script where you will specify the configuration for Surface UEFI is the **Configure Permissions** region. This region begins at line 210 in the sample script with the comment **# Configure Permissions** and continues to line 247. The following code fragment first sets permissions to all Surface UEFI settings so that they may be modified by SEMM only, then adds explicit permissions to allow the local user to modify the Surface UEFI password, TPM, and front and rear cameras:
|
||||
|
||||
```
|
||||
202 # Configure Permissions
|
||||
203 foreach ($uefiV2 IN $surfaceDevices.Values) {
|
||||
204 # Here we define which "identities" will be allowed to modify which settings
|
||||
205 # PermissionSignerOwner = The primary SEMM enterprise owner identity
|
||||
206 # PermissionLocal = The user when booting to the UEFI pre-boot GUI
|
||||
207 # PermissionSignerUser, PermissionSignerUser1, PermissionSignerUser2 =
|
||||
208 # Additional user identities created so that the signer owner
|
||||
209 # can delegate permission control for some settings.
|
||||
210 $ownerOnly = [Microsoft.Surface.IUefiSetting]::PermissionSignerOwner
|
||||
211 $ownerAndLocalUser = ([Microsoft.Surface.IUefiSetting]::PermissionSignerOwner -bor [Microsoft.Surface.IUefiSetting]::PermissionLocal)
|
||||
212
|
||||
213 # Make all permissions owner only by default
|
||||
214 foreach ($setting IN $uefiV2.Settings.Values) {
|
||||
215 $setting.ConfiguredPermissionFlags = $ownerOnly
|
||||
216 }
|
||||
217 # Allow the local user to change their own password
|
||||
218 $uefiV2.SettingsById[501].ConfiguredPermissionFlags = $ownerAndLocalUser
|
||||
219
|
||||
220 # Allow the local user to change the state of the TPM
|
||||
221 $uefiV2.Settings["Trusted Platform Module (TPM)"].ConfiguredPermissionFlags = $ownerAndLocalUser
|
||||
222
|
||||
223 # Allow the local user to change the state of the Front and Rear cameras
|
||||
224 $uefiV2.SettingsById[302].ConfiguredPermissionFlags = $ownerAndLocalUser
|
||||
225 $uefiV2.SettingsById[304].ConfiguredPermissionFlags = $ownerAndLocalUser
|
||||
226
|
||||
227
|
||||
228 # Create a unique package name based on family and LSV.
|
||||
229 # We will choose a name that can be parsed by later scripts.
|
||||
230 $packageName = $uefiV2.SurfaceUefiFamily + "^Permissions^" + $lsv + ".pkg"
|
||||
231 $fullPackageName = Join-Path -Path $packageRoot -ChildPath $packageName
|
||||
232
|
||||
233 # Build and sign the Permission package then save it to a file.
|
||||
234 $permissionPackageStream = $uefiV2.BuildAndSignPermissionPackage($privateOwnerKey, $password, "", $null, $lsv)
|
||||
235 $permissionPackage = New-Object System.IO.Filestream($fullPackageName, [System.IO.FileMode]::CreateNew, [System.IO.FileAccess]::Write)
|
||||
236 $permissionPackageStream.CopyTo($permissionPackage)
|
||||
237 $permissionPackage.Close()
|
||||
238 }
|
||||
210 # Configure Permissions
|
||||
211 foreach ($uefiV2 IN $surfaceDevices.Values) {
|
||||
212 if ($uefiV2.SurfaceUefiFamily -eq $Device.Model) {
|
||||
213 Write-Host "Configuring permissions"
|
||||
214 Write-Host $Device.Model
|
||||
215 Write-Host "======================="
|
||||
216
|
||||
217 # Here we define which "identities" will be allowed to modify which settings
|
||||
218 # PermissionSignerOwner = The primary SEMM enterprise owner identity
|
||||
219 # PermissionLocal = The user when booting to the UEFI pre-boot GUI
|
||||
220 # PermissionSignerUser, PermissionSignerUser1, PermissionSignerUser2 =
|
||||
221 # Additional user identities created so that the signer owner
|
||||
222 # can delegate permission control for some settings.
|
||||
223 $ownerOnly = [Microsoft.Surface.IUefiSetting]::PermissionSignerOwner
|
||||
224 $ownerAndLocalUser = ([Microsoft.Surface.IUefiSetting]::PermissionSignerOwner -bor [Microsoft.Surface.IUefiSetting]::PermissionLocal)
|
||||
225
|
||||
226 # Make all permissions owner only by default
|
||||
227 foreach ($setting IN $uefiV2.Settings.Values) {
|
||||
228 $setting.ConfiguredPermissionFlags = $ownerOnly
|
||||
229 }
|
||||
230
|
||||
231 # Allow the local user to change their own password
|
||||
232 $uefiV2.SettingsById[501].ConfiguredPermissionFlags = $ownerAndLocalUser
|
||||
233
|
||||
234 Write-Host ""
|
||||
235
|
||||
236 # Create a unique package name based on family and LSV.
|
||||
237 # We will choose a name that can be parsed by later scripts.
|
||||
238 $packageName = $uefiV2.SurfaceUefiFamily + "^Permissions^" + $lsv + ".pkg"
|
||||
239 $fullPackageName = Join-Path -Path $packageRoot -ChildPath $packageName
|
||||
240
|
||||
241 # Build and sign the Permission package then save it to a file.
|
||||
242 $permissionPackageStream = $uefiV2.BuildAndSignPermissionPackage($privateOwnerKey, $password, "", $null, $lsv)
|
||||
243 $permissionPackage = New-Object System.IO.Filestream($fullPackageName, [System.IO.FileMode]::CreateNew, [System.IO.FileAccess]::Write)
|
||||
244 $permissionPackageStream.CopyTo($permissionPackage)
|
||||
245 $permissionPackage.Close()
|
||||
246 }
|
||||
247 }
|
||||
```
|
||||
|
||||
Each **$uefiV2** variable identifies a Surface UEFI setting by setting name or ID, and then configures the permissions to one of the following values:
|
||||
@ -204,69 +211,169 @@ You can find information about the available settings names and IDs for Surface
|
||||
|
||||
### Configure settings
|
||||
|
||||
The second region of the script where you will specify the configuration for Surface UEFI is the **Configure Settings** region of the ConfigureSEMM.ps1 script, which configures whether each setting is enabled or disabled. The sample script includes instructions to set all settings to their default values. The script then provides explicit instructions to disable IPv6 for PXE Boot and to leave the Surface UEFI Administrator password unchanged. You can find this region beginning with the **# Configure Settings** comment at line 282 through line 312 in the sample script. The region appears as follows:
|
||||
The second region of the script where you will specify the configuration for Surface UEFI is the **Configure Settings** region of the ConfigureSEMM.ps1 script, which configures whether each setting is enabled or disabled. The sample script includes instructions to set all settings to their default values. The script then provides explicit instructions to disable IPv6 for PXE Boot and to leave the Surface UEFI Administrator password unchanged. You can find this region beginning with the **# Configure Settings** comment at line 291 through line 335 in the sample script. The region appears as follows:
|
||||
|
||||
```
|
||||
282 # Configure Settings
|
||||
283 foreach ($uefiV2 IN $surfaceDevices.Values) {
|
||||
284 # In this demo, we will start by setting every setting to the default factory setting.
|
||||
285 # You may want to start by doing this in your scripts
|
||||
286 # so that every setting gets set to a known state.
|
||||
287 foreach ($setting IN $uefiV2.Settings.Values) {
|
||||
288 $setting.ConfiguredValue = $setting.DefaultValue
|
||||
289 }
|
||||
290
|
||||
291 # If you want to set something to a different value from the default,
|
||||
292 # here are examples of how to accomplish this.
|
||||
293 $uefiV2.Settings["IPv6 for PXE Boot"].ConfiguredValue = "Disabled"
|
||||
294
|
||||
295 # If you want to leave the setting unmodified, set it to $null
|
||||
296 # PowerShell has issues setting things to $null so ClearConfiguredValue()
|
||||
297 # is supplied to do this explicitly.
|
||||
298 # Here is an example of leaving the UEFI administrator password as-is,
|
||||
299 # even after we initially set it to factory default above.
|
||||
300 $uefiV2.SettingsById[501].ClearConfiguredValue()
|
||||
301
|
||||
302 # Create a unique package name based on family and LSV.
|
||||
303 # We will choose a name that can be parsed by later scripts.
|
||||
304 $packageName = $uefiV2.SurfaceUefiFamily + "^Settings^" + $lsv + ".pkg"
|
||||
305 $fullPackageName = Join-Path -Path $packageRoot -ChildPath $packageName
|
||||
306
|
||||
307 # Build and sign the Settings package then save it to a file.
|
||||
308 $settingsPackageStream = $uefiV2.BuildAndSignSecuredSettingsPackage($privateOwnerKey, $password, "", $null, $lsv)
|
||||
309 $settingsPackage = New-Object System.IO.Filestream($fullPackageName, [System.IO.FileMode]::CreateNew, [System.IO.FileAccess]::Write)
|
||||
310 $settingsPackageStream.CopyTo($settingsPackage)
|
||||
311 $settingsPackage.Close()
|
||||
312 }
|
||||
291 # Configure Settings
|
||||
292 foreach ($uefiV2 IN $surfaceDevices.Values) {
|
||||
293 if ($uefiV2.SurfaceUefiFamily -eq $Device.Model) {
|
||||
294 Write-Host "Configuring settings"
|
||||
295 Write-Host $Device.Model
|
||||
296 Write-Host "===================="
|
||||
297
|
||||
298 # In this demo, we will start by setting every setting to the default factory setting.
|
||||
299 # You may want to start by doing this in your scripts
|
||||
300 # so that every setting gets set to a known state.
|
||||
301 foreach ($setting IN $uefiV2.Settings.Values) {
|
||||
302 $setting.ConfiguredValue = $setting.DefaultValue
|
||||
303 }
|
||||
304
|
||||
305 $EnabledValue = "Enabled"
|
||||
306 $DisabledValue = "Disabled"
|
||||
307
|
||||
308 # If you want to set something to a different value from the default,
|
||||
309 # here are examples of how to accomplish this.
|
||||
310 # This disables IPv6 PXE boot by name:
|
||||
311 $uefiV2.Settings["IPv6 for PXE Boot"].ConfiguredValue = $DisabledValue
|
||||
312
|
||||
313 # This disables IPv6 PXE Boot by ID:
|
||||
314 $uefiV2.SettingsById[400].ConfiguredValue = $DisabledValue
|
||||
315
|
||||
316 Write-Host ""
|
||||
317
|
||||
318 # If you want to leave the setting unmodified, set it to $null
|
||||
319 # PowerShell has issues setting things to $null so ClearConfiguredValue()
|
||||
320 # is supplied to do this explicitly.
|
||||
321 # Here is an example of leaving the UEFI administrator password as-is,
|
||||
322 # even after we initially set it to factory default above.
|
||||
323 $uefiV2.SettingsById[501].ClearConfiguredValue()
|
||||
324
|
||||
325 # Create a unique package name based on family and LSV.
|
||||
326 # We will choose a name that can be parsed by later scripts.
|
||||
327 $packageName = $uefiV2.SurfaceUefiFamily + "^Settings^" + $lsv + ".pkg"
|
||||
328 $fullPackageName = Join-Path -Path $packageRoot -ChildPath $packageName
|
||||
329
|
||||
330 # Build and sign the Settings package then save it to a file.
|
||||
331 $settingsPackageStream = $uefiV2.BuildAndSignSecuredSettingsPackage($privateOwnerKey, $password, "", $null, $lsv)
|
||||
332 $settingsPackage = New-Object System.IO.Filestream($fullPackageName, [System.IO.FileMode]::CreateNew, [System.IO.FileAccess]::Write)
|
||||
333 $settingsPackageStream.CopyTo($settingsPackage)
|
||||
334 $settingsPackage.Close()
|
||||
335 }
|
||||
```
|
||||
|
||||
Like the permissions set in the **Configure Permissions** section of the script, the configuration of each Surface UEFI setting is performed by defining the **$uefiV2** variable. For each line defining the **$uefiV2** variable, a Surface UEFI setting is identified by setting name or ID and the configured value is set to **Enabled** or **Disabled**.
|
||||
|
||||
If you do not want to alter the configuration of a Surface UEFI setting, for example to ensure that the Surface UEFI administrator password is not cleared by the action of resetting all Surface UEFI settings to their default, you can use **ClearConfiguredValue()** to enforce that this setting will not be altered. In the sample script, this is used on line 300 to prevent the clearing of the Surface UEFI Administrator password, identified in the sample script by its setting ID, **501**.
|
||||
If you do not want to alter the configuration of a Surface UEFI setting, for example to ensure that the Surface UEFI administrator password is not cleared by the action of resetting all Surface UEFI settings to their default, you can use **ClearConfiguredValue()** to enforce that this setting will not be altered. In the sample script, this is used on line 323 to prevent the clearing of the Surface UEFI Administrator password, identified in the sample script by its setting ID, **501**.
|
||||
|
||||
You can find information about the available settings names and IDs for Surface UEFI in the [Settings Names and IDs](#settings-names-and-ids) section later in this article.
|
||||
|
||||
### Settings registry key
|
||||
|
||||
To identify enrolled systems for Configuration Manager, the ConfigureSEMM.ps1 script writes a registry key that can be used to identify enrolled systems as having been installed with the SEMM configuration script. This key can be found at the following location:
|
||||
To identify enrolled systems for Configuration Manager, the ConfigureSEMM.ps1 script writes registry keys that can be used to identify enrolled systems as having been installed with the SEMM configuration script. These keys can be found at the following location:
|
||||
|
||||
`HKLM\SOFTWARE\Microsoft\Surface\SEMM\Enabled_Version1000`
|
||||
`HKLM\SOFTWARE\Microsoft\Surface\SEMM`
|
||||
|
||||
The following code fragment, found on lines 352-363, is used to write this registry key:
|
||||
The following code fragment, found on lines 380-477, is used to write these registry keys:
|
||||
|
||||
```
|
||||
352 $SurfaceRegKey = "HKLM:\SOFTWARE\Microsoft\Surface\SEMM"
|
||||
353 New-RegKey $SurfaceRegKey
|
||||
354 $SurfaceRegValue = Get-ItemProperty $SurfaceRegKey Enabled_Version1000 -ErrorAction SilentlyContinue
|
||||
355
|
||||
356 If ($SurfaceRegValue -eq $null)
|
||||
357 {
|
||||
358 New-ItemProperty -Path $SurfaceRegKey -Name Enabled_Version1000 -PropertyType String -Value 1 | Out-Null
|
||||
359 }
|
||||
360 Else
|
||||
361 {
|
||||
362 Set-ItemProperty -Path $SurfaceRegKey -Name Enabled_Version1000 -Value 1
|
||||
363 }
|
||||
380 # For SCCM or other management solutions that wish to know what version is applied, tattoo the LSV and current DateTime (in UTC) to the registry:
|
||||
381 $UTCDate = (Get-Date).ToUniversalTime().ToString()
|
||||
382 $certIssuer = $certPrint.Issuer
|
||||
383 $certSubject = $certPrint.Subject
|
||||
384
|
||||
385 $SurfaceRegKey = "HKLM:\SOFTWARE\Microsoft\Surface\SEMM"
|
||||
386 New-RegKey $SurfaceRegKey
|
||||
387 $LSVRegValue = Get-ItemProperty $SurfaceRegKey LSV -ErrorAction SilentlyContinue
|
||||
388 $DateTimeRegValue = Get-ItemProperty $SurfaceRegKey LastConfiguredUTC -ErrorAction SilentlyContinue
|
||||
389 $OwnershipSessionIdRegValue = Get-ItemProperty $SurfaceRegKey OwnershipSessionId -ErrorAction SilentlyContinue
|
||||
390 $PermissionSessionIdRegValue = Get-ItemProperty $SurfaceRegKey PermissionSessionId -ErrorAction SilentlyContinue
|
||||
391 $SettingsSessionIdRegValue = Get-ItemProperty $SurfaceRegKey SettingsSessionId -ErrorAction SilentlyContinue
|
||||
392 $IsResetRegValue = Get-ItemProperty $SurfaceRegKey IsReset -ErrorAction SilentlyContinue
|
||||
393 $certUsedRegValue = Get-ItemProperty $SurfaceRegKey CertName -ErrorAction SilentlyContinue
|
||||
394 $certIssuerRegValue = Get-ItemProperty $SurfaceRegKey CertIssuer -ErrorAction SilentlyContinue
|
||||
395 $certSubjectRegValue = Get-ItemProperty $SurfaceRegKey CertSubject -ErrorAction SilentlyContinue
|
||||
396
|
||||
397
|
||||
398 If ($LSVRegValue -eq $null)
|
||||
399 {
|
||||
400 New-ItemProperty -Path $SurfaceRegKey -Name LSV -PropertyType DWORD -Value $lsv | Out-Null
|
||||
401 }
|
||||
402 Else
|
||||
403 {
|
||||
404 Set-ItemProperty -Path $SurfaceRegKey -Name LSV -Value $lsv
|
||||
405 }
|
||||
406
|
||||
407 If ($DateTimeRegValue -eq $null)
|
||||
408 {
|
||||
409 New-ItemProperty -Path $SurfaceRegKey -Name LastConfiguredUTC -PropertyType String -Value $UTCDate | Out-Null
|
||||
410 }
|
||||
411 Else
|
||||
412 {
|
||||
413 Set-ItemProperty -Path $SurfaceRegKey -Name LastConfiguredUTC -Value $UTCDate
|
||||
414 }
|
||||
415
|
||||
416 If ($OwnershipSessionIdRegValue -eq $null)
|
||||
417 {
|
||||
418 New-ItemProperty -Path $SurfaceRegKey -Name OwnershipSessionId -PropertyType String -Value $ownerSessionIdValue | Out-Null
|
||||
419 }
|
||||
420 Else
|
||||
421 {
|
||||
422 Set-ItemProperty -Path $SurfaceRegKey -Name OwnershipSessionId -Value $ownerSessionIdValue
|
||||
423 }
|
||||
424
|
||||
425 If ($PermissionSessionIdRegValue -eq $null)
|
||||
426 {
|
||||
427 New-ItemProperty -Path $SurfaceRegKey -Name PermissionSessionId -PropertyType String -Value $permissionSessionIdValue | Out-Null
|
||||
428 }
|
||||
429 Else
|
||||
430 {
|
||||
431 Set-ItemProperty -Path $SurfaceRegKey -Name PermissionSessionId -Value $permissionSessionIdValue
|
||||
432 }
|
||||
433
|
||||
434 If ($SettingsSessionIdRegValue -eq $null)
|
||||
435 {
|
||||
436 New-ItemProperty -Path $SurfaceRegKey -Name SettingsSessionId -PropertyType String -Value $settingsSessionIdValue | Out-Null
|
||||
437 }
|
||||
438 Else
|
||||
439 {
|
||||
440 Set-ItemProperty -Path $SurfaceRegKey -Name SettingsSessionId -Value $settingsSessionIdValue
|
||||
441 }
|
||||
442
|
||||
443 If ($IsResetRegValue -eq $null)
|
||||
444 {
|
||||
445 New-ItemProperty -Path $SurfaceRegKey -Name IsReset -PropertyType DWORD -Value 0 | Out-Null
|
||||
446 }
|
||||
447 Else
|
||||
448 {
|
||||
449 Set-ItemProperty -Path $SurfaceRegKey -Name IsReset -Value 0
|
||||
450 }
|
||||
451
|
||||
452 If ($certUsedRegValue -eq $null)
|
||||
453 {
|
||||
454 New-ItemProperty -Path $SurfaceRegKey -Name CertName -PropertyType String -Value $certName | Out-Null
|
||||
455 }
|
||||
456 Else
|
||||
457 {
|
||||
458 Set-ItemProperty -Path $SurfaceRegKey -Name CertName -Value $certName
|
||||
459 }
|
||||
460
|
||||
461 If ($certIssuerRegValue -eq $null)
|
||||
462 {
|
||||
463 New-ItemProperty -Path $SurfaceRegKey -Name CertIssuer -PropertyType String -Value $certIssuer | Out-Null
|
||||
464 }
|
||||
465 Else
|
||||
466 {
|
||||
467 Set-ItemProperty -Path $SurfaceRegKey -Name CertIssuer -Value $certIssuer
|
||||
468 }
|
||||
469
|
||||
470 If ($certSubjectRegValue -eq $null)
|
||||
471 {
|
||||
472 New-ItemProperty -Path $SurfaceRegKey -Name CertSubject -PropertyType String -Value $certSubject | Out-Null
|
||||
473 }
|
||||
474 Else
|
||||
475 {
|
||||
476 Set-ItemProperty -Path $SurfaceRegKey -Name CertSubject -Value $certSubject
|
||||
477 }
|
||||
```
|
||||
|
||||
### Settings names and IDs
|
||||
|
||||
@ -27,6 +27,8 @@
|
||||
"ROBOTS": "INDEX, FOLLOW",
|
||||
"audience": "windows-education",
|
||||
"ms.topic": "article",
|
||||
"ms.technology": "windows",
|
||||
"audience": "ITPro",
|
||||
"breadcrumb_path": "/education/breadcrumb/toc.json",
|
||||
"ms.date": "05/09/2017",
|
||||
"feedback_system": "GitHub",
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft Education, full cloud IT solution, school, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
author: levinec
|
||||
|
||||
@ -5,7 +5,7 @@ keywords: education, Microsoft 365 Education, trial, full cloud IT solution, sch
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.topic: get-started
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: edu
|
||||
ROBOTS: noindex,nofollow
|
||||
|
||||
@ -240,5 +240,6 @@
|
||||
###### [AGPM Server Connection Settings](agpm-server-connection-settings.md)
|
||||
###### [Feature Visibility Settings](feature-visibility-settings.md)
|
||||
##### [Other Enhancements to the GPMC](other-enhancements-to-the-gpmc.md)
|
||||
## [Troubleshooting AGPM Upgrades](troubleshooting-agpm40-upgrades.md)
|
||||
## [Resources for AGPM](resources-for-agpm.md)
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Advanced Group Policy Management
|
||||
description: Advanced Group Policy Management
|
||||
author: jamiejdt
|
||||
author: dansimp
|
||||
ms.assetid: 493ca3c3-c3d6-4bb1-9430-dc1e43c86bb0
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
41
mdop/agpm/troubleshooting-agpm40-upgrades.md
Normal file
41
mdop/agpm/troubleshooting-agpm40-upgrades.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Troubleshooting AGPM Upgrades
|
||||
description: Troubleshooting AGPM Upgrades
|
||||
author: jedodson
|
||||
ms.assetid: 1abbf0c1-fd32-46a8-a3ba-c005f066523d
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: jedodson
|
||||
ms.pagetype: mdop
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
# Troubleshooting AGPM Upgrades
|
||||
|
||||
This section lists common issues that you may encounter when you upgrade your Advanced Group Policy Management (AGPM) server to a newer version (e.g. AGPM 4.0 to AGPM 4.3). To diagnose issues not listed here, it may be helpful to view the [Troubleshooting AGPM](troubleshooting-agpm-agpm40.md) or for an AGPM Administrator (Full Control) to use logging and tracing. For more information, see [Configure Logging and Tracing](configure-logging-and-tracing-agpm40.md).
|
||||
|
||||
## What problems are you having?
|
||||
|
||||
- [Failed to generate a HTML GPO difference report (Error code 80004003)](#bkmk-error-80004003)
|
||||
|
||||
### <a href="" id="bkmk-error-80004003"></a>Failed to generate a HTML GPO difference report (Error code 80004003)
|
||||
|
||||
- **Cause**: You have installed the AGPM upgrade package with an incorrect account.
|
||||
|
||||
- **Solution**: You will need to be an AGPM administrator in order to fix this issue.
|
||||
|
||||
- Ensure you know the username & password of your **AGPM service account**.
|
||||
|
||||
- Log onto your AGPM server interactively as your AGPM service account.
|
||||
|
||||
- This is critically important, as the install will fail if you use a different account.
|
||||
|
||||
- Shutdown the AGPM service.
|
||||
|
||||
- Install the required hotfix.
|
||||
|
||||
- Connect to AGPM using an AGPM client to test that your difference reports are now functioning.
|
||||
@ -9,7 +9,7 @@ ms.author: manikadhiman
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
@ -73,11 +73,11 @@ When this has been completed, install the App-V 4.5 SP2 Clients by using Setup.m
|
||||
|
||||
When installing Microsoft Application Error Reporting, use the following command if you are installing or upgrading to the App-V 4.5 SP2 Desktop Client:
|
||||
|
||||
** msiexec /i dw20shared.msi APPGUID={C6FC75B9-7D86-4C44-8BDB-EAFE1F0E200D} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
**msiexec /i dw20shared.msi APPGUID={C6FC75B9-7D86-4C44-8BDB-EAFE1F0E200D} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
|
||||
Alternatively, if you are installing or upgrading to the App-V 4.5 SP2 Client for Remote Desktop Services (formerly Terminal Services), use the following command:
|
||||
|
||||
** msiexec /i dw20shared.msi APPGUID={ECF80BBA-CA07-4A74-9ED6-E064F38AF1F5} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
**msiexec /i dw20shared.msi APPGUID={ECF80BBA-CA07-4A74-9ED6-E064F38AF1F5} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
|
||||
|
||||
**Note**
|
||||
- The APPGUID parameter references the product code of the App-V Clients that you install or upgrade. The product code is unique for each Setup.msi. You can use the Orca Database Editor or a similar tool to examine Windows Installer files and determine the product code. This step is required for all installations or upgrades to App-V 4.5 SP2.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 08/30/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w8
|
||||
ms.prod: w10
|
||||
ms.date: 06/16/2016
|
||||
---
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user