mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge pull request #10116 from aczechowski/cz-9122642-smode
retire s-mode articles
This commit is contained in:
Stacyrch140
GitHub
commit
6d23f52f83
@ -92,7 +92,7 @@
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
"source_path": "education/windows/enable-s-mode-on-surface-go-devices.md",
|
"source_path": "education/windows/enable-s-mode-on-surface-go-devices.md",
|
||||||
"redirect_url": "/windows/deployment/s-mode",
|
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/s-mode/index",
|
||||||
"redirect_document_id": false
|
"redirect_document_id": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
@ -147,7 +147,7 @@
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
"source_path": "education/windows/test-windows10s-for-edu.md",
|
"source_path": "education/windows/test-windows10s-for-edu.md",
|
||||||
"redirect_url": "/windows/deployment/s-mode",
|
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/s-mode/index",
|
||||||
"redirect_document_id": false
|
"redirect_document_id": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
|
|||||||
@ -1370,6 +1370,16 @@
|
|||||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-overview",
|
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-overview",
|
||||||
"redirect_document_id": true
|
"redirect_document_id": true
|
||||||
},
|
},
|
||||||
|
{
|
||||||
|
"source_path": "windows/deployment/windows-10-pro-in-s-mode.md",
|
||||||
|
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/s-mode/switch-edition-from-s-mode",
|
||||||
|
"redirect_document_id": false
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"source_path": "windows/deployment/s-mode.md",
|
||||||
|
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/s-mode/index",
|
||||||
|
"redirect_document_id": false
|
||||||
|
},
|
||||||
{
|
{
|
||||||
"source_path": "windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md",
|
"source_path": "windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md",
|
||||||
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups",
|
"redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups",
|
||||||
|
|||||||
@ -5127,7 +5127,7 @@
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
"source_path": "windows/security/threat-protection/windows-defender-application-control/LOB-win32-apps-on-s.md",
|
"source_path": "windows/security/threat-protection/windows-defender-application-control/LOB-win32-apps-on-s.md",
|
||||||
"redirect_url": "/windows/security/application-security/application-control/windows-defender-application-control/deployment/LOB-win32-apps-on-s",
|
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/s-mode/wdac-allow-lob-win32-apps",
|
||||||
"redirect_document_id": false
|
"redirect_document_id": false
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
@ -9184,6 +9184,11 @@
|
|||||||
"source_path": "windows/security/identity-protection/hello-for-business/hello-feature-dual-enrollment.md",
|
"source_path": "windows/security/identity-protection/hello-for-business/hello-feature-dual-enrollment.md",
|
||||||
"redirect_url": "/windows/security/identity-protection/hello-for-business/dual-enrollment",
|
"redirect_url": "/windows/security/identity-protection/hello-for-business/dual-enrollment",
|
||||||
"redirect_document_id": false
|
"redirect_document_id": false
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"source_path": "windows/security/application-security/application-control/windows-defender-application-control/deployment/LOB-win32-apps-on-s.md",
|
||||||
|
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/s-mode/wdac-allow-lob-win32-apps",
|
||||||
|
"redirect_document_id": false
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|||||||
@ -16,14 +16,6 @@ items:
|
|||||||
href: windows-11-se-settings-list.md
|
href: windows-11-se-settings-list.md
|
||||||
- name: Frequently Asked Questions (FAQ)
|
- name: Frequently Asked Questions (FAQ)
|
||||||
href: windows-11-se-faq.yml
|
href: windows-11-se-faq.yml
|
||||||
- name: Windows in S Mode
|
|
||||||
items:
|
|
||||||
- name: Overview
|
|
||||||
href: /windows/deployment/s-mode?context=/education/context/context
|
|
||||||
- name: Switch Windows edition from S mode
|
|
||||||
href: /windows/deployment/windows-10-pro-in-s-mode?context=/education/context/context
|
|
||||||
- name: Deploy Win32 apps to S Mode devices
|
|
||||||
href: /windows/security/threat-protection/windows-defender-application-control/lob-win32-apps-on-s?context=/education/context/context
|
|
||||||
- name: Shared devices and guests access
|
- name: Shared devices and guests access
|
||||||
href: /windows/configuration/shared-devices-concepts?context=/education/context/context
|
href: /windows/configuration/shared-devices-concepts?context=/education/context/context
|
||||||
- name: Take tests and assessments in Windows
|
- name: Take tests and assessments in Windows
|
||||||
|
|||||||
@ -367,10 +367,6 @@
|
|||||||
href: do/waas-delivery-optimization-reference.md?context=/windows/deployment/context/context
|
href: do/waas-delivery-optimization-reference.md?context=/windows/deployment/context/context
|
||||||
- name: FoD and language packs for WSUS and Configuration Manager
|
- name: FoD and language packs for WSUS and Configuration Manager
|
||||||
href: update/fod-and-lang-packs.md
|
href: update/fod-and-lang-packs.md
|
||||||
- name: Windows client in S mode
|
|
||||||
href: s-mode.md
|
|
||||||
- name: Switch to Windows client Pro or Enterprise from S mode
|
|
||||||
href: windows-10-pro-in-s-mode.md
|
|
||||||
- name: Windows client deployment tools
|
- name: Windows client deployment tools
|
||||||
items:
|
items:
|
||||||
- name: Windows client deployment scenarios and tools
|
- name: Windows client deployment scenarios and tools
|
||||||
|
|||||||
Binary file not shown.
|
Before Width: | Height: | Size: 31 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB |
@ -1,57 +0,0 @@
|
|||||||
---
|
|
||||||
title: Windows Pro in S mode
|
|
||||||
description: Overview of Windows Pro and Enterprise in S mode.
|
|
||||||
ms.localizationpriority: high
|
|
||||||
ms.service: windows-client
|
|
||||||
manager: aaroncz
|
|
||||||
author: frankroj
|
|
||||||
ms.author: frankroj
|
|
||||||
ms.topic: conceptual
|
|
||||||
ms.date: 04/26/2023
|
|
||||||
ms.subservice: itpro-deploy
|
|
||||||
---
|
|
||||||
|
|
||||||
# Windows Pro in S mode
|
|
||||||
|
|
||||||
S mode is a configuration that's available on all Windows Editions, and it's enabled at the time of manufacturing. Windows can be switched out of S mode at any time, as shown in the picture below. However, the switch is a one-time operation, and can only be undone by a wipe and reload of the operating system.
|
|
||||||
|
|
||||||
:::image type="content" source="images/smodeconfig.png" alt-text="Table listing the capabilities of S mode across the different Windows editions.":::
|
|
||||||
|
|
||||||
## S mode key features
|
|
||||||
|
|
||||||
### Microsoft-verified security
|
|
||||||
|
|
||||||
With Windows in S mode, you'll find your favorite applications in the Microsoft Store, where they're Microsoft-verified for security. You can also feel secure when you're online. Microsoft Edge, your default browser, gives you protection against phishing and socially-engineered malware.
|
|
||||||
|
|
||||||
### Performance that lasts
|
|
||||||
|
|
||||||
Start-ups are quick, and S mode is built to keep them that way. With Microsoft Edge as your browser, your online experience is fast and secure. You'll enjoy a smooth, responsive experience, whether you're streaming videos, opening apps, or being productive on the go.
|
|
||||||
|
|
||||||
### Choice and flexibility
|
|
||||||
|
|
||||||
Save your files to your favorite cloud, like OneDrive or Dropbox, and access them from any device you choose. Browse the Microsoft Store for thousands of apps, and if you don't find exactly what you want, you can easily [switch out of S mode](./windows-10-pro-in-s-mode.md) to Windows Home, Pro, or Enterprise editions at any time and search the web for more choices, as shown below.
|
|
||||||
|
|
||||||
:::image type="content" source="images/s-mode-flow-chart.png" alt-text="Switching out of S mode flow chart.":::
|
|
||||||
|
|
||||||
## Deployment
|
|
||||||
|
|
||||||
Windows in S mode is built for [modern management](/windows/client-management/manage-windows-10-in-your-organization-modern-management), which means using [Windows Autopilot](/mem/autopilot/windows-autopilot) for deployment, and a Mobile Device Management (MDM) solution for management, like Microsoft Intune.
|
|
||||||
|
|
||||||
Windows Autopilot lets you deploy the device directly to a user without IT having to touch the physical device. Instead of manually deploying a custom image, Windows Autopilot will start with a generic device that can only be used to join the company Microsoft Entra tenant or Active Directory domain. Policies are then deployed automatically through MDM, to customize the device to the user and the desired environment.
|
|
||||||
|
|
||||||
For the devices that are shipped in S mode, you can either keep them in S mode, use Windows Autopilot to switch them out of S mode during the first run process, or later using MDM, if desired.
|
|
||||||
|
|
||||||
## Keep line of business apps functioning with Desktop Bridge
|
|
||||||
|
|
||||||
[Desktop Bridge](/windows/uwp/porting/desktop-to-uwp-root) enables you to convert your line of business apps to a packaged app with UWP manifest. After testing and validating the apps, you can distribute them through an MDM solution like Microsoft Intune.
|
|
||||||
|
|
||||||
## Repackage Win32 apps into the MSIX format
|
|
||||||
|
|
||||||
The [MSIX Packaging Tool](/windows/application-management/msix-app-packaging-tool), available from the Microsoft Store, enables you to repackage existing Win32 applications to the MSIX format. You can run your desktop installers through the MSIX Packaging Tool interactively, and obtain an MSIX package that you can deploy through and MDM solution like Microsoft Intune. The MSIX Packaging Tool is another way to get your apps ready to run on Windows in S mode.
|
|
||||||
|
|
||||||
## Related links
|
|
||||||
|
|
||||||
- [Consumer applications for S mode](https://www.microsoft.com/windows/s-mode)
|
|
||||||
- [S mode devices](https://www.microsoft.com/windows/view-all-devices)
|
|
||||||
- [Windows Defender Application Control deployment guide](/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control-deployment-guide)
|
|
||||||
- [Microsoft Defender for Endpoint documentation](/microsoft-365/security/defender-endpoint/)
|
|
||||||
@ -1,85 +0,0 @@
|
|||||||
---
|
|
||||||
title: Switch to Windows 10 Pro/Enterprise from S mode
|
|
||||||
description: Overview of Windows 10 Pro/Enterprise in S mode. S mode switch options are also outlined in this document. Switching out of S mode is optional.
|
|
||||||
author: frankroj
|
|
||||||
ms.author: frankroj
|
|
||||||
manager: aaroncz
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
ms.service: windows-client
|
|
||||||
ms.topic: conceptual
|
|
||||||
ms.date: 11/23/2022
|
|
||||||
ms.subservice: itpro-deploy
|
|
||||||
---
|
|
||||||
|
|
||||||
# Switch to Windows 10 Pro or Enterprise from S mode
|
|
||||||
|
|
||||||
We recommend staying in S mode. However, in some limited scenarios, you might need to switch to Windows 10 Pro, Home, or Enterprise (not in S mode). You can switch devices running Windows 10, version 1709 or later.
|
|
||||||
|
|
||||||
Many other transformations are possible depending on which version and edition of Windows 10 you're starting with. Depending on the details, you might *switch* between S mode and the ordinary version or *convert* between different editions while staying in or out of S mode. The following quick reference table summarizes all of the switches or conversions that are supported by various means:
|
|
||||||
|
|
||||||
| If a device is running this version of Windows 10 | and this edition of Windows 10 | then you can switch or convert it to this edition of Windows 10 by these methods: | | |
|
|
||||||
|-------------|---------------------|-----------------------------------|-------------------------------|--------------------------------------------|
|
|
||||||
| | | **Store for Education** (switch/convert all devices in your tenant) | **Microsoft Store** (switch/convert one device at a time) | **Intune** (switch/convert any number of devices selected by admin) |
|
|
||||||
| **Windows 10, version 1709** | Pro in S mode | Pro EDU | Pro | Not by this method |
|
|
||||||
| | Pro | Pro EDU | Not by any method | Not by any method |
|
|
||||||
| | Home | Not by any method | Not by any method | Not by any method |
|
|
||||||
| | | | | |
|
|
||||||
| **Windows 10, version 1803** | Pro in S mode | Pro EDU in S mode | Pro | Not by this method |
|
|
||||||
| | Pro | Pro EDU | Not by any method | Not by any method |
|
|
||||||
| | Home in S mode | Not by any method | Home | Not by this method |
|
|
||||||
| | Home | Not by any method | Not by any method | Not by any method |
|
|
||||||
| | | | | |
|
|
||||||
| **Windows 10, version 1809** | Pro in S mode | Pro EDU in S mode | Pro | Pro |
|
|
||||||
| | Pro | Pro EDU | Not by any method | Not by any method |
|
|
||||||
| | Home in S mode | Not by any method | Home | Home |
|
|
||||||
| | Home | Not by any method | Not by any method | Not by any method |
|
|
||||||
|
|
||||||
Use the following information to switch to Windows 10 Pro through the Microsoft Store.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> While it's free to switch to Windows 10 Pro, it's not reversible. The only way to rollback this kind of switch is through a [bare-metal recovery (BMR)](/windows-hardware/manufacture/desktop/create-media-to-run-push-button-reset-features-s14) reset. This restores a Windows device to the factory state, even if the user needs to replace the hard drive or completely wipe the drive clean. If a device is switched out of S mode via the Microsoft Store, it will remain out of S mode even after the device is reset.
|
|
||||||
|
|
||||||
## Switch one device through the Microsoft Store
|
|
||||||
|
|
||||||
Use the following information to switch to Windows 10 Pro through the Microsoft Store or by navigating to **Settings** and then **Activation** on the device.
|
|
||||||
|
|
||||||
Note these differences affecting switching modes in various releases of Windows 10:
|
|
||||||
|
|
||||||
- In Windows 10, version 1709, you can switch devices one at a time from Windows 10 Pro in S mode to Windows 10 Pro by using the Microsoft Store or **Settings**. No other switches are possible.
|
|
||||||
|
|
||||||
- In Windows 10, version 1803, you can switch devices running any S mode edition to the equivalent non-S mode edition one at a time by using the Microsoft Store or **Settings**.
|
|
||||||
|
|
||||||
- Windows 10, version 1809, you can switch devices running any S mode edition to the equivalent non-S mode edition one at a time by using the Microsoft Store, **Settings**, or you can switch multiple devices in bulk by using Intune. You can also block users from switching devices themselves.
|
|
||||||
|
|
||||||
1. Sign into the Microsoft Store using your Microsoft account.
|
|
||||||
|
|
||||||
2. Search for "S mode".
|
|
||||||
|
|
||||||
3. In the offer, select **Buy**, **Get**, or **Learn more.**
|
|
||||||
|
|
||||||
You'll be prompted to save your files before the switch starts. Follow the prompts to switch to Windows 10 Pro.
|
|
||||||
|
|
||||||
## Switch one or more devices by using Microsoft Intune
|
|
||||||
|
|
||||||
Starting with Windows 10, version 1809, if you need to switch multiple devices in your environment from Windows 10 Pro in S mode to Windows 10 Pro, you can use Microsoft Intune or any other supported mobile device management software. You can configure devices to switch out of S mode during OOBE or post-OOBE. Switching out of S mode gives you flexibility to manage Windows 10 in S mode devices at any point during the device lifecycle.
|
|
||||||
|
|
||||||
1. Start Microsoft Intune.
|
|
||||||
|
|
||||||
2. Navigate to **Device configuration** > **Profiles** > **Windows 10 and later** > **Edition upgrade and mode switch**.
|
|
||||||
|
|
||||||
3. Follow the instructions to complete the switch.
|
|
||||||
|
|
||||||
## Block users from switching
|
|
||||||
|
|
||||||
You can control which devices or users can use the Microsoft Store to switch out of S mode in Windows 10. To set this policy, go to **Device configuration** > **Profiles** > **Windows 10 and later** > **Edition upgrade and mode switch in Microsoft Intune**, and then choose **Keep in S mode**.
|
|
||||||
|
|
||||||
## S mode management with CSPs
|
|
||||||
|
|
||||||
In addition to using Microsoft Intune or another modern device management tool to manage S mode, you can also use the [WindowsLicensing](/windows/client-management/mdm/windowslicensing-csp) configuration service provider (CSP). In Windows 10, version 1809, we added S mode functionality that lets you switch devices, block devices from switching, and check the status (whether a device is in S mode).
|
|
||||||
|
|
||||||
## Related articles
|
|
||||||
|
|
||||||
[FAQs](https://support.microsoft.com/help/4020089/windows-10-in-s-mode-faq)<br>
|
|
||||||
[Compare Windows 10 editions](https://www.microsoft.com/WindowsForBusiness/Compare)<BR>
|
|
||||||
[Windows 10 Pro Education](/education/windows/test-windows10s-for-edu)<BR>
|
|
||||||
[Introduction to Microsoft Intune in the Azure portal](/intune/what-is-intune)
|
|
||||||
@ -100,8 +100,6 @@
|
|||||||
href: deployment/create-code-signing-cert-for-wdac.md
|
href: deployment/create-code-signing-cert-for-wdac.md
|
||||||
- name: Disable WDAC policies
|
- name: Disable WDAC policies
|
||||||
href: deployment/disable-wdac-policies.md
|
href: deployment/disable-wdac-policies.md
|
||||||
- name: LOB Win32 Apps on S Mode
|
|
||||||
href: deployment/LOB-win32-apps-on-s.md
|
|
||||||
- name: WDAC operational guide
|
- name: WDAC operational guide
|
||||||
href: operations/wdac-operational-guide.md
|
href: operations/wdac-operational-guide.md
|
||||||
items:
|
items:
|
||||||
|
|||||||
@ -1,252 +0,0 @@
|
|||||||
---
|
|
||||||
title: Allow LOB Win32 apps on Intune-managed S Mode devices
|
|
||||||
description: Using Windows Defender Application Control (WDAC) supplemental policies, you can expand the S Mode base policy on your Intune-managed devices.
|
|
||||||
ms.localizationpriority: medium
|
|
||||||
ms.date: 04/05/2023
|
|
||||||
ms.topic: how-to
|
|
||||||
---
|
|
||||||
|
|
||||||
# Allow line-of-business Win32 apps on Intune-managed S Mode devices
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Some capabilities of Windows Defender Application Control (WDAC) are only available on specific Windows versions. For more information, see [Windows Defender Application Control feature availability](../feature-availability.md).
|
|
||||||
|
|
||||||
You can use Microsoft Intune to deploy and run critical Win32 applications, and Windows components that are normally blocked in S mode, on your Intune-managed Windows 10 in S mode devices. For example, PowerShell.exe.
|
|
||||||
|
|
||||||
With Intune, you can configure managed S mode devices using a Windows Defender Application Control (WDAC) supplemental policy that expands the S mode base policy to authorize the apps your organization uses. This feature changes the S mode security posture from "Microsoft has verified every app" to "Microsoft or your organization has verified every app".
|
|
||||||
|
|
||||||
For an overview and brief demo of this feature, see this video:
|
|
||||||
|
|
||||||
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4mlcp]
|
|
||||||
|
|
||||||
## Policy authorization process
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The general steps for expanding the S mode base policy on your Intune-managed Windows 10 in S mode devices are to generate a supplemental policy, sign that policy, upload the signed policy to Intune, and assign it to user or device groups. Because you need access to PowerShell cmdlets to generate your supplemental policy, you should create and manage your policies on a non-S mode device. Once the policy has been uploaded to Intune, before deploying the policy more broadly, assign it to a single test Windows 10 in S mode device to verify expected functioning.
|
|
||||||
|
|
||||||
1. Generate a supplemental policy with WDAC tooling.
|
|
||||||
|
|
||||||
This policy expands the S mode base policy to authorize more applications. Anything authorized by either the S mode base policy or your supplemental policy is allowed to run. Your supplemental policies can specify filepath rules, trusted publishers, and more.
|
|
||||||
|
|
||||||
For more information on creating supplemental policies, see [Deploy multiple WDAC policies](../design/deploy-multiple-wdac-policies.md). For more information on the right type of rules to create for your policy, see [Deploy WDAC policy rules and file rules](../design/select-types-of-rules-to-create.md).
|
|
||||||
|
|
||||||
The following instructions are a basic set for creating an S mode supplemental policy:
|
|
||||||
|
|
||||||
- Create a new base policy using [New-CIPolicy](/powershell/module/configci/new-cipolicy?view=win10-ps&preserve-view=true).
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
New-CIPolicy -MultiplePolicyFormat -ScanPath <path> -UserPEs -FilePath "<path>\SupplementalPolicy.xml" -Level FilePublisher -Fallback SignedVersion,Publisher,Hash
|
|
||||||
```
|
|
||||||
|
|
||||||
- Change it to a supplemental policy using [Set-CIPolicyIdInfo](/powershell/module/configci/set-cipolicyidinfo?view=win10-ps&preserve-view=true).
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Set-CIPolicyIdInfo -SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784 -FilePath "<path>\SupplementalPolicy.xml"
|
|
||||||
```
|
|
||||||
|
|
||||||
For policies that supplement the S mode base policy, use `-SupplementsBasePolicyID 5951A96A-E0B5-4D3D-8FB8-3E5B61030784`. This ID is the S mode policy ID.
|
|
||||||
|
|
||||||
- Put the policy in enforce mode using [Set-RuleOption](/powershell/module/configci/set-ruleoption?view=win10-ps&preserve-view=true).
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Set-RuleOption -FilePath "<path>\SupplementalPolicy.xml>" -Option 3 -Delete
|
|
||||||
```
|
|
||||||
|
|
||||||
This command deletes the 'audit mode' qualifier.
|
|
||||||
|
|
||||||
- Since you're signing your policy, you must authorize the signing certificate you use to sign the policy. Optionally, also authorize one or more extra signers that can be used to sign updates to the policy in the future. The next step in the overall process, **Sign the policy**, describes it in more detail.
|
|
||||||
|
|
||||||
To add the signing certificate to the WDAC policy, use [Add-SignerRule](/powershell/module/configci/add-signerrule?view=win10-ps&preserve-view=true).
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Add-SignerRule -FilePath <policypath> -CertificatePath <certpath> -User -Update
|
|
||||||
```
|
|
||||||
|
|
||||||
- Convert to `.bin` using [ConvertFrom-CIPolicy](/powershell/module/configci/convertfrom-cipolicy?view=win10-ps&preserve-view=true).
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
ConvertFrom-CIPolicy -XmlFilePath "<path>\SupplementalPolicy.xml" -BinaryFilePath "<path>\SupplementalPolicy.bin>
|
|
||||||
```
|
|
||||||
|
|
||||||
2. Sign the policy.
|
|
||||||
|
|
||||||
Supplemental S mode policies must be digitally signed. To sign your policy, use your organization's custom Public Key Infrastructure (PKI). For more information on signing using an internal CA, see [Create a code signing cert for WDAC](create-code-signing-cert-for-wdac.md).
|
|
||||||
|
|
||||||
> [!TIP]
|
|
||||||
> For more information, see [Azure Code Signing, democratizing trust for developers and consumers](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/azure-code-signing-democratizing-trust-for-developers-and/ba-p/3604669).
|
|
||||||
|
|
||||||
After you've signed it, rename your policy to `{PolicyID}.p7b`. Get the **PolicyID** from the supplemental policy XML.
|
|
||||||
|
|
||||||
3. Deploy the signed supplemental policy using Microsoft Intune.
|
|
||||||
|
|
||||||
Go to the Microsoft Intune portal, go to the Client apps page, and select **S mode supplemental policies**. Upload the signed policy to Intune and assign it to user or device groups. Intune generates authorization tokens for the tenant and specific devices. Intune then deploys the corresponding authorization token and supplemental policy to each device in the assigned group. Together, these tokens and policies expand the S mode base policy on the device.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> When you update your supplemental policy, make sure that the new version number is strictly greater than the previous one. Intune doesn't allow using the same version number. For more information on setting the version number, see [Set-CIPolicyVersion](/powershell/module/configci/set-cipolicyversion?view=win10-ps&preserve-view=true).
|
|
||||||
|
|
||||||
## Standard process for deploying apps through Intune
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For more information on the existing procedure of packaging signed catalogs and app deployment, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
|
|
||||||
|
|
||||||
## Optional: Process for deploying apps using catalogs
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Your supplemental policy can be used to significantly relax the S mode base policy, but there are security trade-offs you must consider in doing so. For example, you can use a signer rule to trust an external signer, but that authorizes all apps signed by that certificate, which may include apps you don't want to allow as well.
|
|
||||||
|
|
||||||
Instead of authorizing signers external to your organization, Intune has functionality to make it easier to authorize existing applications by using signed catalogs. This feature doesn't require repackaging or access to the source code. It works for apps that may be unsigned or even signed apps when you don't want to trust all apps that may share the same signing certificate.
|
|
||||||
|
|
||||||
The basic process is to generate a catalog file for each app using Package Inspector, then sign the catalog files using a custom PKI. To authorize the catalog signing certificate in the supplemental policy, use the **Add-SignerRule** PowerShell cmdlet as shown earlier in step 1 of the [Policy authorization process](#policy-authorization-process). After that, use the [Standard process for deploying apps through Intune](#standard-process-for-deploying-apps-through-intune) outlined earlier. For more information on generating catalogs, see [Deploy catalog files to support WDAC](deploy-catalog-files-to-support-wdac.md).
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Every time an app updates, you need to deploy an updated catalog. Try to avoid using catalog files for applications that auto-update, and direct users not to update applications on their own.
|
|
||||||
|
|
||||||
## Sample policy
|
|
||||||
|
|
||||||
The following policy is a sample that allows kernel debuggers, PowerShell ISE, and Registry Editor. It also demonstrates how to specify your organization's code signing and policy signing certificates.
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<?xml version="1.0" encoding="utf-8"?>
|
|
||||||
<SiPolicy xmlns="urn:schemas-microsoft-com:sipolicy" PolicyType="Supplemental Policy">
|
|
||||||
<VersionEx>10.0.0.0</VersionEx>
|
|
||||||
<PlatformID>{2E07F7E4-194C-4D20-B7C9-6F44A6C5A234}</PlatformID>
|
|
||||||
<!--Standard S mode GUID-->
|
|
||||||
<BasePolicyID>{5951A96A-E0B5-4D3D-8FB8-3E5B61030784}</BasePolicyID>
|
|
||||||
<!--Unique policy GUID-->
|
|
||||||
<PolicyID>{52671094-ACC6-43CF-AAF1-096DC69C1345}</PolicyID>
|
|
||||||
<!--EKUS-->
|
|
||||||
<EKUs />
|
|
||||||
<!--File Rules-->
|
|
||||||
<FileRules>
|
|
||||||
<!--Allow kernel debuggers-->
|
|
||||||
<Allow ID="ID_ALLOW_CBD_0" FriendlyName="cdb.exe" FileName="CDB.Exe" />
|
|
||||||
<Allow ID="ID_ALLOW_KD_0" FriendlyName="kd.exe" FileName="kd.Exe" />
|
|
||||||
<Allow ID="ID_ALLOW_WINDBG_0" FriendlyName="windbg.exe" FileName="windbg.Exe" />
|
|
||||||
<Allow ID="ID_ALLOW_MSBUILD_0" FriendlyName="MSBuild.exe" FileName="MSBuild.Exe" />
|
|
||||||
<Allow ID="ID_ALLOW_NTSD_0" FriendlyName="ntsd.exe" FileName="ntsd.Exe" />
|
|
||||||
<!--Allow PowerShell ISE and Registry Editor-->
|
|
||||||
<Allow ID="ID_ALLOW_POWERSHELLISE_0" FriendlyName="powershell_ise.exe" FileName="powershell_ise.exe" />
|
|
||||||
<Allow ID="ID_ALLOW_REGEDIT_0" FriendlyName="regedit.exe" FileName="regedit.exe" />
|
|
||||||
</FileRules>
|
|
||||||
<!--Signers-->
|
|
||||||
<Signers>
|
|
||||||
<!--info of the certificate you will use to do any code/catalog signing-->
|
|
||||||
<Signer ID="EXAMPLE_ID_SIGNER_CODE" Name="Example Code Signing Certificate Friendly Name">
|
|
||||||
<CertRoot Type="TBS" Value="<value>" />
|
|
||||||
</Signer>
|
|
||||||
|
|
||||||
<!--info of the certificate you will use to sign your policy-->
|
|
||||||
<Signer ID="EXAMPLE_ID_SIGNER_POLICY" Name="Example Policy Signing Certificate Friendly Name">
|
|
||||||
<CertRoot Type="TBS" Value="<value>" />
|
|
||||||
</Signer>
|
|
||||||
</Signers>
|
|
||||||
<!--Driver Signing Scenarios-->
|
|
||||||
<SigningScenarios>
|
|
||||||
<SigningScenario Value="131" ID="ID_SIGNINGSCENARIO_KMCI" FriendlyName="Example Name">
|
|
||||||
<ProductSigners />
|
|
||||||
</SigningScenario>
|
|
||||||
<SigningScenario Value="12" ID="ID_SIGNINGSCENARIO_UMCI" FriendlyName="Example Name">
|
|
||||||
<ProductSigners>
|
|
||||||
<AllowedSigners>
|
|
||||||
<AllowedSigner SignerId="EXAMPLE_ID_SIGNER_CODE" />
|
|
||||||
</AllowedSigners>
|
|
||||||
<FileRulesRef>
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_CBD_0" />
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_KD_0" />
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_WINDBG_0" />
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_MSBUILD_0" />
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_NTSD_0" />
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_POWERSHELLISE_0" />
|
|
||||||
<FileRuleRef RuleID="ID_ALLOW_REGEDIT_0" />
|
|
||||||
</FileRulesRef>
|
|
||||||
</ProductSigners>
|
|
||||||
</SigningScenario>
|
|
||||||
</SigningScenarios>
|
|
||||||
<!--Specify one or more certificates that can be used to sign updated policy-->
|
|
||||||
<UpdatePolicySigners>
|
|
||||||
<UpdatePolicySigner SignerId="EXAMPLE_ID_SIGNER_POLICY" />
|
|
||||||
</UpdatePolicySigners>
|
|
||||||
<!--Specify one or more codesigning certificates to trust-->
|
|
||||||
<CiSigners>
|
|
||||||
<CiSigner SignerId="EXAMPLE_ID_SIGNER_CODE" />
|
|
||||||
</CiSigners>
|
|
||||||
<!-- example remove core isolation a.k.a. Hypervisor Enforced Code Integrity (HVCI) options, consider enabling if your system supports it-->
|
|
||||||
<HvciOptions>0</HvciOptions>
|
|
||||||
<Settings>
|
|
||||||
<Setting Provider="PolicyInfo" Key="Information" ValueName="Name">
|
|
||||||
<Value>
|
|
||||||
<String>Example Policy Name</String>
|
|
||||||
</Value>
|
|
||||||
</Setting>
|
|
||||||
<Setting Provider="PolicyInfo" Key="Information" ValueName="Id">
|
|
||||||
<Value>
|
|
||||||
<String>Example-Policy-10.0.0.0</String>
|
|
||||||
</Value>
|
|
||||||
</Setting>
|
|
||||||
</Settings>
|
|
||||||
</SiPolicy>
|
|
||||||
```
|
|
||||||
|
|
||||||
## Policy removal
|
|
||||||
|
|
||||||
In order to revert users to an unmodified S mode policy, remove a user or users from the targeted Intune group that received the policy. This action triggers a removal of both the policy and the authorization token from the device.
|
|
||||||
|
|
||||||
You can also delete a supplemental policy through Intune.
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<?xml version="1.0" encoding="utf-8"?>
|
|
||||||
<SiPolicy xmlns="urn:schemas-microsoft-com:sipolicy" PolicyType="Supplemental Policy">
|
|
||||||
<VersionEx>10.0.0.1</VersionEx>
|
|
||||||
<PlatformID>{2E07F7E4-194C-4D20-B7C9-6F44A6C5A234}</PlatformID>
|
|
||||||
<BasePolicyID>{5951A96A-E0B5-4D3D-8FB8-3E5B61030784}</BasePolicyID>
|
|
||||||
<PolicyID>{52671094-ACC6-43CF-AAF1-096DC69C1345}</PolicyID>
|
|
||||||
<Rules>
|
|
||||||
</Rules>
|
|
||||||
<!--EKUS-->
|
|
||||||
<EKUs />
|
|
||||||
<!--File Rules-->
|
|
||||||
|
|
||||||
<!--Signers-->
|
|
||||||
<Signers>
|
|
||||||
<!--info of the certificate you will use to sign your policy-->
|
|
||||||
<Signer ID="EXAMPLE_ID_SIGNER_POLICY" Name="Example Policy Signing Certificate Friendly Name">
|
|
||||||
<CertRoot Type="TBS" Value="<value>" />
|
|
||||||
</Signer>
|
|
||||||
</Signers>
|
|
||||||
<!--Driver Signing Scenarios-->
|
|
||||||
<SigningScenarios>
|
|
||||||
<SigningScenario Value="131" ID="ID_SIGNINGSCENARIO_KMCI" FriendlyName="KMCI">
|
|
||||||
<ProductSigners>
|
|
||||||
</ProductSigners>
|
|
||||||
</SigningScenario>
|
|
||||||
<SigningScenario Value="12" ID="ID_SIGNINGSCENARIO_UMCI" FriendlyName="UMCI">
|
|
||||||
<ProductSigners>
|
|
||||||
</ProductSigners>
|
|
||||||
</SigningScenario>
|
|
||||||
</SigningScenarios>
|
|
||||||
<UpdatePolicySigners>
|
|
||||||
<UpdatePolicySigner SignerId="EXAMPLE_ID_SIGNER_POLICY" />
|
|
||||||
</UpdatePolicySigners>
|
|
||||||
<!-- example remove core isolation a.k.a. Hypervisor Enforced Code Integrity (HVCI) options, consider enabling if your system is supported-->
|
|
||||||
<HvciOptions>0</HvciOptions>
|
|
||||||
<Settings>
|
|
||||||
<Setting Provider="PolicyInfo" Key="Information" ValueName="Name">
|
|
||||||
<Value>
|
|
||||||
<String>Example Policy Name - Empty</String>
|
|
||||||
</Value>
|
|
||||||
</Setting>
|
|
||||||
<Setting Provider="PolicyInfo" Key="Information" ValueName="Id">
|
|
||||||
<Value>
|
|
||||||
<String>Example-Policy-Empty-10.0.0.1</String>
|
|
||||||
</Value>
|
|
||||||
</Setting>
|
|
||||||
</Settings>
|
|
||||||
</SiPolicy>
|
|
||||||
```
|
|
||||||
|
|
||||||
## Errata
|
|
||||||
|
|
||||||
If a Windows 10 in S mode device with a policy authorization token and supplemental policy is rolled back from the 1909 update to the 1903 build, it will not revert to locked-down S mode until the next policy refresh. To achieve an immediate change to a locked-down S mode state, IT Pros should delete any tokens in %SystemRoot%\System32\CI\Tokens\Active.
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB |
@ -8,7 +8,7 @@ metadata:
|
|||||||
author: vinaypamnani-msft
|
author: vinaypamnani-msft
|
||||||
ms.author: vinpa
|
ms.author: vinpa
|
||||||
manager: aaroncz
|
manager: aaroncz
|
||||||
ms.date: 04/05/2023
|
ms.date: 08/14/2024
|
||||||
# linkListType: overview | how-to-guide | tutorial | video
|
# linkListType: overview | how-to-guide | tutorial | video
|
||||||
landingContent:
|
landingContent:
|
||||||
# Cards and links should be based on top customer tasks or top subjects
|
# Cards and links should be based on top customer tasks or top subjects
|
||||||
@ -39,8 +39,6 @@ landingContent:
|
|||||||
url: design/microsoft-recommended-driver-block-rules.md
|
url: design/microsoft-recommended-driver-block-rules.md
|
||||||
- text: Example WDAC policies
|
- text: Example WDAC policies
|
||||||
url: design/example-wdac-base-policies.md
|
url: design/example-wdac-base-policies.md
|
||||||
- text: LOB Win32 apps on S Mode
|
|
||||||
url: deployment/LOB-win32-apps-on-s.md
|
|
||||||
- text: Managing multiple policies
|
- text: Managing multiple policies
|
||||||
url: design/deploy-multiple-wdac-policies.md
|
url: design/deploy-multiple-wdac-policies.md
|
||||||
- linkListType: how-to-guide
|
- linkListType: how-to-guide
|
||||||
@ -51,7 +49,7 @@ landingContent:
|
|||||||
url: design/create-wdac-policy-for-fully-managed-devices.md
|
url: design/create-wdac-policy-for-fully-managed-devices.md
|
||||||
- text: Create a WDAC policy for a fixed-workload
|
- text: Create a WDAC policy for a fixed-workload
|
||||||
url: design/create-wdac-policy-using-reference-computer.md
|
url: design/create-wdac-policy-using-reference-computer.md
|
||||||
- text: Create a WDAC deny list policy
|
- text: Create a WDAC blocklist policy
|
||||||
url: design/create-wdac-deny-policy.md
|
url: design/create-wdac-deny-policy.md
|
||||||
- text: Deploying catalog files for WDAC management
|
- text: Deploying catalog files for WDAC management
|
||||||
url: deployment/deploy-catalog-files-to-support-wdac.md
|
url: deployment/deploy-catalog-files-to-support-wdac.md
|
||||||
@ -82,7 +80,7 @@ landingContent:
|
|||||||
url: design/manage-packaged-apps-with-wdac.md
|
url: design/manage-packaged-apps-with-wdac.md
|
||||||
- text: Allow com object registration
|
- text: Allow com object registration
|
||||||
url: design/allow-com-object-registration-in-wdac-policy.md
|
url: design/allow-com-object-registration-in-wdac-policy.md
|
||||||
- text: Manage plug-ins, add-ins and modules
|
- text: Manage plug-ins, add-ins, and modules
|
||||||
url: design/use-wdac-policy-to-control-specific-plug-ins-add-ins-and-modules.md
|
url: design/use-wdac-policy-to-control-specific-plug-ins-add-ins-and-modules.md
|
||||||
# Card
|
# Card
|
||||||
- title: Learn how to deploy WDAC Policies
|
- title: Learn how to deploy WDAC Policies
|
||||||
|
|||||||
@ -60,7 +60,7 @@ To upgrade directly to Windows 11, eligible Windows 10 devices must meet both of
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
>
|
>
|
||||||
> - S mode is only supported on the Home edition of Windows 11.
|
> - S mode is only supported on the Home edition of Windows 11.
|
||||||
> - If you're running a different edition of Windows in S mode, before upgrading to Windows 11, first [switch out of S mode](/windows/deployment/windows-10-pro-in-s-mode).
|
> - If you're running a different edition of Windows in S mode, before upgrading to Windows 11, first [switch out of S mode](/previous-versions/windows/it-pro/windows-10/deployment/s-mode/switch-edition-from-s-mode).
|
||||||
> - To switch a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you can't switch back to S mode later.
|
> - To switch a device out of Windows 10 in S mode also requires internet connectivity. If you switch out of S mode, you can't switch back to S mode later.
|
||||||
|
|
||||||
## Feature-specific requirements
|
## Feature-specific requirements
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user