From df848b4a876125d0b560e676d1739adf749062ac Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 7 May 2021 12:27:19 -0700 Subject: [PATCH 001/104] first draft --- windows/sv/TOC.yml | 2 +- windows/sv/index.md | 1 - windows/sv/index.yml | 66 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 67 insertions(+), 2 deletions(-) delete mode 100644 windows/sv/index.md create mode 100644 windows/sv/index.yml diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index b5ef71ac32..2b84fa1b4a 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,2 +1,2 @@ - name: Index - href: index.md \ No newline at end of file + href: index.yml \ No newline at end of file diff --git a/windows/sv/index.md b/windows/sv/index.md deleted file mode 100644 index 8f7cbe8630..0000000000 --- a/windows/sv/index.md +++ /dev/null @@ -1 +0,0 @@ -# Welcome to SV! \ No newline at end of file diff --git a/windows/sv/index.yml b/windows/sv/index.yml new file mode 100644 index 0000000000..5b07303233 --- /dev/null +++ b/windows/sv/index.yml @@ -0,0 +1,66 @@ +### YamlMime:Landing + +title: Windows NAME # < 60 chars +summary: Find out about Windows NAME. # < 160 chars + +metadata: + title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. + description: Learn about the administrative tools, tasks and best practices for managing Windows SV across your enterprise. # Required; article description that is displayed in search results. < 160 chars. + services: windows-10 + ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. + ms.subservice: subservice + ms.topic: landing-page # Required + ms.collection: windows-10 + author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. + ms.author: greglin #Required; microsoft alias of author; optional team alias. + ms.date: 05/07/2021 #Required; mm/dd/yyyy format. + localization_priority: medium + +# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new + +landingContent: +# Cards and links should be based on top customer tasks or top subjects +# Start card title with a verb + # Card (optional) + - title: Card 1 + linkLists: + - linkListType: overview + links: + - text: Link 1 + url: placeholder.md + - text: Link 2 + url: placeholder.md + - text: Link 3 + url: placeholder.md + - text: Link 4 + url: placeholder.md + + + # Card (optional) + - title: Card 2 + linkLists: + - linkListType: overview + links: + - text: Link 1 + url: placeholder.md + - text: Link 2 + url: placeholder.md + - text: Link 3 + url: placeholder.md + - text: Link 4 + url: placeholder.md + + + # Card (optional) + - title: Card 3 + linkLists: + - linkListType: overview + links: + - text: Link 1 + url: placeholder.md + - text: Link 2 + url: placeholder.md + - text: Link 3 + url: placeholder.md + - text: Link 4 + url: placeholder.md From 81811f42433ef6ed174d79984619bc82955acb6c Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 7 May 2021 12:35:49 -0700 Subject: [PATCH 002/104] 2 --- windows/sv/TOC.yml | 2 +- windows/sv/breadcrumb/toc.yml | 3 --- windows/sv/index.yml | 4 ++-- windows/sv/placeholder.md | 22 ++++++++++++++++++++++ 4 files changed, 25 insertions(+), 6 deletions(-) delete mode 100644 windows/sv/breadcrumb/toc.yml create mode 100644 windows/sv/placeholder.md diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index 2b84fa1b4a..459e198125 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,2 +1,2 @@ -- name: Index +- name: Windows SV href: index.yml \ No newline at end of file diff --git a/windows/sv/breadcrumb/toc.yml b/windows/sv/breadcrumb/toc.yml deleted file mode 100644 index 61d8fca61e..0000000000 --- a/windows/sv/breadcrumb/toc.yml +++ /dev/null @@ -1,3 +0,0 @@ -- name: Docs - tocHref: / - topicHref: / \ No newline at end of file diff --git a/windows/sv/index.yml b/windows/sv/index.yml index 5b07303233..0f8c82e9f2 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -1,7 +1,7 @@ ### YamlMime:Landing -title: Windows NAME # < 60 chars -summary: Find out about Windows NAME. # < 160 chars +title: Windows SV # < 60 chars +summary: Find out about Windows SV. # < 160 chars metadata: title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. diff --git a/windows/sv/placeholder.md b/windows/sv/placeholder.md new file mode 100644 index 0000000000..fecfe94a8e --- /dev/null +++ b/windows/sv/placeholder.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Placeholder + +Placeholder text. + From caabdbb0952f8f0f028549acf0d11d9d85b4a6b0 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 09:34:50 -0700 Subject: [PATCH 003/104] draft --- windows/sv/TOC.yml | 44 +++++++++++++++++++++++++++++++++-- windows/sv/index.yml | 6 ++--- windows/sv/sv-faq.md | 22 ++++++++++++++++++ windows/sv/sv-overview.md | 22 ++++++++++++++++++ windows/sv/sv-requirements.md | 22 ++++++++++++++++++ 5 files changed, 111 insertions(+), 5 deletions(-) create mode 100644 windows/sv/sv-faq.md create mode 100644 windows/sv/sv-overview.md create mode 100644 windows/sv/sv-requirements.md diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index 459e198125..b8531c0f0c 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,2 +1,42 @@ -- name: Windows SV - href: index.yml \ No newline at end of file +- name: Deploy and update Windows 10 + href: index.yml + items: + - name: Get started + items: + - name: Sun Valley overview + href: sv-overview.md + - name: Windows Sun Valley requirements + href: sv-requirements.md + - name: Sun Valley FAQ + href: sv-faq.md + + + - name: Upgrade to Windows Sun Valley + items: + + - name: Plan to deploy Windows Sun Valley + href: update/plan-define-readiness.md + - name: Prepare for Windows Sun Valley + href: update/eval-infra-tools.md + - name: Deploy Windows Sun Valley + href: update/plan-determine-app-readiness.md + - name: Define your servicing strategy + href: update/plan-define-strategy.md + - name: Delivery Optimization for Windows 10 updates + href: update/waas-delivery-optimization.md + + + - name: Support + items: + - name: Windows Sun Valley lifecycle + href: sv-requirements.md + - name: Prepare to deploy Windows Sun Valley + href: update/plan-define-readiness.md + - name: Deploy Windows Sun Valley + href: update/eval-infra-tools.md + - name: Determine application readiness + href: update/plan-determine-app-readiness.md + - name: Define your servicing strategy + href: update/plan-define-strategy.md + - name: Delivery Optimization for Windows 10 updates + href: update/waas-delivery-optimization.md diff --git a/windows/sv/index.yml b/windows/sv/index.yml index 0f8c82e9f2..dd25268757 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -22,7 +22,7 @@ landingContent: # Cards and links should be based on top customer tasks or top subjects # Start card title with a verb # Card (optional) - - title: Card 1 + - title: Get started linkLists: - linkListType: overview links: @@ -37,7 +37,7 @@ landingContent: # Card (optional) - - title: Card 2 + - title: Upgrade to Sun Valley linkLists: - linkListType: overview links: @@ -52,7 +52,7 @@ landingContent: # Card (optional) - - title: Card 3 + - title: Support information linkLists: - linkListType: overview links: diff --git a/windows/sv/sv-faq.md b/windows/sv/sv-faq.md new file mode 100644 index 0000000000..fecfe94a8e --- /dev/null +++ b/windows/sv/sv-faq.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Placeholder + +Placeholder text. + diff --git a/windows/sv/sv-overview.md b/windows/sv/sv-overview.md new file mode 100644 index 0000000000..fecfe94a8e --- /dev/null +++ b/windows/sv/sv-overview.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Placeholder + +Placeholder text. + diff --git a/windows/sv/sv-requirements.md b/windows/sv/sv-requirements.md new file mode 100644 index 0000000000..fecfe94a8e --- /dev/null +++ b/windows/sv/sv-requirements.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Placeholder + +Placeholder text. + From 77497788f16c68eaf6d43a030f10add991c7fc25 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 09:51:34 -0700 Subject: [PATCH 004/104] draft2 --- .../sv-app-readiness.md | 183 ++++++++++ windows/client-management/sv-manage.md | 67 ++++ windows/configuration/sv-configure.md | 329 ++++++++++++++++++ windows/deployment/TOC.yml | 4 +- windows/deployment/sv-planning.md | 275 +++++++++++++++ windows/sv/TOC.yml | 41 +-- 6 files changed, 873 insertions(+), 26 deletions(-) create mode 100644 windows/application-management/sv-app-readiness.md create mode 100644 windows/client-management/sv-manage.md create mode 100644 windows/configuration/sv-configure.md create mode 100644 windows/deployment/sv-planning.md diff --git a/windows/application-management/sv-app-readiness.md b/windows/application-management/sv-app-readiness.md new file mode 100644 index 0000000000..d8cddab78d --- /dev/null +++ b/windows/application-management/sv-app-readiness.md @@ -0,0 +1,183 @@ +--- +title: Windows 10 - Apps +ms.reviewer: +manager: dansimp +description: Use this article to understand the different types of apps that run on Windows 10, such as UWP and Win32 apps. +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: mobile +ms.author: greglin +author: greg-lindsay +ms.localizationpriority: medium +ms.topic: article +--- +# Understand the different apps included in Windows 10 + +>Applies to: Windows 10 + +The following types of apps run on Windows 10: +- Windows apps - introduced in Windows 8, primarily installed from the Store app. +- Universal Windows Platform (UWP) apps - designed to work across platforms, can be installed on multiple platforms including Windows client, Windows Phone, and Xbox. All UWP apps are also Windows apps, but not all Windows apps are UWP apps. +- "Win32" apps - traditional Windows applications. + +Digging into the Windows apps, there are two categories: +- Apps - All other apps, installed in C:\Program Files\WindowsApps. There are two classes of apps: + - Provisioned: Installed in user account the first time you sign in with a new user account. + - Installed: Installed as part of the OS. +- System apps - Apps that are installed in the C:\Windows\* directory. These apps are integral to the OS. + +The following tables list the system apps, installed Windows apps, and provisioned Windows apps in a standard Windows 10 Enterprise installation. (If you have a custom image, your specific apps might differ.) The tables list the app, the full name, show the app's status in Windows 10 version 1709, 1803, and 1809 and indicate whether an app can be uninstalled through the UI. + +Some of the apps show up in multiple tables - that's because their status changed between versions. Make sure to check the version column for the version you are currently running. + +## Provisioned Windows apps + +You can list all provisioned Windows apps with this PowerShell command: + +```Powershell +Get-AppxProvisionedPackage -Online | Format-Table DisplayName, PackageName +``` + +Here are the provisioned Windows apps in Windows 10 versions 1803, 1809, 1903, 1909, and 2004. + +| Package name | App name | 1803 | 1809 | 1903 | 1909 | 2004 | Uninstall through UI? | +|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------|:----:|:----:|:----:|:----:|:----:|:---------------------:| +| Microsoft.3DBuilder | [3D Builder](ms-windows-store://pdp/?PFN=Microsoft.3DBuilder_8wekyb3d8bbwe) | | | | | | Yes | +| Microsoft.BingWeather | [MSN Weather](ms-windows-store://pdp/?PFN=Microsoft.BingWeather_8wekyb3d8bbwe) | x | x | x | x | x | Yes | +| Microsoft.DesktopAppInstaller | [App Installer](ms-windows-store://pdp/?PFN=Microsoft.DesktopAppInstaller_8wekyb3d8bbwe) | x | x | x | x | x | Via Settings App | +| Microsoft.GetHelp | [Get Help](ms-windows-store://pdp/?PFN=Microsoft.Gethelp_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.Getstarted | [Microsoft Tips](ms-windows-store://pdp/?PFN=Microsoft.Getstarted_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.HEIFImageExtension | [HEIF Image Extensions](ms-windows-store://pdp/?PFN=Microsoft.HEIFImageExtension_8wekyb3d8bbwe) | | x | x | x | x | No | +| Microsoft.Messaging | [Microsoft Messaging](ms-windows-store://pdp/?PFN=Microsoft.Messaging_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.Microsoft3DViewer | [Mixed Reality Viewer](ms-windows-store://pdp/?PFN=Microsoft.Microsoft3DViewer_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.MicrosoftOfficeHub | [Office](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe) | x | x | x | x | x | Yes | +| Microsoft.MicrosoftSolitaireCollection | [Microsoft Solitaire Collection](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe) | x | x | x | x | x | Yes | +| Microsoft.MicrosoftStickyNotes | [Microsoft Sticky Notes](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.MixedReality.Portal | [Mixed Reality Portal](ms-windows-store://pdp/?PFN=Microsoft.MixedReality.Portal_8wekyb3d8bbwe) | | x | x | x | x | No | +| Microsoft.MSPaint | [Paint 3D](ms-windows-store://pdp/?PFN=Microsoft.MSPaint_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.Office.OneNote | [OneNote for Windows 10](ms-windows-store://pdp/?PFN=Microsoft.Office.OneNote_8wekyb3d8bbwe) | x | x | x | x | x | Yes | +| Microsoft.OneConnect | [Mobile Plans](ms-windows-store://pdp/?PFN=Microsoft.OneConnect_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.Outlook.DesktopIntegrationServices | | | | | x | x | | +| Microsoft.People | [Microsoft People](ms-windows-store://pdp/?PFN=Microsoft.People_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.Print3D | [Print 3D](ms-windows-store://pdp/?PFN=Microsoft.Print3D_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.ScreenSketch | [Snip & Sketch](ms-windows-store://pdp/?PFN=Microsoft.ScreenSketch_8wekyb3d8bbwe) | | x | x | x | x | No | +| Microsoft.SkypeApp | [Skype](ms-windows-store://pdp/?PFN=Microsoft.SkypeApp_kzf8qxf38zg5c) | x | x | x | x | x | No | +| Microsoft.StorePurchaseApp | [Store Purchase App](ms-windows-store://pdp/?PFN=Microsoft.StorePurchaseApp_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.VP9VideoExtensions | | | x | x | x | x | No | +| Microsoft.Wallet | [Microsoft Pay](ms-windows-store://pdp/?PFN=Microsoft.Wallet_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WebMediaExtensions | [Web Media Extensions](ms-windows-store://pdp/?PFN=Microsoft.WebMediaExtensions_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WebpImageExtension | [Webp Image Extension](ms-windows-store://pdp/?PFN=Microsoft.WebpImageExtension_8wekyb3d8bbwe) | | x | x | x | x | No | +| Microsoft.Windows.Photos | [Microsoft Photos](ms-windows-store://pdp/?PFN=Microsoft.Windows.Photos_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsAlarms | [Windows Alarms & Clock](ms-windows-store://pdp/?PFN=Microsoft.WindowsAlarms_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsCalculator | [Windows Calculator](ms-windows-store://pdp/?PFN=Microsoft.WindowsCalculator_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsCamera | [Windows Camera](ms-windows-store://pdp/?PFN=Microsoft.WindowsCamera_8wekyb3d8bbwe) | x | x | x | x | x | No | +| microsoft.windowscommunicationsapps | [Mail and Calendar](ms-windows-store://pdp/?PFN=microsoft.windowscommunicationsapps_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsFeedbackHub | [Feedback Hub](ms-windows-store://pdp/?PFN=Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsMaps | [Windows Maps](ms-windows-store://pdp/?PFN=Microsoft.WindowsMaps_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsSoundRecorder | [Windows Voice Recorder](ms-windows-store://pdp/?PFN=Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.WindowsStore | [Microsoft Store](ms-windows-store://pdp/?PFN=Microsoft.WindowsStore_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.Xbox.TCUI | [Xbox Live in-game experience](ms-windows-store://pdp/?PFN=Microsoft.Xbox.TCUI_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.XboxApp | [Xbox Console Companion](ms-windows-store://pdp/?PFN=Microsoft.XboxApp_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.XboxGameOverlay | [Xbox Game Bar Plugin](ms-windows-store://pdp/?PFN=Microsoft.XboxGameOverlay_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.XboxGamingOverlay | [Xbox Game Bar](ms-windows-store://pdp/?PFN=Microsoft.XboxGamingOverlay_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.XboxIdentityProvider | [Xbox Identity Provider](ms-windows-store://pdp/?PFN=Microsoft.XboxIdentityProvider_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.XboxSpeechToTextOverlay | | x | x | x | x | x | No | +| Microsoft.YourPhone | [Your Phone](ms-windows-store://pdp/?PFN=Microsoft.YourPhone_8wekyb3d8bbwe) | | x | x | x | x | No | +| Microsoft.ZuneMusic | [Groove Music](ms-windows-store://pdp/?PFN=Microsoft.ZuneMusic_8wekyb3d8bbwe) | x | x | x | x | x | No | +| Microsoft.ZuneVideo | [Movies & TV](ms-windows-store://pdp/?PFN=Microsoft.ZuneVideo_8wekyb3d8bbwe) | x | x | x | x | x | No | + +>[!NOTE] +>The Store app can't be removed. If you want to remove and reinstall the Store app, you can only bring Store back by either restoring your system from a backup or resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it. + +## System apps + +System apps are integral to the operating system. Here are the typical system apps in Windows 10 versions 1709, 1803, and 1809. + +You can list all system apps with this PowerShell command: + +```Powershell +Get-AppxPackage -PackageTypeFilter Main | ? { $_.SignatureKind -eq "System" } | Sort Name | Format-Table Name, InstallLocation +``` + +| Name | Package Name | 1709 | 1803 | 1809 |Uninstall through UI? | +|----------------------------------|---------------------------------------------|:-----:|:----:|:----:|-----------------------| +| File Picker | 1527c705-839a-4832-9118-54d4Bd6a0c89 | | x | x | No | +| File Explorer | c5e2524a-ea46-4f67-841f-6a9465d9d515 | | x | x | No | +| App Resolver UX | E2A4F912-2574-4A75-9BB0-0D023378592B | | x | x | No | +| Add Suggested Folders To Library | F46D4000-FD22-4DB4-AC8E-4E1DDDE828FE | | x | x | No | +| | InputApp | x | x | x | No | +| Microsoft.AAD.Broker.Plugin | Microsoft.AAD.Broker.Plugin | x | x | x | No | +| Microsoft.AccountsControl | Microsoft.AccountsControl | x | x | x | No | +| Microsoft.AsyncTextService | Microsoft.AsyncTextService | | x | x | No | +| Hello setup UI | Microsoft.BioEnrollment | x | x | x | No | +| | Microsoft.CredDialogHost | x | x | x | No | +| | Microsoft.ECApp | x | x | x | No | +| | Microsoft.LockApp | x | x | x | No | +| Microsoft Edge | Microsoft.MicrosoftEdge | x | x | x | No | +| | Microsoft.MicrosoftEdgeDevToolsClient | | x | x | No | +| | Microsoft.PPIProjection | x | x | x | No | +| | Microsoft.Win32WebViewHost | | x | x | No | +| | Microsoft.Windows.Apprep.ChxApp | x | x | x | No | +| | Microsoft.Windows.AssignedAccessLockApp | x | x | x | No | +| | Microsoft.Windows.CapturePicker | | x | x | No | +| | Microsoft.Windows.CloudExperienceHost | x | x | x | No | +| | Microsoft.Windows.ContentDeliveryManager | x | x | x | No | +| Cortana | Microsoft.Windows.Cortana | x | x | x | No | +| | Microsoft.Windows.Holographic.FirstRun | x | x | | No | +| | Microsoft.Windows.OOBENetworkCaptivePort | x | x | x | No | +| | Microsoft.Windows.OOBENetworkConnectionFlow | x | x | x | No | +| | Microsoft.Windows.ParentalControls | x | x | x | No | +| People Hub | Microsoft.Windows.PeopleExperienceHost | x | x | x | No | +| | Microsoft.Windows.PinningConfirmationDialog | x | x | x | No | +| | Microsoft.Windows.SecHealthUI | x | x | x | No | +| | Microsoft.Windows.SecondaryTileExperience | x | | | No | +| | Microsoft.Windows.SecureAssessmentBrowser | x | x | x | No | +| Start | Microsoft.Windows.ShellExperienceHost | x | x | x | No | +| Windows Feedback | Microsoft.WindowsFeedback | * | | | No | +| | Microsoft.XboxGameCallableUI | x | x | x | No | +| | Windows.CBSPreview | | x | x | No | +| Contact Support* | Windows.ContactSupport | * | | | Via Settings App | +| Settings | Windows.immersivecontrolpanel | x | x | x | No | +| Print 3D | Windows.Print3D | | x | x | Yes | +| Print UI | Windows.PrintDialog | x | x | x | No | + + +> [!NOTE] +> The Contact Support app changed to Get Help in version 1709. Get Help is a provisioned app (instead of system app like Contact Support). + +## Installed Windows apps + +Here are the typical installed Windows apps in Windows 10 versions 1709, 1803, and 1809. + + +| Name | Full name | 1709 | 1803 | 1809 | Uninstall through UI? | +|-----------------------|------------------------------------------|:----:|:----:|:----:|:---------------------:| +| Remote Desktop | Microsoft.RemoteDesktop | x | | x | Yes | +| Code Writer | ActiproSoftwareLLC.562882FEEB491 | x | x | | Yes | +| Eclipse Manager | 46928bounde.EclipseManager | x | x | | Yes | +| Pandora | PandoraMediaInc.29680B314EFC2 | x | x | | Yes | +| Photoshop Express | AdobeSystemIncorporated. AdobePhotoshop | x | x | | Yes | +| Duolingo | D5EA27B7.Duolingo- LearnLanguagesforFree | x | x | | Yes | +| Network Speed Test | Microsoft.NetworkSpeedTest | x | x | x | Yes | +| News | Microsoft.BingNews | x | x | x | Yes | +| Sway | Microsoft.Office.Sway | x | x | x | Yes | +| Microsoft.Advertising | Microsoft.Advertising.Xaml | x | x | x | Yes | +| | Microsoft.NET.Native.Framework.1.2 | x | x | | Yes | +| | Microsoft.NET.Native.Framework.1.3 | x | x | | Yes | +| | Microsoft.NET.Native.Framework.1.6 | x | x | x | Yes | +| | Microsoft.NET.Native.Framework.1.7 | | x | x | Yes | +| | Microsoft.NET.Native.Framework.2.0 | x | x | | Yes | +| | Microsoft.NET.Native.Runtime.1.1 | x | x | | Yes | +| | Microsoft.NET.Native.Runtime.1.3 | x | | | Yes | +| | Microsoft.NET.Native.Runtime.1.4 | x | x | | Yes | +| | Microsoft.NET.Native.Runtime.1.6 | x | x | x | Yes | +| | Microsoft.NET.Native.Runtime.1.7 | x | x | x | Yes | +| | Microsoft.NET.Native.Runtime.2.0 | x | x | | Yes | +| | Microsoft.Services.Store.Engagement | x | x | | Yes | +| | Microsoft.VCLibs.120.00 | x | x | | Yes | +| | Microsoft.VCLibs.140.00 | x | x | x | Yes | +| | Microsoft.VCLibs.120.00.Universal | x | | | Yes | +| | Microsoft.VCLibs.140.00.UWPDesktop | | x | | Yes | + +--- diff --git a/windows/client-management/sv-manage.md b/windows/client-management/sv-manage.md new file mode 100644 index 0000000000..4fc41d68c1 --- /dev/null +++ b/windows/client-management/sv-manage.md @@ -0,0 +1,67 @@ +--- +title: Manage corporate devices (Windows 10) +description: You can use the same management tools to manage all device types running Windows 10 desktops, laptops, tablets, and phones. +ms.assetid: 62D6710C-E59C-4077-9C7E-CE0A92DFC05D +ms.reviewer: +manager: dansimp +ms.author: dansimp +keywords: ["MDM", "device management"] +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: devices +author: dansimp +ms.localizationpriority: medium +ms.date: 09/21/2017 +ms.topic: article +--- + +# Manage corporate devices + + +**Applies to** + +- Windows 10 +- Windows 10 Mobile + +You can use the same management tools to manage all device types running Windows 10 : desktops, laptops, tablets, and phones. And your current management tools, such as Group Policy, Windows Management Instrumentation (WMI), PowerShell scripts, System Center tools, and so on, will continue to work for Windows 10. + +## In this section + +| Topic | Description | +| --- | --- | +| [Manage Windows 10 in your organization - transitioning to modern management](manage-windows-10-in-your-organization-modern-management.md) | Strategies for deploying and managing Windows 10, including deploying Windows 10 in a mixed environment | +| [Connect to remote Azure Active Directory-joined PC](connect-to-remote-aadj-pc.md) | How to use Remote Desktop Connection to connect to an Azure AD-joined PC | +| [Manage Windows 10 and Microsoft Store tips, tricks, and suggestions](/windows/configuration/manage-tips-and-suggestions) | Options to manage user experiences to provide a consistent and predictable experience for employees | +| [New policies for Windows 10](new-policies-for-windows-10.md) | New Group Policy settings added in Windows 10 | +| [Group Policies that apply only to Windows 10 Enterprise and Windows 10 Education](group-policies-for-enterprise-and-education-editions.md) | Group Policy settings that apply only to Windows 10 Enterprise and Windows 10 Education | +| [Changes to Group Policy settings for Start in Windows 10](/windows/configuration/changes-to-start-policies-in-windows-10) | Changes to the Group Policy settings that you use to manage Start | +| [Introduction to configuration service providers (CSPs) for IT pros](/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers) | How IT pros and system administrators can take advantage of many settings available through CSPs to configure devices running Windows 10 and Windows 10 Mobile in their organizations | + + +## Learn more + +[How to bulk-enroll devices with On-premises Mobile Device Management in Microsoft Endpoint Configuration Manager](/mem/configmgr/mdm/deploy-use/bulk-enroll-devices-on-premises-mdm) + +[Azure AD, Microsoft Intune and Windows 10 - Using the cloud to modernize enterprise mobility](https://blogs.technet.microsoft.com/enterprisemobility/2015/06/12/azure-ad-microsoft-intune-and-windows-10-using-the-cloud-to-modernize-enterprise-mobility/) + +[Microsoft Intune End User Enrollment Guide](/samples/browse/?redirectedfrom=TechNet-Gallery) + +[Azure AD Join on Windows 10 devices](https://go.microsoft.com/fwlink/p/?LinkId=616791) + +[Azure AD support for Windows 10](https://go.microsoft.com/fwlink/p/?LinkID=615765) + +[Windows 10 and Azure Active Directory: Embracing the Cloud](https://go.microsoft.com/fwlink/p/?LinkId=615768) + +[How to manage Windows 10 devices using Intune](https://go.microsoft.com/fwlink/p/?LinkId=613620) + +[Using Intune alone and with Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=613207) + +Microsoft Virtual Academy course: [System Center 2012 R2 Configuration Manager & Windows Intune](/learn/) + + + + + + +  \ No newline at end of file diff --git a/windows/configuration/sv-configure.md b/windows/configuration/sv-configure.md new file mode 100644 index 0000000000..15407ebc50 --- /dev/null +++ b/windows/configuration/sv-configure.md @@ -0,0 +1,329 @@ +--- +title: Configure Windows 10 taskbar (Windows 10) +description: Administrators can pin additional apps to the taskbar and remove default pinned apps from the taskbar by adding a section to a layout modification XML file. +keywords: ["taskbar layout","pin apps"] +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +author: greg-lindsay +ms.author: greglin +ms.topic: article +ms.localizationpriority: medium +ms.date: 01/18/2018 +ms.reviewer: +manager: dansimp +--- +# Configure Windows 10 taskbar + +Starting in Windows 10, version 1607, administrators can pin additional apps to the taskbar and remove default pinned apps from the taskbar by adding a `` section to a layout modification XML file. This method never removes user-pinned apps from the taskbar. + +> [!NOTE] +> The only aspect of the taskbar that can currently be configured by the layout modification XML file is the layout. + +You can specify different taskbar configurations based on device locale and region. There is no limit on the number of apps that you can pin. You specify apps using the [Application User Model ID (AUMID)](./find-the-application-user-model-id-of-an-installed-app.md) or Desktop Application Link Path (the local path to the application). + +If you specify an app to be pinned that is not provisioned for the user on the computer, the pinned icon won't appear on the taskbar. + +The order of apps in the XML file dictates the order of pinned apps on the taskbar from left to right, to the right of any existing apps pinned by the user. + +> [!NOTE] +> In operating systems configured to use a right-to-left language, the taskbar order will be reversed. + +The following example shows how apps will be pinned: Windows default apps to the left (blue circle), apps pinned by the user in the center (orange triangle), and apps that you pin using the XML file to the right (green square). + +![Windows left, user center, enterprise to the right](images/taskbar-generic.png) + + +## Configure taskbar (general) + +**To configure the taskbar:** + +1. Create the XML file. + * If you are also [customizing the Start layout](customize-and-export-start-layout.md), use `Export-StartLayout` to create the XML, and then add the `` section from [the following sample](#sample-taskbar-configuration-added-to-start-layout-xml-file) to the file. + * If you are only configuring the taskbar, use [the following sample](#sample-taskbar-configuration-xml-file) to create a layout modification XML file. +2. Edit and save the XML file. You can use [AUMID](./find-the-application-user-model-id-of-an-installed-app.md) or Desktop Application Link Path to identify the apps to pin to the taskbar. + * Add `xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"` to the first line of the file, before the closing \>. + * Use `` and [AUMID](./find-the-application-user-model-id-of-an-installed-app.md) to pin Universal Windows Platform apps. + * Use `` and Desktop Application Link Path to pin desktop applications. +3. Apply the layout modification XML file to devices using [Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) or a [provisioning package created in Windows Imaging and Configuration Designer (Windows ICD)](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md). + +>[!IMPORTANT] +>If you use a provisioning package or import-startlayout to configure the taskbar, your configuration will be reapplied each time the explorer.exe process restarts. If your configuration pins an app and the user then unpins that app, the user's change will be overwritten the next time the configuration is applied. To apply a taskbar configuration that allows users to make changes that will persist, apply your configuration by using Group Policy. +> +>If you use Group Policy and your configuration only contains a taskbar layout, the default Windows tile layout will be applied and cannot be changed by users. If you use Group Policy and your configuration includes taskbar and a full Start layout, users can only make changes to the taskbar. If you use Group Policy and your configuration includes taskbar and a [partial Start layout](.//customize-and-export-start-layout.md#configure-a-partial-start-layout), users can make changes to the taskbar and to tile groups not defined in the partial Start layout. + +### Tips for finding AUMID and Desktop Application Link Path + +In the layout modification XML file, you will need to add entries for applications in the XML markup. In order to pin an application, you need either its AUMID or Desktop Application Link Path. + +The easiest way to find this data for an application is to: +1. Pin the application to the Start menu on a reference or testing PC. +2. Open Windows PowerShell and run the `Export-StartLayout` cmdlet. +3. Open the generated XML file. +4. Look for an entry corresponding to the app you pinned. +5. Look for a property labeled `AppUserModelID` or `DesktopApplicationLinkPath`. + + +### Sample taskbar configuration XML file + +```xml + + + + + + + + + + + +``` +### Sample taskbar configuration added to Start layout XML file + +```xml + + + + + + + + + + + + + + + + + + + + + + + +``` + +## Keep default apps and add your own + +The `` section will append listed apps to the taskbar by default. The following sample keeps the default apps pinned and adds pins for Paint, Microsoft Reader, and a command prompt. + +```xml + + + + + + + + + + + + +``` +**Before:** + +![default apps pinned to taskbar](images/taskbar-default.png) + +**After:** + + ![additional apps pinned to taskbar](images/taskbar-default-plus.png) + +## Remove default apps and add your own + +By adding `PinListPlacement="Replace"` to ``, you remove all default pinned apps; only the apps that you specify will be pinned to the taskbar. + +If you only want to remove some of the default pinned apps, you would use this method to remove all default pinned apps and then include the default app that you want to keep in your list of pinned apps. + +```xml + + + + + + + + + + + + +``` +**Before:** + +![Taskbar with default apps](images/taskbar-default.png) + +**After:** + +![Taskbar with default apps removed](images/taskbar-default-removed.png) + +## Remove default apps + +By adding `PinListPlacement="Replace"` to ``, you remove all default pinned apps. + + +```xml + + + + + + + + + + +``` + +## Configure taskbar by country or region + +The following example shows you how to configure taskbars by country or region. When the layout is applied to a computer, if there is no `` node with a region tag for the current region, the first `` node that has no specified region will be applied. When you specify one or more countries or regions in a `` node, the specified apps are pinned on computers configured for any of the specified countries or regions. + +```xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +When the preceding example XML file is applied, the resulting taskbar for computers in the US or UK: + +![taskbar for US and UK locale](images/taskbar-region-usuk.png) + +The resulting taskbar for computers in Germany or France: + +![taskbar for DE and FR locale](images/taskbar-region-defr.png) + +The resulting taskbar for computers in any other country region: + +![taskbar for all other regions](images/taskbar-region-other.png) + + +> [!NOTE] +> [Look up country and region codes (use the ISO Short column)](/previous-versions/commerce-server/ee799297(v=cs.20)) + + + + +## Layout Modification Template schema definition + +```xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## Related topics + +- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md) +- [Customize and export Start layout](customize-and-export-start-layout.md) +- [Add image for secondary tiles](start-secondary-tiles.md) +- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md) +- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) +- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md) +- [Customize Windows 10 Start and tasbkar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) +- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md) \ No newline at end of file diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index c8a3334ac2..fb5306a3e3 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -1,4 +1,4 @@ -- name: Deploy and update Windows 10 +- name: Deploy and update Windows client href: index.yml items: - name: Get started @@ -33,6 +33,8 @@ - name: Plan items: + - name: Windows Sun Valley deployment planning + href: sv-planning.md - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria diff --git a/windows/deployment/sv-planning.md b/windows/deployment/sv-planning.md new file mode 100644 index 0000000000..e28a0eb0e8 --- /dev/null +++ b/windows/deployment/sv-planning.md @@ -0,0 +1,275 @@ +--- +title: Windows Sun Valley deployment planning +description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. +ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 +ms.reviewer: +manager: laurawi +ms.audience: itpro +ms.author: greglin +author: greg-lindsay +keywords: upgrade, in-place, configuration, deploy +ms.prod: w10 +ms.mktglfcycl: deploy +ms.localizationpriority: medium +ms.sitesec: library +audience: itpro +ms.topic: article +--- + +# Windows Sun Valley deployment planning + +**Applies to** +- Windows 10 + +To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. + +The following table summarizes various Windows 10 deployment scenarios. The scenarios are each assigned to one of three categories. +- Modern deployment methods are recommended unless you have a specific need to use a different procedure. These methods are supported with existing tools such as Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. These methods are discussed in detail on the [Modern Desktop Deployment Center](/microsoft-365/enterprise/desktop-deployment-center-home). + - Note: Once you have deployed Windows 10 in your organization, it is important to stay up to date by [creating a deployment plan](update/create-deployment-plan.md) for Windows 10 feature updates. +- Dynamic deployment methods enable you to configure applications and settings for specific use cases. +- Traditional deployment methods use existing tools to deploy operating system images.
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CategoryScenarioDescriptionMore information
Modern + +[Windows Autopilot](#windows-autopilot) + Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. + +Overview of Windows Autopilot +
+ +[In-place upgrade](#in-place-upgrade) + + + Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. + +Perform an in-place upgrade to Windows 10 with MDT
Perform an in-place upgrade to Windows 10 using Configuration Manager +
+ Dynamic + + +[Subscription Activation](#windows-10-subscription-activation) + + Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. + +Windows 10 Subscription Activation +
+ + [AAD / MDM](#dynamic-provisioning) + + The device is automatically joined to AAD and configured by MDM. + +Azure Active Directory integration with MDM +
+ + [Provisioning packages](#dynamic-provisioning) + + Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. + +Configure devices without MDM +
+ Traditional + + + [Bare metal](#new-computer) + + Deploy a new device, or wipe an existing device and deploy with a fresh image. + + Deploy a Windows 10 image using MDT
Deploy Windows 10 using PXE and Configuration Manager +
+ + [Refresh](#computer-refresh) + + Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. + + Refresh a Windows 7 computer with Windows 10
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager +
+ + [Replace](#computer-replace) + + Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. + + Replace a Windows 7 computer with a Windows 10 computer
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager +
+ +
  + + +>[!IMPORTANT] +>The Windows Autopilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later.
+>Except for clean install scenarios such as traditional bare metal and Windows Autopilot, all the methods described can optionally migrate apps and settings to the new OS. + +## Modern deployment methods + +Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. + +### Windows Autopilot + +Windows Autopilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows Autopilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. + +For more information about Windows Autopilot, see [Overview of Windows Autopilot](/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows Autopilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). + +### In-place upgrade + +For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. + +Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like Microsoft Endpoint Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences. + +The in-place upgrade process is designed to be extremely reliable, with the ability to automatically roll back to the previous operating system if any issues are encountered during the deployment process, without any IT staff involvement. Rolling back manually can also be done by leveraging the automatically-created recovery information (stored in the Windows.old folder), in case any issues are encountered after the upgrade is finished. The upgrade process is also typically faster than traditional deployments, because applications do not need to be reinstalled as part of the process. + +Because existing applications are preserved through the process, the upgrade process uses the standard Windows installation media image (Install.wim); custom images are not needed and cannot be used because the upgrade process is unable to deal with conflicts between apps in the old and new operating system. (For example, Contoso Timecard 1.0 in Windows 7 and Contoso Timecard 3.0 in the Windows 10 image.) + +Scenarios that support in-place upgrade with some additional procedures include changing from BIOS to UEFI boot mode and upgrade of devices that use non-Microsoft disk encryption software. + +- **Legacy BIOS to UEFI booting**: To perform an in-place upgrade on a UEFI-capable system that currently boots using legacy BIOS, first perform the in-place upgrade to Windows 10, maintaining the legacy BIOS boot mode. Windows 10 does not require UEFI, so it will work fine to upgrade a system using legacy BIOS emulation. After the upgrade, if you wish to enable Windows 10 features that require UEFI (such as Secure Boot), you can convert the system disk to a format that supports UEFI boot using the [MBR2GPT](./mbr-to-gpt.md) tool. Note: [UEFI specification](http://www.uefi.org/specifications) requires GPT disk layout. After the disk has been converted, you must also configure the firmware to boot in UEFI mode. + +- **Non-Microsoft disk encryption software**: While devices encrypted with BitLocker can easily be upgraded, more work is necessary for non-Microsoft disk encryption tools. Some ISVs will provide instructions on how to integrate their software into the in-place upgrade process. Check with your ISV to see if they have instructions. The following articles provide details on how to provision encryption drivers for use during Windows Setup via the ReflectDrivers setting: + - [Windows Setup Automation Overview](/windows-hardware/manufacture/desktop/windows-setup-automation-overview) + - [Windows Setup Command-Line Options](/windows-hardware/manufacture/desktop/windows-setup-command-line-options) + +There are some situations where you cannot use in-place upgrade; in these situations, you can use traditional deployment (wipe-and-load) instead. Examples of these situations include: + +- Changing from Windows 7, Windows 8, or Windows 8.1 x86 to Windows 10 x64. The upgrade process cannot change from a 32-bit operating system to a 64-bit operating system, because of possible complications with installed applications and drivers. +- Windows To Go and Boot from VHD installations. The upgrade process is unable to upgrade these installations. Instead, new installations would need to be performed. +- Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. +- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. + + +## Dynamic provisioning + +For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. + +The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: + +### Windows 10 Subscription Activation + +Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-enterprise-subscription-activation). + + +### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment + +In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](/windows/client-management/mdm/azure-active-directory-integration-with-mdm). + +### Provisioning package configuration + +Using the [Windows Imaging and Configuration Designer (ICD)](/windows/configuration/provisioning-packages/provisioning-install-icd), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). + +These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). + +While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. + +## Traditional deployment: + +New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md), and [Microsoft Endpoint Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). + +With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them. + +The traditional deployment scenario can be divided into different sub-scenarios. These are explained in detail in the following sections, but the following provides a brief summary: + +- **New computer.** A bare-metal deployment of a new machine. +- **Computer refresh.** A reinstall of the same machine (with user-state migration and an optional full Windows Imaging (WIM) image backup). +- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). + +### New computer + +Also called a "bare metal" deployment. This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). + +The deployment process for the new machine scenario is as follows: + +1. Start the setup from boot media (CD, USB, ISO, or PXE). + +2. Wipe the hard disk clean and create new volume(s). + +3. Install the operating system image. + +4. Install other applications (as part of the task sequence). + +After taking these steps, the computer is ready for use. + +### Computer refresh + +A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. + +The deployment process for the wipe-and-load scenario is as follows: + +1. Start the setup on a running operating system. + +2. Save the user state locally. + +3. Wipe the hard disk clean (except for the folder containing the backup). + +4. Install the operating system image. + +5. Install other applications. + +6. Restore the user state. + +After taking these steps, the machine is ready for use. + +### Computer replace + +A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. + +The deployment process for the replace scenario is as follows: + +1. Save the user state (data and settings) on the server through a backup job on the running operating system. + +2. Deploy the new computer as a bare-metal deployment. + + **Note**
In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. + +## Related topics + +- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) +- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) +- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) +- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md) +- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference) +- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) +- [UEFI firmware](/windows-hardware/design/device-experiences/oem-uefi) \ No newline at end of file diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index b8531c0f0c..f9d971cc94 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,42 +1,33 @@ - name: Deploy and update Windows 10 href: index.yml items: - - name: Get started + - name: Get started with Windows Sun Valley items: - name: Sun Valley overview href: sv-overview.md - name: Windows Sun Valley requirements href: sv-requirements.md - - name: Sun Valley FAQ - href: sv-faq.md - + - name: Upgrade to Windows Sun Valley items: - - name: Plan to deploy Windows Sun Valley - href: update/plan-define-readiness.md + href: ../deployment/sv-planning.md - name: Prepare for Windows Sun Valley - href: update/eval-infra-tools.md + href: ../deployment/sv-prepare.md - name: Deploy Windows Sun Valley - href: update/plan-determine-app-readiness.md - - name: Define your servicing strategy - href: update/plan-define-strategy.md - - name: Delivery Optimization for Windows 10 updates - href: update/waas-delivery-optimization.md - + href: ../deployment/sv-deploy.md + - name: Configure Windows Sun Valley + href: ../configuration/sv-configure.md + - name: Manage Windows Sun Valley + href: ../client-management/sv-manage.md - - name: Support + - name: Windows Sun Valley Support items: - name: Windows Sun Valley lifecycle - href: sv-requirements.md - - name: Prepare to deploy Windows Sun Valley - href: update/plan-define-readiness.md - - name: Deploy Windows Sun Valley - href: update/eval-infra-tools.md - - name: Determine application readiness - href: update/plan-determine-app-readiness.md - - name: Define your servicing strategy - href: update/plan-define-strategy.md - - name: Delivery Optimization for Windows 10 updates - href: update/waas-delivery-optimization.md + href: sv-lifecycle.md + - name: Windows Sun Valley application readiness + href: application-management/sv-app-readiness.md + - name: Sun Valley FAQ + href: sv-faq.md + From f3d8408cfc8dea7b52bda1a4f98bec3cb2cbde22 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:05:29 -0700 Subject: [PATCH 005/104] draft3 --- windows/sv/TOC.yml | 21 +++++++++++---------- windows/sv/index.yml | 41 ++++++++++++++++++----------------------- 2 files changed, 29 insertions(+), 33 deletions(-) diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index f9d971cc94..76ac398036 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,15 +1,16 @@ -- name: Deploy and update Windows 10 +- name: Windows Sun Valley href: index.yml items: - - name: Get started with Windows Sun Valley + - name: Get started items: - - name: Sun Valley overview + - name: Windows Sun Valley overview href: sv-overview.md - name: Windows Sun Valley requirements href: sv-requirements.md + - name: Sun Valley FAQ + href: sv-faq.md - - - name: Upgrade to Windows Sun Valley + - name: Deploy and Manage Windows Sun Valley items: - name: Plan to deploy Windows Sun Valley href: ../deployment/sv-planning.md @@ -21,13 +22,13 @@ href: ../configuration/sv-configure.md - name: Manage Windows Sun Valley href: ../client-management/sv-manage.md + - name: Windows Sun Valley application readiness + href: application-management/sv-app-readiness.md - - name: Windows Sun Valley Support + - name: Support items: - name: Windows Sun Valley lifecycle href: sv-lifecycle.md - - name: Windows Sun Valley application readiness - href: application-management/sv-app-readiness.md - - name: Sun Valley FAQ - href: sv-faq.md + + diff --git a/windows/sv/index.yml b/windows/sv/index.yml index dd25268757..f528902792 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -1,7 +1,7 @@ ### YamlMime:Landing title: Windows SV # < 60 chars -summary: Find out about Windows SV. # < 160 chars +summary: Find out about Windows Sun Valley. # < 160 chars metadata: title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. @@ -26,41 +26,36 @@ landingContent: linkLists: - linkListType: overview links: - - text: Link 1 - url: placeholder.md - - text: Link 2 - url: placeholder.md - - text: Link 3 - url: placeholder.md - - text: Link 4 - url: placeholder.md - + - text: Windows Sun Valley overview + url: sv-overview.md + - text: Windows Sun Valley requirements + url: sv-requirements.md + - text: Windows Sun Valley FAQ + url: sv-faq.md # Card (optional) - - title: Upgrade to Sun Valley + - title: Deploy Windows Sun Valley linkLists: - linkListType: overview links: - - text: Link 1 + - text: Plan to deploy Windows Sun Valley url: placeholder.md - - text: Link 2 + - text: Prepare for Windows Sun Valley url: placeholder.md - - text: Link 3 + - text: Deploy Windows Sun Valley url: placeholder.md - - text: Link 4 + - text: Configure Windows Sun Valley + url: placeholder.md + - text: Manage Windows Sun Valley + url: placeholder.md + - text: Windows Sun Valley application readiness url: placeholder.md - # Card (optional) - title: Support information linkLists: - linkListType: overview links: - - text: Link 1 - url: placeholder.md - - text: Link 2 - url: placeholder.md - - text: Link 3 - url: placeholder.md - - text: Link 4 + - text: Windows Sun Valley lifecycle url: placeholder.md + From 68f9baf2a90dea7ccb1359e50df688f9ba251597 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:19:50 -0700 Subject: [PATCH 006/104] draft4 --- windows/hub/TOC.yml | 4 +++- windows/hub/index.yml | 34 ++++++++++++++++++++++------------ windows/sv/TOC.yml | 2 ++ windows/sv/index.yml | 2 ++ 4 files changed, 29 insertions(+), 13 deletions(-) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 2d99b5fb17..36a3417877 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -1,8 +1,10 @@ -- name: Windows 10 +- name: Windows client href: index.yml items: - name: What's new href: /windows/whats-new + - name: Windows Sun Valley + href: /windows/sv - name: Release information href: /windows/release-health - name: Deployment diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 2714aec10e..7ecfe4e922 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -1,10 +1,10 @@ ### YamlMime:Landing -title: Windows 10 resources and documentation for IT Pros # < 60 chars +title: Windows client resources and documentation for IT Pros # < 60 chars summary: Plan, deploy, secure, and manage devices running Windows 10. # < 160 chars metadata: - title: Windows 10 documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. + title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. description: Evaluate, plan, deploy, secure and manage devices running Windows 10. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. @@ -26,12 +26,14 @@ landingContent: linkLists: - linkListType: overview links: - - text: What's new in Windows 10, version 21H1 + - text: Windows Sun Valley overview + url: /sv/sv-overview.md + - text: What's new in Windows Sun Valley, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - - text: What's new in Windows 10, version 20H2 - url: /windows/whats-new/whats-new-windows-10-version-20H2 - - text: What's new in Windows 10, version 2004 - url: /windows/whats-new/whats-new-windows-10-version-2004 + - text: What's new in Windows 10, version 21H2 + url: /windows/whats-new/whats-new-windows-10-version-21H1 + - text: Windows Sun Valley release information + url: /windows/release-health/release-information - text: Windows 10 release information url: /windows/release-health/release-information @@ -40,8 +42,10 @@ landingContent: linkLists: - linkListType: how-to-guide links: - - text: Configure Windows 10 + - text: Configure Windows client url: /windows/configuration/index + - text: Configure Windows Sun Valley + url: /windows/configuration/sv-configure.md - text: Accessibility information for IT Pros url: /windows/configuration/windows-10-accessibility-for-itpros - text: Configure access to Microsoft Store @@ -54,8 +58,10 @@ landingContent: linkLists: - linkListType: deploy links: - - text: Deploy and update Windows 10 + - text: Deploy and update Windows client url: /windows/deployment/index + - text: Deploy Windows Sun Valley + url: /windows/deployment/sv-deploy.md - text: Windows 10 deployment scenarios url: /windows/deployment/windows-10-deployment-scenarios - text: Create a deployment plan @@ -69,8 +75,10 @@ landingContent: linkLists: - linkListType: how-to-guide links: - - text: Windows 10 application management + - text: Windows application management url: /windows/application-management/index + - text: Windows Sun Valley application management + url: /windows/application-management/sv-app-manage.md - text: Understand the different apps included in Windows 10 url: /windows/application-management/apps-in-windows-10 - text: Get started with App-V for Windows 10 @@ -83,8 +91,10 @@ landingContent: linkLists: - linkListType: how-to-guide links: - - text: Windows 10 client management + - text: Windows client management url: /windows/client-management/index + - text: Manage Windows Sun Valley + url: /windows/client-management/sv-manage.md - text: Administrative tools in Windows 10 url: /windows/client-management/administrative-tools-in-windows-10 - text: Create mandatory user profiles @@ -97,7 +107,7 @@ landingContent: linkLists: - linkListType: how-to-guide links: - - text: Windows 10 Enterprise Security + - text: Windows Enterprise Security url: /windows/security/index - text: Windows Privacy url: /windows/privacy/index diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index 76ac398036..5e9b8425bd 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -29,6 +29,8 @@ items: - name: Windows Sun Valley lifecycle href: sv-lifecycle.md + - name: Windows Sun Valley release information + href: ../release-health diff --git a/windows/sv/index.yml b/windows/sv/index.yml index f528902792..61131a5288 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -58,4 +58,6 @@ landingContent: links: - text: Windows Sun Valley lifecycle url: placeholder.md + - text: Windows Sun Valley release information + url: ../release-health From 0b5e722bc9e78c763885157ec7ff287cf38248f9 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:25:16 -0700 Subject: [PATCH 007/104] draft5 --- windows/deployment/TOC.yml | 16 +- .../{sv-planning.md => sv-deploy.md} | 0 windows/deployment/sv-plan.md | 275 ++++++++++++++++++ windows/deployment/sv-prepare.md | 275 ++++++++++++++++++ 4 files changed, 560 insertions(+), 6 deletions(-) rename windows/deployment/{sv-planning.md => sv-deploy.md} (100%) create mode 100644 windows/deployment/sv-plan.md create mode 100644 windows/deployment/sv-prepare.md diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index fb5306a3e3..21fe4cf03f 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -5,7 +5,7 @@ items: - name: What's new href: deploy-whats-new.md - - name: Windows 10 deployment scenarios + - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? href: update/waas-quick-start.md @@ -34,7 +34,7 @@ - name: Plan items: - name: Windows Sun Valley deployment planning - href: sv-planning.md + href: sv-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria @@ -69,6 +69,8 @@ - name: Prepare items: + - name: Prepare to deploy Windows Sun Valley + href: sv-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md - name: Evaluate and update infrastructure @@ -98,11 +100,13 @@ - name: Deploy items: - - name: Deploy Windows 10 + - name: Deploy Windows client items: - - name: Deploy Windows 10 with Autopilot + - name: Windows Sun Valley deployment overview + href: sv-deploy.md + - name: Deploy Windows client with Autopilot href: windows-autopilot/index.yml - - name: Deploy Windows 10 with Configuration Manager + - name: Deploy Windows client with Configuration Manager items: - name: Deploy to a new device href: deploy-windows-cm/deploy-windows-10-using-pxe-and-configuration-manager.md @@ -112,7 +116,7 @@ href: deploy-windows-cm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md - name: In-place upgrade href: deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md - - name: Deploy Windows 10 with MDT + - name: Deploy Windows client with MDT items: - name: Deploy to a new device href: deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md diff --git a/windows/deployment/sv-planning.md b/windows/deployment/sv-deploy.md similarity index 100% rename from windows/deployment/sv-planning.md rename to windows/deployment/sv-deploy.md diff --git a/windows/deployment/sv-plan.md b/windows/deployment/sv-plan.md new file mode 100644 index 0000000000..e28a0eb0e8 --- /dev/null +++ b/windows/deployment/sv-plan.md @@ -0,0 +1,275 @@ +--- +title: Windows Sun Valley deployment planning +description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. +ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 +ms.reviewer: +manager: laurawi +ms.audience: itpro +ms.author: greglin +author: greg-lindsay +keywords: upgrade, in-place, configuration, deploy +ms.prod: w10 +ms.mktglfcycl: deploy +ms.localizationpriority: medium +ms.sitesec: library +audience: itpro +ms.topic: article +--- + +# Windows Sun Valley deployment planning + +**Applies to** +- Windows 10 + +To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. + +The following table summarizes various Windows 10 deployment scenarios. The scenarios are each assigned to one of three categories. +- Modern deployment methods are recommended unless you have a specific need to use a different procedure. These methods are supported with existing tools such as Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. These methods are discussed in detail on the [Modern Desktop Deployment Center](/microsoft-365/enterprise/desktop-deployment-center-home). + - Note: Once you have deployed Windows 10 in your organization, it is important to stay up to date by [creating a deployment plan](update/create-deployment-plan.md) for Windows 10 feature updates. +- Dynamic deployment methods enable you to configure applications and settings for specific use cases. +- Traditional deployment methods use existing tools to deploy operating system images.
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CategoryScenarioDescriptionMore information
Modern + +[Windows Autopilot](#windows-autopilot) + Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. + +Overview of Windows Autopilot +
+ +[In-place upgrade](#in-place-upgrade) + + + Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. + +Perform an in-place upgrade to Windows 10 with MDT
Perform an in-place upgrade to Windows 10 using Configuration Manager +
+ Dynamic + + +[Subscription Activation](#windows-10-subscription-activation) + + Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. + +Windows 10 Subscription Activation +
+ + [AAD / MDM](#dynamic-provisioning) + + The device is automatically joined to AAD and configured by MDM. + +Azure Active Directory integration with MDM +
+ + [Provisioning packages](#dynamic-provisioning) + + Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. + +Configure devices without MDM +
+ Traditional + + + [Bare metal](#new-computer) + + Deploy a new device, or wipe an existing device and deploy with a fresh image. + + Deploy a Windows 10 image using MDT
Deploy Windows 10 using PXE and Configuration Manager +
+ + [Refresh](#computer-refresh) + + Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. + + Refresh a Windows 7 computer with Windows 10
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager +
+ + [Replace](#computer-replace) + + Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. + + Replace a Windows 7 computer with a Windows 10 computer
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager +
+ +
  + + +>[!IMPORTANT] +>The Windows Autopilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later.
+>Except for clean install scenarios such as traditional bare metal and Windows Autopilot, all the methods described can optionally migrate apps and settings to the new OS. + +## Modern deployment methods + +Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. + +### Windows Autopilot + +Windows Autopilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows Autopilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. + +For more information about Windows Autopilot, see [Overview of Windows Autopilot](/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows Autopilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). + +### In-place upgrade + +For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. + +Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like Microsoft Endpoint Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences. + +The in-place upgrade process is designed to be extremely reliable, with the ability to automatically roll back to the previous operating system if any issues are encountered during the deployment process, without any IT staff involvement. Rolling back manually can also be done by leveraging the automatically-created recovery information (stored in the Windows.old folder), in case any issues are encountered after the upgrade is finished. The upgrade process is also typically faster than traditional deployments, because applications do not need to be reinstalled as part of the process. + +Because existing applications are preserved through the process, the upgrade process uses the standard Windows installation media image (Install.wim); custom images are not needed and cannot be used because the upgrade process is unable to deal with conflicts between apps in the old and new operating system. (For example, Contoso Timecard 1.0 in Windows 7 and Contoso Timecard 3.0 in the Windows 10 image.) + +Scenarios that support in-place upgrade with some additional procedures include changing from BIOS to UEFI boot mode and upgrade of devices that use non-Microsoft disk encryption software. + +- **Legacy BIOS to UEFI booting**: To perform an in-place upgrade on a UEFI-capable system that currently boots using legacy BIOS, first perform the in-place upgrade to Windows 10, maintaining the legacy BIOS boot mode. Windows 10 does not require UEFI, so it will work fine to upgrade a system using legacy BIOS emulation. After the upgrade, if you wish to enable Windows 10 features that require UEFI (such as Secure Boot), you can convert the system disk to a format that supports UEFI boot using the [MBR2GPT](./mbr-to-gpt.md) tool. Note: [UEFI specification](http://www.uefi.org/specifications) requires GPT disk layout. After the disk has been converted, you must also configure the firmware to boot in UEFI mode. + +- **Non-Microsoft disk encryption software**: While devices encrypted with BitLocker can easily be upgraded, more work is necessary for non-Microsoft disk encryption tools. Some ISVs will provide instructions on how to integrate their software into the in-place upgrade process. Check with your ISV to see if they have instructions. The following articles provide details on how to provision encryption drivers for use during Windows Setup via the ReflectDrivers setting: + - [Windows Setup Automation Overview](/windows-hardware/manufacture/desktop/windows-setup-automation-overview) + - [Windows Setup Command-Line Options](/windows-hardware/manufacture/desktop/windows-setup-command-line-options) + +There are some situations where you cannot use in-place upgrade; in these situations, you can use traditional deployment (wipe-and-load) instead. Examples of these situations include: + +- Changing from Windows 7, Windows 8, or Windows 8.1 x86 to Windows 10 x64. The upgrade process cannot change from a 32-bit operating system to a 64-bit operating system, because of possible complications with installed applications and drivers. +- Windows To Go and Boot from VHD installations. The upgrade process is unable to upgrade these installations. Instead, new installations would need to be performed. +- Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. +- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. + + +## Dynamic provisioning + +For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. + +The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: + +### Windows 10 Subscription Activation + +Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-enterprise-subscription-activation). + + +### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment + +In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](/windows/client-management/mdm/azure-active-directory-integration-with-mdm). + +### Provisioning package configuration + +Using the [Windows Imaging and Configuration Designer (ICD)](/windows/configuration/provisioning-packages/provisioning-install-icd), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). + +These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). + +While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. + +## Traditional deployment: + +New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md), and [Microsoft Endpoint Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). + +With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them. + +The traditional deployment scenario can be divided into different sub-scenarios. These are explained in detail in the following sections, but the following provides a brief summary: + +- **New computer.** A bare-metal deployment of a new machine. +- **Computer refresh.** A reinstall of the same machine (with user-state migration and an optional full Windows Imaging (WIM) image backup). +- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). + +### New computer + +Also called a "bare metal" deployment. This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). + +The deployment process for the new machine scenario is as follows: + +1. Start the setup from boot media (CD, USB, ISO, or PXE). + +2. Wipe the hard disk clean and create new volume(s). + +3. Install the operating system image. + +4. Install other applications (as part of the task sequence). + +After taking these steps, the computer is ready for use. + +### Computer refresh + +A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. + +The deployment process for the wipe-and-load scenario is as follows: + +1. Start the setup on a running operating system. + +2. Save the user state locally. + +3. Wipe the hard disk clean (except for the folder containing the backup). + +4. Install the operating system image. + +5. Install other applications. + +6. Restore the user state. + +After taking these steps, the machine is ready for use. + +### Computer replace + +A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. + +The deployment process for the replace scenario is as follows: + +1. Save the user state (data and settings) on the server through a backup job on the running operating system. + +2. Deploy the new computer as a bare-metal deployment. + + **Note**
In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. + +## Related topics + +- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) +- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) +- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) +- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md) +- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference) +- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) +- [UEFI firmware](/windows-hardware/design/device-experiences/oem-uefi) \ No newline at end of file diff --git a/windows/deployment/sv-prepare.md b/windows/deployment/sv-prepare.md new file mode 100644 index 0000000000..e28a0eb0e8 --- /dev/null +++ b/windows/deployment/sv-prepare.md @@ -0,0 +1,275 @@ +--- +title: Windows Sun Valley deployment planning +description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. +ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 +ms.reviewer: +manager: laurawi +ms.audience: itpro +ms.author: greglin +author: greg-lindsay +keywords: upgrade, in-place, configuration, deploy +ms.prod: w10 +ms.mktglfcycl: deploy +ms.localizationpriority: medium +ms.sitesec: library +audience: itpro +ms.topic: article +--- + +# Windows Sun Valley deployment planning + +**Applies to** +- Windows 10 + +To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. + +The following table summarizes various Windows 10 deployment scenarios. The scenarios are each assigned to one of three categories. +- Modern deployment methods are recommended unless you have a specific need to use a different procedure. These methods are supported with existing tools such as Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. These methods are discussed in detail on the [Modern Desktop Deployment Center](/microsoft-365/enterprise/desktop-deployment-center-home). + - Note: Once you have deployed Windows 10 in your organization, it is important to stay up to date by [creating a deployment plan](update/create-deployment-plan.md) for Windows 10 feature updates. +- Dynamic deployment methods enable you to configure applications and settings for specific use cases. +- Traditional deployment methods use existing tools to deploy operating system images.
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CategoryScenarioDescriptionMore information
Modern + +[Windows Autopilot](#windows-autopilot) + Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. + +Overview of Windows Autopilot +
+ +[In-place upgrade](#in-place-upgrade) + + + Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. + +Perform an in-place upgrade to Windows 10 with MDT
Perform an in-place upgrade to Windows 10 using Configuration Manager +
+ Dynamic + + +[Subscription Activation](#windows-10-subscription-activation) + + Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. + +Windows 10 Subscription Activation +
+ + [AAD / MDM](#dynamic-provisioning) + + The device is automatically joined to AAD and configured by MDM. + +Azure Active Directory integration with MDM +
+ + [Provisioning packages](#dynamic-provisioning) + + Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. + +Configure devices without MDM +
+ Traditional + + + [Bare metal](#new-computer) + + Deploy a new device, or wipe an existing device and deploy with a fresh image. + + Deploy a Windows 10 image using MDT
Deploy Windows 10 using PXE and Configuration Manager +
+ + [Refresh](#computer-refresh) + + Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. + + Refresh a Windows 7 computer with Windows 10
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager +
+ + [Replace](#computer-replace) + + Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. + + Replace a Windows 7 computer with a Windows 10 computer
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager +
+ +
  + + +>[!IMPORTANT] +>The Windows Autopilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later.
+>Except for clean install scenarios such as traditional bare metal and Windows Autopilot, all the methods described can optionally migrate apps and settings to the new OS. + +## Modern deployment methods + +Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. + +### Windows Autopilot + +Windows Autopilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows Autopilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. + +For more information about Windows Autopilot, see [Overview of Windows Autopilot](/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows Autopilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). + +### In-place upgrade + +For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. + +Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like Microsoft Endpoint Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences. + +The in-place upgrade process is designed to be extremely reliable, with the ability to automatically roll back to the previous operating system if any issues are encountered during the deployment process, without any IT staff involvement. Rolling back manually can also be done by leveraging the automatically-created recovery information (stored in the Windows.old folder), in case any issues are encountered after the upgrade is finished. The upgrade process is also typically faster than traditional deployments, because applications do not need to be reinstalled as part of the process. + +Because existing applications are preserved through the process, the upgrade process uses the standard Windows installation media image (Install.wim); custom images are not needed and cannot be used because the upgrade process is unable to deal with conflicts between apps in the old and new operating system. (For example, Contoso Timecard 1.0 in Windows 7 and Contoso Timecard 3.0 in the Windows 10 image.) + +Scenarios that support in-place upgrade with some additional procedures include changing from BIOS to UEFI boot mode and upgrade of devices that use non-Microsoft disk encryption software. + +- **Legacy BIOS to UEFI booting**: To perform an in-place upgrade on a UEFI-capable system that currently boots using legacy BIOS, first perform the in-place upgrade to Windows 10, maintaining the legacy BIOS boot mode. Windows 10 does not require UEFI, so it will work fine to upgrade a system using legacy BIOS emulation. After the upgrade, if you wish to enable Windows 10 features that require UEFI (such as Secure Boot), you can convert the system disk to a format that supports UEFI boot using the [MBR2GPT](./mbr-to-gpt.md) tool. Note: [UEFI specification](http://www.uefi.org/specifications) requires GPT disk layout. After the disk has been converted, you must also configure the firmware to boot in UEFI mode. + +- **Non-Microsoft disk encryption software**: While devices encrypted with BitLocker can easily be upgraded, more work is necessary for non-Microsoft disk encryption tools. Some ISVs will provide instructions on how to integrate their software into the in-place upgrade process. Check with your ISV to see if they have instructions. The following articles provide details on how to provision encryption drivers for use during Windows Setup via the ReflectDrivers setting: + - [Windows Setup Automation Overview](/windows-hardware/manufacture/desktop/windows-setup-automation-overview) + - [Windows Setup Command-Line Options](/windows-hardware/manufacture/desktop/windows-setup-command-line-options) + +There are some situations where you cannot use in-place upgrade; in these situations, you can use traditional deployment (wipe-and-load) instead. Examples of these situations include: + +- Changing from Windows 7, Windows 8, or Windows 8.1 x86 to Windows 10 x64. The upgrade process cannot change from a 32-bit operating system to a 64-bit operating system, because of possible complications with installed applications and drivers. +- Windows To Go and Boot from VHD installations. The upgrade process is unable to upgrade these installations. Instead, new installations would need to be performed. +- Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. +- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. + + +## Dynamic provisioning + +For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. + +The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: + +### Windows 10 Subscription Activation + +Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-enterprise-subscription-activation). + + +### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment + +In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](/windows/client-management/mdm/azure-active-directory-integration-with-mdm). + +### Provisioning package configuration + +Using the [Windows Imaging and Configuration Designer (ICD)](/windows/configuration/provisioning-packages/provisioning-install-icd), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). + +These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). + +While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. + +## Traditional deployment: + +New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md), and [Microsoft Endpoint Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). + +With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them. + +The traditional deployment scenario can be divided into different sub-scenarios. These are explained in detail in the following sections, but the following provides a brief summary: + +- **New computer.** A bare-metal deployment of a new machine. +- **Computer refresh.** A reinstall of the same machine (with user-state migration and an optional full Windows Imaging (WIM) image backup). +- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). + +### New computer + +Also called a "bare metal" deployment. This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). + +The deployment process for the new machine scenario is as follows: + +1. Start the setup from boot media (CD, USB, ISO, or PXE). + +2. Wipe the hard disk clean and create new volume(s). + +3. Install the operating system image. + +4. Install other applications (as part of the task sequence). + +After taking these steps, the computer is ready for use. + +### Computer refresh + +A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. + +The deployment process for the wipe-and-load scenario is as follows: + +1. Start the setup on a running operating system. + +2. Save the user state locally. + +3. Wipe the hard disk clean (except for the folder containing the backup). + +4. Install the operating system image. + +5. Install other applications. + +6. Restore the user state. + +After taking these steps, the machine is ready for use. + +### Computer replace + +A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. + +The deployment process for the replace scenario is as follows: + +1. Save the user state (data and settings) on the server through a backup job on the running operating system. + +2. Deploy the new computer as a bare-metal deployment. + + **Note**
In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. + +## Related topics + +- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) +- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) +- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) +- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md) +- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference) +- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) +- [UEFI firmware](/windows-hardware/design/device-experiences/oem-uefi) \ No newline at end of file From 0e6ff045990caa70188ebd15afd380822e5c2b84 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:32:07 -0700 Subject: [PATCH 008/104] draft6 --- windows/hub/TOC.yml | 4 +-- windows/hub/index.yml | 12 ++++---- windows/sv/breadcrumb/toc.yml | 53 +++++++++++++++++++++++++++++++++++ 3 files changed, 61 insertions(+), 8 deletions(-) create mode 100644 windows/sv/breadcrumb/toc.yml diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 36a3417877..5ba5004d55 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -3,10 +3,10 @@ items: - name: What's new href: /windows/whats-new - - name: Windows Sun Valley - href: /windows/sv - name: Release information href: /windows/release-health + - name: Windows Sun Valley + href: /windows/sv - name: Deployment href: /windows/deployment - name: Configuration diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 7ecfe4e922..5a9ddebb3d 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -1,11 +1,11 @@ ### YamlMime:Landing title: Windows client resources and documentation for IT Pros # < 60 chars -summary: Plan, deploy, secure, and manage devices running Windows 10. # < 160 chars +summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows Sun Valley. # < 160 chars metadata: title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Evaluate, plan, deploy, secure and manage devices running Windows 10. # Required; article description that is displayed in search results. < 160 chars. + description: Evaluate, plan, deploy, secure and manage devices running Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice @@ -62,11 +62,11 @@ landingContent: url: /windows/deployment/index - text: Deploy Windows Sun Valley url: /windows/deployment/sv-deploy.md - - text: Windows 10 deployment scenarios + - text: Windows deployment scenarios url: /windows/deployment/windows-10-deployment-scenarios - text: Create a deployment plan url: /windows/deployment/update/create-deployment-plan - - text: Prepare to deploy Windows 10 + - text: Prepare to deploy Windows client url: /windows/deployment/update/prepare-deploy-windows @@ -77,7 +77,7 @@ landingContent: links: - text: Windows application management url: /windows/application-management/index - - text: Windows Sun Valley application management + - text: Manage Windows Sun Valley applications url: /windows/application-management/sv-app-manage.md - text: Understand the different apps included in Windows 10 url: /windows/application-management/apps-in-windows-10 @@ -95,7 +95,7 @@ landingContent: url: /windows/client-management/index - text: Manage Windows Sun Valley url: /windows/client-management/sv-manage.md - - text: Administrative tools in Windows 10 + - text: Administrative tools url: /windows/client-management/administrative-tools-in-windows-10 - text: Create mandatory user profiles url: /windows/client-management/mandatory-user-profile diff --git a/windows/sv/breadcrumb/toc.yml b/windows/sv/breadcrumb/toc.yml new file mode 100644 index 0000000000..e2971f2d84 --- /dev/null +++ b/windows/sv/breadcrumb/toc.yml @@ -0,0 +1,53 @@ +- name: Docs + tocHref: / + topicHref: / + items: + - name: Windows + tocHref: /windows + topicHref: /windows/windows-10 + items: + - name: What's new + tocHref: /windows/whats-new/ + topicHref: /windows/whats-new/index + - name: Configuration + tocHref: /windows/configuration/ + topicHref: /windows/configuration/index + - name: Deployment + tocHref: /windows/deployment/ + topicHref: /windows/deployment/index + - name: Application management + tocHref: /windows/application-management/ + topicHref: /windows/application-management/index + - name: Client management + tocHref: /windows/client-management/ + topicHref: /windows/client-management/index + items: + - name: Mobile Device Management + tocHref: /windows/client-management/mdm/ + topicHref: /windows/client-management/mdm/index + - name: Release information + tocHref: /windows/release-information/ + topicHref: /windows/release-health/release-information + - name: Privacy + tocHref: /windows/privacy/ + topicHref: /windows/privacy/index + - name: Security + tocHref: /windows/security/ + topicHref: /windows/security/index + items: + - name: Identity and access protection + tocHref: /windows/security/identity-protection/ + topicHref: /windows/security/identity-protection/index + items: + - name: Windows Hello for Business + tocHref: /windows/security/identity-protection/hello-for-business + topicHref: /windows/security/identity-protection/hello-for-business/hello-identity-verification + - name: Threat protection + tocHref: /windows/security/threat-protection/ + topicHref: /windows/security/threat-protection/index + - name: Information protection + tocHref: /windows/security/information-protection/ + topicHref: /windows/security/information-protection/index + - name: Hardware-based protection + tocHref: /windows/security/hardware-protection/ + topicHref: /windows/security/hardware-protection/index From 3c67265d05561e89ed4f341db665255b0e5f6fd1 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:37:00 -0700 Subject: [PATCH 009/104] draft7 --- windows/sv/TOC.yml | 2 +- windows/sv/sv-faq.md | 4 ++-- windows/sv/sv-lifecycle.md | 22 ++++++++++++++++++++++ windows/sv/sv-overview.md | 4 ++-- windows/sv/sv-requirements.md | 4 ++-- 5 files changed, 29 insertions(+), 7 deletions(-) create mode 100644 windows/sv/sv-lifecycle.md diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index 5e9b8425bd..fb7d2ccba4 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -13,7 +13,7 @@ - name: Deploy and Manage Windows Sun Valley items: - name: Plan to deploy Windows Sun Valley - href: ../deployment/sv-planning.md + href: ../deployment/sv-plan.md - name: Prepare for Windows Sun Valley href: ../deployment/sv-prepare.md - name: Deploy Windows Sun Valley diff --git a/windows/sv/sv-faq.md b/windows/sv/sv-faq.md index fecfe94a8e..220beac886 100644 --- a/windows/sv/sv-faq.md +++ b/windows/sv/sv-faq.md @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Placeholder +# Windows Sun Valley frequently asked questions (FAQ) -Placeholder text. +FAQ. diff --git a/windows/sv/sv-lifecycle.md b/windows/sv/sv-lifecycle.md new file mode 100644 index 0000000000..c16baa14b7 --- /dev/null +++ b/windows/sv/sv-lifecycle.md @@ -0,0 +1,22 @@ +--- +title: Lifecycle +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Windows Sun Valley lifecycle + +Sun Valley lifecycle. + diff --git a/windows/sv/sv-overview.md b/windows/sv/sv-overview.md index fecfe94a8e..4099c30662 100644 --- a/windows/sv/sv-overview.md +++ b/windows/sv/sv-overview.md @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Placeholder +# Windows Sun Valley overview -Placeholder text. +Overview of Sun Valley. diff --git a/windows/sv/sv-requirements.md b/windows/sv/sv-requirements.md index fecfe94a8e..5e4a647fea 100644 --- a/windows/sv/sv-requirements.md +++ b/windows/sv/sv-requirements.md @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Placeholder +# Windows Sun Valley requirements -Placeholder text. +Windows Sun Valley requirements. From 659c59863498881b486a0a062f8af9d75833adec Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:44:43 -0700 Subject: [PATCH 010/104] draft8 --- windows/sv/TOC.yml | 14 +++++++------- windows/sv/index.yml | 12 ++++++------ 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index fb7d2ccba4..355d8e61c1 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -13,24 +13,24 @@ - name: Deploy and Manage Windows Sun Valley items: - name: Plan to deploy Windows Sun Valley - href: ../deployment/sv-plan.md + href: /windows/deployment/sv-plan.md - name: Prepare for Windows Sun Valley - href: ../deployment/sv-prepare.md + href: /windows/deployment/sv-prepare.md - name: Deploy Windows Sun Valley - href: ../deployment/sv-deploy.md + href: /windows/deployment/sv-deploy.md - name: Configure Windows Sun Valley - href: ../configuration/sv-configure.md + href: /windows/configuration/sv-configure.md - name: Manage Windows Sun Valley - href: ../client-management/sv-manage.md + href: /windows/client-management/sv-manage.md - name: Windows Sun Valley application readiness - href: application-management/sv-app-readiness.md + href: /windows/application-management/sv-app-readiness.md - name: Support items: - name: Windows Sun Valley lifecycle href: sv-lifecycle.md - name: Windows Sun Valley release information - href: ../release-health + href: /windows/release-health diff --git a/windows/sv/index.yml b/windows/sv/index.yml index 61131a5288..477ed81e72 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -39,17 +39,17 @@ landingContent: - linkListType: overview links: - text: Plan to deploy Windows Sun Valley - url: placeholder.md + url: /windows/deployment/sv-plan.md - text: Prepare for Windows Sun Valley - url: placeholder.md + url: /windows/deployment/sv-prepare.md - text: Deploy Windows Sun Valley - url: placeholder.md + url: /windows/deployment/sv-deploy.md - text: Configure Windows Sun Valley - url: placeholder.md + url: /windows/configuration/sv-configure.md - text: Manage Windows Sun Valley - url: placeholder.md + url: /windows/client-management/sv-manage.md - text: Windows Sun Valley application readiness - url: placeholder.md + url: /windows/application-management/sv-app-readiness.md # Card (optional) - title: Support information From a9eea14b6088c303110d976e4b3d013da119d3d0 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:50:25 -0700 Subject: [PATCH 011/104] draft9 --- windows/deployment/TOC.yml | 2 ++ windows/deployment/index.yml | 10 ++++++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 21fe4cf03f..9eb39c2bb6 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -5,6 +5,8 @@ items: - name: What's new href: deploy-whats-new.md + - name: Windows Sun Valley deployment overview + href: sv-deploy.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index 55641790b7..12426c9a08 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -1,10 +1,10 @@ ### YamlMime:Landing -title: Windows 10 deployment resources and documentation # < 60 chars +title: Windows client deployment resources and documentation # < 60 chars summary: Learn about deploying and keeping Windows 10 up to date. # < 160 chars metadata: - title: Windows 10 deployment resources and documentation # Required; page title displayed in search results. Include the brand. < 60 chars. + title: Windows client deployment resources and documentation # Required; page title displayed in search results. Include the brand. < 60 chars. description: Learn about deploying Windows 10 and keeping it up to date in your organization. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. @@ -40,7 +40,7 @@ landingContent: linkLists: - linkListType: how-to-guide links: - - text: Prepare to deploy Windows 10 updates + - text: Prepare to deploy Windows updates url: update/prepare-deploy-windows.md - text: Prepare updates using Windows Update for Business url: update/waas-manage-updates-wufb.md @@ -66,7 +66,9 @@ landingContent: links: - text: What's new in Windows deployment url: windows-10-deployment-scenarios.md - - text: Windows 10 deployment scenarios + - text: Windows Sun Valley deployment overview + url: sv-deploy.md + - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md - text: Basics of Windows updates, channels, and tools url: update/get-started-updates-channels-tools.md From 52ff9eaae898127e8195f0b3051740fa35368944 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 21 May 2021 10:57:41 -0700 Subject: [PATCH 012/104] draft10 --- windows/deployment/deploy-whats-new.md | 8 +- windows/deployment/index.yml | 2 +- windows/deployment/sv-deploy.md | 254 +------------------------ 3 files changed, 8 insertions(+), 256 deletions(-) diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index 4707849d86..95cc27289d 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -1,9 +1,9 @@ --- -title: What's new in Windows 10 deployment +title: What's new in Windows client deployment ms.reviewer: manager: laurawi ms.author: greglin -description: Use this article to learn about new solutions and online content related to deploying Windows 10 in your organization. +description: Use this article to learn about new solutions and online content related to deploying Windows in your organization. keywords: deployment, automate, tools, configure, news ms.mktglfcycl: deploy ms.localizationpriority: medium @@ -20,12 +20,14 @@ ms.custom: seo-marvel-apr2020 **Applies to:** - Windows 10 +- Windows Sun Valley ## In this topic -This topic provides an overview of new solutions and online content related to deploying Windows 10 in your organization. +This topic provides an overview of new solutions and online content related to deploying Windows client in your organization. - For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index). +- For an all-up overview of new features in Windows Sun Valley, see [What's new in Windows Sun Valley](/windows/whats-new/index). ## Latest news diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index 12426c9a08..10182bbea5 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -65,7 +65,7 @@ landingContent: - linkListType: overview links: - text: What's new in Windows deployment - url: windows-10-deployment-scenarios.md + url: deploy-whats-new.md - text: Windows Sun Valley deployment overview url: sv-deploy.md - text: Windows client deployment scenarios diff --git a/windows/deployment/sv-deploy.md b/windows/deployment/sv-deploy.md index e28a0eb0e8..75df574256 100644 --- a/windows/deployment/sv-deploy.md +++ b/windows/deployment/sv-deploy.md @@ -19,257 +19,7 @@ ms.topic: article # Windows Sun Valley deployment planning **Applies to** -- Windows 10 +- Windows Sun Valley -To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. +To successfully deploy the Windows Sun Valley operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. -The following table summarizes various Windows 10 deployment scenarios. The scenarios are each assigned to one of three categories. -- Modern deployment methods are recommended unless you have a specific need to use a different procedure. These methods are supported with existing tools such as Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. These methods are discussed in detail on the [Modern Desktop Deployment Center](/microsoft-365/enterprise/desktop-deployment-center-home). - - Note: Once you have deployed Windows 10 in your organization, it is important to stay up to date by [creating a deployment plan](update/create-deployment-plan.md) for Windows 10 feature updates. -- Dynamic deployment methods enable you to configure applications and settings for specific use cases. -- Traditional deployment methods use existing tools to deploy operating system images.
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CategoryScenarioDescriptionMore information
Modern - -[Windows Autopilot](#windows-autopilot) - Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. - -Overview of Windows Autopilot -
- -[In-place upgrade](#in-place-upgrade) - - - Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. - -Perform an in-place upgrade to Windows 10 with MDT
Perform an in-place upgrade to Windows 10 using Configuration Manager -
- Dynamic - - -[Subscription Activation](#windows-10-subscription-activation) - - Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. - -Windows 10 Subscription Activation -
- - [AAD / MDM](#dynamic-provisioning) - - The device is automatically joined to AAD and configured by MDM. - -Azure Active Directory integration with MDM -
- - [Provisioning packages](#dynamic-provisioning) - - Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. - -Configure devices without MDM -
- Traditional - - - [Bare metal](#new-computer) - - Deploy a new device, or wipe an existing device and deploy with a fresh image. - - Deploy a Windows 10 image using MDT
Deploy Windows 10 using PXE and Configuration Manager -
- - [Refresh](#computer-refresh) - - Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. - - Refresh a Windows 7 computer with Windows 10
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager -
- - [Replace](#computer-replace) - - Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. - - Replace a Windows 7 computer with a Windows 10 computer
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager -
- -
  - - ->[!IMPORTANT] ->The Windows Autopilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later.
->Except for clean install scenarios such as traditional bare metal and Windows Autopilot, all the methods described can optionally migrate apps and settings to the new OS. - -## Modern deployment methods - -Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. - -### Windows Autopilot - -Windows Autopilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows Autopilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. - -For more information about Windows Autopilot, see [Overview of Windows Autopilot](/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows Autopilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). - -### In-place upgrade - -For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. - -Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like Microsoft Endpoint Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences. - -The in-place upgrade process is designed to be extremely reliable, with the ability to automatically roll back to the previous operating system if any issues are encountered during the deployment process, without any IT staff involvement. Rolling back manually can also be done by leveraging the automatically-created recovery information (stored in the Windows.old folder), in case any issues are encountered after the upgrade is finished. The upgrade process is also typically faster than traditional deployments, because applications do not need to be reinstalled as part of the process. - -Because existing applications are preserved through the process, the upgrade process uses the standard Windows installation media image (Install.wim); custom images are not needed and cannot be used because the upgrade process is unable to deal with conflicts between apps in the old and new operating system. (For example, Contoso Timecard 1.0 in Windows 7 and Contoso Timecard 3.0 in the Windows 10 image.) - -Scenarios that support in-place upgrade with some additional procedures include changing from BIOS to UEFI boot mode and upgrade of devices that use non-Microsoft disk encryption software. - -- **Legacy BIOS to UEFI booting**: To perform an in-place upgrade on a UEFI-capable system that currently boots using legacy BIOS, first perform the in-place upgrade to Windows 10, maintaining the legacy BIOS boot mode. Windows 10 does not require UEFI, so it will work fine to upgrade a system using legacy BIOS emulation. After the upgrade, if you wish to enable Windows 10 features that require UEFI (such as Secure Boot), you can convert the system disk to a format that supports UEFI boot using the [MBR2GPT](./mbr-to-gpt.md) tool. Note: [UEFI specification](http://www.uefi.org/specifications) requires GPT disk layout. After the disk has been converted, you must also configure the firmware to boot in UEFI mode. - -- **Non-Microsoft disk encryption software**: While devices encrypted with BitLocker can easily be upgraded, more work is necessary for non-Microsoft disk encryption tools. Some ISVs will provide instructions on how to integrate their software into the in-place upgrade process. Check with your ISV to see if they have instructions. The following articles provide details on how to provision encryption drivers for use during Windows Setup via the ReflectDrivers setting: - - [Windows Setup Automation Overview](/windows-hardware/manufacture/desktop/windows-setup-automation-overview) - - [Windows Setup Command-Line Options](/windows-hardware/manufacture/desktop/windows-setup-command-line-options) - -There are some situations where you cannot use in-place upgrade; in these situations, you can use traditional deployment (wipe-and-load) instead. Examples of these situations include: - -- Changing from Windows 7, Windows 8, or Windows 8.1 x86 to Windows 10 x64. The upgrade process cannot change from a 32-bit operating system to a 64-bit operating system, because of possible complications with installed applications and drivers. -- Windows To Go and Boot from VHD installations. The upgrade process is unable to upgrade these installations. Instead, new installations would need to be performed. -- Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. -- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. - - -## Dynamic provisioning - -For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. - -The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: - -### Windows 10 Subscription Activation - -Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-enterprise-subscription-activation). - - -### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment - -In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](/windows/client-management/mdm/azure-active-directory-integration-with-mdm). - -### Provisioning package configuration - -Using the [Windows Imaging and Configuration Designer (ICD)](/windows/configuration/provisioning-packages/provisioning-install-icd), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). - -These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). - -While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. - -## Traditional deployment: - -New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md), and [Microsoft Endpoint Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). - -With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them. - -The traditional deployment scenario can be divided into different sub-scenarios. These are explained in detail in the following sections, but the following provides a brief summary: - -- **New computer.** A bare-metal deployment of a new machine. -- **Computer refresh.** A reinstall of the same machine (with user-state migration and an optional full Windows Imaging (WIM) image backup). -- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). - -### New computer - -Also called a "bare metal" deployment. This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). - -The deployment process for the new machine scenario is as follows: - -1. Start the setup from boot media (CD, USB, ISO, or PXE). - -2. Wipe the hard disk clean and create new volume(s). - -3. Install the operating system image. - -4. Install other applications (as part of the task sequence). - -After taking these steps, the computer is ready for use. - -### Computer refresh - -A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. - -The deployment process for the wipe-and-load scenario is as follows: - -1. Start the setup on a running operating system. - -2. Save the user state locally. - -3. Wipe the hard disk clean (except for the folder containing the backup). - -4. Install the operating system image. - -5. Install other applications. - -6. Restore the user state. - -After taking these steps, the machine is ready for use. - -### Computer replace - -A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. - -The deployment process for the replace scenario is as follows: - -1. Save the user state (data and settings) on the server through a backup job on the running operating system. - -2. Deploy the new computer as a bare-metal deployment. - - **Note**
In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. - -## Related topics - -- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) -- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) -- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) -- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md) -- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference) -- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) -- [UEFI firmware](/windows-hardware/design/device-experiences/oem-uefi) \ No newline at end of file From 0e1b842fb9016049e452ec258fde08b5db5f595c Mon Sep 17 00:00:00 2001 From: Thomas Raya Date: Mon, 24 May 2021 10:01:48 -0700 Subject: [PATCH 013/104] Update TOC.yml test site relative link --- windows/sv/TOC.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index 355d8e61c1..a293d047ad 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -13,7 +13,7 @@ - name: Deploy and Manage Windows Sun Valley items: - name: Plan to deploy Windows Sun Valley - href: /windows/deployment/sv-plan.md + href: /windows/deployment/sv-plan - name: Prepare for Windows Sun Valley href: /windows/deployment/sv-prepare.md - name: Deploy Windows Sun Valley From 8b70ad21214bff96116460ecaaf711bed625eada Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 1 Jun 2021 09:21:51 -0700 Subject: [PATCH 014/104] sv to 11 --- .openpublishing.publish.config.json | 6 ++-- windows/application-management/index.yml | 2 +- windows/deployment/TOC.yml | 8 ++--- windows/deployment/deploy-whats-new.md | 4 +-- windows/deployment/index.yml | 2 +- windows/deployment/sv-deploy.md | 8 ++--- windows/deployment/sv-plan.md | 4 +-- windows/deployment/sv-prepare.md | 4 +-- windows/hub/TOC.yml | 4 +-- windows/hub/index.yml | 30 ++++++++-------- windows/sv/TOC.yml | 36 ------------------- windows/windows-11/TOC.yml | 36 +++++++++++++++++++ windows/{sv => windows-11}/breadcrumb/toc.yml | 0 windows/{sv => windows-11}/docfx.json | 4 +-- windows/{sv => windows-11}/index.yml | 26 +++++++------- windows/{sv => windows-11}/placeholder.md | 0 .../windows-11-faq.md} | 5 ++- .../windows-11-lifecycle.md} | 7 ++-- .../windows-11-overview.md} | 4 +-- .../windows-11-requirements.md} | 4 +-- 20 files changed, 96 insertions(+), 98 deletions(-) delete mode 100644 windows/sv/TOC.yml create mode 100644 windows/windows-11/TOC.yml rename windows/{sv => windows-11}/breadcrumb/toc.yml (100%) rename windows/{sv => windows-11}/docfx.json (90%) rename windows/{sv => windows-11}/index.yml (75%) rename windows/{sv => windows-11}/placeholder.md (100%) rename windows/{sv/sv-requirements.md => windows-11/windows-11-faq.md} (71%) rename windows/{sv/sv-lifecycle.md => windows-11/windows-11-lifecycle.md} (69%) rename windows/{sv/sv-overview.md => windows-11/windows-11-overview.md} (86%) rename windows/{sv/sv-faq.md => windows-11/windows-11-requirements.md} (85%) diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json index ecd7571ea7..4fc470da75 100644 --- a/.openpublishing.publish.config.json +++ b/.openpublishing.publish.config.json @@ -130,9 +130,9 @@ "template_folder": "_themes" }, { - "docset_name": "SV", - "build_source_folder": "windows/sv", - "build_output_subfolder": "SV", + "docset_name": "windows-11", + "build_source_folder": "windows/windows-11", + "build_output_subfolder": "windows-11", "locale": "en-us", "monikers": [], "moniker_ranges": [], diff --git a/windows/application-management/index.yml b/windows/application-management/index.yml index dc786fd289..d3a95df0d0 100644 --- a/windows/application-management/index.yml +++ b/windows/application-management/index.yml @@ -5,7 +5,7 @@ summary: Learn about managing applications in Windows client, including how to r metadata: title: Windows application management # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Learn about managing applications in Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Learn about managing applications in Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 9eb39c2bb6..3a19c56f54 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -5,7 +5,7 @@ items: - name: What's new href: deploy-whats-new.md - - name: Windows Sun Valley deployment overview + - name: Windows 11 deployment overview href: sv-deploy.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md @@ -35,7 +35,7 @@ - name: Plan items: - - name: Windows Sun Valley deployment planning + - name: Windows 11 deployment planning href: sv-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md @@ -71,7 +71,7 @@ - name: Prepare items: - - name: Prepare to deploy Windows Sun Valley + - name: Prepare to deploy Windows 11 href: sv-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md @@ -104,7 +104,7 @@ items: - name: Deploy Windows client items: - - name: Windows Sun Valley deployment overview + - name: Windows 11 deployment overview href: sv-deploy.md - name: Deploy Windows client with Autopilot href: windows-autopilot/index.yml diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index 95cc27289d..03d5ce122e 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -20,14 +20,14 @@ ms.custom: seo-marvel-apr2020 **Applies to:** - Windows 10 -- Windows Sun Valley +- Windows 11 ## In this topic This topic provides an overview of new solutions and online content related to deploying Windows client in your organization. - For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index). -- For an all-up overview of new features in Windows Sun Valley, see [What's new in Windows Sun Valley](/windows/whats-new/index). +- For an all-up overview of new features in Windows 11, see [What's new in Windows 11](/windows/whats-new/index). ## Latest news diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index 10182bbea5..f6f9bf26ec 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -66,7 +66,7 @@ landingContent: links: - text: What's new in Windows deployment url: deploy-whats-new.md - - text: Windows Sun Valley deployment overview + - text: Windows 11 deployment overview url: sv-deploy.md - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md diff --git a/windows/deployment/sv-deploy.md b/windows/deployment/sv-deploy.md index 75df574256..ca92e990a7 100644 --- a/windows/deployment/sv-deploy.md +++ b/windows/deployment/sv-deploy.md @@ -1,5 +1,5 @@ --- -title: Windows Sun Valley deployment planning +title: Windows 11 deployment planning description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 ms.reviewer: @@ -16,10 +16,10 @@ audience: itpro ms.topic: article --- -# Windows Sun Valley deployment planning +# Windows 11 deployment planning **Applies to** -- Windows Sun Valley +- Windows 11, version 21H1 -To successfully deploy the Windows Sun Valley operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. +To successfully deploy the Windows 11 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. diff --git a/windows/deployment/sv-plan.md b/windows/deployment/sv-plan.md index e28a0eb0e8..cd88a54b3d 100644 --- a/windows/deployment/sv-plan.md +++ b/windows/deployment/sv-plan.md @@ -1,5 +1,5 @@ --- -title: Windows Sun Valley deployment planning +title: Windows 11 deployment planning description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 ms.reviewer: @@ -16,7 +16,7 @@ audience: itpro ms.topic: article --- -# Windows Sun Valley deployment planning +# Windows 11 deployment planning **Applies to** - Windows 10 diff --git a/windows/deployment/sv-prepare.md b/windows/deployment/sv-prepare.md index e28a0eb0e8..cd88a54b3d 100644 --- a/windows/deployment/sv-prepare.md +++ b/windows/deployment/sv-prepare.md @@ -1,5 +1,5 @@ --- -title: Windows Sun Valley deployment planning +title: Windows 11 deployment planning description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 ms.reviewer: @@ -16,7 +16,7 @@ audience: itpro ms.topic: article --- -# Windows Sun Valley deployment planning +# Windows 11 deployment planning **Applies to** - Windows 10 diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 5ba5004d55..812bcc04b5 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -5,8 +5,8 @@ href: /windows/whats-new - name: Release information href: /windows/release-health - - name: Windows Sun Valley - href: /windows/sv + - name: Windows 11 + href: /windows/windows-11 - name: Deployment href: /windows/deployment - name: Configuration diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 5a9ddebb3d..572df40317 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -1,11 +1,11 @@ ### YamlMime:Landing title: Windows client resources and documentation for IT Pros # < 60 chars -summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows Sun Valley. # < 160 chars +summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # < 160 chars metadata: title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Evaluate, plan, deploy, secure and manage devices running Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Evaluate, plan, deploy, secure and manage devices running Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice @@ -13,7 +13,7 @@ metadata: ms.collection: windows-10 author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. ms.author: greglin #Required; microsoft alias of author; optional team alias. - ms.date: 10/20/2020 #Required; mm/dd/yyyy format. + ms.date: 06/01/2020 #Required; mm/dd/yyyy format. localization_priority: medium # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new @@ -26,13 +26,13 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows Sun Valley overview - url: /sv/sv-overview.md - - text: What's new in Windows Sun Valley, version 21H2 + - text: Windows 11 overview + url: /windows-11/windows-11-overview.md + - text: What's new in Windows 11, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - - text: Windows Sun Valley release information + - text: Windows 11 release information url: /windows/release-health/release-information - text: Windows 10 release information url: /windows/release-health/release-information @@ -44,8 +44,8 @@ landingContent: links: - text: Configure Windows client url: /windows/configuration/index - - text: Configure Windows Sun Valley - url: /windows/configuration/sv-configure.md + - text: Configure Windows 11 + url: /windows/configuration/windows-11-configure.md - text: Accessibility information for IT Pros url: /windows/configuration/windows-10-accessibility-for-itpros - text: Configure access to Microsoft Store @@ -60,8 +60,8 @@ landingContent: links: - text: Deploy and update Windows client url: /windows/deployment/index - - text: Deploy Windows Sun Valley - url: /windows/deployment/sv-deploy.md + - text: Deploy Windows 11 + url: /windows/deployment/windows-11-deploy.md - text: Windows deployment scenarios url: /windows/deployment/windows-10-deployment-scenarios - text: Create a deployment plan @@ -77,8 +77,8 @@ landingContent: links: - text: Windows application management url: /windows/application-management/index - - text: Manage Windows Sun Valley applications - url: /windows/application-management/sv-app-manage.md + - text: Manage Windows 11 applications + url: /windows/application-management/windows-11-app-manage.md - text: Understand the different apps included in Windows 10 url: /windows/application-management/apps-in-windows-10 - text: Get started with App-V for Windows 10 @@ -93,8 +93,8 @@ landingContent: links: - text: Windows client management url: /windows/client-management/index - - text: Manage Windows Sun Valley - url: /windows/client-management/sv-manage.md + - text: Manage Windows 11 + url: /windows/client-management/windows-11-manage.md - text: Administrative tools url: /windows/client-management/administrative-tools-in-windows-10 - text: Create mandatory user profiles diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml deleted file mode 100644 index a293d047ad..0000000000 --- a/windows/sv/TOC.yml +++ /dev/null @@ -1,36 +0,0 @@ -- name: Windows Sun Valley - href: index.yml - items: - - name: Get started - items: - - name: Windows Sun Valley overview - href: sv-overview.md - - name: Windows Sun Valley requirements - href: sv-requirements.md - - name: Sun Valley FAQ - href: sv-faq.md - - - name: Deploy and Manage Windows Sun Valley - items: - - name: Plan to deploy Windows Sun Valley - href: /windows/deployment/sv-plan - - name: Prepare for Windows Sun Valley - href: /windows/deployment/sv-prepare.md - - name: Deploy Windows Sun Valley - href: /windows/deployment/sv-deploy.md - - name: Configure Windows Sun Valley - href: /windows/configuration/sv-configure.md - - name: Manage Windows Sun Valley - href: /windows/client-management/sv-manage.md - - name: Windows Sun Valley application readiness - href: /windows/application-management/sv-app-readiness.md - - - name: Support - items: - - name: Windows Sun Valley lifecycle - href: sv-lifecycle.md - - name: Windows Sun Valley release information - href: /windows/release-health - - - diff --git a/windows/windows-11/TOC.yml b/windows/windows-11/TOC.yml new file mode 100644 index 0000000000..ad14e66327 --- /dev/null +++ b/windows/windows-11/TOC.yml @@ -0,0 +1,36 @@ +- name: Windows 11 + href: index.yml + items: + - name: Get started + items: + - name: Windows 11 overview + href: windows-11-overview.md + - name: Windows 11 requirements + href: windows-11-requirements.md + - name: Windows 11 FAQ + href: windows-11-faq.md + + - name: Deploy and Manage Windows 11 + items: + - name: Plan to deploy Windows 11 + href: /windows/deployment/windows-11-plan + - name: Prepare for Windows 11 + href: /windows/deployment/windows-11-prepare.md + - name: Deploy Windows 11 + href: /windows/deployment/windows-11-deploy.md + - name: Configure Windows 11 + href: /windows/configuration/windows-11-configure.md + - name: Manage Windows 11 + href: /windows/client-management/windows-11-manage.md + - name: Windows 11 application readiness + href: /windows/application-management/windows-11-app-readiness.md + + - name: Support + items: + - name: Windows 11 lifecycle + href: windows-11-lifecycle.md + - name: Windows 11 release information + href: /windows/release-health + + + diff --git a/windows/sv/breadcrumb/toc.yml b/windows/windows-11/breadcrumb/toc.yml similarity index 100% rename from windows/sv/breadcrumb/toc.yml rename to windows/windows-11/breadcrumb/toc.yml diff --git a/windows/sv/docfx.json b/windows/windows-11/docfx.json similarity index 90% rename from windows/sv/docfx.json rename to windows/windows-11/docfx.json index 7035c4cd69..e7955464fe 100644 --- a/windows/sv/docfx.json +++ b/windows/windows-11/docfx.json @@ -39,13 +39,13 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "breadcrumb_path": "/windows/sv/breadcrumb/toc.json", + "breadcrumb_path": "/windows/windows-11/breadcrumb/toc.json", "extendBreadcrumb": true, "feedback_system": "None" }, "fileMetadata": {}, "template": [], - "dest": "SV", + "dest": "windows-11", "markdownEngineName": "markdig" } } \ No newline at end of file diff --git a/windows/sv/index.yml b/windows/windows-11/index.yml similarity index 75% rename from windows/sv/index.yml rename to windows/windows-11/index.yml index 477ed81e72..5e33fe3113 100644 --- a/windows/sv/index.yml +++ b/windows/windows-11/index.yml @@ -1,7 +1,7 @@ ### YamlMime:Landing title: Windows SV # < 60 chars -summary: Find out about Windows Sun Valley. # < 160 chars +summary: Find out about Windows Windows 11. # < 160 chars metadata: title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. @@ -26,29 +26,29 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows Sun Valley overview + - text: Windows Windows 11 overview url: sv-overview.md - - text: Windows Sun Valley requirements + - text: Windows Windows 11 requirements url: sv-requirements.md - - text: Windows Sun Valley FAQ + - text: Windows Windows 11 FAQ url: sv-faq.md # Card (optional) - - title: Deploy Windows Sun Valley + - title: Deploy Windows 11 linkLists: - linkListType: overview links: - - text: Plan to deploy Windows Sun Valley + - text: Plan to deploy Windows Windows 11 url: /windows/deployment/sv-plan.md - - text: Prepare for Windows Sun Valley + - text: Prepare for Windows Windows 11 url: /windows/deployment/sv-prepare.md - - text: Deploy Windows Sun Valley + - text: Deploy Windows Windows 11 url: /windows/deployment/sv-deploy.md - - text: Configure Windows Sun Valley + - text: Configure Windows Windows 11 url: /windows/configuration/sv-configure.md - - text: Manage Windows Sun Valley + - text: Manage Windows Windows 11 url: /windows/client-management/sv-manage.md - - text: Windows Sun Valley application readiness + - text: Windows Windows 11 application readiness url: /windows/application-management/sv-app-readiness.md # Card (optional) @@ -56,8 +56,8 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows Sun Valley lifecycle + - text: Windows Windows 11 lifecycle url: placeholder.md - - text: Windows Sun Valley release information + - text: Windows Windows 11 release information url: ../release-health diff --git a/windows/sv/placeholder.md b/windows/windows-11/placeholder.md similarity index 100% rename from windows/sv/placeholder.md rename to windows/windows-11/placeholder.md diff --git a/windows/sv/sv-requirements.md b/windows/windows-11/windows-11-faq.md similarity index 71% rename from windows/sv/sv-requirements.md rename to windows/windows-11/windows-11-faq.md index 5e4a647fea..1ac810bb60 100644 --- a/windows/sv/sv-requirements.md +++ b/windows/windows-11/windows-11-faq.md @@ -1,7 +1,6 @@ --- title: Placeholder description: PH -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C ms.reviewer: manager: laurawi ms.audience: itpro @@ -16,7 +15,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows Sun Valley requirements +# Windows 11 frequently asked questions (FAQ) -Windows Sun Valley requirements. +FAQ. diff --git a/windows/sv/sv-lifecycle.md b/windows/windows-11/windows-11-lifecycle.md similarity index 69% rename from windows/sv/sv-lifecycle.md rename to windows/windows-11/windows-11-lifecycle.md index c16baa14b7..fab8fda180 100644 --- a/windows/sv/sv-lifecycle.md +++ b/windows/windows-11/windows-11-lifecycle.md @@ -1,7 +1,6 @@ --- title: Lifecycle -description: PH -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +description: Lifecycle information for Windows 11 ms.reviewer: manager: laurawi ms.audience: itpro @@ -16,7 +15,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows Sun Valley lifecycle +# Windows 11 lifecycle -Sun Valley lifecycle. +Windows 11 lifecycle. diff --git a/windows/sv/sv-overview.md b/windows/windows-11/windows-11-overview.md similarity index 86% rename from windows/sv/sv-overview.md rename to windows/windows-11/windows-11-overview.md index 4099c30662..f39f5e4c23 100644 --- a/windows/sv/sv-overview.md +++ b/windows/windows-11/windows-11-overview.md @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows Sun Valley overview +# Windows 11 overview -Overview of Sun Valley. +Overview of Windows 11. diff --git a/windows/sv/sv-faq.md b/windows/windows-11/windows-11-requirements.md similarity index 85% rename from windows/sv/sv-faq.md rename to windows/windows-11/windows-11-requirements.md index 220beac886..482850a4f9 100644 --- a/windows/sv/sv-faq.md +++ b/windows/windows-11/windows-11-requirements.md @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows Sun Valley frequently asked questions (FAQ) +# Windows 11 requirements -FAQ. +Windows 11 requirements. From 5b1f9848a3b8a6de82a5cb336460c10a34d7ad14 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 1 Jun 2021 09:46:31 -0700 Subject: [PATCH 015/104] H1 fixes --- windows/deployment/{sv-deploy.md => windows-11-deploy.md} | 0 windows/deployment/{sv-plan.md => windows-11-plan.md} | 4 ++-- .../deployment/{sv-prepare.md => windows-11-prepare.md} | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) rename windows/deployment/{sv-deploy.md => windows-11-deploy.md} (100%) rename windows/deployment/{sv-plan.md => windows-11-plan.md} (99%) rename windows/deployment/{sv-prepare.md => windows-11-prepare.md} (99%) diff --git a/windows/deployment/sv-deploy.md b/windows/deployment/windows-11-deploy.md similarity index 100% rename from windows/deployment/sv-deploy.md rename to windows/deployment/windows-11-deploy.md diff --git a/windows/deployment/sv-plan.md b/windows/deployment/windows-11-plan.md similarity index 99% rename from windows/deployment/sv-plan.md rename to windows/deployment/windows-11-plan.md index cd88a54b3d..e3b81e8c3c 100644 --- a/windows/deployment/sv-plan.md +++ b/windows/deployment/windows-11-plan.md @@ -1,6 +1,6 @@ --- title: Windows 11 deployment planning -description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. +description: Understand the different ways Windows 11 operating system can be deployed in your organization. Explore several Windows 11 deployment scenarios. ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 ms.reviewer: manager: laurawi @@ -19,7 +19,7 @@ ms.topic: article # Windows 11 deployment planning **Applies to** -- Windows 10 +- Windows 11 To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. diff --git a/windows/deployment/sv-prepare.md b/windows/deployment/windows-11-prepare.md similarity index 99% rename from windows/deployment/sv-prepare.md rename to windows/deployment/windows-11-prepare.md index cd88a54b3d..eb8ce64aa0 100644 --- a/windows/deployment/sv-prepare.md +++ b/windows/deployment/windows-11-prepare.md @@ -1,6 +1,6 @@ --- -title: Windows 11 deployment planning -description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. +title: Prepare to deploy Windows 11 +description: Understand the different ways Windows 11 operating system can be deployed in your organization. Explore several Windows 11 deployment scenarios. ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 ms.reviewer: manager: laurawi @@ -16,10 +16,10 @@ audience: itpro ms.topic: article --- -# Windows 11 deployment planning +# Prepare to deploy Windows 11 **Applies to** -- Windows 10 +- Windows 11, version 21H1 To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. From 5af48f6be2deb00ea8733163229159bde7d2e972 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 1 Jun 2021 12:17:01 -0700 Subject: [PATCH 016/104] sv --- .openpublishing.publish.config.json | 6 +- windows/deployment/TOC.yml | 8 +-- windows/{windows-11 => sv}/TOC.yml | 0 windows/{windows-11 => sv}/breadcrumb/toc.yml | 0 windows/{windows-11 => sv}/docfx.json | 0 windows/{windows-11 => sv}/index.yml | 0 windows/{windows-11 => sv}/placeholder.md | 0 windows/{windows-11 => sv}/windows-11-faq.md | 0 .../windows-11-lifecycle.md | 0 .../{windows-11 => sv}/windows-11-overview.md | 0 .../windows-11-requirements.md | 0 windows/whats-new/sv/TOC.yml | 36 +++++++++++ windows/whats-new/sv/breadcrumb/toc.yml | 53 ++++++++++++++++ windows/whats-new/sv/docfx.json | 51 +++++++++++++++ windows/whats-new/sv/index.yml | 63 +++++++++++++++++++ windows/whats-new/sv/placeholder.md | 22 +++++++ windows/whats-new/sv/windows-11-faq.md | 21 +++++++ windows/whats-new/sv/windows-11-lifecycle.md | 21 +++++++ windows/whats-new/sv/windows-11-overview.md | 22 +++++++ .../whats-new/sv/windows-11-requirements.md | 22 +++++++ 20 files changed, 318 insertions(+), 7 deletions(-) rename windows/{windows-11 => sv}/TOC.yml (100%) rename windows/{windows-11 => sv}/breadcrumb/toc.yml (100%) rename windows/{windows-11 => sv}/docfx.json (100%) rename windows/{windows-11 => sv}/index.yml (100%) rename windows/{windows-11 => sv}/placeholder.md (100%) rename windows/{windows-11 => sv}/windows-11-faq.md (100%) rename windows/{windows-11 => sv}/windows-11-lifecycle.md (100%) rename windows/{windows-11 => sv}/windows-11-overview.md (100%) rename windows/{windows-11 => sv}/windows-11-requirements.md (100%) create mode 100644 windows/whats-new/sv/TOC.yml create mode 100644 windows/whats-new/sv/breadcrumb/toc.yml create mode 100644 windows/whats-new/sv/docfx.json create mode 100644 windows/whats-new/sv/index.yml create mode 100644 windows/whats-new/sv/placeholder.md create mode 100644 windows/whats-new/sv/windows-11-faq.md create mode 100644 windows/whats-new/sv/windows-11-lifecycle.md create mode 100644 windows/whats-new/sv/windows-11-overview.md create mode 100644 windows/whats-new/sv/windows-11-requirements.md diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json index 4fc470da75..32eb1b181b 100644 --- a/.openpublishing.publish.config.json +++ b/.openpublishing.publish.config.json @@ -130,9 +130,9 @@ "template_folder": "_themes" }, { - "docset_name": "windows-11", - "build_source_folder": "windows/windows-11", - "build_output_subfolder": "windows-11", + "docset_name": "sv", + "build_source_folder": "windows/sv", + "build_output_subfolder": "sv", "locale": "en-us", "monikers": [], "moniker_ranges": [], diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 3a19c56f54..559a6b7d13 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -6,7 +6,7 @@ - name: What's new href: deploy-whats-new.md - name: Windows 11 deployment overview - href: sv-deploy.md + href: windows-11-deploy.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? @@ -36,7 +36,7 @@ - name: Plan items: - name: Windows 11 deployment planning - href: sv-plan.md + href: windows-11-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria @@ -72,7 +72,7 @@ - name: Prepare items: - name: Prepare to deploy Windows 11 - href: sv-prepare.md + href: windows-11-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md - name: Evaluate and update infrastructure @@ -105,7 +105,7 @@ - name: Deploy Windows client items: - name: Windows 11 deployment overview - href: sv-deploy.md + href: windows-11-deploy.md - name: Deploy Windows client with Autopilot href: windows-autopilot/index.yml - name: Deploy Windows client with Configuration Manager diff --git a/windows/windows-11/TOC.yml b/windows/sv/TOC.yml similarity index 100% rename from windows/windows-11/TOC.yml rename to windows/sv/TOC.yml diff --git a/windows/windows-11/breadcrumb/toc.yml b/windows/sv/breadcrumb/toc.yml similarity index 100% rename from windows/windows-11/breadcrumb/toc.yml rename to windows/sv/breadcrumb/toc.yml diff --git a/windows/windows-11/docfx.json b/windows/sv/docfx.json similarity index 100% rename from windows/windows-11/docfx.json rename to windows/sv/docfx.json diff --git a/windows/windows-11/index.yml b/windows/sv/index.yml similarity index 100% rename from windows/windows-11/index.yml rename to windows/sv/index.yml diff --git a/windows/windows-11/placeholder.md b/windows/sv/placeholder.md similarity index 100% rename from windows/windows-11/placeholder.md rename to windows/sv/placeholder.md diff --git a/windows/windows-11/windows-11-faq.md b/windows/sv/windows-11-faq.md similarity index 100% rename from windows/windows-11/windows-11-faq.md rename to windows/sv/windows-11-faq.md diff --git a/windows/windows-11/windows-11-lifecycle.md b/windows/sv/windows-11-lifecycle.md similarity index 100% rename from windows/windows-11/windows-11-lifecycle.md rename to windows/sv/windows-11-lifecycle.md diff --git a/windows/windows-11/windows-11-overview.md b/windows/sv/windows-11-overview.md similarity index 100% rename from windows/windows-11/windows-11-overview.md rename to windows/sv/windows-11-overview.md diff --git a/windows/windows-11/windows-11-requirements.md b/windows/sv/windows-11-requirements.md similarity index 100% rename from windows/windows-11/windows-11-requirements.md rename to windows/sv/windows-11-requirements.md diff --git a/windows/whats-new/sv/TOC.yml b/windows/whats-new/sv/TOC.yml new file mode 100644 index 0000000000..ad14e66327 --- /dev/null +++ b/windows/whats-new/sv/TOC.yml @@ -0,0 +1,36 @@ +- name: Windows 11 + href: index.yml + items: + - name: Get started + items: + - name: Windows 11 overview + href: windows-11-overview.md + - name: Windows 11 requirements + href: windows-11-requirements.md + - name: Windows 11 FAQ + href: windows-11-faq.md + + - name: Deploy and Manage Windows 11 + items: + - name: Plan to deploy Windows 11 + href: /windows/deployment/windows-11-plan + - name: Prepare for Windows 11 + href: /windows/deployment/windows-11-prepare.md + - name: Deploy Windows 11 + href: /windows/deployment/windows-11-deploy.md + - name: Configure Windows 11 + href: /windows/configuration/windows-11-configure.md + - name: Manage Windows 11 + href: /windows/client-management/windows-11-manage.md + - name: Windows 11 application readiness + href: /windows/application-management/windows-11-app-readiness.md + + - name: Support + items: + - name: Windows 11 lifecycle + href: windows-11-lifecycle.md + - name: Windows 11 release information + href: /windows/release-health + + + diff --git a/windows/whats-new/sv/breadcrumb/toc.yml b/windows/whats-new/sv/breadcrumb/toc.yml new file mode 100644 index 0000000000..e2971f2d84 --- /dev/null +++ b/windows/whats-new/sv/breadcrumb/toc.yml @@ -0,0 +1,53 @@ +- name: Docs + tocHref: / + topicHref: / + items: + - name: Windows + tocHref: /windows + topicHref: /windows/windows-10 + items: + - name: What's new + tocHref: /windows/whats-new/ + topicHref: /windows/whats-new/index + - name: Configuration + tocHref: /windows/configuration/ + topicHref: /windows/configuration/index + - name: Deployment + tocHref: /windows/deployment/ + topicHref: /windows/deployment/index + - name: Application management + tocHref: /windows/application-management/ + topicHref: /windows/application-management/index + - name: Client management + tocHref: /windows/client-management/ + topicHref: /windows/client-management/index + items: + - name: Mobile Device Management + tocHref: /windows/client-management/mdm/ + topicHref: /windows/client-management/mdm/index + - name: Release information + tocHref: /windows/release-information/ + topicHref: /windows/release-health/release-information + - name: Privacy + tocHref: /windows/privacy/ + topicHref: /windows/privacy/index + - name: Security + tocHref: /windows/security/ + topicHref: /windows/security/index + items: + - name: Identity and access protection + tocHref: /windows/security/identity-protection/ + topicHref: /windows/security/identity-protection/index + items: + - name: Windows Hello for Business + tocHref: /windows/security/identity-protection/hello-for-business + topicHref: /windows/security/identity-protection/hello-for-business/hello-identity-verification + - name: Threat protection + tocHref: /windows/security/threat-protection/ + topicHref: /windows/security/threat-protection/index + - name: Information protection + tocHref: /windows/security/information-protection/ + topicHref: /windows/security/information-protection/index + - name: Hardware-based protection + tocHref: /windows/security/hardware-protection/ + topicHref: /windows/security/hardware-protection/index diff --git a/windows/whats-new/sv/docfx.json b/windows/whats-new/sv/docfx.json new file mode 100644 index 0000000000..e7955464fe --- /dev/null +++ b/windows/whats-new/sv/docfx.json @@ -0,0 +1,51 @@ +{ + "build": { + "content": [ + { + "files": [ + "**/*.md", + "**/*.yml" + ], + "exclude": [ + "**/obj/**", + "**/includes/**", + "_themes/**", + "_themes.pdf/**", + "**/docfx.json", + "_repo.en-us/**", + "README.md", + "LICENSE", + "LICENSE-CODE", + "ThirdPartyNotices.md" + ] + } + ], + "resource": [ + { + "files": [ + "**/*.png", + "**/*.jpg" + ], + "exclude": [ + "**/obj/**", + "**/includes/**", + "_themes/**", + "_themes.pdf/**", + "**/docfx.json", + "_repo.en-us/**" + ] + } + ], + "overwrite": [], + "externalReference": [], + "globalMetadata": { + "breadcrumb_path": "/windows/windows-11/breadcrumb/toc.json", + "extendBreadcrumb": true, + "feedback_system": "None" + }, + "fileMetadata": {}, + "template": [], + "dest": "windows-11", + "markdownEngineName": "markdig" + } +} \ No newline at end of file diff --git a/windows/whats-new/sv/index.yml b/windows/whats-new/sv/index.yml new file mode 100644 index 0000000000..5e33fe3113 --- /dev/null +++ b/windows/whats-new/sv/index.yml @@ -0,0 +1,63 @@ +### YamlMime:Landing + +title: Windows SV # < 60 chars +summary: Find out about Windows Windows 11. # < 160 chars + +metadata: + title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. + description: Learn about the administrative tools, tasks and best practices for managing Windows SV across your enterprise. # Required; article description that is displayed in search results. < 160 chars. + services: windows-10 + ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. + ms.subservice: subservice + ms.topic: landing-page # Required + ms.collection: windows-10 + author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. + ms.author: greglin #Required; microsoft alias of author; optional team alias. + ms.date: 05/07/2021 #Required; mm/dd/yyyy format. + localization_priority: medium + +# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new + +landingContent: +# Cards and links should be based on top customer tasks or top subjects +# Start card title with a verb + # Card (optional) + - title: Get started + linkLists: + - linkListType: overview + links: + - text: Windows Windows 11 overview + url: sv-overview.md + - text: Windows Windows 11 requirements + url: sv-requirements.md + - text: Windows Windows 11 FAQ + url: sv-faq.md + + # Card (optional) + - title: Deploy Windows 11 + linkLists: + - linkListType: overview + links: + - text: Plan to deploy Windows Windows 11 + url: /windows/deployment/sv-plan.md + - text: Prepare for Windows Windows 11 + url: /windows/deployment/sv-prepare.md + - text: Deploy Windows Windows 11 + url: /windows/deployment/sv-deploy.md + - text: Configure Windows Windows 11 + url: /windows/configuration/sv-configure.md + - text: Manage Windows Windows 11 + url: /windows/client-management/sv-manage.md + - text: Windows Windows 11 application readiness + url: /windows/application-management/sv-app-readiness.md + + # Card (optional) + - title: Support information + linkLists: + - linkListType: overview + links: + - text: Windows Windows 11 lifecycle + url: placeholder.md + - text: Windows Windows 11 release information + url: ../release-health + diff --git a/windows/whats-new/sv/placeholder.md b/windows/whats-new/sv/placeholder.md new file mode 100644 index 0000000000..fecfe94a8e --- /dev/null +++ b/windows/whats-new/sv/placeholder.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Placeholder + +Placeholder text. + diff --git a/windows/whats-new/sv/windows-11-faq.md b/windows/whats-new/sv/windows-11-faq.md new file mode 100644 index 0000000000..1ac810bb60 --- /dev/null +++ b/windows/whats-new/sv/windows-11-faq.md @@ -0,0 +1,21 @@ +--- +title: Placeholder +description: PH +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Windows 11 frequently asked questions (FAQ) + +FAQ. + diff --git a/windows/whats-new/sv/windows-11-lifecycle.md b/windows/whats-new/sv/windows-11-lifecycle.md new file mode 100644 index 0000000000..fab8fda180 --- /dev/null +++ b/windows/whats-new/sv/windows-11-lifecycle.md @@ -0,0 +1,21 @@ +--- +title: Lifecycle +description: Lifecycle information for Windows 11 +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Windows 11 lifecycle + +Windows 11 lifecycle. + diff --git a/windows/whats-new/sv/windows-11-overview.md b/windows/whats-new/sv/windows-11-overview.md new file mode 100644 index 0000000000..f39f5e4c23 --- /dev/null +++ b/windows/whats-new/sv/windows-11-overview.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Windows 11 overview + +Overview of Windows 11. + diff --git a/windows/whats-new/sv/windows-11-requirements.md b/windows/whats-new/sv/windows-11-requirements.md new file mode 100644 index 0000000000..482850a4f9 --- /dev/null +++ b/windows/whats-new/sv/windows-11-requirements.md @@ -0,0 +1,22 @@ +--- +title: Placeholder +description: PH +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Windows 11 requirements + +Windows 11 requirements. + From 0dd7f54dfb636f8e3ed3a5308ae96ba93323928b Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 14:00:59 -0700 Subject: [PATCH 017/104] content in whats new --- windows/whats-new/TOC.yml | 36 +++++++---- windows/whats-new/sv/TOC.yml | 36 ----------- windows/whats-new/sv/breadcrumb/toc.yml | 53 ---------------- windows/whats-new/sv/docfx.json | 51 --------------- windows/whats-new/sv/index.yml | 63 ------------------- windows/whats-new/sv/placeholder.md | 22 ------- windows/whats-new/sv/windows-11-faq.md | 21 ------- windows/whats-new/sv/windows-11-lifecycle.md | 21 ------- windows/whats-new/windows-sv-get-started.md | 51 +++++++++++++++ ...-11-overview.md => windows-sv-overview.md} | 0 ...irements.md => windows-sv-requirements.md} | 0 11 files changed, 74 insertions(+), 280 deletions(-) delete mode 100644 windows/whats-new/sv/TOC.yml delete mode 100644 windows/whats-new/sv/breadcrumb/toc.yml delete mode 100644 windows/whats-new/sv/docfx.json delete mode 100644 windows/whats-new/sv/index.yml delete mode 100644 windows/whats-new/sv/placeholder.md delete mode 100644 windows/whats-new/sv/windows-11-faq.md delete mode 100644 windows/whats-new/sv/windows-11-lifecycle.md create mode 100644 windows/whats-new/windows-sv-get-started.md rename windows/whats-new/{sv/windows-11-overview.md => windows-sv-overview.md} (100%) rename windows/whats-new/{sv/windows-11-requirements.md => windows-sv-requirements.md} (100%) diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index b0d672f68c..2afb052a34 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -1,19 +1,29 @@ -- name: What's new in Windows 10 +- name: What's new in Windows client href: index.yml -- name: What's new in Windows 10, version 21H1 - href: whats-new-windows-10-version-21H1.md -- name: What's new in Windows 10, version 20H2 - href: whats-new-windows-10-version-20H2.md -- name: What's new in Windows 10, version 2004 - href: whats-new-windows-10-version-2004.md -- name: What's new in Windows 10, version 1909 - href: whats-new-windows-10-version-1909.md -- name: What's new in Windows 10, version 1903 - href: whats-new-windows-10-version-1903.md -- name: What's new in Windows 10, version 1809 - href: whats-new-windows-10-version-1809.md +- name: Windows Sun Valley + items: + - name: Windows Sun Valley overview + href: sv-overview.md + - name: Windows Sun Valley requirements + href: sv-requirements.md + - name: Get started with Windows Sun Valley + href: sv-get-started.md +- name: Windows 10 + items: + - name: What's new in Windows 10, version 21H1 + href: whats-new-windows-10-version-21H1.md + - name: What's new in Windows 10, version 20H2 + href: whats-new-windows-10-version-20H2.md + - name: What's new in Windows 10, version 2004 + href: whats-new-windows-10-version-2004.md + - name: What's new in Windows 10, version 1909 + href: whats-new-windows-10-version-1909.md + - name: What's new in Windows 10, version 1903 + href: whats-new-windows-10-version-1903.md - name: Previous versions items: + - name: What's new in Windows 10, version 1809 + href: whats-new-windows-10-version-1809.md - name: What's new in Windows 10, version 1803 href: whats-new-windows-10-version-1803.md - name: What's new in Windows 10, version 1709 diff --git a/windows/whats-new/sv/TOC.yml b/windows/whats-new/sv/TOC.yml deleted file mode 100644 index ad14e66327..0000000000 --- a/windows/whats-new/sv/TOC.yml +++ /dev/null @@ -1,36 +0,0 @@ -- name: Windows 11 - href: index.yml - items: - - name: Get started - items: - - name: Windows 11 overview - href: windows-11-overview.md - - name: Windows 11 requirements - href: windows-11-requirements.md - - name: Windows 11 FAQ - href: windows-11-faq.md - - - name: Deploy and Manage Windows 11 - items: - - name: Plan to deploy Windows 11 - href: /windows/deployment/windows-11-plan - - name: Prepare for Windows 11 - href: /windows/deployment/windows-11-prepare.md - - name: Deploy Windows 11 - href: /windows/deployment/windows-11-deploy.md - - name: Configure Windows 11 - href: /windows/configuration/windows-11-configure.md - - name: Manage Windows 11 - href: /windows/client-management/windows-11-manage.md - - name: Windows 11 application readiness - href: /windows/application-management/windows-11-app-readiness.md - - - name: Support - items: - - name: Windows 11 lifecycle - href: windows-11-lifecycle.md - - name: Windows 11 release information - href: /windows/release-health - - - diff --git a/windows/whats-new/sv/breadcrumb/toc.yml b/windows/whats-new/sv/breadcrumb/toc.yml deleted file mode 100644 index e2971f2d84..0000000000 --- a/windows/whats-new/sv/breadcrumb/toc.yml +++ /dev/null @@ -1,53 +0,0 @@ -- name: Docs - tocHref: / - topicHref: / - items: - - name: Windows - tocHref: /windows - topicHref: /windows/windows-10 - items: - - name: What's new - tocHref: /windows/whats-new/ - topicHref: /windows/whats-new/index - - name: Configuration - tocHref: /windows/configuration/ - topicHref: /windows/configuration/index - - name: Deployment - tocHref: /windows/deployment/ - topicHref: /windows/deployment/index - - name: Application management - tocHref: /windows/application-management/ - topicHref: /windows/application-management/index - - name: Client management - tocHref: /windows/client-management/ - topicHref: /windows/client-management/index - items: - - name: Mobile Device Management - tocHref: /windows/client-management/mdm/ - topicHref: /windows/client-management/mdm/index - - name: Release information - tocHref: /windows/release-information/ - topicHref: /windows/release-health/release-information - - name: Privacy - tocHref: /windows/privacy/ - topicHref: /windows/privacy/index - - name: Security - tocHref: /windows/security/ - topicHref: /windows/security/index - items: - - name: Identity and access protection - tocHref: /windows/security/identity-protection/ - topicHref: /windows/security/identity-protection/index - items: - - name: Windows Hello for Business - tocHref: /windows/security/identity-protection/hello-for-business - topicHref: /windows/security/identity-protection/hello-for-business/hello-identity-verification - - name: Threat protection - tocHref: /windows/security/threat-protection/ - topicHref: /windows/security/threat-protection/index - - name: Information protection - tocHref: /windows/security/information-protection/ - topicHref: /windows/security/information-protection/index - - name: Hardware-based protection - tocHref: /windows/security/hardware-protection/ - topicHref: /windows/security/hardware-protection/index diff --git a/windows/whats-new/sv/docfx.json b/windows/whats-new/sv/docfx.json deleted file mode 100644 index e7955464fe..0000000000 --- a/windows/whats-new/sv/docfx.json +++ /dev/null @@ -1,51 +0,0 @@ -{ - "build": { - "content": [ - { - "files": [ - "**/*.md", - "**/*.yml" - ], - "exclude": [ - "**/obj/**", - "**/includes/**", - "_themes/**", - "_themes.pdf/**", - "**/docfx.json", - "_repo.en-us/**", - "README.md", - "LICENSE", - "LICENSE-CODE", - "ThirdPartyNotices.md" - ] - } - ], - "resource": [ - { - "files": [ - "**/*.png", - "**/*.jpg" - ], - "exclude": [ - "**/obj/**", - "**/includes/**", - "_themes/**", - "_themes.pdf/**", - "**/docfx.json", - "_repo.en-us/**" - ] - } - ], - "overwrite": [], - "externalReference": [], - "globalMetadata": { - "breadcrumb_path": "/windows/windows-11/breadcrumb/toc.json", - "extendBreadcrumb": true, - "feedback_system": "None" - }, - "fileMetadata": {}, - "template": [], - "dest": "windows-11", - "markdownEngineName": "markdig" - } -} \ No newline at end of file diff --git a/windows/whats-new/sv/index.yml b/windows/whats-new/sv/index.yml deleted file mode 100644 index 5e33fe3113..0000000000 --- a/windows/whats-new/sv/index.yml +++ /dev/null @@ -1,63 +0,0 @@ -### YamlMime:Landing - -title: Windows SV # < 60 chars -summary: Find out about Windows Windows 11. # < 160 chars - -metadata: - title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Learn about the administrative tools, tasks and best practices for managing Windows SV across your enterprise. # Required; article description that is displayed in search results. < 160 chars. - services: windows-10 - ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. - ms.subservice: subservice - ms.topic: landing-page # Required - ms.collection: windows-10 - author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. - ms.author: greglin #Required; microsoft alias of author; optional team alias. - ms.date: 05/07/2021 #Required; mm/dd/yyyy format. - localization_priority: medium - -# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new - -landingContent: -# Cards and links should be based on top customer tasks or top subjects -# Start card title with a verb - # Card (optional) - - title: Get started - linkLists: - - linkListType: overview - links: - - text: Windows Windows 11 overview - url: sv-overview.md - - text: Windows Windows 11 requirements - url: sv-requirements.md - - text: Windows Windows 11 FAQ - url: sv-faq.md - - # Card (optional) - - title: Deploy Windows 11 - linkLists: - - linkListType: overview - links: - - text: Plan to deploy Windows Windows 11 - url: /windows/deployment/sv-plan.md - - text: Prepare for Windows Windows 11 - url: /windows/deployment/sv-prepare.md - - text: Deploy Windows Windows 11 - url: /windows/deployment/sv-deploy.md - - text: Configure Windows Windows 11 - url: /windows/configuration/sv-configure.md - - text: Manage Windows Windows 11 - url: /windows/client-management/sv-manage.md - - text: Windows Windows 11 application readiness - url: /windows/application-management/sv-app-readiness.md - - # Card (optional) - - title: Support information - linkLists: - - linkListType: overview - links: - - text: Windows Windows 11 lifecycle - url: placeholder.md - - text: Windows Windows 11 release information - url: ../release-health - diff --git a/windows/whats-new/sv/placeholder.md b/windows/whats-new/sv/placeholder.md deleted file mode 100644 index fecfe94a8e..0000000000 --- a/windows/whats-new/sv/placeholder.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Placeholder -description: PH -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Placeholder - -Placeholder text. - diff --git a/windows/whats-new/sv/windows-11-faq.md b/windows/whats-new/sv/windows-11-faq.md deleted file mode 100644 index 1ac810bb60..0000000000 --- a/windows/whats-new/sv/windows-11-faq.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Placeholder -description: PH -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows 11 frequently asked questions (FAQ) - -FAQ. - diff --git a/windows/whats-new/sv/windows-11-lifecycle.md b/windows/whats-new/sv/windows-11-lifecycle.md deleted file mode 100644 index fab8fda180..0000000000 --- a/windows/whats-new/sv/windows-11-lifecycle.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Lifecycle -description: Lifecycle information for Windows 11 -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows 11 lifecycle - -Windows 11 lifecycle. - diff --git a/windows/whats-new/windows-sv-get-started.md b/windows/whats-new/windows-sv-get-started.md new file mode 100644 index 0000000000..c2522f3e4c --- /dev/null +++ b/windows/whats-new/windows-sv-get-started.md @@ -0,0 +1,51 @@ +--- +title: Get started with Windows 10, version 1709 +description: Learn about features, review requirements, and plan your deployment of Windows 10, version 1709, including IT Pro content, release information, and history. +keywords: ["get started", "windows 10", "fall creators update", "1709"] +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +author: dansimp +ms.author: dansimp +ms.date: 10/16/2017 +ms.reviewer: +manager: dansimp +ms.localizationpriority: high +ms.topic: article +--- + +# Get started with Windows 10, version 1709 + +**Applies to** + +- Windows 10 + +> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) + +Welcome to Windows 10, version 1709, also known as the Fall Creators Update. Use the following information to learn about new features, review system requirements, and plan your deployment of the latest version of Windows 10. + +## Specification and systems requirements + +Before you install any version of Windows 10, make sure you visit the [Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/windows/windows-10-specifications) page. This page contains the minimum systems requirements and important notes to install Windows 10, as well as feature deprecation information and additional requirements to use certain features. + +## What's new in Windows 10, version 1709 IT Pro content + +Take a look at the [What's new in Windows 10, version 1709 IT Pro content](whats-new-windows-10-version-1709.md), for the latest updates in content. Use this topic to easily navigate the documentation for the new features in Windows 10, version 1709. + +## Windows 10 release information and update history + +To view availability dates and servicing options for each version and update of Windows, including version 1709, visit the [Windows 10 release information](https://technet.microsoft.com/windows/mt679505.aspx) page. For further details on each update, go to the [Windows 10 update history](https://support.microsoft.com/help/4018124/windows-10-update-history) page. + +## Windows 10 Roadmap + +If you'd like to gain some insight into preview, or in-development features, visit the [Windows 10 Roadmap](https://www.microsoft.com/WindowsForBusiness/windows-roadmap) page. You'll be able to filter by feature state and product category, to make this information easier to navigate. + +## Top support solutions for Windows 10 + +Having problems with your latest deployment of Windows 10, version 1709? Check out the [Top support solutions for Windows 10](/windows/client-management/windows-10-support-solutions) topic, where we've collected the top Microsoft Support solutions for the most common issues experienced when using Windows 10 in an enterprise or IT pro environment. + +> Want even more information? Visit the [Windows 10 lifecycle page](https://www.microsoft.com/itpro/windows-10) on the [Windows IT Pro Center](https://itpro.windows.com). + +Ready to get started with Windows 10, version 1709? +> [!div class="nextstepaction"] +> [Deploy and Update Windows 10](/windows/deployment) diff --git a/windows/whats-new/sv/windows-11-overview.md b/windows/whats-new/windows-sv-overview.md similarity index 100% rename from windows/whats-new/sv/windows-11-overview.md rename to windows/whats-new/windows-sv-overview.md diff --git a/windows/whats-new/sv/windows-11-requirements.md b/windows/whats-new/windows-sv-requirements.md similarity index 100% rename from windows/whats-new/sv/windows-11-requirements.md rename to windows/whats-new/windows-sv-requirements.md From dc04f0325f595f9f7d1ac7e9de31adc8f9208a2e Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 14:09:02 -0700 Subject: [PATCH 018/104] link fix --- windows/whats-new/TOC.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index 2afb052a34..4ee09a9849 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -3,11 +3,11 @@ - name: Windows Sun Valley items: - name: Windows Sun Valley overview - href: sv-overview.md + href: windows-sv-overview.md - name: Windows Sun Valley requirements - href: sv-requirements.md + href: windows-sv-requirements.md - name: Get started with Windows Sun Valley - href: sv-get-started.md + href: windows-sv-get-started.md - name: Windows 10 items: - name: What's new in Windows 10, version 21H1 From a09acb3d6a645a0c3e07564b0672a07c1956bbc8 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 16:09:25 -0700 Subject: [PATCH 019/104] edits --- windows/hub/TOC.yml | 6 +++--- windows/hub/index.yml | 18 +++++++++--------- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 812bcc04b5..71671b2312 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -1,12 +1,12 @@ -- name: Windows client +- name: Windows href: index.yml items: + - name: Windows Sun Valley + href: /windows/whats-new/windows-sv-overview.md - name: What's new href: /windows/whats-new - name: Release information href: /windows/release-health - - name: Windows 11 - href: /windows/windows-11 - name: Deployment href: /windows/deployment - name: Configuration diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 572df40317..97ba2fdf8a 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -26,13 +26,13 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows 11 overview - url: /windows-11/windows-11-overview.md - - text: What's new in Windows 11, version 21H2 + - text: Windows SV overview + url: /windows-11/windows-sv-overview.md + - text: What's new in Windows SV, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - - text: Windows 11 release information + - text: Windows Sun Valley release information url: /windows/release-health/release-information - text: Windows 10 release information url: /windows/release-health/release-information @@ -44,7 +44,7 @@ landingContent: links: - text: Configure Windows client url: /windows/configuration/index - - text: Configure Windows 11 + - text: Configure Windows Sun Valley url: /windows/configuration/windows-11-configure.md - text: Accessibility information for IT Pros url: /windows/configuration/windows-10-accessibility-for-itpros @@ -60,8 +60,8 @@ landingContent: links: - text: Deploy and update Windows client url: /windows/deployment/index - - text: Deploy Windows 11 - url: /windows/deployment/windows-11-deploy.md + - text: Deploy Windows Sun Valley + url: /windows/deployment/windows-sv-deploy.md - text: Windows deployment scenarios url: /windows/deployment/windows-10-deployment-scenarios - text: Create a deployment plan @@ -77,7 +77,7 @@ landingContent: links: - text: Windows application management url: /windows/application-management/index - - text: Manage Windows 11 applications + - text: Manage Windows SV applications url: /windows/application-management/windows-11-app-manage.md - text: Understand the different apps included in Windows 10 url: /windows/application-management/apps-in-windows-10 @@ -93,7 +93,7 @@ landingContent: links: - text: Windows client management url: /windows/client-management/index - - text: Manage Windows 11 + - text: Manage Windows Sun Valley url: /windows/client-management/windows-11-manage.md - text: Administrative tools url: /windows/client-management/administrative-tools-in-windows-10 From 9a3aeb4b74bd72ae4c16f2cc712dac4f73e563a2 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 16:26:53 -0700 Subject: [PATCH 020/104] edits --- .../windows-sv-app-manage.md | 17 ++++++++++++++++ .../client-management/windows-sv-manage.md | 19 ++++++++++++++++++ windows/configuration/windows-sv-configure.md | 17 ++++++++++++++++ ...dows-11-deploy.md => windows-sv-deploy.md} | 0 ...{windows-11-plan.md => windows-sv-plan.md} | 0 ...ws-11-prepare.md => windows-sv-prepare.md} | 0 windows/hub/index.yml | 20 +++++++++---------- 7 files changed, 63 insertions(+), 10 deletions(-) create mode 100644 windows/application-management/windows-sv-app-manage.md create mode 100644 windows/client-management/windows-sv-manage.md create mode 100644 windows/configuration/windows-sv-configure.md rename windows/deployment/{windows-11-deploy.md => windows-sv-deploy.md} (100%) rename windows/deployment/{windows-11-plan.md => windows-sv-plan.md} (100%) rename windows/deployment/{windows-11-prepare.md => windows-sv-prepare.md} (100%) diff --git a/windows/application-management/windows-sv-app-manage.md b/windows/application-management/windows-sv-app-manage.md new file mode 100644 index 0000000000..86ee8a28c0 --- /dev/null +++ b/windows/application-management/windows-sv-app-manage.md @@ -0,0 +1,17 @@ +--- +title: Manage applications in Windows Sun Valley +ms.reviewer: +manager: dansimp +description: Use this article to understand the different types of apps that run on Windows Sun Valley, such as UWP and Win32 apps. +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.pagetype: mobile +ms.author: greglin +author: greg-lindsay +ms.localizationpriority: medium +ms.topic: article +--- +# Manage applications in Windows Sun Valley + +>Applies to: Windows Sun Valley diff --git a/windows/client-management/windows-sv-manage.md b/windows/client-management/windows-sv-manage.md new file mode 100644 index 0000000000..22704843bd --- /dev/null +++ b/windows/client-management/windows-sv-manage.md @@ -0,0 +1,19 @@ +--- +title: Manage Windows Sun Valley in your organization +description: This topic offers strategies for deploying and managing Windows Sun Valley, including deploying Windows Sun Valley in a mixed environment. +keywords: ["MDM", "device management", "group policy", "Azure Active Directory"] +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +ms.pagetype: devices +author: dansimp +ms.localizationpriority: medium +ms.date: 04/26/2018 +ms.reviewer: +manager: dansimp +ms.author: dansimp +ms.topic: article +--- + +# Manage Windows Sun Valley in your organization + diff --git a/windows/configuration/windows-sv-configure.md b/windows/configuration/windows-sv-configure.md new file mode 100644 index 0000000000..2a7ccf17d1 --- /dev/null +++ b/windows/configuration/windows-sv-configure.md @@ -0,0 +1,17 @@ +--- +title: Configure Windows Sun Valley +description: Administrators can pin additional apps to the taskbar and remove default pinned apps from the taskbar by adding a section to a layout modification XML file. +keywords: ["taskbar layout","pin apps"] +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +author: greg-lindsay +ms.author: greglin +ms.topic: article +ms.localizationpriority: medium +ms.date: 01/18/2018 +ms.reviewer: +manager: dansimp +--- +# Configure Windows Sun Valley + diff --git a/windows/deployment/windows-11-deploy.md b/windows/deployment/windows-sv-deploy.md similarity index 100% rename from windows/deployment/windows-11-deploy.md rename to windows/deployment/windows-sv-deploy.md diff --git a/windows/deployment/windows-11-plan.md b/windows/deployment/windows-sv-plan.md similarity index 100% rename from windows/deployment/windows-11-plan.md rename to windows/deployment/windows-sv-plan.md diff --git a/windows/deployment/windows-11-prepare.md b/windows/deployment/windows-sv-prepare.md similarity index 100% rename from windows/deployment/windows-11-prepare.md rename to windows/deployment/windows-sv-prepare.md diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 97ba2fdf8a..1013fb36b3 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -26,14 +26,14 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows SV overview - url: /windows-11/windows-sv-overview.md - - text: What's new in Windows SV, version 21H2 - url: /windows/whats-new/whats-new-windows-10-version-21H1 + - text: Windows Sun Valley overview + url: /windows/whats-new/windows-sv-overview.md + - text: Windows Sun Valley requirements + url: /windows/whats-new/windows-sv-requirements.md + - text: Get started with Windows Sun Valley + url: /windows/whats-new/get-started-windows-sv.md - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - - text: Windows Sun Valley release information - url: /windows/release-health/release-information - text: Windows 10 release information url: /windows/release-health/release-information @@ -45,7 +45,7 @@ landingContent: - text: Configure Windows client url: /windows/configuration/index - text: Configure Windows Sun Valley - url: /windows/configuration/windows-11-configure.md + url: /windows/configuration/windows-sv-configure.md - text: Accessibility information for IT Pros url: /windows/configuration/windows-10-accessibility-for-itpros - text: Configure access to Microsoft Store @@ -77,8 +77,8 @@ landingContent: links: - text: Windows application management url: /windows/application-management/index - - text: Manage Windows SV applications - url: /windows/application-management/windows-11-app-manage.md + - text: Manage Windows Sun Valley applications + url: /windows/application-management/windows-sv-app-manage.md - text: Understand the different apps included in Windows 10 url: /windows/application-management/apps-in-windows-10 - text: Get started with App-V for Windows 10 @@ -94,7 +94,7 @@ landingContent: - text: Windows client management url: /windows/client-management/index - text: Manage Windows Sun Valley - url: /windows/client-management/windows-11-manage.md + url: /windows/client-management/windows-sv-manage.md - text: Administrative tools url: /windows/client-management/administrative-tools-in-windows-10 - text: Create mandatory user profiles From dd2fcb113d1fcf73b056d6666057d478d25523c5 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 16:46:49 -0700 Subject: [PATCH 021/104] edits --- windows/whats-new/index.yml | 28 +++++++++++++++++++++------- 1 file changed, 21 insertions(+), 7 deletions(-) diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index 45c6930684..7531bc087e 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -22,6 +22,26 @@ landingContent: # Cards and links should be based on top customer tasks or top subjects # Start card title with a verb # Card (optional) + + - title: Windows Sun Valley + linkLists: + - linkListType: overview + links: + - text: Windows Sun Valley Overview + url: windows-sv-overview.md + - text: Windows Sun Valley requirements + url: windows-sv-requirements.md + - text: Get started with Windows Sun Valley + url: windows-sv-get-started.md + - text: Deploy Windows Sun Valley + url: /windows/deployment/windows-sv-deploy.md + - text: Windows Sun Valley app management + url: /windows/application-managerment/windows-sv-app-manage.md + - text: Configure Windows Sun Valley + url: /windows/configuration/windows-sv-configure.md + - text: Manage Windows Sun Valley clients + url: /windows/client-management/windows-sv-manage.md + - title: What's new in Windows 10 linkLists: - linkListType: overview @@ -57,13 +77,7 @@ landingContent: url: /windows/deployment/planning/windows-10-removed-features - text: Compare Windows 10 Editions url: https://go.microsoft.com/fwlink/p/?LinkId=690485 - - # Card (optional) - - title: See also - linkLists: - - linkListType: overview - links: - text: Windows 10 Enterprise LTSC url: ltsc/index.md - text: Edit an existing topic using the Edit link - url: contribute-to-a-topic.md \ No newline at end of file + url: contribute-to-a-topic.md From 5f4f59a8dcdc3f4eaa0c0743bafb40648c084eb5 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 19:27:32 -0700 Subject: [PATCH 022/104] edits --- windows/whats-new/TOC.yml | 2 +- windows/whats-new/index.yml | 29 +++++++++-------------------- 2 files changed, 10 insertions(+), 21 deletions(-) diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index 4ee09a9849..cc890c69f0 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -1,4 +1,4 @@ -- name: What's new in Windows client +- name: What's new in Windows href: index.yml - name: Windows Sun Valley items: diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index 7531bc087e..e1c75debe3 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -1,11 +1,11 @@ ### YamlMime:Landing -title: What's new in Windows 10 # < 60 chars -summary: Find out about new features and capabilities in the latest release of Windows 10. # < 160 chars +title: What's new in Windows # < 60 chars +summary: Find out about new features and capabilities in the latest release of Windows 10 and Windows Sun Valley. # < 160 chars metadata: - title: What's new in Windows 10 # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Find out about new features and capabilities in the latest release of Windows 10. # Required; article description that is displayed in search results. < 160 chars. + title: What's new in Windows # Required; page title displayed in search results. Include the brand. < 60 chars. + description: Find out about new features and capabilities in the latest release of Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice @@ -13,7 +13,7 @@ metadata: ms.collection: windows-10 author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. ms.author: greglin #Required; microsoft alias of author; optional team alias. - ms.date: 02/09/2021 #Required; mm/dd/yyyy format. + ms.date: 06/02/2021 #Required; mm/dd/yyyy format. localization_priority: medium # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new @@ -33,14 +33,7 @@ landingContent: url: windows-sv-requirements.md - text: Get started with Windows Sun Valley url: windows-sv-get-started.md - - text: Deploy Windows Sun Valley - url: /windows/deployment/windows-sv-deploy.md - - text: Windows Sun Valley app management - url: /windows/application-managerment/windows-sv-app-manage.md - - text: Configure Windows Sun Valley - url: /windows/configuration/windows-sv-configure.md - - text: Manage Windows Sun Valley clients - url: /windows/client-management/windows-sv-manage.md + - title: What's new in Windows 10 linkLists: @@ -56,8 +49,6 @@ landingContent: url: whats-new-windows-10-version-1909.md - text: What's new in Windows 10, version 1903 url: whats-new-windows-10-version-1903.md - - text: What's new in Windows 10, version 1809 - url: whats-new-windows-10-version-1809.md # Card (optional) @@ -65,11 +56,11 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows 10 release information + - text: Windows release information url: /windows/release-health/release-information - - text: Windows 10 release health dashboard + - text: Windows release health dashboard url: /windows/release-information/ - - text: Windows 10 update history + - text: Windows update history url: https://support.microsoft.com/topic/windows-10-update-history-7dd3071a-3906-fa2c-c342-f7f86728a6e3 - text: Windows 10 features we’re no longer developing url: /windows/deployment/planning/windows-10-deprecated-features @@ -79,5 +70,3 @@ landingContent: url: https://go.microsoft.com/fwlink/p/?LinkId=690485 - text: Windows 10 Enterprise LTSC url: ltsc/index.md - - text: Edit an existing topic using the Edit link - url: contribute-to-a-topic.md From 98f419251ca43ddcfdbae667089c6995cfc02502 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 19:46:44 -0700 Subject: [PATCH 023/104] edits --- windows/hub/TOC.yml | 9 ++-- windows/whats-new/windows-sv-get-started.md | 46 ++++---------------- windows/whats-new/windows-sv-overview.md | 8 ++-- windows/whats-new/windows-sv-requirements.md | 8 ++-- 4 files changed, 22 insertions(+), 49 deletions(-) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 71671b2312..d8320ed98c 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -1,10 +1,13 @@ - name: Windows href: index.yml items: - - name: Windows Sun Valley - href: /windows/whats-new/windows-sv-overview.md - name: What's new - href: /windows/whats-new + expanded: true + items: + - name: What's new in Windows + href: /windows/whats-new + - name: Windows Sun Valley + href: /windows/whats-new/windows-sv-overview.md - name: Release information href: /windows/release-health - name: Deployment diff --git a/windows/whats-new/windows-sv-get-started.md b/windows/whats-new/windows-sv-get-started.md index c2522f3e4c..3bcdd4f4e0 100644 --- a/windows/whats-new/windows-sv-get-started.md +++ b/windows/whats-new/windows-sv-get-started.md @@ -1,51 +1,21 @@ --- -title: Get started with Windows 10, version 1709 -description: Learn about features, review requirements, and plan your deployment of Windows 10, version 1709, including IT Pro content, release information, and history. -keywords: ["get started", "windows 10", "fall creators update", "1709"] +title: Get started with Windows Sun Valley +description: Learn about features, review requirements, and plan your deployment of Windows Sun Valley, including IT Pro content, release information, and history. +keywords: ["get started", "windows sun valley"] ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library -author: dansimp -ms.author: dansimp +author: greg-lindsay +ms.author: greglin ms.date: 10/16/2017 ms.reviewer: -manager: dansimp +manager: laurawi ms.localizationpriority: high ms.topic: article --- -# Get started with Windows 10, version 1709 +# Get started with Windows Sun Valley **Applies to** -- Windows 10 - -> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) - -Welcome to Windows 10, version 1709, also known as the Fall Creators Update. Use the following information to learn about new features, review system requirements, and plan your deployment of the latest version of Windows 10. - -## Specification and systems requirements - -Before you install any version of Windows 10, make sure you visit the [Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/windows/windows-10-specifications) page. This page contains the minimum systems requirements and important notes to install Windows 10, as well as feature deprecation information and additional requirements to use certain features. - -## What's new in Windows 10, version 1709 IT Pro content - -Take a look at the [What's new in Windows 10, version 1709 IT Pro content](whats-new-windows-10-version-1709.md), for the latest updates in content. Use this topic to easily navigate the documentation for the new features in Windows 10, version 1709. - -## Windows 10 release information and update history - -To view availability dates and servicing options for each version and update of Windows, including version 1709, visit the [Windows 10 release information](https://technet.microsoft.com/windows/mt679505.aspx) page. For further details on each update, go to the [Windows 10 update history](https://support.microsoft.com/help/4018124/windows-10-update-history) page. - -## Windows 10 Roadmap - -If you'd like to gain some insight into preview, or in-development features, visit the [Windows 10 Roadmap](https://www.microsoft.com/WindowsForBusiness/windows-roadmap) page. You'll be able to filter by feature state and product category, to make this information easier to navigate. - -## Top support solutions for Windows 10 - -Having problems with your latest deployment of Windows 10, version 1709? Check out the [Top support solutions for Windows 10](/windows/client-management/windows-10-support-solutions) topic, where we've collected the top Microsoft Support solutions for the most common issues experienced when using Windows 10 in an enterprise or IT pro environment. - -> Want even more information? Visit the [Windows 10 lifecycle page](https://www.microsoft.com/itpro/windows-10) on the [Windows IT Pro Center](https://itpro.windows.com). - -Ready to get started with Windows 10, version 1709? -> [!div class="nextstepaction"] -> [Deploy and Update Windows 10](/windows/deployment) +- Windows Sun Valley diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index f39f5e4c23..7b375294fe 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -1,6 +1,6 @@ --- -title: Placeholder -description: PH +title: Windows Sun Valley overview +description: Overview of Windows Sun Valley ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C ms.reviewer: manager: laurawi @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows 11 overview +# Windows Sun Valley overview -Overview of Windows 11. +Overview of Windows Sun Valley. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 482850a4f9..8c7e043b4e 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -1,6 +1,6 @@ --- -title: Placeholder -description: PH +title: Windows Sun Valley requirements +description: Hardware requirements to deploy Windows Sun Valley ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C ms.reviewer: manager: laurawi @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows 11 requirements +# Windows Sun Valley requirements -Windows 11 requirements. +Windows Sun Valley requirements. From 802d5c6d87fd2c3de55894ab0b3d93412cc4d23d Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 19:57:04 -0700 Subject: [PATCH 024/104] edits --- windows/hub/TOC.yml | 2 +- windows/hub/index.yml | 6 +++--- windows/whats-new/TOC.yml | 2 ++ 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index d8320ed98c..0b7e4c7651 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -7,7 +7,7 @@ - name: What's new in Windows href: /windows/whats-new - name: Windows Sun Valley - href: /windows/whats-new/windows-sv-overview.md + href: whats-new/windows-sv-overview.md - name: Release information href: /windows/release-health - name: Deployment diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 1013fb36b3..372692de4c 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -1,11 +1,11 @@ ### YamlMime:Landing title: Windows client resources and documentation for IT Pros # < 60 chars -summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # < 160 chars +summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows Sun Valley. # < 160 chars metadata: title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Evaluate, plan, deploy, secure and manage devices running Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars. + description: Evaluate, plan, deploy, secure and manage devices running Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice @@ -34,7 +34,7 @@ landingContent: url: /windows/whats-new/get-started-windows-sv.md - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - - text: Windows 10 release information + - text: Windows release information url: /windows/release-health/release-information # Card (optional) diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index cc890c69f0..21c6326fb5 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -1,6 +1,7 @@ - name: What's new in Windows href: index.yml - name: Windows Sun Valley + expanded: true items: - name: Windows Sun Valley overview href: windows-sv-overview.md @@ -9,6 +10,7 @@ - name: Get started with Windows Sun Valley href: windows-sv-get-started.md - name: Windows 10 + expanded: true items: - name: What's new in Windows 10, version 21H1 href: whats-new-windows-10-version-21H1.md From 15cac4271a529104b3594a1de5f11d205c81d23f Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 20:01:30 -0700 Subject: [PATCH 025/104] edits --- windows/hub/TOC.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 0b7e4c7651..13a76d8a85 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -7,7 +7,7 @@ - name: What's new in Windows href: /windows/whats-new - name: Windows Sun Valley - href: whats-new/windows-sv-overview.md + href: whats-new/windows-sv-overview - name: Release information href: /windows/release-health - name: Deployment From d97c072e54335eb4c8f40cd7812a2fb13daa2a8e Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 20:05:09 -0700 Subject: [PATCH 026/104] edits --- windows/hub/index.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 372692de4c..14991296ce 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -42,7 +42,7 @@ landingContent: linkLists: - linkListType: how-to-guide links: - - text: Configure Windows client + - text: Configure Windows url: /windows/configuration/index - text: Configure Windows Sun Valley url: /windows/configuration/windows-sv-configure.md @@ -58,7 +58,7 @@ landingContent: linkLists: - linkListType: deploy links: - - text: Deploy and update Windows client + - text: Deploy and update Windows url: /windows/deployment/index - text: Deploy Windows Sun Valley url: /windows/deployment/windows-sv-deploy.md From 006dc81e807bf7c55248723d73b8fe0881c47f84 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 20:08:07 -0700 Subject: [PATCH 027/104] cant get link to work --- windows/hub/TOC.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 13a76d8a85..18f3f6c535 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -7,7 +7,7 @@ - name: What's new in Windows href: /windows/whats-new - name: Windows Sun Valley - href: whats-new/windows-sv-overview + href: /windows/whats-new/windows-sv-overview - name: Release information href: /windows/release-health - name: Deployment From e09986f3beda35c0d0e04a1d3b17c89c2f0703ae Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 20:15:22 -0700 Subject: [PATCH 028/104] fixup --- windows/deployment/TOC.yml | 8 ++-- windows/deployment/index.yml | 2 +- windows/sv/index.yml | 42 +++++++++---------- windows/sv/windows-11-faq.md | 21 ---------- ...1-lifecycle.md => windows-sv-lifecycle.md} | 0 ...-11-overview.md => windows-sv-overview.md} | 0 ...irements.md => windows-sv-requirements.md} | 0 7 files changed, 25 insertions(+), 48 deletions(-) delete mode 100644 windows/sv/windows-11-faq.md rename windows/sv/{windows-11-lifecycle.md => windows-sv-lifecycle.md} (100%) rename windows/sv/{windows-11-overview.md => windows-sv-overview.md} (100%) rename windows/sv/{windows-11-requirements.md => windows-sv-requirements.md} (100%) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 50fd1c8bb7..0e2693fd62 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -6,7 +6,7 @@ - name: What's new href: deploy-whats-new.md - name: Windows 11 deployment overview - href: windows-11-deploy.md + href: windows-sv-deploy.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? @@ -36,7 +36,7 @@ - name: Plan items: - name: Windows 11 deployment planning - href: windows-11-plan.md + href: windows-sv-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria @@ -72,7 +72,7 @@ - name: Prepare items: - name: Prepare to deploy Windows 11 - href: windows-11-prepare.md + href: windows-sv-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md - name: Evaluate and update infrastructure @@ -105,7 +105,7 @@ - name: Deploy Windows client items: - name: Windows 11 deployment overview - href: windows-11-deploy.md + href: windows-sv-deploy.md - name: Deploy Windows client with Autopilot href: windows-autopilot/index.yml - name: Deploy Windows client with Configuration Manager diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index f6f9bf26ec..7b8a56f315 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -67,7 +67,7 @@ landingContent: - text: What's new in Windows deployment url: deploy-whats-new.md - text: Windows 11 deployment overview - url: sv-deploy.md + url: windows-sv-deploy.md - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md - text: Basics of Windows updates, channels, and tools diff --git a/windows/sv/index.yml b/windows/sv/index.yml index 5e33fe3113..9ce50839f3 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -1,7 +1,7 @@ ### YamlMime:Landing title: Windows SV # < 60 chars -summary: Find out about Windows Windows 11. # < 160 chars +summary: Find out about Windows Windows Sun Valley. # < 160 chars metadata: title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. @@ -26,38 +26,36 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows Windows 11 overview - url: sv-overview.md - - text: Windows Windows 11 requirements - url: sv-requirements.md - - text: Windows Windows 11 FAQ - url: sv-faq.md + - text: Windows Sun Valley overview + url: windows-sv-overview.md + - text: Windows Sun Valley requirements + url: windows-sv-requirements.md # Card (optional) - - title: Deploy Windows 11 + - title: Deploy Windows Sun Valley linkLists: - linkListType: overview links: - - text: Plan to deploy Windows Windows 11 - url: /windows/deployment/sv-plan.md - - text: Prepare for Windows Windows 11 - url: /windows/deployment/sv-prepare.md - - text: Deploy Windows Windows 11 - url: /windows/deployment/sv-deploy.md - - text: Configure Windows Windows 11 + - text: Plan to deploy Windows Windows Sun Valley + url: /windows/deployment/windows-sv-plan.md + - text: Prepare for Windows Windows Sun Valley + url: /windows/deployment/windows-sv-prepare.md + - text: Deploy Windows Windows Sun Valley + url: /windows/deployment/windows-sv-deploy.md + - text: Configure Windows Windows Sun Valley url: /windows/configuration/sv-configure.md - - text: Manage Windows Windows 11 - url: /windows/client-management/sv-manage.md - - text: Windows Windows 11 application readiness - url: /windows/application-management/sv-app-readiness.md + - text: Manage Windows Windows Sun Valley + url: /windows/client-management/windows-sv-manage.md + - text: Windows Windows Sun Valley application readiness + url: /windows/application-management/windows-sv-app-readiness.md # Card (optional) - title: Support information linkLists: - linkListType: overview links: - - text: Windows Windows 11 lifecycle + - text: Windows Windows Sun Valley lifecycle url: placeholder.md - - text: Windows Windows 11 release information - url: ../release-health + - text: Windows Windows Sun Valley release information + url: /windows/release-health diff --git a/windows/sv/windows-11-faq.md b/windows/sv/windows-11-faq.md deleted file mode 100644 index 1ac810bb60..0000000000 --- a/windows/sv/windows-11-faq.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Placeholder -description: PH -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows 11 frequently asked questions (FAQ) - -FAQ. - diff --git a/windows/sv/windows-11-lifecycle.md b/windows/sv/windows-sv-lifecycle.md similarity index 100% rename from windows/sv/windows-11-lifecycle.md rename to windows/sv/windows-sv-lifecycle.md diff --git a/windows/sv/windows-11-overview.md b/windows/sv/windows-sv-overview.md similarity index 100% rename from windows/sv/windows-11-overview.md rename to windows/sv/windows-sv-overview.md diff --git a/windows/sv/windows-11-requirements.md b/windows/sv/windows-sv-requirements.md similarity index 100% rename from windows/sv/windows-11-requirements.md rename to windows/sv/windows-sv-requirements.md From 9d3f37c97518a8655fc3964f13dd538c353a35cf Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 2 Jun 2021 20:27:26 -0700 Subject: [PATCH 029/104] fixup --- windows/sv/TOC.yml | 44 +++++++++++++-------------- windows/sv/windows-sv-overview.md | 8 ++--- windows/sv/windows-sv-requirements.md | 9 +++--- 3 files changed, 29 insertions(+), 32 deletions(-) diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index ad14e66327..f0ec3588a7 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,35 +1,33 @@ -- name: Windows 11 +- name: Windows Sun Valley href: index.yml items: - name: Get started items: - - name: Windows 11 overview - href: windows-11-overview.md - - name: Windows 11 requirements - href: windows-11-requirements.md - - name: Windows 11 FAQ - href: windows-11-faq.md + - name: Windows Sun Valley overview + href: windows-sv-overview.md + - name: Windows Sun Valley requirements + href: windows-sv-requirements.md - - name: Deploy and Manage Windows 11 + - name: Deploy and Manage Windows Sun Valley items: - - name: Plan to deploy Windows 11 - href: /windows/deployment/windows-11-plan - - name: Prepare for Windows 11 - href: /windows/deployment/windows-11-prepare.md - - name: Deploy Windows 11 - href: /windows/deployment/windows-11-deploy.md - - name: Configure Windows 11 - href: /windows/configuration/windows-11-configure.md - - name: Manage Windows 11 - href: /windows/client-management/windows-11-manage.md - - name: Windows 11 application readiness - href: /windows/application-management/windows-11-app-readiness.md + - name: Plan to deploy Windows Sun Valley + href: /windows/deployment/windows-sv-plan + - name: Prepare for Windows Sun Valley + href: /windows/deployment/windows-sv-prepare.md + - name: Deploy Windows Sun Valley + href: /windows/deployment/windows-sv-deploy.md + - name: Configure Windows Sun Valley + href: /windows/configuration/windows-sv-configure.md + - name: Manage Windows Sun Valley + href: /windows/client-management/windows-sv-manage.md + - name: Windows Sun Valley application readiness + href: /windows/application-management/windows-sv-app-readiness.md - name: Support items: - - name: Windows 11 lifecycle - href: windows-11-lifecycle.md - - name: Windows 11 release information + - name: Windows Sun Valley lifecycle + href: windows-sv-lifecycle.md + - name: Windows Sun Valley release information href: /windows/release-health diff --git a/windows/sv/windows-sv-overview.md b/windows/sv/windows-sv-overview.md index f39f5e4c23..7b375294fe 100644 --- a/windows/sv/windows-sv-overview.md +++ b/windows/sv/windows-sv-overview.md @@ -1,6 +1,6 @@ --- -title: Placeholder -description: PH +title: Windows Sun Valley overview +description: Overview of Windows Sun Valley ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C ms.reviewer: manager: laurawi @@ -16,7 +16,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows 11 overview +# Windows Sun Valley overview -Overview of Windows 11. +Overview of Windows Sun Valley. diff --git a/windows/sv/windows-sv-requirements.md b/windows/sv/windows-sv-requirements.md index 482850a4f9..88eb31f2f5 100644 --- a/windows/sv/windows-sv-requirements.md +++ b/windows/sv/windows-sv-requirements.md @@ -1,7 +1,6 @@ --- -title: Placeholder -description: PH -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +title: Windows Sun Valley requirements +description: Requirements to deploy Windows Sun Valley ms.reviewer: manager: laurawi ms.audience: itpro @@ -16,7 +15,7 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows 11 requirements +# Windows Sun Valley requirements -Windows 11 requirements. +Windows Sun Valley requirements. From 4921cd416d3d24245aaacb7ec5e017c04ca9018a Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 00:25:37 -0700 Subject: [PATCH 030/104] leverage faq --- windows/whats-new/windows-sv-overview.md | 187 ++++++++++++++++++- windows/whats-new/windows-sv-requirements.md | 2 +- 2 files changed, 187 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index 7b375294fe..3ab1b42497 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -18,5 +18,190 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley overview -Overview of Windows Sun Valley. +Sun Valley is the next client release of Windows. It represents an evolution of Windows 10 that is modern, streamlined, fresh, light, yet familiar to those who use Windows today. It is optimized to deliver great working, learning, and playing experiences. Its goal is to be our most reliable, secure, connected, and performant OS release ever. + +Sun Valley offers new features and functionality built to address challenges our customers face today as well as a completely refreshed look and feel that makes the experience clean and simple. Head to Windows.com/SV to read more about all the new features. + +Windows 10 launched six years ago. Since then, there has been a lot of hardware innovation. With Windows SV every detail has been considered. It has the power and security you crave in a redesigned and refreshed look. Plus, it comes with new tools, sounds, and apps. + +Windows SV provides a familiar modern and refreshed interface that is still familiar that increases productivity and enhances the collaboration experience for end users while maintaining consistent the management forof those IT managed devices. for IT + +The goal with Windows is still the same, regardless of number. Our commitment to drive innovation, bring people together and build the best version of Windows remains. +We said we would always update Windows, of course we’re going to innovate, move people forward, commitment to give people the best version of Windows remains. + +We expect most new devices to be built and designed for Windows SV, and consumer offerings will transition very quickly. Commercial and educational organizations should work with their device partners to understand what options are available for new PCs. + +Commercial version +Eventually all new devices will be built and shipped with Windows Oct2021. Commercial organizations should work with their device partners to understand what options are available for new PCs + +Will there be an evaluation version of Sun Valley? Yes, you can take advantage of the Windows Insider Program to evaluate builds of Sun Valley just as we do today for Windows 10. + +When will new devices be ready for purchase? New devices will be available later in 2021. We expect to see a large refresh of commercial devices in 2022 + +## How to get Windows Sun Valley + +All upgrades to Sun Valley from Windows 10 will be free. + +Windows Sun Valley is due out later in 2021 and will be delivered over several months. The rollout of the upgrade to Windows 10 devices already in use today will begin in 2022 through the first half of that year. Once it has been tested and validated for your specific PC, Windows Update will indicate that the upgrade is ready for installation. + +If your Windows 10 PC meets the minimum specifications for Sun Valley, you will be able to upgrade. We’ve made it simple for you to see for yourself. Download the PC Health Check App to see if your PC meets the minimum specifications. (go to aka.ms/PCHealthCheck - not real URL) + +Commercial version +There is no cost to upgrade for eligible devices to Windows Oct21. Only Windows 10 PCs that are running the most current version of Windows 10 and meet the minimum hardware specifications will be eligible to upgrade. You can check to see if you have the latest updates by navigating to Windows Update in settings. + +Commercial version +The upgrade is expected to be available in early 2022. Not all eligible Windows 10 PCs will be offered theo upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). Once the upgrade rollout has started, you can check the status of your device by navigating to Windows Update in settings.  + +Test out either experience by joining the Windows Insider Program (either by syncing the Windows Insider Pre-release category in WSUS or by selecting “Manage preview builds – Release Preview”). + + +## Windows Sun Valley servicing + +No. Features of Windows SV will be updated once per year in the second half of the year, and quality updates will be releasesd every month oin the second Tuesday of the month. Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month + +Commercial version +No. Features of Windows Oct21 will be updated once per year in the second half of the year, and quality updates will be released every month in the second Tuesday of the month. Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. + +How long is the support window for each Sun Valley release? We will support each annual release for 24 months for Home, Pro, Pro for Workstations and Pro Education editions, and 36 months for Enterprise and Education editions, beginning at GA in October 2021 + +Annual SV releases will be supported for either 24 or 36 months, depending on edition, beginning at their initial GA. + +• SV editions supported for 24 months: Home, Pro, Pro Education, Pro for Workstations, Cloud +• SV editions supported for 36 months: Enterprise, IoT Enterprise, Education + +Will there still be a combined LCU and SSU package capability? Yes. Windows XX will continue to support one cumulative package where we will deploy all LCUs and SSUs (if applicable) together as a single package to Windows Server Update Service (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for those updating from Windows Update. + +## Mixed environment + +Yes. We will continue to support Windows 10 with security updates until October 2025. + +Can I run both Sun Valley and Windows 10 in parallel? If so, do I use the same process and tools to manage both? Yes, Windows SV is based on the same foundation of Windows 10 so they can coexist and will use the same processes and tools to manage them. + +Will I be able to manage my Windows environment with MEM in the same way, or will there be changes? In Configuration Manager, you can manage exactly the same way you do today. Simply sync the new Windows XX Product category. + +How will update management look for environments with mixed Sun Valley and Windows 10 populations? You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows XX, in addition to using them to move between the two products. + + +Commercial +Yes. You do not have to upgrade to Windows Oct21. Microsoft will continue to support Windows 10 until October 14, 2025. + +## Deploying Windows Sun Valley + +You will have the option to upgrade, clean install, or reimage Windows 10 devices to move to Windows SV. For Windows 7 devices that meet hardware requirements, you will need to clean install or reimage to go directly to Windows SV. + +Any specific rollback or upgrade recover mechanisms exist? The Windows SV upgrade has a 10 day rollback period, similar to what is offered today for Windows 10 updates + +I leverage Autopilot to allow end users auto provision devices, will Autopilot be available for Sun Valley? Yes, Autopilot can still be leveraged. + +Timing will vary, particularly based on internet speed. Downloading and installing Windows SV will most likely take longer than a typical Windows 10 feature update. You can use your PC while you’re downloading it and then you have the option to schedule the install to happen at a specific time when you aren’t planning on using your PC. + +The free upgrade is for the same edition as you have on your device for Windows 10. If you have Windows 10 Home eEdition, you will be upgraded to Windows SV Home eEdition. For Pro and higher editions, SV will no longer be offered in S mode, so you will need to first switch out of S mode toto qualify for upgrade. + +Commercial +The upgrade to Windows Oct21 is for the same edition as you have on your Windows 10 device. Devices with Windows 10 Pro installed will be upgraded to Windows Oct21 Pro. Devices running Windows 10 Enterprise will upgrade to Windows Oct21 Enterprise. Windows Oct21 Pro will not offer Windows Oct21 Pro in S mode, so you will need to switch out of S mode to upgrade. + +Yes, once you have upgraded to Sun Valley, you have 10 days to utilize the rollback function to move back to Windows 10 while keeping files and data that you brought along with you. After that 10 day10-day period, you will need to back up this data and do a “clean install” to move back to Windows 10. + +In Intune, you will need to leverage target version, if you are not already, to upgrade from Windows 10 to Windows XX. While feature update deferrals are great for moving you to newer versions of your current product (e.g. Windows 10, version 20H2 to 21H1) they are not able to move you between two different products. You will continue being able to manage quality updates for Windows 10 and Windows XX the same way as you do today. + +Commercial +Yes, once you have upgraded to Windows Oct21, you have 10 days to utilize the rollback function to move back to Windows 10 while keeping files and data that you brought along with you. After that 10-day period, you will need to back up your data and do a “clean install” to move back to Windows 10. + +The upgrade experience will be similar to a feature update in Windows 10. You will download the software while able to continue to use your device. Once it is downloaded and ready to install, you will be guided through the installation process through aprocess: a series of screen and prompts. + +Commercial version +The upgrade experience will be similar to a feature update in Windows 10. You will download the software while being able to continue to use your device. Once the update is downloaded and ready to install, you will be guided through the installation process through a series of screens and prompts. There will be at least one restart. + +If I decline the upgrade, can I change my mind and upgrade later? You will be given the opportunity to upgrade via the Windows Update section in Settings if you originally declined the offer. + +If customers upgrade, the default experience will be for files and data to move forward with the new installation. However, we always recommend that customers back up files before installing a new Windows version. If you already sync your files to OneDrive, you may not need to take any additional action to create a backup. + +Commercial version +By default, all your files and data will transfer. However, Microsoft recommends backing up your files before installation. + +Are customers able to download the upgrade ‘on demand’? Will there be ways that customers can find the upgrade prior to Intelligent rollout? Yes, we plan to have similar options that we do today for updates to Windows 10: Upgrade Assistant (similar to Update Assistant) and the Media Creation Tool. We recommend, however, that the customer wait until they are notified through Windows Update that the upgrade is ready for their device. Note that there will be temporary blocks in some instances that will prevent the upgrade from completing installation. + +If a CYOD user purchases a Sun Valley device, can I move them back to Windows 10 and how? Downgrade rights are available with Windows SV Pro OEM licensed devices. You can downgrade to any version of Windows Pro/Professional that has not reached its end of support date. You will need to reimage or clean install a Windows SV device to downgrade it to Windows 10. Downgrade rights are also available through Microsoft Volume Licensing (check your agreement for more details). + +If I’m upgrading from Windows 10 to Sun Valley can I change editions at that time (e.g., from Home or Education to Pro)? No, you will need to change editions separately (before or after upgrading). Applicable fees may apply to acquire the license for the new edition + +Commercial version +If you have Windows 10 Pro, you’ll upgrade to Windows Oct2021 Pro. You can then step up to Windows Oct2021 Enterprise. If you have Windows 10 Home, you’ll upgrade to Windows Oct2021 Home. You can then step up to Windows 10 Pro. + +## Requirements + +The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. + +You can use the PC Health Check app to determine if your PC can upgrade. The PC Health Check is available for download . [this will eventually need to change to a message about WU – Aug 2021 timeframe] + +Can Enterprise customers get the upgrade? Enterprise customers are eligible per the terms of their current licensing agreement + +What about Windows RT? Windows RT is not eligible for upgrade. + +Any device that meets the minimum specification can upgrade run Windows SV. However, Windows 7 devices will likely not meet the minimum specification because of age and generation of the processor that was included with that device. Please see below for the full CPU list available through our Windows SV specifications page to see which ones are compatible for upgrade. If a customer with a Windows 7 PC that meets the minimum spec wants to upgrade, they would need to purchase a Windows 10 license, perform a clean install, and proceed with the upgrade to Windows SV. In 2022, they will also have the option to purchase Windows SV at retail and install it on the compatible Windows 7 device. + +The minimum storage drive requirement is 64GB for Windows SV. Ongoing requirements for feature and quality updates will vary, but are generally expected to be similar to what we see today for Windows 10 + + +Commercial +To see if your PC is eligible, download the PC Health Check app (link). Once the upgrade rollout has started, you can check the status of your device by navigating to Windows Update in settings. + +## Managing Windows Sun Valley + + +With Windows 10, Microsoft forced me to make significant changes to my IT processes, management approach and tooling, what will this new version require me to change? Windows SV is based on the same foundation of Windows 10, so it will support the same management tools that you use today with Windows 10. + +## Hardware compatibility + +Most software and accessories that worked with Windows 10 areis expected to work with Windows SV. Check with your software publisher or accessory manufacturer for specific details on your products. + +Commercial version +Most software and accessories that worked with Windows 10 are expected to work with Windows Oct21. Check with your software publisher or accessory manufacturer for specific details on your products. + +Most software and accessories that worked with Windows 10 is expected to work with Windows SV. Check with your software publisher or accessory manufacturer for specific details on your products. + +Most software and accessories that worked with Windows 10 is expected to work with Windows SV. Check with your software publisher or accessory manufacturer for specific details on your products and to see if an upgrade of your security solution is required for WIndowsWindows SV. + +Commercial version +Most software and accessories that worked with Windows 10 are expected to work with Windows Oct21. Check with your software publisher or accessory manufacturer for specific details on your products. + +## App management in Windows Sun Valley + +Commercial version (specific to apps) +Yes, Microsoft is committed to ensuring your applications work on the latest versions of our software and Windows Oct21 has been built with compatibility in mind. Our promise states that apps that worked on Windows 7/8.1/10 will work on Windows Oct21. If you have App Assure, Microsoft will help you fix them at no cost. + +App Assure is a service that helps customers remediate application issues that they may experience when deploying the latest version of our software. + +App Assure is available at no additional cost for eligible customers with 150+ seats. For more information on eligibility requirements, please navigate to this page + +Visit the App Assure page and sign in to submit your request for assistance for a dedicated App Assure Manager. If you experience any issues submitting a request for assistance, please contact ACHELP@microsoft.com and our team members will reach out to you to help! + +Yes, most apps and devices that worked with Windows 10 will be compatible with Sun Valley. You can also check with your software publisher manufacturer for more detailed information. + +## Licensing + +Will I get Sun Valley as part of my Microsoft 365 license? +Microsoft 365 licenses that include Windows licenses will allow you to run Sun Valley on supported devices. + + +If I have a volume license, will it equally cover Sun Valley and Windows 10 devices both before and after upgrade? Yes + +## Applications + +Will Safeguard holds still function for SV and how will that work between the two different OS versions? Yes. IT Administrators will have access to safeguard hold information using Update Compliance. More information can be found here. + +What’s going to happen with kiosk mode? Commercial version +Windows Oct2021 is committed to support all of the commercial scenarios that we supported in Windows 10, which includes kiosk mode. In this initial Windows Oct2021 release, we are supporting single app kiosk mode. In the future, we plan to support multi-app kiosk mode. + +Will Known Issue Rollback (KIR) function on SV? Yes, the known issue rollback will function on SV. + +What’s not in Sun Valley that’s in Windows 10? (link to Aaron Grady deck). This is also published on the Windows specifications page and there will be a docs/technet article that will be published, too + + +---------------------------------------- + + + + + diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 8c7e043b4e..fffaec9814 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -18,5 +18,5 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley requirements -Windows Sun Valley requirements. +The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. From 9446cdaa9b55733b5d45a70c95127d648a349367 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 10:32:38 -0700 Subject: [PATCH 031/104] edits --- windows/deployment/windows-sv-deploy.md | 13 +- windows/whats-new/windows-sv-overview.md | 193 ++++--------------- windows/whats-new/windows-sv-requirements.md | 24 +++ 3 files changed, 73 insertions(+), 157 deletions(-) diff --git a/windows/deployment/windows-sv-deploy.md b/windows/deployment/windows-sv-deploy.md index ca92e990a7..033c8308fa 100644 --- a/windows/deployment/windows-sv-deploy.md +++ b/windows/deployment/windows-sv-deploy.md @@ -1,7 +1,6 @@ --- -title: Windows 11 deployment planning -description: Understand the different ways Windows 10 operating system can be deployed in your organization. Explore several Windows 10 deployment scenarios. -ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 +title: Windows Sun Valley deployment planning +description: Understand the different ways Windows Sun Valley operating system can be deployed in your organization. Explore several Windows Sun Valley deployment scenarios. ms.reviewer: manager: laurawi ms.audience: itpro @@ -16,10 +15,12 @@ audience: itpro ms.topic: article --- -# Windows 11 deployment planning +# Windows Sun Valley deployment planning **Applies to** -- Windows 11, version 21H1 +- Windows Sun Valley -To successfully deploy the Windows 11 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. +## + +To successfully deploy the Windows Sun Valley operating system in your organization, ... diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index 3ab1b42497..44ce28569a 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -18,190 +18,81 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley overview -Sun Valley is the next client release of Windows. It represents an evolution of Windows 10 that is modern, streamlined, fresh, light, yet familiar to those who use Windows today. It is optimized to deliver great working, learning, and playing experiences. Its goal is to be our most reliable, secure, connected, and performant OS release ever. +**Applies to** +- Windows Sun Valley -Sun Valley offers new features and functionality built to address challenges our customers face today as well as a completely refreshed look and feel that makes the experience clean and simple. Head to Windows.com/SV to read more about all the new features. +This article provides an introduction to Windows Sun Valley, the next client release of Windows. -Windows 10 launched six years ago. Since then, there has been a lot of hardware innovation. With Windows SV every detail has been considered. It has the power and security you crave in a redesigned and refreshed look. Plus, it comes with new tools, sounds, and apps. +## What is Windows Sun Valley? -Windows SV provides a familiar modern and refreshed interface that is still familiar that increases productivity and enhances the collaboration experience for end users while maintaining consistent the management forof those IT managed devices. for IT - -The goal with Windows is still the same, regardless of number. Our commitment to drive innovation, bring people together and build the best version of Windows remains. -We said we would always update Windows, of course we’re going to innovate, move people forward, commitment to give people the best version of Windows remains. - -We expect most new devices to be built and designed for Windows SV, and consumer offerings will transition very quickly. Commercial and educational organizations should work with their device partners to understand what options are available for new PCs. - -Commercial version -Eventually all new devices will be built and shipped with Windows Oct2021. Commercial organizations should work with their device partners to understand what options are available for new PCs - -Will there be an evaluation version of Sun Valley? Yes, you can take advantage of the Windows Insider Program to evaluate builds of Sun Valley just as we do today for Windows 10. - -When will new devices be ready for purchase? New devices will be available later in 2021. We expect to see a large refresh of commercial devices in 2022 +Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. ## How to get Windows Sun Valley -All upgrades to Sun Valley from Windows 10 will be free. +Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. It will also be available on new devices that meet the hardware requirements. -Windows Sun Valley is due out later in 2021 and will be delivered over several months. The rollout of the upgrade to Windows 10 devices already in use today will begin in 2022 through the first half of that year. Once it has been tested and validated for your specific PC, Windows Update will indicate that the upgrade is ready for installation. +You must be running the most current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). -If your Windows 10 PC meets the minimum specifications for Sun Valley, you will be able to upgrade. We’ve made it simple for you to see for yourself. Download the PC Health Check App to see if your PC meets the minimum specifications. (go to aka.ms/PCHealthCheck - not real URL) +Not all eligible Windows 10 PCs will be offered theo upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to Windows Update in settings. Once the upgrade rollout has started and the upgrade has been tested and validated for your specific PC hardware, Windows Update will indicate that the upgrade is ready for installation. -Commercial version -There is no cost to upgrade for eligible devices to Windows Oct21. Only Windows 10 PCs that are running the most current version of Windows 10 and meet the minimum hardware specifications will be eligible to upgrade. You can check to see if you have the latest updates by navigating to Windows Update in settings. +You can get early access to test Windows Sun Valley by joining the Windows Insider Program, or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). -Commercial version -The upgrade is expected to be available in early 2022. Not all eligible Windows 10 PCs will be offered theo upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). Once the upgrade rollout has started, you can check the status of your device by navigating to Windows Update in settings.  +## Windows Sun Valley lifecycle -Test out either experience by joining the Windows Insider Program (either by syncing the Windows Insider Pre-release category in WSUS or by selecting “Manage preview builds – Release Preview”). +Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. +Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. -## Windows Sun Valley servicing +Windows Sun Valley annual releases are supported for 24 months for the following editions: +- Home +- Pro +- Pro for Workstations +- Pro Education -No. Features of Windows SV will be updated once per year in the second half of the year, and quality updates will be releasesd every month oin the second Tuesday of the month. Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month +Windows Sun Valley annual releases are supported for 36 months for the following editions: +- Enterprise +- Education editions -Commercial version -No. Features of Windows Oct21 will be updated once per year in the second half of the year, and quality updates will be released every month in the second Tuesday of the month. Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. +## Windows 10 lifecycle -How long is the support window for each Sun Valley release? We will support each annual release for 24 months for Home, Pro, Pro for Workstations and Pro Education editions, and 36 months for Enterprise and Education editions, beginning at GA in October 2021 +Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. Windows 10 will be supported with security updates until October 2025. -Annual SV releases will be supported for either 24 or 36 months, depending on edition, beginning at their initial GA. - -• SV editions supported for 24 months: Home, Pro, Pro Education, Pro for Workstations, Cloud -• SV editions supported for 36 months: Enterprise, IoT Enterprise, Education +## OS management in a mixed environment -Will there still be a combined LCU and SSU package capability? Yes. Windows XX will continue to support one cumulative package where we will deploy all LCUs and SSUs (if applicable) together as a single package to Windows Server Update Service (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for those updating from Windows Update. +Windows Sun Valley is based on the same foundation as Windows 10. You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products. -## Mixed environment +## Deploy Windows Sun Valley -Yes. We will continue to support Windows 10 with security updates until October 2025. +Consider using the following process to deploy Windows Sun Valley to existing devices: +1. Preview Windows Sun Valley and create a deployment plan. +2. Test critical applications and management policies. +3. Update devices to the latest release of Windows 10. +4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. +5. Update deployment tools and infrastructure. +6. Update qualifying devices to Windows Sun Valley. -Can I run both Sun Valley and Windows 10 in parallel? If so, do I use the same process and tools to manage both? Yes, Windows SV is based on the same foundation of Windows 10 so they can coexist and will use the same processes and tools to manage them. - -Will I be able to manage my Windows environment with MEM in the same way, or will there be changes? In Configuration Manager, you can manage exactly the same way you do today. Simply sync the new Windows XX Product category. - -How will update management look for environments with mixed Sun Valley and Windows 10 populations? You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows XX, in addition to using them to move between the two products. - - -Commercial -Yes. You do not have to upgrade to Windows Oct21. Microsoft will continue to support Windows 10 until October 14, 2025. - -## Deploying Windows Sun Valley - -You will have the option to upgrade, clean install, or reimage Windows 10 devices to move to Windows SV. For Windows 7 devices that meet hardware requirements, you will need to clean install or reimage to go directly to Windows SV. - -Any specific rollback or upgrade recover mechanisms exist? The Windows SV upgrade has a 10 day rollback period, similar to what is offered today for Windows 10 updates - -I leverage Autopilot to allow end users auto provision devices, will Autopilot be available for Sun Valley? Yes, Autopilot can still be leveraged. - -Timing will vary, particularly based on internet speed. Downloading and installing Windows SV will most likely take longer than a typical Windows 10 feature update. You can use your PC while you’re downloading it and then you have the option to schedule the install to happen at a specific time when you aren’t planning on using your PC. - -The free upgrade is for the same edition as you have on your device for Windows 10. If you have Windows 10 Home eEdition, you will be upgraded to Windows SV Home eEdition. For Pro and higher editions, SV will no longer be offered in S mode, so you will need to first switch out of S mode toto qualify for upgrade. - -Commercial -The upgrade to Windows Oct21 is for the same edition as you have on your Windows 10 device. Devices with Windows 10 Pro installed will be upgraded to Windows Oct21 Pro. Devices running Windows 10 Enterprise will upgrade to Windows Oct21 Enterprise. Windows Oct21 Pro will not offer Windows Oct21 Pro in S mode, so you will need to switch out of S mode to upgrade. - -Yes, once you have upgraded to Sun Valley, you have 10 days to utilize the rollback function to move back to Windows 10 while keeping files and data that you brought along with you. After that 10 day10-day period, you will need to back up this data and do a “clean install” to move back to Windows 10. - -In Intune, you will need to leverage target version, if you are not already, to upgrade from Windows 10 to Windows XX. While feature update deferrals are great for moving you to newer versions of your current product (e.g. Windows 10, version 20H2 to 21H1) they are not able to move you between two different products. You will continue being able to manage quality updates for Windows 10 and Windows XX the same way as you do today. - -Commercial -Yes, once you have upgraded to Windows Oct21, you have 10 days to utilize the rollback function to move back to Windows 10 while keeping files and data that you brought along with you. After that 10-day period, you will need to back up your data and do a “clean install” to move back to Windows 10. - -The upgrade experience will be similar to a feature update in Windows 10. You will download the software while able to continue to use your device. Once it is downloaded and ready to install, you will be guided through the installation process through aprocess: a series of screen and prompts. - -Commercial version -The upgrade experience will be similar to a feature update in Windows 10. You will download the software while being able to continue to use your device. Once the update is downloaded and ready to install, you will be guided through the installation process through a series of screens and prompts. There will be at least one restart. - -If I decline the upgrade, can I change my mind and upgrade later? You will be given the opportunity to upgrade via the Windows Update section in Settings if you originally declined the offer. - -If customers upgrade, the default experience will be for files and data to move forward with the new installation. However, we always recommend that customers back up files before installing a new Windows version. If you already sync your files to OneDrive, you may not need to take any additional action to create a backup. - -Commercial version -By default, all your files and data will transfer. However, Microsoft recommends backing up your files before installation. - -Are customers able to download the upgrade ‘on demand’? Will there be ways that customers can find the upgrade prior to Intelligent rollout? Yes, we plan to have similar options that we do today for updates to Windows 10: Upgrade Assistant (similar to Update Assistant) and the Media Creation Tool. We recommend, however, that the customer wait until they are notified through Windows Update that the upgrade is ready for their device. Note that there will be temporary blocks in some instances that will prevent the upgrade from completing installation. - -If a CYOD user purchases a Sun Valley device, can I move them back to Windows 10 and how? Downgrade rights are available with Windows SV Pro OEM licensed devices. You can downgrade to any version of Windows Pro/Professional that has not reached its end of support date. You will need to reimage or clean install a Windows SV device to downgrade it to Windows 10. Downgrade rights are also available through Microsoft Volume Licensing (check your agreement for more details). - -If I’m upgrading from Windows 10 to Sun Valley can I change editions at that time (e.g., from Home or Education to Pro)? No, you will need to change editions separately (before or after upgrading). Applicable fees may apply to acquire the license for the new edition - -Commercial version -If you have Windows 10 Pro, you’ll upgrade to Windows Oct2021 Pro. You can then step up to Windows Oct2021 Enterprise. If you have Windows 10 Home, you’ll upgrade to Windows Oct2021 Home. You can then step up to Windows 10 Pro. - -## Requirements - -The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. - -You can use the PC Health Check app to determine if your PC can upgrade. The PC Health Check is available for download . [this will eventually need to change to a message about WU – Aug 2021 timeframe] - -Can Enterprise customers get the upgrade? Enterprise customers are eligible per the terms of their current licensing agreement - -What about Windows RT? Windows RT is not eligible for upgrade. - -Any device that meets the minimum specification can upgrade run Windows SV. However, Windows 7 devices will likely not meet the minimum specification because of age and generation of the processor that was included with that device. Please see below for the full CPU list available through our Windows SV specifications page to see which ones are compatible for upgrade. If a customer with a Windows 7 PC that meets the minimum spec wants to upgrade, they would need to purchase a Windows 10 license, perform a clean install, and proceed with the upgrade to Windows SV. In 2022, they will also have the option to purchase Windows SV at retail and install it on the compatible Windows 7 device. - -The minimum storage drive requirement is 64GB for Windows SV. Ongoing requirements for feature and quality updates will vary, but are generally expected to be similar to what we see today for Windows 10 - - -Commercial -To see if your PC is eligible, download the PC Health Check app (link). Once the upgrade rollout has started, you can check the status of your device by navigating to Windows Update in settings. - -## Managing Windows Sun Valley +For more information, see [Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy). +## Manage Windows Sun Valley With Windows 10, Microsoft forced me to make significant changes to my IT processes, management approach and tooling, what will this new version require me to change? Windows SV is based on the same foundation of Windows 10, so it will support the same management tools that you use today with Windows 10. ## Hardware compatibility -Most software and accessories that worked with Windows 10 areis expected to work with Windows SV. Check with your software publisher or accessory manufacturer for specific details on your products. +Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. -Commercial version -Most software and accessories that worked with Windows 10 are expected to work with Windows Oct21. Check with your software publisher or accessory manufacturer for specific details on your products. +## Application compatibility -Most software and accessories that worked with Windows 10 is expected to work with Windows SV. Check with your software publisher or accessory manufacturer for specific details on your products. +Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have App Assure, Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [article link here]. -Most software and accessories that worked with Windows 10 is expected to work with Windows SV. Check with your software publisher or accessory manufacturer for specific details on your products and to see if an upgrade of your security solution is required for WIndowsWindows SV. +## Windows Sun Valley features and applications -Commercial version -Most software and accessories that worked with Windows 10 are expected to work with Windows Oct21. Check with your software publisher or accessory manufacturer for specific details on your products. - -## App management in Windows Sun Valley - -Commercial version (specific to apps) -Yes, Microsoft is committed to ensuring your applications work on the latest versions of our software and Windows Oct21 has been built with compatibility in mind. Our promise states that apps that worked on Windows 7/8.1/10 will work on Windows Oct21. If you have App Assure, Microsoft will help you fix them at no cost. - -App Assure is a service that helps customers remediate application issues that they may experience when deploying the latest version of our software. - -App Assure is available at no additional cost for eligible customers with 150+ seats. For more information on eligibility requirements, please navigate to this page - -Visit the App Assure page and sign in to submit your request for assistance for a dedicated App Assure Manager. If you experience any issues submitting a request for assistance, please contact ACHELP@microsoft.com and our team members will reach out to you to help! - -Yes, most apps and devices that worked with Windows 10 will be compatible with Sun Valley. You can also check with your software publisher manufacturer for more detailed information. +Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. ## Licensing -Will I get Sun Valley as part of my Microsoft 365 license? -Microsoft 365 licenses that include Windows licenses will allow you to run Sun Valley on supported devices. - - -If I have a volume license, will it equally cover Sun Valley and Windows 10 devices both before and after upgrade? Yes - -## Applications - -Will Safeguard holds still function for SV and how will that work between the two different OS versions? Yes. IT Administrators will have access to safeguard hold information using Update Compliance. More information can be found here. - -What’s going to happen with kiosk mode? Commercial version -Windows Oct2021 is committed to support all of the commercial scenarios that we supported in Windows 10, which includes kiosk mode. In this initial Windows Oct2021 release, we are supporting single app kiosk mode. In the future, we plan to support multi-app kiosk mode. - -Will Known Issue Rollback (KIR) function on SV? Yes, the known issue rollback will function on SV. - -What’s not in Sun Valley that’s in Windows 10? (link to Aaron Grady deck). This is also published on the Windows specifications page and there will be a docs/technet article that will be published, too - - ----------------------------------------- - - - - +There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. +Microsoft 365 licenses that include Windows licenses will permit you to run Windows Sun Valley on supported devices. +If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index fffaec9814..2866b8c09a 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -18,5 +18,29 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley requirements +This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley can also be run on Virtual Machines (VMs). + +## Software requirements + The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. +## Hardware requirements + +The following processor and hardware requirements are necessary to support Windows Sun Valley: + +Processor +- Intel 8th generation, Intel Celeron N4000, Pentium N5000 +- AMD Ryzen gen 2 (Zen+), AMD 3xxx +- Qualcomm 7c, 8c, 8cx +- 64bit architecture +- 1Ghz clock speed +- 2 cores + +Hardware +- 64GB drive +- 4GB RAM +- UEFI, Secure Boot capable & TPM 2.0 +- >9” with HD Resolution (1366x768 equivalent) +- DirectX 12 compatible graphics / WDDM 2.x +- Connectivity required (Home Edition) + From bb27dd991180afa4066a9ba4f87d495a0e0ca9f0 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:12:47 -0700 Subject: [PATCH 032/104] 3 articles drafted --- windows/deployment/windows-sv-deploy.md | 4 +- windows/whats-new/windows-sv-get-started.md | 15 ++++++++ windows/whats-new/windows-sv-overview.md | 42 ++++++++------------- 3 files changed, 32 insertions(+), 29 deletions(-) diff --git a/windows/deployment/windows-sv-deploy.md b/windows/deployment/windows-sv-deploy.md index 033c8308fa..fe50501d35 100644 --- a/windows/deployment/windows-sv-deploy.md +++ b/windows/deployment/windows-sv-deploy.md @@ -20,7 +20,7 @@ ms.topic: article **Applies to** - Windows Sun Valley -## +## Windows Sun Valley deployment considerations + -To successfully deploy the Windows Sun Valley operating system in your organization, ... diff --git a/windows/whats-new/windows-sv-get-started.md b/windows/whats-new/windows-sv-get-started.md index 3bcdd4f4e0..9e588a9e10 100644 --- a/windows/whats-new/windows-sv-get-started.md +++ b/windows/whats-new/windows-sv-get-started.md @@ -19,3 +19,18 @@ ms.topic: article **Applies to** - Windows Sun Valley + +## Windows Sun Valley deployment planning + +Consider using the following process to deploy Windows Sun Valley to existing devices: +1. Preview Windows Sun Valley and create a deployment plan. +2. Test critical applications and management policies. +3. Update devices to the latest release of Windows 10. +4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. +5. Update deployment tools and infrastructure. +6. Update qualifying devices to Windows Sun Valley. + + +## See also + +[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy). diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index 44ce28569a..a68ec2aa11 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -21,11 +21,7 @@ ms.custom: seo-marvel-apr2020 **Applies to** - Windows Sun Valley -This article provides an introduction to Windows Sun Valley, the next client release of Windows. - -## What is Windows Sun Valley? - -Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. +This article provides an introduction to Windows Sun Valley, the next client release of Windows. Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. ## How to get Windows Sun Valley @@ -39,10 +35,14 @@ You can get early access to test Windows Sun Valley by joining the Windows Insid ## Windows Sun Valley lifecycle +### Updates + Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. +### Servicing + Windows Sun Valley annual releases are supported for 24 months for the following editions: - Home - Pro @@ -51,32 +51,20 @@ Windows Sun Valley annual releases are supported for 24 months for the following Windows Sun Valley annual releases are supported for 36 months for the following editions: - Enterprise -- Education editions +- Education + +### Feature and application lifecycle + +Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. ## Windows 10 lifecycle Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. Windows 10 will be supported with security updates until October 2025. -## OS management in a mixed environment +## Management and tools Windows Sun Valley is based on the same foundation as Windows 10. You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products. -## Deploy Windows Sun Valley - -Consider using the following process to deploy Windows Sun Valley to existing devices: -1. Preview Windows Sun Valley and create a deployment plan. -2. Test critical applications and management policies. -3. Update devices to the latest release of Windows 10. -4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. -5. Update deployment tools and infrastructure. -6. Update qualifying devices to Windows Sun Valley. - -For more information, see [Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy). - -## Manage Windows Sun Valley - -With Windows 10, Microsoft forced me to make significant changes to my IT processes, management approach and tooling, what will this new version require me to change? Windows SV is based on the same foundation of Windows 10, so it will support the same management tools that you use today with Windows 10. - ## Hardware compatibility Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. @@ -85,10 +73,6 @@ Most accessories and associated software that worked with Windows 10 are expecte Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have App Assure, Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [article link here]. -## Windows Sun Valley features and applications - -Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. - ## Licensing There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. @@ -96,3 +80,7 @@ There are no unique licensing requirements for Windows Sun Valley beyond what is Microsoft 365 licenses that include Windows licenses will permit you to run Windows Sun Valley on supported devices. If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. + +## See also + +[Get started with Windows Sun Valley](windows-sv-get-started.md) From 5d5bad186fb63d9b10c6eab447f7cf149bd34dcc Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:17:51 -0700 Subject: [PATCH 033/104] fix some other articles --- windows/deployment/windows-sv-plan.md | 259 +--------------------- windows/deployment/windows-sv-prepare.md | 260 +---------------------- windows/sv/index.yml | 2 +- 3 files changed, 10 insertions(+), 511 deletions(-) diff --git a/windows/deployment/windows-sv-plan.md b/windows/deployment/windows-sv-plan.md index e3b81e8c3c..7244da875c 100644 --- a/windows/deployment/windows-sv-plan.md +++ b/windows/deployment/windows-sv-plan.md @@ -1,6 +1,6 @@ --- -title: Windows 11 deployment planning -description: Understand the different ways Windows 11 operating system can be deployed in your organization. Explore several Windows 11 deployment scenarios. +title: Windows Sun Valley deployment planning +description: Understand the different ways Windows Sun Valley operating system can be deployed in your organization. Explore several Windows Sun Valley deployment scenarios. ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 ms.reviewer: manager: laurawi @@ -19,257 +19,8 @@ ms.topic: article # Windows 11 deployment planning **Applies to** -- Windows 11 +- Windows Sun Valley -To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. +To successfully deploy the Windows Sun Valley operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. -The following table summarizes various Windows 10 deployment scenarios. The scenarios are each assigned to one of three categories. -- Modern deployment methods are recommended unless you have a specific need to use a different procedure. These methods are supported with existing tools such as Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. These methods are discussed in detail on the [Modern Desktop Deployment Center](/microsoft-365/enterprise/desktop-deployment-center-home). - - Note: Once you have deployed Windows 10 in your organization, it is important to stay up to date by [creating a deployment plan](update/create-deployment-plan.md) for Windows 10 feature updates. -- Dynamic deployment methods enable you to configure applications and settings for specific use cases. -- Traditional deployment methods use existing tools to deploy operating system images.
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CategoryScenarioDescriptionMore information
Modern - -[Windows Autopilot](#windows-autopilot) - Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. - -Overview of Windows Autopilot -
- -[In-place upgrade](#in-place-upgrade) - - - Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. - -Perform an in-place upgrade to Windows 10 with MDT
Perform an in-place upgrade to Windows 10 using Configuration Manager -
- Dynamic - - -[Subscription Activation](#windows-10-subscription-activation) - - Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. - -Windows 10 Subscription Activation -
- - [AAD / MDM](#dynamic-provisioning) - - The device is automatically joined to AAD and configured by MDM. - -Azure Active Directory integration with MDM -
- - [Provisioning packages](#dynamic-provisioning) - - Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. - -Configure devices without MDM -
- Traditional - - - [Bare metal](#new-computer) - - Deploy a new device, or wipe an existing device and deploy with a fresh image. - - Deploy a Windows 10 image using MDT
Deploy Windows 10 using PXE and Configuration Manager -
- - [Refresh](#computer-refresh) - - Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. - - Refresh a Windows 7 computer with Windows 10
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager -
- - [Replace](#computer-replace) - - Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. - - Replace a Windows 7 computer with a Windows 10 computer
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager -
- -
  - - ->[!IMPORTANT] ->The Windows Autopilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later.
->Except for clean install scenarios such as traditional bare metal and Windows Autopilot, all the methods described can optionally migrate apps and settings to the new OS. - -## Modern deployment methods - -Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. - -### Windows Autopilot - -Windows Autopilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows Autopilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. - -For more information about Windows Autopilot, see [Overview of Windows Autopilot](/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows Autopilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). - -### In-place upgrade - -For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. - -Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like Microsoft Endpoint Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences. - -The in-place upgrade process is designed to be extremely reliable, with the ability to automatically roll back to the previous operating system if any issues are encountered during the deployment process, without any IT staff involvement. Rolling back manually can also be done by leveraging the automatically-created recovery information (stored in the Windows.old folder), in case any issues are encountered after the upgrade is finished. The upgrade process is also typically faster than traditional deployments, because applications do not need to be reinstalled as part of the process. - -Because existing applications are preserved through the process, the upgrade process uses the standard Windows installation media image (Install.wim); custom images are not needed and cannot be used because the upgrade process is unable to deal with conflicts between apps in the old and new operating system. (For example, Contoso Timecard 1.0 in Windows 7 and Contoso Timecard 3.0 in the Windows 10 image.) - -Scenarios that support in-place upgrade with some additional procedures include changing from BIOS to UEFI boot mode and upgrade of devices that use non-Microsoft disk encryption software. - -- **Legacy BIOS to UEFI booting**: To perform an in-place upgrade on a UEFI-capable system that currently boots using legacy BIOS, first perform the in-place upgrade to Windows 10, maintaining the legacy BIOS boot mode. Windows 10 does not require UEFI, so it will work fine to upgrade a system using legacy BIOS emulation. After the upgrade, if you wish to enable Windows 10 features that require UEFI (such as Secure Boot), you can convert the system disk to a format that supports UEFI boot using the [MBR2GPT](./mbr-to-gpt.md) tool. Note: [UEFI specification](http://www.uefi.org/specifications) requires GPT disk layout. After the disk has been converted, you must also configure the firmware to boot in UEFI mode. - -- **Non-Microsoft disk encryption software**: While devices encrypted with BitLocker can easily be upgraded, more work is necessary for non-Microsoft disk encryption tools. Some ISVs will provide instructions on how to integrate their software into the in-place upgrade process. Check with your ISV to see if they have instructions. The following articles provide details on how to provision encryption drivers for use during Windows Setup via the ReflectDrivers setting: - - [Windows Setup Automation Overview](/windows-hardware/manufacture/desktop/windows-setup-automation-overview) - - [Windows Setup Command-Line Options](/windows-hardware/manufacture/desktop/windows-setup-command-line-options) - -There are some situations where you cannot use in-place upgrade; in these situations, you can use traditional deployment (wipe-and-load) instead. Examples of these situations include: - -- Changing from Windows 7, Windows 8, or Windows 8.1 x86 to Windows 10 x64. The upgrade process cannot change from a 32-bit operating system to a 64-bit operating system, because of possible complications with installed applications and drivers. -- Windows To Go and Boot from VHD installations. The upgrade process is unable to upgrade these installations. Instead, new installations would need to be performed. -- Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. -- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. - - -## Dynamic provisioning - -For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. - -The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: - -### Windows 10 Subscription Activation - -Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-enterprise-subscription-activation). - - -### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment - -In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](/windows/client-management/mdm/azure-active-directory-integration-with-mdm). - -### Provisioning package configuration - -Using the [Windows Imaging and Configuration Designer (ICD)](/windows/configuration/provisioning-packages/provisioning-install-icd), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). - -These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). - -While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. - -## Traditional deployment: - -New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md), and [Microsoft Endpoint Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). - -With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them. - -The traditional deployment scenario can be divided into different sub-scenarios. These are explained in detail in the following sections, but the following provides a brief summary: - -- **New computer.** A bare-metal deployment of a new machine. -- **Computer refresh.** A reinstall of the same machine (with user-state migration and an optional full Windows Imaging (WIM) image backup). -- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). - -### New computer - -Also called a "bare metal" deployment. This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). - -The deployment process for the new machine scenario is as follows: - -1. Start the setup from boot media (CD, USB, ISO, or PXE). - -2. Wipe the hard disk clean and create new volume(s). - -3. Install the operating system image. - -4. Install other applications (as part of the task sequence). - -After taking these steps, the computer is ready for use. - -### Computer refresh - -A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. - -The deployment process for the wipe-and-load scenario is as follows: - -1. Start the setup on a running operating system. - -2. Save the user state locally. - -3. Wipe the hard disk clean (except for the folder containing the backup). - -4. Install the operating system image. - -5. Install other applications. - -6. Restore the user state. - -After taking these steps, the machine is ready for use. - -### Computer replace - -A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. - -The deployment process for the replace scenario is as follows: - -1. Save the user state (data and settings) on the server through a backup job on the running operating system. - -2. Deploy the new computer as a bare-metal deployment. - - **Note**
In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. - -## Related topics - -- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) -- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) -- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) -- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md) -- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference) -- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) -- [UEFI firmware](/windows-hardware/design/device-experiences/oem-uefi) \ No newline at end of file +The following table summarizes various Windows Sun Valley deployment scenarios. The scenarios are each assigned to one of three categories. \ No newline at end of file diff --git a/windows/deployment/windows-sv-prepare.md b/windows/deployment/windows-sv-prepare.md index eb8ce64aa0..2a0b778723 100644 --- a/windows/deployment/windows-sv-prepare.md +++ b/windows/deployment/windows-sv-prepare.md @@ -1,7 +1,6 @@ --- -title: Prepare to deploy Windows 11 -description: Understand the different ways Windows 11 operating system can be deployed in your organization. Explore several Windows 11 deployment scenarios. -ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 +title: Prepare to deploy Windows Sun Valley +description: Understand the different ways Windows Sun Valley operating system can be deployed in your organization. Explore several Windows Sun Valley deployment scenarios. ms.reviewer: manager: laurawi ms.audience: itpro @@ -19,257 +18,6 @@ ms.topic: article # Prepare to deploy Windows 11 **Applies to** -- Windows 11, version 21H1 +- Windows Sun Valley -To successfully deploy the Windows 10 operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. - -The following table summarizes various Windows 10 deployment scenarios. The scenarios are each assigned to one of three categories. -- Modern deployment methods are recommended unless you have a specific need to use a different procedure. These methods are supported with existing tools such as Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. These methods are discussed in detail on the [Modern Desktop Deployment Center](/microsoft-365/enterprise/desktop-deployment-center-home). - - Note: Once you have deployed Windows 10 in your organization, it is important to stay up to date by [creating a deployment plan](update/create-deployment-plan.md) for Windows 10 feature updates. -- Dynamic deployment methods enable you to configure applications and settings for specific use cases. -- Traditional deployment methods use existing tools to deploy operating system images.
  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CategoryScenarioDescriptionMore information
Modern - -[Windows Autopilot](#windows-autopilot) - Customize the out-of-box-experience (OOBE) for your organization, and deploy a new system with apps and settings already configured. - -Overview of Windows Autopilot -
- -[In-place upgrade](#in-place-upgrade) - - - Use Windows Setup to update your OS and migrate apps and settings. Rollback data is saved in Windows.old. - -Perform an in-place upgrade to Windows 10 with MDT
Perform an in-place upgrade to Windows 10 using Configuration Manager -
- Dynamic - - -[Subscription Activation](#windows-10-subscription-activation) - - Switch from Windows 10 Pro to Enterprise when a subscribed user signs in. - -Windows 10 Subscription Activation -
- - [AAD / MDM](#dynamic-provisioning) - - The device is automatically joined to AAD and configured by MDM. - -Azure Active Directory integration with MDM -
- - [Provisioning packages](#dynamic-provisioning) - - Using the Windows Imaging and Configuration Designer tool, create provisioning packages that can be applied to devices. - -Configure devices without MDM -
- Traditional - - - [Bare metal](#new-computer) - - Deploy a new device, or wipe an existing device and deploy with a fresh image. - - Deploy a Windows 10 image using MDT
Deploy Windows 10 using PXE and Configuration Manager -
- - [Refresh](#computer-refresh) - - Also called wipe and load. Redeploy a device by saving the user state, wiping the disk, then restoring the user state. - - Refresh a Windows 7 computer with Windows 10
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager -
- - [Replace](#computer-replace) - - Replace an existing device with a new one by saving the user state on the old device and then restoring it to the new device. - - Replace a Windows 7 computer with a Windows 10 computer
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager -
- -
  - - ->[!IMPORTANT] ->The Windows Autopilot and Subscription Activation scenarios require that the beginning OS be Windows 10 version 1703, or later.
->Except for clean install scenarios such as traditional bare metal and Windows Autopilot, all the methods described can optionally migrate apps and settings to the new OS. - -## Modern deployment methods - -Modern deployment methods embrace both traditional on-prem and cloud services to deliver a simple, streamlined, cost effective deployment experience. - -### Windows Autopilot - -Windows Autopilot is a new suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs. Windows Autopilot enables IT professionals to customize the Out of Box Experience (OOBE) for Windows 10 PCs and provide end users with a fully configured new Windows 10 device after just a few clicks. There are no images to deploy, no drivers to inject, and no infrastructure to manage. Users can go through the deployment process independently, without the need consult their IT administrator. - -For more information about Windows Autopilot, see [Overview of Windows Autopilot](/windows/deployment/windows-10-auto-pilot) and [Modernizing Windows deployment with Windows Autopilot](https://blogs.technet.microsoft.com/windowsitpro/2017/06/29/modernizing-windows-deployment-with-windows-autopilot/). - -### In-place upgrade - -For existing computers running Windows 7, Windows 8, or Windows 8.1, the recommended path for organizations deploying Windows 10 leverages the Windows installation program (Setup.exe) to perform an in-place upgrade, which automatically preserves all data, settings, applications, and drivers from the existing operating system version. This requires the least IT effort, because there is no need for any complex deployment infrastructure. - -Although consumer PCs will be upgraded using Windows Update, organizations want more control over the process. This is accomplished by leveraging tools like Microsoft Endpoint Manager or the Microsoft Deployment Toolkit to completely automate the upgrade process through simple task sequences. - -The in-place upgrade process is designed to be extremely reliable, with the ability to automatically roll back to the previous operating system if any issues are encountered during the deployment process, without any IT staff involvement. Rolling back manually can also be done by leveraging the automatically-created recovery information (stored in the Windows.old folder), in case any issues are encountered after the upgrade is finished. The upgrade process is also typically faster than traditional deployments, because applications do not need to be reinstalled as part of the process. - -Because existing applications are preserved through the process, the upgrade process uses the standard Windows installation media image (Install.wim); custom images are not needed and cannot be used because the upgrade process is unable to deal with conflicts between apps in the old and new operating system. (For example, Contoso Timecard 1.0 in Windows 7 and Contoso Timecard 3.0 in the Windows 10 image.) - -Scenarios that support in-place upgrade with some additional procedures include changing from BIOS to UEFI boot mode and upgrade of devices that use non-Microsoft disk encryption software. - -- **Legacy BIOS to UEFI booting**: To perform an in-place upgrade on a UEFI-capable system that currently boots using legacy BIOS, first perform the in-place upgrade to Windows 10, maintaining the legacy BIOS boot mode. Windows 10 does not require UEFI, so it will work fine to upgrade a system using legacy BIOS emulation. After the upgrade, if you wish to enable Windows 10 features that require UEFI (such as Secure Boot), you can convert the system disk to a format that supports UEFI boot using the [MBR2GPT](./mbr-to-gpt.md) tool. Note: [UEFI specification](http://www.uefi.org/specifications) requires GPT disk layout. After the disk has been converted, you must also configure the firmware to boot in UEFI mode. - -- **Non-Microsoft disk encryption software**: While devices encrypted with BitLocker can easily be upgraded, more work is necessary for non-Microsoft disk encryption tools. Some ISVs will provide instructions on how to integrate their software into the in-place upgrade process. Check with your ISV to see if they have instructions. The following articles provide details on how to provision encryption drivers for use during Windows Setup via the ReflectDrivers setting: - - [Windows Setup Automation Overview](/windows-hardware/manufacture/desktop/windows-setup-automation-overview) - - [Windows Setup Command-Line Options](/windows-hardware/manufacture/desktop/windows-setup-command-line-options) - -There are some situations where you cannot use in-place upgrade; in these situations, you can use traditional deployment (wipe-and-load) instead. Examples of these situations include: - -- Changing from Windows 7, Windows 8, or Windows 8.1 x86 to Windows 10 x64. The upgrade process cannot change from a 32-bit operating system to a 64-bit operating system, because of possible complications with installed applications and drivers. -- Windows To Go and Boot from VHD installations. The upgrade process is unable to upgrade these installations. Instead, new installations would need to be performed. -- Updating existing images. While it might be tempting to try to upgrade existing Windows 7, Windows 8, or Windows 8.1 images to Windows 10 by installing the old image, upgrading it, and then recapturing the new Windows 10 image, this is not supported – preparing an upgraded OS for imaging (using Sysprep.exe) is not supported and will not work when it detects the upgraded OS. -- Dual-boot and multi-boot systems. The upgrade process is designed for devices running a single OS; if using dual-boot or multi-boot systems with multiple operating systems (not leveraging virtual machines for the second and subsequent operating systems), additional care should be taken. - - -## Dynamic provisioning - -For new PCs, organizations have historically replaced the version of Windows included on the device with their own custom Windows image, because this was often faster and easier than leveraging the preinstalled version. But this is an added expense due to the time and effort required. With the new dynamic provisioning capabilities and tools provided with Windows 10, it is now possible to avoid this. - -The goal of dynamic provisioning is to take a new PC out of the box, turn it on, and transform it into a productive organization device, with minimal time and effort. The types of transformations that are available include: - -### Windows 10 Subscription Activation - -Windows 10 Subscription Activation is a modern deployment method that enables you to change the SKU from Pro to Enterprise with no keys and no reboots. For more information about Subscription Activation, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-enterprise-subscription-activation). - - -### Azure Active Directory (AAD) join with automatic mobile device management (MDM) enrollment - -In this scenario, the organization member just needs to provide their work or school user ID and password; the device can then be automatically joined to Azure Active Directory and enrolled in a mobile device management (MDM) solution with no additional user interaction. Once done, the MDM solution can finish configuring the device as needed. For more information, see [Azure Active Directory integration with MDM](/windows/client-management/mdm/azure-active-directory-integration-with-mdm). - -### Provisioning package configuration - -Using the [Windows Imaging and Configuration Designer (ICD)](/windows/configuration/provisioning-packages/provisioning-install-icd), IT administrators can create a self-contained package that contains all of the configuration, settings, and apps that need to be applied to a machine. These packages can then be deployed to new PCs through a variety of means, typically by IT professionals. For more information, see [Configure devices without MDM](/windows/configuration/configure-devices-without-mdm). - -These scenarios can be used to enable “choose your own device” (CYOD) programs where the organization’s users can pick their own PC and not be restricted to a small list of approved or certified models (programs that are difficult to implement using traditional deployment scenarios). - -While the initial Windows 10 release includes a variety of provisioning settings and deployment mechanisms, these will continue to be enhanced and extended based on feedback from organizations. As with all Windows features, organizations can submit suggestions for additional features through the Windows Feedback app or through their Microsoft Support contacts. - -## Traditional deployment: - -New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the [Windows Assessment and Deployment Kit](windows-adk-scenarios-for-it-pros.md), Windows Deployment Services, the [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md), and [Microsoft Endpoint Configuration Manager](deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). - -With the release of Windows 10, all of these tools are being updated to fully support Windows 10. Although newer scenarios such as in-place upgrade and dynamic provisioning may reduce the need for traditional deployment capabilities in some organizations, these traditional methods remain important and will continue to be available to organizations that need them. - -The traditional deployment scenario can be divided into different sub-scenarios. These are explained in detail in the following sections, but the following provides a brief summary: - -- **New computer.** A bare-metal deployment of a new machine. -- **Computer refresh.** A reinstall of the same machine (with user-state migration and an optional full Windows Imaging (WIM) image backup). -- **Computer replace.** A replacement of the old machine with a new machine (with user-state migration and an optional full WIM image backup). - -### New computer - -Also called a "bare metal" deployment. This scenario occurs when you have a blank machine you need to deploy, or an existing machine you want to wipe and redeploy without needing to preserve any existing data. The setup starts from a boot media, using CD, USB, ISO, or Pre-Boot Execution Environment (PXE). You can also generate a full offline media that includes all the files needed for a client deployment, allowing you to deploy without having to connect to a central deployment share. The target can be a physical computer, a virtual machine, or a Virtual Hard Disk (VHD) running on a physical computer (boot from VHD). - -The deployment process for the new machine scenario is as follows: - -1. Start the setup from boot media (CD, USB, ISO, or PXE). - -2. Wipe the hard disk clean and create new volume(s). - -3. Install the operating system image. - -4. Install other applications (as part of the task sequence). - -After taking these steps, the computer is ready for use. - -### Computer refresh - -A refresh is sometimes called wipe-and-load. The process is normally initiated in the running operating system. User data and settings are backed up and restored later as part of the deployment process. The target can be the same as for the new computer scenario. - -The deployment process for the wipe-and-load scenario is as follows: - -1. Start the setup on a running operating system. - -2. Save the user state locally. - -3. Wipe the hard disk clean (except for the folder containing the backup). - -4. Install the operating system image. - -5. Install other applications. - -6. Restore the user state. - -After taking these steps, the machine is ready for use. - -### Computer replace - -A computer replace is similar to the refresh scenario. However, since we are replacing the machine, we divide this scenario into two main tasks: backup of the old client and bare-metal deployment of the new client. As with the refresh scenario, user data and settings are backed up and restored. - -The deployment process for the replace scenario is as follows: - -1. Save the user state (data and settings) on the server through a backup job on the running operating system. - -2. Deploy the new computer as a bare-metal deployment. - - **Note**
In some situations, you can use the replace scenario even if the target is the same machine. For example, you can use replace if you want to modify the disk layout from the master boot record (MBR) to the GUID partition table (GPT), which will allow you to take advantage of the Unified Extensible Firmware Interface (UEFI) functionality. You can also use replace if the disk needs to be repartitioned since user data needs to be transferred off the disk. - -## Related topics - -- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md) -- [Upgrade to Windows 10 with Microsoft Endpoint Configuration Manager](./deploy-windows-cm/upgrade-to-windows-10-with-configuraton-manager.md) -- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=620230) -- [Deploy Windows 10 with the Microsoft Deployment Toolkit](./deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md) -- [Windows setup technical reference](/windows-hardware/manufacture/desktop/windows-setup-technical-reference) -- [Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) -- [UEFI firmware](/windows-hardware/design/device-experiences/oem-uefi) \ No newline at end of file +To successfully deploy \ No newline at end of file diff --git a/windows/sv/index.yml b/windows/sv/index.yml index 9ce50839f3..6f30d77869 100644 --- a/windows/sv/index.yml +++ b/windows/sv/index.yml @@ -1,6 +1,6 @@ ### YamlMime:Landing -title: Windows SV # < 60 chars +title: Windows Sun Valley # < 60 chars summary: Find out about Windows Windows Sun Valley. # < 160 chars metadata: From 5a8e04486522015bb3919bc04d51519effce493b Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:20:37 -0700 Subject: [PATCH 034/104] index card link --- windows/whats-new/index.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index e1c75debe3..433ee55b6f 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -28,7 +28,7 @@ landingContent: - linkListType: overview links: - text: Windows Sun Valley Overview - url: windows-sv-overview.md + url: windows-sv-overview - text: Windows Sun Valley requirements url: windows-sv-requirements.md - text: Get started with Windows Sun Valley From 7c9f075f2169c75364129b37cbbc815f8e3f2936 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:22:25 -0700 Subject: [PATCH 035/104] index card link!! --- windows/hub/index.yml | 6 +++--- windows/whats-new/index.yml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 14991296ce..748310bd3c 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -27,11 +27,11 @@ landingContent: - linkListType: overview links: - text: Windows Sun Valley overview - url: /windows/whats-new/windows-sv-overview.md + url: /windows/whats-new/windows-sv-overview - text: Windows Sun Valley requirements - url: /windows/whats-new/windows-sv-requirements.md + url: /windows/whats-new/windows-sv-requirements - text: Get started with Windows Sun Valley - url: /windows/whats-new/get-started-windows-sv.md + url: /windows/whats-new/get-started-windows-sv - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: Windows release information diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index 433ee55b6f..e1c75debe3 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -28,7 +28,7 @@ landingContent: - linkListType: overview links: - text: Windows Sun Valley Overview - url: windows-sv-overview + url: windows-sv-overview.md - text: Windows Sun Valley requirements url: windows-sv-requirements.md - text: Get started with Windows Sun Valley From e3ef8dc6ad5d4d5e033c9242cd2bb08184b028e4 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:32:22 -0700 Subject: [PATCH 036/104] add some links --- windows/whats-new/windows-sv-overview.md | 12 ++++++++---- windows/whats-new/windows-sv-requirements.md | 11 +++++++---- 2 files changed, 15 insertions(+), 8 deletions(-) diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index a68ec2aa11..343ad3490b 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -21,11 +21,13 @@ ms.custom: seo-marvel-apr2020 **Applies to** - Windows Sun Valley -This article provides an introduction to Windows Sun Valley, the next client release of Windows. Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. +This article provides an introduction to Windows Sun Valley, the next client release of Windows. + +Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. ## How to get Windows Sun Valley -Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. It will also be available on new devices that meet the hardware requirements. +Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. Windows Sun Valley will also be available on new devices that meet the hardware requirements. You must be running the most current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). @@ -59,7 +61,9 @@ Most features and applications that are included with Windows 10 will be availab ## Windows 10 lifecycle -Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. Windows 10 will be supported with security updates until October 2025. +Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. + +Windows 10 will be supported with security updates until October 2025. ## Management and tools @@ -71,7 +75,7 @@ Most accessories and associated software that worked with Windows 10 are expecte ## Application compatibility -Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have App Assure, Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [article link here]. +Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have [App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure), Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [Products and Capabilities: App Assure](https://docs.microsoft.com/fasttrack/products-and-capabilities#app-assure). ## Licensing diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 2866b8c09a..949af445bb 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -26,7 +26,7 @@ The upgrade to Sun Valley is available for devices running Windows 10, version 2 ## Hardware requirements -The following processor and hardware requirements are necessary to support Windows Sun Valley: +To install Windows Sun Valley, devices must meet the following specifications: Processor - Intel 8th generation, Intel Celeron N4000, Pentium N5000 @@ -40,7 +40,10 @@ Hardware - 64GB drive - 4GB RAM - UEFI, Secure Boot capable & TPM 2.0 -- >9” with HD Resolution (1366x768 equivalent) -- DirectX 12 compatible graphics / WDDM 2.x -- Connectivity required (Home Edition) +- Monitor 9” or more, with HD Resolution +- DirectX 12 compatible graphics / WDDM 2.x + +## Network requirements + +Internet connectivity is required for the Home Edition From 65a9b57f0065ba9fc73380b5467a0d07faecfafa Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:35:02 -0700 Subject: [PATCH 037/104] rm --- windows/deployment/TOC.yml | 8 ++++---- windows/whats-new/windows-sv-get-started.md | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 0e2693fd62..b66af87886 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -5,7 +5,7 @@ items: - name: What's new href: deploy-whats-new.md - - name: Windows 11 deployment overview + - name: Windows Sun Valley deployment overview href: windows-sv-deploy.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md @@ -35,7 +35,7 @@ - name: Plan items: - - name: Windows 11 deployment planning + - name: Windows Sun Valley deployment planning href: windows-sv-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md @@ -71,7 +71,7 @@ - name: Prepare items: - - name: Prepare to deploy Windows 11 + - name: Prepare to deploy Windows Sun Valley href: windows-sv-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md @@ -104,7 +104,7 @@ items: - name: Deploy Windows client items: - - name: Windows 11 deployment overview + - name: Windows Sun Valley deployment overview href: windows-sv-deploy.md - name: Deploy Windows client with Autopilot href: windows-autopilot/index.yml diff --git a/windows/whats-new/windows-sv-get-started.md b/windows/whats-new/windows-sv-get-started.md index 9e588a9e10..25b0d9e99c 100644 --- a/windows/whats-new/windows-sv-get-started.md +++ b/windows/whats-new/windows-sv-get-started.md @@ -20,7 +20,7 @@ ms.topic: article - Windows Sun Valley -## Windows Sun Valley deployment planning +## Deployment planning Consider using the following process to deploy Windows Sun Valley to existing devices: 1. Preview Windows Sun Valley and create a deployment plan. @@ -33,4 +33,4 @@ Consider using the following process to deploy Windows Sun Valley to existing de ## See also -[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy). +[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy) From 9d3e667196a2eea54f4acefec1387213fc026841 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:38:13 -0700 Subject: [PATCH 038/104] see also --- windows/whats-new/windows-sv-requirements.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 949af445bb..ddb8bf84c1 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -40,10 +40,14 @@ Hardware - 64GB drive - 4GB RAM - UEFI, Secure Boot capable & TPM 2.0 -- Monitor 9” or more, with HD Resolution +- Monitor size 9” or more with HD Resolution - DirectX 12 compatible graphics / WDDM 2.x ## Network requirements Internet connectivity is required for the Home Edition +## See also + +[Windows Sun Valley overview](windows-sv-overview.md) + From 215a7783a66347e67e59dc7668edb611c55052b4 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:40:55 -0700 Subject: [PATCH 039/104] small edits --- windows/whats-new/windows-sv-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index 343ad3490b..dc48dc8b7b 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -21,7 +21,7 @@ ms.custom: seo-marvel-apr2020 **Applies to** - Windows Sun Valley -This article provides an introduction to Windows Sun Valley, the next client release of Windows. +This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. @@ -55,7 +55,7 @@ Windows Sun Valley annual releases are supported for 36 months for the following - Enterprise - Education -### Feature and application lifecycle +### Features and applications Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. From 01c3844cb17028a84cf6f09b467f129a3168cdf5 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:49:45 -0700 Subject: [PATCH 040/104] add rollback --- windows/whats-new/windows-sv-overview.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv-overview.md index dc48dc8b7b..2407048dbc 100644 --- a/windows/whats-new/windows-sv-overview.md +++ b/windows/whats-new/windows-sv-overview.md @@ -29,11 +29,11 @@ Windows Sun Valley is a newly designed Windows client operating system due to be Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. Windows Sun Valley will also be available on new devices that meet the hardware requirements. -You must be running the most current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). +You must be running a current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). -Not all eligible Windows 10 PCs will be offered theo upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to Windows Update in settings. Once the upgrade rollout has started and the upgrade has been tested and validated for your specific PC hardware, Windows Update will indicate that the upgrade is ready for installation. +Not all eligible Windows 10 PCs will be offered the upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to **Windows Update** in **Settings**. Once the upgrade rollout has started and the upgrade has been tested and validated for your PC's hardware, Windows Update will indicate that the upgrade is ready for installation. -You can get early access to test Windows Sun Valley by joining the Windows Insider Program, or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). +You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). ## Windows Sun Valley lifecycle @@ -85,6 +85,10 @@ Microsoft 365 licenses that include Windows licenses will permit you to run Wind If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. +## Rollback + +After you have upgraded to Windows Sun Valley, you have 10 days to use the rollback function if you wish to move back to Windows 10 while keeping your files and data. After the 10 day grace period, you will need to back up your data and perform a clean install to move back to Windows 10. + ## See also [Get started with Windows Sun Valley](windows-sv-get-started.md) From 2f9c22406530f92d022ae533148aeaab31abd9d6 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:53:17 -0700 Subject: [PATCH 041/104] fix link --- windows/hub/index.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 748310bd3c..ee4cf53863 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -31,7 +31,7 @@ landingContent: - text: Windows Sun Valley requirements url: /windows/whats-new/windows-sv-requirements - text: Get started with Windows Sun Valley - url: /windows/whats-new/get-started-windows-sv + url: /windows/whats-new/windows-sv-get-started - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: Windows release information From 3370035c0aa5ec219a703f9d4cae969d054f3e5a Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:57:00 -0700 Subject: [PATCH 042/104] remove hub index links to sv in other doc sets --- windows/hub/index.yml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index ee4cf53863..2673320b9e 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -44,8 +44,6 @@ landingContent: links: - text: Configure Windows url: /windows/configuration/index - - text: Configure Windows Sun Valley - url: /windows/configuration/windows-sv-configure.md - text: Accessibility information for IT Pros url: /windows/configuration/windows-10-accessibility-for-itpros - text: Configure access to Microsoft Store @@ -60,8 +58,6 @@ landingContent: links: - text: Deploy and update Windows url: /windows/deployment/index - - text: Deploy Windows Sun Valley - url: /windows/deployment/windows-sv-deploy.md - text: Windows deployment scenarios url: /windows/deployment/windows-10-deployment-scenarios - text: Create a deployment plan @@ -77,8 +73,6 @@ landingContent: links: - text: Windows application management url: /windows/application-management/index - - text: Manage Windows Sun Valley applications - url: /windows/application-management/windows-sv-app-manage.md - text: Understand the different apps included in Windows 10 url: /windows/application-management/apps-in-windows-10 - text: Get started with App-V for Windows 10 @@ -93,8 +87,6 @@ landingContent: links: - text: Windows client management url: /windows/client-management/index - - text: Manage Windows Sun Valley - url: /windows/client-management/windows-sv-manage.md - text: Administrative tools url: /windows/client-management/administrative-tools-in-windows-10 - text: Create mandatory user profiles From 925f6fb900772415648cd214db71578a81ebcb65 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 11:58:37 -0700 Subject: [PATCH 043/104] shorten card name in whats new --- windows/whats-new/index.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index e1c75debe3..3c77fc9036 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -35,7 +35,7 @@ landingContent: url: windows-sv-get-started.md - - title: What's new in Windows 10 + - title: Windows 10 linkLists: - linkListType: overview links: From 0ca60cfe027bccc4de07aa8d577ad7f9da981621 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 3 Jun 2021 12:03:42 -0700 Subject: [PATCH 044/104] copy over articles to sv node --- windows/sv/windows-sv-get-started.md | 36 +++++++++++++ windows/sv/windows-sv-overview.md | 74 ++++++++++++++++++++++++++- windows/sv/windows-sv-requirements.md | 36 ++++++++++++- 3 files changed, 143 insertions(+), 3 deletions(-) create mode 100644 windows/sv/windows-sv-get-started.md diff --git a/windows/sv/windows-sv-get-started.md b/windows/sv/windows-sv-get-started.md new file mode 100644 index 0000000000..25b0d9e99c --- /dev/null +++ b/windows/sv/windows-sv-get-started.md @@ -0,0 +1,36 @@ +--- +title: Get started with Windows Sun Valley +description: Learn about features, review requirements, and plan your deployment of Windows Sun Valley, including IT Pro content, release information, and history. +keywords: ["get started", "windows sun valley"] +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +author: greg-lindsay +ms.author: greglin +ms.date: 10/16/2017 +ms.reviewer: +manager: laurawi +ms.localizationpriority: high +ms.topic: article +--- + +# Get started with Windows Sun Valley + +**Applies to** + +- Windows Sun Valley + +## Deployment planning + +Consider using the following process to deploy Windows Sun Valley to existing devices: +1. Preview Windows Sun Valley and create a deployment plan. +2. Test critical applications and management policies. +3. Update devices to the latest release of Windows 10. +4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. +5. Update deployment tools and infrastructure. +6. Update qualifying devices to Windows Sun Valley. + + +## See also + +[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy) diff --git a/windows/sv/windows-sv-overview.md b/windows/sv/windows-sv-overview.md index 7b375294fe..2407048dbc 100644 --- a/windows/sv/windows-sv-overview.md +++ b/windows/sv/windows-sv-overview.md @@ -18,5 +18,77 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley overview -Overview of Windows Sun Valley. +**Applies to** +- Windows Sun Valley +This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. + +Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. + +## How to get Windows Sun Valley + +Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. Windows Sun Valley will also be available on new devices that meet the hardware requirements. + +You must be running a current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). + +Not all eligible Windows 10 PCs will be offered the upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to **Windows Update** in **Settings**. Once the upgrade rollout has started and the upgrade has been tested and validated for your PC's hardware, Windows Update will indicate that the upgrade is ready for installation. + +You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). + +## Windows Sun Valley lifecycle + +### Updates + +Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. + +Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. + +### Servicing + +Windows Sun Valley annual releases are supported for 24 months for the following editions: +- Home +- Pro +- Pro for Workstations +- Pro Education + +Windows Sun Valley annual releases are supported for 36 months for the following editions: +- Enterprise +- Education + +### Features and applications + +Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. + +## Windows 10 lifecycle + +Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. + +Windows 10 will be supported with security updates until October 2025. + +## Management and tools + +Windows Sun Valley is based on the same foundation as Windows 10. You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products. + +## Hardware compatibility + +Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. + +## Application compatibility + +Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have [App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure), Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [Products and Capabilities: App Assure](https://docs.microsoft.com/fasttrack/products-and-capabilities#app-assure). + +## Licensing + +There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. + +Microsoft 365 licenses that include Windows licenses will permit you to run Windows Sun Valley on supported devices. + +If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. + +## Rollback + +After you have upgraded to Windows Sun Valley, you have 10 days to use the rollback function if you wish to move back to Windows 10 while keeping your files and data. After the 10 day grace period, you will need to back up your data and perform a clean install to move back to Windows 10. + +## See also + +[Get started with Windows Sun Valley](windows-sv-get-started.md) diff --git a/windows/sv/windows-sv-requirements.md b/windows/sv/windows-sv-requirements.md index 88eb31f2f5..ddb8bf84c1 100644 --- a/windows/sv/windows-sv-requirements.md +++ b/windows/sv/windows-sv-requirements.md @@ -1,6 +1,7 @@ --- title: Windows Sun Valley requirements -description: Requirements to deploy Windows Sun Valley +description: Hardware requirements to deploy Windows Sun Valley +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C ms.reviewer: manager: laurawi ms.audience: itpro @@ -17,5 +18,36 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley requirements -Windows Sun Valley requirements. +This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley can also be run on Virtual Machines (VMs). + +## Software requirements + +The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. + +## Hardware requirements + +To install Windows Sun Valley, devices must meet the following specifications: + +Processor +- Intel 8th generation, Intel Celeron N4000, Pentium N5000 +- AMD Ryzen gen 2 (Zen+), AMD 3xxx +- Qualcomm 7c, 8c, 8cx +- 64bit architecture +- 1Ghz clock speed +- 2 cores + +Hardware +- 64GB drive +- 4GB RAM +- UEFI, Secure Boot capable & TPM 2.0 +- Monitor size 9” or more with HD Resolution +- DirectX 12 compatible graphics / WDDM 2.x + +## Network requirements + +Internet connectivity is required for the Home Edition + +## See also + +[Windows Sun Valley overview](windows-sv-overview.md) From ec1e78030b840bb4000029b3194ac327ffdba97d Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Mon, 7 Jun 2021 13:55:47 -0700 Subject: [PATCH 045/104] overview url shortened --- windows/hub/TOC.yml | 2 +- windows/hub/index.yml | 2 +- windows/whats-new/TOC.yml | 2 +- windows/whats-new/index.yml | 2 +- windows/whats-new/{windows-sv-overview.md => windows-sv.md} | 0 5 files changed, 4 insertions(+), 4 deletions(-) rename windows/whats-new/{windows-sv-overview.md => windows-sv.md} (100%) diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 18f3f6c535..1752028577 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -7,7 +7,7 @@ - name: What's new in Windows href: /windows/whats-new - name: Windows Sun Valley - href: /windows/whats-new/windows-sv-overview + href: /windows/whats-new/windows-sv - name: Release information href: /windows/release-health - name: Deployment diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 2673320b9e..e9086a6765 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -27,7 +27,7 @@ landingContent: - linkListType: overview links: - text: Windows Sun Valley overview - url: /windows/whats-new/windows-sv-overview + url: /windows/whats-new/windows-sv - text: Windows Sun Valley requirements url: /windows/whats-new/windows-sv-requirements - text: Get started with Windows Sun Valley diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index 21c6326fb5..896d20ab51 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -4,7 +4,7 @@ expanded: true items: - name: Windows Sun Valley overview - href: windows-sv-overview.md + href: windows-sv.md - name: Windows Sun Valley requirements href: windows-sv-requirements.md - name: Get started with Windows Sun Valley diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index 3c77fc9036..2d9e4f6076 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -28,7 +28,7 @@ landingContent: - linkListType: overview links: - text: Windows Sun Valley Overview - url: windows-sv-overview.md + url: windows-sv.md - text: Windows Sun Valley requirements url: windows-sv-requirements.md - text: Get started with Windows Sun Valley diff --git a/windows/whats-new/windows-sv-overview.md b/windows/whats-new/windows-sv.md similarity index 100% rename from windows/whats-new/windows-sv-overview.md rename to windows/whats-new/windows-sv.md From 3c8347fee326b81e0ef337794893e9ce3a6982b2 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 10:23:43 -0700 Subject: [PATCH 046/104] plan and prepare --- windows/whats-new/TOC.yml | 6 ++-- windows/whats-new/index.yml | 7 ++-- ...s-sv-get-started.md => windows-sv-plan.md} | 0 windows/whats-new/windows-sv-prepare.md | 36 +++++++++++++++++++ 4 files changed, 44 insertions(+), 5 deletions(-) rename windows/whats-new/{windows-sv-get-started.md => windows-sv-plan.md} (100%) create mode 100644 windows/whats-new/windows-sv-prepare.md diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index 896d20ab51..612896a73f 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -7,8 +7,10 @@ href: windows-sv.md - name: Windows Sun Valley requirements href: windows-sv-requirements.md - - name: Get started with Windows Sun Valley - href: windows-sv-get-started.md + - name: Plan to deploy Windows Sun Valley + href: windows-sv-plan.md + - name: Get ready for Windows Sun Valley + href: windows-sv-prepare.md - name: Windows 10 expanded: true items: diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index 2d9e4f6076..7e3ba4fc82 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -31,9 +31,10 @@ landingContent: url: windows-sv.md - text: Windows Sun Valley requirements url: windows-sv-requirements.md - - text: Get started with Windows Sun Valley - url: windows-sv-get-started.md - + - text: Plan to deploy Windows Sun Valley + url: windows-sv-plan.md + - text: Get ready for Windows Sun Valley + url: windows-sv-prepare.md - title: Windows 10 linkLists: diff --git a/windows/whats-new/windows-sv-get-started.md b/windows/whats-new/windows-sv-plan.md similarity index 100% rename from windows/whats-new/windows-sv-get-started.md rename to windows/whats-new/windows-sv-plan.md diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md new file mode 100644 index 0000000000..25b0d9e99c --- /dev/null +++ b/windows/whats-new/windows-sv-prepare.md @@ -0,0 +1,36 @@ +--- +title: Get started with Windows Sun Valley +description: Learn about features, review requirements, and plan your deployment of Windows Sun Valley, including IT Pro content, release information, and history. +keywords: ["get started", "windows sun valley"] +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +author: greg-lindsay +ms.author: greglin +ms.date: 10/16/2017 +ms.reviewer: +manager: laurawi +ms.localizationpriority: high +ms.topic: article +--- + +# Get started with Windows Sun Valley + +**Applies to** + +- Windows Sun Valley + +## Deployment planning + +Consider using the following process to deploy Windows Sun Valley to existing devices: +1. Preview Windows Sun Valley and create a deployment plan. +2. Test critical applications and management policies. +3. Update devices to the latest release of Windows 10. +4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. +5. Update deployment tools and infrastructure. +6. Update qualifying devices to Windows Sun Valley. + + +## See also + +[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy) From 65360cb93aa8a91aedaa2a78c63625a3ee0444cf Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 10:38:55 -0700 Subject: [PATCH 047/104] reset deploy content --- windows/deployment/TOC.yml | 8 +++----- windows/deployment/index.yml | 8 ++++---- windows/deployment/windows-sv-deploy.md | 26 ------------------------ windows/deployment/windows-sv-plan.md | 26 ------------------------ windows/deployment/windows-sv-prepare.md | 23 --------------------- windows/whats-new/windows-sv-plan.md | 12 +++++------ windows/whats-new/windows-sv-prepare.md | 14 ++++++------- 7 files changed, 20 insertions(+), 97 deletions(-) delete mode 100644 windows/deployment/windows-sv-deploy.md delete mode 100644 windows/deployment/windows-sv-plan.md delete mode 100644 windows/deployment/windows-sv-prepare.md diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index b66af87886..e3fcfca9e0 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -6,7 +6,7 @@ - name: What's new href: deploy-whats-new.md - name: Windows Sun Valley deployment overview - href: windows-sv-deploy.md + href: /windows/whats-new/windows-sv-overview.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? @@ -36,7 +36,7 @@ - name: Plan items: - name: Windows Sun Valley deployment planning - href: windows-sv-plan.md + href: /windows/whats-new/windows-sv-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria @@ -72,7 +72,7 @@ - name: Prepare items: - name: Prepare to deploy Windows Sun Valley - href: windows-sv-prepare.md + href: /windows/whats-new/windows-sv-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md - name: Evaluate and update infrastructure @@ -104,8 +104,6 @@ items: - name: Deploy Windows client items: - - name: Windows Sun Valley deployment overview - href: windows-sv-deploy.md - name: Deploy Windows client with Autopilot href: windows-autopilot/index.yml - name: Deploy Windows client with Configuration Manager diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index 7b8a56f315..ef58977660 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -1,7 +1,7 @@ ### YamlMime:Landing title: Windows client deployment resources and documentation # < 60 chars -summary: Learn about deploying and keeping Windows 10 up to date. # < 160 chars +summary: Learn about deploying and keeping Windows client devices up to date. # < 160 chars metadata: title: Windows client deployment resources and documentation # Required; page title displayed in search results. Include the brand. < 60 chars. @@ -13,7 +13,7 @@ metadata: ms.collection: windows-10 author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. ms.author: greglin #Required; microsoft alias of author; optional team alias. - ms.date: 08/05/2020 #Required; mm/dd/yyyy format. + ms.date: 06/24/2021 #Required; mm/dd/yyyy format. localization_priority: medium # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new @@ -66,8 +66,8 @@ landingContent: links: - text: What's new in Windows deployment url: deploy-whats-new.md - - text: Windows 11 deployment overview - url: windows-sv-deploy.md + - text: Windows Sun Valley overview + url: /windows/whats-new/windows-sv-overview.md - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md - text: Basics of Windows updates, channels, and tools diff --git a/windows/deployment/windows-sv-deploy.md b/windows/deployment/windows-sv-deploy.md deleted file mode 100644 index fe50501d35..0000000000 --- a/windows/deployment/windows-sv-deploy.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Windows Sun Valley deployment planning -description: Understand the different ways Windows Sun Valley operating system can be deployed in your organization. Explore several Windows Sun Valley deployment scenarios. -ms.reviewer: -manager: laurawi -ms.audience: itpro -ms.author: greglin -author: greg-lindsay -keywords: upgrade, in-place, configuration, deploy -ms.prod: w10 -ms.mktglfcycl: deploy -ms.localizationpriority: medium -ms.sitesec: library -audience: itpro -ms.topic: article ---- - -# Windows Sun Valley deployment planning - -**Applies to** -- Windows Sun Valley - -## Windows Sun Valley deployment considerations - - - diff --git a/windows/deployment/windows-sv-plan.md b/windows/deployment/windows-sv-plan.md deleted file mode 100644 index 7244da875c..0000000000 --- a/windows/deployment/windows-sv-plan.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Windows Sun Valley deployment planning -description: Understand the different ways Windows Sun Valley operating system can be deployed in your organization. Explore several Windows Sun Valley deployment scenarios. -ms.assetid: 7A29D546-52CC-482C-8870-8123C7DC04B5 -ms.reviewer: -manager: laurawi -ms.audience: itpro -ms.author: greglin -author: greg-lindsay -keywords: upgrade, in-place, configuration, deploy -ms.prod: w10 -ms.mktglfcycl: deploy -ms.localizationpriority: medium -ms.sitesec: library -audience: itpro -ms.topic: article ---- - -# Windows 11 deployment planning - -**Applies to** -- Windows Sun Valley - -To successfully deploy the Windows Sun Valley operating system in your organization, it is important to understand the different ways that it can be deployed, especially now that there are new scenarios to consider. Choosing among these scenarios, and understanding the capabilities and limitations of each, is a key task. - -The following table summarizes various Windows Sun Valley deployment scenarios. The scenarios are each assigned to one of three categories. \ No newline at end of file diff --git a/windows/deployment/windows-sv-prepare.md b/windows/deployment/windows-sv-prepare.md deleted file mode 100644 index 2a0b778723..0000000000 --- a/windows/deployment/windows-sv-prepare.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Prepare to deploy Windows Sun Valley -description: Understand the different ways Windows Sun Valley operating system can be deployed in your organization. Explore several Windows Sun Valley deployment scenarios. -ms.reviewer: -manager: laurawi -ms.audience: itpro -ms.author: greglin -author: greg-lindsay -keywords: upgrade, in-place, configuration, deploy -ms.prod: w10 -ms.mktglfcycl: deploy -ms.localizationpriority: medium -ms.sitesec: library -audience: itpro -ms.topic: article ---- - -# Prepare to deploy Windows 11 - -**Applies to** -- Windows Sun Valley - -To successfully deploy \ No newline at end of file diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 25b0d9e99c..337709d6fe 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -1,13 +1,13 @@ --- -title: Get started with Windows Sun Valley -description: Learn about features, review requirements, and plan your deployment of Windows Sun Valley, including IT Pro content, release information, and history. -keywords: ["get started", "windows sun valley"] -ms.prod: w10 +title: Plan to deploy Windows Sun Valley +description: Windows Sun Valley deployment planning, IT Pro content. +keywords: ["get started", "windows sun valley", "plan"] +ms.prod: w11 ms.mktglfcycl: deploy ms.sitesec: library author: greg-lindsay ms.author: greglin -ms.date: 10/16/2017 +ms.date: 06/24/2021 ms.reviewer: manager: laurawi ms.localizationpriority: high @@ -33,4 +33,4 @@ Consider using the following process to deploy Windows Sun Valley to existing de ## See also -[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy) +[Get ready for Windows Sun Valley](windows-sv-prepare.md) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 25b0d9e99c..f3692eeaff 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -1,26 +1,26 @@ --- -title: Get started with Windows Sun Valley -description: Learn about features, review requirements, and plan your deployment of Windows Sun Valley, including IT Pro content, release information, and history. +title: Prepare to deploy Windows Sun Valley +description: Prepare your infrastructure and tools to deploy Windows Sun Valley, IT Pro content. keywords: ["get started", "windows sun valley"] -ms.prod: w10 +ms.prod: w11 ms.mktglfcycl: deploy ms.sitesec: library author: greg-lindsay ms.author: greglin -ms.date: 10/16/2017 +ms.date: 06/24/2021 ms.reviewer: manager: laurawi ms.localizationpriority: high ms.topic: article --- -# Get started with Windows Sun Valley +# Prepare to deploy Windows Sun Valley **Applies to** - Windows Sun Valley -## Deployment planning +## Deployment readiness Consider using the following process to deploy Windows Sun Valley to existing devices: 1. Preview Windows Sun Valley and create a deployment plan. @@ -33,4 +33,4 @@ Consider using the following process to deploy Windows Sun Valley to existing de ## See also -[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy) +[Windows Sun Valley deployment planning](windows-sv-plan.md) From 1da7b6dfefcb1dd20281f3d0ac9a01476edc232d Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 11:37:09 -0700 Subject: [PATCH 048/104] added whitepaper draft --- windows/whats-new/TOC.yml | 4 +- windows/whats-new/windows-sv-plan.md | 90 +++++++++++++++++++++++++ windows/whats-new/windows-sv-prepare.md | 63 +++++++++++++++++ windows/whats-new/windows-sv.md | 13 +++- 4 files changed, 167 insertions(+), 3 deletions(-) diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index 612896a73f..d611e4787f 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -7,9 +7,9 @@ href: windows-sv.md - name: Windows Sun Valley requirements href: windows-sv-requirements.md - - name: Plan to deploy Windows Sun Valley + - name: Create a deployment plan href: windows-sv-plan.md - - name: Get ready for Windows Sun Valley + - name: Prepare to deploy Windows Sun Valley href: windows-sv-prepare.md - name: Windows 10 expanded: true diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 337709d6fe..190595d9be 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -22,6 +22,96 @@ ms.topic: article ## Deployment planning +Planning for Sun Valley + +Sun Valley has the same underlying technology used today in Windows 10. IT Professionals can use familiar existing toolsets to plan, prepare , deploy, manage, and updateand manage both Sun Valley and Windows 10 updates alike. Because we anticipate customers organizations will be using a mix of Windows 10 devices side-by-side as they integrate Sun Valley into their environments, there are some unique yet largely familiar considerations for this new operating system to help aid in planning for upcoming deployments. + +Determining eligibility +We know one of the first questions that you will have is "Do the current PC(s) in my environment meet the Sun Valley hardware requirements bar? To assess if your device(s) meet these hardware criteria, IT Professionals can continue to use the first party analytics tools they are familiar with, including Update Compliance. In addition, Microsoft is sharing necessary information to 3rd party ISVs to enable their tools to support analytics for Sun Valley. + +Consumers can determine whether their device is eligible for Sun Valley by using the PC Health Check application to assess if a device meets the minimum hardware specifications [place forthcoming ink here]. In addition, detailed minimum requirements can be found at aka.ms/minspec [link forthcoming here]. + + +Sun Valley rollouts +In this section, we’ll share more on the rollout experience for home users benefiting from the role of intelligent rollout and for IT admin managed devices who will note some changes to management controls. +Home user, consumer devices +W indows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Sun Valley will be offered Sun Valley in October of 2021. Though the message will vary by PC manufacturer, customers will see labels such as ‘this PC will upgrade to Sun Valley once available’ on products for purchase. Note, devices purchased beginning in October will see the Sun Valley offer during the out of box experience or already be imaged with Sun Valley. + +Sun Valley will be made available to current Windows 10 devices who are eligible after General Availability (GA) through the familiar Windows Update experience, first to seekers, then as part of our intelligent rollout process. The Windows Update Settings page will confirm when a device is eligible, and users can choose to upgrade or not. + + +As with Windows 10, the machine learning based intelligent rollout will be leveraged when rolling out upgrades. Our ML uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience, ensuring that devices first nominated for updates are those likely to have a seamless experience, and that devices which may be problematic get the benefit of resolving potential compatibility issues before being offered an upgrade to Sun Valley. + +Managed devices + +While we are excited about the innovations and end user productivity improvements in Sun Valley, we recognize that the "right time" to move will be different for each organization. As always, for devices that you manage as an organization, you can choose between Sun Valley and Windows 10, and when the right time is for your organization to make the migration. + +Commercial customers will be able to deploy the Sun Valley update using their typical management tools to eligible devices in their organization beginning at GA. Customers upgrading from Windows Update using WUfB will have the additional benefit of two safety nets: offering blocks on non-eligible devices who do not meet the hardware requirements to upgrade to Sun Valley and Safeguard holds. Safeguard holds will function for Sun Valley devices just as they do for Windows 10. IT Professionals will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Sun Valley . + +It is worth noting that if you use Windows Update for Business to manage feature update deployments today you will need to leverage the “Target Version” policy rather than Feature Update deferrals to move from Windows 10 to Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (e.g. Windows 10 21H1 to Windows 10 21H2), but they can not move you between products (e.g. Windows 10 to Windows Sun Valley). + +Additionally, please note that Sun Valley has a new end user license agreement. By nature of deploying with WUfB Target Version or with WSUS you are accepting this new end user license agreement on behalf of the end users within your organization. + +Finally, please note that while Windows 10 Pro or higher can upgrade for free using their existing management tools, those using S mode will need to first switch out of S mode (as S mode is currently not supported on Sun Valley). + +What about customizations that customers have in place necessary to support their deployments today? Will those continue to work for Sun Valley? + +Availability and upgrade path +The Sun Valley upgrade offer will begin for eligible devices at Sun Valley GA in October of this year (2021). This is true for eligible devices already running updated Windows 10 as well as for brand new devices . + +Enterprise customers who have a volume licensing agreement with Software Assurance or Windows Enterprise E3 subscription will be able to upgrade existing devices to Sun Valley after GA. + +To get a jump start on Sun Valley, we recommend that IT professionals join the Windows Insider Program (WIP) to deploy and validate it in their environments. + +If you're an IT administrator who's interested in exploring new features as they're being created, we recommend using the Beta Channel (available summer 2021) + +As an IT administrator, if you who would like to validate the Sun Valley release (and Windows 10 releases) before broadly deploying in your organization, we recommend you join our Windows Insider Program Release Preview Channel (available in summer 2021). + +Commercial customers can begin validating and exploring Sun Valley prior to GA. Sun Valley will be available for commercial customers to deploy beginning in the summer of 2021 via the Windows Insider Program for Business. Customers can deploy bits from the Windows Insider Pre-release category in WSUS, by configuring Manage Preview Builds to “Release Preview” with WUfB, by leveraging Windows Virtual Devices or Cloud PC*(will this be announced when this paper goes out?) and Azure Marketplace images, or even through simply downloading and deploying ISOs from our Windows Insider Program ISO Download page. Note – regardless of which way you choose to deploy, commercial customers have the benefit of free Microsoft support when validating pre-release, simply submit your support cases here. + +To learn more about the Windows Insider Program for Business, click here. + + + +Like Windows 10, Sun Valley devices will receive regular monthly quality updates to provide security updates and bug fixes, and at times, new functionality when deemed appropriate. Unlike Windows 10, however, Sun Valley devices will receive a single feature update annually. Knowing this will help you define your servicing strategy. + +For devices on in-service versions of Windows 10 that do not meet Sun Valley hardware requirements, they will continue to receive monthly Windows 10 security updates. +Servicing Duration: Sun Valley vs. Windows 10 +The duration of support changes slightly. Today, Windows 10 feature updates are released twice yearly, around March and September, via the Semi-Annual Channel. They are serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy. For Sun Valley, we will support each annual release for 24 months for Home and Pro editions, and 36 months for Enterprise and Education editions, beginning at GA in October 2021. + +Windows 10 will continue to receive twice yearly feature updates . We have committed to supporting Windows 10 through October 14, 2025. + +For more information, see the Windows Release Information Page, which includes information for Windows 10 semi-annual channel and LTSC releases, as well as Sun Valley. + +Potential section from Michael Raschko (pending as of 5/31): Windows 10 currently runs on more than 1 billion devices around the world, representing considerable time and investment from consumers and organizations alike. While we expect the migration to Windows “Sun Valley” will have less overhead than previous legacy Windows versions to Windows 10, we understand that organizations will need time to complete their move to Sun Valley based on their individual situations. Further, they will want to maintain and grow the value of their Windows 10 investment in the interim. + +For organizations who cannot move to Sun Valley immediately, Microsoft’s guidance is to standardize their devices on Windows 10 version to 21H2. Windows 10, version 21H2 will be the last feature update to Windows 10 but will receive specific feature enhancements to ease any growing pains there may be in migrating to Sun Valley. These features aim to provide compatibility with Microsoft existing and future products and services. + +It’s important that organizations remain in control and have adequate time to plan for feature enhancements which could affect the experience of end users. To facilitate this, feature enhancements will be provided on a quarterly cadence and will be provided with management policies to enable or disable those features. [some of this, once we get it locked in, will belong in the Feature update section below] + +Alternative sentence coming from Ellie’s deck: We will release Windows 10, version 21H2 in the second half of 2021 to keep your users productive and secure while you chart your path to Sun Valley. this is ‘we have your back’ language, and would be great to include it +Application compatibility & readiness + +Application Compatibility +Understanding that applications will work following an OS rollout is critical in the planning stage. Since Sun Valley has been built with compatibility in mind, it’s undergoing and passing the same application compatibility testing requirements that we have in place for Windows 10 feature and quality update releases. + +Microsoft is committed to ensuring applications work on the latest versions of our software. Our promise states that applications that worked on Windows 7/8.1/10 will work on Sun Valley. [This is where app compat info goes, as Test Base and AppAssure go into the Prepare section] + + + + + + + + + + + + + + + + Consider using the following process to deploy Windows Sun Valley to existing devices: 1. Preview Windows Sun Valley and create a deployment plan. 2. Test critical applications and management policies. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index f3692eeaff..5cf0d2459c 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -21,6 +21,62 @@ ms.topic: article - Windows Sun Valley ## Deployment readiness + +Organizations will vary in their pace relative to transitioning from Windows 10 to Sun Valley, and we expect early corporate adoptions to consist of smaller test environments before rolling out to wider groups begins. With the new Sun Valley experience, it’s highly plausible that hybrid environments of both operating systems running simultaneously will be the norm, at least initially. + +As you prepare for Sun Valley, it’s also a good time to look at the deployment infrastructure of your environment. If you aren’t already taking advantage of cloud-based management tools like Microsoft Endpoint Manager this might be the perfect scenario in which to make that leap. Or if you are on -premises, Configuration Manager’s Cloud management gateway <- additional Configuration Manager content needed here . + +Additionally, policies related to deployment may need to be updated or re-evaluated respective of update compliance deadlines, device activity policies, and the re-evaluation of older policies. A servicing mindset pointed at keeping current means that, as with Windows 10 devices, you will create a deployment plan in order to build out your servicing strategy. + +The IT Pro tools that you are familiar with and have been using in the past to prepare for deployments also work in Sun Valley; you can analyze endpoints, determine application compatibility, and manage deployments in the same way you did with Windows 10: + +Analytics +Content on Endpoint analytics needed. + +Application compatibility +Two Microsoft services that work directly with you to ensure application compatibility with Sun Valley are App Assure and Test Base. + +If you experience any issues with your apps and are enrolled in the App Assure service, Microsoft will help you identify the issue at no cost. App Assure works with you to troubleshoot the issue, determine the root cause, and can help fix the issue as well. App Assure is subscription based, but subscriptions are free for eligible customers with 150+ seats. + +Test Base is our intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. + +Management tools +The management toolset that you use for heavy lifting during deployments of Windows 10 are still able to be leveraged in Sun Valley. There are a few nuanced differences described here: + +• Windows Server Update Service (WSUS): For commercial customers using WSUS, they will need to sync the new “Windows ” product category. +• Windows Update for Business (WUfB): For commercial customers using WUfB, they will need to leverage the Target Version capability rather than feature update deferrals to move from Windows 10 to Windows . Feature Update deferrals are great to move to newer versions of your current product (e.g. Windows 10 21H1 to Windows 10 21H2), but do not enable you to move between products (e.g. Windows 10 to Windows ). Quality update deferrals will continue to work the same across both Windows 10 and Windows . +• MEM Configuration Manager: For customers using MEM Configuration Manager, you will easily be able to sync the new “Windows ” Product category and begin upgrading eligible devices. Please note that Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. If you would like to validate Sun Valley prior to release, simply sync the “Windows Insider Pre-release" category as well. +• MEM Intune: For customers using MEM Intune with E3 licenses you will be able to leverage the “Feature Update Deployments” to easily manage moving between Windows 10 versions or to Windows 21H2. +• Autopilot: Autopilot works seamlessly in a Windows Sun Valley OOBE experience (out of box experience). It’s plug and play. +• In an Intune environment, a Sun Valley boot image needs to already exist on the device for Autopilot to work with Sun Valley. If the device comes with a Windows 10 boot image, IT Pros can use Windows Autopilot to deploy Windows 10, and then use Windows Update for Business to upgrade to Windows Sun Valley. +o +o To use Windows Autopilot to upgrade existing, eligible devices, Configuration Manager plus the task sequence ‘Windows Autopilot for existing devices’ can place the Windows Sun Valley boot image onto the managed device, allowing Windows Autopilot to then deploy Sun Valley. +o Note that Windows Autopilot cannot downgrade a device from Sun Valley to Windows 10. + + + + + + + + + + + + + + + + + + + + + + + + + Consider using the following process to deploy Windows Sun Valley to existing devices: 1. Preview Windows Sun Valley and create a deployment plan. @@ -34,3 +90,10 @@ Consider using the following process to deploy Windows Sun Valley to existing de ## See also [Windows Sun Valley deployment planning](windows-sv-plan.md) + +• Technical documentation: Prescriptive and authoritative documentation on Microsoft Docs can help you plan for, prepare, and deploy Sun Valley — and to service and manage Windows devices effectively across your organization. +• Windows release health: Windows release health offers the quickest way to stay up to date on update-related news, information, and best practices, including important lifecycle reminders and the status of known issues and safeguard holds. IT administrators have access to this information, plus additional details, within the health experience Microsoft 365 admin center. +• Windows 10 update history: For every version of the Windows operating system, we publish a consolidated update history documentation experience, offering quick access to the knowledge base (KB) articles for each monthly, optional, and out-of-band release. In addition to update highlights, you’ll find a list of improvements and fixes, a summary of any known issues, and details on how to get the update, including any prerequisites. Want to see an example? See Windows 10 update history. +• Windows Tech Community: Offering technical professionals a place to discuss, share, troubleshoot, and learn around Windows, Tech Community is also the home of the Windows IT Pro Blog, our monthly Windows Office Hours events, and the Windows Video Hub. +• Microsoft Learn: We are in the process of developing online learning paths and modules to help you and your organization effectively plan, prepare, and deploy Sun Valley effectively. + diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 2407048dbc..c25337973d 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -25,6 +25,15 @@ This article provides an introduction and answers some frequently asked question Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. +--statement to edit +In general, you can deploy , manage, and secure Sun Valley using the same tools and solutions you use today. +You can use Configuration Manager for your deployment, though we recommend cloud-based solutions such as Microsoft Endpoint Manager to fully take advantage of more data-driven insights. Monitoring update compliance. +Since your familiar Windows 10 tools are meant to be used with Sun Valley as well, then managing, securing, and deploying Sun Valley devices will be well-known procedures in the Plan, Prepare and Deploy process. +Just as we recommend that broad deployment of new versions of Windows 10 begin with a pilot deployment phase, Sun Valley is no different. Further, you will likely have an environment that is a blend of Windows 10-capable devices and Windows 10 + Sun Valley-eligible devices. You will be poised to rollout an update to a select number of devices, once you’ve gone through the checklist of Pilot deployment tasks such as assigning the pilot devices from your Prepare phase, implementing baseline and operations updates, testing and supporting the devices, and so forth. When you deploy to your test group, we recommend cloud-based deployment solutions such as Microsoft Endpoint Manager to fully take advantage of data-driven insights, though Configuration Manager works as well. +Using artifacts from your Plan and Prepare phase (such as application assignments, security and configuration baselines, etc.) as well as data from your test deployment, will give you the confidence you seek to manage a broader rollout of Sun Valley to increasingly larger rings of eligible devices. Desktop Analytics will help you ensure that your apps are scoped to only the pilot rings you designate. +Though we’ve mentioned only a few, the tools and processes we have had in place for your previous 10 Windows deployment will be there for you with Sun Valley as well. +---------statement end + ## How to get Windows Sun Valley Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. Windows Sun Valley will also be available on new devices that meet the hardware requirements. @@ -91,4 +100,6 @@ After you have upgraded to Windows Sun Valley, you have 10 days to use the rollb ## See also -[Get started with Windows Sun Valley](windows-sv-get-started.md) +[Get started with Windows Sun Valley](windows-sv-plan.md) + + From 1e4b23e92e217e81b560a44b218dffc13828ff71 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 13:36:24 -0700 Subject: [PATCH 049/104] some edits --- windows/whats-new/windows-sv-plan.md | 2 +- windows/whats-new/windows-sv.md | 13 ++++++++++--- 2 files changed, 11 insertions(+), 4 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 190595d9be..e005a6fda7 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -14,7 +14,7 @@ ms.localizationpriority: high ms.topic: article --- -# Get started with Windows Sun Valley +# Planning for Windows Sun Valley **Applies to** diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index c25337973d..1bd9dac13e 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -25,13 +25,20 @@ This article provides an introduction and answers some frequently asked question Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. ---statement to edit +The following articles are available to learn about Windows Sun Valley. The articles are designed to be read in order. + +1. Windows Sun Valley overview: An introduction to Windows Sun Valley (this article). +2. [Windows Sun Valley requirements](windows-sv-requirements.md): Hardware, software, network, and licensing requirements to deploy Windows Sun Valley. +3. [Planning for Windows Sun Valley](windows-sv-plan.md): Guidance to create a Windows Sun Valley deployment plan. +4. [Prepare to deploy Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley in your organization. + +--statement to edit
In general, you can deploy , manage, and secure Sun Valley using the same tools and solutions you use today. You can use Configuration Manager for your deployment, though we recommend cloud-based solutions such as Microsoft Endpoint Manager to fully take advantage of more data-driven insights. Monitoring update compliance. Since your familiar Windows 10 tools are meant to be used with Sun Valley as well, then managing, securing, and deploying Sun Valley devices will be well-known procedures in the Plan, Prepare and Deploy process. Just as we recommend that broad deployment of new versions of Windows 10 begin with a pilot deployment phase, Sun Valley is no different. Further, you will likely have an environment that is a blend of Windows 10-capable devices and Windows 10 + Sun Valley-eligible devices. You will be poised to rollout an update to a select number of devices, once you’ve gone through the checklist of Pilot deployment tasks such as assigning the pilot devices from your Prepare phase, implementing baseline and operations updates, testing and supporting the devices, and so forth. When you deploy to your test group, we recommend cloud-based deployment solutions such as Microsoft Endpoint Manager to fully take advantage of data-driven insights, though Configuration Manager works as well. Using artifacts from your Plan and Prepare phase (such as application assignments, security and configuration baselines, etc.) as well as data from your test deployment, will give you the confidence you seek to manage a broader rollout of Sun Valley to increasingly larger rings of eligible devices. Desktop Analytics will help you ensure that your apps are scoped to only the pilot rings you designate. -Though we’ve mentioned only a few, the tools and processes we have had in place for your previous 10 Windows deployment will be there for you with Sun Valley as well. +Though we’ve mentioned only a few, the tools and processes we have had in place for your previous 10 Windows deployment will be there for you with Sun Valley as well.
---------statement end ## How to get Windows Sun Valley @@ -84,7 +91,7 @@ Most accessories and associated software that worked with Windows 10 are expecte ## Application compatibility -Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have [App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure), Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [Products and Capabilities: App Assure](https://docs.microsoft.com/fasttrack/products-and-capabilities#app-assure). +Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have [App Assure](/fasttrack/microsoft-365/app-assure), Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [Products and Capabilities: App Assure](/fasttrack/products-and-capabilities#app-assure). ## Licensing From 0e4086933b45b98e4d64d6320eb84709f3cc202c Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 14:43:21 -0700 Subject: [PATCH 050/104] some edits --- windows/whats-new/windows-sv.md | 50 +++++++++++++++++---------------- 1 file changed, 26 insertions(+), 24 deletions(-) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 1bd9dac13e..f63b6653dd 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -21,33 +21,33 @@ ms.custom: seo-marvel-apr2020 **Applies to** - Windows Sun Valley -This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. +This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. -Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. +The following articles are available to learn about Windows Sun Valley. -The following articles are available to learn about Windows Sun Valley. The articles are designed to be read in order. - -1. Windows Sun Valley overview: An introduction to Windows Sun Valley (this article). +1. [Windows Sun Valley overview](windows-sv-md): An introduction to Windows Sun Valley (this article). 2. [Windows Sun Valley requirements](windows-sv-requirements.md): Hardware, software, network, and licensing requirements to deploy Windows Sun Valley. 3. [Planning for Windows Sun Valley](windows-sv-plan.md): Guidance to create a Windows Sun Valley deployment plan. 4. [Prepare to deploy Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley in your organization. ---statement to edit
-In general, you can deploy , manage, and secure Sun Valley using the same tools and solutions you use today. -You can use Configuration Manager for your deployment, though we recommend cloud-based solutions such as Microsoft Endpoint Manager to fully take advantage of more data-driven insights. Monitoring update compliance. -Since your familiar Windows 10 tools are meant to be used with Sun Valley as well, then managing, securing, and deploying Sun Valley devices will be well-known procedures in the Plan, Prepare and Deploy process. -Just as we recommend that broad deployment of new versions of Windows 10 begin with a pilot deployment phase, Sun Valley is no different. Further, you will likely have an environment that is a blend of Windows 10-capable devices and Windows 10 + Sun Valley-eligible devices. You will be poised to rollout an update to a select number of devices, once you’ve gone through the checklist of Pilot deployment tasks such as assigning the pilot devices from your Prepare phase, implementing baseline and operations updates, testing and supporting the devices, and so forth. When you deploy to your test group, we recommend cloud-based deployment solutions such as Microsoft Endpoint Manager to fully take advantage of data-driven insights, though Configuration Manager works as well. -Using artifacts from your Plan and Prepare phase (such as application assignments, security and configuration baselines, etc.) as well as data from your test deployment, will give you the confidence you seek to manage a broader rollout of Sun Valley to increasingly larger rings of eligible devices. Desktop Analytics will help you ensure that your apps are scoped to only the pilot rings you designate. -Though we’ve mentioned only a few, the tools and processes we have had in place for your previous 10 Windows deployment will be there for you with Sun Valley as well.
----------statement end +## Introduction + +Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. Windows Sun Valley is designed to support today's flexible [hybrid work](https://pulse.microsoft.com/the-journey-to-the-new-normal-driving-innovation-and-productivity-in-a-hybrid-world/) environment. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. + +Windows Sun Valley is built on the same foundation as Windows 10, so you can generally deploy, manage, and secure Sun Valley using the same tools and solutions you use today. + +All upgrades to Windows Sun Valley from Windows 10 will be free. ## How to get Windows Sun Valley -Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. Windows Sun Valley will also be available on new devices that meet the hardware requirements. +Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new devices that meet the hardware requirements. -You must be running a current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). +You must be running Windows 10, version 20H1 or later, and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). -Not all eligible Windows 10 PCs will be offered the upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to **Windows Update** in **Settings**. Once the upgrade rollout has started and the upgrade has been tested and validated for your PC's hardware, Windows Update will indicate that the upgrade is ready for installation. +For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. + +For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update. +- Not all eligible Windows 10 PCs will be offered the upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to **Settings** > **Update & Security** > **Windows Update**. Once the upgrade rollout has started and the upgrade has been tested and validated for your PC's hardware, Windows Update will indicate that the upgrade is ready for installation. You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). @@ -61,15 +61,17 @@ Microsoft will continue to provide one cumulative package that includes all late ### Servicing -Windows Sun Valley annual releases are supported for 24 months for the following editions: -- Home -- Pro -- Pro for Workstations -- Pro Education +Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table. -Windows Sun Valley annual releases are supported for 36 months for the following editions: -- Enterprise -- Education + + + + + + + + +
EditionServicing timeline
Windows Sun Valley Home24 months from the release date
Windows Sun Valley Pro
Windows Sun Valley Pro for Workstations
Windows Sun Valley Pro Education
Windows Sun Valley Enterprise36 months from the release date
Windows Sun Valley Education
### Features and applications From ea92ce15d666e34f50a95d3ef72c2257eae296fa Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 14:57:15 -0700 Subject: [PATCH 051/104] some edits --- windows/whats-new/windows-sv.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index f63b6653dd..b522d4c788 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -25,7 +25,7 @@ This article provides an introduction and answers some frequently asked question The following articles are available to learn about Windows Sun Valley. -1. [Windows Sun Valley overview](windows-sv-md): An introduction to Windows Sun Valley (this article). +1. Windows Sun Valley overview (this article): An introduction to Windows Sun Valley. 2. [Windows Sun Valley requirements](windows-sv-requirements.md): Hardware, software, network, and licensing requirements to deploy Windows Sun Valley. 3. [Planning for Windows Sun Valley](windows-sv-plan.md): Guidance to create a Windows Sun Valley deployment plan. 4. [Prepare to deploy Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley in your organization. @@ -63,15 +63,14 @@ Microsoft will continue to provide one cumulative package that includes all late Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table. - - - - - - - - -
EditionServicing timeline
Windows Sun Valley Home24 months from the release date
Windows Sun Valley Pro
Windows Sun Valley Pro for Workstations
Windows Sun Valley Pro Education
Windows Sun Valley Enterprise36 months from the release date
Windows Sun Valley Education
+ +| 24 months from the release date | 36 months from the release date | +| --- | --- | +| Windows Sun Valley Home | Windows Sun Valley Enterprise | +| Windows Sun Valley Pro | Windows Sun Valley Education | +| Windows Sun Valley Pro for Workstations | | +| Windows Sun Valley Pro Education | | + ### Features and applications From 595141a61131183276144ea7e2fdce0af897dc5e Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 15:59:11 -0700 Subject: [PATCH 052/104] some edits --- windows/whats-new/windows-sv-prepare.md | 21 +++++++++++---------- windows/whats-new/windows-sv.md | 4 +++- 2 files changed, 14 insertions(+), 11 deletions(-) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 5cf0d2459c..7e9f6b1e5c 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -41,17 +41,18 @@ If you experience any issues with your apps and are enrolled in the App Assure s Test Base is our intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. Management tools -The management toolset that you use for heavy lifting during deployments of Windows 10 are still able to be leveraged in Sun Valley. There are a few nuanced differences described here: +The management toolset that you use for heavy lifting during deployments of Windows 10 are still able to be leveraged in Sun Valley. There are a few differences: -• Windows Server Update Service (WSUS): For commercial customers using WSUS, they will need to sync the new “Windows ” product category. -• Windows Update for Business (WUfB): For commercial customers using WUfB, they will need to leverage the Target Version capability rather than feature update deferrals to move from Windows 10 to Windows . Feature Update deferrals are great to move to newer versions of your current product (e.g. Windows 10 21H1 to Windows 10 21H2), but do not enable you to move between products (e.g. Windows 10 to Windows ). Quality update deferrals will continue to work the same across both Windows 10 and Windows . -• MEM Configuration Manager: For customers using MEM Configuration Manager, you will easily be able to sync the new “Windows ” Product category and begin upgrading eligible devices. Please note that Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. If you would like to validate Sun Valley prior to release, simply sync the “Windows Insider Pre-release" category as well. -• MEM Intune: For customers using MEM Intune with E3 licenses you will be able to leverage the “Feature Update Deployments” to easily manage moving between Windows 10 versions or to Windows 21H2. -• Autopilot: Autopilot works seamlessly in a Windows Sun Valley OOBE experience (out of box experience). It’s plug and play. -• In an Intune environment, a Sun Valley boot image needs to already exist on the device for Autopilot to work with Sun Valley. If the device comes with a Windows 10 boot image, IT Pros can use Windows Autopilot to deploy Windows 10, and then use Windows Update for Business to upgrade to Windows Sun Valley. -o -o To use Windows Autopilot to upgrade existing, eligible devices, Configuration Manager plus the task sequence ‘Windows Autopilot for existing devices’ can place the Windows Sun Valley boot image onto the managed device, allowing Windows Autopilot to then deploy Sun Valley. -o Note that Windows Autopilot cannot downgrade a device from Sun Valley to Windows 10. +- Windows Server Update Service (WSUS): For commercial customers using WSUS, they will need to sync the new “Windows ” product category. +- Windows Update for Business (WUfB): For commercial customers using WUfB, they will need to leverage the Target Version capability rather than feature update deferrals to move from Windows 10 to Windows . Feature Update deferrals are great to move to newer versions of your current product (e.g. Windows 10 21H1 to Windows 10 21H2), but do not enable you to move between products (e.g. Windows 10 to Windows ). Quality update deferrals will continue to work the same across both Windows 10 and Windows . +- MEM Configuration Manager: For customers using MEM Configuration Manager, you will easily be able to sync the new “Windows ” Product category and begin upgrading eligible devices. Please note that Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. If you would like to validate Sun Valley prior to release, simply sync the “Windows Insider Pre-release" category as well. +- MEM Intune: For customers using MEM Intune with E3 licenses you will be able to leverage the “Feature Update Deployments” to easily manage moving between Windows 10 versions or to Windows 21H2. +- Autopilot: Autopilot works seamlessly in a Windows Sun Valley OOBE experience (out of box experience). It’s plug and play. +- In an Intune environment, a Sun Valley boot image needs to already exist on the device for Autopilot to work with Sun Valley. If the device comes with a Windows 10 boot image, IT Pros can use Windows Autopilot to deploy Windows 10, and then use Windows Update for Business to upgrade to Windows Sun Valley. + +To use Windows Autopilot to upgrade existing, eligible devices, Configuration Manager plus the task sequence ‘Windows Autopilot for existing devices’ can place the Windows Sun Valley boot image onto the managed device, allowing Windows Autopilot to then deploy Sun Valley. + +Windows Autopilot cannot downgrade a device from Sun Valley to Windows 10. diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index b522d4c788..96288250c3 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -61,7 +61,9 @@ Microsoft will continue to provide one cumulative package that includes all late ### Servicing -Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table. +Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. + +See the following table. | 24 months from the release date | 36 months from the release date | From ba0b3bdec452c36c016c28445ce2a6ffb62cf8b4 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 8 Jun 2021 16:45:59 -0700 Subject: [PATCH 053/104] rm sv --- windows/application-management/index.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/application-management/index.yml b/windows/application-management/index.yml index dc786fd289..95053b27f0 100644 --- a/windows/application-management/index.yml +++ b/windows/application-management/index.yml @@ -5,7 +5,7 @@ summary: Learn about managing applications in Windows client, including how to r metadata: title: Windows application management # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Learn about managing applications in Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Learn about managing applications in Windows 10. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice From 371c0224e94e326b82e0a5215fdecfe0cd450062 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 10 Jun 2021 16:28:09 -0700 Subject: [PATCH 054/104] draft --- windows/whats-new/windows-sv-plan.md | 173 +++++++++---------- windows/whats-new/windows-sv-prepare.md | 94 ++++------ windows/whats-new/windows-sv-requirements.md | 2 + windows/whats-new/windows-sv.md | 88 ++++------ 4 files changed, 148 insertions(+), 209 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index e005a6fda7..d7fda86414 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -14,7 +14,7 @@ ms.localizationpriority: high ms.topic: article --- -# Planning for Windows Sun Valley +# Plan to deploy Windows Sun Valley **Applies to** @@ -22,103 +22,92 @@ ms.topic: article ## Deployment planning -Planning for Sun Valley - -Sun Valley has the same underlying technology used today in Windows 10. IT Professionals can use familiar existing toolsets to plan, prepare , deploy, manage, and updateand manage both Sun Valley and Windows 10 updates alike. Because we anticipate customers organizations will be using a mix of Windows 10 devices side-by-side as they integrate Sun Valley into their environments, there are some unique yet largely familiar considerations for this new operating system to help aid in planning for upcoming deployments. - -Determining eligibility -We know one of the first questions that you will have is "Do the current PC(s) in my environment meet the Sun Valley hardware requirements bar? To assess if your device(s) meet these hardware criteria, IT Professionals can continue to use the first party analytics tools they are familiar with, including Update Compliance. In addition, Microsoft is sharing necessary information to 3rd party ISVs to enable their tools to support analytics for Sun Valley. - -Consumers can determine whether their device is eligible for Sun Valley by using the PC Health Check application to assess if a device meets the minimum hardware specifications [place forthcoming ink here]. In addition, detailed minimum requirements can be found at aka.ms/minspec [link forthcoming here]. - - -Sun Valley rollouts -In this section, we’ll share more on the rollout experience for home users benefiting from the role of intelligent rollout and for IT admin managed devices who will note some changes to management controls. -Home user, consumer devices -W indows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Sun Valley will be offered Sun Valley in October of 2021. Though the message will vary by PC manufacturer, customers will see labels such as ‘this PC will upgrade to Sun Valley once available’ on products for purchase. Note, devices purchased beginning in October will see the Sun Valley offer during the out of box experience or already be imaged with Sun Valley. - -Sun Valley will be made available to current Windows 10 devices who are eligible after General Availability (GA) through the familiar Windows Update experience, first to seekers, then as part of our intelligent rollout process. The Windows Update Settings page will confirm when a device is eligible, and users can choose to upgrade or not. - - -As with Windows 10, the machine learning based intelligent rollout will be leveraged when rolling out upgrades. Our ML uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience, ensuring that devices first nominated for updates are those likely to have a seamless experience, and that devices which may be problematic get the benefit of resolving potential compatibility issues before being offered an upgrade to Sun Valley. - -Managed devices - -While we are excited about the innovations and end user productivity improvements in Sun Valley, we recognize that the "right time" to move will be different for each organization. As always, for devices that you manage as an organization, you can choose between Sun Valley and Windows 10, and when the right time is for your organization to make the migration. - -Commercial customers will be able to deploy the Sun Valley update using their typical management tools to eligible devices in their organization beginning at GA. Customers upgrading from Windows Update using WUfB will have the additional benefit of two safety nets: offering blocks on non-eligible devices who do not meet the hardware requirements to upgrade to Sun Valley and Safeguard holds. Safeguard holds will function for Sun Valley devices just as they do for Windows 10. IT Professionals will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Sun Valley . - -It is worth noting that if you use Windows Update for Business to manage feature update deployments today you will need to leverage the “Target Version” policy rather than Feature Update deferrals to move from Windows 10 to Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (e.g. Windows 10 21H1 to Windows 10 21H2), but they can not move you between products (e.g. Windows 10 to Windows Sun Valley). - -Additionally, please note that Sun Valley has a new end user license agreement. By nature of deploying with WUfB Target Version or with WSUS you are accepting this new end user license agreement on behalf of the end users within your organization. - -Finally, please note that while Windows 10 Pro or higher can upgrade for free using their existing management tools, those using S mode will need to first switch out of S mode (as S mode is currently not supported on Sun Valley). - -What about customizations that customers have in place necessary to support their deployments today? Will those continue to work for Sun Valley? - -Availability and upgrade path -The Sun Valley upgrade offer will begin for eligible devices at Sun Valley GA in October of this year (2021). This is true for eligible devices already running updated Windows 10 as well as for brand new devices . - -Enterprise customers who have a volume licensing agreement with Software Assurance or Windows Enterprise E3 subscription will be able to upgrade existing devices to Sun Valley after GA. - -To get a jump start on Sun Valley, we recommend that IT professionals join the Windows Insider Program (WIP) to deploy and validate it in their environments. - -If you're an IT administrator who's interested in exploring new features as they're being created, we recommend using the Beta Channel (available summer 2021) - -As an IT administrator, if you who would like to validate the Sun Valley release (and Windows 10 releases) before broadly deploying in your organization, we recommend you join our Windows Insider Program Release Preview Channel (available in summer 2021). - -Commercial customers can begin validating and exploring Sun Valley prior to GA. Sun Valley will be available for commercial customers to deploy beginning in the summer of 2021 via the Windows Insider Program for Business. Customers can deploy bits from the Windows Insider Pre-release category in WSUS, by configuring Manage Preview Builds to “Release Preview” with WUfB, by leveraging Windows Virtual Devices or Cloud PC*(will this be announced when this paper goes out?) and Azure Marketplace images, or even through simply downloading and deploying ISOs from our Windows Insider Program ISO Download page. Note – regardless of which way you choose to deploy, commercial customers have the benefit of free Microsoft support when validating pre-release, simply submit your support cases here. - -To learn more about the Windows Insider Program for Business, click here. - - - -Like Windows 10, Sun Valley devices will receive regular monthly quality updates to provide security updates and bug fixes, and at times, new functionality when deemed appropriate. Unlike Windows 10, however, Sun Valley devices will receive a single feature update annually. Knowing this will help you define your servicing strategy. - -For devices on in-service versions of Windows 10 that do not meet Sun Valley hardware requirements, they will continue to receive monthly Windows 10 security updates. -Servicing Duration: Sun Valley vs. Windows 10 -The duration of support changes slightly. Today, Windows 10 feature updates are released twice yearly, around March and September, via the Semi-Annual Channel. They are serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy. For Sun Valley, we will support each annual release for 24 months for Home and Pro editions, and 36 months for Enterprise and Education editions, beginning at GA in October 2021. +This article provides IT professionals with planning guidance for the recent Windows Sun Valley announcements, specifically: -Windows 10 will continue to receive twice yearly feature updates . We have committed to supporting Windows 10 through October 14, 2025. + - Adoption guidance + - Infrastructure planning + - Servicing cadence and lifecycle + - Application readiness + - Functionality and coexistence with Windows 10 ecosystems + +## Deployment process -For more information, see the Windows Release Information Page, which includes information for Windows 10 semi-annual channel and LTSC releases, as well as Sun Valley. - -Potential section from Michael Raschko (pending as of 5/31): Windows 10 currently runs on more than 1 billion devices around the world, representing considerable time and investment from consumers and organizations alike. While we expect the migration to Windows “Sun Valley” will have less overhead than previous legacy Windows versions to Windows 10, we understand that organizations will need time to complete their move to Sun Valley based on their individual situations. Further, they will want to maintain and grow the value of their Windows 10 investment in the interim. - -For organizations who cannot move to Sun Valley immediately, Microsoft’s guidance is to standardize their devices on Windows 10 version to 21H2. Windows 10, version 21H2 will be the last feature update to Windows 10 but will receive specific feature enhancements to ease any growing pains there may be in migrating to Sun Valley. These features aim to provide compatibility with Microsoft existing and future products and services. - -It’s important that organizations remain in control and have adequate time to plan for feature enhancements which could affect the experience of end users. To facilitate this, feature enhancements will be provided on a quarterly cadence and will be provided with management policies to enable or disable those features. [some of this, once we get it locked in, will belong in the Feature update section below] - -Alternative sentence coming from Ellie’s deck: We will release Windows 10, version 21H2 in the second half of 2021 to keep your users productive and secure while you chart your path to Sun Valley. this is ‘we have your back’ language, and would be great to include it -Application compatibility & readiness - -Application Compatibility -Understanding that applications will work following an OS rollout is critical in the planning stage. Since Sun Valley has been built with compatibility in mind, it’s undergoing and passing the same application compatibility testing requirements that we have in place for Windows 10 feature and quality update releases. - -Microsoft is committed to ensuring applications work on the latest versions of our software. Our promise states that applications that worked on Windows 7/8.1/10 will work on Sun Valley. [This is where app compat info goes, as Test Base and AppAssure go into the Prepare section] - - - - - - - - - - - - - - - - -Consider using the following process to deploy Windows Sun Valley to existing devices: +Consider using the following processes to deploy Windows Sun Valley: 1. Preview Windows Sun Valley and create a deployment plan. 2. Test critical applications and management policies. -3. Update devices to the latest release of Windows 10. +3. Update devices to the Windows 10, version 20H1 or later. 4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. -5. Update deployment tools and infrastructure. +5. Update deployment tools, infrastructure, and policies. 6. Update qualifying devices to Windows Sun Valley. + +## Phased deployment + +A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is identical to the [service management model](/windows/deployment/update/create-deployment-plan) recommended for Windows 10 updates. With this method, you define the time and scope of devices that will migrate to Windows Sun Valley. A [calendar based approac](/windows/deployment/update/plan-define-strategy#calendar-approaches) is an effective method to plan Windows Sun Valley upgrades that includes scheduling of future Windows 10 and Windows Sun Valley updates. + +Also consider [assigning roles](/windows/deployment/update/plan-define-readiness) within your organization to groups and individuals you'll need to carry out specific tasks, if you have not already done so. + +## Infrastructure and tools + +You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products beginning on the General Availability (GA) date for Windows Sun Valley. As part of your deployment planning, you will need to [evaluate your infrastructure](/windows/deployment/update/eval-infra-tools) and tools to verify they can support deployment and updates for Windows Sun Valley. For more information about updates to support the deployment of Windows Sun Valley, see [Management tools](windows-sv-prepare.md#management-tools). + +## Configurations + +Assess your current [configurations](/windows/deployment/update/eval-infra-tools#configuration-updates) such as security baselines, administrative templates, and policies that affect updates. Then, set some criteria to define your [operational readiness](/windows/deployment/update/eval-infra-tools#define-operational-readiness-criteria), Define an infrastructure update plan to: +- Review requirements +- Identify gaps +- Implement required updates + +## Windows Sun Valley Servicing + +### Cadence + +Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. + +Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. + +### Lifecycle + +Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table:
+ + +| 24 months from the release date | 36 months from the release date | +| ------------------------------- | ------------------------------- | +| Windows Sun Valley Home | Windows Sun Valley Enterprise | +| Windows Sun Valley Pro | Windows Sun Valley Education | +| Windows Sun Valley Pro for Workstations | | +| Windows Sun Valley Pro Education | | + +### Features and applications + +Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. + +## Application readiness + +Windows Sun Valley is designed to work with the applications you are currently using with Windows 10. If an application compatibility issue is identified, Microsoft provides services to help you remediate the problem. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility) + + + + + + + + + + + + + + + + + + + + + + + + ## See also diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 7e9f6b1e5c..3d7fa0815a 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -22,79 +22,45 @@ ms.topic: article ## Deployment readiness -Organizations will vary in their pace relative to transitioning from Windows 10 to Sun Valley, and we expect early corporate adoptions to consist of smaller test environments before rolling out to wider groups begins. With the new Sun Valley experience, it’s highly plausible that hybrid environments of both operating systems running simultaneously will be the norm, at least initially. +This article provides details on how to begin testing and validating Windows Sun Valley in your environment, and prepare for deployment. Links are also provided to important resource locations for more information. -As you prepare for Sun Valley, it’s also a good time to look at the deployment infrastructure of your environment. If you aren’t already taking advantage of cloud-based management tools like Microsoft Endpoint Manager this might be the perfect scenario in which to make that leap. Or if you are on -premises, Configuration Manager’s Cloud management gateway <- additional Configuration Manager content needed here . +To prepare for deployment of Windows Sun Valley, you will need to implement your [planned updates](windows-sv-plan.md) to infrastructure, settings, and tools, including: +- Test your critical applications and management policies +- Update devices to Windows 10, version 20H1 or later +- Verify hardware meets requirements for Windows Sun Valley +- Update your management tools, infrastructure, and policies +- [Prepare users](/windows/deployment/update/prepare-deploy-windows#prepare-users) for Windows Sun Valley. -Additionally, policies related to deployment may need to be updated or re-evaluated respective of update compliance deadlines, device activity policies, and the re-evaluation of older policies. A servicing mindset pointed at keeping current means that, as with Windows 10 devices, you will create a deployment plan in order to build out your servicing strategy. +When these actions are completed, you can begin your phased deployment of Windows Sun Valley. -The IT Pro tools that you are familiar with and have been using in the past to prepare for deployments also work in Sun Valley; you can analyze endpoints, determine application compatibility, and manage deployments in the same way you did with Windows 10: +## Application compatibility -Analytics -Content on Endpoint analytics needed. +Two Microsoft services that work directly with you to ensure application compatibility with Windows Sun Valley are [App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure) and [Test Base](https://www.microsoft.com/testbase). -Application compatibility -Two Microsoft services that work directly with you to ensure application compatibility with Sun Valley are App Assure and Test Base. +- If you experience any issues with your apps and are enrolled in the App Assure service, Microsoft will help you identify the issue at no cost. App Assure works with you to troubleshoot the issue, determine the root cause, and can help fix the issue as well. App Assure is subscription based, but subscriptions are free for eligible customers with 150+ seats. +- Test Base is Microsoft's intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Windows Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. -If you experience any issues with your apps and are enrolled in the App Assure service, Microsoft will help you identify the issue at no cost. App Assure works with you to troubleshoot the issue, determine the root cause, and can help fix the issue as well. App Assure is subscription based, but subscriptions are free for eligible customers with 150+ seats. +You can use [Desktop Analytics](/mem/configmgr/desktop-analytics/overview), to test application compatibility. To determine the impact of a potential application compatiblity issue, [assign priority to apps](/windows/deployment/update/plan-define-readiness#set-criteria-for-rating-apps) and then perform a [compatibility assessment](/mem/configmgr/desktop-analytics/compat-assessment). -Test Base is our intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. - -Management tools -The management toolset that you use for heavy lifting during deployments of Windows 10 are still able to be leveraged in Sun Valley. There are a few differences: - -- Windows Server Update Service (WSUS): For commercial customers using WSUS, they will need to sync the new “Windows ” product category. -- Windows Update for Business (WUfB): For commercial customers using WUfB, they will need to leverage the Target Version capability rather than feature update deferrals to move from Windows 10 to Windows . Feature Update deferrals are great to move to newer versions of your current product (e.g. Windows 10 21H1 to Windows 10 21H2), but do not enable you to move between products (e.g. Windows 10 to Windows ). Quality update deferrals will continue to work the same across both Windows 10 and Windows . -- MEM Configuration Manager: For customers using MEM Configuration Manager, you will easily be able to sync the new “Windows ” Product category and begin upgrading eligible devices. Please note that Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. If you would like to validate Sun Valley prior to release, simply sync the “Windows Insider Pre-release" category as well. -- MEM Intune: For customers using MEM Intune with E3 licenses you will be able to leverage the “Feature Update Deployments” to easily manage moving between Windows 10 versions or to Windows 21H2. -- Autopilot: Autopilot works seamlessly in a Windows Sun Valley OOBE experience (out of box experience). It’s plug and play. -- In an Intune environment, a Sun Valley boot image needs to already exist on the device for Autopilot to work with Sun Valley. If the device comes with a Windows 10 boot image, IT Pros can use Windows Autopilot to deploy Windows 10, and then use Windows Update for Business to upgrade to Windows Sun Valley. - -To use Windows Autopilot to upgrade existing, eligible devices, Configuration Manager plus the task sequence ‘Windows Autopilot for existing devices’ can place the Windows Sun Valley boot image onto the managed device, allowing Windows Autopilot to then deploy Sun Valley. - -Windows Autopilot cannot downgrade a device from Sun Valley to Windows 10. - - - - - - - - - - - - - - - - - - - - - - - - - - -Consider using the following process to deploy Windows Sun Valley to existing devices: -1. Preview Windows Sun Valley and create a deployment plan. -2. Test critical applications and management policies. -3. Update devices to the latest release of Windows 10. -4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. -5. Update deployment tools and infrastructure. -6. Update qualifying devices to Windows Sun Valley. +## Management tools +The following updates are required to support deploying Windows Sun Valley: +- Configuration Manager should use the current branch. + - You will easily be able to sync the new **Windows Sun Valley** product category and upgrade eligible devices. + - Configuration Manager will prompt you to accept the End User License Agreement on behalf of the users in your organization. + - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. +- If you use Windows Server Update Services (WSUS), you will need to sync the new Windows Sun Valley category. +- Windows Update for Business (WUfB) users can leverage the Target Version capability (not Feature Update deferrals). + - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. + - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and Safeguard holds. Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. +- No action is required for you to use Microsoft Intune because it is cloud-based. + - If you are using MEM Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley. +- Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience (OOBE) environment. + - In an Intune environment, a Windows Sun Valley boot image needs to already exist on the device for Windows Autopilot to work with Windows Sun Valley. + - If the device comes with a Windows 10 boot image, an administrator can use Windows Autopilot to deploy Windows 10, and then use WUfB to upgrade to Windows Sun Valley. + - To use Windows Autopilot to upgrade existing devices, Configuration Manager and the task sequence: **Windows Autopilot for existing devices** can place the Windows Sun Valley boot image on the managed device, allowing Windows Autopilot to deploy Windows Sun Valley. + - Windows Autopilot cannot be used to downgrade a device from Windows Sun Valley to Windows 10. ## See also [Windows Sun Valley deployment planning](windows-sv-plan.md) - -• Technical documentation: Prescriptive and authoritative documentation on Microsoft Docs can help you plan for, prepare, and deploy Sun Valley — and to service and manage Windows devices effectively across your organization. -• Windows release health: Windows release health offers the quickest way to stay up to date on update-related news, information, and best practices, including important lifecycle reminders and the status of known issues and safeguard holds. IT administrators have access to this information, plus additional details, within the health experience Microsoft 365 admin center. -• Windows 10 update history: For every version of the Windows operating system, we publish a consolidated update history documentation experience, offering quick access to the knowledge base (KB) articles for each monthly, optional, and out-of-band release. In addition to update highlights, you’ll find a list of improvements and fixes, a summary of any known issues, and details on how to get the update, including any prerequisites. Want to see an example? See Windows 10 update history. -• Windows Tech Community: Offering technical professionals a place to discuss, share, troubleshoot, and learn around Windows, Tech Community is also the home of the Windows IT Pro Blog, our monthly Windows Office Hours events, and the Windows Video Hub. -• Microsoft Learn: We are in the process of developing online learning paths and modules to help you and your organization effectively plan, prepare, and deploy Sun Valley effectively. - diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index ddb8bf84c1..e33c0381d6 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -24,6 +24,8 @@ This article lists the sotware and physical hardware requirements to run Windows The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. +If you are running Windows in S mode, you will need to first switch out of S mode prior to upgrading. S mode is not supported on Sun Valley. + ## Hardware requirements To install Windows Sun Valley, devices must meet the following specifications: diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 96288250c3..ac2765847b 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -44,59 +44,11 @@ Windows Sun Valley will delivered as an upgrade to devices running Windows 10 be You must be running Windows 10, version 20H1 or later, and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). -For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. - -For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update. -- Not all eligible Windows 10 PCs will be offered the upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to **Settings** > **Update & Security** > **Windows Update**. Once the upgrade rollout has started and the upgrade has been tested and validated for your PC's hardware, Windows Update will indicate that the upgrade is ready for installation. +For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update. You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). -## Windows Sun Valley lifecycle - -### Updates - -Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. - -Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. - -### Servicing - -Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. - -See the following table. - - -| 24 months from the release date | 36 months from the release date | -| --- | --- | -| Windows Sun Valley Home | Windows Sun Valley Enterprise | -| Windows Sun Valley Pro | Windows Sun Valley Education | -| Windows Sun Valley Pro for Workstations | | -| Windows Sun Valley Pro Education | | - - -### Features and applications - -Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. - -## Windows 10 lifecycle - -Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. - -Windows 10 will be supported with security updates until October 2025. - -## Management and tools - -Windows Sun Valley is based on the same foundation as Windows 10. You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products. - -## Hardware compatibility - -Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. - -## Application compatibility - -Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have [App Assure](/fasttrack/microsoft-365/app-assure), Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [Products and Capabilities: App Assure](/fasttrack/products-and-capabilities#app-assure). - -## Licensing +### Licensing There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. @@ -104,12 +56,42 @@ Microsoft 365 licenses that include Windows licenses will permit you to run Wind If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. -## Rollback +### Rollback After you have upgraded to Windows Sun Valley, you have 10 days to use the rollback function if you wish to move back to Windows 10 while keeping your files and data. After the 10 day grace period, you will need to back up your data and perform a clean install to move back to Windows 10. -## See also +## Compatibility -[Get started with Windows Sun Valley](windows-sv-plan.md) +Windows Sun Valley is based on the same foundation as Windows 10. Therefore, it supports investments that IT organizations have made to support Windows 10. + +### Management and tools + +You can use your current management tools, processes, and settings to manage quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools) and [Configurations](windows-sv-plan.md#configurations). + +### Hardware compatibility + +Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. + +### Application compatibility + +Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. +## Windows Sun Valley servicing + +For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](sv-plan.md#servicing). + +## Windows 10 lifecycle + +For organizations who cannot move to Windows Sun Valley immediately, Microsoft’s guidance is to standardize devices on Windows 10, version 21H2. This release will be the last feature update to Windows 10, but will receive specific feature enhancements to ease migrating to Windows Sun Valley. + +Windows 10 will continue to be supported with security updates until October 2025. + + +## Next steps + +[Plan to deploy Windows Sun Valley](windows-sv-plan.md)
+[Prepare for Windows Sun Valley](windows-sv-prepare.md) + + +## See also \ No newline at end of file From b7fd5c5eaf4a893f6f24a648b43662041cbd43df Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Jun 2021 11:59:36 -0700 Subject: [PATCH 055/104] tweaks --- windows/hub/index.yml | 4 +-- windows/whats-new/TOC.yml | 4 +-- windows/whats-new/index.yml | 2 +- windows/whats-new/windows-sv-plan.md | 24 +++++++++----- windows/whats-new/windows-sv-prepare.md | 6 ++-- windows/whats-new/windows-sv-requirements.md | 13 ++++++-- windows/whats-new/windows-sv.md | 35 ++++++++------------ 7 files changed, 50 insertions(+), 38 deletions(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index e9086a6765..60a1b71261 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -30,8 +30,8 @@ landingContent: url: /windows/whats-new/windows-sv - text: Windows Sun Valley requirements url: /windows/whats-new/windows-sv-requirements - - text: Get started with Windows Sun Valley - url: /windows/whats-new/windows-sv-get-started + - text: Plan to deploy Windows Sun Valley + url: /windows/whats-new/windows-sv-plan - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: Windows release information diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index d611e4787f..fb7a0de80e 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -7,9 +7,9 @@ href: windows-sv.md - name: Windows Sun Valley requirements href: windows-sv-requirements.md - - name: Create a deployment plan + - name: Plan to deploy Windows Sun Valley href: windows-sv-plan.md - - name: Prepare to deploy Windows Sun Valley + - name: Prepare for Windows Sun Valley href: windows-sv-prepare.md - name: Windows 10 expanded: true diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index 7e3ba4fc82..bf2243760c 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -33,7 +33,7 @@ landingContent: url: windows-sv-requirements.md - text: Plan to deploy Windows Sun Valley url: windows-sv-plan.md - - text: Get ready for Windows Sun Valley + - text: Prepare for Windows Sun Valley url: windows-sv-prepare.md - title: Windows 10 diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index d7fda86414..bdc60ffec4 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -18,21 +18,21 @@ ms.topic: article **Applies to** -- Windows Sun Valley +- Windows Sun Valley, version 21H2 ## Deployment planning -This article provides IT professionals with planning guidance for the recent Windows Sun Valley announcements, specifically: +This article provides you with planning guidance to deploy Windows Sun Valley in your organization, specifically: - Adoption guidance - Infrastructure planning - Servicing cadence and lifecycle - Application readiness - Functionality and coexistence with Windows 10 ecosystems - -## Deployment process -Consider using the following processes to deploy Windows Sun Valley: +### Deployment process + +Consider the following order of activities: 1. Preview Windows Sun Valley and create a deployment plan. 2. Test critical applications and management policies. 3. Update devices to the Windows 10, version 20H1 or later. @@ -40,9 +40,11 @@ Consider using the following processes to deploy Windows Sun Valley: 5. Update deployment tools, infrastructure, and policies. 6. Update qualifying devices to Windows Sun Valley. -## Phased deployment +### Phased deployment -A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is identical to the [service management model](/windows/deployment/update/create-deployment-plan) recommended for Windows 10 updates. With this method, you define the time and scope of devices that will migrate to Windows Sun Valley. A [calendar based approac](/windows/deployment/update/plan-define-strategy#calendar-approaches) is an effective method to plan Windows Sun Valley upgrades that includes scheduling of future Windows 10 and Windows Sun Valley updates. +A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is identical to the [service management model](/windows/deployment/update/create-deployment-plan) recommended for Windows 10 updates. With this method, you define the time and scope of devices that will migrate to Windows Sun Valley. + +A [calendar based approac](/windows/deployment/update/plan-define-strategy#calendar-approaches) is an effective method to plan Windows Sun Valley upgrades that includes scheduling of future Windows 10 and Windows Sun Valley updates. Also consider [assigning roles](/windows/deployment/update/plan-define-readiness) within your organization to groups and individuals you'll need to carry out specific tasks, if you have not already done so. @@ -57,7 +59,13 @@ Assess your current [configurations](/windows/deployment/update/eval-infra-tools - Identify gaps - Implement required updates -## Windows Sun Valley Servicing +## Windows 10 lifecycle + +For organizations who cannot move to Windows Sun Valley immediately, Microsoft’s guidance is to standardize devices on Windows 10, version 21H2. This release will be the last feature update to Windows 10, and will receive specific feature enhancements to ease migrating to Windows Sun Valley. + +Windows 10 will continue to be supported with security updates until October 2025. + +## Windows Sun Valley servicing ### Cadence diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 3d7fa0815a..14f8b5e369 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -14,11 +14,11 @@ ms.localizationpriority: high ms.topic: article --- -# Prepare to deploy Windows Sun Valley +# Prepare for Windows Sun Valley **Applies to** -- Windows Sun Valley +- Windows Sun Valley, version 21H2 ## Deployment readiness @@ -31,6 +31,8 @@ To prepare for deployment of Windows Sun Valley, you will need to implement your - Update your management tools, infrastructure, and policies - [Prepare users](/windows/deployment/update/prepare-deploy-windows#prepare-users) for Windows Sun Valley. + + When these actions are completed, you can begin your phased deployment of Windows Sun Valley. ## Application compatibility diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index e33c0381d6..ddd412c1cb 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -18,13 +18,17 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley requirements +**Applies to** + +- Windows Sun Valley, version 21H2 + This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley can also be run on Virtual Machines (VMs). ## Software requirements The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. -If you are running Windows in S mode, you will need to first switch out of S mode prior to upgrading. S mode is not supported on Sun Valley. +S mode is not supported on Windows Sun Valley. If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. ## Hardware requirements @@ -49,7 +53,12 @@ Hardware Internet connectivity is required for the Home Edition +## Next steps + +[Plan to deploy Windows Sun Valley](windows-sv-plan.md)
+[Prepare for Windows Sun Valley](windows-sv-prepare.md) + ## See also -[Windows Sun Valley overview](windows-sv-overview.md) +[Windows Sun Valley overview](windows-sv.md) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index ac2765847b..0513369d68 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -19,34 +19,34 @@ ms.custom: seo-marvel-apr2020 # Windows Sun Valley overview **Applies to** -- Windows Sun Valley + +- Windows Sun Valley, version 21H2 This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. -The following articles are available to learn about Windows Sun Valley. +The following articles are available to learn about Windows Sun Valley: 1. Windows Sun Valley overview (this article): An introduction to Windows Sun Valley. 2. [Windows Sun Valley requirements](windows-sv-requirements.md): Hardware, software, network, and licensing requirements to deploy Windows Sun Valley. 3. [Planning for Windows Sun Valley](windows-sv-plan.md): Guidance to create a Windows Sun Valley deployment plan. -4. [Prepare to deploy Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley in your organization. +4. [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley in your organization. ## Introduction Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. Windows Sun Valley is designed to support today's flexible [hybrid work](https://pulse.microsoft.com/the-journey-to-the-new-normal-driving-innovation-and-productivity-in-a-hybrid-world/) environment. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. -Windows Sun Valley is built on the same foundation as Windows 10, so you can generally deploy, manage, and secure Sun Valley using the same tools and solutions you use today. +Windows Sun Valley is built on the same foundation as Windows 10, so you can deploy, manage, and secure Windows Sun Valley using the same tools and solutions you use today. All upgrades to Windows Sun Valley from Windows 10 will be free. ## How to get Windows Sun Valley -Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new devices that meet the hardware requirements. +Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new devices that meet the hardware requirements. +- For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. +- For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update. +- You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). -You must be running Windows 10, version 20H1 or later, and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). - -For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update. - -You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). +For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). ### Licensing @@ -62,7 +62,7 @@ After you have upgraded to Windows Sun Valley, you have 10 days to use the rollb ## Compatibility -Windows Sun Valley is based on the same foundation as Windows 10. Therefore, it supports investments that IT organizations have made to support Windows 10. +Windows Sun Valley is built on the same foundation as Windows 10, so you can generally deploy, manage, and secure Sun Valley using the same tools and solutions you use today. ### Management and tools @@ -74,24 +74,17 @@ Most accessories and associated software that worked with Windows 10 are expecte ### Application compatibility -Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. - +Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility) ## Windows Sun Valley servicing For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](sv-plan.md#servicing). -## Windows 10 lifecycle - -For organizations who cannot move to Windows Sun Valley immediately, Microsoft’s guidance is to standardize devices on Windows 10, version 21H2. This release will be the last feature update to Windows 10, but will receive specific feature enhancements to ease migrating to Windows Sun Valley. - -Windows 10 will continue to be supported with security updates until October 2025. +## Windows 10 servicing +Windows 10 will continue to be supported with security updates until October 2025. For more information, see [Windows 10 lifecycle](windows-sv.plan.md#windows-10-lifecycle). ## Next steps [Plan to deploy Windows Sun Valley](windows-sv-plan.md)
[Prepare for Windows Sun Valley](windows-sv-prepare.md) - - -## See also \ No newline at end of file From 023aae766a37db24913c591e833acc941e85b2d1 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Jun 2021 12:52:51 -0700 Subject: [PATCH 056/104] draft --- windows/whats-new/windows-sv-plan.md | 46 ++++++-------------- windows/whats-new/windows-sv-prepare.md | 4 +- windows/whats-new/windows-sv-requirements.md | 6 +-- windows/whats-new/windows-sv.md | 8 ++-- 4 files changed, 21 insertions(+), 43 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index bdc60ffec4..8e49a77cdf 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -42,9 +42,14 @@ Consider the following order of activities: ### Phased deployment -A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is identical to the [service management model](/windows/deployment/update/create-deployment-plan) recommended for Windows 10 updates. With this method, you define the time and scope of devices that will migrate to Windows Sun Valley. +A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is identical to the [service management model](/windows/deployment/update/create-deployment-plan) recommended for Windows 10 updates and includes separate groups or 'rings' that receive an update at different times. For example: +- Preview: Windows Sun Valley planning and development +- Limited: Windows Sun Valley pilot deployment +- Broad: Windows Sun Valley rollout -A [calendar based approac](/windows/deployment/update/plan-define-strategy#calendar-approaches) is an effective method to plan Windows Sun Valley upgrades that includes scheduling of future Windows 10 and Windows Sun Valley updates. +With this method, you define the timing and scope of devices that will migrate to Windows Sun Valley, documenting and validating each phase before moving to the next one. + +A [calendar based approac](/windows/deployment/update/plan-define-strategy#calendar-approaches) is an effective method to plan Windows Sun Valley upgrades that includes scheduling of future Windows 10 and Windows Sun Valley updates. The calendar based approach can be very useful for update planning in a mixed Windows 10 and Windows Sun Valley enviroment. Also consider [assigning roles](/windows/deployment/update/plan-define-readiness) within your organization to groups and individuals you'll need to carry out specific tasks, if you have not already done so. @@ -59,12 +64,6 @@ Assess your current [configurations](/windows/deployment/update/eval-infra-tools - Identify gaps - Implement required updates -## Windows 10 lifecycle - -For organizations who cannot move to Windows Sun Valley immediately, Microsoft’s guidance is to standardize devices on Windows 10, version 21H2. This release will be the last feature update to Windows 10, and will receive specific feature enhancements to ease migrating to Windows Sun Valley. - -Windows 10 will continue to be supported with security updates until October 2025. - ## Windows Sun Valley servicing ### Cadence @@ -91,33 +90,14 @@ Most features and applications that are included with Windows 10 will be availab ## Application readiness -Windows Sun Valley is designed to work with the applications you are currently using with Windows 10. If an application compatibility issue is identified, Microsoft provides services to help you remediate the problem. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility) +Windows Sun Valley is designed to work with the applications you are currently using with Windows 10. If an application compatibility issue is identified, Microsoft provides services to help you remediate the problem. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility). +## Windows 10 coexistence +For organizations that need to maintain a mixed enviroment with coexisting Windows 10 and Windows Sun Valley devices, Microsoft’s guidance is to standardize on Windows 10, version 21H2. This release will be the last feature update to Windows 10, and will receive specific feature enhancements to ease migrating to Windows Sun Valley. +Windows 10 will continue to be supported with security updates until October 2025. +## Next steps - - - - - - - - - - - - - - - - - - - - - -## See also - -[Get ready for Windows Sun Valley](windows-sv-prepare.md) +[Prepare for Windows Sun Valley](windows-sv-prepare.md) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 14f8b5e369..754df4db9d 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -31,9 +31,7 @@ To prepare for deployment of Windows Sun Valley, you will need to implement your - Update your management tools, infrastructure, and policies - [Prepare users](/windows/deployment/update/prepare-deploy-windows#prepare-users) for Windows Sun Valley. - - -When these actions are completed, you can begin your phased deployment of Windows Sun Valley. +After completing these actions, you can begin your phased deployment of Windows Sun Valley. ## Application compatibility diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index ddd412c1cb..5be3c8bf06 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -22,11 +22,11 @@ ms.custom: seo-marvel-apr2020 - Windows Sun Valley, version 21H2 -This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley can also be run on Virtual Machines (VMs). +This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley is also supported on a Virtual Machine (VM). ## Software requirements -The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. +The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or later, on eligible hardware. S mode is not supported on Windows Sun Valley. If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. @@ -51,7 +51,7 @@ Hardware ## Network requirements -Internet connectivity is required for the Home Edition +Internet connectivity is required for the Home edition of Windows Sun Valley. ## Next steps diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 0513369d68..e8354606db 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -42,8 +42,8 @@ All upgrades to Windows Sun Valley from Windows 10 will be free. ## How to get Windows Sun Valley Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new devices that meet the hardware requirements. -- For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. -- For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update. +- For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. For more information, see [Management tools](windows-sv-prepare.md#management-tools). +- For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update using [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860). Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. - You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). @@ -78,11 +78,11 @@ Windows Sun Valley preserves the application compatibility promise made with Win ## Windows Sun Valley servicing -For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](sv-plan.md#servicing). +For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](windows-sv-plan.md#servicing). ## Windows 10 servicing -Windows 10 will continue to be supported with security updates until October 2025. For more information, see [Windows 10 lifecycle](windows-sv.plan.md#windows-10-lifecycle). +Windows 10 will continue to be supported with security updates until October 2025. For more information, see [Windows 10 lifecycle](windows-sv-plan.md#windows-10-lifecycle). ## Next steps From d96023e5dadcff575dc1f57518d014822c93246a Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Jun 2021 13:48:49 -0700 Subject: [PATCH 057/104] draft2 --- windows/whats-new/windows-sv-plan.md | 16 ++++++------ windows/whats-new/windows-sv-prepare.md | 4 +-- windows/whats-new/windows-sv-requirements.md | 3 ++- windows/whats-new/windows-sv.md | 26 +++++++++++--------- 4 files changed, 28 insertions(+), 21 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 8e49a77cdf..8904cf19e3 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -22,7 +22,7 @@ ms.topic: article ## Deployment planning -This article provides you with planning guidance to deploy Windows Sun Valley in your organization, specifically: +This article provides planning guidance to deploy Windows Sun Valley, specifically: - Adoption guidance - Infrastructure planning @@ -32,7 +32,7 @@ This article provides you with planning guidance to deploy Windows Sun Valley in ### Deployment process -Consider the following order of activities: +Consider using the following process to deploy Windows Sun Valley: 1. Preview Windows Sun Valley and create a deployment plan. 2. Test critical applications and management policies. 3. Update devices to the Windows 10, version 20H1 or later. @@ -42,20 +42,22 @@ Consider the following order of activities: ### Phased deployment -A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is identical to the [service management model](/windows/deployment/update/create-deployment-plan) recommended for Windows 10 updates and includes separate groups or 'rings' that receive an update at different times. For example: +A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is is described in the [service management model](/windows/deployment/update/create-deployment-plan) that is recommended for Windows 10 updates. It includes separate groups or 'rings' of devices that receive updates based on their role in your deployment plan. For example: - Preview: Windows Sun Valley planning and development - Limited: Windows Sun Valley pilot deployment - Broad: Windows Sun Valley rollout With this method, you define the timing and scope of devices that will migrate to Windows Sun Valley, documenting and validating each phase before moving to the next one. -A [calendar based approac](/windows/deployment/update/plan-define-strategy#calendar-approaches) is an effective method to plan Windows Sun Valley upgrades that includes scheduling of future Windows 10 and Windows Sun Valley updates. The calendar based approach can be very useful for update planning in a mixed Windows 10 and Windows Sun Valley enviroment. +Use a [calendar based approach](/windows/deployment/update/plan-define-strategy#calendar-approaches) to plan Windows Sun Valley upgrades, and include scheduling of future Windows 10 and Windows Sun Valley updates. The calendar based approach can be very useful for update planning in a mixed Windows 10 and Windows Sun Valley enviroment. Also consider [assigning roles](/windows/deployment/update/plan-define-readiness) within your organization to groups and individuals you'll need to carry out specific tasks, if you have not already done so. ## Infrastructure and tools -You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products beginning on the General Availability (GA) date for Windows Sun Valley. As part of your deployment planning, you will need to [evaluate your infrastructure](/windows/deployment/update/eval-infra-tools) and tools to verify they can support deployment and updates for Windows Sun Valley. For more information about updates to support the deployment of Windows Sun Valley, see [Management tools](windows-sv-prepare.md#management-tools). +You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, as well as using them to move between the two products beginning on the General Availability (GA) date for Windows Sun Valley. + +As part of your deployment planning, you will need to [evaluate your infrastructure](/windows/deployment/update/eval-infra-tools) and tools to verify they can support deployment and updates for Windows Sun Valley. For more information about updates to support the deployment of Windows Sun Valley, see [Management tools](windows-sv-prepare.md#management-tools). ## Configurations @@ -68,13 +70,13 @@ Assess your current [configurations](/windows/deployment/update/eval-infra-tools ### Cadence -Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. +Windows Sun Valley feature updates will be released once per year, in the second half of the year. Quality updates will be released each month, on the second Tuesday of the month. Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. ### Lifecycle -Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table:
+Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table:
 
| 24 months from the release date | 36 months from the release date | diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 754df4db9d..5b3b15b817 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -50,7 +50,7 @@ The following updates are required to support deploying Windows Sun Valley: - Configuration Manager will prompt you to accept the End User License Agreement on behalf of the users in your organization. - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. - If you use Windows Server Update Services (WSUS), you will need to sync the new Windows Sun Valley category. -- Windows Update for Business (WUfB) users can leverage the Target Version capability (not Feature Update deferrals). +- Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and Safeguard holds. Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. - No action is required for you to use Microsoft Intune because it is cloud-based. @@ -58,7 +58,7 @@ The following updates are required to support deploying Windows Sun Valley: - Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience (OOBE) environment. - In an Intune environment, a Windows Sun Valley boot image needs to already exist on the device for Windows Autopilot to work with Windows Sun Valley. - If the device comes with a Windows 10 boot image, an administrator can use Windows Autopilot to deploy Windows 10, and then use WUfB to upgrade to Windows Sun Valley. - - To use Windows Autopilot to upgrade existing devices, Configuration Manager and the task sequence: **Windows Autopilot for existing devices** can place the Windows Sun Valley boot image on the managed device, allowing Windows Autopilot to deploy Windows Sun Valley. + - To use [Windows Autopilot to upgrade existing devices](/mem/autopilot/existing-devices), Configuration Manager and the task sequence: **Windows Autopilot for existing devices** can place the Windows Sun Valley boot image on the managed device, allowing Windows Autopilot to deploy Windows Sun Valley. - Windows Autopilot cannot be used to downgrade a device from Windows Sun Valley to Windows 10. ## See also diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 5be3c8bf06..22999267a0 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -28,7 +28,8 @@ This article lists the sotware and physical hardware requirements to run Windows The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or later, on eligible hardware. -S mode is not supported on Windows Sun Valley. If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. +S mode is not supported on Windows Sun Valley. +- If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. ## Hardware requirements diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index e8354606db..50c3f38aa3 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -26,14 +26,14 @@ This article provides an introduction and answers some frequently asked question The following articles are available to learn about Windows Sun Valley: -1. Windows Sun Valley overview (this article): An introduction to Windows Sun Valley. -2. [Windows Sun Valley requirements](windows-sv-requirements.md): Hardware, software, network, and licensing requirements to deploy Windows Sun Valley. -3. [Planning for Windows Sun Valley](windows-sv-plan.md): Guidance to create a Windows Sun Valley deployment plan. -4. [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley in your organization. +1. Windows Sun Valley overview (this article): An introduction and brief overview. +2. [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. +3. [Planning for Windows Sun Valley](windows-sv-plan.md): Information to help you create a Windows Sun Valley deployment plan. +4. [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. ## Introduction -Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. Windows Sun Valley is designed to support today's flexible [hybrid work](https://pulse.microsoft.com/the-journey-to-the-new-normal-driving-innovation-and-productivity-in-a-hybrid-world/) environment. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. +Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. Windows Sun Valley is designed to support today's flexible [hybrid work](https://pulse.microsoft.com/the-journey-to-the-new-normal-driving-innovation-and-productivity-in-a-hybrid-world/) environment and to be the most reliable, secure, connected, and performant OS release ever. Windows Sun Valley is built on the same foundation as Windows 10, so you can deploy, manage, and secure Windows Sun Valley using the same tools and solutions you use today. @@ -41,10 +41,10 @@ All upgrades to Windows Sun Valley from Windows 10 will be free. ## How to get Windows Sun Valley -Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new devices that meet the hardware requirements. -- For managed PCs that meet requirements, the upgrade will be provided using the same process that you use today for feature updates. For more information, see [Management tools](windows-sv-prepare.md#management-tools). +Windows Sun Valley will delivered as an upgrade to devices running Windows 10, beginning in the first half of 2022. Windows Sun Valley will also be available on new, eligible devices. +- For managed PCs that meet requirements, the upgrade will be provided using the same processes that you use today for feature updates. For more information, see [Management tools](windows-sv-prepare.md#management-tools). - For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update using [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860). Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. -- You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). +- You can get early access to test Windows Sun Valley by joining the the Windows Insider Program [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). @@ -52,7 +52,7 @@ For more information about eligibility to upgrade, see [Windows Sun Valley requi There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. -Microsoft 365 licenses that include Windows licenses will permit you to run Windows Sun Valley on supported devices. +Microsoft 365 licenses that include Windows 10 licenses will permit you to run Windows Sun Valley on supported devices. If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. @@ -74,7 +74,9 @@ Most accessories and associated software that worked with Windows 10 are expecte ### Application compatibility -Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility) +Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. + +For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility) ## Windows Sun Valley servicing @@ -82,7 +84,9 @@ For details about the Windows Sun Valley servicing cadence and lifecycle, see [W ## Windows 10 servicing -Windows 10 will continue to be supported with security updates until October 2025. For more information, see [Windows 10 lifecycle](windows-sv-plan.md#windows-10-lifecycle). +Windows 10 will continue to be supported with security updates until October 2025. + +For more information, see [Windows 10 lifecycle](windows-sv-plan.md#windows-10-lifecycle). ## Next steps From 2f475267baeea249e5c50f3650ff48ce34f11653 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Jun 2021 13:53:01 -0700 Subject: [PATCH 058/104] draft3 --- windows/whats-new/windows-sv-prepare.md | 29 +++++++++++++++++++------ 1 file changed, 22 insertions(+), 7 deletions(-) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 5b3b15b817..5c5f1687db 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -40,22 +40,37 @@ Two Microsoft services that work directly with you to ensure application compati - If you experience any issues with your apps and are enrolled in the App Assure service, Microsoft will help you identify the issue at no cost. App Assure works with you to troubleshoot the issue, determine the root cause, and can help fix the issue as well. App Assure is subscription based, but subscriptions are free for eligible customers with 150+ seats. - Test Base is Microsoft's intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Windows Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. -You can use [Desktop Analytics](/mem/configmgr/desktop-analytics/overview), to test application compatibility. To determine the impact of a potential application compatiblity issue, [assign priority to apps](/windows/deployment/update/plan-define-readiness#set-criteria-for-rating-apps) and then perform a [compatibility assessment](/mem/configmgr/desktop-analytics/compat-assessment). +You can also use [Desktop Analytics](/mem/configmgr/desktop-analytics/overview), to test application compatibility. To determine the impact of a potential application compatiblity issue, [assign priority to apps](/windows/deployment/update/plan-define-readiness#set-criteria-for-rating-apps) and then perform a [compatibility assessment](/mem/configmgr/desktop-analytics/compat-assessment). ## Management tools -The following updates are required to support deploying Windows Sun Valley: -- Configuration Manager should use the current branch. +The following updates are required to support deploying Windows Sun Valley. + +### Configuration Manager + +Configuration Manager should use the current branch. - You will easily be able to sync the new **Windows Sun Valley** product category and upgrade eligible devices. - Configuration Manager will prompt you to accept the End User License Agreement on behalf of the users in your organization. - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. -- If you use Windows Server Update Services (WSUS), you will need to sync the new Windows Sun Valley category. -- Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). + +### WSUS + +If you use Windows Server Update Services (WSUS), you will need to sync the new Windows Sun Valley category. + +### WUfB + +Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and Safeguard holds. Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. -- No action is required for you to use Microsoft Intune because it is cloud-based. + +### Microsoft Intune + +No infrastructure update is required for you to use Microsoft Intune because it is cloud-based. - If you are using MEM Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley. -- Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience (OOBE) environment. + +### Windows Autopilot + +Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience (OOBE) environment. - In an Intune environment, a Windows Sun Valley boot image needs to already exist on the device for Windows Autopilot to work with Windows Sun Valley. - If the device comes with a Windows 10 boot image, an administrator can use Windows Autopilot to deploy Windows 10, and then use WUfB to upgrade to Windows Sun Valley. - To use [Windows Autopilot to upgrade existing devices](/mem/autopilot/existing-devices), Configuration Manager and the task sequence: **Windows Autopilot for existing devices** can place the Windows Sun Valley boot image on the managed device, allowing Windows Autopilot to deploy Windows Sun Valley. From beb49f84712f572ce319e480a1d6952b9bf9c583 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Jun 2021 13:56:14 -0700 Subject: [PATCH 059/104] draft4 --- windows/whats-new/windows-sv.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 50c3f38aa3..c1c31de0c4 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -80,13 +80,13 @@ For more information, see [Application compatibility](windows-sv-prepare.md#appl ## Windows Sun Valley servicing -For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](windows-sv-plan.md#servicing). +For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). ## Windows 10 servicing Windows 10 will continue to be supported with security updates until October 2025. -For more information, see [Windows 10 lifecycle](windows-sv-plan.md#windows-10-lifecycle). +For more information, see [Windows 10 coexistence](windows-sv-plan.md#windows-10-coexistence). ## Next steps From ed7b18112ed0e515ef463044c6341429cae10b9a Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Jun 2021 14:00:15 -0700 Subject: [PATCH 060/104] draft5 --- windows/whats-new/windows-sv-prepare.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 5c5f1687db..9bc3e59982 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -50,18 +50,18 @@ The following updates are required to support deploying Windows Sun Valley. Configuration Manager should use the current branch. - You will easily be able to sync the new **Windows Sun Valley** product category and upgrade eligible devices. - - Configuration Manager will prompt you to accept the End User License Agreement on behalf of the users in your organization. + - Configuration Manager will prompt you to accept the End User License Agreement (EULA) on behalf of the users in your organization. - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. ### WSUS -If you use Windows Server Update Services (WSUS), you will need to sync the new Windows Sun Valley category. +If you use Windows Server Update Services (WSUS), you will need to sync the new **Windows Sun Valley** category. ### WUfB Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. - - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and Safeguard holds. Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. + - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and [Safeguard holds](/windows/deployment/update/safeguard-holds). Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. ### Microsoft Intune From 00d940e661cdf570067ac61ae2bad4b5daaa5da7 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 15 Jun 2021 10:52:39 -0700 Subject: [PATCH 061/104] edits --- windows/whats-new/windows-sv-plan.md | 28 +++++++------ windows/whats-new/windows-sv-prepare.md | 42 ++++++++++---------- windows/whats-new/windows-sv-requirements.md | 7 ++-- windows/whats-new/windows-sv.md | 15 +++---- 4 files changed, 50 insertions(+), 42 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 8904cf19e3..ff388e1c4f 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -22,7 +22,9 @@ ms.topic: article ## Deployment planning -This article provides planning guidance to deploy Windows Sun Valley, specifically: +Windows Sun Valley is developed with Windows 10 as its foundation, enabling you to plan, prepare, deploy, and manage Windows Sun Valley with the same tools and methods that you use for Windows 10. As you integrate Windows Sun Valley into your environment, there will be some unique but familiar considerations as you work with a mix of Windows 10 and Windows Sun Valley devices side-by-side. + +This article provides planning guidance to help you begin depoying Windows Sun Valley, specifically: - Adoption guidance - Infrastructure planning @@ -30,9 +32,9 @@ This article provides planning guidance to deploy Windows Sun Valley, specifical - Application readiness - Functionality and coexistence with Windows 10 ecosystems -### Deployment process +#### Deployment process -Consider using the following process to deploy Windows Sun Valley: +Consider using the following processes to deploy Windows Sun Valley: 1. Preview Windows Sun Valley and create a deployment plan. 2. Test critical applications and management policies. 3. Update devices to the Windows 10, version 20H1 or later. @@ -40,7 +42,7 @@ Consider using the following process to deploy Windows Sun Valley: 5. Update deployment tools, infrastructure, and policies. 6. Update qualifying devices to Windows Sun Valley. -### Phased deployment +#### Phased deployment A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is is described in the [service management model](/windows/deployment/update/create-deployment-plan) that is recommended for Windows 10 updates. It includes separate groups or 'rings' of devices that receive updates based on their role in your deployment plan. For example: - Preview: Windows Sun Valley planning and development @@ -49,15 +51,15 @@ A phased deployment model is recommended for rolling out upgrades to devices in With this method, you define the timing and scope of devices that will migrate to Windows Sun Valley, documenting and validating each phase before moving to the next one. -Use a [calendar based approach](/windows/deployment/update/plan-define-strategy#calendar-approaches) to plan Windows Sun Valley upgrades, and include scheduling of future Windows 10 and Windows Sun Valley updates. The calendar based approach can be very useful for update planning in a mixed Windows 10 and Windows Sun Valley enviroment. - Also consider [assigning roles](/windows/deployment/update/plan-define-readiness) within your organization to groups and individuals you'll need to carry out specific tasks, if you have not already done so. ## Infrastructure and tools You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, as well as using them to move between the two products beginning on the General Availability (GA) date for Windows Sun Valley. -As part of your deployment planning, you will need to [evaluate your infrastructure](/windows/deployment/update/eval-infra-tools) and tools to verify they can support deployment and updates for Windows Sun Valley. For more information about updates to support the deployment of Windows Sun Valley, see [Management tools](windows-sv-prepare.md#management-tools). +For information about updates that are required to support the deployment of Windows Sun Valley, see [Management tools](windows-sv-prepare.md#management-tools). + +Also see [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) for a list of tasks related to deploying feature updates. ## Configurations @@ -68,15 +70,15 @@ Assess your current [configurations](/windows/deployment/update/eval-infra-tools ## Windows Sun Valley servicing -### Cadence +#### Cadence Windows Sun Valley feature updates will be released once per year, in the second half of the year. Quality updates will be released each month, on the second Tuesday of the month. -Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. +Microsoft will continue to provide one cumulative package that includes all latest cumulative updates and servicing stack updates, if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. -### Lifecycle +#### Lifecycle -Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. See the following table:
 
+Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. This is a different servicing lifecycle than that for [Windows 10 release information](/windows/release-health/release-information). See the following table:
 
| 24 months from the release date | 36 months from the release date | @@ -86,7 +88,9 @@ Windows Sun Valley annual releases are supported for 24 months or 36 months, dep | Windows Sun Valley Pro for Workstations | | | Windows Sun Valley Pro Education | | -### Features and applications +A long term servicing channel release of Windows Sun Valley is not planned at this time. + +#### Features and applications Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 9bc3e59982..85f8bd4b1b 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -40,35 +40,18 @@ Two Microsoft services that work directly with you to ensure application compati - If you experience any issues with your apps and are enrolled in the App Assure service, Microsoft will help you identify the issue at no cost. App Assure works with you to troubleshoot the issue, determine the root cause, and can help fix the issue as well. App Assure is subscription based, but subscriptions are free for eligible customers with 150+ seats. - Test Base is Microsoft's intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Windows Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. -You can also use [Desktop Analytics](/mem/configmgr/desktop-analytics/overview), to test application compatibility. To determine the impact of a potential application compatiblity issue, [assign priority to apps](/windows/deployment/update/plan-define-readiness#set-criteria-for-rating-apps) and then perform a [compatibility assessment](/mem/configmgr/desktop-analytics/compat-assessment). +You can also use [Endpoint Analytics](/mem/analytics/app-reliability), to test application compatibility. ## Management tools The following updates are required to support deploying Windows Sun Valley. -### Configuration Manager - -Configuration Manager should use the current branch. - - You will easily be able to sync the new **Windows Sun Valley** product category and upgrade eligible devices. - - Configuration Manager will prompt you to accept the End User License Agreement (EULA) on behalf of the users in your organization. - - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. - -### WSUS - -If you use Windows Server Update Services (WSUS), you will need to sync the new **Windows Sun Valley** category. - -### WUfB - -Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). - - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. - - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and [Safeguard holds](/windows/deployment/update/safeguard-holds). Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. - -### Microsoft Intune +#### Microsoft Intune No infrastructure update is required for you to use Microsoft Intune because it is cloud-based. - If you are using MEM Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley. -### Windows Autopilot +#### Windows Autopilot Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience (OOBE) environment. - In an Intune environment, a Windows Sun Valley boot image needs to already exist on the device for Windows Autopilot to work with Windows Sun Valley. @@ -76,6 +59,25 @@ Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience - To use [Windows Autopilot to upgrade existing devices](/mem/autopilot/existing-devices), Configuration Manager and the task sequence: **Windows Autopilot for existing devices** can place the Windows Sun Valley boot image on the managed device, allowing Windows Autopilot to deploy Windows Sun Valley. - Windows Autopilot cannot be used to downgrade a device from Windows Sun Valley to Windows 10. +#### Configuration Manager + +Configuration Manager should use the current branch. + - You will easily be able to sync the new **Windows Sun Valley** product category and upgrade eligible devices. + - Configuration Manager will prompt you to accept the End User License Agreement (EULA) on behalf of the users in your organization. + - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. + +#### WSUS + +If you use Windows Server Update Services (WSUS), you will need to sync the new **Windows Sun Valley** category. + +#### WUfB + +Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). + - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. + - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and [Safeguard holds](/windows/deployment/update/safeguard-holds). Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. + + + ## See also [Windows Sun Valley deployment planning](windows-sv-plan.md) diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 22999267a0..1ec42163e8 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -22,14 +22,15 @@ ms.custom: seo-marvel-apr2020 - Windows Sun Valley, version 21H2 -This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley is also supported on a Virtual Machine (VM). +This article lists the software and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley is also supported on a Virtual Machine (VM). ## Software requirements The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or later, on eligible hardware. -S mode is not supported on Windows Sun Valley. -- If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. +> [!NOTE] +> S mode is not supported on Windows Sun Valley. +> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. ## Hardware requirements diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index c1c31de0c4..21147d17cf 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -42,13 +42,13 @@ All upgrades to Windows Sun Valley from Windows 10 will be free. ## How to get Windows Sun Valley Windows Sun Valley will delivered as an upgrade to devices running Windows 10, beginning in the first half of 2022. Windows Sun Valley will also be available on new, eligible devices. -- For managed PCs that meet requirements, the upgrade will be provided using the same processes that you use today for feature updates. For more information, see [Management tools](windows-sv-prepare.md#management-tools). -- For unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update using [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860). Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. +- For PCs that are managed by your organization and meet requirements, the upgrade will be provided using the same processes that you use today for feature updates. For more information, see [Management tools](windows-sv-prepare.md#management-tools). +- For personal devices and other unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update using [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860). Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. - You can get early access to test Windows Sun Valley by joining the the Windows Insider Program [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). -### Licensing +#### Licensing There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. @@ -56,7 +56,7 @@ Microsoft 365 licenses that include Windows 10 licenses will permit you to run W If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. -### Rollback +#### Rollback After you have upgraded to Windows Sun Valley, you have 10 days to use the rollback function if you wish to move back to Windows 10 while keeping your files and data. After the 10 day grace period, you will need to back up your data and perform a clean install to move back to Windows 10. @@ -64,15 +64,15 @@ After you have upgraded to Windows Sun Valley, you have 10 days to use the rollb Windows Sun Valley is built on the same foundation as Windows 10, so you can generally deploy, manage, and secure Sun Valley using the same tools and solutions you use today. -### Management and tools +#### Management and tools You can use your current management tools, processes, and settings to manage quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools) and [Configurations](windows-sv-plan.md#configurations). -### Hardware compatibility +#### Hardware compatibility Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. -### Application compatibility +#### Application compatibility Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. @@ -90,5 +90,6 @@ For more information, see [Windows 10 coexistence](windows-sv-plan.md#windows-10 ## Next steps +[Windows Sun Valley requirements](windows-sv-requirements.md) [Plan to deploy Windows Sun Valley](windows-sv-plan.md)
[Prepare for Windows Sun Valley](windows-sv-prepare.md) From e627e8b1daeee9f0fe8bd27b8434e37b5ac211d6 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 15 Jun 2021 11:07:22 -0700 Subject: [PATCH 062/104] edits --- windows/whats-new/windows-sv-plan.md | 12 ++++++------ windows/whats-new/windows-sv-prepare.md | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index ff388e1c4f..76f9576c7b 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -22,7 +22,7 @@ ms.topic: article ## Deployment planning -Windows Sun Valley is developed with Windows 10 as its foundation, enabling you to plan, prepare, deploy, and manage Windows Sun Valley with the same tools and methods that you use for Windows 10. As you integrate Windows Sun Valley into your environment, there will be some unique but familiar considerations as you work with a mix of Windows 10 and Windows Sun Valley devices side-by-side. +Windows Sun Valley is developed with Windows 10 as its foundation, enabling you to plan, prepare, deploy, and manage Windows Sun Valley with the same tools and methods that you use for Windows 10. As you integrate Windows Sun Valley into your environment, there will be some unique but familiar considerations working with a mix of Windows 10 and Windows Sun Valley devices side-by-side. This article provides planning guidance to help you begin depoying Windows Sun Valley, specifically: @@ -32,14 +32,14 @@ This article provides planning guidance to help you begin depoying Windows Sun V - Application readiness - Functionality and coexistence with Windows 10 ecosystems -#### Deployment process +#### Deployment processes Consider using the following processes to deploy Windows Sun Valley: -1. Preview Windows Sun Valley and create a deployment plan. -2. Test critical applications and management policies. +1. [Preview Windows Sun Valley](windows-sv.md#how-to-get-windows-sun-valley) and create a deployment plan. +2. [Test critical applications](windows-sv-prepare.md#application-compatibility) and management policies. 3. Update devices to the Windows 10, version 20H1 or later. -4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. -5. Update deployment tools, infrastructure, and policies. +4. Verify that devices meet the [minimum hardware requirements](windows-sv-requirements.md#hardware-requirements) for Windows Sun Valley. +5. [Update](windows-sv-prepare.md#management-tools) deployment tools, infrastructure, and policies. 6. Update qualifying devices to Windows Sun Valley. #### Phased deployment diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 85f8bd4b1b..0c7db4b32a 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -49,7 +49,7 @@ The following updates are required to support deploying Windows Sun Valley. #### Microsoft Intune No infrastructure update is required for you to use Microsoft Intune because it is cloud-based. - - If you are using MEM Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley. + - If you are using Microsoft Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley. #### Windows Autopilot From a69125e9db70b097b651f720b7c51fd66641cde8 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 15 Jun 2021 11:21:17 -0700 Subject: [PATCH 063/104] ms.technology removed --- windows/whats-new/docfx.json | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/whats-new/docfx.json b/windows/whats-new/docfx.json index 04908deceb..16f6364ce9 100644 --- a/windows/whats-new/docfx.json +++ b/windows/whats-new/docfx.json @@ -34,7 +34,6 @@ "globalMetadata": { "breadcrumb_path": "/windows/windows-10/breadcrumb/toc.json", "uhfHeaderId": "MSDocsHeader-M365-IT", - "ms.technology": "windows", "ms.topic": "article", "audience": "ITPro", "feedback_system": "GitHub", From d517852fea164ac95a94868f2a46f49f483a3c3f Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 15 Jun 2021 13:03:47 -0700 Subject: [PATCH 064/104] edits --- windows/whats-new/windows-sv-plan.md | 7 ++++--- windows/whats-new/windows-sv.md | 2 +- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 76f9576c7b..9afc2d8cc7 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -22,7 +22,7 @@ ms.topic: article ## Deployment planning -Windows Sun Valley is developed with Windows 10 as its foundation, enabling you to plan, prepare, deploy, and manage Windows Sun Valley with the same tools and methods that you use for Windows 10. As you integrate Windows Sun Valley into your environment, there will be some unique but familiar considerations working with a mix of Windows 10 and Windows Sun Valley devices side-by-side. +Windows Sun Valley is developed with Windows 10 as its foundation, enabling you to plan, prepare, deploy, and manage Windows Sun Valley with the same tools and methods that you use for Windows 10. When you integrate Windows Sun Valley into your environment, there will be some unique but familiar considerations, as you work with a mix of Windows 10 and Windows Sun Valley devices side-by-side. This article provides planning guidance to help you begin depoying Windows Sun Valley, specifically: @@ -32,9 +32,10 @@ This article provides planning guidance to help you begin depoying Windows Sun V - Application readiness - Functionality and coexistence with Windows 10 ecosystems -#### Deployment processes +#### Deployment process + +Consider the following steps to deploy Windows Sun Valley in your environment: -Consider using the following processes to deploy Windows Sun Valley: 1. [Preview Windows Sun Valley](windows-sv.md#how-to-get-windows-sun-valley) and create a deployment plan. 2. [Test critical applications](windows-sv-prepare.md#application-compatibility) and management policies. 3. Update devices to the Windows 10, version 20H1 or later. diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 21147d17cf..3f327156fc 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -90,6 +90,6 @@ For more information, see [Windows 10 coexistence](windows-sv-plan.md#windows-10 ## Next steps -[Windows Sun Valley requirements](windows-sv-requirements.md) +[Windows Sun Valley requirements](windows-sv-requirements.md)
[Plan to deploy Windows Sun Valley](windows-sv-plan.md)
[Prepare for Windows Sun Valley](windows-sv-prepare.md) From 662a4e02ecbe21196549f980a36787f47f543e41 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 15 Jun 2021 13:18:29 -0700 Subject: [PATCH 065/104] edits --- windows/whats-new/windows-sv-plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 9afc2d8cc7..d6b6b7cde3 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -36,7 +36,7 @@ This article provides planning guidance to help you begin depoying Windows Sun V Consider the following steps to deploy Windows Sun Valley in your environment: -1. [Preview Windows Sun Valley](windows-sv.md#how-to-get-windows-sun-valley) and create a deployment plan. +1. [Preview Windows Sun Valley](windows-sv.md#how-to-get-windows-sun-valley) and create a phased deployment plan. 2. [Test critical applications](windows-sv-prepare.md#application-compatibility) and management policies. 3. Update devices to the Windows 10, version 20H1 or later. 4. Verify that devices meet the [minimum hardware requirements](windows-sv-requirements.md#hardware-requirements) for Windows Sun Valley. From cd204dd5cde3599646391b705ba17ff7857cfa9d Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 15 Jun 2021 14:06:10 -0700 Subject: [PATCH 066/104] edits --- windows/whats-new/windows-sv-plan.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index d6b6b7cde3..95f8c84268 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -89,8 +89,6 @@ Windows Sun Valley annual releases are supported for 24 months or 36 months, dep | Windows Sun Valley Pro for Workstations | | | Windows Sun Valley Pro Education | | -A long term servicing channel release of Windows Sun Valley is not planned at this time. - #### Features and applications Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. From d8af561f11b372e4647544b91b790a89b71a09bc Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 16 Jun 2021 10:17:59 -0700 Subject: [PATCH 067/104] incorp white paper --- windows/whats-new/windows-sv.md | 64 +++++++++++++-------------------- 1 file changed, 24 insertions(+), 40 deletions(-) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 3f327156fc..eabaaffd5c 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -24,69 +24,53 @@ ms.custom: seo-marvel-apr2020 This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. -The following articles are available to learn about Windows Sun Valley: +Also see the following articles to learn about Windows Sun Valley: -1. Windows Sun Valley overview (this article): An introduction and brief overview. -2. [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. -3. [Planning for Windows Sun Valley](windows-sv-plan.md): Information to help you create a Windows Sun Valley deployment plan. -4. [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. +- [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. +- [Planning for Windows Sun Valley](windows-sv-plan.md): Information to help you create a Windows Sun Valley deployment plan. +- [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. ## Introduction -Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. Windows Sun Valley is designed to support today's flexible [hybrid work](https://pulse.microsoft.com/the-journey-to-the-new-normal-driving-innovation-and-productivity-in-a-hybrid-world/) environment and to be the most reliable, secure, connected, and performant OS release ever. +Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers a fresh experience that is flexible and fluid, designed to support today's hybrid work environment and to be the most reliable, secure, connected, and performant Windows OS ever. -Windows Sun Valley is built on the same foundation as Windows 10, so you can deploy, manage, and secure Windows Sun Valley using the same tools and solutions you use today. +Windows Sun Valley contains many innovations focused on enhancing end user productivity. It is built on the same foundation as Windows 10, ensuring that the investments you have made in tools for update and device management are carried forward. Windows Sun Valley provides the benefits that commercial organizations and IT pros need and rely upon every day: best-in-class security, simplified manageability, and high availability. It also sustains the application compatibility promise we made with Windows 10, supplemented by programs like App Assure in cases where additional support is needed. -All upgrades to Windows Sun Valley from Windows 10 will be free. +In summary, because Windows Sun Valley is built on the same foundation as Windows 10, you can deploy, manage, and secure Windows SV using the same tools and solutions you use today. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows SV. ## How to get Windows Sun Valley -Windows Sun Valley will delivered as an upgrade to devices running Windows 10, beginning in the first half of 2022. Windows Sun Valley will also be available on new, eligible devices. -- For PCs that are managed by your organization and meet requirements, the upgrade will be provided using the same processes that you use today for feature updates. For more information, see [Management tools](windows-sv-prepare.md#management-tools). -- For personal devices and other unmanaged PCs that meet requirements, the upgrade will be offered through Windows Update using [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860). Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. -- You can get early access to test Windows Sun Valley by joining the the Windows Insider Program [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). +Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new, eligible devices. + +For PCs that are managed by your organization and meet the eligibility requirements, Windows Sun Valley will be available through the same, familiar channels we utilize for Windows 10 feature updates today. You will be able to use existing deployment and management toolsets, such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot and those commercial customers running Pro, Enterprise and Education editions of Windows 10 will have control over when to upgrade their devices from Windows 10 to Windows Sun Valley. For more information, see Management tools. + +For personal devices and other unmanaged PCs that meet the eligibility requirements, the upgrade will be offered through Windows Update using our intelligent rollout process to ensure a smooth upgrade experience. Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. + +For those interested in testing Windows Sun Valley before general availability, we recommend joining the Windows Insider Program or Windows Insider Program for Business [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), or enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). +## Before you begin + #### Licensing There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. -Microsoft 365 licenses that include Windows 10 licenses will permit you to run Windows Sun Valley on supported devices. +Microsoft 365 licenses that include Windows 10 licenses will permit you to run Windows Sun Valley on supported devices. If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. -If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. +#### Compatibility -#### Rollback +Most accessories and associated drivers that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. -After you have upgraded to Windows Sun Valley, you have 10 days to use the rollback function if you wish to move back to Windows 10 while keeping your files and data. After the 10 day grace period, you will need to back up your data and perform a clean install to move back to Windows 10. +Windows Sun Valley also preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility). -## Compatibility +#### Familiar deployment process -Windows Sun Valley is built on the same foundation as Windows 10, so you can generally deploy, manage, and secure Sun Valley using the same tools and solutions you use today. +Windows Sun Valley is built on the same foundation as Windows 10, so you can generally use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. You can also use your current management tools, processes, and settings to manage monthly quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools) and [Configurations](windows-sv-plan.md#configurations). -#### Management and tools +#### Servicing Windows Sun Valley -You can use your current management tools, processes, and settings to manage quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools) and [Configurations](windows-sv-plan.md#configurations). - -#### Hardware compatibility - -Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. - -#### Application compatibility - -Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Programs like App Assure and FastTrack for Microsoft M365 customers will continue to be available to support IT efforts to adopt and maintain Windows Sun Valley. - -For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility) - -## Windows Sun Valley servicing - -For details about the Windows Sun Valley servicing cadence and lifecycle, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). - -## Windows 10 servicing - -Windows 10 will continue to be supported with security updates until October 2025. - -For more information, see [Windows 10 coexistence](windows-sv-plan.md#windows-10-coexistence). +Windows Sun Valley will have an annual feature update cadence and receive monthly quality updates. For details, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available via a consolidated Windows Sun Valley update history page at that time as well. ## Next steps From d8e7613d44998aa49989e83f8aa3c68b3aa8c381 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 16 Jun 2021 12:30:35 -0700 Subject: [PATCH 068/104] incorp white paper --- windows/whats-new/windows-sv-plan.md | 165 ++++++++++--------- windows/whats-new/windows-sv-prepare.md | 63 +++---- windows/whats-new/windows-sv-requirements.md | 42 ++--- windows/whats-new/windows-sv.md | 2 +- 4 files changed, 133 insertions(+), 139 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 95f8c84268..1eed113eaa 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -1,5 +1,5 @@ --- -title: Plan to deploy Windows Sun Valley +title: Plan for Windows Sun Valley description: Windows Sun Valley deployment planning, IT Pro content. keywords: ["get started", "windows sun valley", "plan"] ms.prod: w11 @@ -14,7 +14,7 @@ ms.localizationpriority: high ms.topic: article --- -# Plan to deploy Windows Sun Valley +# Plan for Windows Sun Valley **Applies to** @@ -22,87 +22,104 @@ ms.topic: article ## Deployment planning -Windows Sun Valley is developed with Windows 10 as its foundation, enabling you to plan, prepare, deploy, and manage Windows Sun Valley with the same tools and methods that you use for Windows 10. When you integrate Windows Sun Valley into your environment, there will be some unique but familiar considerations, as you work with a mix of Windows 10 and Windows Sun Valley devices side-by-side. +This article provides guidance to help you plan for Windows Sun Valley in your organization. -This article provides planning guidance to help you begin depoying Windows Sun Valley, specifically: +Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment and servicing strategy. At a high level, this strategy should include the following steps: +- Create a deployment plan. +- Define readiness criteria. +- Evaluate current infrastructure and tools. +- Determine application readiness. +- Define your servicing strategy. + +As most organizations will have a mix of Windows Sun Valley and Windows 10 and SV devices side-by-side as they integrate SV into their environments, there are some unique yet largely familiar considerations for this new operating system to help in planning for upcoming deployments. + +#### Determine eligibility + +As a first step, you will need to know which of your current PCs meet the Windows Sun Valley hardware requirements. Detailed requirements can be found at [LINK NEEDED](). However, in general you should expect that if your devices were acquired within the last 18-24 months, they will be able to run Windows Sun Valley. + +Analysis tools will be created and made available to evaluate devices against the Windows Sun Valley hardware requirements. A standalone tool will be available, and the ability to evaluate upgrade eligibility will also be integrated into your existing enterprise tool sets. + +When Windows Sun Valley reaches general availability, end users running Windows 10 Home, Pro, and Pro for Workstations can use the PC Health Check app to determine their eligibility for Windows Sun Valley. End users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade. [LINK NEEDED]() has been developed for this purpose. + +For enterprise customers, analytics tools will be available for administrators to evaluate device readiness, including Endpoint Analytics and Update Compliance. Microsoft is also sharing information with independent sofware vendors to enable their tools to support analytics for Windows Sun Valley. + +#### Windows Sun Valley availability + +As with Windows 10, the availability of Windows Sun Valley experience will vary depending on whether the device receives updates from Windows Update (unmanaged devices), or from a management solution that is maintained by an administrator (managed devices). + +##### Unmanaged devices + +For unmanaged devices, most eligible devices purchased after June of 2021 will be offered the Windows Sun Valley upgrade in October of 2021. New device messaging will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. + +> [!NOTE] +> New devices purchased after October 2021 will see the Windows Sun Valley offer during the out of box experience, or they will already be upgraded to Windows Sun Valley. + +After General Availability (GA) date for Windows Sun Valley, the OS upgrade will be available to eligible Windows 10 devices that use Windows Update. The upgrade will be available first to seekers, then as part of Microsoft's intelligent rollout process. As with all Microsoft update managed devices, the Windows Update Settings page will confirm when a device is eligible, and users can choose to upgrade or not. + +Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience and ensures that devices first nominated for updates are those likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. + +##### Managed devices + +The innovations and end user productivity improvements in Windows Sun Valley are exciting. However, the "right time" to upgrade will be different for each organization. For devices that you manage as an organization, you can choose between Windows Sun Valley and Windows 10, and decide when the time is right to incorporate Window Sun Valley into your environment. Initially, it is expected that enterprise environments will contain a mix of Windows 10 and Windows Sun Valley. + +Organizations will be able to deploy the Windows Sun Valley upgrade to eligible devices using their existing management tools beginning at GA. Environments that use Windows Update for Business (WUfB) will have the additional benefit of two safety nets: offering blocks on non-eligible devices who do not meet the hardware requirements, and Safeguard holds. Safeguard holds will function for SV devices just as they do for Windows 10. Administrators will have access to information on which Safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. + +> [!NOTE] +> If you use WUfB to manage feature update deployments today you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (Windows 10 to Windows 10), but they cannot migrate a devices between products (Windows 10 to Windows Sun Valley). +> Additionally, Windows Sun Valley has a new end user license agreement. If you are deploying with WUfB **Target Version** or with WSUS, you are accepting this new end user license agreement on behalf of the end users within your organization. + +Some additional considerations about upgrading: + +- Windows 10 Pro or higher can upgrade for free using existing management tools. +- Devices running S mode will first need to switch out of S mode because it is not supported on Windows Sun Valley. +- Downgrade rights are available with Windows Sun Valley Pro OEM licensed devices and with Microsoft Volume Licensing, where the licensing agreement permits it. +- You can downgrade to any version of Windows Pro/Professional that has not reached its end of support date. + +##### Availability and upgrade path + +As previously mentioned, the Windows Sun Valley upgrade offer will begin for eligible devices at GA in October of 2021. This is true for eligible devices already running updated Windows 10 as well as for new devices. + +To preview Windows Sun Valley, you can join the [Windows Insider Program](https://insider.windows.com/for-business) (WIP). This enables you to begin validating Windows Sun Valley, as well as exploring new features as they’re being created. As a WIP participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), Windows Sun Valley will be available to you in the summer of 2021, well ahead of the October GA date. + +You can deploy directly from the Windows Insider Pre-release category in WSUS in a variety of ways: +1. Configure Manage Preview Builds to **Release Preview** with WUfB. +2. Leverage Windows Virtual Devices or Cloud PC* (check if this will be announced when this paper goes out) and Azure Marketplace images. +3. Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. + +Regardless of which way you choose to deploy, you have the benefit of free Microsoft support when validating a pre-release. All you need to do is go to [Support for business](http://support.microsoft.com/supportforbusiness/productselection?sapId=39fc4a93-68cd-5a19-f91b-f0b349a098f3) and submit your support case. This is free for any Microsoft commercial customer deploying Windows 10 version 21H2 or Windows Sun Valley 21H2 pre-release bits after the commercial preview date in summer 2021. + +Your Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. Windows Sun Valley devices will receive a single feature update annually, a change from the twice per year of Windows 10. + +Devices on in-service versions of Windows 10 that do not meet Windows Sun Valley hardware requirements will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support your ongoing deployments of Microsoft 365. + +##### Servicing duration + +Along with end user experience and security improvements, Windows Sun Valley introduces enhancements to our servicing approach based on your suggestions and feedback. + +Windows 10 feature updates are released twice yearly via the Semi-Annual Channel. They are serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy. Windows Sun Valley will have an annual feature update cadence, targeted for release in the second half of the calendar year. +- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the date of release. +- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months. + +For more details on the lifecycle and servicing strategy for Windows Sun Valley, see [Windows lifecycle and servicing update overview](). - - Adoption guidance - - Infrastructure planning - - Servicing cadence and lifecycle - - Application readiness - - Functionality and coexistence with Windows 10 ecosystems +Microsoft recognizes the importance that organizations have adequate time to plan for Windows Sun Valley. Therefore, we have committed to supporting Windows 10 through October 14, 2025. For more information, see the [Windows release information]() page. This page also includes information for Windows 10 semi-annual channel and LTSC releases. -#### Deployment process +A consolidated [update history]() is also available for every version of the Windows operating system. This information offers quick access to knowledge base articles for each monthly, optional, and out-of-band release. In addition to update highlights, you’ll find a list of improvements and fixes, a summary of any known issues, and details on how to get the update, including any prerequisites. -Consider the following steps to deploy Windows Sun Valley in your environment: +##### Application compatibility -1. [Preview Windows Sun Valley](windows-sv.md#how-to-get-windows-sun-valley) and create a phased deployment plan. -2. [Test critical applications](windows-sv-prepare.md#application-compatibility) and management policies. -3. Update devices to the Windows 10, version 20H1 or later. -4. Verify that devices meet the [minimum hardware requirements](windows-sv-requirements.md#hardware-requirements) for Windows Sun Valley. -5. [Update](windows-sv-prepare.md#management-tools) deployment tools, infrastructure, and policies. -6. Update qualifying devices to Windows Sun Valley. +Windows 10 upgrades have proven to be highly compatible, and that does not change with Windows Sun Valley. Our compatibility promise for Windows 10 is that upgrades will maintain compatibility with apps written for previously released versions. Windows Sun Valley comes with the same App Assure promise and commitment that you have known with Windows 10. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for our enterprise customers, including line of business apps. This great progress will not be lost. Windows Sun Valley has been subjected to, and is passing the same app compatibility validation requirements, that are in place for Windows 10 feature and quality update releases today. -#### Phased deployment +##### App Assure and Test Base -A phased deployment model is recommended for rolling out upgrades to devices in your organization. This is is described in the [service management model](/windows/deployment/update/create-deployment-plan) that is recommended for Windows 10 updates. It includes separate groups or 'rings' of devices that receive updates based on their role in your deployment plan. For example: -- Preview: Windows Sun Valley planning and development -- Limited: Windows Sun Valley pilot deployment -- Broad: Windows Sun Valley rollout +You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. With enrollment in the App Assure service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. -With this method, you define the timing and scope of devices that will migrate to Windows Sun Valley, documenting and validating each phase before moving to the next one. - -Also consider [assigning roles](/windows/deployment/update/plan-define-readiness) within your organization to groups and individuals you'll need to carry out specific tasks, if you have not already done so. - -## Infrastructure and tools - -You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, as well as using them to move between the two products beginning on the General Availability (GA) date for Windows Sun Valley. - -For information about updates that are required to support the deployment of Windows Sun Valley, see [Management tools](windows-sv-prepare.md#management-tools). - -Also see [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) for a list of tasks related to deploying feature updates. - -## Configurations - -Assess your current [configurations](/windows/deployment/update/eval-infra-tools#configuration-updates) such as security baselines, administrative templates, and policies that affect updates. Then, set some criteria to define your [operational readiness](/windows/deployment/update/eval-infra-tools#define-operational-readiness-criteria), Define an infrastructure update plan to: -- Review requirements -- Identify gaps -- Implement required updates - -## Windows Sun Valley servicing - -#### Cadence - -Windows Sun Valley feature updates will be released once per year, in the second half of the year. Quality updates will be released each month, on the second Tuesday of the month. - -Microsoft will continue to provide one cumulative package that includes all latest cumulative updates and servicing stack updates, if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. - -#### Lifecycle - -Windows Sun Valley annual releases are supported for 24 months or 36 months, depending on the edition. This is a different servicing lifecycle than that for [Windows 10 release information](/windows/release-health/release-information). See the following table:
 
- - -| 24 months from the release date | 36 months from the release date | -| ------------------------------- | ------------------------------- | -| Windows Sun Valley Home | Windows Sun Valley Enterprise | -| Windows Sun Valley Pro | Windows Sun Valley Education | -| Windows Sun Valley Pro for Workstations | | -| Windows Sun Valley Pro Education | | - -#### Features and applications - -Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. - -## Application readiness - -Windows Sun Valley is designed to work with the applications you are currently using with Windows 10. If an application compatibility issue is identified, Microsoft provides services to help you remediate the problem. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility). - -## Windows 10 coexistence - -For organizations that need to maintain a mixed enviroment with coexisting Windows 10 and Windows Sun Valley devices, Microsoft’s guidance is to standardize on Windows 10, version 21H2. This release will be the last feature update to Windows 10, and will receive specific feature enhancements to ease migrating to Windows Sun Valley. - -Windows 10 will continue to be supported with security updates until October 2025. +If you’ve created your own applications, Test Base for Microsoft is a service that allows independent software vendors and commercial customers to validate their apps across a variety of updates and environments in a Microsoft managed Azure environment. Both services can be of benefit to you as you roll out Windows Sun Valley into your environment. ## Next steps [Prepare for Windows Sun Valley](windows-sv-prepare.md) + +## Also see + +Learning module diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 0c7db4b32a..c617d105a9 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -20,64 +20,51 @@ ms.topic: article - Windows Sun Valley, version 21H2 -## Deployment readiness -This article provides details on how to begin testing and validating Windows Sun Valley in your environment, and prepare for deployment. Links are also provided to important resource locations for more information. +Organizations will vary in their pace relative to transitioning from Windows 10 to SV, and we expect early corporate adoptions to consist of smaller test environments before rolling out to wider groups begins. We are committed to supporting you through your migration to Windows Sun Valley whether you are a fast adopter, or will make the transition over the coming months or years. -To prepare for deployment of Windows Sun Valley, you will need to implement your [planned updates](windows-sv-plan.md) to infrastructure, settings, and tools, including: -- Test your critical applications and management policies -- Update devices to Windows 10, version 20H1 or later -- Verify hardware meets requirements for Windows Sun Valley -- Update your management tools, infrastructure, and policies -- [Prepare users](/windows/deployment/update/prepare-deploy-windows#prepare-users) for Windows Sun Valley. +With the new Windows Sun Valley experience, hybrid environments of both operating systems running simultaneously will be the norm. Windows 10 and Windows Sun Valley are designed to co-exist during this time, so that you can use the same familiar tools and process to manage them, as well as continue to give your users the best Microsoft 365 experience. You’ll have one common management infrastructure, and support for common applications across both Windows 10 and Windows Sun Valley to simplify the migration process. You’ll use the IT Pro tools that you are familiar with and have been using in the past to prepare for deployments also work in Windows Sun Valley; you can analyze endpoints, determine application compatibility, and manage deployments in the same way you did with Windows 10. -After completing these actions, you can begin your phased deployment of Windows Sun Valley. +As you prepare for Windows Sun Valley, it’s also a good time to look at the deployment infrastructure of your environment. If you aren’t already taking advantage of cloud-based management tools like Microsoft Endpoint Manager this might be the perfect scenario in which to make that leap. Or if you are exclusively using an on-premises management tool such as Configuration Manager, using Cloud management gateway, enabling tenant attach, or enabling co-management with Microsoft Intune are all ways to help keep devices secure and up-to-date. ---insert links for the named solutions -## Application compatibility +Additionally, policies related to deployment may need to be updated or re-evaluated respective of update compliance deadlines, device activity policies, and the re-evaluation of older policies. A servicing mindset pointed at keeping current means that, as with Windows 10 devices, you will create a deployment plan in order to build out your servicing strategy. -Two Microsoft services that work directly with you to ensure application compatibility with Windows Sun Valley are [App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure) and [Test Base](https://www.microsoft.com/testbase). +## Analytics -- If you experience any issues with your apps and are enrolled in the App Assure service, Microsoft will help you identify the issue at no cost. App Assure works with you to troubleshoot the issue, determine the root cause, and can help fix the issue as well. App Assure is subscription based, but subscriptions are free for eligible customers with 150+ seats. -- Test Base is Microsoft's intelligent application validation service that allows software vendors and commercial customers to test their applications. The Test Base test and validation environment runs Windows Sun Valley as well as Windows 10 with a matrix of updates and environments in a Microsoft managed Azure environment. You can get started by enrolling in Test Base for Microsoft 365. +If you’re a Microsoft Endpoint Manager customer, make sure you’ve onboarded your devices to Endpoint analytics. Later this year, we’ll be providing a hardware readiness assessment directly in Endpoint analytics so that you can quickly identify which of your managed devices meet or exceed the minimum hardware requirements. -You can also use [Endpoint Analytics](/mem/analytics/app-reliability), to test application compatibility. +If you’d rather start exploring Windows Sun Valley readiness within your organization right away, take advantage of our [hardware eligibility assessment script](add link). By following the instructions to deploy and aggregate results via Microsoft Intune or Configuration Manager, you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. ## Management tools -The following updates are required to support deploying Windows Sun Valley. +The toolset that you use for heavy lifting during deployments of Windows 10 are still able to be leveraged in Windows Sun Valley. There are a few nuanced differences described here: -#### Microsoft Intune +#### On-premises management -No infrastructure update is required for you to use Microsoft Intune because it is cloud-based. - - If you are using Microsoft Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley. +- Windows Server Update Service (WSUS): Commercial customers using WSUS will need to sync the new **Windows Sun Valley** product category. Once you sync the product category you will see the feature update to SV. Please note that during deployment you will be prompted to agree to the license agreement on behalf of your end users. Additionally, you will note there is no x86 (32 bit?) payload for Windows Sun Valley as such is no longer supported on Windows Sun Valley going forward. +- MEM Configuration Manager: For customers using MEM Configuration Manager, you will easily be able to sync the new “Windows Sun Valley” Product category and begin upgrading eligible devices. Please note that Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. If you would like to validate Windows Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. -#### Windows Autopilot +#### Cloud management -Windows Autopilot works seamlessly in a Windows Sun Valley Out-of-Box-Experience (OOBE) environment. - - In an Intune environment, a Windows Sun Valley boot image needs to already exist on the device for Windows Autopilot to work with Windows Sun Valley. - - If the device comes with a Windows 10 boot image, an administrator can use Windows Autopilot to deploy Windows 10, and then use WUfB to upgrade to Windows Sun Valley. - - To use [Windows Autopilot to upgrade existing devices](/mem/autopilot/existing-devices), Configuration Manager and the task sequence: **Windows Autopilot for existing devices** can place the Windows Sun Valley boot image on the managed device, allowing Windows Autopilot to deploy Windows Sun Valley. - - Windows Autopilot cannot be used to downgrade a device from Windows Sun Valley to Windows 10. +- Windows Update for Business (WUfB) Group Policy (GP) and Configuration Service Provider (CSP) policies: Commercial customers using WUfB will need to leverage the Target Version capability rather than feature update deferrals to move from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product, but do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether using WUfB through Group Policy Management Console (GPMC), MEM Intune, or other 3rd party management tools. +- MEM Intune: For customers using MEM Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley, version 21H2. You will be able to continue using the same update experience controls to manage the behavior of the device once updates are offered for either Windows 10, version 21H2 and Windows Sun Valley, version 21H2. -#### Configuration Manager +## Deploy Windows Sun Valley -Configuration Manager should use the current branch. - - You will easily be able to sync the new **Windows Sun Valley** product category and upgrade eligible devices. - - Configuration Manager will prompt you to accept the End User License Agreement (EULA) on behalf of the users in your organization. - - If you would like to validate Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. +Since your familiar Windows 10 toolsets are meant to be used with Windows Sun Valley as well, then managing, securing, and deploying Windows Sun Valley devices will be well known procedures in the plan, prepare and deploy process. -#### WSUS - -If you use Windows Server Update Services (WSUS), you will need to sync the new **Windows Sun Valley** category. - -#### WUfB - -Windows Update for Business (WUfB) users can leverage the **Target Version** capability (not Feature Update deferrals). - - Feature Update deferrals are great to move to newer versions of a product (for example: Windows 10 21H1 to Windows 10 21H2), but deferrals do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. - - WUfB has the additional benefit of two safety nets: offering blocks on non-eligible devices, and [Safeguard holds](/windows/deployment/update/safeguard-holds). Safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10. Administrators will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. +Just as we recommend that broad deployment of new versions of Windows 10 begin with a pilot deployment phase, Windows Sun Valley is no different. Further, in your blended environment of Windows 10-capable devices and Windows 10 + SV-eligible devices, you will be poised to roll out an update to a select number of devices. Once you’ve gone through the checklist of pilot deployment tasks such as assigning the pilot devices from your prepare phase, implementing baseline and operations updates, testing and supporting the devices, and so forth, you can deploy to your test group. We recommend cloud-based deployment solutions such as Microsoft Endpoint Manager to fully take advantage of data-driven insights, though Configuration Manager works as well. +Using artifacts from your Plan and Prepare phase (such as security and configuration baselines, etc.) as well as data from your test deployment, will give you the confidence you seek to manage a broader rollout of Windows Sun Valley to increasingly larger rings of eligible devices. Desktop Analytics will help you ensure that your apps are scoped to only the pilot rings you designate. +Though we’ve mentioned only a few, the tools and processes we have had in place for your previous 10 Windows deployment will be there for you with Windows Sun Valley as well. ## See also [Windows Sun Valley deployment planning](windows-sv-plan.md) + +• Windows release health: Windows release health offers the quickest way to stay up to date on update-related news, information, and best practices, including important lifecycle reminders and the status of known issues and safeguard holds. IT administrators have access to this information, plus additional details, within the health experience Microsoft 365 admin center. + +• Windows Tech Community: Offering technical professionals a place to discuss, share, troubleshoot, and learn around Windows, Tech Community is also the home of the Windows IT Pro Blog, our monthly Windows Office Hours events, and the Windows Video Hub. + +• Microsoft Learn: We are in the process of developing online learning paths and modules to help you and your organization effectively plan, prepare, and deploy Windows Sun Valley effectively. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 1ec42163e8..469fe1924c 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -1,7 +1,6 @@ --- title: Windows Sun Valley requirements description: Hardware requirements to deploy Windows Sun Valley -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C ms.reviewer: manager: laurawi ms.audience: itpro @@ -22,38 +21,29 @@ ms.custom: seo-marvel-apr2020 - Windows Sun Valley, version 21H2 -This article lists the software and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley is also supported on a Virtual Machine (VM). - -## Software requirements - -The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or later, on eligible hardware. - -> [!NOTE] -> S mode is not supported on Windows Sun Valley. -> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. +This article lists the system requirements for Windows Sun Valley. Windows Sun Valley is also supported on a virtual machine (VM). For the best Windows Sun Valley upgrade experience, eligible devices should be running Windows 10, version 20H1 or later. ## Hardware requirements To install Windows Sun Valley, devices must meet the following specifications: -Processor -- Intel 8th generation, Intel Celeron N4000, Pentium N5000 -- AMD Ryzen gen 2 (Zen+), AMD 3xxx -- Qualcomm 7c, 8c, 8cx -- 64bit architecture -- 1Ghz clock speed -- 2 cores - -Hardware -- 64GB drive -- 4GB RAM -- UEFI, Secure Boot capable & TPM 2.0 -- Monitor size 9” or more with HD Resolution -- DirectX 12 compatible graphics / WDDM 2.x +- Processor: 1 gigahertz (GHz) or faster processor or SoC; dual-core CPU or greater + - Intel 8th generation, Intel Celeron N4000, Pentium N5000 + - AMD Ryzen gen 2 (Zen+), AMD 3xxx + - Qualcomm 7c, 8c, 8cx -## Network requirements +- RAM: 4 gigabyte (GB) or greater +- Hard disk space: 64GB, 64-bit architecture +- Graphics card: DirectX 12 or later with WDDM 2.x driver +- Security: Trusted Platform Module (TPM) 2.0 chip, UEFI support, Secure Boot capable +- Display: 9" monitor size or greater with HD (1366 x 768) resolution or greater +- Internet connection: Internet connectivity is necessary to perform updates and to download and take advantage of some features. It is required for the Home edition of Windows Sun Valley. -Internet connectivity is required for the Home edition of Windows Sun Valley. +For additional guidance, see [Determine eligibility](windows-sv-plan.md#determine-eligibility) NEED LINK. + +> [!NOTE] +> S mode is not supported on Windows Sun Valley. +> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. Switching a device out of Windows 10 in S mode also requires internet connectivity. ## Next steps diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index eabaaffd5c..1e9127bae0 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -76,4 +76,4 @@ Windows Sun Valley will have an annual feature update cadence and receive monthl [Windows Sun Valley requirements](windows-sv-requirements.md)
[Plan to deploy Windows Sun Valley](windows-sv-plan.md)
-[Prepare for Windows Sun Valley](windows-sv-prepare.md) +[Prepare for Windows Sun Valley](windows-sv-prepare.md) \ No newline at end of file From dadbe6af01d60574508e5d36f41a0d262a1ce1c3 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 16 Jun 2021 14:35:00 -0700 Subject: [PATCH 069/104] incorp white paper --- windows/whats-new/windows-sv-plan.md | 56 ++++++++++---------- windows/whats-new/windows-sv-prepare.md | 2 +- windows/whats-new/windows-sv-requirements.md | 6 ++- windows/whats-new/windows-sv.md | 22 ++++---- 4 files changed, 46 insertions(+), 40 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 1eed113eaa..310e572df1 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -31,86 +31,88 @@ Since Windows Sun Valley is built on the same foundation as Windows 10, you can - Determine application readiness. - Define your servicing strategy. -As most organizations will have a mix of Windows Sun Valley and Windows 10 and SV devices side-by-side as they integrate SV into their environments, there are some unique yet largely familiar considerations for this new operating system to help in planning for upcoming deployments. +Most organizations will have a mix of Windows Sun Valley and Windows 10 devices side-by-side as they integrate the upgrade into their environments. As such, there are unique yet largely familiar considerations to take into account when planning your deployments. -#### Determine eligibility +## Upgrade eligibility -As a first step, you will need to know which of your current PCs meet the Windows Sun Valley hardware requirements. Detailed requirements can be found at [LINK NEEDED](). However, in general you should expect that if your devices were acquired within the last 18-24 months, they will be able to run Windows Sun Valley. +As a first step, you will need to know which of your current PCs meet the Windows Sun Valley hardware requirements. Detailed requirements can be found [here](windows-sv-requirements.md). However, in general you should expect that if your devices were purchased within the last 18-24 months, they will be able to run Windows Sun Valley. -Analysis tools will be created and made available to evaluate devices against the Windows Sun Valley hardware requirements. A standalone tool will be available, and the ability to evaluate upgrade eligibility will also be integrated into your existing enterprise tool sets. +Analysis tools will be developed and made available to validate devices against the Windows Sun Valley hardware requirements. A standalone tool is planned, and upgrade eligibility will also be integrated into your existing enterprise deployment tools. When Windows Sun Valley reaches general availability, end users running Windows 10 Home, Pro, and Pro for Workstations can use the PC Health Check app to determine their eligibility for Windows Sun Valley. End users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade. [LINK NEEDED]() has been developed for this purpose. -For enterprise customers, analytics tools will be available for administrators to evaluate device readiness, including Endpoint Analytics and Update Compliance. Microsoft is also sharing information with independent sofware vendors to enable their tools to support analytics for Windows Sun Valley. +For organizations with investments in enterprise deployment tools, analytics functionality will be available to evaluate device readiness, including Endpoint Analytics and Update Compliance. Microsoft is also sharing information with independent sofware vendors to enable their tools to support analytics for Windows Sun Valley. -#### Windows Sun Valley availability +## Windows Sun Valley availability -As with Windows 10, the availability of Windows Sun Valley experience will vary depending on whether the device receives updates from Windows Update (unmanaged devices), or from a management solution that is maintained by an administrator (managed devices). +As with Windows 10, the availability of Windows Sun Valley will vary depending on whether the device is unmanaged and receives updates from Windows Update, or a device is managed using tools operated by an IT administrator. ##### Unmanaged devices -For unmanaged devices, most eligible devices purchased after June of 2021 will be offered the Windows Sun Valley upgrade in October of 2021. New device messaging will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. +For unmanaged devices, most eligible devices purchased after June of 2021 will be offered the Windows Sun Valley upgrade in October of 2021. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. > [!NOTE] -> New devices purchased after October 2021 will see the Windows Sun Valley offer during the out of box experience, or they will already be upgraded to Windows Sun Valley. +> New devices purchased after October 2021 will see the Windows Sun Valley offer during the out of box experience (OOBE), or they will already be upgraded to Windows Sun Valley. -After General Availability (GA) date for Windows Sun Valley, the OS upgrade will be available to eligible Windows 10 devices that use Windows Update. The upgrade will be available first to seekers, then as part of Microsoft's intelligent rollout process. As with all Microsoft update managed devices, the Windows Update Settings page will confirm when a device is eligible, and users can choose to upgrade or not. +After General Availability (GA) date for Windows Sun Valley, the OS upgrade will be available to eligible devices that use Windows Update. The upgrade will be available first to seekers, then as part of Microsoft's intelligent rollout process. The Windows Update Settings page will confirm when a device is eligible, and users can choose whether or not to upgrade. Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience and ensures that devices first nominated for updates are those likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. ##### Managed devices -The innovations and end user productivity improvements in Windows Sun Valley are exciting. However, the "right time" to upgrade will be different for each organization. For devices that you manage as an organization, you can choose between Windows Sun Valley and Windows 10, and decide when the time is right to incorporate Window Sun Valley into your environment. Initially, it is expected that enterprise environments will contain a mix of Windows 10 and Windows Sun Valley. +The right time to upgrade will be different for each organization and environment. You can choose between Windows Sun Valley and Windows 10, and decide when the time is right to integrate Window Sun Valley into your environment. Initially, it is expected that many organizations will operate with a mix of Windows 10 and Windows Sun Valley. -Organizations will be able to deploy the Windows Sun Valley upgrade to eligible devices using their existing management tools beginning at GA. Environments that use Windows Update for Business (WUfB) will have the additional benefit of two safety nets: offering blocks on non-eligible devices who do not meet the hardware requirements, and Safeguard holds. Safeguard holds will function for SV devices just as they do for Windows 10. Administrators will have access to information on which Safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. +You can deploy the Windows Sun Valley upgrade to eligible devices using your existing management tools beginning at GA. If you use Windows Update for Business (WUfB), you will have the additional benefit of two safety nets: offering blocks on non-eligible devices that do not meet the hardware requirements, and Safeguard holds. Safeguard holds will function for Windows Sun Valley devices the same way that they do for Windows 10. Administrators will have access to information on which Safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. > [!NOTE] -> If you use WUfB to manage feature update deployments today you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (Windows 10 to Windows 10), but they cannot migrate a devices between products (Windows 10 to Windows Sun Valley). -> Additionally, Windows Sun Valley has a new end user license agreement. If you are deploying with WUfB **Target Version** or with WSUS, you are accepting this new end user license agreement on behalf of the end users within your organization. +> If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (Windows 10 to Windows 10), but they cannot migrate a devices between products (Windows 10 to Windows Sun Valley).
+> Additionally, Windows Sun Valley has a new end user license agreement (EULA). If you are deploying with WUfB **Target Version** or with WSUS, you are accepting this new EULA on behalf of the end users within your organization. -Some additional considerations about upgrading: +Additional considerations: - Windows 10 Pro or higher can upgrade for free using existing management tools. - Devices running S mode will first need to switch out of S mode because it is not supported on Windows Sun Valley. - Downgrade rights are available with Windows Sun Valley Pro OEM licensed devices and with Microsoft Volume Licensing, where the licensing agreement permits it. -- You can downgrade to any version of Windows Pro/Professional that has not reached its end of support date. +- You can downgrade to any version of Windows Pro that has not reached its end of support date. -##### Availability and upgrade path +## Availability and upgrade path -As previously mentioned, the Windows Sun Valley upgrade offer will begin for eligible devices at GA in October of 2021. This is true for eligible devices already running updated Windows 10 as well as for new devices. +As previously mentioned, the Windows Sun Valley upgrade offer will begin for eligible devices at GA in October of 2021. This is true for existing eligible devices as well as for new devices. -To preview Windows Sun Valley, you can join the [Windows Insider Program](https://insider.windows.com/for-business) (WIP). This enables you to begin validating Windows Sun Valley, as well as exploring new features as they’re being created. As a WIP participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), Windows Sun Valley will be available to you in the summer of 2021, well ahead of the October GA date. +To preview Windows Sun Valley, you can join the [Windows Insider Program](https://insider.windows.com/for-business) (WIP). This enables you to begin validating Windows Sun Valley, and to explore new features as they’re being created. As a WIP participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), Windows Sun Valley will be available to you in the summer of 2021, well ahead of the October GA date. You can deploy directly from the Windows Insider Pre-release category in WSUS in a variety of ways: 1. Configure Manage Preview Builds to **Release Preview** with WUfB. 2. Leverage Windows Virtual Devices or Cloud PC* (check if this will be announced when this paper goes out) and Azure Marketplace images. 3. Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. -Regardless of which way you choose to deploy, you have the benefit of free Microsoft support when validating a pre-release. All you need to do is go to [Support for business](http://support.microsoft.com/supportforbusiness/productselection?sapId=39fc4a93-68cd-5a19-f91b-f0b349a098f3) and submit your support case. This is free for any Microsoft commercial customer deploying Windows 10 version 21H2 or Windows Sun Valley 21H2 pre-release bits after the commercial preview date in summer 2021. +Regardless of which way you choose to deploy, you have the benefit of free Microsoft support when validating a pre-release. Just go to [Support for business](http://support.microsoft.com/supportforbusiness/productselection?sapId=39fc4a93-68cd-5a19-f91b-f0b349a098f3) and submit your support case. This is free for any Microsoft commercial customer deploying Windows 10 version 21H2 or Windows Sun Valley 21H2 pre-release bits after the commercial preview date in the summer of 2021. -Your Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. Windows Sun Valley devices will receive a single feature update annually, a change from the twice per year of Windows 10. +## Quality updates -Devices on in-service versions of Windows 10 that do not meet Windows Sun Valley hardware requirements will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support your ongoing deployments of Microsoft 365. +- Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates. +- Windows Sun Valley devices will receive a single feature update annually, a change from the twice per year of Windows 10. +- Devices on in-service versions of Windows 10 that do not meet Windows Sun Valley hardware requirements will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support your ongoing deployments of Microsoft 365. -##### Servicing duration +## Servicing duration Along with end user experience and security improvements, Windows Sun Valley introduces enhancements to our servicing approach based on your suggestions and feedback. -Windows 10 feature updates are released twice yearly via the Semi-Annual Channel. They are serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy. Windows Sun Valley will have an annual feature update cadence, targeted for release in the second half of the calendar year. +Windows 10 feature updates are released twice yearly via the Semi-Annual Channel. They are serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy. Windows Sun Valley will have an annual feature update cadence, targeted for release in the second half of the calendar year: - Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the date of release. - Enterprise and Education editions of Windows Sun Valley will be supported for 36 months. -For more details on the lifecycle and servicing strategy for Windows Sun Valley, see [Windows lifecycle and servicing update overview](). +THIS SECTION DOESNT EXIST: For more details on the lifecycle and servicing strategy for Windows Sun Valley, see [Windows lifecycle and servicing update overview](). Microsoft recognizes the importance that organizations have adequate time to plan for Windows Sun Valley. Therefore, we have committed to supporting Windows 10 through October 14, 2025. For more information, see the [Windows release information]() page. This page also includes information for Windows 10 semi-annual channel and LTSC releases. A consolidated [update history]() is also available for every version of the Windows operating system. This information offers quick access to knowledge base articles for each monthly, optional, and out-of-band release. In addition to update highlights, you’ll find a list of improvements and fixes, a summary of any known issues, and details on how to get the update, including any prerequisites. -##### Application compatibility +## Application compatibility Windows 10 upgrades have proven to be highly compatible, and that does not change with Windows Sun Valley. Our compatibility promise for Windows 10 is that upgrades will maintain compatibility with apps written for previously released versions. Windows Sun Valley comes with the same App Assure promise and commitment that you have known with Windows 10. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for our enterprise customers, including line of business apps. This great progress will not be lost. Windows Sun Valley has been subjected to, and is passing the same app compatibility validation requirements, that are in place for Windows 10 feature and quality update releases today. -##### App Assure and Test Base +#### App Assure and Test Base You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. With enrollment in the App Assure service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index c617d105a9..8da15603d9 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -1,5 +1,5 @@ --- -title: Prepare to deploy Windows Sun Valley +title: Prepare for Windows Sun Valley description: Prepare your infrastructure and tools to deploy Windows Sun Valley, IT Pro content. keywords: ["get started", "windows sun valley"] ms.prod: w11 diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 469fe1924c..d9c0d22b1a 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -21,7 +21,7 @@ ms.custom: seo-marvel-apr2020 - Windows Sun Valley, version 21H2 -This article lists the system requirements for Windows Sun Valley. Windows Sun Valley is also supported on a virtual machine (VM). For the best Windows Sun Valley upgrade experience, eligible devices should be running Windows 10, version 20H1 or later. +This article lists the system requirements for Windows Sun Valley. Windows Sun Valley is also supported on a virtual machine (VM). ## Hardware requirements @@ -41,6 +41,10 @@ To install Windows Sun Valley, devices must meet the following specifications: For additional guidance, see [Determine eligibility](windows-sv-plan.md#determine-eligibility) NEED LINK. +## Operating system requirements + +For the best Windows Sun Valley upgrade experience, eligible devices should be running Windows 10, version 20H1 or later. + > [!NOTE] > S mode is not supported on Windows Sun Valley. > If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. Switching a device out of Windows 10 in S mode also requires internet connectivity. diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 1e9127bae0..b1b09d27be 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -32,21 +32,19 @@ Also see the following articles to learn about Windows Sun Valley: ## Introduction -Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers a fresh experience that is flexible and fluid, designed to support today's hybrid work environment and to be the most reliable, secure, connected, and performant Windows OS ever. +Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows OS ever. -Windows Sun Valley contains many innovations focused on enhancing end user productivity. It is built on the same foundation as Windows 10, ensuring that the investments you have made in tools for update and device management are carried forward. Windows Sun Valley provides the benefits that commercial organizations and IT pros need and rely upon every day: best-in-class security, simplified manageability, and high availability. It also sustains the application compatibility promise we made with Windows 10, supplemented by programs like App Assure in cases where additional support is needed. - -In summary, because Windows Sun Valley is built on the same foundation as Windows 10, you can deploy, manage, and secure Windows SV using the same tools and solutions you use today. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows SV. +This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise we made with Windows 10. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. ## How to get Windows Sun Valley Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new, eligible devices. -For PCs that are managed by your organization and meet the eligibility requirements, Windows Sun Valley will be available through the same, familiar channels we utilize for Windows 10 feature updates today. You will be able to use existing deployment and management toolsets, such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot and those commercial customers running Pro, Enterprise and Education editions of Windows 10 will have control over when to upgrade their devices from Windows 10 to Windows Sun Valley. For more information, see Management tools. +For PCs that are managed by your organization and meet the eligibility requirements, Windows Sun Valley will be available through the same channels that you use for Windows 10 feature updates today. Existing deployment and management tools such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot can be used to deploy and manage Windows Sun Valley. Commercial organizations running Pro, Enterprise and Education editions of Windows 10 will have control over when to upgrade their devices from Windows 10 to Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools). -For personal devices and other unmanaged PCs that meet the eligibility requirements, the upgrade will be offered through Windows Update using our intelligent rollout process to ensure a smooth upgrade experience. Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. +For personal devices and other unmanaged PCs that meet the eligibility requirements, the Windows Sun Valley upgrade will be offered through Windows Update using Microsoft's [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process. Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. -For those interested in testing Windows Sun Valley before general availability, we recommend joining the Windows Insider Program or Windows Insider Program for Business [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), or enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). +If you are interested in testing Windows Sun Valley before general availability, you can join the Windows Insider Program or Windows Insider Program for Business [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). You can also preview Windows Sun Valley by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). @@ -62,15 +60,17 @@ Microsoft 365 licenses that include Windows 10 licenses will permit you to run W Most accessories and associated drivers that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. -Windows Sun Valley also preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility). +Windows Sun Valley preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility). -#### Familiar deployment process +#### Familiar processes -Windows Sun Valley is built on the same foundation as Windows 10, so you can generally use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. You can also use your current management tools, processes, and settings to manage monthly quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools) and [Configurations](windows-sv-plan.md#configurations). +Windows Sun Valley is built on the same foundation as Windows 10, so generally you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools). #### Servicing Windows Sun Valley -Windows Sun Valley will have an annual feature update cadence and receive monthly quality updates. For details, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available via a consolidated Windows Sun Valley update history page at that time as well. +Windows Sun Valley will have an annual feature update cadence and receive monthly quality updates. For details, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). + +When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available from a consolidated Windows Sun Valley update history page. ## Next steps From 6ceaf03326d07c9cad486be76f8f654af46deeaa Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 16 Jun 2021 14:50:02 -0700 Subject: [PATCH 070/104] incorp white paper --- windows/whats-new/windows-sv-plan.md | 6 ++++-- windows/whats-new/windows-sv-prepare.md | 9 +++------ 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 310e572df1..87cefa2210 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -110,11 +110,13 @@ A consolidated [update history]() is also available for every version of the Win ## Application compatibility -Windows 10 upgrades have proven to be highly compatible, and that does not change with Windows Sun Valley. Our compatibility promise for Windows 10 is that upgrades will maintain compatibility with apps written for previously released versions. Windows Sun Valley comes with the same App Assure promise and commitment that you have known with Windows 10. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for our enterprise customers, including line of business apps. This great progress will not be lost. Windows Sun Valley has been subjected to, and is passing the same app compatibility validation requirements, that are in place for Windows 10 feature and quality update releases today. +Windows 10 upgrades have proven to be highly compatible, and that does not change with Windows Sun Valley. Microsoft's compatibility promise for Windows 10 that upgrades will preserve application compatibility is maintained for Windows Sun Valley. Windows Sun Valley comes with the same App Assure promise and commitment that you have known with Windows 10. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for our enterprise customers, including line of business apps. Windows Sun Valley has passed the same app compatibility validation requirements that are in place for Windows 10 feature and quality update releases. #### App Assure and Test Base -You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. With enrollment in the App Assure service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. +You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. + +With enrollment in the App Assure service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. If you’ve created your own applications, Test Base for Microsoft is a service that allows independent software vendors and commercial customers to validate their apps across a variety of updates and environments in a Microsoft managed Azure environment. Both services can be of benefit to you as you roll out Windows Sun Valley into your environment. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 8da15603d9..db5959e103 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -20,14 +20,11 @@ ms.topic: article - Windows Sun Valley, version 21H2 +Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. One common management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. -Organizations will vary in their pace relative to transitioning from Windows 10 to SV, and we expect early corporate adoptions to consist of smaller test environments before rolling out to wider groups begins. We are committed to supporting you through your migration to Windows Sun Valley whether you are a fast adopter, or will make the transition over the coming months or years. +As you prepare for Windows Sun Valley, it’s also a good time to look at the deployment infrastructure of your environment. If you aren’t already taking advantage of cloud-based management tools like Microsoft Endpoint Manager this might be the perfect time. Or, if you are exclusively using an on-premises management tool such as Configuration Manager (Note: Config Mgr is part of MEM, need clarification here), using Cloud management gateway, enabling tenant attach, or enabling co-management with Microsoft Intune are all ways to help keep devices secure and up-to-date. ---insert links for the named solutions -With the new Windows Sun Valley experience, hybrid environments of both operating systems running simultaneously will be the norm. Windows 10 and Windows Sun Valley are designed to co-exist during this time, so that you can use the same familiar tools and process to manage them, as well as continue to give your users the best Microsoft 365 experience. You’ll have one common management infrastructure, and support for common applications across both Windows 10 and Windows Sun Valley to simplify the migration process. You’ll use the IT Pro tools that you are familiar with and have been using in the past to prepare for deployments also work in Windows Sun Valley; you can analyze endpoints, determine application compatibility, and manage deployments in the same way you did with Windows 10. - -As you prepare for Windows Sun Valley, it’s also a good time to look at the deployment infrastructure of your environment. If you aren’t already taking advantage of cloud-based management tools like Microsoft Endpoint Manager this might be the perfect scenario in which to make that leap. Or if you are exclusively using an on-premises management tool such as Configuration Manager, using Cloud management gateway, enabling tenant attach, or enabling co-management with Microsoft Intune are all ways to help keep devices secure and up-to-date. ---insert links for the named solutions - -Additionally, policies related to deployment may need to be updated or re-evaluated respective of update compliance deadlines, device activity policies, and the re-evaluation of older policies. A servicing mindset pointed at keeping current means that, as with Windows 10 devices, you will create a deployment plan in order to build out your servicing strategy. +Policies related to deployment may need to be updated or re-evaluated, considering update compliance deadlines, device activity policies, and the replacement of older policies. A servicing mindset focused on keeping current means creating a deployment plan to build out your servicing strategy. ## Analytics From b0191eb0f632c0ff5a95d53789ef550dd6f51362 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 16 Jun 2021 14:54:50 -0700 Subject: [PATCH 071/104] toc and index --- windows/whats-new/TOC.yml | 2 +- windows/whats-new/index.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index fb7a0de80e..71e18303ee 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -7,7 +7,7 @@ href: windows-sv.md - name: Windows Sun Valley requirements href: windows-sv-requirements.md - - name: Plan to deploy Windows Sun Valley + - name: Plan for Windows Sun Valley href: windows-sv-plan.md - name: Prepare for Windows Sun Valley href: windows-sv-prepare.md diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index bf2243760c..fbea14e982 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -31,7 +31,7 @@ landingContent: url: windows-sv.md - text: Windows Sun Valley requirements url: windows-sv-requirements.md - - text: Plan to deploy Windows Sun Valley + - text: Plan for Windows Sun Valley url: windows-sv-plan.md - text: Prepare for Windows Sun Valley url: windows-sv-prepare.md From f20b7e7a1f92c38fffd20c3abdde85630969aefa Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Mon, 21 Jun 2021 13:58:34 -0700 Subject: [PATCH 072/104] edits --- windows/whats-new/windows-sv-plan.md | 126 +++++++++---------- windows/whats-new/windows-sv-requirements.md | 53 ++++++-- windows/whats-new/windows-sv.md | 28 ++--- 3 files changed, 117 insertions(+), 90 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 87cefa2210..aa15b3748b 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -25,101 +25,101 @@ ms.topic: article This article provides guidance to help you plan for Windows Sun Valley in your organization. Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment and servicing strategy. At a high level, this strategy should include the following steps: -- Create a deployment plan. -- Define readiness criteria. -- Evaluate current infrastructure and tools. -- Determine application readiness. -- Define your servicing strategy. +- [Create a deployment plan](/windows/deployment/update/create-deployment-plan) +- [Define readiness criteria](/windows/deployment/update/plan-define-readiness) +- [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) +- [Determine application readiness](/windows/deployment/update/plan-determine-app-readiness) +- [Define your servicing strategy](/windows/deployment/update/plan-define-strategy) -Most organizations will have a mix of Windows Sun Valley and Windows 10 devices side-by-side as they integrate the upgrade into their environments. As such, there are unique yet largely familiar considerations to take into account when planning your deployments. +If you are looking for ways to optimize your approach to deploying Windows Sun Valley, or if deploying a new version of an operating system is not a familiar process for you, some additional items to consider are provided below. -## Upgrade eligibility +## Determining eligibility -As a first step, you will need to know which of your current PCs meet the Windows Sun Valley hardware requirements. Detailed requirements can be found [here](windows-sv-requirements.md). However, in general you should expect that if your devices were purchased within the last 18-24 months, they will be able to run Windows Sun Valley. +As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. Detailed requirements can be found at [Windows Sun Valley requirements](windows-sv-requirements.md). In general, you should expect that a device purchased in the last 18-24 months will be able to run Windows Sun Valley. -Analysis tools will be developed and made available to validate devices against the Windows Sun Valley hardware requirements. A standalone tool is planned, and upgrade eligibility will also be integrated into your existing enterprise deployment tools. - -When Windows Sun Valley reaches general availability, end users running Windows 10 Home, Pro, and Pro for Workstations can use the PC Health Check app to determine their eligibility for Windows Sun Valley. End users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade. [LINK NEEDED]() has been developed for this purpose. - -For organizations with investments in enterprise deployment tools, analytics functionality will be available to evaluate device readiness, including Endpoint Analytics and Update Compliance. Microsoft is also sharing information with independent sofware vendors to enable their tools to support analytics for Windows Sun Valley. +Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. End users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  + +Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint Analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software vendor partners to facilitate Windows Sun Valley device readiness into their solutions. ## Windows Sun Valley availability -As with Windows 10, the availability of Windows Sun Valley will vary depending on whether the device is unmanaged and receives updates from Windows Update, or a device is managed using tools operated by an IT administrator. - -##### Unmanaged devices - -For unmanaged devices, most eligible devices purchased after June of 2021 will be offered the Windows Sun Valley upgrade in October of 2021. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. - -> [!NOTE] -> New devices purchased after October 2021 will see the Windows Sun Valley offer during the out of box experience (OOBE), or they will already be upgraded to Windows Sun Valley. - -After General Availability (GA) date for Windows Sun Valley, the OS upgrade will be available to eligible devices that use Windows Update. The upgrade will be available first to seekers, then as part of Microsoft's intelligent rollout process. The Windows Update Settings page will confirm when a device is eligible, and users can choose whether or not to upgrade. - -Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience and ensures that devices first nominated for updates are those likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. +Windows Sun Valley will be offered to eligible Windows 10 devices beginning the last quarter of calendar year 2021. The availability of Windows Sun Valley will vary according to a device's hardware and whether or not the device receives updates directly or from a management solution that is maintained by an IT administrator. ##### Managed devices -The right time to upgrade will be different for each organization and environment. You can choose between Windows Sun Valley and Windows 10, and decide when the time is right to integrate Window Sun Valley into your environment. Initially, it is expected that many organizations will operate with a mix of Windows 10 and Windows Sun Valley. +Managed devices are devices that are under organization control. For example: devices managed by Microsoft Endpoint Manager (Microsoft Intune or Microsoft Endpoint Configuration Manager) or another endpoint management solution. -You can deploy the Windows Sun Valley upgrade to eligible devices using your existing management tools beginning at GA. If you use Windows Update for Business (WUfB), you will have the additional benefit of two safety nets: offering blocks on non-eligible devices that do not meet the hardware requirements, and Safeguard holds. Safeguard holds will function for Windows Sun Valley devices the same way that they do for Windows 10. Administrators will have access to information on which Safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. +If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools when the upgrade reaches general availability. Organizations that use Windows Update for Business will have additional benefits, such as: + +- Blocking the upgrade on non-eligible devices. +- Additional insight into safeguard holds. While safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. > [!NOTE] > If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (Windows 10 to Windows 10), but they cannot migrate a devices between products (Windows 10 to Windows Sun Valley).
-> Additionally, Windows Sun Valley has a new end user license agreement (EULA). If you are deploying with WUfB **Target Version** or with WSUS, you are accepting this new EULA on behalf of the end users within your organization. +> Additionally, Windows Sun Valley has a new end user license agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new end user license agreements on behalf of the end users within your organization. Additional considerations: -- Windows 10 Pro or higher can upgrade for free using existing management tools. +- Devices running Windows 10 Pro or higher can upgrade for free using existing management tools. - Devices running S mode will first need to switch out of S mode because it is not supported on Windows Sun Valley. - Downgrade rights are available with Windows Sun Valley Pro OEM licensed devices and with Microsoft Volume Licensing, where the licensing agreement permits it. - You can downgrade to any version of Windows Pro that has not reached its end of support date. -## Availability and upgrade path +##### Unmanaged devices -As previously mentioned, the Windows Sun Valley upgrade offer will begin for eligible devices at GA in October of 2021. This is true for existing eligible devices as well as for new devices. +Unmanaged devices are those that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. -To preview Windows Sun Valley, you can join the [Windows Insider Program](https://insider.windows.com/for-business) (WIP). This enables you to begin validating Windows Sun Valley, and to explore new features as they’re being created. As a WIP participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), Windows Sun Valley will be available to you in the summer of 2021, well ahead of the October GA date. - -You can deploy directly from the Windows Insider Pre-release category in WSUS in a variety of ways: -1. Configure Manage Preview Builds to **Release Preview** with WUfB. -2. Leverage Windows Virtual Devices or Cloud PC* (check if this will be announced when this paper goes out) and Azure Marketplace images. -3. Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. - -Regardless of which way you choose to deploy, you have the benefit of free Microsoft support when validating a pre-release. Just go to [Support for business](http://support.microsoft.com/supportforbusiness/productselection?sapId=39fc4a93-68cd-5a19-f91b-f0b349a098f3) and submit your support case. This is free for any Microsoft commercial customer deploying Windows 10 version 21H2 or Windows Sun Valley 21H2 pre-release bits after the commercial preview date in the summer of 2021. - -## Quality updates - -- Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates. -- Windows Sun Valley devices will receive a single feature update annually, a change from the twice per year of Windows 10. -- Devices on in-service versions of Windows 10 that do not meet Windows Sun Valley hardware requirements will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support your ongoing deployments of Microsoft 365. - -## Servicing duration - -Along with end user experience and security improvements, Windows Sun Valley introduces enhancements to our servicing approach based on your suggestions and feedback. - -Windows 10 feature updates are released twice yearly via the Semi-Annual Channel. They are serviced with monthly quality updates for 18 or 30 months from the date of the release, depending on the lifecycle policy. Windows Sun Valley will have an annual feature update cadence, targeted for release in the second half of the calendar year: -- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the date of release. -- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months. - -THIS SECTION DOESNT EXIST: For more details on the lifecycle and servicing strategy for Windows Sun Valley, see [Windows lifecycle and servicing update overview](). -Microsoft recognizes the importance that organizations have adequate time to plan for Windows Sun Valley. Therefore, we have committed to supporting Windows 10 through October 14, 2025. For more information, see the [Windows release information]() page. This page also includes information for Windows 10 semi-annual channel and LTSC releases. -A consolidated [update history]() is also available for every version of the Windows operating system. This information offers quick access to knowledge base articles for each monthly, optional, and out-of-band release. In addition to update highlights, you’ll find a list of improvements and fixes, a summary of any known issues, and details on how to get the update, including any prerequisites. +Unmanaged eligible devices running Windows 10 that were purchased after June 2021 will be offered the Windows Sun Valley upgrade in the last quarter of the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. + +> [!NOTE] +> New devices purchased after October 2021 will see the Windows Sun Valley offer during the out of box experience (OOBE), or they will already be upgraded to Windows Sun Valley. + +The Windows Sun Valley upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Microsoft Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. + +Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience and ensures that devices first nominated for updates are those likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. + +## Windows Sun Valley readiness considerations + +The recommended method for organizations to determine if their infrastructure, deployment processes, and management tools are ready for Windows Sun Valley is to join the [Windows Insider Program for Business](https://insider.windows.com/for-business). As a participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), you can validate that your devices and applications work as expected, and explore new features in details. + +As you plan your endpoint management strategy for Windows Sun Valley, consider moving to cloud-based mobile device management (MDM), such as [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). If a cloud-only approach isn't right for your organization just yet, you can still modernize and streamline essential pieces of your endpoint management strategy as follows: +- Create a [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview) (CMG) to manage Configuration Manager clients over the internet. +- Attach your existing Configuration Management estate to the cloud with [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions) so you can manage all devices from within the Microsoft Endpoint Manager admin center. +- Use [co-management](/mem/configmgr/comanage/overview) to concurrently manage devices using both Configuration Manager and Microsoft Intune, allowing you to take advantage of cloud-powered capabilities like [Conditional Access](/azure/active-directory/conditional-access/overview). + +For more information on the benefits of these approaches, see [Cloud Attach Your Future: The Big 3](https://techcommunity.microsoft.com/t5/configuration-manager-blog/cloud-attach-your-future-part-ii-quot-the-big-3-quot/ba-p/1750664). + +The introduction of Windows Sun Valley is also a good time to review your hardware refresh plans and prioritize eligible devices to ensure an optimal experience for your users. + +## Servicing and support + +Along with end user experience and security improvements, Windows Sun Valley introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. + +Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. However, Windows Sun Valley devices will receive a single feature update annually, targeted for release in the second half of each calendar year. +- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the date of release. +- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the date of release. + +When Windows Sun Valley reaches general availability, a consolidated Windows Sun Valley update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows Sun Valley servicing announcements, known issues, and safeguard holds. + + +It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 that do not meet Windows Sun Valley hardware requirements will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about Windows 10 semi-annual channel and LTSC releases. ## Application compatibility -Windows 10 upgrades have proven to be highly compatible, and that does not change with Windows Sun Valley. Microsoft's compatibility promise for Windows 10 that upgrades will preserve application compatibility is maintained for Windows Sun Valley. Windows Sun Valley comes with the same App Assure promise and commitment that you have known with Windows 10. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for our enterprise customers, including line of business apps. Windows Sun Valley has passed the same app compatibility validation requirements that are in place for Windows 10 feature and quality update releases. +Microsoft's compatibility promise for Windows 10 is maintained for Windows Sun Valley. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for enterprise organizations, including line of business (LOB) apps. Microsoft remains committed to ensuring that the apps you rely upon continue to work as expected when you upgrade. Windows Sun Valley is subject to the same app compatibility validation requirements that are in place for Windows 10 today, and it is passing these requirements. -#### App Assure and Test Base +#### App Assure and Test Base for Microsoft 365 + +If you run into compatibility issues or want to ensure that your organization's applications are compatible from day one, App Assure and Test Base for Microsoft 365 can help. + +With enrollment in the [App Assure](/windows/compatibility/app-assure) service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy those application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. + +For software vendors and systems integrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software vendors for participation by completing a short form. You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. -With enrollment in the App Assure service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. - -If you’ve created your own applications, Test Base for Microsoft is a service that allows independent software vendors and commercial customers to validate their apps across a variety of updates and environments in a Microsoft managed Azure environment. Both services can be of benefit to you as you roll out Windows Sun Valley into your environment. - ## Next steps [Prepare for Windows Sun Valley](windows-sv-prepare.md) diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index d9c0d22b1a..99d261a3d9 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -25,21 +25,20 @@ This article lists the system requirements for Windows Sun Valley. Windows Sun V ## Hardware requirements -To install Windows Sun Valley, devices must meet the following specifications: +To install or upgrade to Windows Sun Valley, devices must meet the following minimum hardware requirements: -- Processor: 1 gigahertz (GHz) or faster processor or SoC; dual-core CPU or greater - - Intel 8th generation, Intel Celeron N4000, Pentium N5000 - - AMD Ryzen gen 2 (Zen+), AMD 3xxx - - Qualcomm 7c, 8c, 8cx +- Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](http://aka.ms/CPUlist) or system on a chip (SoC) +- RAM: 4 gigabytes (GB) or greater +- Storage: 64GB or greater available storage is required to install Windows Sun Valley + - Additional storage space might be required to download updates and enable specific features +- Graphics card: Compatible with DirectX 12 or later with WDDM 2.0 driver +- System firmware: UEFI, Secure Boot capable +- TPM: Trusted Platform Module (TPM) version 2.0 +- Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel +- Internet connection: Internet connectivity is necessary to perform updates and to download and take advantage of some features. + - Windows Sun Valley Home edition requires an Internet connection and a Microsoft Account to complete device setup on first use. -- RAM: 4 gigabyte (GB) or greater -- Hard disk space: 64GB, 64-bit architecture -- Graphics card: DirectX 12 or later with WDDM 2.x driver -- Security: Trusted Platform Module (TPM) 2.0 chip, UEFI support, Secure Boot capable -- Display: 9" monitor size or greater with HD (1366 x 768) resolution or greater -- Internet connection: Internet connectivity is necessary to perform updates and to download and take advantage of some features. It is required for the Home edition of Windows Sun Valley. - -For additional guidance, see [Determine eligibility](windows-sv-plan.md#determine-eligibility) NEED LINK. +For additional guidance, see [Determine eligibility](windows-sv-plan.md#determine-eligibility). ## Operating system requirements @@ -49,6 +48,34 @@ For the best Windows Sun Valley upgrade experience, eligible devices should be r > S mode is not supported on Windows Sun Valley. > If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. Switching a device out of Windows 10 in S mode also requires internet connectivity. +## Feature-specific requirements + +Some features in Windows Sun Valley have requirements beyond those listed above. See the following list: + +- **5G support** requires 5G capable modem. +- **Auto HDR** requires an HDR monitor. +- **BitLocker to Go** requires a USB flash drive. This feature is available in Windows Pro and above editions. +- **Client Hyper-V** requires a processor with second level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. +- **Cortana** requires a microphone and speaker and is currently available on Windows 11 for the Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States +- **DirectStorage** requires 1TB or greater NVMe SSD to store and run games that uses the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU +- **DirectX 12 Ultimate** is available with supported games and graphics chips +- **Presence** requires sensor that can detect human distance from device or intent to interact with device +- **Intelligent Video Conferencing** requires video camera, microphone and speaker (audio output) +- **Multiple Voice Assistant** requires a microphone and speaker +- **Snap** three column layouts require a screen that is 1920 effective pixels or greater in width +- **Mute** and **unmute** from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute +- **Spatial Sound** requires supporting hardware and software +- **Microsoft Teams** requires video camera, microphone and speaker (audio output) +- **Touch** requires a screen or monitor that supports multi-touch +- **Two-factor authentication** requires use of PIN, biometric (fingerprint reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities +- **Voice Typing** requires a PC with a microphone +- **Wake on Voice** requires Modern Standby power model and microphone +- **Wi-Fi 6E** requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router +- **Windows Hello** requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key +- **Windows Projection** requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct +- **Xbox** app requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active Xbox Game Pass subscription. See https://www.xbox.com/xbox-game-pass to learn more about the pass. + + ## Next steps [Plan to deploy Windows Sun Valley](windows-sv-plan.md)
diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index b1b09d27be..31c967b779 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -22,34 +22,36 @@ ms.custom: seo-marvel-apr2020 - Windows Sun Valley, version 21H2 -This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. +This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next Windows client operating systgem release. -Also see the following articles to learn about Windows Sun Valley: +Also see the following articles to learn more about Windows Sun Valley: - [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. -- [Planning for Windows Sun Valley](windows-sv-plan.md): Information to help you create a Windows Sun Valley deployment plan. +- [Planning for Windows Sun Valley](windows-sv-plan.md): Information to help you plan for Windows Sun Valley in your organizatioin. - [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. ## Introduction Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows OS ever. -This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise we made with Windows 10. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. +This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. ## How to get Windows Sun Valley -Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10 beginning in the first half of 2022. Windows Sun Valley will also be available on new, eligible devices. +Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10, beginning in the last quarter of the 2021 calendar year. Windows Sun Valley will also be available on new, eligible devices. -For PCs that are managed by your organization and meet the eligibility requirements, Windows Sun Valley will be available through the same channels that you use for Windows 10 feature updates today. Existing deployment and management tools such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot can be used to deploy and manage Windows Sun Valley. Commercial organizations running Pro, Enterprise and Education editions of Windows 10 will have control over when to upgrade their devices from Windows 10 to Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools). +For administrators managing devices on behalf of their organization, Windows Sun Valley will be available through the same, familiar channels that you utilize today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot. For more information, see [Plan for Windows Sun Valley](windows-sv-plan.md). -For personal devices and other unmanaged PCs that meet the eligibility requirements, the Windows Sun Valley upgrade will be offered through Windows Update using Microsoft's [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process. Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements for Windows Sun Valley will be offered the upgrade starting in October of 2021. +For eligible PCs that are not managed by an organization, the Windows Sun Valley upgrade will be offered through Windows Update using Microsoft's intelligent rollout process to ensure a smooth upgrade experience. Windows Sun Valley will initially be offered to Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements. -If you are interested in testing Windows Sun Valley before general availability, you can join the Windows Insider Program or Windows Insider Program for Business [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). You can also preview Windows Sun Valley by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). +For more information about device eligibility, see [Windows Sun Valley requirements](windows-sv-requirements.md). -For more information about eligibility to upgrade, see [Windows Sun Valley requirements](windows-sv-requirements.md). +For those interested in testing Windows Sun Valley before general availability, you can join the [Windows Insider Program](https://insider.windows.com) or [Windows Insider Program for Business](https://insider.windows.com/for-business). You can also preview Windows Sun Valley by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). ## Before you begin +Many organizations will have a mixed environment of Windows Sun Valley and Windows 10 devices. The following is a quick summary of licensing, compatibility, management, and servicing considerations. + #### Licensing There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. @@ -64,16 +66,14 @@ Windows Sun Valley preserves the application compatibility promise made with Win #### Familiar processes -Windows Sun Valley is built on the same foundation as Windows 10, so generally you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Management tools](windows-sv-prepare.md#management-tools). +Windows Sun Valley is built on the same foundation as Windows 10, so generally you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md). #### Servicing Windows Sun Valley -Windows Sun Valley will have an annual feature update cadence and receive monthly quality updates. For details, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). - -When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available from a consolidated Windows Sun Valley update history page. +Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available via a consolidated Windows SV update history page at that time as well. For more information, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). ## Next steps [Windows Sun Valley requirements](windows-sv-requirements.md)
-[Plan to deploy Windows Sun Valley](windows-sv-plan.md)
+[Plan for Windows Sun Valley](windows-sv-plan.md)
[Prepare for Windows Sun Valley](windows-sv-prepare.md) \ No newline at end of file From 3e49e11277468a943426735c54d2bb692e2024f7 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Mon, 21 Jun 2021 14:11:04 -0700 Subject: [PATCH 073/104] edits --- windows/whats-new/windows-sv-plan.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index aa15b3748b..31658c2150 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -55,7 +55,7 @@ If you manage devices on behalf of your organization, you will be able to upgrad - Additional insight into safeguard holds. While safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. > [!NOTE] -> If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer versions of the same product (Windows 10 to Windows 10), but they cannot migrate a devices between products (Windows 10 to Windows Sun Valley).
+> If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer version of the same product (Windows 10 to Windows 10), but they cannot migrate a device between products (Windows 10 to Windows Sun Valley).
> Additionally, Windows Sun Valley has a new end user license agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new end user license agreements on behalf of the end users within your organization. Additional considerations: @@ -69,8 +69,6 @@ Additional considerations: Unmanaged devices are those that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. - - Unmanaged eligible devices running Windows 10 that were purchased after June 2021 will be offered the Windows Sun Valley upgrade in the last quarter of the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. > [!NOTE] From 18e50e69af70791ad22788321e44d64f71e6d2de Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Mon, 21 Jun 2021 16:05:43 -0700 Subject: [PATCH 074/104] draft of final --- windows/whats-new/windows-sv-plan.md | 4 +- windows/whats-new/windows-sv-prepare.md | 107 ++++++++++++++----- windows/whats-new/windows-sv-requirements.md | 2 +- windows/whats-new/windows-sv.md | 4 +- 4 files changed, 88 insertions(+), 29 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 31658c2150..3f6adedbbd 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -33,7 +33,7 @@ Since Windows Sun Valley is built on the same foundation as Windows 10, you can If you are looking for ways to optimize your approach to deploying Windows Sun Valley, or if deploying a new version of an operating system is not a familiar process for you, some additional items to consider are provided below. -## Determining eligibility +## Determine eligibility As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. Detailed requirements can be found at [Windows Sun Valley requirements](windows-sv-requirements.md). In general, you should expect that a device purchased in the last 18-24 months will be able to run Windows Sun Valley. @@ -43,7 +43,7 @@ Enterprise organizations looking to evaluate device readiness in their environme ## Windows Sun Valley availability -Windows Sun Valley will be offered to eligible Windows 10 devices beginning the last quarter of calendar year 2021. The availability of Windows Sun Valley will vary according to a device's hardware and whether or not the device receives updates directly or from a management solution that is maintained by an IT administrator. +Windows Sun Valley will be offered to eligible Windows 10 devices beginning later in the 2021 calendar year. The availability of Windows Sun Valley will vary according to a device's hardware and whether or not the device receives updates directly or from a management solution that is maintained by an IT administrator. ##### Managed devices diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index db5959e103..238373f36b 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -22,46 +22,105 @@ ms.topic: article Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. One common management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. -As you prepare for Windows Sun Valley, it’s also a good time to look at the deployment infrastructure of your environment. If you aren’t already taking advantage of cloud-based management tools like Microsoft Endpoint Manager this might be the perfect time. Or, if you are exclusively using an on-premises management tool such as Configuration Manager (Note: Config Mgr is part of MEM, need clarification here), using Cloud management gateway, enabling tenant attach, or enabling co-management with Microsoft Intune are all ways to help keep devices secure and up-to-date. ---insert links for the named solutions +After you evaluate your hardware to see if it meets [requirements](windows-sv-requirements.md) for Windows Sun Valley, it's also a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. -Policies related to deployment may need to be updated or re-evaluated, considering update compliance deadlines, device activity policies, and the replacement of older policies. A servicing mindset focused on keeping current means creating a deployment plan to build out your servicing strategy. +## Infrastructure and tools -## Analytics +The tools that you use for heavy lifting during Windows 10 deployments can still be leveraged for Windows Sun Valley. Aa few nuanced differences are described below: -If you’re a Microsoft Endpoint Manager customer, make sure you’ve onboarded your devices to Endpoint analytics. Later this year, we’ll be providing a hardware readiness assessment directly in Endpoint analytics so that you can quickly identify which of your managed devices meet or exceed the minimum hardware requirements. +#### On-premises solutions -If you’d rather start exploring Windows Sun Valley readiness within your organization right away, take advantage of our [hardware eligibility assessment script](add link). By following the instructions to deploy and aggregate results via Microsoft Intune or Configuration Manager, you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. +- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. Once you sync the product category you will see Windows Sun Valley offered as an option. -## Management tools +> [!NOTE] +> During deployment, you will be prompted to agree to the license agreement on behalf of your end users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. -The toolset that you use for heavy lifting during deployments of Windows 10 are still able to be leveraged in Windows Sun Valley. There are a few nuanced differences described here: +- If you use Microsoft Endpoint Configuration Manager, you can sync the new **Windows Sun Valley** product category and begin upgrading eligible devices. If you would like to validate Windows Sun Valley prior to release, you can sync the **Windows Insider Pre-release** category as well. -#### On-premises management +> [!NOTE] +> Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. -- Windows Server Update Service (WSUS): Commercial customers using WSUS will need to sync the new **Windows Sun Valley** product category. Once you sync the product category you will see the feature update to SV. Please note that during deployment you will be prompted to agree to the license agreement on behalf of your end users. Additionally, you will note there is no x86 (32 bit?) payload for Windows Sun Valley as such is no longer supported on Windows Sun Valley going forward. -- MEM Configuration Manager: For customers using MEM Configuration Manager, you will easily be able to sync the new “Windows Sun Valley” Product category and begin upgrading eligible devices. Please note that Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. If you would like to validate Windows Sun Valley prior to release, simply sync the **Windows Insider Pre-release** category as well. +#### Cloud-based solutions -#### Cloud management +- If you use Windows Update for Business Group Policy and Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product, but do not enable you to move between products (Windows 10 to Windows Sun Valley). +- Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether using Windows Update for Business, Microsoft Intune, or other management tools. +- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to leverage **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Wndows 10 devices to Windows Sun Valley. You can then continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. -- Windows Update for Business (WUfB) Group Policy (GP) and Configuration Service Provider (CSP) policies: Commercial customers using WUfB will need to leverage the Target Version capability rather than feature update deferrals to move from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product, but do not enable you to move between products (Windows 10 to Windows Sun Valley). Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether using WUfB through Group Policy Management Console (GPMC), MEM Intune, or other 3rd party management tools. -- MEM Intune: For customers using MEM Intune with E3 licenses you will be able to leverage **Feature Update Deployments** to easily manage moving between Windows 10 versions or to Windows Sun Valley, version 21H2. You will be able to continue using the same update experience controls to manage the behavior of the device once updates are offered for either Windows 10, version 21H2 and Windows Sun Valley, version 21H2. +You'll also want to check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows Sun Valley, particularly those providing security or data loss prevention capabilities. -## Deploy Windows Sun Valley +## Cloud-based management -Since your familiar Windows 10 toolsets are meant to be used with Windows Sun Valley as well, then managing, securing, and deploying Windows Sun Valley devices will be well known procedures in the plan, prepare and deploy process. +If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. Aside from consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end user privacy. -Just as we recommend that broad deployment of new versions of Windows 10 begin with a pilot deployment phase, Windows Sun Valley is no different. Further, in your blended environment of Windows 10-capable devices and Windows 10 + SV-eligible devices, you will be poised to roll out an update to a select number of devices. Once you’ve gone through the checklist of pilot deployment tasks such as assigning the pilot devices from your prepare phase, implementing baseline and operations updates, testing and supporting the devices, and so forth, you can deploy to your test group. We recommend cloud-based deployment solutions such as Microsoft Endpoint Manager to fully take advantage of data-driven insights, though Configuration Manager works as well. +The following are some common use cases and the corresponding Microsoft Endpoint Manager capabilities that support them: -Using artifacts from your Plan and Prepare phase (such as security and configuration baselines, etc.) as well as data from your test deployment, will give you the confidence you seek to manage a broader rollout of Windows Sun Valley to increasingly larger rings of eligible devices. Desktop Analytics will help you ensure that your apps are scoped to only the pilot rings you designate. +- **Provision and pre-configure new Windows Sun Valley devices**: [Windows Autopilot](/mem/autopilot/windows-autopilot) enables you to deploy new Windows Sun Valley devices in a “business-ready” state that includes your desired applications, settings, and policies. It can also be used to change the edition of Windows. For example, you can upgrade from Pro to Enterprise edition and gain the use of advanced features. +- **Configure rules and control settings for users, apps, and devices for both Windows SV and Windows 10**: Devices that are enrolled in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) provide administrators with full control over apps, settings, features, and security. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. +- **Streamlined, easy-to-manage devices for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley using Microsoft Endpoint Manager. -Though we’ve mentioned only a few, the tools and processes we have had in place for your previous 10 Windows deployment will be there for you with Windows Sun Valley as well. +If you are exclusively managing devices on-premises (for example, using Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune, making it easier to keep devices secure and up-to-date. + + +## Review servicing approach and policies + +Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. Every organization will transition to Windows Sun Valley at its own pace. However, thinking of operating system updates as an ongoing process improve your ability to deploy feature and quality updates, and enable you to stay current with less effort and impact on productivity. + +To begin, think about how you roll out Windows updates today: which devices, and at what pace. Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: + +- Preview (first or canary): Planning and development +- Limited (fast or early adopters): Pilot and validation +- Broad (users or critical): Wide deployment + +For more information, see [Create a deployment plan](/windows/deployment/update/create-deployment-plan). + +#### Review policies + +Review deployment-related polices, taking into consideration your organization's security objectives, update compliance deadlines, and device activity. Apply changes where you can gain a clear improvement, particularly with regard to the speed of the update process or security. + +#### Validate apps and infrastructure + +To validate that your apps, infrastructure, and deployment processes are ready for Windows Sun Valley, join the [Windows Insider Program for Business](https://insider.windows.com/for-business-getting-started) and opt in to the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). + +If you use Windows Server Update Services, you can deploy directly from the Windows Insider Pre-release category using one of the following: + +- Set **Manage Preview Builds** to **Release Preview** in Windows Update for Business. +- Leverage Azure Virtual Desktop and Azure Marketplace images . +- Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. + +Regardless of the method you choose, you have the benefit of free Microsoft support when validating pre-release builds. Free support is available to any commercial customer deploying Windows 10, version 21H2 or Windows Sun Valley, version 21H2 pre-release bits, once they become available through the Windows Insider Program. + +#### Analytics and assessment tools + +If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year that enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. + +For those that are ready to explore Windows Sun Valley readiness right away, you can take advantage of Microsoft's **hardware eligibility assessment script**. This script includes instructions on how to deploy and aggregate your assessment results using Microsoft Intune or Configuration Manager, so you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. + +## Prepare a pilot deployment + +A pilot deployment is a proof of concept that rolls out an upgrade to a select number of devices in production before deploying it broadly across the organization. + +At a high level, the tasks involved are: + +1. Assign a group of users or devices to receive the update. +2. Implement baseline updates. +3. Implement operational updates. +4. Validate the deployment process. +5. Deploy the upgrade to devices. +6. Test and support the pilot devices. +7. Determine broad deployment readiness based on the results of the pilot. + +## End user readiness + +To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end user readiness should not be overlooked. Windows Sun Valley has a familiar design, but end users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: + +- Create a communications schedule to ensure that you provide the right communications at the right time to the right groups of users based on when they will see the changes. +- Draft concise emails that inform users of what changes they can expect to see. Offer tips on how to use or customize their experience. Include information about support and help desk options. +- Update help desk manuals with screenshots of the new user interface, the out-of-box experience for new devices, and the upgrade experience for existing devices. + +## Learn more + +See the [Stay current with Windows 10 and Microsoft 365 Apps](/learn/paths/m365-stay-current/) learning path on Microsoft Learn. The learning path was created for Windows 10, but the basic principles and tasks outlined for the plan, prepare, and deploy phases also apply to your deployment of Windows Sun Valley. ## See also [Windows Sun Valley deployment planning](windows-sv-plan.md) - -• Windows release health: Windows release health offers the quickest way to stay up to date on update-related news, information, and best practices, including important lifecycle reminders and the status of known issues and safeguard holds. IT administrators have access to this information, plus additional details, within the health experience Microsoft 365 admin center. - -• Windows Tech Community: Offering technical professionals a place to discuss, share, troubleshoot, and learn around Windows, Tech Community is also the home of the Windows IT Pro Blog, our monthly Windows Office Hours events, and the Windows Video Hub. - -• Microsoft Learn: We are in the process of developing online learning paths and modules to help you and your organization effectively plan, prepare, and deploy Windows Sun Valley effectively. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 99d261a3d9..341495b506 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -27,7 +27,7 @@ This article lists the system requirements for Windows Sun Valley. Windows Sun V To install or upgrade to Windows Sun Valley, devices must meet the following minimum hardware requirements: -- Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](http://aka.ms/CPUlist) or system on a chip (SoC) +- Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](https://aka.ms/CPUlist) or system on a chip (SoC) - RAM: 4 gigabytes (GB) or greater - Storage: 64GB or greater available storage is required to install Windows Sun Valley - Additional storage space might be required to download updates and enable specific features diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 31c967b779..86cffe9e8f 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -38,7 +38,7 @@ This release is built on the same foundation as Windows 10, so the investments y ## How to get Windows Sun Valley -Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10, beginning in the last quarter of the 2021 calendar year. Windows Sun Valley will also be available on new, eligible devices. +Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10, beginning later in the 2021 calendar year. Windows Sun Valley will also be available on eligible new devices. For administrators managing devices on behalf of their organization, Windows Sun Valley will be available through the same, familiar channels that you utilize today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot. For more information, see [Plan for Windows Sun Valley](windows-sv-plan.md). @@ -70,7 +70,7 @@ Windows Sun Valley is built on the same foundation as Windows 10, so generally y #### Servicing Windows Sun Valley -Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available via a consolidated Windows SV update history page at that time as well. For more information, see [Windows Sun Valley servicing](windows-sv-plan.md#windows-sun-valley-servicing). +Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available via a consolidated Windows SV update history page at that time as well. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). ## Next steps From bd2ceade13af7d98a2b51b3f0dd5d3f01e855109 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Mon, 21 Jun 2021 16:09:53 -0700 Subject: [PATCH 075/104] draft of final2 --- windows/whats-new/windows-sv-prepare.md | 1 - windows/whats-new/windows-sv.md | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 238373f36b..71e51fe64f 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -60,7 +60,6 @@ The following are some common use cases and the corresponding Microsoft Endpoint If you are exclusively managing devices on-premises (for example, using Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune, making it easier to keep devices secure and up-to-date. - ## Review servicing approach and policies Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. Every organization will transition to Windows Sun Valley at its own pace. However, thinking of operating system updates as an ongoing process improve your ability to deploy feature and quality updates, and enable you to stay current with less effort and impact on productivity. diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 86cffe9e8f..6a44007c98 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -62,7 +62,7 @@ Microsoft 365 licenses that include Windows 10 licenses will permit you to run W Most accessories and associated drivers that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. -Windows Sun Valley preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-prepare.md#application-compatibility). +Windows Sun Valley preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-plan.md#application-compatibility). #### Familiar processes From 9e9e77eeec912044aaf4f1eda89dc110adbdb2b9 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Mon, 21 Jun 2021 16:43:46 -0700 Subject: [PATCH 076/104] draft of final3 --- windows/whats-new/windows-sv.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 6a44007c98..3aca95c50b 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -27,12 +27,12 @@ This article provides an introduction and answers some frequently asked question Also see the following articles to learn more about Windows Sun Valley: - [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. -- [Planning for Windows Sun Valley](windows-sv-plan.md): Information to help you plan for Windows Sun Valley in your organizatioin. +- [Plan for Windows Sun Valley](windows-sv-plan.md): Information to help you plan for Windows Sun Valley in your organizatioin. - [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. ## Introduction -Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows OS ever. +Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. From bddcb1af8601cb8bd0b2bf74cce24e70d42631fa Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 11:22:53 -0700 Subject: [PATCH 077/104] close to final --- windows/whats-new/windows-sv-plan.md | 26 +++++++------------- windows/whats-new/windows-sv-prepare.md | 11 +++++---- windows/whats-new/windows-sv-requirements.md | 6 ++--- windows/whats-new/windows-sv.md | 9 +++++-- 4 files changed, 25 insertions(+), 27 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 3f6adedbbd..81e3281c7d 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -24,7 +24,7 @@ ms.topic: article This article provides guidance to help you plan for Windows Sun Valley in your organization. -Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment and servicing strategy. At a high level, this strategy should include the following steps: +Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) that are in place for Windows Sun Valley. At a high level, this strategy should include the following steps: - [Create a deployment plan](/windows/deployment/update/create-deployment-plan) - [Define readiness criteria](/windows/deployment/update/plan-define-readiness) - [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) @@ -35,11 +35,11 @@ If you are looking for ways to optimize your approach to deploying Windows Sun V ## Determine eligibility -As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. Detailed requirements can be found at [Windows Sun Valley requirements](windows-sv-requirements.md). In general, you should expect that a device purchased in the last 18-24 months will be able to run Windows Sun Valley. +As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. The majority of devices purchased in the last 18-24 months will be compatible with Windows Sun Valley. Verify that your device meets or exceeds [Windows Sun Valley requirements](windows-sv-requirements.md) to ensure it is compatible. Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. End users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  -Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint Analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software vendor partners to facilitate Windows Sun Valley device readiness into their solutions. +Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software vendor partners to facilitate Windows Sun Valley device readiness into their solutions. ## Windows Sun Valley availability @@ -49,7 +49,7 @@ Windows Sun Valley will be offered to eligible Windows 10 devices beginning late Managed devices are devices that are under organization control. For example: devices managed by Microsoft Endpoint Manager (Microsoft Intune or Microsoft Endpoint Configuration Manager) or another endpoint management solution. -If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools when the upgrade reaches general availability. Organizations that use Windows Update for Business will have additional benefits, such as: +If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools at no cost when the upgrade reaches general availability. Organizations that use Windows Update for Business will have additional benefits, such as: - Blocking the upgrade on non-eligible devices. - Additional insight into safeguard holds. While safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. @@ -58,13 +58,6 @@ If you manage devices on behalf of your organization, you will be able to upgrad > If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer version of the same product (Windows 10 to Windows 10), but they cannot migrate a device between products (Windows 10 to Windows Sun Valley).
> Additionally, Windows Sun Valley has a new end user license agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new end user license agreements on behalf of the end users within your organization. -Additional considerations: - -- Devices running Windows 10 Pro or higher can upgrade for free using existing management tools. -- Devices running S mode will first need to switch out of S mode because it is not supported on Windows Sun Valley. -- Downgrade rights are available with Windows Sun Valley Pro OEM licensed devices and with Microsoft Volume Licensing, where the licensing agreement permits it. -- You can downgrade to any version of Windows Pro that has not reached its end of support date. - ##### Unmanaged devices Unmanaged devices are those that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. @@ -95,14 +88,13 @@ The introduction of Windows Sun Valley is also a good time to review your hardwa Along with end user experience and security improvements, Windows Sun Valley introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. -Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. However, Windows Sun Valley devices will receive a single feature update annually, targeted for release in the second half of each calendar year. -- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the date of release. -- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the date of release. +Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. However, Microsoft will provide a single feature update annually, targeted for release in the second half of each calendar year. +- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the availability date. +- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the availabily date. When Windows Sun Valley reaches general availability, a consolidated Windows Sun Valley update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows Sun Valley servicing announcements, known issues, and safeguard holds. - -It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 that do not meet Windows Sun Valley hardware requirements will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about Windows 10 semi-annual channel and LTSC releases. +It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about Windows 10 semi-annual channel and LTSC releases. ## Application compatibility @@ -114,7 +106,7 @@ If you run into compatibility issues or want to ensure that your organization's With enrollment in the [App Assure](/windows/compatibility/app-assure) service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy those application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. -For software vendors and systems integrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software vendors for participation by completing a short form. +For software vendors, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software vendors for participation by completing a short form. You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 71e51fe64f..da5759ab4b 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -26,7 +26,10 @@ After you evaluate your hardware to see if it meets [requirements](windows-sv-re ## Infrastructure and tools -The tools that you use for heavy lifting during Windows 10 deployments can still be leveraged for Windows Sun Valley. Aa few nuanced differences are described below: +The tools that you use for heavy lifting during Windows 10 deployments can still be leveraged for Windows Sun Valley. A few nuanced differences are described below. + +> [!IMPORTANT] +> Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows Sun Valley, particularly if they provide security or data loss prevention capabilities. #### On-premises solutions @@ -46,8 +49,6 @@ The tools that you use for heavy lifting during Windows 10 deployments can still - Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether using Windows Update for Business, Microsoft Intune, or other management tools. - If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to leverage **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Wndows 10 devices to Windows Sun Valley. You can then continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. -You'll also want to check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows Sun Valley, particularly those providing security or data loss prevention capabilities. - ## Cloud-based management If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. Aside from consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end user privacy. @@ -64,7 +65,7 @@ If you are exclusively managing devices on-premises (for example, using Configur Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. Every organization will transition to Windows Sun Valley at its own pace. However, thinking of operating system updates as an ongoing process improve your ability to deploy feature and quality updates, and enable you to stay current with less effort and impact on productivity. -To begin, think about how you roll out Windows updates today: which devices, and at what pace. Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: +To begin, think about how you roll out Windows feature updates today: which devices, and at what pace. Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: - Preview (first or canary): Planning and development - Limited (fast or early adopters): Pilot and validation @@ -100,7 +101,7 @@ A pilot deployment is a proof of concept that rolls out an upgrade to a select n At a high level, the tasks involved are: -1. Assign a group of users or devices to receive the update. +1. Assign a group of users or devices to receive the upgrade. 2. Implement baseline updates. 3. Implement operational updates. 4. Validate the deployment process. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 341495b506..a1ae360f30 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -46,7 +46,7 @@ For the best Windows Sun Valley upgrade experience, eligible devices should be r > [!NOTE] > S mode is not supported on Windows Sun Valley. -> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. Switching a device out of Windows 10 in S mode also requires internet connectivity. +> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. Switching a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you cannot switch back to S mode later. ## Feature-specific requirements @@ -56,7 +56,7 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **Auto HDR** requires an HDR monitor. - **BitLocker to Go** requires a USB flash drive. This feature is available in Windows Pro and above editions. - **Client Hyper-V** requires a processor with second level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. -- **Cortana** requires a microphone and speaker and is currently available on Windows 11 for the Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States +- **Cortana** requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States - **DirectStorage** requires 1TB or greater NVMe SSD to store and run games that uses the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU - **DirectX 12 Ultimate** is available with supported games and graphics chips - **Presence** requires sensor that can detect human distance from device or intent to interact with device @@ -71,7 +71,7 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **Voice Typing** requires a PC with a microphone - **Wake on Voice** requires Modern Standby power model and microphone - **Wi-Fi 6E** requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router -- **Windows Hello** requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key +- **Windows Hello** requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see [IT tools to support Windows 10, version 21H1](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/it-tools-to-support-windows-10-version-21h1/ba-p/2365103). - **Windows Projection** requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct - **Xbox** app requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active Xbox Game Pass subscription. See https://www.xbox.com/xbox-game-pass to learn more about the pass. diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 3aca95c50b..fcbf1043e9 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -60,13 +60,18 @@ Microsoft 365 licenses that include Windows 10 licenses will permit you to run W #### Compatibility -Most accessories and associated drivers that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. +Most accessories and associated drivers that work with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. Windows Sun Valley preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-plan.md#application-compatibility). #### Familiar processes -Windows Sun Valley is built on the same foundation as Windows 10, so generally you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md). +Windows Sun Valley is built on the same foundation as Windows 10, so generally you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. If you use non-Microsoft tools, check with your vendor to verify compatibility. + +> [!IMPORTANT] +> Check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows Sun Valley, particularly those providing security or data loss prevention capabilities. + +For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md). #### Servicing Windows Sun Valley From e33525fcf0047aef686fcf0daa502645c0f017b7 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 11:40:51 -0700 Subject: [PATCH 078/104] remove extraneous --- .../windows-sv-app-manage.md | 17 - windows/client-management/sv-manage.md | 67 ---- .../client-management/windows-sv-manage.md | 19 - windows/configuration/sv-configure.md | 329 ------------------ windows/configuration/windows-sv-configure.md | 17 - windows/deployment/index.yml | 2 +- windows/hub/index.yml | 4 +- windows/sv/TOC.yml | 33 +- windows/sv/breadcrumb/toc.yml | 50 --- windows/sv/docfx.json | 4 +- windows/sv/index.md | 0 windows/sv/index.yml | 61 ---- windows/sv/placeholder.md | 22 -- windows/sv/windows-sv-get-started.md | 36 -- windows/sv/windows-sv-lifecycle.md | 21 -- windows/sv/windows-sv-overview.md | 94 ----- windows/sv/windows-sv-requirements.md | 53 --- 17 files changed, 8 insertions(+), 821 deletions(-) delete mode 100644 windows/application-management/windows-sv-app-manage.md delete mode 100644 windows/client-management/sv-manage.md delete mode 100644 windows/client-management/windows-sv-manage.md delete mode 100644 windows/configuration/sv-configure.md delete mode 100644 windows/configuration/windows-sv-configure.md create mode 100644 windows/sv/index.md delete mode 100644 windows/sv/index.yml delete mode 100644 windows/sv/placeholder.md delete mode 100644 windows/sv/windows-sv-get-started.md delete mode 100644 windows/sv/windows-sv-lifecycle.md delete mode 100644 windows/sv/windows-sv-overview.md delete mode 100644 windows/sv/windows-sv-requirements.md diff --git a/windows/application-management/windows-sv-app-manage.md b/windows/application-management/windows-sv-app-manage.md deleted file mode 100644 index 86ee8a28c0..0000000000 --- a/windows/application-management/windows-sv-app-manage.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Manage applications in Windows Sun Valley -ms.reviewer: -manager: dansimp -description: Use this article to understand the different types of apps that run on Windows Sun Valley, such as UWP and Win32 apps. -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: mobile -ms.author: greglin -author: greg-lindsay -ms.localizationpriority: medium -ms.topic: article ---- -# Manage applications in Windows Sun Valley - ->Applies to: Windows Sun Valley diff --git a/windows/client-management/sv-manage.md b/windows/client-management/sv-manage.md deleted file mode 100644 index 4fc41d68c1..0000000000 --- a/windows/client-management/sv-manage.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Manage corporate devices (Windows 10) -description: You can use the same management tools to manage all device types running Windows 10 desktops, laptops, tablets, and phones. -ms.assetid: 62D6710C-E59C-4077-9C7E-CE0A92DFC05D -ms.reviewer: -manager: dansimp -ms.author: dansimp -keywords: ["MDM", "device management"] -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -ms.pagetype: devices -author: dansimp -ms.localizationpriority: medium -ms.date: 09/21/2017 -ms.topic: article ---- - -# Manage corporate devices - - -**Applies to** - -- Windows 10 -- Windows 10 Mobile - -You can use the same management tools to manage all device types running Windows 10 : desktops, laptops, tablets, and phones. And your current management tools, such as Group Policy, Windows Management Instrumentation (WMI), PowerShell scripts, System Center tools, and so on, will continue to work for Windows 10. - -## In this section - -| Topic | Description | -| --- | --- | -| [Manage Windows 10 in your organization - transitioning to modern management](manage-windows-10-in-your-organization-modern-management.md) | Strategies for deploying and managing Windows 10, including deploying Windows 10 in a mixed environment | -| [Connect to remote Azure Active Directory-joined PC](connect-to-remote-aadj-pc.md) | How to use Remote Desktop Connection to connect to an Azure AD-joined PC | -| [Manage Windows 10 and Microsoft Store tips, tricks, and suggestions](/windows/configuration/manage-tips-and-suggestions) | Options to manage user experiences to provide a consistent and predictable experience for employees | -| [New policies for Windows 10](new-policies-for-windows-10.md) | New Group Policy settings added in Windows 10 | -| [Group Policies that apply only to Windows 10 Enterprise and Windows 10 Education](group-policies-for-enterprise-and-education-editions.md) | Group Policy settings that apply only to Windows 10 Enterprise and Windows 10 Education | -| [Changes to Group Policy settings for Start in Windows 10](/windows/configuration/changes-to-start-policies-in-windows-10) | Changes to the Group Policy settings that you use to manage Start | -| [Introduction to configuration service providers (CSPs) for IT pros](/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers) | How IT pros and system administrators can take advantage of many settings available through CSPs to configure devices running Windows 10 and Windows 10 Mobile in their organizations | - - -## Learn more - -[How to bulk-enroll devices with On-premises Mobile Device Management in Microsoft Endpoint Configuration Manager](/mem/configmgr/mdm/deploy-use/bulk-enroll-devices-on-premises-mdm) - -[Azure AD, Microsoft Intune and Windows 10 - Using the cloud to modernize enterprise mobility](https://blogs.technet.microsoft.com/enterprisemobility/2015/06/12/azure-ad-microsoft-intune-and-windows-10-using-the-cloud-to-modernize-enterprise-mobility/) - -[Microsoft Intune End User Enrollment Guide](/samples/browse/?redirectedfrom=TechNet-Gallery) - -[Azure AD Join on Windows 10 devices](https://go.microsoft.com/fwlink/p/?LinkId=616791) - -[Azure AD support for Windows 10](https://go.microsoft.com/fwlink/p/?LinkID=615765) - -[Windows 10 and Azure Active Directory: Embracing the Cloud](https://go.microsoft.com/fwlink/p/?LinkId=615768) - -[How to manage Windows 10 devices using Intune](https://go.microsoft.com/fwlink/p/?LinkId=613620) - -[Using Intune alone and with Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=613207) - -Microsoft Virtual Academy course: [System Center 2012 R2 Configuration Manager & Windows Intune](/learn/) - - - - - - -  \ No newline at end of file diff --git a/windows/client-management/windows-sv-manage.md b/windows/client-management/windows-sv-manage.md deleted file mode 100644 index 22704843bd..0000000000 --- a/windows/client-management/windows-sv-manage.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Manage Windows Sun Valley in your organization -description: This topic offers strategies for deploying and managing Windows Sun Valley, including deploying Windows Sun Valley in a mixed environment. -keywords: ["MDM", "device management", "group policy", "Azure Active Directory"] -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -ms.pagetype: devices -author: dansimp -ms.localizationpriority: medium -ms.date: 04/26/2018 -ms.reviewer: -manager: dansimp -ms.author: dansimp -ms.topic: article ---- - -# Manage Windows Sun Valley in your organization - diff --git a/windows/configuration/sv-configure.md b/windows/configuration/sv-configure.md deleted file mode 100644 index 15407ebc50..0000000000 --- a/windows/configuration/sv-configure.md +++ /dev/null @@ -1,329 +0,0 @@ ---- -title: Configure Windows 10 taskbar (Windows 10) -description: Administrators can pin additional apps to the taskbar and remove default pinned apps from the taskbar by adding a section to a layout modification XML file. -keywords: ["taskbar layout","pin apps"] -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -author: greg-lindsay -ms.author: greglin -ms.topic: article -ms.localizationpriority: medium -ms.date: 01/18/2018 -ms.reviewer: -manager: dansimp ---- -# Configure Windows 10 taskbar - -Starting in Windows 10, version 1607, administrators can pin additional apps to the taskbar and remove default pinned apps from the taskbar by adding a `` section to a layout modification XML file. This method never removes user-pinned apps from the taskbar. - -> [!NOTE] -> The only aspect of the taskbar that can currently be configured by the layout modification XML file is the layout. - -You can specify different taskbar configurations based on device locale and region. There is no limit on the number of apps that you can pin. You specify apps using the [Application User Model ID (AUMID)](./find-the-application-user-model-id-of-an-installed-app.md) or Desktop Application Link Path (the local path to the application). - -If you specify an app to be pinned that is not provisioned for the user on the computer, the pinned icon won't appear on the taskbar. - -The order of apps in the XML file dictates the order of pinned apps on the taskbar from left to right, to the right of any existing apps pinned by the user. - -> [!NOTE] -> In operating systems configured to use a right-to-left language, the taskbar order will be reversed. - -The following example shows how apps will be pinned: Windows default apps to the left (blue circle), apps pinned by the user in the center (orange triangle), and apps that you pin using the XML file to the right (green square). - -![Windows left, user center, enterprise to the right](images/taskbar-generic.png) - - -## Configure taskbar (general) - -**To configure the taskbar:** - -1. Create the XML file. - * If you are also [customizing the Start layout](customize-and-export-start-layout.md), use `Export-StartLayout` to create the XML, and then add the `` section from [the following sample](#sample-taskbar-configuration-added-to-start-layout-xml-file) to the file. - * If you are only configuring the taskbar, use [the following sample](#sample-taskbar-configuration-xml-file) to create a layout modification XML file. -2. Edit and save the XML file. You can use [AUMID](./find-the-application-user-model-id-of-an-installed-app.md) or Desktop Application Link Path to identify the apps to pin to the taskbar. - * Add `xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"` to the first line of the file, before the closing \>. - * Use `` and [AUMID](./find-the-application-user-model-id-of-an-installed-app.md) to pin Universal Windows Platform apps. - * Use `` and Desktop Application Link Path to pin desktop applications. -3. Apply the layout modification XML file to devices using [Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) or a [provisioning package created in Windows Imaging and Configuration Designer (Windows ICD)](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md). - ->[!IMPORTANT] ->If you use a provisioning package or import-startlayout to configure the taskbar, your configuration will be reapplied each time the explorer.exe process restarts. If your configuration pins an app and the user then unpins that app, the user's change will be overwritten the next time the configuration is applied. To apply a taskbar configuration that allows users to make changes that will persist, apply your configuration by using Group Policy. -> ->If you use Group Policy and your configuration only contains a taskbar layout, the default Windows tile layout will be applied and cannot be changed by users. If you use Group Policy and your configuration includes taskbar and a full Start layout, users can only make changes to the taskbar. If you use Group Policy and your configuration includes taskbar and a [partial Start layout](.//customize-and-export-start-layout.md#configure-a-partial-start-layout), users can make changes to the taskbar and to tile groups not defined in the partial Start layout. - -### Tips for finding AUMID and Desktop Application Link Path - -In the layout modification XML file, you will need to add entries for applications in the XML markup. In order to pin an application, you need either its AUMID or Desktop Application Link Path. - -The easiest way to find this data for an application is to: -1. Pin the application to the Start menu on a reference or testing PC. -2. Open Windows PowerShell and run the `Export-StartLayout` cmdlet. -3. Open the generated XML file. -4. Look for an entry corresponding to the app you pinned. -5. Look for a property labeled `AppUserModelID` or `DesktopApplicationLinkPath`. - - -### Sample taskbar configuration XML file - -```xml - - - - - - - - - - - -``` -### Sample taskbar configuration added to Start layout XML file - -```xml - - - - - - - - - - - - - - - - - - - - - - - -``` - -## Keep default apps and add your own - -The `` section will append listed apps to the taskbar by default. The following sample keeps the default apps pinned and adds pins for Paint, Microsoft Reader, and a command prompt. - -```xml - - - - - - - - - - - - -``` -**Before:** - -![default apps pinned to taskbar](images/taskbar-default.png) - -**After:** - - ![additional apps pinned to taskbar](images/taskbar-default-plus.png) - -## Remove default apps and add your own - -By adding `PinListPlacement="Replace"` to ``, you remove all default pinned apps; only the apps that you specify will be pinned to the taskbar. - -If you only want to remove some of the default pinned apps, you would use this method to remove all default pinned apps and then include the default app that you want to keep in your list of pinned apps. - -```xml - - - - - - - - - - - - -``` -**Before:** - -![Taskbar with default apps](images/taskbar-default.png) - -**After:** - -![Taskbar with default apps removed](images/taskbar-default-removed.png) - -## Remove default apps - -By adding `PinListPlacement="Replace"` to ``, you remove all default pinned apps. - - -```xml - - - - - - - - - - -``` - -## Configure taskbar by country or region - -The following example shows you how to configure taskbars by country or region. When the layout is applied to a computer, if there is no `` node with a region tag for the current region, the first `` node that has no specified region will be applied. When you specify one or more countries or regions in a `` node, the specified apps are pinned on computers configured for any of the specified countries or regions. - -```xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -``` - -When the preceding example XML file is applied, the resulting taskbar for computers in the US or UK: - -![taskbar for US and UK locale](images/taskbar-region-usuk.png) - -The resulting taskbar for computers in Germany or France: - -![taskbar for DE and FR locale](images/taskbar-region-defr.png) - -The resulting taskbar for computers in any other country region: - -![taskbar for all other regions](images/taskbar-region-other.png) - - -> [!NOTE] -> [Look up country and region codes (use the ISO Short column)](/previous-versions/commerce-server/ee799297(v=cs.20)) - - - - -## Layout Modification Template schema definition - -```xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -``` - -## Related topics - -- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md) -- [Customize and export Start layout](customize-and-export-start-layout.md) -- [Add image for secondary tiles](start-secondary-tiles.md) -- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md) -- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) -- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md) -- [Customize Windows 10 Start and tasbkar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) -- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md) \ No newline at end of file diff --git a/windows/configuration/windows-sv-configure.md b/windows/configuration/windows-sv-configure.md deleted file mode 100644 index 2a7ccf17d1..0000000000 --- a/windows/configuration/windows-sv-configure.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Configure Windows Sun Valley -description: Administrators can pin additional apps to the taskbar and remove default pinned apps from the taskbar by adding a section to a layout modification XML file. -keywords: ["taskbar layout","pin apps"] -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -author: greg-lindsay -ms.author: greglin -ms.topic: article -ms.localizationpriority: medium -ms.date: 01/18/2018 -ms.reviewer: -manager: dansimp ---- -# Configure Windows Sun Valley - diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index ef58977660..eda7ab8577 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -67,7 +67,7 @@ landingContent: - text: What's new in Windows deployment url: deploy-whats-new.md - text: Windows Sun Valley overview - url: /windows/whats-new/windows-sv-overview.md + url: /windows/whats-new/windows-sv.md - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md - text: Basics of Windows updates, channels, and tools diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 60a1b71261..c745cb605b 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -30,8 +30,10 @@ landingContent: url: /windows/whats-new/windows-sv - text: Windows Sun Valley requirements url: /windows/whats-new/windows-sv-requirements - - text: Plan to deploy Windows Sun Valley + - text: Plan for Windows Sun Valley url: /windows/whats-new/windows-sv-plan + - text: Prepare for Windows Sun Valley + url: /windows/whats-new/windows-sv-prepare - text: What's new in Windows 10, version 21H2 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: Windows release information diff --git a/windows/sv/TOC.yml b/windows/sv/TOC.yml index f0ec3588a7..01da3e1c0a 100644 --- a/windows/sv/TOC.yml +++ b/windows/sv/TOC.yml @@ -1,34 +1,5 @@ -- name: Windows Sun Valley - href: index.yml - items: - - name: Get started - items: - - name: Windows Sun Valley overview - href: windows-sv-overview.md - - name: Windows Sun Valley requirements - href: windows-sv-requirements.md - - - name: Deploy and Manage Windows Sun Valley - items: - - name: Plan to deploy Windows Sun Valley - href: /windows/deployment/windows-sv-plan - - name: Prepare for Windows Sun Valley - href: /windows/deployment/windows-sv-prepare.md - - name: Deploy Windows Sun Valley - href: /windows/deployment/windows-sv-deploy.md - - name: Configure Windows Sun Valley - href: /windows/configuration/windows-sv-configure.md - - name: Manage Windows Sun Valley - href: /windows/client-management/windows-sv-manage.md - - name: Windows Sun Valley application readiness - href: /windows/application-management/windows-sv-app-readiness.md - - - name: Support - items: - - name: Windows Sun Valley lifecycle - href: windows-sv-lifecycle.md - - name: Windows Sun Valley release information - href: /windows/release-health +- name: Index + href: index.md diff --git a/windows/sv/breadcrumb/toc.yml b/windows/sv/breadcrumb/toc.yml index e2971f2d84..48236190f9 100644 --- a/windows/sv/breadcrumb/toc.yml +++ b/windows/sv/breadcrumb/toc.yml @@ -1,53 +1,3 @@ - name: Docs tocHref: / topicHref: / - items: - - name: Windows - tocHref: /windows - topicHref: /windows/windows-10 - items: - - name: What's new - tocHref: /windows/whats-new/ - topicHref: /windows/whats-new/index - - name: Configuration - tocHref: /windows/configuration/ - topicHref: /windows/configuration/index - - name: Deployment - tocHref: /windows/deployment/ - topicHref: /windows/deployment/index - - name: Application management - tocHref: /windows/application-management/ - topicHref: /windows/application-management/index - - name: Client management - tocHref: /windows/client-management/ - topicHref: /windows/client-management/index - items: - - name: Mobile Device Management - tocHref: /windows/client-management/mdm/ - topicHref: /windows/client-management/mdm/index - - name: Release information - tocHref: /windows/release-information/ - topicHref: /windows/release-health/release-information - - name: Privacy - tocHref: /windows/privacy/ - topicHref: /windows/privacy/index - - name: Security - tocHref: /windows/security/ - topicHref: /windows/security/index - items: - - name: Identity and access protection - tocHref: /windows/security/identity-protection/ - topicHref: /windows/security/identity-protection/index - items: - - name: Windows Hello for Business - tocHref: /windows/security/identity-protection/hello-for-business - topicHref: /windows/security/identity-protection/hello-for-business/hello-identity-verification - - name: Threat protection - tocHref: /windows/security/threat-protection/ - topicHref: /windows/security/threat-protection/index - - name: Information protection - tocHref: /windows/security/information-protection/ - topicHref: /windows/security/information-protection/index - - name: Hardware-based protection - tocHref: /windows/security/hardware-protection/ - topicHref: /windows/security/hardware-protection/index diff --git a/windows/sv/docfx.json b/windows/sv/docfx.json index e7955464fe..fe874614d1 100644 --- a/windows/sv/docfx.json +++ b/windows/sv/docfx.json @@ -39,13 +39,13 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "breadcrumb_path": "/windows/windows-11/breadcrumb/toc.json", + "breadcrumb_path": "/windows/windows-sv/breadcrumb/toc.json", "extendBreadcrumb": true, "feedback_system": "None" }, "fileMetadata": {}, "template": [], - "dest": "windows-11", + "dest": "windows-sv", "markdownEngineName": "markdig" } } \ No newline at end of file diff --git a/windows/sv/index.md b/windows/sv/index.md new file mode 100644 index 0000000000..e69de29bb2 diff --git a/windows/sv/index.yml b/windows/sv/index.yml deleted file mode 100644 index 6f30d77869..0000000000 --- a/windows/sv/index.yml +++ /dev/null @@ -1,61 +0,0 @@ -### YamlMime:Landing - -title: Windows Sun Valley # < 60 chars -summary: Find out about Windows Windows Sun Valley. # < 160 chars - -metadata: - title: Windows SV # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Learn about the administrative tools, tasks and best practices for managing Windows SV across your enterprise. # Required; article description that is displayed in search results. < 160 chars. - services: windows-10 - ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. - ms.subservice: subservice - ms.topic: landing-page # Required - ms.collection: windows-10 - author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. - ms.author: greglin #Required; microsoft alias of author; optional team alias. - ms.date: 05/07/2021 #Required; mm/dd/yyyy format. - localization_priority: medium - -# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new - -landingContent: -# Cards and links should be based on top customer tasks or top subjects -# Start card title with a verb - # Card (optional) - - title: Get started - linkLists: - - linkListType: overview - links: - - text: Windows Sun Valley overview - url: windows-sv-overview.md - - text: Windows Sun Valley requirements - url: windows-sv-requirements.md - - # Card (optional) - - title: Deploy Windows Sun Valley - linkLists: - - linkListType: overview - links: - - text: Plan to deploy Windows Windows Sun Valley - url: /windows/deployment/windows-sv-plan.md - - text: Prepare for Windows Windows Sun Valley - url: /windows/deployment/windows-sv-prepare.md - - text: Deploy Windows Windows Sun Valley - url: /windows/deployment/windows-sv-deploy.md - - text: Configure Windows Windows Sun Valley - url: /windows/configuration/sv-configure.md - - text: Manage Windows Windows Sun Valley - url: /windows/client-management/windows-sv-manage.md - - text: Windows Windows Sun Valley application readiness - url: /windows/application-management/windows-sv-app-readiness.md - - # Card (optional) - - title: Support information - linkLists: - - linkListType: overview - links: - - text: Windows Windows Sun Valley lifecycle - url: placeholder.md - - text: Windows Windows Sun Valley release information - url: /windows/release-health - diff --git a/windows/sv/placeholder.md b/windows/sv/placeholder.md deleted file mode 100644 index fecfe94a8e..0000000000 --- a/windows/sv/placeholder.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Placeholder -description: PH -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Placeholder - -Placeholder text. - diff --git a/windows/sv/windows-sv-get-started.md b/windows/sv/windows-sv-get-started.md deleted file mode 100644 index 25b0d9e99c..0000000000 --- a/windows/sv/windows-sv-get-started.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Get started with Windows Sun Valley -description: Learn about features, review requirements, and plan your deployment of Windows Sun Valley, including IT Pro content, release information, and history. -keywords: ["get started", "windows sun valley"] -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -author: greg-lindsay -ms.author: greglin -ms.date: 10/16/2017 -ms.reviewer: -manager: laurawi -ms.localizationpriority: high -ms.topic: article ---- - -# Get started with Windows Sun Valley - -**Applies to** - -- Windows Sun Valley - -## Deployment planning - -Consider using the following process to deploy Windows Sun Valley to existing devices: -1. Preview Windows Sun Valley and create a deployment plan. -2. Test critical applications and management policies. -3. Update devices to the latest release of Windows 10. -4. Verify that devices meet the minimum hardware requirements for Windows Sun Valley. -5. Update deployment tools and infrastructure. -6. Update qualifying devices to Windows Sun Valley. - - -## See also - -[Windows Sun Valley deployment planning](/windows/deployment/windows-sv-deploy) diff --git a/windows/sv/windows-sv-lifecycle.md b/windows/sv/windows-sv-lifecycle.md deleted file mode 100644 index fab8fda180..0000000000 --- a/windows/sv/windows-sv-lifecycle.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Lifecycle -description: Lifecycle information for Windows 11 -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows 11 lifecycle - -Windows 11 lifecycle. - diff --git a/windows/sv/windows-sv-overview.md b/windows/sv/windows-sv-overview.md deleted file mode 100644 index 2407048dbc..0000000000 --- a/windows/sv/windows-sv-overview.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Windows Sun Valley overview -description: Overview of Windows Sun Valley -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows Sun Valley overview - -**Applies to** -- Windows Sun Valley - -This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next client release of Windows. - -Windows Sun Valley is a newly designed Windows client operating system due to be released later in 2021. It is fresh and light, yet familiar to those who use Windows today. The goal of this release is to be the most reliable, secure, connected, and performant OS release ever. - -## How to get Windows Sun Valley - -Windows Sun Valley will delivered as an upgrade to devices running Windows 10 beginning in the first half of 2022. All upgrades to Windows Sun Valley from Windows 10 will be free. Windows Sun Valley will also be available on new devices that meet the hardware requirements. - -You must be running a current version of Windows 10 and meet the minimum hardware specifications to be eligible to upgrade. For more information, see [Windows Sun Valley requirements](windows-sv-requirements.md). - -Not all eligible Windows 10 PCs will be offered the upgrade at the same time. To see if your PC is eligible, download the PC Health Check app (link). The app will check that your devices meets hardware and software requirements to perform an upgrade to Windows Sun Valley. You can also check the status of your device by navigating to **Windows Update** in **Settings**. Once the upgrade rollout has started and the upgrade has been tested and validated for your PC's hardware, Windows Update will indicate that the upgrade is ready for installation. - -You can get early access to test Windows Sun Valley by joining the [Windows Insider Program](https://insider.windows.com), or by enabling pre-release Windows 10 feature updates in Configuration Manager or Windows Server Update Services (WSUS). - -## Windows Sun Valley lifecycle - -### Updates - -Windows Sun Valley feature updates will be released once per year in the second half of the year. Quality updates will be released each month on the second Tuesday of the month. - -Microsoft will continue to provide one cumulative package that includes all latest cumulative updates (LCUs) and servicing stack updates (SSUs), if applicable, for Windows Sun Valley. This will be provided as a single package to Windows Server Update Services (WSUS) and Catalog, and have them orchestrated on the device. This capability is also the default for devices using Windows Update. - -### Servicing - -Windows Sun Valley annual releases are supported for 24 months for the following editions: -- Home -- Pro -- Pro for Workstations -- Pro Education - -Windows Sun Valley annual releases are supported for 36 months for the following editions: -- Enterprise -- Education - -### Features and applications - -Most features and applications that are included with Windows 10 will be available on Windows Sun Valley. For information about features that are deprecated or work differently on Windows Sun Valley, see [article link here]. - -## Windows 10 lifecycle - -Starting with Windows 10, version 21H2, Windows 10 will receive only quality updates on the second Tuesday of the month. - -Windows 10 will be supported with security updates until October 2025. - -## Management and tools - -Windows Sun Valley is based on the same foundation as Windows 10. You can use your current management tools and processes to manage quality updates for both Windows 10 and Windows Sun Valley, in addition to using them to move between the two products. - -## Hardware compatibility - -Most accessories and associated software that worked with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. - -## Application compatibility - -Microsoft is committed to ensuring your Windows 10 applications work on Windows Sun Valley. If you have [App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure), Microsoft will help you fix any issues at no cost. App Assure is free for organizations with 150 or more seats. For more information on eligibility requirements, see [Products and Capabilities: App Assure](https://docs.microsoft.com/fasttrack/products-and-capabilities#app-assure). - -## Licensing - -There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. - -Microsoft 365 licenses that include Windows licenses will permit you to run Windows Sun Valley on supported devices. - -If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. - -## Rollback - -After you have upgraded to Windows Sun Valley, you have 10 days to use the rollback function if you wish to move back to Windows 10 while keeping your files and data. After the 10 day grace period, you will need to back up your data and perform a clean install to move back to Windows 10. - -## See also - -[Get started with Windows Sun Valley](windows-sv-get-started.md) diff --git a/windows/sv/windows-sv-requirements.md b/windows/sv/windows-sv-requirements.md deleted file mode 100644 index ddb8bf84c1..0000000000 --- a/windows/sv/windows-sv-requirements.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Windows Sun Valley requirements -description: Hardware requirements to deploy Windows Sun Valley -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows Sun Valley requirements - -This article lists the sotware and physical hardware requirements to run Windows Sun Valley. Windows Sun Valley can also be run on Virtual Machines (VMs). - -## Software requirements - -The upgrade to Sun Valley is available for devices running Windows 10, version 20H1 or newer, on eligible hardware. - -## Hardware requirements - -To install Windows Sun Valley, devices must meet the following specifications: - -Processor -- Intel 8th generation, Intel Celeron N4000, Pentium N5000 -- AMD Ryzen gen 2 (Zen+), AMD 3xxx -- Qualcomm 7c, 8c, 8cx -- 64bit architecture -- 1Ghz clock speed -- 2 cores - -Hardware -- 64GB drive -- 4GB RAM -- UEFI, Secure Boot capable & TPM 2.0 -- Monitor size 9” or more with HD Resolution -- DirectX 12 compatible graphics / WDDM 2.x - -## Network requirements - -Internet connectivity is required for the Home Edition - -## See also - -[Windows Sun Valley overview](windows-sv-overview.md) - From 36c589b9e5d96f87f935bde4729dacf959f2fb41 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 12:18:22 -0700 Subject: [PATCH 079/104] acrolinx --- .../sv-app-readiness.md | 183 ------------------ windows/sv/index.md | 1 + windows/whats-new/windows-sv-plan.md | 16 +- windows/whats-new/windows-sv-prepare.md | 20 +- windows/whats-new/windows-sv-requirements.md | 36 ++-- windows/whats-new/windows-sv.md | 12 +- 6 files changed, 43 insertions(+), 225 deletions(-) delete mode 100644 windows/application-management/sv-app-readiness.md diff --git a/windows/application-management/sv-app-readiness.md b/windows/application-management/sv-app-readiness.md deleted file mode 100644 index d8cddab78d..0000000000 --- a/windows/application-management/sv-app-readiness.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Windows 10 - Apps -ms.reviewer: -manager: dansimp -description: Use this article to understand the different types of apps that run on Windows 10, such as UWP and Win32 apps. -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: mobile -ms.author: greglin -author: greg-lindsay -ms.localizationpriority: medium -ms.topic: article ---- -# Understand the different apps included in Windows 10 - ->Applies to: Windows 10 - -The following types of apps run on Windows 10: -- Windows apps - introduced in Windows 8, primarily installed from the Store app. -- Universal Windows Platform (UWP) apps - designed to work across platforms, can be installed on multiple platforms including Windows client, Windows Phone, and Xbox. All UWP apps are also Windows apps, but not all Windows apps are UWP apps. -- "Win32" apps - traditional Windows applications. - -Digging into the Windows apps, there are two categories: -- Apps - All other apps, installed in C:\Program Files\WindowsApps. There are two classes of apps: - - Provisioned: Installed in user account the first time you sign in with a new user account. - - Installed: Installed as part of the OS. -- System apps - Apps that are installed in the C:\Windows\* directory. These apps are integral to the OS. - -The following tables list the system apps, installed Windows apps, and provisioned Windows apps in a standard Windows 10 Enterprise installation. (If you have a custom image, your specific apps might differ.) The tables list the app, the full name, show the app's status in Windows 10 version 1709, 1803, and 1809 and indicate whether an app can be uninstalled through the UI. - -Some of the apps show up in multiple tables - that's because their status changed between versions. Make sure to check the version column for the version you are currently running. - -## Provisioned Windows apps - -You can list all provisioned Windows apps with this PowerShell command: - -```Powershell -Get-AppxProvisionedPackage -Online | Format-Table DisplayName, PackageName -``` - -Here are the provisioned Windows apps in Windows 10 versions 1803, 1809, 1903, 1909, and 2004. - -| Package name | App name | 1803 | 1809 | 1903 | 1909 | 2004 | Uninstall through UI? | -|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------|:----:|:----:|:----:|:----:|:----:|:---------------------:| -| Microsoft.3DBuilder | [3D Builder](ms-windows-store://pdp/?PFN=Microsoft.3DBuilder_8wekyb3d8bbwe) | | | | | | Yes | -| Microsoft.BingWeather | [MSN Weather](ms-windows-store://pdp/?PFN=Microsoft.BingWeather_8wekyb3d8bbwe) | x | x | x | x | x | Yes | -| Microsoft.DesktopAppInstaller | [App Installer](ms-windows-store://pdp/?PFN=Microsoft.DesktopAppInstaller_8wekyb3d8bbwe) | x | x | x | x | x | Via Settings App | -| Microsoft.GetHelp | [Get Help](ms-windows-store://pdp/?PFN=Microsoft.Gethelp_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.Getstarted | [Microsoft Tips](ms-windows-store://pdp/?PFN=Microsoft.Getstarted_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.HEIFImageExtension | [HEIF Image Extensions](ms-windows-store://pdp/?PFN=Microsoft.HEIFImageExtension_8wekyb3d8bbwe) | | x | x | x | x | No | -| Microsoft.Messaging | [Microsoft Messaging](ms-windows-store://pdp/?PFN=Microsoft.Messaging_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.Microsoft3DViewer | [Mixed Reality Viewer](ms-windows-store://pdp/?PFN=Microsoft.Microsoft3DViewer_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.MicrosoftOfficeHub | [Office](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe) | x | x | x | x | x | Yes | -| Microsoft.MicrosoftSolitaireCollection | [Microsoft Solitaire Collection](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe) | x | x | x | x | x | Yes | -| Microsoft.MicrosoftStickyNotes | [Microsoft Sticky Notes](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.MixedReality.Portal | [Mixed Reality Portal](ms-windows-store://pdp/?PFN=Microsoft.MixedReality.Portal_8wekyb3d8bbwe) | | x | x | x | x | No | -| Microsoft.MSPaint | [Paint 3D](ms-windows-store://pdp/?PFN=Microsoft.MSPaint_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.Office.OneNote | [OneNote for Windows 10](ms-windows-store://pdp/?PFN=Microsoft.Office.OneNote_8wekyb3d8bbwe) | x | x | x | x | x | Yes | -| Microsoft.OneConnect | [Mobile Plans](ms-windows-store://pdp/?PFN=Microsoft.OneConnect_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.Outlook.DesktopIntegrationServices | | | | | x | x | | -| Microsoft.People | [Microsoft People](ms-windows-store://pdp/?PFN=Microsoft.People_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.Print3D | [Print 3D](ms-windows-store://pdp/?PFN=Microsoft.Print3D_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.ScreenSketch | [Snip & Sketch](ms-windows-store://pdp/?PFN=Microsoft.ScreenSketch_8wekyb3d8bbwe) | | x | x | x | x | No | -| Microsoft.SkypeApp | [Skype](ms-windows-store://pdp/?PFN=Microsoft.SkypeApp_kzf8qxf38zg5c) | x | x | x | x | x | No | -| Microsoft.StorePurchaseApp | [Store Purchase App](ms-windows-store://pdp/?PFN=Microsoft.StorePurchaseApp_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.VP9VideoExtensions | | | x | x | x | x | No | -| Microsoft.Wallet | [Microsoft Pay](ms-windows-store://pdp/?PFN=Microsoft.Wallet_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WebMediaExtensions | [Web Media Extensions](ms-windows-store://pdp/?PFN=Microsoft.WebMediaExtensions_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WebpImageExtension | [Webp Image Extension](ms-windows-store://pdp/?PFN=Microsoft.WebpImageExtension_8wekyb3d8bbwe) | | x | x | x | x | No | -| Microsoft.Windows.Photos | [Microsoft Photos](ms-windows-store://pdp/?PFN=Microsoft.Windows.Photos_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsAlarms | [Windows Alarms & Clock](ms-windows-store://pdp/?PFN=Microsoft.WindowsAlarms_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsCalculator | [Windows Calculator](ms-windows-store://pdp/?PFN=Microsoft.WindowsCalculator_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsCamera | [Windows Camera](ms-windows-store://pdp/?PFN=Microsoft.WindowsCamera_8wekyb3d8bbwe) | x | x | x | x | x | No | -| microsoft.windowscommunicationsapps | [Mail and Calendar](ms-windows-store://pdp/?PFN=microsoft.windowscommunicationsapps_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsFeedbackHub | [Feedback Hub](ms-windows-store://pdp/?PFN=Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsMaps | [Windows Maps](ms-windows-store://pdp/?PFN=Microsoft.WindowsMaps_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsSoundRecorder | [Windows Voice Recorder](ms-windows-store://pdp/?PFN=Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.WindowsStore | [Microsoft Store](ms-windows-store://pdp/?PFN=Microsoft.WindowsStore_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.Xbox.TCUI | [Xbox Live in-game experience](ms-windows-store://pdp/?PFN=Microsoft.Xbox.TCUI_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.XboxApp | [Xbox Console Companion](ms-windows-store://pdp/?PFN=Microsoft.XboxApp_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.XboxGameOverlay | [Xbox Game Bar Plugin](ms-windows-store://pdp/?PFN=Microsoft.XboxGameOverlay_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.XboxGamingOverlay | [Xbox Game Bar](ms-windows-store://pdp/?PFN=Microsoft.XboxGamingOverlay_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.XboxIdentityProvider | [Xbox Identity Provider](ms-windows-store://pdp/?PFN=Microsoft.XboxIdentityProvider_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.XboxSpeechToTextOverlay | | x | x | x | x | x | No | -| Microsoft.YourPhone | [Your Phone](ms-windows-store://pdp/?PFN=Microsoft.YourPhone_8wekyb3d8bbwe) | | x | x | x | x | No | -| Microsoft.ZuneMusic | [Groove Music](ms-windows-store://pdp/?PFN=Microsoft.ZuneMusic_8wekyb3d8bbwe) | x | x | x | x | x | No | -| Microsoft.ZuneVideo | [Movies & TV](ms-windows-store://pdp/?PFN=Microsoft.ZuneVideo_8wekyb3d8bbwe) | x | x | x | x | x | No | - ->[!NOTE] ->The Store app can't be removed. If you want to remove and reinstall the Store app, you can only bring Store back by either restoring your system from a backup or resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it. - -## System apps - -System apps are integral to the operating system. Here are the typical system apps in Windows 10 versions 1709, 1803, and 1809. - -You can list all system apps with this PowerShell command: - -```Powershell -Get-AppxPackage -PackageTypeFilter Main | ? { $_.SignatureKind -eq "System" } | Sort Name | Format-Table Name, InstallLocation -``` - -| Name | Package Name | 1709 | 1803 | 1809 |Uninstall through UI? | -|----------------------------------|---------------------------------------------|:-----:|:----:|:----:|-----------------------| -| File Picker | 1527c705-839a-4832-9118-54d4Bd6a0c89 | | x | x | No | -| File Explorer | c5e2524a-ea46-4f67-841f-6a9465d9d515 | | x | x | No | -| App Resolver UX | E2A4F912-2574-4A75-9BB0-0D023378592B | | x | x | No | -| Add Suggested Folders To Library | F46D4000-FD22-4DB4-AC8E-4E1DDDE828FE | | x | x | No | -| | InputApp | x | x | x | No | -| Microsoft.AAD.Broker.Plugin | Microsoft.AAD.Broker.Plugin | x | x | x | No | -| Microsoft.AccountsControl | Microsoft.AccountsControl | x | x | x | No | -| Microsoft.AsyncTextService | Microsoft.AsyncTextService | | x | x | No | -| Hello setup UI | Microsoft.BioEnrollment | x | x | x | No | -| | Microsoft.CredDialogHost | x | x | x | No | -| | Microsoft.ECApp | x | x | x | No | -| | Microsoft.LockApp | x | x | x | No | -| Microsoft Edge | Microsoft.MicrosoftEdge | x | x | x | No | -| | Microsoft.MicrosoftEdgeDevToolsClient | | x | x | No | -| | Microsoft.PPIProjection | x | x | x | No | -| | Microsoft.Win32WebViewHost | | x | x | No | -| | Microsoft.Windows.Apprep.ChxApp | x | x | x | No | -| | Microsoft.Windows.AssignedAccessLockApp | x | x | x | No | -| | Microsoft.Windows.CapturePicker | | x | x | No | -| | Microsoft.Windows.CloudExperienceHost | x | x | x | No | -| | Microsoft.Windows.ContentDeliveryManager | x | x | x | No | -| Cortana | Microsoft.Windows.Cortana | x | x | x | No | -| | Microsoft.Windows.Holographic.FirstRun | x | x | | No | -| | Microsoft.Windows.OOBENetworkCaptivePort | x | x | x | No | -| | Microsoft.Windows.OOBENetworkConnectionFlow | x | x | x | No | -| | Microsoft.Windows.ParentalControls | x | x | x | No | -| People Hub | Microsoft.Windows.PeopleExperienceHost | x | x | x | No | -| | Microsoft.Windows.PinningConfirmationDialog | x | x | x | No | -| | Microsoft.Windows.SecHealthUI | x | x | x | No | -| | Microsoft.Windows.SecondaryTileExperience | x | | | No | -| | Microsoft.Windows.SecureAssessmentBrowser | x | x | x | No | -| Start | Microsoft.Windows.ShellExperienceHost | x | x | x | No | -| Windows Feedback | Microsoft.WindowsFeedback | * | | | No | -| | Microsoft.XboxGameCallableUI | x | x | x | No | -| | Windows.CBSPreview | | x | x | No | -| Contact Support* | Windows.ContactSupport | * | | | Via Settings App | -| Settings | Windows.immersivecontrolpanel | x | x | x | No | -| Print 3D | Windows.Print3D | | x | x | Yes | -| Print UI | Windows.PrintDialog | x | x | x | No | - - -> [!NOTE] -> The Contact Support app changed to Get Help in version 1709. Get Help is a provisioned app (instead of system app like Contact Support). - -## Installed Windows apps - -Here are the typical installed Windows apps in Windows 10 versions 1709, 1803, and 1809. - - -| Name | Full name | 1709 | 1803 | 1809 | Uninstall through UI? | -|-----------------------|------------------------------------------|:----:|:----:|:----:|:---------------------:| -| Remote Desktop | Microsoft.RemoteDesktop | x | | x | Yes | -| Code Writer | ActiproSoftwareLLC.562882FEEB491 | x | x | | Yes | -| Eclipse Manager | 46928bounde.EclipseManager | x | x | | Yes | -| Pandora | PandoraMediaInc.29680B314EFC2 | x | x | | Yes | -| Photoshop Express | AdobeSystemIncorporated. AdobePhotoshop | x | x | | Yes | -| Duolingo | D5EA27B7.Duolingo- LearnLanguagesforFree | x | x | | Yes | -| Network Speed Test | Microsoft.NetworkSpeedTest | x | x | x | Yes | -| News | Microsoft.BingNews | x | x | x | Yes | -| Sway | Microsoft.Office.Sway | x | x | x | Yes | -| Microsoft.Advertising | Microsoft.Advertising.Xaml | x | x | x | Yes | -| | Microsoft.NET.Native.Framework.1.2 | x | x | | Yes | -| | Microsoft.NET.Native.Framework.1.3 | x | x | | Yes | -| | Microsoft.NET.Native.Framework.1.6 | x | x | x | Yes | -| | Microsoft.NET.Native.Framework.1.7 | | x | x | Yes | -| | Microsoft.NET.Native.Framework.2.0 | x | x | | Yes | -| | Microsoft.NET.Native.Runtime.1.1 | x | x | | Yes | -| | Microsoft.NET.Native.Runtime.1.3 | x | | | Yes | -| | Microsoft.NET.Native.Runtime.1.4 | x | x | | Yes | -| | Microsoft.NET.Native.Runtime.1.6 | x | x | x | Yes | -| | Microsoft.NET.Native.Runtime.1.7 | x | x | x | Yes | -| | Microsoft.NET.Native.Runtime.2.0 | x | x | | Yes | -| | Microsoft.Services.Store.Engagement | x | x | | Yes | -| | Microsoft.VCLibs.120.00 | x | x | | Yes | -| | Microsoft.VCLibs.140.00 | x | x | x | Yes | -| | Microsoft.VCLibs.120.00.Universal | x | | | Yes | -| | Microsoft.VCLibs.140.00.UWPDesktop | | x | | Yes | - ---- diff --git a/windows/sv/index.md b/windows/sv/index.md index e69de29bb2..9796fd78a1 100644 --- a/windows/sv/index.md +++ b/windows/sv/index.md @@ -0,0 +1 @@ +# Welcome to sv \ No newline at end of file diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 81e3281c7d..45080d69f4 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -35,11 +35,11 @@ If you are looking for ways to optimize your approach to deploying Windows Sun V ## Determine eligibility -As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. The majority of devices purchased in the last 18-24 months will be compatible with Windows Sun Valley. Verify that your device meets or exceeds [Windows Sun Valley requirements](windows-sv-requirements.md) to ensure it is compatible. +As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. Most devices purchased in the last 18-24 months will be compatible with Windows Sun Valley. Verify that your device meets or exceeds [Windows Sun Valley requirements](windows-sv-requirements.md) to ensure it is compatible. -Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. End users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  +Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end-users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. End-users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  -Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software vendor partners to facilitate Windows Sun Valley device readiness into their solutions. +Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software publisher partners to facilitate Windows Sun Valley device readiness into their solutions. ## Windows Sun Valley availability @@ -56,7 +56,7 @@ If you manage devices on behalf of your organization, you will be able to upgrad > [!NOTE] > If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer version of the same product (Windows 10 to Windows 10), but they cannot migrate a device between products (Windows 10 to Windows Sun Valley).
-> Additionally, Windows Sun Valley has a new end user license agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new end user license agreements on behalf of the end users within your organization. +> Additionally, Windows Sun Valley has a new end-user license agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new end-user license agreements on behalf of the end-users within your organization. ##### Unmanaged devices @@ -86,15 +86,15 @@ The introduction of Windows Sun Valley is also a good time to review your hardwa ## Servicing and support -Along with end user experience and security improvements, Windows Sun Valley introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. +Along with end-user experience and security improvements, Windows Sun Valley introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. However, Microsoft will provide a single feature update annually, targeted for release in the second half of each calendar year. - Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the availability date. -- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the availabily date. +- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the availability date. When Windows Sun Valley reaches general availability, a consolidated Windows Sun Valley update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows Sun Valley servicing announcements, known issues, and safeguard holds. -It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about Windows 10 semi-annual channel and LTSC releases. +It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about Windows 10 Semi-Annual Channel and LTSC releases. ## Application compatibility @@ -106,7 +106,7 @@ If you run into compatibility issues or want to ensure that your organization's With enrollment in the [App Assure](/windows/compatibility/app-assure) service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy those application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. -For software vendors, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software vendors for participation by completing a short form. +For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index da5759ab4b..ee5d8fea7d 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -33,30 +33,30 @@ The tools that you use for heavy lifting during Windows 10 deployments can still #### On-premises solutions -- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. Once you sync the product category you will see Windows Sun Valley offered as an option. +- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. Once you sync the product category, you will see Windows Sun Valley offered as an option. > [!NOTE] -> During deployment, you will be prompted to agree to the license agreement on behalf of your end users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. +> During deployment, you will be prompted to agree to the license agreement on behalf of your end-users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. - If you use Microsoft Endpoint Configuration Manager, you can sync the new **Windows Sun Valley** product category and begin upgrading eligible devices. If you would like to validate Windows Sun Valley prior to release, you can sync the **Windows Insider Pre-release** category as well. > [!NOTE] -> Configuration Manager will prompt you to accept the end user license agreement on behalf of the users in your organization. +> Configuration Manager will prompt you to accept the end-user license agreement on behalf of the users in your organization. #### Cloud-based solutions - If you use Windows Update for Business Group Policy and Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product, but do not enable you to move between products (Windows 10 to Windows Sun Valley). - Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether using Windows Update for Business, Microsoft Intune, or other management tools. -- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to leverage **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Wndows 10 devices to Windows Sun Valley. You can then continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. +- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to leverage **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows Sun Valley. You can then continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. ## Cloud-based management -If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. Aside from consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end user privacy. +If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. Aside from consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end-user privacy. The following are some common use cases and the corresponding Microsoft Endpoint Manager capabilities that support them: - **Provision and pre-configure new Windows Sun Valley devices**: [Windows Autopilot](/mem/autopilot/windows-autopilot) enables you to deploy new Windows Sun Valley devices in a “business-ready” state that includes your desired applications, settings, and policies. It can also be used to change the edition of Windows. For example, you can upgrade from Pro to Enterprise edition and gain the use of advanced features. -- **Configure rules and control settings for users, apps, and devices for both Windows SV and Windows 10**: Devices that are enrolled in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) provide administrators with full control over apps, settings, features, and security. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. +- **Configure rules and control settings for users, apps, and devices**: Devices that are enrolled in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) provide administrators with full control over apps, settings, features, and security for both Windows Sun Valley and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. - **Streamlined, easy-to-manage devices for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley using Microsoft Endpoint Manager. If you are exclusively managing devices on-premises (for example, using Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune, making it easier to keep devices secure and up-to-date. @@ -84,7 +84,7 @@ To validate that your apps, infrastructure, and deployment processes are ready f If you use Windows Server Update Services, you can deploy directly from the Windows Insider Pre-release category using one of the following: - Set **Manage Preview Builds** to **Release Preview** in Windows Update for Business. -- Leverage Azure Virtual Desktop and Azure Marketplace images . +- Leverage Azure Virtual Desktop and Azure Marketplace images. - Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. Regardless of the method you choose, you have the benefit of free Microsoft support when validating pre-release builds. Free support is available to any commercial customer deploying Windows 10, version 21H2 or Windows Sun Valley, version 21H2 pre-release bits, once they become available through the Windows Insider Program. @@ -93,7 +93,7 @@ Regardless of the method you choose, you have the benefit of free Microsoft supp If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year that enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. -For those that are ready to explore Windows Sun Valley readiness right away, you can take advantage of Microsoft's **hardware eligibility assessment script**. This script includes instructions on how to deploy and aggregate your assessment results using Microsoft Intune or Configuration Manager, so you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. +If you are ready to explore Windows Sun Valley readiness right away, you can take advantage of Microsoft's [hardware eligibility assessment script](https://aka.ms/HWReadinessScript). This script includes instructions on how to deploy and aggregate your assessment results using Microsoft Intune or Configuration Manager, so you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. For more information, see [Understanding Windows Sun Valley readiness in your organization with Microsoft Endpoint Manager](https://aka.ms/HWReadinessBlog). ## Prepare a pilot deployment @@ -109,9 +109,9 @@ At a high level, the tasks involved are: 6. Test and support the pilot devices. 7. Determine broad deployment readiness based on the results of the pilot. -## End user readiness +## End-user readiness -To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end user readiness should not be overlooked. Windows Sun Valley has a familiar design, but end users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: +To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end-user readiness should not be overlooked. Windows Sun Valley has a familiar design, but end-users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: - Create a communications schedule to ensure that you provide the right communications at the right time to the right groups of users based on when they will see the changes. - Draft concise emails that inform users of what changes they can expect to see. Offer tips on how to use or customize their experience. Include information about support and help desk options. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index a1ae360f30..d3b9ece9e5 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -29,7 +29,7 @@ To install or upgrade to Windows Sun Valley, devices must meet the following min - Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](https://aka.ms/CPUlist) or system on a chip (SoC) - RAM: 4 gigabytes (GB) or greater -- Storage: 64GB or greater available storage is required to install Windows Sun Valley +- Storage: 64 GB or greater available storage is required to install Windows Sun Valley - Additional storage space might be required to download updates and enable specific features - Graphics card: Compatible with DirectX 12 or later with WDDM 2.0 driver - System firmware: UEFI, Secure Boot capable @@ -55,24 +55,24 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **5G support** requires 5G capable modem. - **Auto HDR** requires an HDR monitor. - **BitLocker to Go** requires a USB flash drive. This feature is available in Windows Pro and above editions. -- **Client Hyper-V** requires a processor with second level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. -- **Cortana** requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States -- **DirectStorage** requires 1TB or greater NVMe SSD to store and run games that uses the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU -- **DirectX 12 Ultimate** is available with supported games and graphics chips -- **Presence** requires sensor that can detect human distance from device or intent to interact with device -- **Intelligent Video Conferencing** requires video camera, microphone and speaker (audio output) -- **Multiple Voice Assistant** requires a microphone and speaker -- **Snap** three column layouts require a screen that is 1920 effective pixels or greater in width -- **Mute** and **unmute** from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute -- **Spatial Sound** requires supporting hardware and software -- **Microsoft Teams** requires video camera, microphone and speaker (audio output) -- **Touch** requires a screen or monitor that supports multi-touch -- **Two-factor authentication** requires use of PIN, biometric (fingerprint reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities -- **Voice Typing** requires a PC with a microphone -- **Wake on Voice** requires Modern Standby power model and microphone -- **Wi-Fi 6E** requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router +- **Client Hyper-V** requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. +- **Cortana** requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. +- **DirectStorage** requires 1 TB or greater NVMe SSD to store and run games that use the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU. +- **DirectX 12 Ultimate** is available with supported games and graphics chips. +- **Presence** requires sensor that can detect human distance from device or intent to interact with device. +- **Intelligent Video Conferencing** requires video camera, microphone, and speaker (audio output) +- **Multiple Voice Assistant** requires a microphone and speaker. +- **Snap** three column layouts require a screen that is 1920 effective pixels or greater in width. +- **Mute** and **unmute** from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute. +- **Spatial Sound** requires supporting hardware and software. +- **Microsoft Teams** requires video camera, microphone, and speaker (audio output). +- **Touch** requires a screen or monitor that supports multi-touch. +- **Two-factor authentication** requires use of PIN, biometric (fingerprint reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities. +- **Voice Typing** requires a PC with a microphone. +- **Wake on Voice** requires Modern Standby power model and microphone. +- **Wi-Fi 6E** requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router. - **Windows Hello** requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see [IT tools to support Windows 10, version 21H1](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/it-tools-to-support-windows-10-version-21h1/ba-p/2365103). -- **Windows Projection** requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct +- **Windows Projection** requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct. - **Xbox** app requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active Xbox Game Pass subscription. See https://www.xbox.com/xbox-game-pass to learn more about the pass. diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index fcbf1043e9..8c2564672a 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -22,17 +22,17 @@ ms.custom: seo-marvel-apr2020 - Windows Sun Valley, version 21H2 -This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next Windows client operating systgem release. +This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next Windows client operating system release. Also see the following articles to learn more about Windows Sun Valley: - [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. -- [Plan for Windows Sun Valley](windows-sv-plan.md): Information to help you plan for Windows Sun Valley in your organizatioin. +- [Plan for Windows Sun Valley](windows-sv-plan.md): Information to help you plan for Windows Sun Valley in your organization. - [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. ## Introduction -Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. +Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end-user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. @@ -46,11 +46,11 @@ For eligible PCs that are not managed by an organization, the Windows Sun Valley For more information about device eligibility, see [Windows Sun Valley requirements](windows-sv-requirements.md). -For those interested in testing Windows Sun Valley before general availability, you can join the [Windows Insider Program](https://insider.windows.com) or [Windows Insider Program for Business](https://insider.windows.com/for-business). You can also preview Windows Sun Valley by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). +If you are interested in testing Windows Sun Valley before general availability, you can join the [Windows Insider Program](https://insider.windows.com) or [Windows Insider Program for Business](https://insider.windows.com/for-business). You can also preview Windows Sun Valley by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). ## Before you begin -Many organizations will have a mixed environment of Windows Sun Valley and Windows 10 devices. The following is a quick summary of licensing, compatibility, management, and servicing considerations. +Many organizations will have a mixed environment of Windows Sun Valley and Windows 10 devices. The following sections provide a quick summary of licensing, compatibility, management, and servicing considerations. #### Licensing @@ -75,7 +75,7 @@ For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md #### Servicing Windows Sun Valley -Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available via a consolidated Windows SV update history page at that time as well. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). +Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available from a consolidated Windows Sun Valley update history page at that time as well. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). ## Next steps From ff368163501f4e9af127c97ffec4a515b6c021cf Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 12:28:02 -0700 Subject: [PATCH 080/104] fixes --- windows/sv/index.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/windows/sv/index.md b/windows/sv/index.md index 9796fd78a1..2217e6e08d 100644 --- a/windows/sv/index.md +++ b/windows/sv/index.md @@ -1 +1,5 @@ -# Welcome to sv \ No newline at end of file +--- +title: SV +author: greg-lindsay +ms.author: greglin +--- \ No newline at end of file From 98f5f95120a757da1ff7d3dfedfe44efc4ce8115 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 12:53:07 -0700 Subject: [PATCH 081/104] acrolinx --- windows/hub/index.yml | 2 +- windows/whats-new/windows-sv-prepare.md | 8 ++++---- windows/whats-new/windows-sv-requirements.md | 18 +++++++++--------- windows/whats-new/windows-sv.md | 2 +- 4 files changed, 15 insertions(+), 15 deletions(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index c745cb605b..0eeef6aed5 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -5,7 +5,7 @@ summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows metadata: title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Evaluate, plan, deploy, secure and manage devices running Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Evaluate, plan, deploy, secure, and manage devices running Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index ee5d8fea7d..4abb0e142c 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -75,13 +75,13 @@ For more information, see [Create a deployment plan](/windows/deployment/update/ #### Review policies -Review deployment-related polices, taking into consideration your organization's security objectives, update compliance deadlines, and device activity. Apply changes where you can gain a clear improvement, particularly with regard to the speed of the update process or security. +Review deployment-related policies, taking into consideration your organization's security objectives, update compliance deadlines, and device activity. Apply changes where you can gain a clear improvement, particularly with regard to the speed of the update process or security. #### Validate apps and infrastructure -To validate that your apps, infrastructure, and deployment processes are ready for Windows Sun Valley, join the [Windows Insider Program for Business](https://insider.windows.com/for-business-getting-started) and opt in to the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). +To validate that your apps, infrastructure, and deployment processes are ready for Windows Sun Valley, join the [Windows Insider Program for Business](https://insider.windows.com/for-business-getting-started), and opt in to the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). -If you use Windows Server Update Services, you can deploy directly from the Windows Insider Pre-release category using one of the following: +If you use Windows Server Update Services, you can deploy directly from the Windows Insider Pre-release category using one of the following processes: - Set **Manage Preview Builds** to **Release Preview** in Windows Update for Business. - Leverage Azure Virtual Desktop and Azure Marketplace images. @@ -111,7 +111,7 @@ At a high level, the tasks involved are: ## End-user readiness -To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end-user readiness should not be overlooked. Windows Sun Valley has a familiar design, but end-users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: +To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end-user readiness should not be overlooked. Windows Sun Valley has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: - Create a communications schedule to ensure that you provide the right communications at the right time to the right groups of users based on when they will see the changes. - Draft concise emails that inform users of what changes they can expect to see. Offer tips on how to use or customize their experience. Include information about support and help desk options. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index d3b9ece9e5..bcb173bfe8 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -27,14 +27,14 @@ This article lists the system requirements for Windows Sun Valley. Windows Sun V To install or upgrade to Windows Sun Valley, devices must meet the following minimum hardware requirements: -- Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](https://aka.ms/CPUlist) or system on a chip (SoC) -- RAM: 4 gigabytes (GB) or greater -- Storage: 64 GB or greater available storage is required to install Windows Sun Valley - - Additional storage space might be required to download updates and enable specific features -- Graphics card: Compatible with DirectX 12 or later with WDDM 2.0 driver -- System firmware: UEFI, Secure Boot capable -- TPM: Trusted Platform Module (TPM) version 2.0 -- Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel +- Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](https://aka.ms/CPUlist) or system on a chip (SoC). +- RAM: 4 gigabytes (GB) or greater. +- Storage: 64 GB or greater available storage is required to install Windows Sun Valley. + - Additional storage space might be required to download updates and enable specific features. +- Graphics card: Compatible with DirectX 12 or later with WDDM 2.0 driver. +- System firmware: UEFI, Secure Boot capable. +- TPM: Trusted Platform Module (TPM) version 2.0. +- Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel. - Internet connection: Internet connectivity is necessary to perform updates and to download and take advantage of some features. - Windows Sun Valley Home edition requires an Internet connection and a Microsoft Account to complete device setup on first use. @@ -62,7 +62,7 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **Presence** requires sensor that can detect human distance from device or intent to interact with device. - **Intelligent Video Conferencing** requires video camera, microphone, and speaker (audio output) - **Multiple Voice Assistant** requires a microphone and speaker. -- **Snap** three column layouts require a screen that is 1920 effective pixels or greater in width. +- **Snap** three-column layouts require a screen that is 1920 effective pixels or greater in width. - **Mute** and **unmute** from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute. - **Spatial Sound** requires supporting hardware and software. - **Microsoft Teams** requires video camera, microphone, and speaker (audio output). diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 8c2564672a..ae6a0260d0 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -75,7 +75,7 @@ For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md #### Servicing Windows Sun Valley -Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will available from a consolidated Windows Sun Valley update history page at that time as well. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). +Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will be available from a consolidated Windows Sun Valley update history page at that time as well. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). ## Next steps From 19ecc31a67c25c3c85f87993e789552d8d8b7114 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 13:03:50 -0700 Subject: [PATCH 082/104] acrolinx --- windows/sv/index.md | 5 ++++- windows/whats-new/windows-sv-plan.md | 10 +++++----- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/windows/sv/index.md b/windows/sv/index.md index 2217e6e08d..6f48df996d 100644 --- a/windows/sv/index.md +++ b/windows/sv/index.md @@ -1,5 +1,8 @@ --- title: SV +md.prod: w10 author: greg-lindsay ms.author: greglin ---- \ No newline at end of file +--- + +# \ No newline at end of file diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 45080d69f4..6cae30fc07 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -24,14 +24,14 @@ ms.topic: article This article provides guidance to help you plan for Windows Sun Valley in your organization. -Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) that are in place for Windows Sun Valley. At a high level, this strategy should include the following steps: +Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows Sun Valley. At a high level, this strategy should include the following steps: - [Create a deployment plan](/windows/deployment/update/create-deployment-plan) - [Define readiness criteria](/windows/deployment/update/plan-define-readiness) - [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) - [Determine application readiness](/windows/deployment/update/plan-determine-app-readiness) - [Define your servicing strategy](/windows/deployment/update/plan-define-strategy) -If you are looking for ways to optimize your approach to deploying Windows Sun Valley, or if deploying a new version of an operating system is not a familiar process for you, some additional items to consider are provided below. +If you are looking for ways to optimize your approach to deploying Windows Sun Valley, or if deploying a new version of an operating system is not a familiar process for you, some items to consider are provided below. ## Determine eligibility @@ -49,7 +49,7 @@ Windows Sun Valley will be offered to eligible Windows 10 devices beginning late Managed devices are devices that are under organization control. For example: devices managed by Microsoft Endpoint Manager (Microsoft Intune or Microsoft Endpoint Configuration Manager) or another endpoint management solution. -If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools at no cost when the upgrade reaches general availability. Organizations that use Windows Update for Business will have additional benefits, such as: +If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools at no cost when the upgrade reaches general availability. Organizations that use Windows Update for Business will have added benefits, such as: - Blocking the upgrade on non-eligible devices. - Additional insight into safeguard holds. While safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. @@ -60,7 +60,7 @@ If you manage devices on behalf of your organization, you will be able to upgrad ##### Unmanaged devices -Unmanaged devices are those that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. +Unmanaged devices are devices that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. Unmanaged eligible devices running Windows 10 that were purchased after June 2021 will be offered the Windows Sun Valley upgrade in the last quarter of the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. @@ -69,7 +69,7 @@ Unmanaged eligible devices running Windows 10 that were purchased after June 202 The Windows Sun Valley upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Microsoft Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. -Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This improves the update experience and ensures that devices first nominated for updates are those likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. +Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This process improves the update experience and ensures that devices first nominated for updates are the devices likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. ## Windows Sun Valley readiness considerations From a16c12781777c3e34e91a8e1811422139e3a9f47 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 14:01:55 -0700 Subject: [PATCH 083/104] some edits --- windows/whats-new/windows-sv-plan.md | 16 ++++-- windows/whats-new/windows-sv-prepare.md | 46 ++++++++-------- windows/whats-new/windows-sv-requirements.md | 55 ++++++++++---------- windows/whats-new/windows-sv.md | 12 +++-- 4 files changed, 71 insertions(+), 58 deletions(-) diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index 6cae30fc07..d1e4c7dbec 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -24,7 +24,9 @@ ms.topic: article This article provides guidance to help you plan for Windows Sun Valley in your organization. -Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows Sun Valley. At a high level, this strategy should include the following steps: +Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy that you use today for Windows 10. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows Sun Valley. + +At a high level, this strategy should include the following steps: - [Create a deployment plan](/windows/deployment/update/create-deployment-plan) - [Define readiness criteria](/windows/deployment/update/plan-define-readiness) - [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) @@ -88,13 +90,17 @@ The introduction of Windows Sun Valley is also a good time to review your hardwa Along with end-user experience and security improvements, Windows Sun Valley introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. -Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. However, Microsoft will provide a single feature update annually, targeted for release in the second half of each calendar year. +**Quality updates**: Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. + +**Feature updates**: Microsoft will provide a single feature update annually, targeted for release in the second half of each calendar year. + +**Lifecycle**: - Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the availability date. - Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the availability date. When Windows Sun Valley reaches general availability, a consolidated Windows Sun Valley update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows Sun Valley servicing announcements, known issues, and safeguard holds. -It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about Windows 10 Semi-Annual Channel and LTSC releases. +It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about the Windows 10 Semi-Annual Channel and Long-term Servicing Channel (LTSC) releases. ## Application compatibility @@ -104,9 +110,9 @@ Microsoft's compatibility promise for Windows 10 is maintained for Windows Sun V If you run into compatibility issues or want to ensure that your organization's applications are compatible from day one, App Assure and Test Base for Microsoft 365 can help. -With enrollment in the [App Assure](/windows/compatibility/app-assure) service, if you find any problems with an existing application as you migrate to Windows Sun Valley, Microsoft will help you remedy those application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. +**App Assure**: With enrollment in the [App Assure](/windows/compatibility/app-assure) service, any app compatibility issues that you find with Windows Sun Valley can be resolved. Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. -For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. +**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 4abb0e142c..5220b153c3 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -20,58 +20,59 @@ ms.topic: article - Windows Sun Valley, version 21H2 -Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. One common management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. +Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. One management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. -After you evaluate your hardware to see if it meets [requirements](windows-sv-requirements.md) for Windows Sun Valley, it's also a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. +After you evaluate your hardware to see if it meets [requirements](windows-sv-requirements.md) for Windows Sun Valley, it's also a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. This article provides some helpful guidance to accomplish these tasks. ## Infrastructure and tools The tools that you use for heavy lifting during Windows 10 deployments can still be leveraged for Windows Sun Valley. A few nuanced differences are described below. -> [!IMPORTANT] -> Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows Sun Valley, particularly if they provide security or data loss prevention capabilities. + > [!IMPORTANT] + > Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows Sun Valley, particularly if they provide security or data loss prevention capabilities. #### On-premises solutions - If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. Once you sync the product category, you will see Windows Sun Valley offered as an option. -> [!NOTE] -> During deployment, you will be prompted to agree to the license agreement on behalf of your end-users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. + > [!NOTE] + > During deployment, you will be prompted to agree to the end-user license agreement on behalf of your users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. - If you use Microsoft Endpoint Configuration Manager, you can sync the new **Windows Sun Valley** product category and begin upgrading eligible devices. If you would like to validate Windows Sun Valley prior to release, you can sync the **Windows Insider Pre-release** category as well. -> [!NOTE] -> Configuration Manager will prompt you to accept the end-user license agreement on behalf of the users in your organization. + > [!NOTE] + > Configuration Manager will prompt you to accept the end-user license agreement on behalf of the users in your organization. #### Cloud-based solutions -- If you use Windows Update for Business Group Policy and Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product, but do not enable you to move between products (Windows 10 to Windows Sun Valley). -- Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether using Windows Update for Business, Microsoft Intune, or other management tools. -- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to leverage **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows Sun Valley. You can then continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. +- If you use Windows Update for Business Group Policy and Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product (Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows Sun Valley). +- Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether you are using Windows Update for Business, Microsoft Intune, or other management tools. +- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows Sun Valley. You can also continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. ## Cloud-based management -If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. Aside from consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end-user privacy. +If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. In addition to consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end-user privacy. The following are some common use cases and the corresponding Microsoft Endpoint Manager capabilities that support them: - **Provision and pre-configure new Windows Sun Valley devices**: [Windows Autopilot](/mem/autopilot/windows-autopilot) enables you to deploy new Windows Sun Valley devices in a “business-ready” state that includes your desired applications, settings, and policies. It can also be used to change the edition of Windows. For example, you can upgrade from Pro to Enterprise edition and gain the use of advanced features. - **Configure rules and control settings for users, apps, and devices**: Devices that are enrolled in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) provide administrators with full control over apps, settings, features, and security for both Windows Sun Valley and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. -- **Streamlined, easy-to-manage devices for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley using Microsoft Endpoint Manager. +- **Streamlined, easy-to-manage devices for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley by using Microsoft Endpoint Manager. -If you are exclusively managing devices on-premises (for example, using Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune, making it easier to keep devices secure and up-to-date. +If you are exclusively managing devices on-premise (for example, using Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune, making it easier to keep devices secure and up-to-date. ## Review servicing approach and policies -Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. Every organization will transition to Windows Sun Valley at its own pace. However, thinking of operating system updates as an ongoing process improve your ability to deploy feature and quality updates, and enable you to stay current with less effort and impact on productivity. +Every organization will transition to Windows Sun Valley at its own pace. Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. -To begin, think about how you roll out Windows feature updates today: which devices, and at what pace. Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: +When you think of operating system updates as an ongoing process, you will automatically improve your ability to deploy updates. This enables you to stay current with less effort and impact on productivity. To begin, think about how you roll out Windows feature updates today: which devices, and at what pace. +Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: - Preview (first or canary): Planning and development - Limited (fast or early adopters): Pilot and validation - Broad (users or critical): Wide deployment -For more information, see [Create a deployment plan](/windows/deployment/update/create-deployment-plan). +For detailed information, see [Create a deployment plan](/windows/deployment/update/create-deployment-plan). #### Review policies @@ -91,13 +92,15 @@ Regardless of the method you choose, you have the benefit of free Microsoft supp #### Analytics and assessment tools -If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year that enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. +If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year. This tool enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. -If you are ready to explore Windows Sun Valley readiness right away, you can take advantage of Microsoft's [hardware eligibility assessment script](https://aka.ms/HWReadinessScript). This script includes instructions on how to deploy and aggregate your assessment results using Microsoft Intune or Configuration Manager, so you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. For more information, see [Understanding Windows Sun Valley readiness in your organization with Microsoft Endpoint Manager](https://aka.ms/HWReadinessBlog). +If you are ready to explore Windows Sun Valley readiness right away, you can take advantage of Microsoft's [hardware eligibility assessment script](https://aka.ms/HWReadinessScript). This script includes instructions on how to deploy and aggregate your assessment results using Microsoft Intune or Configuration Manager, so you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. + +For more information, see [Understanding Windows Sun Valley readiness in your organization with Microsoft Endpoint Manager](https://aka.ms/HWReadinessBlog). ## Prepare a pilot deployment -A pilot deployment is a proof of concept that rolls out an upgrade to a select number of devices in production before deploying it broadly across the organization. +A pilot deployment is a proof of concept that rolls out an upgrade to a select number of devices in production, before deploying it broadly across the organization. At a high level, the tasks involved are: @@ -112,8 +115,7 @@ At a high level, the tasks involved are: ## End-user readiness To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end-user readiness should not be overlooked. Windows Sun Valley has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: - -- Create a communications schedule to ensure that you provide the right communications at the right time to the right groups of users based on when they will see the changes. +- Create a communications schedule to ensure that you provide the right message at the right time to the right groups of users, based on when they will see the changes. - Draft concise emails that inform users of what changes they can expect to see. Offer tips on how to use or customize their experience. Include information about support and help desk options. - Update help desk manuals with screenshots of the new user interface, the out-of-box experience for new devices, and the upgrade experience for existing devices. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index bcb173bfe8..f32476c8f3 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -31,14 +31,14 @@ To install or upgrade to Windows Sun Valley, devices must meet the following min - RAM: 4 gigabytes (GB) or greater. - Storage: 64 GB or greater available storage is required to install Windows Sun Valley. - Additional storage space might be required to download updates and enable specific features. -- Graphics card: Compatible with DirectX 12 or later with WDDM 2.0 driver. +- Graphics card: Compatible with DirectX 12 or later, with a WDDM 2.0 driver. - System firmware: UEFI, Secure Boot capable. - TPM: Trusted Platform Module (TPM) version 2.0. - Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel. -- Internet connection: Internet connectivity is necessary to perform updates and to download and take advantage of some features. +- Internet connection: Internet connectivity is necessary to perform updates, download, and use some features. - Windows Sun Valley Home edition requires an Internet connection and a Microsoft Account to complete device setup on first use. -For additional guidance, see [Determine eligibility](windows-sv-plan.md#determine-eligibility). +For information about tools to evaluate readiness, see [Determine eligibility](windows-sv-plan.md#determine-eligibility). ## Operating system requirements @@ -46,34 +46,35 @@ For the best Windows Sun Valley upgrade experience, eligible devices should be r > [!NOTE] > S mode is not supported on Windows Sun Valley. -> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading. Switching a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you cannot switch back to S mode later. +> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading.
+> Switching a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you cannot switch back to S mode later. ## Feature-specific requirements -Some features in Windows Sun Valley have requirements beyond those listed above. See the following list: +Some features in Windows Sun Valley have requirements beyond those listed above. See the following list of features and associated requirements. -- **5G support** requires 5G capable modem. -- **Auto HDR** requires an HDR monitor. -- **BitLocker to Go** requires a USB flash drive. This feature is available in Windows Pro and above editions. -- **Client Hyper-V** requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. -- **Cortana** requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. -- **DirectStorage** requires 1 TB or greater NVMe SSD to store and run games that use the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU. -- **DirectX 12 Ultimate** is available with supported games and graphics chips. -- **Presence** requires sensor that can detect human distance from device or intent to interact with device. -- **Intelligent Video Conferencing** requires video camera, microphone, and speaker (audio output) -- **Multiple Voice Assistant** requires a microphone and speaker. -- **Snap** three-column layouts require a screen that is 1920 effective pixels or greater in width. -- **Mute** and **unmute** from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute. -- **Spatial Sound** requires supporting hardware and software. -- **Microsoft Teams** requires video camera, microphone, and speaker (audio output). -- **Touch** requires a screen or monitor that supports multi-touch. -- **Two-factor authentication** requires use of PIN, biometric (fingerprint reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities. -- **Voice Typing** requires a PC with a microphone. -- **Wake on Voice** requires Modern Standby power model and microphone. -- **Wi-Fi 6E** requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router. -- **Windows Hello** requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see [IT tools to support Windows 10, version 21H1](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/it-tools-to-support-windows-10-version-21h1/ba-p/2365103). -- **Windows Projection** requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct. -- **Xbox** app requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active Xbox Game Pass subscription. See https://www.xbox.com/xbox-game-pass to learn more about the pass. +- **5G support**: requires 5G capable modem. +- **Auto HDR**: requires an HDR monitor. +- **BitLocker to Go**: requires a USB flash drive. This feature is available in Windows Pro and above editions. +- **Client Hyper-V**: requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. +- **Cortana**: requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. +- **DirectStorage**: requires 1 TB or greater NVMe SSD to store and run games that use the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU. +- **DirectX 12 Ultimate**: is available with supported games and graphics chips. +- **Presence**: requires sensor that can detect human distance from device or intent to interact with device. +- **Intelligent Video Conferencing**: requires video camera, microphone, and speaker (audio output) +- **Multiple Voice Assistant**: requires a microphone and speaker. +- **Snap**: three-column layouts require a screen that is 1920 effective pixels or greater in width. +- **Mute** and **unmute**: from Taskbar requires video camera, microphone, and speaker (audio output). App must be compatible with feature to enable global mute/unmute. +- **Spatial Sound**: requires supporting hardware and software. +- **Microsoft Teams**: requires video camera, microphone, and speaker (audio output). +- **Touch**: requires a screen or monitor that supports multi-touch. +- **Two-factor authentication**: requires use of PIN, biometric (fingerprint reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities. +- **Voice Typing**: requires a PC with a microphone. +- **Wake on Voice**: requires Modern Standby power model and microphone. +- **Wi-Fi 6E**: requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router. +- **Windows Hello**: requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see [IT tools to support Windows 10, version 21H1](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/it-tools-to-support-windows-10-version-21h1/ba-p/2365103). +- **Windows Projection**: requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct. +- **Xbox app**: requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active Xbox Game Pass subscription. See https://www.xbox.com/xbox-game-pass to learn more about the pass. ## Next steps diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index ae6a0260d0..335297ca86 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -36,6 +36,8 @@ Windows Sun Valley is the next evolution of Windows; the most significant update This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. +After Windows Sun Valley is generally available, it is expected that many organizations will have a mixed environment of Windows Sun Valley and Windows 10 devices. The guidance provided here can help you to manage this hybrid environment. + ## How to get Windows Sun Valley Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10, beginning later in the 2021 calendar year. Windows Sun Valley will also be available on eligible new devices. @@ -50,7 +52,7 @@ If you are interested in testing Windows Sun Valley before general availability, ## Before you begin -Many organizations will have a mixed environment of Windows Sun Valley and Windows 10 devices. The following sections provide a quick summary of licensing, compatibility, management, and servicing considerations. +The following sections provide a quick summary of licensing, compatibility, management, and servicing considerations to help you get started with Windows Sun Valley. #### Licensing @@ -62,11 +64,11 @@ Microsoft 365 licenses that include Windows 10 licenses will permit you to run W Most accessories and associated drivers that work with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. -Windows Sun Valley preserves the application compatibility promise made with Windows 10 and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-plan.md#application-compatibility). +Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-plan.md#application-compatibility). #### Familiar processes -Windows Sun Valley is built on the same foundation as Windows 10, so generally you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. If you use non-Microsoft tools, check with your vendor to verify compatibility. +Windows Sun Valley is built on the same foundation as Windows 10. Typically, you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will also work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. > [!IMPORTANT] > Check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows Sun Valley, particularly those providing security or data loss prevention capabilities. @@ -75,7 +77,9 @@ For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md #### Servicing Windows Sun Valley -Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have an annual feature update cadence. When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will be available from a consolidated Windows Sun Valley update history page at that time as well. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). +Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have a new feature update cadence. Windows Sun Valley feature updates will be released once per year. + +When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will also be available from a consolidated Windows Sun Valley update history page at that time. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). ## Next steps From 5e7dcbac9d78e94a8c48259b510b325eecb28160 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 22 Jun 2021 14:20:10 -0700 Subject: [PATCH 084/104] some edits --- windows/deployment/deploy-whats-new.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index 03d5ce122e..583e4392a1 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -20,14 +20,13 @@ ms.custom: seo-marvel-apr2020 **Applies to:** - Windows 10 -- Windows 11 ## In this topic This topic provides an overview of new solutions and online content related to deploying Windows client in your organization. - For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index). -- For an all-up overview of new features in Windows 11, see [What's new in Windows 11](/windows/whats-new/index). +- For an overview of Windows Sun Valley, see [What's new in Windows Sun Valley](/windows/whats-new/windows-sv). ## Latest news From 6c92cd3cdbba8167b1fef020426b49f0b1d58710 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 23 Jun 2021 13:54:22 -0700 Subject: [PATCH 085/104] incorp changes --- windows/hub/index.yml | 2 +- windows/whats-new/windows-sv-plan.md | 39 ++++++++--------- windows/whats-new/windows-sv-prepare.md | 45 +++++++++----------- windows/whats-new/windows-sv-requirements.md | 18 ++++---- windows/whats-new/windows-sv.md | 16 +++---- 5 files changed, 57 insertions(+), 63 deletions(-) diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 0eeef6aed5..846ee4e900 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -34,7 +34,7 @@ landingContent: url: /windows/whats-new/windows-sv-plan - text: Prepare for Windows Sun Valley url: /windows/whats-new/windows-sv-prepare - - text: What's new in Windows 10, version 21H2 + - text: What's new in Windows 10, version 21H1 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: Windows release information url: /windows/release-health/release-information diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md index d1e4c7dbec..11aa8a3ddc 100644 --- a/windows/whats-new/windows-sv-plan.md +++ b/windows/whats-new/windows-sv-plan.md @@ -18,13 +18,13 @@ ms.topic: article **Applies to** -- Windows Sun Valley, version 21H2 +- Windows Sun Valley ## Deployment planning This article provides guidance to help you plan for Windows Sun Valley in your organization. -Since Windows Sun Valley is built on the same foundation as Windows 10, you can utilize the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy that you use today for Windows 10. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows Sun Valley. +Since Windows Sun Valley is built on the same foundation as Windows 10, you can use the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy that you use today for Windows 10. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows Sun Valley. At a high level, this strategy should include the following steps: - [Create a deployment plan](/windows/deployment/update/create-deployment-plan) @@ -39,48 +39,45 @@ If you are looking for ways to optimize your approach to deploying Windows Sun V As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. Most devices purchased in the last 18-24 months will be compatible with Windows Sun Valley. Verify that your device meets or exceeds [Windows Sun Valley requirements](windows-sv-requirements.md) to ensure it is compatible. -Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end-users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. End-users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  +Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end-users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. end-users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  -Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software publisher partners to facilitate Windows Sun Valley device readiness into their solutions. +Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software publishing partners to facilitate adding Windows Sun Valley device support into their solutions. ## Windows Sun Valley availability -Windows Sun Valley will be offered to eligible Windows 10 devices beginning later in the 2021 calendar year. The availability of Windows Sun Valley will vary according to a device's hardware and whether or not the device receives updates directly or from a management solution that is maintained by an IT administrator. +The availability of Windows Sun Valley will vary according to a device's hardware and whether the device receives updates directly, or from a management solution that is maintained by an IT administrator. ##### Managed devices -Managed devices are devices that are under organization control. For example: devices managed by Microsoft Endpoint Manager (Microsoft Intune or Microsoft Endpoint Configuration Manager) or another endpoint management solution. +Managed devices are devices that are under organization control. Managed devices include those managed by Microsoft Intune, Microsoft Endpoint Configuration Manager, or other endpoint management solutions. If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools at no cost when the upgrade reaches general availability. Organizations that use Windows Update for Business will have added benefits, such as: -- Blocking the upgrade on non-eligible devices. +- Ensuring that devices that don't meet the minimum hardware requirements are not automatically offered the Windows Sun Valley upgrade. - Additional insight into safeguard holds. While safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. > [!NOTE] -> If you use WUfB to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer version of the same product (Windows 10 to Windows 10), but they cannot migrate a device between products (Windows 10 to Windows Sun Valley).
-> Additionally, Windows Sun Valley has a new end-user license agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new end-user license agreements on behalf of the end-users within your organization. +> If you use Windows Update for Business to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer version of the same product (from example, from Windows 10, version 20H2 to 21H1), but they cannot migrate a device between products (from Windows 10 to Windows Sun Valley).
+> Additionally, Windows Sun Valley has a new End User License Agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new End User License Agreement on behalf of the end-users within your organization. ##### Unmanaged devices Unmanaged devices are devices that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. -Unmanaged eligible devices running Windows 10 that were purchased after June 2021 will be offered the Windows Sun Valley upgrade in the last quarter of the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. +Windows Sun Valley will be offered to eligible Windows 10 devices beginning later in the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. -> [!NOTE] -> New devices purchased after October 2021 will see the Windows Sun Valley offer during the out of box experience (OOBE), or they will already be upgraded to Windows Sun Valley. - -The Windows Sun Valley upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Microsoft Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. +The Windows Sun Valley upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Windows Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This process improves the update experience and ensures that devices first nominated for updates are the devices likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. ## Windows Sun Valley readiness considerations -The recommended method for organizations to determine if their infrastructure, deployment processes, and management tools are ready for Windows Sun Valley is to join the [Windows Insider Program for Business](https://insider.windows.com/for-business). As a participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), you can validate that your devices and applications work as expected, and explore new features in details. +The recommended method to determine if your infrastructure, deployment processes, and management tools are ready for Windows Sun Valley is to join the [Windows Insider Program for Business](https://insider.windows.com/for-business). As a participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), you can validate that your devices and applications work as expected, and explore new features. As you plan your endpoint management strategy for Windows Sun Valley, consider moving to cloud-based mobile device management (MDM), such as [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). If a cloud-only approach isn't right for your organization just yet, you can still modernize and streamline essential pieces of your endpoint management strategy as follows: - Create a [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview) (CMG) to manage Configuration Manager clients over the internet. - Attach your existing Configuration Management estate to the cloud with [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions) so you can manage all devices from within the Microsoft Endpoint Manager admin center. -- Use [co-management](/mem/configmgr/comanage/overview) to concurrently manage devices using both Configuration Manager and Microsoft Intune, allowing you to take advantage of cloud-powered capabilities like [Conditional Access](/azure/active-directory/conditional-access/overview). +- Use [co-management](/mem/configmgr/comanage/overview) to concurrently manage devices using both Configuration Manager and Microsoft Intune. This allows you to take advantage of cloud-powered capabilities like [Conditional Access](/azure/active-directory/conditional-access/overview). For more information on the benefits of these approaches, see [Cloud Attach Your Future: The Big 3](https://techcommunity.microsoft.com/t5/configuration-manager-blog/cloud-attach-your-future-part-ii-quot-the-big-3-quot/ba-p/1750664). @@ -92,11 +89,11 @@ Along with end-user experience and security improvements, Windows Sun Valley int **Quality updates**: Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. -**Feature updates**: Microsoft will provide a single feature update annually, targeted for release in the second half of each calendar year. +**Feature updates**: Microsoft will provide a single Windows Sun Valley feature update annually, targeted for release in the second half of each calendar year. **Lifecycle**: -- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the availability date. -- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the availability date. +- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the general availability date. +- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the general availability date. When Windows Sun Valley reaches general availability, a consolidated Windows Sun Valley update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows Sun Valley servicing announcements, known issues, and safeguard holds. @@ -104,7 +101,7 @@ It is important that organizations have adequate time to plan for Windows Sun Va ## Application compatibility -Microsoft's compatibility promise for Windows 10 is maintained for Windows Sun Valley. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for enterprise organizations, including line of business (LOB) apps. Microsoft remains committed to ensuring that the apps you rely upon continue to work as expected when you upgrade. Windows Sun Valley is subject to the same app compatibility validation requirements that are in place for Windows 10 today, and it is passing these requirements. +Microsoft's compatibility promise for Windows 10 is maintained for Windows Sun Valley. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for enterprise organizations, including line of business (LOB) apps. Microsoft remains committed to ensuring that the apps you rely upon continue to work as expected when you upgrade. Windows Sun Valley is subject to the same app compatibility validation requirements that are in place for Windows 10 today, for both feature and quality updates. #### App Assure and Test Base for Microsoft 365 @@ -122,4 +119,4 @@ You might already be using App Assure and Test Base in your Windows 10 environme ## Also see -Learning module +[Plan to deploy updates for Windows 10 and Microsoft 365 Apps](/learn/modules/windows-plan/) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index 5220b153c3..dfca52badf 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -18,54 +18,54 @@ ms.topic: article **Applies to** -- Windows Sun Valley, version 21H2 +- Windows Sun Valley -Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. One management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. +Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. Using a single management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. -After you evaluate your hardware to see if it meets [requirements](windows-sv-requirements.md) for Windows Sun Valley, it's also a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. This article provides some helpful guidance to accomplish these tasks. +After you evaluate your hardware to see if it meets [requirements](windows-sv-requirements.md) for Windows Sun Valley, it's a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. This article provides some helpful guidance to accomplish these tasks. ## Infrastructure and tools -The tools that you use for heavy lifting during Windows 10 deployments can still be leveraged for Windows Sun Valley. A few nuanced differences are described below. +The tools that you use for core workloads during Windows 10 deployments can still be leveraged for Windows Sun Valley. A few nuanced differences are described below. > [!IMPORTANT] > Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows Sun Valley, particularly if they provide security or data loss prevention capabilities. -#### On-premises solutions +#### On-premise solutions -- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. Once you sync the product category, you will see Windows Sun Valley offered as an option. +- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. After you sync the product category, you will see Windows Sun Valley offered as an option. If you would like to validate Windows Sun Valley prior to release, you can sync the Windows Insider Pre-release category as well. > [!NOTE] - > During deployment, you will be prompted to agree to the end-user license agreement on behalf of your users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. + > During deployment, you will be prompted to agree to the End User License Agreement on behalf of your users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. - If you use Microsoft Endpoint Configuration Manager, you can sync the new **Windows Sun Valley** product category and begin upgrading eligible devices. If you would like to validate Windows Sun Valley prior to release, you can sync the **Windows Insider Pre-release** category as well. > [!NOTE] - > Configuration Manager will prompt you to accept the end-user license agreement on behalf of the users in your organization. + > Configuration Manager will prompt you to accept the End User License Agreement on behalf of the users in your organization. #### Cloud-based solutions -- If you use Windows Update for Business Group Policy and Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product (Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows Sun Valley). -- Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true whether you are using Windows Update for Business, Microsoft Intune, or other management tools. +- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows Sun Valley). +- Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true regardless of which management tool you use to configure Windows Update for Business policies. - If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows Sun Valley. You can also continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. ## Cloud-based management -If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. In addition to consolidating device management and endpoint security into a single platform, it can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end-user privacy. +If you aren’t already taking advantage of cloud-based management capabilities, like those available in [Microsoft Endpoint Manager](/mem/endpoint-manager-overview), it's worth considering. In addition to consolidating device management and endpoint security into a single platform, Microsoft Endpoint Manager can better support the diverse bring-your-own-device (BYOD) ecosystem that is increasingly the norm with hybrid work scenarios. It can also enable you to track your progress against compliance and business objectives, while protecting end-user privacy. The following are some common use cases and the corresponding Microsoft Endpoint Manager capabilities that support them: - **Provision and pre-configure new Windows Sun Valley devices**: [Windows Autopilot](/mem/autopilot/windows-autopilot) enables you to deploy new Windows Sun Valley devices in a “business-ready” state that includes your desired applications, settings, and policies. It can also be used to change the edition of Windows. For example, you can upgrade from Pro to Enterprise edition and gain the use of advanced features. -- **Configure rules and control settings for users, apps, and devices**: Devices that are enrolled in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) provide administrators with full control over apps, settings, features, and security for both Windows Sun Valley and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. -- **Streamlined, easy-to-manage devices for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley by using Microsoft Endpoint Manager. +- **Configure rules and control settings for users, apps, and devices**: When you enroll devices in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), administrators have full control over apps, settings, features, and security for both Windows Sun Valley and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. +- **Streamline device management for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley by using Microsoft Endpoint Manager. -If you are exclusively managing devices on-premise (for example, using Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune, making it easier to keep devices secure and up-to-date. +If you are exclusively using an on-premise device management solution (for example, Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune. These solutions can make it easier to keep devices secure and up-to-date. ## Review servicing approach and policies Every organization will transition to Windows Sun Valley at its own pace. Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. -When you think of operating system updates as an ongoing process, you will automatically improve your ability to deploy updates. This enables you to stay current with less effort and impact on productivity. To begin, think about how you roll out Windows feature updates today: which devices, and at what pace. +When you think of operating system updates as an ongoing process, you will automatically improve your ability to deploy updates. This approach enables you to stay current with less effort, and less impact on productivity. To begin, think about how you roll out Windows feature updates today: which devices, and at what pace. Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: - Preview (first or canary): Planning and development @@ -88,15 +88,11 @@ If you use Windows Server Update Services, you can deploy directly from the Wind - Leverage Azure Virtual Desktop and Azure Marketplace images. - Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. -Regardless of the method you choose, you have the benefit of free Microsoft support when validating pre-release builds. Free support is available to any commercial customer deploying Windows 10, version 21H2 or Windows Sun Valley, version 21H2 pre-release bits, once they become available through the Windows Insider Program. +Regardless of the method you choose, you have the benefit of free Microsoft support when validating pre-release builds. Free support is available to any commercial customer deploying Windows 10 or Windows Sun Valley Preview Builds, once they become available through the Windows Insider Program. #### Analytics and assessment tools -If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year. This tool enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. - -If you are ready to explore Windows Sun Valley readiness right away, you can take advantage of Microsoft's [hardware eligibility assessment script](https://aka.ms/HWReadinessScript). This script includes instructions on how to deploy and aggregate your assessment results using Microsoft Intune or Configuration Manager, so you can quickly determine how many of your devices meet the hardware requirements for Windows Sun Valley. - -For more information, see [Understanding Windows Sun Valley readiness in your organization with Microsoft Endpoint Manager](https://aka.ms/HWReadinessBlog). +If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year. This tool enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. ## Prepare a pilot deployment @@ -112,9 +108,9 @@ At a high level, the tasks involved are: 6. Test and support the pilot devices. 7. Determine broad deployment readiness based on the results of the pilot. -## End-user readiness +## end-user readiness -To prepare an effective, enterprise-wide deployment of Windows Sun Valley, the importance of end-user readiness should not be overlooked. Windows Sun Valley has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: +Do not overlook the importance of end-user readiness to deliver an effective, enterprise-wide deployment of Windows Sun Valley. Windows Sun Valley has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: - Create a communications schedule to ensure that you provide the right message at the right time to the right groups of users, based on when they will see the changes. - Draft concise emails that inform users of what changes they can expect to see. Offer tips on how to use or customize their experience. Include information about support and help desk options. - Update help desk manuals with screenshots of the new user interface, the out-of-box experience for new devices, and the upgrade experience for existing devices. @@ -125,4 +121,5 @@ See the [Stay current with Windows 10 and Microsoft 365 Apps](/learn/paths/m365- ## See also -[Windows Sun Valley deployment planning](windows-sv-plan.md) +[Plan for Windows Sun Valley](windows-sv-plan.md)
+[Windows help & learning](https://support.microsoft.com/windows) diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index f32476c8f3..75dffa0e7b 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -19,7 +19,7 @@ ms.custom: seo-marvel-apr2020 **Applies to** -- Windows Sun Valley, version 21H2 +- Windows Sun Valley This article lists the system requirements for Windows Sun Valley. Windows Sun Valley is also supported on a virtual machine (VM). @@ -29,15 +29,17 @@ To install or upgrade to Windows Sun Valley, devices must meet the following min - Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](https://aka.ms/CPUlist) or system on a chip (SoC). - RAM: 4 gigabytes (GB) or greater. -- Storage: 64 GB or greater available storage is required to install Windows Sun Valley. +- Storage: 64 GB\* or greater available storage is required to install Windows Sun Valley. - Additional storage space might be required to download updates and enable specific features. - Graphics card: Compatible with DirectX 12 or later, with a WDDM 2.0 driver. - System firmware: UEFI, Secure Boot capable. -- TPM: Trusted Platform Module (TPM) version 2.0. +- TPM: [Trusted Platform Module](/windows/security/information-protection/tpm/trusted-platform-module-overview) (TPM) version 2.0. - Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel. -- Internet connection: Internet connectivity is necessary to perform updates, download, and use some features. +- Internet connection: Internet connectivity is necessary to perform updates, and to download and use some features. - Windows Sun Valley Home edition requires an Internet connection and a Microsoft Account to complete device setup on first use. +\* There might be additional requirements over time for updates, and to enable specific features within the operating system. For more information, see [Keeping Windows Sun Valley up-to-date](https://www.microsoft.com/windows/windows-10-specifications#primaryR5). + For information about tools to evaluate readiness, see [Determine eligibility](windows-sv-plan.md#determine-eligibility). ## Operating system requirements @@ -46,7 +48,7 @@ For the best Windows Sun Valley upgrade experience, eligible devices should be r > [!NOTE] > S mode is not supported on Windows Sun Valley. -> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading.
+> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading.
 
> Switching a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you cannot switch back to S mode later. ## Feature-specific requirements @@ -59,7 +61,7 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **Client Hyper-V**: requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. - **Cortana**: requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. - **DirectStorage**: requires 1 TB or greater NVMe SSD to store and run games that use the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU. -- **DirectX 12 Ultimate**: is available with supported games and graphics chips. +- **DirectX 12 Ultimate**: available with supported games and graphics chips. - **Presence**: requires sensor that can detect human distance from device or intent to interact with device. - **Intelligent Video Conferencing**: requires video camera, microphone, and speaker (audio output) - **Multiple Voice Assistant**: requires a microphone and speaker. @@ -74,12 +76,12 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **Wi-Fi 6E**: requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router. - **Windows Hello**: requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see [IT tools to support Windows 10, version 21H1](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/it-tools-to-support-windows-10-version-21h1/ba-p/2365103). - **Windows Projection**: requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct. -- **Xbox app**: requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active Xbox Game Pass subscription. See https://www.xbox.com/xbox-game-pass to learn more about the pass. +- **Xbox app**: requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active [Xbox Game Pass](https://www.xbox.com/xbox-game-pass) subscription. ## Next steps -[Plan to deploy Windows Sun Valley](windows-sv-plan.md)
+[Plan for Windows Sun Valley](windows-sv-plan.md)
[Prepare for Windows Sun Valley](windows-sv-prepare.md) ## See also diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md index 335297ca86..392951b9ff 100644 --- a/windows/whats-new/windows-sv.md +++ b/windows/whats-new/windows-sv.md @@ -20,9 +20,9 @@ ms.custom: seo-marvel-apr2020 **Applies to** -- Windows Sun Valley, version 21H2 +- Windows Sun Valley -This article provides an introduction and answers some frequently asked questions about Windows Sun Valley, the next Windows client operating system release. +This article provides an introduction to Windows Sun Valley, and answers some frequently asked questions. Also see the following articles to learn more about Windows Sun Valley: @@ -32,19 +32,17 @@ Also see the following articles to learn more about Windows Sun Valley: ## Introduction -Windows Sun Valley is the next evolution of Windows; the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end-user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. +Windows Sun Valley is the next evolution of Windows; it is the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end-user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. -This release is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. - -After Windows Sun Valley is generally available, it is expected that many organizations will have a mixed environment of Windows Sun Valley and Windows 10 devices. The guidance provided here can help you to manage this hybrid environment. +Windows Sun Valley is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. ## How to get Windows Sun Valley Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10, beginning later in the 2021 calendar year. Windows Sun Valley will also be available on eligible new devices. -For administrators managing devices on behalf of their organization, Windows Sun Valley will be available through the same, familiar channels that you utilize today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Management, and Windows Autopilot. For more information, see [Plan for Windows Sun Valley](windows-sv-plan.md). +For administrators managing devices on behalf of their organization, Windows Sun Valley will be available through the same, familiar channels that you use today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Manager, and Windows Autopilot. For more information, see [Plan for Windows Sun Valley](windows-sv-plan.md). -For eligible PCs that are not managed by an organization, the Windows Sun Valley upgrade will be offered through Windows Update using Microsoft's intelligent rollout process to ensure a smooth upgrade experience. Windows Sun Valley will initially be offered to Windows 10 devices purchased after June 2021 that meet or exceed the minimum hardware requirements. +For devices that are not managed by an organization, the Windows Sun Valley upgrade will be offered to eligible Windows 10 devices through Windows Update using Microsoft's intelligent rollout process to ensure a smooth upgrade experience. For more information about device eligibility, see [Windows Sun Valley requirements](windows-sv-requirements.md). @@ -79,7 +77,7 @@ For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have a new feature update cadence. Windows Sun Valley feature updates will be released once per year. -When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the Windows release health hub. Monthly release notes will also be available from a consolidated Windows Sun Valley update history page at that time. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). +When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the [Windows release health](https://aka.ms/windowsreleasehealth) hub. Monthly release notes will also be available from a consolidated Windows Sun Valley update history page at that time. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). ## Next steps From b840943cb4adfc4afc0d6d867f1ef1d721f64cb1 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 23 Jun 2021 13:58:33 -0700 Subject: [PATCH 086/104] warning --- windows/sv/index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/windows/sv/index.md b/windows/sv/index.md index 6f48df996d..6918ab9666 100644 --- a/windows/sv/index.md +++ b/windows/sv/index.md @@ -1,8 +1,11 @@ --- title: SV +description: SV md.prod: w10 +manager: laurawi +ms.topic: article author: greg-lindsay ms.author: greglin --- -# \ No newline at end of file +# . \ No newline at end of file From 37adc674590200f58a76dfcd24a24eb5790ee2ad Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 23 Jun 2021 14:06:58 -0700 Subject: [PATCH 087/104] final --- windows/sv/index.md | 2 +- windows/whats-new/windows-sv-prepare.md | 4 ++-- windows/whats-new/windows-sv-requirements.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/sv/index.md b/windows/sv/index.md index 6918ab9666..7a31c42d39 100644 --- a/windows/sv/index.md +++ b/windows/sv/index.md @@ -1,7 +1,7 @@ --- title: SV description: SV -md.prod: w10 +ms.prod: w10 manager: laurawi ms.topic: article author: greg-lindsay diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-sv-prepare.md index dfca52badf..e6f48a1037 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-sv-prepare.md @@ -26,7 +26,7 @@ After you evaluate your hardware to see if it meets [requirements](windows-sv-re ## Infrastructure and tools -The tools that you use for core workloads during Windows 10 deployments can still be leveraged for Windows Sun Valley. A few nuanced differences are described below. +The tools that you use for core workloads during Windows 10 deployments can still be used for Windows Sun Valley. A few nuanced differences are described below. > [!IMPORTANT] > Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows Sun Valley, particularly if they provide security or data loss prevention capabilities. @@ -45,7 +45,7 @@ The tools that you use for core workloads during Windows 10 deployments can stil #### Cloud-based solutions -- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to leverage the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows Sun Valley). +- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to use the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows Sun Valley). - Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true regardless of which management tool you use to configure Windows Update for Business policies. - If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows Sun Valley. You can also continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-sv-requirements.md index 75dffa0e7b..eb25e65a86 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-sv-requirements.md @@ -75,7 +75,7 @@ Some features in Windows Sun Valley have requirements beyond those listed above. - **Wake on Voice**: requires Modern Standby power model and microphone. - **Wi-Fi 6E**: requires new WLAN IHV hardware and driver and a Wi-Fi 6E capable AP/router. - **Windows Hello**: requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or portable Microsoft compatible security key. For more information, see [IT tools to support Windows 10, version 21H1](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/it-tools-to-support-windows-10-version-21h1/ba-p/2365103). -- **Windows Projection**: requires a display adapter which supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct. +- **Windows Projection**: requires a display adapter that supports Windows Display Driver Model (WDDM) 2.0 and a Wi-Fi adapter that supports Wi-Fi Direct. - **Xbox app**: requires an Xbox Live account, which is not available in all regions. Please go to the Xbox Live Countries and Regions page for the most up-to-date information on availability. Some features in the Xbox app will require an active [Xbox Game Pass](https://www.xbox.com/xbox-game-pass) subscription. From d84deb14fe354539e2cfc5dd6135d30f1e1f08d5 Mon Sep 17 00:00:00 2001 From: denisebmsft <18405051+denisebmsft@users.noreply.github.comgit> Date: Wed, 23 Jun 2021 15:14:07 -0700 Subject: [PATCH 088/104] Update defender-csp.md --- windows/client-management/mdm/defender-csp.md | 73 ++++++++++++++++++- 1 file changed, 71 insertions(+), 2 deletions(-) diff --git a/windows/client-management/mdm/defender-csp.md b/windows/client-management/mdm/defender-csp.md index eeb53adf0b..3916a1550a 100644 --- a/windows/client-management/mdm/defender-csp.md +++ b/windows/client-management/mdm/defender-csp.md @@ -10,7 +10,7 @@ ms.prod: w10 ms.technology: windows author: dansimp ms.localizationpriority: medium -ms.date: 06/02/2021 +ms.date: 06/23/2021 --- # Defender CSP @@ -59,6 +59,9 @@ Defender --------TamperProtection (Added in Windows 10, version 1903) --------EnableFileHashComputation (Added in Windows 10, version 1903) --------SupportLogLocation (Added in the next major release of Windows 10) +--------PlatformUpdatesChannel (Added with the 4.18.2106.5 Defender platform release) +--------EngineUpdatesChannel (Added with the 4.18.2106.5 Defender platform release) +--------SignaturesUpdatesChannel (Added with the 4.18.2106.5 Defender platform release) ----Scan ----UpdateSignature ----OfflineScan (Added in Windows 10 version 1803) @@ -518,9 +521,75 @@ When enabled or disabled exists on the client and admin moves the setting to not More details: -- [Microsoft Defender AV diagnostic data](/microsoft-365/security/defender-endpoint/collect-diagnostic-data) +- [Microsoft Defender Antivirus diagnostic data](/microsoft-365/security/defender-endpoint/collect-diagnostic-data) - [Collect investigation package from devices](/microsoft-365/security/defender-endpoint/respond-machine-alerts#collect-investigation-package-from-devices) +**Configuration/PlatformUpdatesChannel** + +Enable this policy to specify when devices receive Microsoft Defender platform updates during the monthly gradual rollout. + +Beta Channel: Devices set to this channel will be the first to receive new updates. Select Beta Channel to participate in identifying and reporting issues to Microsoft. Devices in the Windows Insider Program are subscribed to this channel by default. For use in (manual) test environments only and a limited number of devices. + +Current Channel (Preview): Devices set to this channel will be offered updates earliest during the monthly gradual release cycle. Suggested for pre-production/validation environments. + +Current Channel (Staged): Devices will be offered updates after the monthly gradual release cycle. Suggested to apply to a small, representative part of your production population (~10%). + +Current Channel (Broad): Devices will be offered updates only after the gradual release cycle completes. Suggested to apply to a broad set of devices in your production population (~10-100%). + +If you disable or do not configure this policy, the device will stay up to date automatically during the gradual release cycle. Suitable for most devices. + +The data type is integer. + +Supported operations are Add, Delete, Get, Replace. + +Valid values are: +- 0: Not configured (Default) +- 1: Beta Channel - Prerelease +- 2: Current Channel (Preview) +- 3: Current Channel (Staged) +- 4: Current Channel (Broad) + +**Configuration/EngineUpdatesChannel** + +Enable this policy to specify when devices receive Microsoft Defender engine updates during the monthly gradual rollout. + +Beta Channel: Devices set to this channel will be the first to receive new updates. Select Beta Channel to participate in identifying and reporting issues to Microsoft. Devices in the Windows Insider Program are subscribed to this channel by default. For use in (manual) test environments only and a limited number of devices. + +Current Channel (Preview): Devices set to this channel will be offered updates earliest during the monthly gradual release cycle. Suggested for pre-production/validation environments. + +Current Channel (Staged): Devices will be offered updates after the monthly gradual release cycle. Suggested to apply to a small, representative part of your production population (~10%). + +Current Channel (Broad): Devices will be offered updates only after the gradual release cycle completes. Suggested to apply to a broad set of devices in your production population (~10-100%). + +If you disable or do not configure this policy, the device will stay up to date automatically during the gradual release cycle. Suitable for most devices. + +The data type is integer. + +Supported operations are Add, Delete, Get, Replace. + +Valid values are: +- 0 - Not configured (Default) +- 1 - Beta Channel - Prerelease +- 2 - Current Channel (Preview) +- 3 - Current Channel (Staged) +- 4 - Current Channel (Broad) + +**Configuration/DefinitionUpdatesChannel** + +Enable this policy to specify when devices receive daily Microsoft Defender definition updates during the daily gradual rollout. + +Current Channel (Broad): Devices will be offered updates only after the gradual release cycle completes. Suggested to apply to a broad set of devices in your production population (~10-100%). + +If you disable or do not configure this policy, the device will stay up to date automatically during the daily release cycle. Suitable for most devices. + +The data type is integer. +Supported operations are Add, Delete, Get, Replace. + +Valid Values are: +- 0: Not configured (Default) +- 3: Current Channel (Staged) +- 4: Current Channel (Broad) + **Scan** Node that can be used to start a Windows Defender scan on a device. From 9f21e81e112a2c816c10ec7a8f0dab73b3723e36 Mon Sep 17 00:00:00 2001 From: denisebmsft <18405051+denisebmsft@users.noreply.github.comgit> Date: Wed, 23 Jun 2021 15:21:45 -0700 Subject: [PATCH 089/104] Update defender-csp.md --- windows/client-management/mdm/defender-csp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/defender-csp.md b/windows/client-management/mdm/defender-csp.md index 3916a1550a..97561119e4 100644 --- a/windows/client-management/mdm/defender-csp.md +++ b/windows/client-management/mdm/defender-csp.md @@ -574,7 +574,7 @@ Valid values are: - 3 - Current Channel (Staged) - 4 - Current Channel (Broad) -**Configuration/DefinitionUpdatesChannel** +**Configuration/SignaturesUpdatesChannel** Enable this policy to specify when devices receive daily Microsoft Defender definition updates during the daily gradual rollout. From 051dd31f47d60f5b74e9cceaef1ca96a84b432b8 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 01:00:11 -0700 Subject: [PATCH 090/104] 11 --- windows/application-management/index.yml | 2 +- windows/deployment/TOC.yml | 12 +- windows/deployment/deploy-whats-new.md | 2 +- windows/deployment/index.yml | 4 +- windows/hub/TOC.yml | 4 +- windows/hub/index.yml | 20 +-- windows/sv/docfx.json | 4 +- windows/whats-new/TOC.yml | 18 +-- windows/whats-new/index.yml | 24 ++-- windows/whats-new/windows-11-plan.md | 122 ++++++++++++++++++ ...ws-sv-prepare.md => windows-11-prepare.md} | 52 ++++---- ...irements.md => windows-11-requirements.md} | 34 ++--- windows/whats-new/windows-11.md | 86 ++++++++++++ windows/whats-new/windows-sv-plan.md | 122 ------------------ windows/whats-new/windows-sv.md | 86 ------------ 15 files changed, 296 insertions(+), 296 deletions(-) create mode 100644 windows/whats-new/windows-11-plan.md rename windows/whats-new/{windows-sv-prepare.md => windows-11-prepare.md} (60%) rename windows/whats-new/{windows-sv-requirements.md => windows-11-requirements.md} (76%) create mode 100644 windows/whats-new/windows-11.md delete mode 100644 windows/whats-new/windows-sv-plan.md delete mode 100644 windows/whats-new/windows-sv.md diff --git a/windows/application-management/index.yml b/windows/application-management/index.yml index dc786fd289..d3a95df0d0 100644 --- a/windows/application-management/index.yml +++ b/windows/application-management/index.yml @@ -5,7 +5,7 @@ summary: Learn about managing applications in Windows client, including how to r metadata: title: Windows application management # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Learn about managing applications in Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Learn about managing applications in Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index e3fcfca9e0..cafdf97782 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -5,8 +5,8 @@ items: - name: What's new href: deploy-whats-new.md - - name: Windows Sun Valley deployment overview - href: /windows/whats-new/windows-sv-overview.md + - name: Windows 11 deployment overview + href: /windows/whats-new/windows-11-overview.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? @@ -35,8 +35,8 @@ - name: Plan items: - - name: Windows Sun Valley deployment planning - href: /windows/whats-new/windows-sv-plan.md + - name: Windows 11 deployment planning + href: /windows/whats-new/windows-11-plan.md - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria @@ -71,8 +71,8 @@ - name: Prepare items: - - name: Prepare to deploy Windows Sun Valley - href: /windows/whats-new/windows-sv-prepare.md + - name: Prepare to deploy Windows 11 + href: /windows/whats-new/windows-11-prepare.md - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md - name: Evaluate and update infrastructure diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index 583e4392a1..fa8ca9e964 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -26,7 +26,7 @@ ms.custom: seo-marvel-apr2020 This topic provides an overview of new solutions and online content related to deploying Windows client in your organization. - For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index). -- For an overview of Windows Sun Valley, see [What's new in Windows Sun Valley](/windows/whats-new/windows-sv). +- For an overview of Windows 11, see [What's new in Windows 11](/windows/whats-new/windows-11). ## Latest news diff --git a/windows/deployment/index.yml b/windows/deployment/index.yml index eda7ab8577..d938c4922b 100644 --- a/windows/deployment/index.yml +++ b/windows/deployment/index.yml @@ -66,8 +66,8 @@ landingContent: links: - text: What's new in Windows deployment url: deploy-whats-new.md - - text: Windows Sun Valley overview - url: /windows/whats-new/windows-sv.md + - text: Windows 11 overview + url: /windows/whats-new/windows-11.md - text: Windows client deployment scenarios url: windows-10-deployment-scenarios.md - text: Basics of Windows updates, channels, and tools diff --git a/windows/hub/TOC.yml b/windows/hub/TOC.yml index 1752028577..a199923b84 100644 --- a/windows/hub/TOC.yml +++ b/windows/hub/TOC.yml @@ -6,8 +6,8 @@ items: - name: What's new in Windows href: /windows/whats-new - - name: Windows Sun Valley - href: /windows/whats-new/windows-sv + - name: Windows 11 + href: /windows/whats-new/windows-11 - name: Release information href: /windows/release-health - name: Deployment diff --git a/windows/hub/index.yml b/windows/hub/index.yml index 846ee4e900..f61c3a9861 100644 --- a/windows/hub/index.yml +++ b/windows/hub/index.yml @@ -1,11 +1,11 @@ ### YamlMime:Landing title: Windows client resources and documentation for IT Pros # < 60 chars -summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows Sun Valley. # < 160 chars +summary: Plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # < 160 chars metadata: title: Windows client documentation for IT Pros # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Evaluate, plan, deploy, secure, and manage devices running Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Evaluate, plan, deploy, secure, and manage devices running Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice @@ -26,14 +26,14 @@ landingContent: linkLists: - linkListType: overview links: - - text: Windows Sun Valley overview - url: /windows/whats-new/windows-sv - - text: Windows Sun Valley requirements - url: /windows/whats-new/windows-sv-requirements - - text: Plan for Windows Sun Valley - url: /windows/whats-new/windows-sv-plan - - text: Prepare for Windows Sun Valley - url: /windows/whats-new/windows-sv-prepare + - text: Windows 11 overview + url: /windows/whats-new/windows-11 + - text: Windows 11 requirements + url: /windows/whats-new/windows-11-requirements + - text: Plan for Windows 11 + url: /windows/whats-new/windows-11-plan + - text: Prepare for Windows 11 + url: /windows/whats-new/windows-11-prepare - text: What's new in Windows 10, version 21H1 url: /windows/whats-new/whats-new-windows-10-version-21H1 - text: Windows release information diff --git a/windows/sv/docfx.json b/windows/sv/docfx.json index fe874614d1..e7955464fe 100644 --- a/windows/sv/docfx.json +++ b/windows/sv/docfx.json @@ -39,13 +39,13 @@ "overwrite": [], "externalReference": [], "globalMetadata": { - "breadcrumb_path": "/windows/windows-sv/breadcrumb/toc.json", + "breadcrumb_path": "/windows/windows-11/breadcrumb/toc.json", "extendBreadcrumb": true, "feedback_system": "None" }, "fileMetadata": {}, "template": [], - "dest": "windows-sv", + "dest": "windows-11", "markdownEngineName": "markdig" } } \ No newline at end of file diff --git a/windows/whats-new/TOC.yml b/windows/whats-new/TOC.yml index 71e18303ee..a9ae9e12ba 100644 --- a/windows/whats-new/TOC.yml +++ b/windows/whats-new/TOC.yml @@ -1,16 +1,16 @@ - name: What's new in Windows href: index.yml -- name: Windows Sun Valley +- name: Windows 11 expanded: true items: - - name: Windows Sun Valley overview - href: windows-sv.md - - name: Windows Sun Valley requirements - href: windows-sv-requirements.md - - name: Plan for Windows Sun Valley - href: windows-sv-plan.md - - name: Prepare for Windows Sun Valley - href: windows-sv-prepare.md + - name: Windows 11 overview + href: windows-11.md + - name: Windows 11 requirements + href: windows-11-requirements.md + - name: Plan for Windows 11 + href: windows-11-plan.md + - name: Prepare for Windows 11 + href: windows-11-prepare.md - name: Windows 10 expanded: true items: diff --git a/windows/whats-new/index.yml b/windows/whats-new/index.yml index fbea14e982..375f946870 100644 --- a/windows/whats-new/index.yml +++ b/windows/whats-new/index.yml @@ -1,11 +1,11 @@ ### YamlMime:Landing title: What's new in Windows # < 60 chars -summary: Find out about new features and capabilities in the latest release of Windows 10 and Windows Sun Valley. # < 160 chars +summary: Find out about new features and capabilities in the latest release of Windows 10 and Windows 11. # < 160 chars metadata: title: What's new in Windows # Required; page title displayed in search results. Include the brand. < 60 chars. - description: Find out about new features and capabilities in the latest release of Windows 10 and Windows Sun Valley. # Required; article description that is displayed in search results. < 160 chars. + description: Find out about new features and capabilities in the latest release of Windows 10 and Windows 11. # Required; article description that is displayed in search results. < 160 chars. services: windows-10 ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM. ms.subservice: subservice @@ -13,7 +13,7 @@ metadata: ms.collection: windows-10 author: greg-lindsay #Required; your GitHub user alias, with correct capitalization. ms.author: greglin #Required; microsoft alias of author; optional team alias. - ms.date: 06/02/2021 #Required; mm/dd/yyyy format. + ms.date: 06/24/2021 #Required; mm/dd/yyyy format. localization_priority: medium # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new @@ -23,18 +23,18 @@ landingContent: # Start card title with a verb # Card (optional) - - title: Windows Sun Valley + - title: Windows 11 linkLists: - linkListType: overview links: - - text: Windows Sun Valley Overview - url: windows-sv.md - - text: Windows Sun Valley requirements - url: windows-sv-requirements.md - - text: Plan for Windows Sun Valley - url: windows-sv-plan.md - - text: Prepare for Windows Sun Valley - url: windows-sv-prepare.md + - text: Windows 11 overview + url: windows-11.md + - text: Windows 11 requirements + url: windows-11-requirements.md + - text: Plan for Windows 11 + url: windows-11-plan.md + - text: Prepare for Windows 11 + url: windows-11-prepare.md - title: Windows 10 linkLists: diff --git a/windows/whats-new/windows-11-plan.md b/windows/whats-new/windows-11-plan.md new file mode 100644 index 0000000000..ad68e1ebfa --- /dev/null +++ b/windows/whats-new/windows-11-plan.md @@ -0,0 +1,122 @@ +--- +title: Plan for Windows 11 +description: Windows 11 deployment planning, IT Pro content. +keywords: ["get started", "windows 11", "plan"] +ms.prod: w11 +ms.mktglfcycl: deploy +ms.sitesec: library +author: greg-lindsay +ms.author: greglin +ms.date: 06/24/2021 +ms.reviewer: +manager: laurawi +ms.localizationpriority: high +ms.topic: article +--- + +# Plan for Windows 11 + +**Applies to** + +- Windows 11 + +## Deployment planning + +This article provides guidance to help you plan for Windows 11 in your organization. + +Since Windows 11 is built on the same foundation as Windows 10, you can use the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy that you use today for Windows 10. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows 11. + +At a high level, this strategy should include the following steps: +- [Create a deployment plan](/windows/deployment/update/create-deployment-plan) +- [Define readiness criteria](/windows/deployment/update/plan-define-readiness) +- [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) +- [Determine application readiness](/windows/deployment/update/plan-determine-app-readiness) +- [Define your servicing strategy](/windows/deployment/update/plan-define-strategy) + +If you are looking for ways to optimize your approach to deploying Windows 11, or if deploying a new version of an operating system is not a familiar process for you, some items to consider are provided below. + +## Determine eligibility + +As a first step, you will need to know which of your current devices meet the Windows 11 hardware requirements. Most devices purchased in the last 18-24 months will be compatible with Windows 11. Verify that your device meets or exceeds [Windows 11 requirements](windows-11-requirements.md) to ensure it is compatible. + +Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows 11 hardware requirements. When Windows 11 reaches general availability, end-users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows 11. end-users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  + +Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows 11 is generally available. Microsoft is also working with software publishing partners to facilitate adding Windows 11 device support into their solutions. + +## Windows 11 availability + +The availability of Windows 11 will vary according to a device's hardware and whether the device receives updates directly, or from a management solution that is maintained by an IT administrator. + +##### Managed devices + +Managed devices are devices that are under organization control. Managed devices include those managed by Microsoft Intune, Microsoft Endpoint Configuration Manager, or other endpoint management solutions. + +If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows 11 using your existing deployment and management tools at no cost when the upgrade reaches general availability. Organizations that use Windows Update for Business will have added benefits, such as: + +- Ensuring that devices that don't meet the minimum hardware requirements are not automatically offered the Windows 11 upgrade. +- Additional insight into safeguard holds. While safeguard holds will function for Windows 11 devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows 11. + +> [!NOTE] +> If you use Windows Update for Business to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows 11. Deferrals are great for quality updates or to move to newer version of the same product (from example, from Windows 10, version 20H2 to 21H1), but they cannot migrate a device between products (from Windows 10 to Windows 11).
+> Additionally, Windows 11 has a new End User License Agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new End User License Agreement on behalf of the end-users within your organization. + +##### Unmanaged devices + +Unmanaged devices are devices that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. + +Windows 11 will be offered to eligible Windows 10 devices beginning later in the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows 11 once available** on products that are available for purchase. + +The Windows 11 upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Windows Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. + +Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This process improves the update experience and ensures that devices first nominated for updates are the devices likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. + +## Windows 11 readiness considerations + +The recommended method to determine if your infrastructure, deployment processes, and management tools are ready for Windows 11 is to join the [Windows Insider Program for Business](https://insider.windows.com/for-business). As a participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), you can validate that your devices and applications work as expected, and explore new features. + +As you plan your endpoint management strategy for Windows 11, consider moving to cloud-based mobile device management (MDM), such as [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). If a cloud-only approach isn't right for your organization just yet, you can still modernize and streamline essential pieces of your endpoint management strategy as follows: +- Create a [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview) (CMG) to manage Configuration Manager clients over the internet. +- Attach your existing Configuration Management estate to the cloud with [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions) so you can manage all devices from within the Microsoft Endpoint Manager admin center. +- Use [co-management](/mem/configmgr/comanage/overview) to concurrently manage devices using both Configuration Manager and Microsoft Intune. This allows you to take advantage of cloud-powered capabilities like [Conditional Access](/azure/active-directory/conditional-access/overview). + +For more information on the benefits of these approaches, see [Cloud Attach Your Future: The Big 3](https://techcommunity.microsoft.com/t5/configuration-manager-blog/cloud-attach-your-future-part-ii-quot-the-big-3-quot/ba-p/1750664). + +The introduction of Windows 11 is also a good time to review your hardware refresh plans and prioritize eligible devices to ensure an optimal experience for your users. + +## Servicing and support + +Along with end-user experience and security improvements, Windows 11 introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. + +**Quality updates**: Windows 11 and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. + +**Feature updates**: Microsoft will provide a single Windows 11 feature update annually, targeted for release in the second half of each calendar year. + +**Lifecycle**: +- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows 11 will receive 24 months of support from the general availability date. +- Enterprise and Education editions of Windows 11 will be supported for 36 months from the general availability date. + +When Windows 11 reaches general availability, a consolidated Windows 11 update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows 11 servicing announcements, known issues, and safeguard holds. + +It is important that organizations have adequate time to plan for Windows 11. Microsoft also recognizes that many organizations will have a mix of Windows 11 and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about the Windows 10 Semi-Annual Channel and Long-term Servicing Channel (LTSC) releases. + +## Application compatibility + +Microsoft's compatibility promise for Windows 10 is maintained for Windows 11. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for enterprise organizations, including line of business (LOB) apps. Microsoft remains committed to ensuring that the apps you rely upon continue to work as expected when you upgrade. Windows 11 is subject to the same app compatibility validation requirements that are in place for Windows 10 today, for both feature and quality updates. + +#### App Assure and Test Base for Microsoft 365 + +If you run into compatibility issues or want to ensure that your organization's applications are compatible from day one, App Assure and Test Base for Microsoft 365 can help. + +**App Assure**: With enrollment in the [App Assure](/windows/compatibility/app-assure) service, any app compatibility issues that you find with Windows 11 can be resolved. Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. + +**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. + +You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows 11. + +## Next steps + +[Prepare for Windows 11](windows-11-prepare.md) + +## Also see + +[Plan to deploy updates for Windows 10 and Microsoft 365 Apps](/learn/modules/windows-plan/) diff --git a/windows/whats-new/windows-sv-prepare.md b/windows/whats-new/windows-11-prepare.md similarity index 60% rename from windows/whats-new/windows-sv-prepare.md rename to windows/whats-new/windows-11-prepare.md index e6f48a1037..3ef63328a5 100644 --- a/windows/whats-new/windows-sv-prepare.md +++ b/windows/whats-new/windows-11-prepare.md @@ -1,7 +1,7 @@ --- -title: Prepare for Windows Sun Valley -description: Prepare your infrastructure and tools to deploy Windows Sun Valley, IT Pro content. -keywords: ["get started", "windows sun valley"] +title: Prepare for Windows 11 +description: Prepare your infrastructure and tools to deploy Windows 11, IT Pro content. +keywords: ["get started", "windows 11"] ms.prod: w11 ms.mktglfcycl: deploy ms.sitesec: library @@ -14,40 +14,40 @@ ms.localizationpriority: high ms.topic: article --- -# Prepare for Windows Sun Valley +# Prepare for Windows 11 **Applies to** -- Windows Sun Valley +- Windows 11 -Windows 10 and Windows Sun Valley are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. Using a single management infrastructure that supports common applications across both Windows 10 and Windows Sun Valley helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows Sun Valley deployments in the same way that you do with Windows 10. +Windows 10 and Windows 11 are designed to coexist, so that you can use the same familiar tools and process to manage both operating systems. Using a single management infrastructure that supports common applications across both Windows 10 and Windows 11 helps to simplify the migration process. You can analyze endpoints, determine application compatibility, and manage Windows 11 deployments in the same way that you do with Windows 10. -After you evaluate your hardware to see if it meets [requirements](windows-sv-requirements.md) for Windows Sun Valley, it's a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. This article provides some helpful guidance to accomplish these tasks. +After you evaluate your hardware to see if it meets [requirements](windows-11-requirements.md) for Windows 11, it's a good time to review your deployment infrastructure, tools, and overall endpoint and update management processes and look for opportunities to simplify and optimize. This article provides some helpful guidance to accomplish these tasks. ## Infrastructure and tools -The tools that you use for core workloads during Windows 10 deployments can still be used for Windows Sun Valley. A few nuanced differences are described below. +The tools that you use for core workloads during Windows 10 deployments can still be used for Windows 11. A few nuanced differences are described below. > [!IMPORTANT] - > Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows Sun Valley, particularly if they provide security or data loss prevention capabilities. + > Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows 11, particularly if they provide security or data loss prevention capabilities. #### On-premise solutions -- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows Sun Valley** product category. After you sync the product category, you will see Windows Sun Valley offered as an option. If you would like to validate Windows Sun Valley prior to release, you can sync the Windows Insider Pre-release category as well. +- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows 11** product category. After you sync the product category, you will see Windows 11 offered as an option. If you would like to validate Windows 11 prior to release, you can sync the Windows Insider Pre-release category as well. > [!NOTE] - > During deployment, you will be prompted to agree to the End User License Agreement on behalf of your users. Additionally, you will not see an x86 option because Windows Sun Valley is not supported on 32-bit architecture. + > During deployment, you will be prompted to agree to the End User License Agreement on behalf of your users. Additionally, you will not see an x86 option because Windows 11 is not supported on 32-bit architecture. -- If you use Microsoft Endpoint Configuration Manager, you can sync the new **Windows Sun Valley** product category and begin upgrading eligible devices. If you would like to validate Windows Sun Valley prior to release, you can sync the **Windows Insider Pre-release** category as well. +- If you use Microsoft Endpoint Configuration Manager, you can sync the new **Windows 11** product category and begin upgrading eligible devices. If you would like to validate Windows 11 prior to release, you can sync the **Windows Insider Pre-release** category as well. > [!NOTE] > Configuration Manager will prompt you to accept the End User License Agreement on behalf of the users in your organization. #### Cloud-based solutions -- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to use the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows Sun Valley. Feature Update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows Sun Valley). -- Quality update deferrals will continue to work the same across both Windows 10 and Windows Sun Valley. This is true regardless of which management tool you use to configure Windows Update for Business policies. -- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows Sun Valley. You can also continue using the same update experience controls to manage Windows 10 and Windows Sun Valley. +- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to use the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows 11. Feature Update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows 11). +- Quality update deferrals will continue to work the same across both Windows 10 and Windows 11. This is true regardless of which management tool you use to configure Windows Update for Business policies. +- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows 11. You can also continue using the same update experience controls to manage Windows 10 and Windows 11. ## Cloud-based management @@ -55,19 +55,19 @@ If you aren’t already taking advantage of cloud-based management capabilities, The following are some common use cases and the corresponding Microsoft Endpoint Manager capabilities that support them: -- **Provision and pre-configure new Windows Sun Valley devices**: [Windows Autopilot](/mem/autopilot/windows-autopilot) enables you to deploy new Windows Sun Valley devices in a “business-ready” state that includes your desired applications, settings, and policies. It can also be used to change the edition of Windows. For example, you can upgrade from Pro to Enterprise edition and gain the use of advanced features. -- **Configure rules and control settings for users, apps, and devices**: When you enroll devices in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), administrators have full control over apps, settings, features, and security for both Windows Sun Valley and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. -- **Streamline device management for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows Sun Valley by using Microsoft Endpoint Manager. +- **Provision and pre-configure new Windows 11 devices**: [Windows Autopilot](/mem/autopilot/windows-autopilot) enables you to deploy new Windows 11 devices in a “business-ready” state that includes your desired applications, settings, and policies. It can also be used to change the edition of Windows. For example, you can upgrade from Pro to Enterprise edition and gain the use of advanced features. +- **Configure rules and control settings for users, apps, and devices**: When you enroll devices in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), administrators have full control over apps, settings, features, and security for both Windows 11 and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. +- **Streamline device management for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows 11 by using Microsoft Endpoint Manager. If you are exclusively using an on-premise device management solution (for example, Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune. These solutions can make it easier to keep devices secure and up-to-date. ## Review servicing approach and policies -Every organization will transition to Windows Sun Valley at its own pace. Microsoft is committed to supporting you through your migration to Windows Sun Valley, whether you are a fast adopter or will make the transition over the coming months or years. +Every organization will transition to Windows 11 at its own pace. Microsoft is committed to supporting you through your migration to Windows 11, whether you are a fast adopter or will make the transition over the coming months or years. When you think of operating system updates as an ongoing process, you will automatically improve your ability to deploy updates. This approach enables you to stay current with less effort, and less impact on productivity. To begin, think about how you roll out Windows feature updates today: which devices, and at what pace. -Next, craft a deployment plan for Windows Sun Valley that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: +Next, craft a deployment plan for Windows 11 that includes deployment groups, rings, users, or devices. There are no absolute rules for exactly how many rings to have for your deployments, but a common structure is: - Preview (first or canary): Planning and development - Limited (fast or early adopters): Pilot and validation - Broad (users or critical): Wide deployment @@ -80,7 +80,7 @@ Review deployment-related policies, taking into consideration your organization' #### Validate apps and infrastructure -To validate that your apps, infrastructure, and deployment processes are ready for Windows Sun Valley, join the [Windows Insider Program for Business](https://insider.windows.com/for-business-getting-started), and opt in to the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). +To validate that your apps, infrastructure, and deployment processes are ready for Windows 11, join the [Windows Insider Program for Business](https://insider.windows.com/for-business-getting-started), and opt in to the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel). If you use Windows Server Update Services, you can deploy directly from the Windows Insider Pre-release category using one of the following processes: @@ -88,11 +88,11 @@ If you use Windows Server Update Services, you can deploy directly from the Wind - Leverage Azure Virtual Desktop and Azure Marketplace images. - Download and deploy ISOs from Microsoft’s Windows Insider Program ISO Download page. -Regardless of the method you choose, you have the benefit of free Microsoft support when validating pre-release builds. Free support is available to any commercial customer deploying Windows 10 or Windows Sun Valley Preview Builds, once they become available through the Windows Insider Program. +Regardless of the method you choose, you have the benefit of free Microsoft support when validating pre-release builds. Free support is available to any commercial customer deploying Windows 10 or Windows 11 Preview Builds, once they become available through the Windows Insider Program. #### Analytics and assessment tools -If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year. This tool enables you to quickly identify which of your managed devices are eligible for the Windows Sun Valley upgrade. +If you use Microsoft Endpoint Manager and have onboarded devices to Endpoint analytics, you will have access to a hardware readiness assessment later this year. This tool enables you to quickly identify which of your managed devices are eligible for the Windows 11 upgrade. ## Prepare a pilot deployment @@ -110,16 +110,16 @@ At a high level, the tasks involved are: ## end-user readiness -Do not overlook the importance of end-user readiness to deliver an effective, enterprise-wide deployment of Windows Sun Valley. Windows Sun Valley has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows Sun Valley: +Do not overlook the importance of end-user readiness to deliver an effective, enterprise-wide deployment of Windows 11. Windows 11 has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows 11: - Create a communications schedule to ensure that you provide the right message at the right time to the right groups of users, based on when they will see the changes. - Draft concise emails that inform users of what changes they can expect to see. Offer tips on how to use or customize their experience. Include information about support and help desk options. - Update help desk manuals with screenshots of the new user interface, the out-of-box experience for new devices, and the upgrade experience for existing devices. ## Learn more -See the [Stay current with Windows 10 and Microsoft 365 Apps](/learn/paths/m365-stay-current/) learning path on Microsoft Learn. The learning path was created for Windows 10, but the basic principles and tasks outlined for the plan, prepare, and deploy phases also apply to your deployment of Windows Sun Valley. +See the [Stay current with Windows 10 and Microsoft 365 Apps](/learn/paths/m365-stay-current/) learning path on Microsoft Learn. The learning path was created for Windows 10, but the basic principles and tasks outlined for the plan, prepare, and deploy phases also apply to your deployment of Windows 11. ## See also -[Plan for Windows Sun Valley](windows-sv-plan.md)
+[Plan for Windows 11](windows-11-plan.md)
[Windows help & learning](https://support.microsoft.com/windows) diff --git a/windows/whats-new/windows-sv-requirements.md b/windows/whats-new/windows-11-requirements.md similarity index 76% rename from windows/whats-new/windows-sv-requirements.md rename to windows/whats-new/windows-11-requirements.md index eb25e65a86..2fbeeb8490 100644 --- a/windows/whats-new/windows-sv-requirements.md +++ b/windows/whats-new/windows-11-requirements.md @@ -1,6 +1,6 @@ --- -title: Windows Sun Valley requirements -description: Hardware requirements to deploy Windows Sun Valley +title: Windows 11 requirements +description: Hardware requirements to deploy Windows 11 ms.reviewer: manager: laurawi ms.audience: itpro @@ -15,51 +15,51 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# Windows Sun Valley requirements +# Windows 11 requirements **Applies to** -- Windows Sun Valley +- Windows 11 -This article lists the system requirements for Windows Sun Valley. Windows Sun Valley is also supported on a virtual machine (VM). +This article lists the system requirements for Windows 11. Windows 11 is also supported on a virtual machine (VM). ## Hardware requirements -To install or upgrade to Windows Sun Valley, devices must meet the following minimum hardware requirements: +To install or upgrade to Windows 11, devices must meet the following minimum hardware requirements: - Processor: 1 gigahertz (GHz) or faster with two or more cores on a [compatible 64-bit processor](https://aka.ms/CPUlist) or system on a chip (SoC). - RAM: 4 gigabytes (GB) or greater. -- Storage: 64 GB\* or greater available storage is required to install Windows Sun Valley. +- Storage: 64 GB\* or greater available storage is required to install Windows 11. - Additional storage space might be required to download updates and enable specific features. - Graphics card: Compatible with DirectX 12 or later, with a WDDM 2.0 driver. - System firmware: UEFI, Secure Boot capable. - TPM: [Trusted Platform Module](/windows/security/information-protection/tpm/trusted-platform-module-overview) (TPM) version 2.0. - Display: High definition (720p) display, 9" or greater monitor, 8 bits per color channel. - Internet connection: Internet connectivity is necessary to perform updates, and to download and use some features. - - Windows Sun Valley Home edition requires an Internet connection and a Microsoft Account to complete device setup on first use. + - Windows 11 Home edition requires an Internet connection and a Microsoft Account to complete device setup on first use. -\* There might be additional requirements over time for updates, and to enable specific features within the operating system. For more information, see [Keeping Windows Sun Valley up-to-date](https://www.microsoft.com/windows/windows-10-specifications#primaryR5). +\* There might be additional requirements over time for updates, and to enable specific features within the operating system. For more information, see [Keeping Windows 11 up-to-date](https://www.microsoft.com/windows/windows-10-specifications#primaryR5). -For information about tools to evaluate readiness, see [Determine eligibility](windows-sv-plan.md#determine-eligibility). +For information about tools to evaluate readiness, see [Determine eligibility](windows-11-plan.md#determine-eligibility). ## Operating system requirements -For the best Windows Sun Valley upgrade experience, eligible devices should be running Windows 10, version 20H1 or later. +For the best Windows 11 upgrade experience, eligible devices should be running Windows 10, version 20H1 or later. > [!NOTE] -> S mode is not supported on Windows Sun Valley. +> S mode is not supported on Windows 11. > If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading.
 
> Switching a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you cannot switch back to S mode later. ## Feature-specific requirements -Some features in Windows Sun Valley have requirements beyond those listed above. See the following list of features and associated requirements. +Some features in Windows 11 have requirements beyond those listed above. See the following list of features and associated requirements. - **5G support**: requires 5G capable modem. - **Auto HDR**: requires an HDR monitor. - **BitLocker to Go**: requires a USB flash drive. This feature is available in Windows Pro and above editions. - **Client Hyper-V**: requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. -- **Cortana**: requires a microphone and speaker and is currently available on Windows Sun Valley for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. +- **Cortana**: requires a microphone and speaker and is currently available on Windows 11 for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. - **DirectStorage**: requires 1 TB or greater NVMe SSD to store and run games that use the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU. - **DirectX 12 Ultimate**: available with supported games and graphics chips. - **Presence**: requires sensor that can detect human distance from device or intent to interact with device. @@ -81,10 +81,10 @@ Some features in Windows Sun Valley have requirements beyond those listed above. ## Next steps -[Plan for Windows Sun Valley](windows-sv-plan.md)
-[Prepare for Windows Sun Valley](windows-sv-prepare.md) +[Plan for Windows 11](windows-11-plan.md)
+[Prepare for Windows 11](windows-11-prepare.md) ## See also -[Windows Sun Valley overview](windows-sv.md) +[Windows 11 overview](windows-11.md) diff --git a/windows/whats-new/windows-11.md b/windows/whats-new/windows-11.md new file mode 100644 index 0000000000..260967a467 --- /dev/null +++ b/windows/whats-new/windows-11.md @@ -0,0 +1,86 @@ +--- +title: Windows 11 overview +description: Overview of Windows 11 +ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C +ms.reviewer: +manager: laurawi +ms.audience: itpro +author: greg-lindsay +ms.author: greglin +ms.prod: w10 +ms.mktglfcycl: deploy +ms.sitesec: library +ms.localizationpriority: medium +audience: itpro +ms.topic: article +ms.custom: seo-marvel-apr2020 +--- + +# Windows 11 overview + +**Applies to** + +- Windows 11 + +This article provides an introduction to Windows 11, and answers some frequently asked questions. + +Also see the following articles to learn more about Windows 11: + +- [Windows 11 requirements](windows-11-requirements.md): Requirements to deploy Windows 11. +- [Plan for Windows 11](windows-11-plan.md): Information to help you plan for Windows 11 in your organization. +- [Prepare for Windows 11](windows-11-prepare.md): Procedures to ensure readiness to deploy Windows 11. + +## Introduction + +Windows 11 is the next evolution of Windows; it is the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end-user productivity in a fresh experience that is flexible and fluid. Windows 11 is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. + +Windows 11 is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows 11 also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows 11. + +## How to get Windows 11 + +Windows 11 will be delivered as an upgrade to eligible devices running Windows 10, beginning later in the 2021 calendar year. Windows 11 will also be available on eligible new devices. + +For administrators managing devices on behalf of their organization, Windows 11 will be available through the same, familiar channels that you use today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Manager, and Windows Autopilot. For more information, see [Plan for Windows 11](windows-11-plan.md). + +For devices that are not managed by an organization, the Windows 11 upgrade will be offered to eligible Windows 10 devices through Windows Update using Microsoft's intelligent rollout process to ensure a smooth upgrade experience. + +For more information about device eligibility, see [Windows 11 requirements](windows-11-requirements.md). + +If you are interested in testing Windows 11 before general availability, you can join the [Windows Insider Program](https://insider.windows.com) or [Windows Insider Program for Business](https://insider.windows.com/for-business). You can also preview Windows 11 by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). + +## Before you begin + +The following sections provide a quick summary of licensing, compatibility, management, and servicing considerations to help you get started with Windows 11. + +#### Licensing + +There are no unique licensing requirements for Windows 11 beyond what is required for Windows 10 devices. + +Microsoft 365 licenses that include Windows 10 licenses will permit you to run Windows 11 on supported devices. If you have a volume license, it will equally cover Windows 11 and Windows 10 devices before and after upgrade. + +#### Compatibility + +Most accessories and associated drivers that work with Windows 10 are expected to work with Windows 11. Check with your accessory manufacturer for specific details. + +Windows 11 preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows 11. For more information, see [Application compatibility](windows-11-plan.md#application-compatibility). + +#### Familiar processes + +Windows 11 is built on the same foundation as Windows 10. Typically, you can use the same tools and solutions you use today to deploy, manage, and secure Windows 11. Your current management tools and processes will also work to manage monthly quality updates for both Windows 10 and Windows 11. + +> [!IMPORTANT] +> Check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows 11, particularly those providing security or data loss prevention capabilities. + +For more information, see [Prepare for Windows 11](windows-11-prepare.md). + +#### Servicing Windows 11 + +Like Windows 10, Windows 11 will receive monthly quality updates. However, it will have a new feature update cadence. Windows 11 feature updates will be released once per year. + +When Windows 11 reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the [Windows release health](https://aka.ms/windowsreleasehealth) hub. Monthly release notes will also be available from a consolidated Windows 11 update history page at that time. For more information, see [Servicing and support](windows-11-plan.md#servicing-and-support). + +## Next steps + +[Windows 11 requirements](windows-11-requirements.md)
+[Plan for Windows 11](windows-11-plan.md)
+[Prepare for Windows 11](windows-11-prepare.md) \ No newline at end of file diff --git a/windows/whats-new/windows-sv-plan.md b/windows/whats-new/windows-sv-plan.md deleted file mode 100644 index 11aa8a3ddc..0000000000 --- a/windows/whats-new/windows-sv-plan.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -title: Plan for Windows Sun Valley -description: Windows Sun Valley deployment planning, IT Pro content. -keywords: ["get started", "windows sun valley", "plan"] -ms.prod: w11 -ms.mktglfcycl: deploy -ms.sitesec: library -author: greg-lindsay -ms.author: greglin -ms.date: 06/24/2021 -ms.reviewer: -manager: laurawi -ms.localizationpriority: high -ms.topic: article ---- - -# Plan for Windows Sun Valley - -**Applies to** - -- Windows Sun Valley - -## Deployment planning - -This article provides guidance to help you plan for Windows Sun Valley in your organization. - -Since Windows Sun Valley is built on the same foundation as Windows 10, you can use the same deployment capabilities, scenarios, and tools—as well as the same basic deployment strategy that you use today for Windows 10. You will need to review and update your servicing strategy to adjust for changes in [Servicing and support](#servicing-and-support) for Windows Sun Valley. - -At a high level, this strategy should include the following steps: -- [Create a deployment plan](/windows/deployment/update/create-deployment-plan) -- [Define readiness criteria](/windows/deployment/update/plan-define-readiness) -- [Evaluate infrastructure and tools](/windows/deployment/update/eval-infra-tools) -- [Determine application readiness](/windows/deployment/update/plan-determine-app-readiness) -- [Define your servicing strategy](/windows/deployment/update/plan-define-strategy) - -If you are looking for ways to optimize your approach to deploying Windows Sun Valley, or if deploying a new version of an operating system is not a familiar process for you, some items to consider are provided below. - -## Determine eligibility - -As a first step, you will need to know which of your current devices meet the Windows Sun Valley hardware requirements. Most devices purchased in the last 18-24 months will be compatible with Windows Sun Valley. Verify that your device meets or exceeds [Windows Sun Valley requirements](windows-sv-requirements.md) to ensure it is compatible. - -Microsoft is currently developing analysis tools to help you evaluate your devices against the Windows Sun Valley hardware requirements. When Windows Sun Valley reaches general availability, end-users running Windows 10 Home, Pro, and Pro for Workstations will be able to use the **PC Health Check** app to determine their eligibility for Windows Sun Valley. end-users running Windows 10 Enterprise and Education editions should rely on their IT administrators to let them know when they are eligible for the upgrade.  - -Enterprise organizations looking to evaluate device readiness in their environments can expect this capability to be integrated into existing Microsoft tools, such as Endpoint analytics and Update Compliance. This capability will be available when Windows Sun Valley is generally available. Microsoft is also working with software publishing partners to facilitate adding Windows Sun Valley device support into their solutions. - -## Windows Sun Valley availability - -The availability of Windows Sun Valley will vary according to a device's hardware and whether the device receives updates directly, or from a management solution that is maintained by an IT administrator. - -##### Managed devices - -Managed devices are devices that are under organization control. Managed devices include those managed by Microsoft Intune, Microsoft Endpoint Configuration Manager, or other endpoint management solutions. - -If you manage devices on behalf of your organization, you will be able to upgrade eligible devices to Windows Sun Valley using your existing deployment and management tools at no cost when the upgrade reaches general availability. Organizations that use Windows Update for Business will have added benefits, such as: - -- Ensuring that devices that don't meet the minimum hardware requirements are not automatically offered the Windows Sun Valley upgrade. -- Additional insight into safeguard holds. While safeguard holds will function for Windows Sun Valley devices just as they do for Windows 10 today, administrators using Windows Update for Business will have access to information on which safeguard holds are preventing individual devices from taking the upgrade to Windows Sun Valley. - -> [!NOTE] -> If you use Windows Update for Business to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows Sun Valley. Deferrals are great for quality updates or to move to newer version of the same product (from example, from Windows 10, version 20H2 to 21H1), but they cannot migrate a device between products (from Windows 10 to Windows Sun Valley).
-> Additionally, Windows Sun Valley has a new End User License Agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new End User License Agreement on behalf of the end-users within your organization. - -##### Unmanaged devices - -Unmanaged devices are devices that are not managed by an IT administrator on behalf of an organization. For operating system (OS) deployment, these devices are not subject to organizational policies that manage upgrades or updates. - -Windows Sun Valley will be offered to eligible Windows 10 devices beginning later in the 2021 calendar year. Messaging on new devices will vary by PC manufacturer, but users will see labels such as **This PC will upgrade to Windows Sun Valley once available** on products that are available for purchase. - -The Windows Sun Valley upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Windows Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. - -Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This process improves the update experience and ensures that devices first nominated for updates are the devices likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. - -## Windows Sun Valley readiness considerations - -The recommended method to determine if your infrastructure, deployment processes, and management tools are ready for Windows Sun Valley is to join the [Windows Insider Program for Business](https://insider.windows.com/for-business). As a participant in the [Release Preview Channel](/windows-insider/business/validate-Release-Preview-Channel), you can validate that your devices and applications work as expected, and explore new features. - -As you plan your endpoint management strategy for Windows Sun Valley, consider moving to cloud-based mobile device management (MDM), such as [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). If a cloud-only approach isn't right for your organization just yet, you can still modernize and streamline essential pieces of your endpoint management strategy as follows: -- Create a [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview) (CMG) to manage Configuration Manager clients over the internet. -- Attach your existing Configuration Management estate to the cloud with [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions) so you can manage all devices from within the Microsoft Endpoint Manager admin center. -- Use [co-management](/mem/configmgr/comanage/overview) to concurrently manage devices using both Configuration Manager and Microsoft Intune. This allows you to take advantage of cloud-powered capabilities like [Conditional Access](/azure/active-directory/conditional-access/overview). - -For more information on the benefits of these approaches, see [Cloud Attach Your Future: The Big 3](https://techcommunity.microsoft.com/t5/configuration-manager-blog/cloud-attach-your-future-part-ii-quot-the-big-3-quot/ba-p/1750664). - -The introduction of Windows Sun Valley is also a good time to review your hardware refresh plans and prioritize eligible devices to ensure an optimal experience for your users. - -## Servicing and support - -Along with end-user experience and security improvements, Windows Sun Valley introduces enhancements to Microsoft's servicing approach based on your suggestions and feedback. - -**Quality updates**: Windows Sun Valley and Windows 10 devices will receive regular monthly quality updates to provide security updates and bug fixes. - -**Feature updates**: Microsoft will provide a single Windows Sun Valley feature update annually, targeted for release in the second half of each calendar year. - -**Lifecycle**: -- Home, Pro, Pro for Workstations, and Pro for Education editions of Windows Sun Valley will receive 24 months of support from the general availability date. -- Enterprise and Education editions of Windows Sun Valley will be supported for 36 months from the general availability date. - -When Windows Sun Valley reaches general availability, a consolidated Windows Sun Valley update history will be available on support.microsoft.com, similar to what is [available today for Windows 10](https://support.microsoft.com/topic/windows-10-update-history-1b6aac92-bf01-42b5-b158-f80c6d93eb11). Similarly, the [Windows release health](/windows/release-health/) hub will offer quick access to Windows Sun Valley servicing announcements, known issues, and safeguard holds. - -It is important that organizations have adequate time to plan for Windows Sun Valley. Microsoft also recognizes that many organizations will have a mix of Windows Sun Valley and Windows 10 devices across their ecosystem. Devices on in-service versions of Windows 10 will continue to receive monthly Windows 10 security updates through 2025, as well as incremental improvements to Windows 10 to support ongoing Microsoft 365 deployments. For more information, see the [Windows 10 release information](/windows/release-health/release-information) page, which offers information about the Windows 10 Semi-Annual Channel and Long-term Servicing Channel (LTSC) releases. - -## Application compatibility - -Microsoft's compatibility promise for Windows 10 is maintained for Windows Sun Valley. Data from the App Assure program shows that Windows 10 compatibility rates are over 99.7% for enterprise organizations, including line of business (LOB) apps. Microsoft remains committed to ensuring that the apps you rely upon continue to work as expected when you upgrade. Windows Sun Valley is subject to the same app compatibility validation requirements that are in place for Windows 10 today, for both feature and quality updates. - -#### App Assure and Test Base for Microsoft 365 - -If you run into compatibility issues or want to ensure that your organization's applications are compatible from day one, App Assure and Test Base for Microsoft 365 can help. - -**App Assure**: With enrollment in the [App Assure](/windows/compatibility/app-assure) service, any app compatibility issues that you find with Windows Sun Valley can be resolved. Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. - -**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. - -You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows Sun Valley. - -## Next steps - -[Prepare for Windows Sun Valley](windows-sv-prepare.md) - -## Also see - -[Plan to deploy updates for Windows 10 and Microsoft 365 Apps](/learn/modules/windows-plan/) diff --git a/windows/whats-new/windows-sv.md b/windows/whats-new/windows-sv.md deleted file mode 100644 index 392951b9ff..0000000000 --- a/windows/whats-new/windows-sv.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Windows Sun Valley overview -description: Overview of Windows Sun Valley -ms.assetid: E9E2DED5-DBA7-4300-B411-BA0FD39BE18C -ms.reviewer: -manager: laurawi -ms.audience: itpro -author: greg-lindsay -ms.author: greglin -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.localizationpriority: medium -audience: itpro -ms.topic: article -ms.custom: seo-marvel-apr2020 ---- - -# Windows Sun Valley overview - -**Applies to** - -- Windows Sun Valley - -This article provides an introduction to Windows Sun Valley, and answers some frequently asked questions. - -Also see the following articles to learn more about Windows Sun Valley: - -- [Windows Sun Valley requirements](windows-sv-requirements.md): Requirements to deploy Windows Sun Valley. -- [Plan for Windows Sun Valley](windows-sv-plan.md): Information to help you plan for Windows Sun Valley in your organization. -- [Prepare for Windows Sun Valley](windows-sv-prepare.md): Procedures to ensure readiness to deploy Windows Sun Valley. - -## Introduction - -Windows Sun Valley is the next evolution of Windows; it is the most significant update to the Windows operating system since Windows 10. It offers many innovations focused on enhancing end-user productivity in a fresh experience that is flexible and fluid. Windows Sun Valley is designed to support today's hybrid work environment, and intended to be the most reliable, secure, connected, and performant Windows operating system ever. - -Windows Sun Valley is built on the same foundation as Windows 10, so the investments you have made in tools for update and device management are carried forward. Windows Sun Valley also sustains the application compatibility promise made with Windows 10, supplemented by programs like App Assure. For Microsoft 365 customers seeking further assistance, FastTrack will continue to be available to support your efforts to adopt Windows Sun Valley. - -## How to get Windows Sun Valley - -Windows Sun Valley will be delivered as an upgrade to eligible devices running Windows 10, beginning later in the 2021 calendar year. Windows Sun Valley will also be available on eligible new devices. - -For administrators managing devices on behalf of their organization, Windows Sun Valley will be available through the same, familiar channels that you use today for Windows 10 feature updates. You will be able to use existing deployment and management tools, such as Windows Update for Business, Microsoft Endpoint Manager, and Windows Autopilot. For more information, see [Plan for Windows Sun Valley](windows-sv-plan.md). - -For devices that are not managed by an organization, the Windows Sun Valley upgrade will be offered to eligible Windows 10 devices through Windows Update using Microsoft's intelligent rollout process to ensure a smooth upgrade experience. - -For more information about device eligibility, see [Windows Sun Valley requirements](windows-sv-requirements.md). - -If you are interested in testing Windows Sun Valley before general availability, you can join the [Windows Insider Program](https://insider.windows.com) or [Windows Insider Program for Business](https://insider.windows.com/for-business). You can also preview Windows Sun Valley by enabling pre-release Windows 10 feature updates in [Microsoft Endpoint Configuration Manager](/mem/configmgr/core/servers/manage/pre-release-features) or [Windows Server Update Services](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/publishing-pre-release-windows-10-feature-updates-to-wsus/ba-p/845054) (WSUS). - -## Before you begin - -The following sections provide a quick summary of licensing, compatibility, management, and servicing considerations to help you get started with Windows Sun Valley. - -#### Licensing - -There are no unique licensing requirements for Windows Sun Valley beyond what is required for Windows 10 devices. - -Microsoft 365 licenses that include Windows 10 licenses will permit you to run Windows Sun Valley on supported devices. If you have a volume license, it will equally cover Windows Sun Valley and Windows 10 devices before and after upgrade. - -#### Compatibility - -Most accessories and associated drivers that work with Windows 10 are expected to work with Windows Sun Valley. Check with your accessory manufacturer for specific details. - -Windows Sun Valley preserves the application compatibility promise made with Windows 10, and does not require changes to existing support processes or tooling to sustain the currency of applications and devices. Microsoft 365 customers can continue to use programs such as App Assure and FastTrack to support IT efforts to adopt and maintain Windows Sun Valley. For more information, see [Application compatibility](windows-sv-plan.md#application-compatibility). - -#### Familiar processes - -Windows Sun Valley is built on the same foundation as Windows 10. Typically, you can use the same tools and solutions you use today to deploy, manage, and secure Windows Sun Valley. Your current management tools and processes will also work to manage monthly quality updates for both Windows 10 and Windows Sun Valley. - -> [!IMPORTANT] -> Check with the providers of any non-Microsoft security and management solutions that you use to ensure compatibility with Windows Sun Valley, particularly those providing security or data loss prevention capabilities. - -For more information, see [Prepare for Windows Sun Valley](windows-sv-prepare.md). - -#### Servicing Windows Sun Valley - -Like Windows 10, Windows Sun Valley will receive monthly quality updates. However, it will have a new feature update cadence. Windows Sun Valley feature updates will be released once per year. - -When Windows Sun Valley reaches general availability, important servicing-related announcements and information about known issues and safeguard holds can be found on the [Windows release health](https://aka.ms/windowsreleasehealth) hub. Monthly release notes will also be available from a consolidated Windows Sun Valley update history page at that time. For more information, see [Servicing and support](windows-sv-plan.md#servicing-and-support). - -## Next steps - -[Windows Sun Valley requirements](windows-sv-requirements.md)
-[Plan for Windows Sun Valley](windows-sv-plan.md)
-[Prepare for Windows Sun Valley](windows-sv-prepare.md) \ No newline at end of file From da5e83a1887db5401adf04d571724d1e0a31129b Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 01:21:08 -0700 Subject: [PATCH 091/104] capitalization --- windows/whats-new/windows-11-prepare.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/whats-new/windows-11-prepare.md b/windows/whats-new/windows-11-prepare.md index 3ef63328a5..a1a45c11c6 100644 --- a/windows/whats-new/windows-11-prepare.md +++ b/windows/whats-new/windows-11-prepare.md @@ -33,7 +33,7 @@ The tools that you use for core workloads during Windows 10 deployments can stil #### On-premise solutions -- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows 11** product category. After you sync the product category, you will see Windows 11 offered as an option. If you would like to validate Windows 11 prior to release, you can sync the Windows Insider Pre-release category as well. +- If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows 11** product category. After you sync the product category, you will see Windows 11 offered as an option. If you would like to validate Windows 11 prior to release, you can sync the **Windows Insider Pre-release** category as well. > [!NOTE] > During deployment, you will be prompted to agree to the End User License Agreement on behalf of your users. Additionally, you will not see an x86 option because Windows 11 is not supported on 32-bit architecture. @@ -45,9 +45,9 @@ The tools that you use for core workloads during Windows 10 deployments can stil #### Cloud-based solutions -- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to use the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows 11. Feature Update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows 11). +- If you use Windows Update for Business Group Policy or Configuration Service Provider (CSP) policies, you will need to use the **Target Version** capability rather than feature update deferrals to upgrade from Windows 10 to Windows 11. Feature update deferrals are great to move to newer versions of your current product (for example, Windows 10, version 20H2 to 21H1), but do not enable you to move between products (Windows 10 to Windows 11). - Quality update deferrals will continue to work the same across both Windows 10 and Windows 11. This is true regardless of which management tool you use to configure Windows Update for Business policies. -- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use **Feature Update Deployments** to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows 11. You can also continue using the same update experience controls to manage Windows 10 and Windows 11. +- If you use Microsoft Intune and have a Microsoft 365 E3 license, you will be able to use feature update deployments to easily update devices from one release of Windows 10 to another, or to upgrade Windows 10 devices to Windows 11. You can also continue using the same update experience controls to manage Windows 10 and Windows 11. ## Cloud-based management From a0f5e69c5d83903b287a0dd186e62b62cfcc9d89 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 01:36:46 -0700 Subject: [PATCH 092/104] link fix --- windows/deployment/TOC.yml | 10 ++++------ windows/deployment/deploy-whats-new.md | 5 +++-- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index cafdf97782..1348d4e836 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -5,8 +5,6 @@ items: - name: What's new href: deploy-whats-new.md - - name: Windows 11 deployment overview - href: /windows/whats-new/windows-11-overview.md - name: Windows client deployment scenarios href: windows-10-deployment-scenarios.md - name: What is Windows as a service? @@ -35,8 +33,8 @@ - name: Plan items: - - name: Windows 11 deployment planning - href: /windows/whats-new/windows-11-plan.md + - name: Plan for Windows 11 + href: /windows/whats-new/windows-11-plan - name: Create a deployment plan href: update/create-deployment-plan.md - name: Define readiness criteria @@ -71,8 +69,8 @@ - name: Prepare items: - - name: Prepare to deploy Windows 11 - href: /windows/whats-new/windows-11-prepare.md + - name: Prepare for Windows 11 + href: /windows/whats-new/windows-11-prepare - name: Prepare to deploy Windows 10 updates href: update/prepare-deploy-windows.md - name: Evaluate and update infrastructure diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index fa8ca9e964..e3a0d81b25 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -16,20 +16,21 @@ ms.topic: article ms.custom: seo-marvel-apr2020 --- -# What's new in Windows 10 deployment +# What's new in Windows client deployment **Applies to:** - Windows 10 +- Windows 11 ## In this topic This topic provides an overview of new solutions and online content related to deploying Windows client in your organization. - For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index). -- For an overview of Windows 11, see [What's new in Windows 11](/windows/whats-new/windows-11). ## Latest news +Check out the [Overview of Windows 11](/windows/whats-new/windows-11). [SetupDiag](#setupdiag) is included with Windows 10, version 2004 and later.
The [Windows ADK for Windows 10, version 2004](/windows-hardware/get-started/adk-install) is available.
New capabilities are available for [Delivery Optimization](#delivery-optimization) and [Windows Update for Business](#windows-update-for-business).
From f980c28e109ca579201859dd436635716942e944 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 02:07:14 -0700 Subject: [PATCH 093/104] small edit --- windows/whats-new/windows-11-plan.md | 4 ++-- windows/whats-new/windows-11-prepare.md | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/windows/whats-new/windows-11-plan.md b/windows/whats-new/windows-11-plan.md index ad68e1ebfa..1227f3908d 100644 --- a/windows/whats-new/windows-11-plan.md +++ b/windows/whats-new/windows-11-plan.md @@ -58,7 +58,7 @@ If you manage devices on behalf of your organization, you will be able to upgrad > [!NOTE] > If you use Windows Update for Business to manage feature update deployments today, you will need to leverage the **Target Version** policy rather than **Feature Update deferrals** to move from Windows 10 to Windows 11. Deferrals are great for quality updates or to move to newer version of the same product (from example, from Windows 10, version 20H2 to 21H1), but they cannot migrate a device between products (from Windows 10 to Windows 11).
-> Additionally, Windows 11 has a new End User License Agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new End User License Agreement on behalf of the end-users within your organization. +> Also, Windows 11 has a new End User License Agreement. If you are deploying with Windows Update for Business **Target Version** or with Windows Server Update Services, you are accepting this new End User License Agreement on behalf of the end-users within your organization. ##### Unmanaged devices @@ -68,7 +68,7 @@ Windows 11 will be offered to eligible Windows 10 devices beginning later in the The Windows 11 upgrade will be available initially on eligible, unmanaged devices to users who manually seek the upgrade through Windows Update. As with all Windows Update managed devices, the **Windows Update Settings** page will confirm when a device is eligible, and users can upgrade if they choose to. -Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be leveraged when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This process improves the update experience and ensures that devices first nominated for updates are the devices likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. +Just like Windows 10, the machine learning based [intelligent rollout](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/using-machine-learning-to-improve-the-windows-10-update/ba-p/877860) process will be used when rolling out upgrades. Machine learning uses a combination of testing, close partner engagement, feedback, diagnostic data, and real-life insights to manage quality. This process improves the update experience, and ensures that devices first nominated for updates are the devices likely to have a seamless experience. Devices that might have compatibility issues with the upgrade get the benefit of resolving these issues before the upgrade is offered. ## Windows 11 readiness considerations diff --git a/windows/whats-new/windows-11-prepare.md b/windows/whats-new/windows-11-prepare.md index a1a45c11c6..dda3e2c11d 100644 --- a/windows/whats-new/windows-11-prepare.md +++ b/windows/whats-new/windows-11-prepare.md @@ -108,7 +108,7 @@ At a high level, the tasks involved are: 6. Test and support the pilot devices. 7. Determine broad deployment readiness based on the results of the pilot. -## end-user readiness +## End-user readiness Do not overlook the importance of end-user readiness to deliver an effective, enterprise-wide deployment of Windows 11. Windows 11 has a familiar design, but your users will see several enhancements to the overall user interface. They will also need to adapt to changes in menus and settings pages. Therefore, consider the following tasks to prepare users and your IT support staff Windows 11: - Create a communications schedule to ensure that you provide the right message at the right time to the right groups of users, based on when they will see the changes. @@ -117,7 +117,8 @@ Do not overlook the importance of end-user readiness to deliver an effective, en ## Learn more -See the [Stay current with Windows 10 and Microsoft 365 Apps](/learn/paths/m365-stay-current/) learning path on Microsoft Learn. The learning path was created for Windows 10, but the basic principles and tasks outlined for the plan, prepare, and deploy phases also apply to your deployment of Windows 11. +See the [Stay current with Windows 10 and Microsoft 365 Apps](/learn/paths/m365-stay-current/) learning path on Microsoft Learn. +- The learning path was created for Windows 10, but the basic principles and tasks outlined for the plan, prepare, and deploy phases also apply to your deployment of Windows 11. ## See also From 3c0db3c4609ccb692a6394adce30440a37a130b3 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 02:12:22 -0700 Subject: [PATCH 094/104] format fix --- windows/deployment/deploy-whats-new.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index e3a0d81b25..d2e0935b7d 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -30,7 +30,11 @@ This topic provides an overview of new solutions and online content related to d ## Latest news -Check out the [Overview of Windows 11](/windows/whats-new/windows-11). +Check out the following new articles about Windows 11: +- [Overview of Windows 11](/windows/whats-new/windows-11) +- [Plan for Windows 11](/windows/whats-new/windows-11-plan) +- [Prepare for Windows 11](/windows/whats-new/windows-11-prepare) + [SetupDiag](#setupdiag) is included with Windows 10, version 2004 and later.
The [Windows ADK for Windows 10, version 2004](/windows-hardware/get-started/adk-install) is available.
New capabilities are available for [Delivery Optimization](#delivery-optimization) and [Windows Update for Business](#windows-update-for-business).
From f20d6bcbb2669165ce231e35735dcd4defa8dd95 Mon Sep 17 00:00:00 2001 From: v-miegge <49650192+v-miegge@users.noreply.github.com> Date: Thu, 24 Jun 2021 07:15:42 -0700 Subject: [PATCH 095/104] CI 152135 - QA review --- .../hello-for-business/hello-aad-join-cloud-only-deploy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-aad-join-cloud-only-deploy.md b/windows/security/identity-protection/hello-for-business/hello-aad-join-cloud-only-deploy.md index 379f033684..850b4b5214 100644 --- a/windows/security/identity-protection/hello-for-business/hello-aad-join-cloud-only-deploy.md +++ b/windows/security/identity-protection/hello-for-business/hello-aad-join-cloud-only-deploy.md @@ -16,7 +16,7 @@ localizationpriority: medium ms.date: 06/23/2021 ms.reviewer: --- -# Azure AD Joined Cloud Only Deployment +# Azure Active Directory join cloud only deployment ## Introduction @@ -59,9 +59,9 @@ However, not everyone uses Intune. The following method explains how to disable 1. Sign into the [Microsoft Endpoint Manager](https://endpoint.microsoft.com/) admin center. 2. Go to **Devices** > **Enrollment** > **Enroll devices** > **Windows enrollment** > **Windows Hello for Business**. The Windows Hello for Business pane opens. -3. Select from the following options for **Configure Windows Hello for Business**: +3. If you don't want to enable Windows Hello for Business during device enrollment, select **Disabled** for **Configure Windows Hello for Business**. - 1. **Disabled**: If you don't want to enable Windows Hello for Business during device enrollment, select this option. When disabled, users cannot provision Windows Hello for Business. When set to Disabled, you can still configure the subsequent settings for Windows Hello for Business even though this policy won't enable Windows Hello for Business. + When disabled, users cannot provision Windows Hello for Business. When set to Disabled, you can still configure the subsequent settings for Windows Hello for Business even though this policy won't enable Windows Hello for Business. > [!NOTE] > This policy is only applied during new device enrollments. For currently enrolled devices, you can [set the same settings in a device configuration policy](hello-manage-in-organization.md). From 01af22fc75513dbe69c9bafa76e70e5c831cf8e7 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 11:37:19 -0700 Subject: [PATCH 096/104] hook up article to TOC --- windows/deployment/TOC.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 1348d4e836..ae0fdee1a2 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -267,6 +267,8 @@ items: - name: How does Windows Update work? href: update/how-windows-update-works.md + - name: Windows 10 upgrade paths + href: upgrade/windows-10-upgrade-paths.md - name: Deploy Windows 10 with Microsoft 365 href: deploy-m365.md - name: Understanding the Unified Update Platform From f25f4173932e00702c8aa4d9525c593a013ab649 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 12:15:35 -0700 Subject: [PATCH 097/104] change testbase link --- windows/whats-new/windows-11-plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/windows-11-plan.md b/windows/whats-new/windows-11-plan.md index 1227f3908d..3df8ed3080 100644 --- a/windows/whats-new/windows-11-plan.md +++ b/windows/whats-new/windows-11-plan.md @@ -109,7 +109,7 @@ If you run into compatibility issues or want to ensure that your organization's **App Assure**: With enrollment in the [App Assure](/windows/compatibility/app-assure) service, any app compatibility issues that you find with Windows 11 can be resolved. Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. -**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://www.microsoft.com/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. +**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://aka.ms/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows 11. From eefda074104c8536d027ddbe9b4a4736078b7cd7 Mon Sep 17 00:00:00 2001 From: John Flores Date: Thu, 24 Jun 2021 15:16:47 -0400 Subject: [PATCH 098/104] Update windows-11-prepare.md --- windows/whats-new/windows-11-prepare.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/windows-11-prepare.md b/windows/whats-new/windows-11-prepare.md index dda3e2c11d..5ccbff2c5b 100644 --- a/windows/whats-new/windows-11-prepare.md +++ b/windows/whats-new/windows-11-prepare.md @@ -31,7 +31,7 @@ The tools that you use for core workloads during Windows 10 deployments can stil > [!IMPORTANT] > Be sure to check with the providers of any non-Microsoft solutions that you use. Verify compatibility of these tools with Windows 11, particularly if they provide security or data loss prevention capabilities. -#### On-premise solutions +#### On-premises solutions - If you use Windows Server Update Service (WSUS), you will need to sync the new **Windows 11** product category. After you sync the product category, you will see Windows 11 offered as an option. If you would like to validate Windows 11 prior to release, you can sync the **Windows Insider Pre-release** category as well. @@ -59,7 +59,7 @@ The following are some common use cases and the corresponding Microsoft Endpoint - **Configure rules and control settings for users, apps, and devices**: When you enroll devices in [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), administrators have full control over apps, settings, features, and security for both Windows 11 and Windows 10. You can also use app protection policies to require multi-factor authentication (MFA) for specific apps. - **Streamline device management for frontline, remote, and onsite workers**: Introduced with Windows 10, [cloud configuration](/mem/intune/fundamentals/cloud-configuration) is a standard, easy-to-manage, device configuration that is cloud-optimized for users with specific workflow needs. It can be deployed to devices running the Pro, Enterprise, and Education editions of Windows 11 by using Microsoft Endpoint Manager. -If you are exclusively using an on-premise device management solution (for example, Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune. These solutions can make it easier to keep devices secure and up-to-date. +If you are exclusively using an on-premises device management solution (for example, Configuration Manager), you can still use the [cloud management gateway](/mem/configmgr/core/clients/manage/cmg/overview), enable [tenant attach](/mem/configmgr/tenant-attach/device-sync-actions), or enable [co-management](/mem/configmgr/comanage/overview) with Microsoft Intune. These solutions can make it easier to keep devices secure and up-to-date. ## Review servicing approach and policies From 2b1f47e6f3dcc2a72d5965d1d6bf9a72bd72c896 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 12:44:49 -0700 Subject: [PATCH 099/104] edit S mode requirements --- windows/whats-new/windows-11-requirements.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/whats-new/windows-11-requirements.md b/windows/whats-new/windows-11-requirements.md index 2fbeeb8490..2b48d9fb14 100644 --- a/windows/whats-new/windows-11-requirements.md +++ b/windows/whats-new/windows-11-requirements.md @@ -47,8 +47,8 @@ For information about tools to evaluate readiness, see [Determine eligibility](w For the best Windows 11 upgrade experience, eligible devices should be running Windows 10, version 20H1 or later. > [!NOTE] -> S mode is not supported on Windows 11. -> If you are running Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading.
 
+> S mode is only supported on the Home edition of Windows 11. +> If you are running a different edition of Windows in S mode, you will need to first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode) prior to upgrading.
 
> Switching a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you cannot switch back to S mode later. ## Feature-specific requirements From 6b4c4036a9753d7ae79f7b2891de7290bc70bf3f Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 12:49:11 -0700 Subject: [PATCH 100/104] public to private for testbase --- windows/whats-new/windows-11-plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/windows-11-plan.md b/windows/whats-new/windows-11-plan.md index 3df8ed3080..17d61a7125 100644 --- a/windows/whats-new/windows-11-plan.md +++ b/windows/whats-new/windows-11-plan.md @@ -109,7 +109,7 @@ If you run into compatibility issues or want to ensure that your organization's **App Assure**: With enrollment in the [App Assure](/windows/compatibility/app-assure) service, any app compatibility issues that you find with Windows 11 can be resolved. Microsoft will help you remedy application issues at no cost. Since 2018, App Assure has evaluated almost 800,000 apps, and subscriptions are free for eligible customers with 150+ seats. -**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://aka.ms/testbase) (currently in public preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. +**Test Base for Microsoft 365**: For software publishers, systems integrators, and IT administrators, [Test Base for Microsoft 365](https://aka.ms/testbase) (currently in private preview) is a service that allows you to validate your apps across a variety of Windows feature and quality updates and environments in a Microsoft-managed Azure environment. Enterprise organizations can also nominate their software publishers for participation by completing a short form. You might already be using App Assure and Test Base in your Windows 10 environment. Both of these tools will continue to function with Windows 11. From 6747493aab97d69588473413beaf68978e48af4d Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 24 Jun 2021 13:13:28 -0700 Subject: [PATCH 101/104] update requirements --- windows/whats-new/windows-11-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/windows-11-requirements.md b/windows/whats-new/windows-11-requirements.md index 2b48d9fb14..8c87b2c454 100644 --- a/windows/whats-new/windows-11-requirements.md +++ b/windows/whats-new/windows-11-requirements.md @@ -60,7 +60,7 @@ Some features in Windows 11 have requirements beyond those listed above. See the - **BitLocker to Go**: requires a USB flash drive. This feature is available in Windows Pro and above editions. - **Client Hyper-V**: requires a processor with second-level address translation (SLAT) capabilities. This feature is available in Windows Pro editions and above. - **Cortana**: requires a microphone and speaker and is currently available on Windows 11 for Australia, Brazil, Canada, China, France, Germany, India, Italy, Japan, Mexico, Spain, United Kingdom, and United States. -- **DirectStorage**: requires 1 TB or greater NVMe SSD to store and run games that use the "Standard NVM Express Controller" driver and a DirectX12 Ultimate GPU. +- **DirectStorage**: requires an NVMe SSD to store and run games that use the Standard NVM Express Controller driver and a DirectX12 GPU with Shader Model 6.0 support. - **DirectX 12 Ultimate**: available with supported games and graphics chips. - **Presence**: requires sensor that can detect human distance from device or intent to interact with device. - **Intelligent Video Conferencing**: requires video camera, microphone, and speaker (audio output) From 3919f4de32931580f92760397d6ec2390afa0dc8 Mon Sep 17 00:00:00 2001 From: Thomas Raya Date: Thu, 24 Jun 2021 16:34:43 -0700 Subject: [PATCH 102/104] Update docfx.json --- windows/whats-new/docfx.json | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/whats-new/docfx.json b/windows/whats-new/docfx.json index 16f6364ce9..fe5bc2fe98 100644 --- a/windows/whats-new/docfx.json +++ b/windows/whats-new/docfx.json @@ -3,8 +3,8 @@ "content": [ { "files": [ - "**/*.md", - "**/*.yml" + "**/**/*.md", + "**/**/*.yml" ], "exclude": [ "**/obj/**", @@ -19,9 +19,9 @@ "resource": [ { "files": [ - "**/*.png", - "**/*.jpg", - "**/*.gif" + "**/**/*.png", + "**/**/*.jpg", + "**/**/*.gif" ], "exclude": [ "**/obj/**", From 01d51d82f1b559925c5b029fa959cea9aab20336 Mon Sep 17 00:00:00 2001 From: denisebmsft <18405051+denisebmsft@users.noreply.github.comgit> Date: Fri, 25 Jun 2021 08:54:28 -0700 Subject: [PATCH 103/104] Update .openpublishing.redirection.json --- .openpublishing.redirection.json | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 4afc122348..8dbea776cc 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -18919,6 +18919,11 @@ "source_path": "windows/security/threat-protection/device-control/device-control-report.md", "redirect_url": "/microsoft-365/security/defender-endpoint/device-control-report", "redirect_document_id": false - } + }, + { + "source_path": "windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows.md", + "redirect_url": "/windows/security/threat-protection/windows-defender-system-guard/how-hardware-based-root-of-trust-helps-protect-windows", + "redirect_document_id": false + } ] } From 7d9be28bd3ac8285558ffc9248ba849c65f52a4c Mon Sep 17 00:00:00 2001 From: denisebmsft <18405051+denisebmsft@users.noreply.github.comgit> Date: Fri, 25 Jun 2021 08:55:31 -0700 Subject: [PATCH 104/104] Delete system-guard-how-hardware-based-root-of-trust-helps-protect-windows.md --- ...sed-root-of-trust-helps-protect-windows.md | 88 ------------------- 1 file changed, 88 deletions(-) delete mode 100644 windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows.md diff --git a/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows.md b/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows.md deleted file mode 100644 index bb47f523e4..0000000000 --- a/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: How Windows Defender System Guard protect Windows 10 from firmware exploits -description: Windows Defender System Guard in Windows 10 uses a hardware-based root of trust to securely protect systems against firmware exploits. -ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb -ms.reviewer: -manager: dansimp -ms.author: deniseb -author: denisebmsft -search.appverid: met150 -ms.prod: m365-security -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: security -ms.localizationpriority: medium -ms.date: 03/01/2019 -ms.custom: asr -ms.technology: mde ---- - - -# Windows Defender System Guard: How a hardware-based root of trust helps protect Windows 10 - -In order to protect critical resources such as the Windows authentication stack, single sign-on tokens, the Windows Hello biometric stack, and the Virtual Trusted Platform Module, a system's firmware and hardware must be trustworthy. - -Windows Defender System Guard reorganizes the existing Windows 10 system integrity features under one roof and sets up the next set of investments in Windows security. It's designed to make these security guarantees: - -- Protect and maintain the integrity of the system as it starts up -- Validate that system integrity has truly been maintained through local and remote attestation - -## Maintaining the integrity of the system as it starts - -### Static Root of Trust for Measurement (SRTM) - -With Windows 7, one of the means attackers would use to persist and evade detection was to install what is often referred to as a bootkit or rootkit on the system. -This malicious software would start before Windows started, or during the boot process itself, enabling it to start with the highest level of privilege. - -With Windows 10 running on modern hardware (that is, Windows 8-certified or greater) a hardware-based root of trust helps ensure that no unauthorized firmware or software (such as a bootkit) can start before the Windows bootloader. -This hardware-based root of trust comes from the device’s Secure Boot feature, which is part of the Unified Extensible Firmware Interface (UEFI). -This technique of measuring the static early boot UEFI components is called the Static Root of Trust for Measurement (SRTM). - -As there are thousands of PC vendors that produce numerous models with different UEFI BIOS versions, there becomes an incredibly large number of SRTM measurements upon bootup. -Two techniques exist to establish trust here—either maintain a list of known 'bad' SRTM measurements (also known as a block list), or a list of known 'good' SRTM measurements (also known as an allow list). -Each option has a drawback: - -- A list of known 'bad' SRTM measurements allows a hacker to change just 1 bit in a component to create an entirely new SRTM hash that needs to be listed. This means that the SRTM flow is inherently brittle - a minor change can invalidate the entire chain of trust. -- A list of known 'good' SRTM measurements requires each new BIOS/PC combination measurement to be carefully added, which is slow. -In addition, a bug fix for UEFI code can take a long time to design, build, retest, validate, and redeploy. - -### Secure Launch—the Dynamic Root of Trust for Measurement (DRTM) - -Windows Defender System Guard Secure Launch, first introduced in Windows 10 version 1809, aims to alleviate these issues by leveraging a technology known as the Dynamic Root of Trust for Measurement (DRTM). -DRTM lets the system freely boot into untrusted code initially, but shortly after launches the system into a trusted state by taking control of all CPUs and forcing them down a well-known and measured code path. -This has the benefit of allowing untrusted early UEFI code to boot the system, but then being able to securely transition into a trusted and measured state. - - -![System Guard Secure Launch](images/system-guard-secure-launch.png) - -Secure Launch simplifies management of SRTM measurements because the launch code is now unrelated to a specific hardware configuration. This means the number of valid code measurements is small, and future updates can be deployed more widely and quickly. - -### System Management Mode (SMM) protection - -System Management Mode (SMM) is a special-purpose CPU mode in x86 microcontrollers that handles power management, hardware configuration, thermal monitoring, and anything else the manufacturer deems useful. -Whenever one of these system operations is requested, a non-maskable interrupt (SMI) is invoked at runtime, which executes SMM code installed by the BIOS. -SMM code executes in the highest privilege level and is invisible to the OS, which makes it an attractive target for malicious activity. Even if System Guard Secure Launch is used to late launch, SMM code can potentially access hypervisor memory and change the hypervisor. -To defend against this, two techniques are used: - -1. Paging protection to prevent inappropriate access to code and data -2. SMM hardware supervision and attestation - -Paging protection can be implemented to lock certain code tables to be read-only to prevent tampering. -This prevents access to any memory that has not been specifically assigned. - -A hardware-enforced processor feature known as a supervisor SMI handler can monitor the SMM and make sure it does not access any part of the address space that it is not supposed to. - -SMM protection is built on top of the Secure Launch technology and requires it to function. -In the future, Windows 10 will also measure this SMI Handler’s behavior and attest that no OS-owned memory has been tampered with. - -## Validating platform integrity after Windows is running (run time) - -While Windows Defender System Guard provides advanced protection that will help protect and maintain the integrity of the platform during boot and at run time, the reality is that we must apply an "assume breach" mentality to even our most sophisticated security technologies. We should be able to trust that the technologies are successfully doing their jobs, but we also need the ability to verify that they were successful in achieving their goals. When it comes to platform integrity, we can’t just trust the platform, which potentially could be compromised, to self-attest to its security state. So Windows Defender System Guard includes a series of technologies that enable remote analysis of the device’s integrity. - -As Windows 10 boots, a series of integrity measurements are taken by Windows Defender System Guard using the device’s Trusted Platform Module 2.0 (TPM 2.0). System Guard Secure Launch will not support earlier TPM versions, such as TPM 1.2. This process and data are hardware-isolated away from Windows to help ensure that the measurement data is not subject to the type of tampering that could happen if the platform was compromised. From here, the measurements can be used to determine the integrity of the device’s firmware, hardware configuration state, and Windows boot-related components, just to name a few. - - -![Boot time integrity](images/windows-defender-system-guard-boot-time-integrity.png) - -After the system boots, Windows Defender System Guard signs and seals these measurements using the TPM. Upon request, a management system like Intune or Microsoft Endpoint Manager can acquire them for remote analysis. If Windows Defender System Guard indicates that the device lacks integrity, the management system can take a series of actions, such as denying the device access to resources. -