deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-14 06:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge branch 'master' into v-lamoyn-working

Browse Source
This commit is contained in:
Lauren Moynihan 2019-08-15 11:03:52 -07:00
commit 1a22f62ecf
2 changed files with 71 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
devices/surface-hub/surface-hub-start-menu.md
View File

@ -3,12 +3,12 @@ title: Configure Surface Hub Start menu
description: Use MDM to customize the Start menu on Surface Hub. description: Use MDM to customize the Start menu on Surface Hub.
ms.prod: surface-hub ms.prod: surface-hub
ms.sitesec: library ms.sitesec: library
author: levinec author: robmazz
ms.author: ellevin ms.author: robmazz
ms.topic: article ms.topic: article
ms.date: 01/17/2018 ms.date: 08/15/2018
ms.reviewer: ms.reviewer:
manager: dansimp manager: laurawi
ms.localizationpriority: medium ms.localizationpriority: medium
--- ---
@ -107,7 +107,7 @@ There are a few key differences between Start menu customization for Surface Hub
<span id="edge" /> <span id="edge" />
## Example: Start layout that includes a Microsoft Edge link ## Example: Start layout that includes a Microsoft Edge link
This example shows a link to a website and a link to a .pdf file. This example shows a link to a website and a link to a .pdf file. The secondary tile for Microsoft Edge uses a 150 x 150 pixel icon.
```xml ```xml
<LayoutModificationTemplate Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"> <LayoutModificationTemplate Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
@ -165,10 +165,10 @@ This example shows a link to a website and a link to a .pdf file.
TileID="6153963000" TileID="6153963000"
DisplayName="cstrtqbiology.pdf" DisplayName="cstrtqbiology.pdf"
Arguments="-contentTile -formatVersion 0x00000003 -pinnedTimeLow 0x45b7376e -pinnedTimeHigh 0x01d2356c -securityFlags 0x00000000 -tileType 0x00000000 -url 0x0000003a https://www.ada.gov/regs2010/2010ADAStandards/Guidance_2010ADAStandards.pdf" Arguments="-contentTile -formatVersion 0x00000003 -pinnedTimeLow 0x45b7376e -pinnedTimeHigh 0x01d2356c -securityFlags 0x00000000 -tileType 0x00000000 -url 0x0000003a https://www.ada.gov/regs2010/2010ADAStandards/Guidance_2010ADAStandards.pdf"
Square150x150LogoUri="ms-appx:///" Square150x150LogoUri="ms-appx:///Assets/MicrosoftEdgeSquare150x150.png"
Wide310x150LogoUri="ms-appx:///" Wide310x150LogoUri="ms-appx:///"
ShowNameOnSquare150x150Logo="true" ShowNameOnSquare150x150Logo="true"
ShowNameOnWide310x150Logo="true" ShowNameOnWide310x150Logo="false"
BackgroundColor="#ff4e4248" BackgroundColor="#ff4e4248"
Size="4x2" Size="4x2"
Row="4" Row="4"
@ -181,8 +181,6 @@ This example shows a link to a website and a link to a .pdf file.
``` ```
>[!NOTE] >[!NOTE]
>Microsoft Edge tile logos won't appear on secondary tiles because they aren't stored in Surface Hub.
>
>The default value for `ForegroundText` is light; you don't need to include `ForegroundText` in your XML unless you're changing the value to dark. >The default value for `ForegroundText` is light; you don't need to include `ForegroundText` in your XML unless you're changing the value to dark.
## More information ## More information

14
windows/deployment/upgrade/use-upgrade-readiness-to-manage-windows-upgrades.md
View File

@ -6,8 +6,9 @@ description: Describes how to use Upgrade Readiness to manage Windows upgrades.
keywords: windows analytics, oms, operations management suite, prerequisites, requirements, upgrades, log analytics, keywords: windows analytics, oms, operations management suite, prerequisites, requirements, upgrades, log analytics,
ms.localizationpriority: medium ms.localizationpriority: medium
ms.prod: w10 ms.prod: w10
audience: itpro author: greg-lindsay audience: itpro
ms.author: greglin author: jaimeo
ms.author: jaimeo
ms.topic: article ms.topic: article
--- ---
@ -25,9 +26,8 @@ When you are ready to begin the upgrade process, a workflow is provided to guide
<A HREF="../images/ua-cg-15.png">![Series of blades showing Upgrade Overview, Step 1: Identify Important Apps, Prioritize Applications, Step 2: Resolve issues, and Review applications with known issues](../images/ua-cg-15.png)</A> <A HREF="../images/ua-cg-15.png">![Series of blades showing Upgrade Overview, Step 1: Identify Important Apps, Prioritize Applications, Step 2: Resolve issues, and Review applications with known issues](../images/ua-cg-15.png)</A>
Each step in the workflow is enumerated using blue tiles. Helpful data is provided on white tiles to help you get started, to monitor your progress, and to complete each step. Blue tiles enumerate each step in the workflow. White tiles show data to help you get started, to monitor your progress, and to complete each step.
>**Important**: You can use the [Target version](#target-version) setting to evaluate computers that are running a specified version of Windows before starting the Upgrade Readiness workflow. By default, the Target version is configured to the released version of Windows 10 for the Semi-Annual Channel.
>**Important**: You can use the [Target version](#target-version) setting to evaluate computers that are running a specified version of Windows before starting the Upgrade Readiness workflow. By default, the Target version is configured to the released version of Windows 10 for the Current Branch for Business (CBB).
The following information and workflow is provided: The following information and workflow is provided:
@ -46,11 +46,11 @@ The target version setting is used to evaluate the number of computers that are
![Upgrade overview showing target version](../images/ur-target-version.png) ![Upgrade overview showing target version](../images/ur-target-version.png)
The default target version in Upgrade Readiness is set to the released version of the Current Branch for Business (CBB). CBB can be determined by reviewing [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version. The default target version in Upgrade Readiness is set to the released version of the Semi-Annual Channel. Check [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx) to learn the current version in the Semi-Annual Channel. The target version setting is used to evaluate the number of computers that are already running this version of Windows, or a later version.
The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target version. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Readiness is based on the target operating system version. The number displayed under **Computers upgraded** in the Upgrade Overview blade is the total number of computers that are already running the same or a later version of Windows compared to the target version. It also is used in the evaluation of apps and drivers: Known issues and guidance for the apps and drivers in Upgrade Readiness is based on the target operating system version.
You now have the ability to change the Windows 10 version you wish to target. The available options currently are: Windows 10 version 1507, Windows 10 version 1511, Windows 10 version 1607, Windows 10 version 1703, Windows 10 version 1709 and Windows 10 version 1803. You can change the Windows 10 version you want to target. All currently supported versions of Windows 10 are available options.
To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution: To change the target version setting, click on **Solutions Settings**, which appears at the top when you open you Upgrade Readiness solution: