mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-11 12:57:23 +00:00
Merge branch 'main' into vp-csp-2504
This commit is contained in:
Vinay Pamnani
GitHub
commit
37a43510ee
@ -45,7 +45,7 @@ Hide only the Bluetooth page, which has the URI `ms-settings:bluetooth`:
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune/CSP**](#tab/intune)
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune**](#tab/intune)
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
||||
|
||||
@ -55,7 +55,9 @@ Hide only the Bluetooth page, which has the URI `ms-settings:bluetooth`:
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
||||
|
||||
Alternatively, you can configure devices using a [custom policy][INT-1] with the [Policy CSP][CSP-1].
|
||||
#### [:::image type="icon" source="../images/icons/csp.svg"::: **CSP**](#tab/csp)
|
||||
|
||||
You can configure devices using the [Policy CSP][CSP-1].
|
||||
|
||||
| Setting |
|
||||
|--|
|
||||
|
||||
@ -150,7 +150,7 @@ To learn how to configure the Shell Launcher XML file, see [Create a Shell Launc
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune**](#tab/intune)
|
||||
|
||||
You can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
|
||||
|
||||
@ -159,12 +159,19 @@ You can configure devices using a [custom policy][MEM-1] with the [AssignedAcces
|
||||
|
||||
Assign the policy to a group that contains as members the devices that you want to configure.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/csp.svg"::: **CSP**](#tab/csp)
|
||||
|
||||
You can configure devices using the [AssignedAccess CSP][WIN-3].
|
||||
|
||||
- **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
|
||||
- **Value:** content of the XML configuration file
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
||||
|
||||
You can configure Shell Launcher by creating a provisioning package and then applying the provisioning package during image deployment time or at runtime:
|
||||
|
||||
- If you're creating an installation media with settings for Shell Launcher included in the image, or you're applying a provisioning package during setup, you must enable Shell Launcher on the installation media with DISM for a provisioning package to successfully apply
|
||||
- If exectuing the provisioning package at runtime, ensure to [enable Shell Launcher](#enable-shell-launcher) before applying the provisioning package
|
||||
- If executing the provisioning package at runtime, ensure to [enable Shell Launcher](#enable-shell-launcher) before applying the provisioning package
|
||||
|
||||
[!INCLUDE [provisioning-package-1](../../../includes/configure/provisioning-package-1.md)]
|
||||
|
||||
@ -233,7 +240,11 @@ Depending on your configuration, you can have a user to automatically sign in to
|
||||
|
||||
Here are the options to remove Shell Launcher, select the method that best fits your needs:
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune**](#tab/intune)
|
||||
|
||||
Unassign or delete the policy that contains the configuration.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/csp.svg"::: **CSP**](#tab/csp)
|
||||
|
||||
Unassign or delete the policy that contains the configuration.
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ The examples can be modified to fit your specific requirements. For example, you
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune**](#tab/intune)
|
||||
|
||||
> [!TIP]
|
||||
> Use the following Graph call to automatically create a custom policy in your Microsoft Intune tenant without assignments nor scope tags.
|
||||
@ -35,13 +35,18 @@ The examples can be modified to fit your specific requirements. For example, you
|
||||
|
||||
Assign the policy to a group that contains as members the devices that you want to configure.
|
||||
|
||||
Alternatively, you can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
|
||||
|
||||
- **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
|
||||
- **Value:**
|
||||
|
||||
[!INCLUDE [quickstart-xml](includes/quickstart-xml.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/csp.svg"::: **CSP**](#tab/csp)
|
||||
|
||||
You can configure devices using the [AssignedAccess CSP][WIN-3].
|
||||
|
||||
| Setting |
|
||||
|--|
|
||||
|- **OMA-URI:** `./Vendor/MSFT/AssignedAccess/ShellLauncher` <br>- **Data type:** string<br>- **Value:** content of the following XML |
|
||||
|
||||
[!INCLUDE [quickstart-xml](includes/quickstart-xml.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/powershell.svg"::: **PowerShell**](#tab/ps)
|
||||
|
||||
[!INCLUDE [powershell-wmi-bridge-1](../../../includes/configure/powershell-wmi-bridge-1.md)]
|
||||
|
||||
@ -17,7 +17,7 @@ You can use configuration service provider (CSP) or group policy (GPO) settings
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune/CSP**](#tab/intune)
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune**](#tab/intune)
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
||||
|
||||
@ -27,7 +27,10 @@ You can use configuration service provider (CSP) or group policy (GPO) settings
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
||||
|
||||
Alternatively, you can configure devices using a [custom policy][INT-1] with the [Policy CSP][CSP-1].
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/csp.svg"::: **CSP**](#tab/csp-11)
|
||||
|
||||
You can configure devices using the [Policy CSP][CSP-1].
|
||||
|
||||
| Setting |
|
||||
|--|
|
||||
|
||||
@ -11,8 +11,10 @@ items:
|
||||
href: background/index.md
|
||||
- name: Windows spotlight
|
||||
href: windows-spotlight/index.md
|
||||
- name: Settings page visibility
|
||||
href: settings/page-visibility.md
|
||||
- name: Settings
|
||||
items:
|
||||
- name: Page visibility
|
||||
href: settings/page-visibility.md
|
||||
- name: Microsoft Store
|
||||
href: store/toc.yml
|
||||
- name: Quick machine recovery
|
||||
|
||||
@ -85,8 +85,6 @@ In Windows client Enterprise, Professional, and Education editions, Delivery Opt
|
||||
|
||||
At Microsoft, to help ensure that ongoing deployments weren't affecting our network and taking away bandwidth for other services, Microsoft IT used a couple of different bandwidth management strategies. Delivery Optimization, peer-to-peer caching enabled through Group Policy, was piloted and then deployed to all managed devices using Group Policy. Based on recommendations from the Delivery Optimization team, we used the "group" configuration to limit sharing of content to only the devices that are members of the same Active Directory domain. The content is cached for 24 hours. More than 76 percent of content came from peer devices versus the Internet.
|
||||
|
||||
For more information, check out the [Adopting Windows as a Service at Microsoft](https://www.microsoft.com/itshowcase/Article/Content/851/Adopting-Windows-as-a-service-at-Microsoft) technical case study.
|
||||
|
||||
## Using a proxy with Delivery Optimization
|
||||
|
||||
If a proxy is being used in your environment, see [Using a proxy with Delivery Optimization](delivery-optimization-proxy.md) to understand the proxy settings needed to properly using Delivery Optimization.
|
||||
|
||||
@ -20,9 +20,9 @@ groups:
|
||||
title: Windows versions
|
||||
prompt: "Select the Windows version you want to learn about:"
|
||||
pivots:
|
||||
- id: windows-insider
|
||||
title: Windows Insider
|
||||
- id: windows-11
|
||||
title: Windows 11
|
||||
- id: windows-10
|
||||
title: Windows 10
|
||||
title: Windows 10
|
||||
- id: windows-insider
|
||||
title: Windows Insider
|
||||
@ -7,9 +7,6 @@ ms.date: 04/07/2025
|
||||
|
||||
# Windows Firewall dynamic keywords
|
||||
|
||||
> [!IMPORTANT]
|
||||
>This article describes features or settings that are in preview. The content is subject to change and may have dependencies on other features or services in preview.
|
||||
|
||||
Windows Firewall includes a functionality called *dynamic keywords*, which simplifies the configuration and management of Windows Firewall.
|
||||
|
||||
With dynamic keywords, you can define a set of IP address ranges, fully qualified domain names (FQDNs), and **autoresolution** options, to which one or more Firewall rules can refer.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Deprecated features in the Windows client
|
||||
description: Review the list of features that Microsoft is no longer actively developing in Windows 10 and Windows 11.
|
||||
ms.date: 04/24/2025
|
||||
ms.date: 05/02/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-fundamentals
|
||||
ms.localizationpriority: medium
|
||||
@ -48,10 +48,10 @@ The features in this article are no longer being actively developed, and might b
|
||||
| Feature | Details and mitigation | Deprecation announced |
|
||||
|---|---|---|
|
||||
| Maps app <!--9853653--> | Maps app is deprecated. It will be removed from the Microsoft Store by July 2025 and will no longer be supported. For more information, see [Resources for deprecated features](deprecated-features-resources.md#maps-app). | April 2025 |
|
||||
| VBS enclaves for Windows 11, version 23H2 and earlier <!--9693593-->| [VBS enclaves](/windows/win32/trusted-execution/vbs-enclaves) are being deprecated on Windows 11, version 23H2 and earlier versions of Windows. Support for VBS enclaves will continue for Windows 11, version 24H2 and later. </br> </br> VBS enclaves are being [deprecated on Windows Server 2022](/windows-server/get-started/removed-deprecated-features-windows-server) and earlier versions of Windows Server. Support for VBS enclaves will continue for Windows Server 2025 and later. | April 2025 |
|
||||
| VBS enclaves for Windows 11, version 23H2 and earlier <!--9693593-->| [VBS enclaves](/windows/win32/trusted-execution/vbs-enclaves) are being deprecated on Windows 11, version 23H2 and earlier versions of Windows. Support for VBS enclaves will continue for Windows 11, version 24H2 and later. </br> </br> **[Update May 2025]** Existing enclaves signed with the EKU 1.3.6.1.4.1.311.76.57.1.15 will continue to be supported for all Windows 11, version 23H2 and earlier versions of Windows, so long as no changes are made to the enclave that requires a re-sign of it. If a re-sign of the enclave occurs, the new EKU will be used to re-sign and the enclave will only be supported on Windows 11, version 24H2 and later. Existing enclaves signed with EKU 1.3.6.1.4.1.311.76.57.1.15 will continue to function without disruption on the following operating systems until a re-sign is needed: </br> <ul><li>Windows 10, version 22H2 </li> <li> Windows 11, version 22H2 </li><li> Windows 11, version 23H2 </li><li>Windows 11, version 24H2 and later</li></ul>| April 2025 |
|
||||
| Windows UWP Map control and Windows Maps platform APIs <!--9853556--> | The [Windows UWP Map control](/uwp/api/windows.ui.xaml.controls.maps) and [Windows Maps platform APIs](/uwp/api/windows.services.maps) within Windows have been deprecated as of April 8, 2025. The Maps UWP Control and Maps platform support within Windows will continue to function but will not be updated. For more information, see [Resources for deprecated features](deprecated-features-resources.md#windows-uwp-map-control-and-windows-maps-platform-apis). | April 8, 2025 |
|
||||
| Line printer daemon (LPR/LPD) <!--9787121--> | Deprecation reminder: [The line printer daemon protocol (LPR/LPD) was deprecated](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing) starting in Windows Server 2012. As removal of the line printer daemon protocol nears, we'd like to remind customers to ensure their environments are prepared for removal. When these features are eventually removed, clients that print to a server using this protocol, such as UNIX clients, will not be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the [Windows Standard Port Monitor](/troubleshoot/windows-server/printing/standard-port-monitor-for-tcpip). | [Original announcement: Windows Server 2012](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing) </br> <br> Courtesy reminder: February 2025 |
|
||||
| Location History <!--9798092--> | We are deprecating and removing the Location History feature, an [API](/uwp/api/windows.devices.geolocation.geolocator.getgeopositionhistoryasync) that allowed Cortana to access 24 hours of device history when location was enabled. With the removal of the Location History feature, location data will no longer be saved locally and the corresponding settings will also be removed from the **Privacy & Security** > **Location** page in **Settings**. | February 2025 |
|
||||
| Line printer daemon (LPR/LPD) <!--9787121--> | Deprecation reminder: [The line printer daemon protocol (LPR/LPD) was deprecated](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing) starting in Windows Server 2012. As removal of the line printer daemon protocol nears, we'd like to remind customers to ensure their environments are prepared for removal. When these features are eventually removed, clients that print to a server using this protocol, such as UNIX clients, won't be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the [Windows Standard Port Monitor](/troubleshoot/windows-server/printing/standard-port-monitor-for-tcpip). | [Original announcement: Windows Server 2012](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing) </br> <br> Courtesy reminder: February 2025 |
|
||||
| Location History <!--9798092--> | We're deprecating and removing the Location History feature, an [API](/uwp/api/windows.devices.geolocation.geolocator.getgeopositionhistoryasync) that allowed Cortana to access 24 hours of device history when location was enabled. With the removal of the Location History feature, location data will no longer be saved locally and the corresponding settings will also be removed from the **Privacy & Security** > **Location** page in **Settings**. | February 2025 |
|
||||
| Suggested actions <!--9614241-->| Suggested actions that appear when you copy a phone number or future date in Windows 11 are deprecated and will be removed in a future Windows 11 update. | December 2024 |
|
||||
| Legacy DRM services <!--9183757-->| Legacy DRM services, used by either Windows Media Player, Silverlight clients, Windows 7, or Windows 8 clients are deprecated. The following functionality won't work when these services are fully retired: </br><ul><li>Playback of protected content in the legacy Windows Media Player on Windows 7</li><li> Playback of protected content in a Silverlight client and Windows 8 clients</li><li> In-home streaming playback from a Silverlight client or Windows 8 client to an Xbox 360</li><li>Playback of protected content ripped from a personal CD on Windows 7 clients using Windows Media Player </li></ul> | September 2024 |
|
||||
| Paint 3D <!--8995017--> | Paint 3D is deprecated and will be removed from the Microsoft Store on November 4, 2024. To view and edit 2D images, you can use [Paint](https://apps.microsoft.com/detail/9pcfs5b6t72h) or [Photos](https://apps.microsoft.com/detail/9wzdncrfjbh4). For viewing 3D content, you can use [3D Viewer](https://apps.microsoft.com/detail/9nblggh42ths). For more information, see [Resources for deprecated features](deprecated-features-resources.md#paint-3d). | August 2024 |
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user