mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'main' into ADO-8098862
This commit is contained in:
Thomas Raya
GitHub
commit
dac94a7728
@ -6,16 +6,15 @@ manager: aaroncz
|
||||
ms.prod: windows-client
|
||||
author: lizgt2000
|
||||
ms.author: lizlong
|
||||
ms.topic: article
|
||||
ms.topic: whats-new
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/28/2017
|
||||
ms.date: 08/18/2023
|
||||
ms.technology: itpro-configure
|
||||
---
|
||||
|
||||
# Changes to Group Policy settings for Windows 10 Start
|
||||
|
||||
|
||||
**Applies to**
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
|
||||
@ -33,7 +32,7 @@ These policy settings are available in **Administrative Templates\\Start Menu an
|
||||
|Don't display or track items in Jump Lists from remote locations|When this policy is applied, only items local on the computer are shown in Jump Lists.|
|
||||
|Don't keep history of recently opened documents|Documents that the user opens aren't tracked during the session.|
|
||||
|Prevent changes to Taskbar and Start Menu Settings|In Windows 10, this policy disables all of the settings in **Settings** > **Personalization** > **Start** and the options in dialog available via right-click Taskbar > **Properties**|
|
||||
|Prevent users from customizing their Start Screen|Use this policy in conjunction with a [customized Start layout](windows-10-start-layout-options-and-policies.md) to prevent users from changing it|
|
||||
|Prevent users from customizing their Start Screen|Use this policy with a [customized Start layout](windows-10-start-layout-options-and-policies.md) to prevent users from changing it|
|
||||
|Prevent users from uninstalling applications from Start|In Windows 10, this policy removes the uninstall button in the context menu. It doesn't prevent users from uninstalling the app through other entry points (for example, PowerShell)|
|
||||
|Remove All Programs list from the Start menu|In Windows 10, this policy removes the **All apps** button.|
|
||||
|Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands|This policy removes the Shut Down, Restart, Sleep, and Hibernate commands from the Start Menu, Start Menu power button, CTRL+ALT+DEL screen, and Alt+F4 Shut Down Windows menu.|
|
||||
@ -45,11 +44,9 @@ These policy settings are available in **Administrative Templates\\Start Menu an
|
||||
|Start Layout|This policy applies a specific Start layout, and it also prevents users from changing the layout. This policy can be configured in **User Configuration** or **Computer Configuration**.|
|
||||
|Force Start to be either full screen size or menu size|This policy applies a specific size for Start.|
|
||||
|
||||
## Deprecated Group Policy settings for Start
|
||||
|
||||
## <a href="" id="deprecated-group-policy-settings-for-start-"></a>Deprecated Group Policy settings for Start
|
||||
|
||||
|
||||
The Start policy settings listed below don't work on Windows 10. Most of them were deprecated in Windows 8 however a few more were deprecated in Windows 10. Deprecation in this case means that the policy setting won't work on Windows 10. The “Supported on” text for a policy setting won't list Windows 10. The policy settings are still in the Group Policy Management Console and can be used on the operating systems that they apply to.
|
||||
The Start policy settings listed in the following table don't work on Windows 10. Most of them were deprecated in Windows 8 however a few more were deprecated in Windows 10. Deprecation in this case means that the policy setting won't work on Windows 10. The “Supported on” text for a policy setting won't list Windows 10. The policy settings are still in the Group Policy Management Console and can be used on the operating systems that they apply to.
|
||||
|
||||
| Policy | When deprecated |
|
||||
|----------------------------------------------------------------------------------|-----------------|
|
||||
@ -92,7 +89,3 @@ The Start policy settings listed below don't work on Windows 10. Most of them w
|
||||
- [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 taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -4,9 +4,9 @@ description: Administrators can pin more apps to the taskbar and remove default
|
||||
ms.prod: windows-client
|
||||
author: lizgt2000
|
||||
ms.author: lizlong
|
||||
ms.topic: article
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 01/18/2018
|
||||
ms.date: 08/18/2023
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
@ -26,7 +26,7 @@ You can specify different taskbar configurations based on device locale and regi
|
||||
|
||||
If you specify an app to be pinned that isn't 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.
|
||||
The order of apps in the XML file dictates the order of pinned apps on the taskbar from left to right, starting 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.
|
||||
@ -321,11 +321,18 @@ The resulting taskbar for computers in any other country region:
|
||||
|
||||
## 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 taskbar 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)
|
||||
[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 taskbar 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)
|
||||
|
||||
@ -6,9 +6,9 @@ manager: aaroncz
|
||||
ms.prod: windows-client
|
||||
author: lizgt2000
|
||||
ms.author: lizlong
|
||||
ms.topic: article
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/18/2018
|
||||
ms.date: 08/18/2023
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier1
|
||||
@ -17,7 +17,7 @@ ms.technology: itpro-configure
|
||||
|
||||
# Customize and export Start layout
|
||||
|
||||
**Applies to**
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
|
||||
@ -27,15 +27,13 @@ The easiest method for creating a customized Start layout to apply to other Wind
|
||||
|
||||
After you export the layout, decide whether you want to apply a *full* Start layout or a *partial* Start layout.
|
||||
|
||||
When a full Start layout is applied, the users cannot pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they cannot pin any apps to Start.
|
||||
When a full Start layout is applied, the users can't pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they can't pin any apps to Start.
|
||||
|
||||
When [a partial Start layout](#configure-a-partial-start-layout) is applied, the contents of the specified tile groups cannot be changed, but users can move those groups, and can also create and customize their own groups.
|
||||
When [a partial Start layout](#configure-a-partial-start-layout) is applied, the contents of the specified tile groups can't be changed, but users can move those groups, and can also create and customize their own groups.
|
||||
|
||||
> [!NOTE]
|
||||
> Partial Start layout is only supported on Windows 10, version 1511 and later.
|
||||
|
||||
|
||||
|
||||
You can deploy the resulting .xml file to devices using one of the following methods:
|
||||
|
||||
- [Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
@ -44,7 +42,7 @@ You can deploy the resulting .xml file to devices using one of the following met
|
||||
|
||||
- [Mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
|
||||
## Customize the Start screen on your test computer
|
||||
### Customize the Start screen on your test computer
|
||||
|
||||
To prepare a Start layout for export, you simply customize the Start layout on a test computer.
|
||||
|
||||
@ -52,32 +50,32 @@ To prepare a Start layout for export, you simply customize the Start layout on a
|
||||
|
||||
1. Set up a test computer on which to customize the Start layout. Your test computer should have the operating system that is installed on the users' computers (Windows 10 Pro, Enterprise, or Education). Install all apps and services that the Start layout should display.
|
||||
|
||||
2. Create a new user account that you will use to customize the Start layout.
|
||||
1. Create a new user account that you'll use to customize the Start layout.
|
||||
|
||||
**To customize Start**
|
||||
|
||||
1. Sign in to your test computer with the user account that you created.
|
||||
|
||||
2. Customize the Start layout as you want users to see it by using the following techniques:
|
||||
1. Customize the Start layout as you want users to see it by using the following techniques:
|
||||
|
||||
- **Pin apps to Start**. From Start, type the name of the app. When the app appears in the search results, right-click the app, and then click **Pin to Start**.
|
||||
- **Pin apps to Start**. From Start, type the name of the app. When the app appears in the search results, right-click the app, and then select **Pin to Start**.
|
||||
|
||||
To view all apps, click **All apps** in the bottom-left corner of Start. Right-click any app, and pin or unpin it from Start.
|
||||
To view all apps, select **All apps** in the bottom-left corner of Start. Right-click any app, and pin or unpin it from Start.
|
||||
|
||||
- **Unpin apps** that you don't want to display. To unpin an app, right-click the app, and then click **Unpin from Start**.
|
||||
- **Unpin apps** that you don't want to display. To unpin an app, right-click the app, and then select **Unpin from Start**.
|
||||
|
||||
- **Drag tiles** on Start to reorder or group apps.
|
||||
|
||||
- **Resize tiles**. To resize tiles, right-click the tile and then click **Resize.**
|
||||
- **Resize tiles**. To resize tiles, right-click the tile and then select **Resize.**
|
||||
|
||||
- **Create your own app groups**. Drag the apps to an empty area. To name a group, click above the group of tiles and then type the name in the **Name group** field that appears above the group.
|
||||
- **Create your own app groups**. Drag the apps to an empty area. To name a group, select above the group of tiles and then type the name in the **Name group** field that appears above the group.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> In Windows 10, version 1703, if the Start layout includes tiles for apps that are not installed on the device that the layout is later applied to, the tiles for those apps will be blank. The blank tiles will persist until the next time the user signs in, at which time the blank tiles are removed. Some system events may cause the blank tiles to be removed before the next sign-in.
|
||||
>
|
||||
> In earlier versions of Windows 10, no tile would be pinned.
|
||||
|
||||
## Export the Start layout
|
||||
### Export the Start layout
|
||||
|
||||
When you have the Start layout that you want your users to see, use the [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell to export the Start layout to an .xml file. Start layout is located by default at C:\Users\username\AppData\Local\Microsoft\Windows\Shell\
|
||||
|
||||
@ -88,7 +86,7 @@ When you have the Start layout that you want your users to see, use the [Export-
|
||||
|
||||
1. While signed in with the same account that you used to customize Start, right-click Start, and select **Windows PowerShell**.
|
||||
|
||||
2. On a device running Windows 10, version 1607, 1703, or 1803, at the Windows PowerShell command prompt, enter the following command:
|
||||
1. On a device running Windows 10, version 1607, 1703, or 1803, at the Windows PowerShell command prompt, enter the following command:
|
||||
|
||||
`Export-StartLayout -path <path><file name>.xml`
|
||||
|
||||
@ -100,7 +98,7 @@ When you have the Start layout that you want your users to see, use the [Export-
|
||||
|
||||
In the previous command, `-path` is a required parameter that specifies the path and file name for the export file. You can specify a local path or a UNC path (for example, \\\\FileServer01\\StartLayouts\\StartLayoutMarketing.xml).
|
||||
|
||||
Use a file name of your choice—for example, StartLayoutMarketing.xml. Include the .xml file name extension. The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet does not append the file name extension, and the policy settings require the extension.
|
||||
Use a file name of your choice—for example, StartLayoutMarketing.xml. Include the .xml file name extension. The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet doesn't append the file name extension, and the policy settings require the extension.
|
||||
|
||||
Example of a layout file produced by `Export-StartLayout`:
|
||||
|
||||
@ -120,12 +118,11 @@ When you have the Start layout that you want your users to see, use the [Export-
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
3. (Optional) Edit the .xml file to add [a taskbar configuration](configure-windows-10-taskbar.md) or to [modify the exported layout](start-layout-xml-desktop.md). When you make changes to the exported layout, be aware that [the order of the elements in the .xml file is critical.](start-layout-xml-desktop.md#required-order)
|
||||
1. (Optional) Edit the .xml file to add [a taskbar configuration](configure-windows-10-taskbar.md) or to [modify the exported layout](start-layout-xml-desktop.md). When you make changes to the exported layout, be aware that [the order of the elements in the .xml file is critical.](start-layout-xml-desktop.md#required-order)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If the Start layout that you export contains tiles for desktop (Win32) apps or .url links, **Export-StartLayout** will use **DesktopApplicationLinkPath** in the resulting file. Use a text or XML editor to change **DesktopApplicationLinkPath** to **DesktopApplicationID**. See [Specify Start tiles](start-layout-xml-desktop.md#specify-start-tiles) for details on using the app ID in place of the link path.
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> All clients that the start layout applies to must have the apps and other shortcuts present on the local system in the same location as the source for the Start layout.
|
||||
>
|
||||
@ -141,11 +138,9 @@ When you have the Start layout that you want your users to see, use the [Export-
|
||||
>
|
||||
>* Three additional shortcuts are pinned to the start menu after the export. These are shortcuts to %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs, %APPDATA%\Microsoft\Windows\Start Menu\Programs, and %APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\.
|
||||
|
||||
### Configure a partial Start layout
|
||||
|
||||
## Configure a partial Start layout
|
||||
|
||||
|
||||
A partial Start layout enables you to add one or more customized tile groups to users' Start screens or menus, while still allowing users to make changes to other parts of the Start layout. All groups that you add are *locked*, meaning users cannot change the contents of those tile groups, however users can change the location of those groups. Locked groups are identified with an icon, as shown in the following image.
|
||||
A partial Start layout enables you to add one or more customized tile groups to users' Start screens or menus, while still allowing users to make changes to other parts of the Start layout. All groups that you add are *locked*, meaning users can't change the contents of those tile groups, however users can change the location of those groups. Locked groups are identified with an icon, as shown in the following image.
|
||||
|
||||
|
||||
|
||||
@ -159,28 +154,32 @@ If the Start layout is applied by Group Policy or MDM, and the policy is removed
|
||||
|
||||
1. [Customize the Start layout](#customize-the-start-screen-on-your-test-computer).
|
||||
|
||||
2. [Export the Start layout](#export-the-start-layout).
|
||||
3. Open the layout .xml file. There is a `<DefaultLayoutOverride>` element. Add `LayoutCustomizationRestrictionType="OnlySpecifiedGroups"` to the **DefaultLayoutOverride** element as follows:
|
||||
1. [Export the Start layout](#export-the-start-layout).
|
||||
1. Open the layout .xml file. There is a `<DefaultLayoutOverride>` element. Add `LayoutCustomizationRestrictionType="OnlySpecifiedGroups"` to the **DefaultLayoutOverride** element as follows:
|
||||
|
||||
```xml
|
||||
<DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
|
||||
```
|
||||
|
||||
4. Save the file and apply using any of the deployment methods.
|
||||
1. Save the file and apply using any of the deployment methods.
|
||||
|
||||
> [!NOTE]
|
||||
> Office 2019 tiles might be removed from the Start menu when you upgrade Office 2019. This only occurs if Office 2019 app tiles are in a custom group in the Start menu and only contains the Office 2019 app tiles. To avoid this problem, place another app tile in the Office 2019 group prior to the upgrade. For example, add Notepad.exe or calc.exe to the group. This issue occurs because Office 2019 removes and reinstalls the apps when they are upgraded. Start removes empty groups when it detects that all apps for that group have been removed.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
|
||||
## Related topics
|
||||
[Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
|
||||
[Add image for secondary tiles](start-secondary-tiles.md)
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.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 taskbar 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)
|
||||
[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 taskbar 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)
|
||||
|
||||
@ -68,7 +68,7 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
1. Select **Devices** from the left navigation menu.
|
||||
1. Under the **Windows Autopatch** section, select **Release management**.
|
||||
1. In the **Release management** blade, select **Autopatch groups (preview)**.
|
||||
1. In the **Release management** blade, select **Autopatch groups**.
|
||||
1. In the **Autopatch groups** blade, select **Create**.
|
||||
1. In **Basics** page, enter a **name** and a **description** then select **Next: Deployment rings**.
|
||||
1. Enter up to 64 characters for the Autopatch group name and 150 characters maximum for the description. The Autopatch group name is appended to both the update rings and the DSS policy names that get created once the Custom Autopatch group is created.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 12/13/2018
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
localizationpriority: medium
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/27/2017
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
localizationpriority: medium
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/27/2017
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
localizationpriority: medium
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/27/2017
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
localizationpriority: medium
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/27/2017
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 06/04/2020
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/11/2016
|
||||
ms.collection: highpri
|
||||
ms.topic: conceptual
|
||||
|
||||
70
windows/privacy/copilot-supplemental-terms.md
Normal file
70
windows/privacy/copilot-supplemental-terms.md
Normal file
@ -0,0 +1,70 @@
|
||||
---
|
||||
title: COPILOT IN WINDOWS (PREVIEW) SUPPLEMENTAL TERMS
|
||||
description: The Supplemental Terms for Copilot in Windows (Preview)
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-privacy
|
||||
ms.localizationpriority: medium
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: laurawi
|
||||
ms.date: 09/20/2023
|
||||
ms.topic: conceptual
|
||||
hideEdit: true
|
||||
layout: ContentPage
|
||||
ROBOTS: NOINDEX, NOFOLLOW
|
||||
feedback_system: None
|
||||
---
|
||||
|
||||
# COPILOT IN WINDOWS (PREVIEW) SUPPLEMENTAL TERMS
|
||||
|
||||
Copilot in Windows is your AI companion that brings productivity to your fingertips. Leveraging Bing Chat or Bing Chat Enterprise, Copilot in Windows accelerates your tasks, reduces friction, saves you time and provides you with personalized answers, inspiration and task assistance. Your use of Copilot in Windows is subject to these supplemental terms of use (“Terms”). By using Copilot in Windows you agree to be bound by these Terms.
|
||||
|
||||
1. Preview
|
||||
|
||||
a. COPILOT IN WINDOWS IS A PREVIEW FEATURE AND IS PROVIDED “AS-IS,” “WITH ALL FAULTS,” AND “AS AVAILABLE".
|
||||
|
||||
b. Microsoft makes no guarantees or promises about how Copilot in Windows operates or that it will function as intended.
|
||||
|
||||
2. Eligibility and Use Requirements.
|
||||
|
||||
a. You must be signed into Windows with your Microsoft account to access Copilot in Windows.
|
||||
|
||||
b. If you're signed into Windows with your work or school account, your organization may have given you the ability to use Copilot in Windows. If you have access to Copilot in Windows but your organization hasn't enabled Bing Chat Enterprise, your use will be limited to Bing Chat’s current turn limit.
|
||||
|
||||
c. Along with these Terms, your use of Copilot in Windows is also governed by the Microsoft Services Agreement, which is incorporated by reference. You agree that Copilot in Windows constitutes a Service, as defined in the [Microsoft Services Agreement](https://www.microsoft.com/servicesagreement). If there's any conflict between these Terms and the Microsoft Services Agreement, the conflicting provision in these Terms will control.
|
||||
|
||||
3. Bing Chat
|
||||
|
||||
a. Your Copilot in Windows experiences powered by Bing Chat are subject to [Bing Chat’s terms of use](https://go.microsoft.com/fwlink/p/?linkid=2247757).
|
||||
|
||||
b. If your organization is allowing you to use Bing Chat Enterprise, your Copilot in Windows experiences will be powered by Bing Chat Enterprise and will be subject to [Bing Chat Enterprise’s terms of use](https://go.microsoft.com/fwlink/p/?linkid=2247908).
|
||||
|
||||
4. Using Copilot in Windows
|
||||
|
||||
a. Copilot in Windows may allow you to submit text inputs and converse with an online computer-powered chatbot and in certain circumstances generate text content or image content. Your use of Copilot in Windows must comply with the Code of Conduct section of the Microsoft Services Agreement and the Bing Chat Code of Conduct or Bing Chat Enterprise Content Policy.
|
||||
|
||||
b. Copilot in Windows may allow you to change some of your Windows settings based on the text you submit into Copilot in Windows. Additionally, when you copy text in other apps while Copilot in Windows is open, it may automatically prompt you with suggestions to send the copied text to the chat and offer further suggestions of what you can do with that text.
|
||||
|
||||
c. You can consent to letting Copilot in Windows access your Microsoft Edge webpage content. This allows Copilot in Windows to provide relevant responses by accessing content from your active foreground Edge tab. This can be adjusted anytime in Copilot in Windows settings.
|
||||
|
||||
5. Data
|
||||
|
||||
a. All data processed by Copilot in Windows, including voice input data, will be processed according to the Microsoft Privacy Statement.
|
||||
|
||||
6. Ownership of Content
|
||||
|
||||
a. Microsoft doesn't claim ownership of any content you provide, post, input, or submit to, or receive from, Copilot in Windows, Bing Chat, or Bing Chat Enterprise (including feedback and suggestions). You'll need to make your own determination regarding the intellectual property rights you have in output content and its commercial usability, taking into account, among other things, your usage scenario(s) and the laws of the relevant jurisdiction. You warrant and represent that you or your organization owns or otherwise controls all of the rights to your content as described in these Terms including, without limitation, all the rights necessary for you to provide, post, upload, input or submit the content.
|
||||
|
||||
7. Third-party claims
|
||||
|
||||
a. You're responsible for responding to any third-party claims regarding your use of Copilot in Windows in compliance with applicable laws (including, but not limited to, copyright infringement or other claims relating to output content that was output during your use of Copilot in Windows).
|
||||
|
||||
8. Reverse engineering
|
||||
|
||||
a. You may not use Copilot in Windows to discover any underlying components of the models, algorithms, or systems, such as exfiltrating the weights of models.
|
||||
|
||||
9. Extracting data
|
||||
|
||||
a. You may not use web scraping, web harvesting, or web data extraction methods to extract data from Copilot in Windows or from any output content.
|
||||
|
||||
10. **IF YOU LIVE IN (OR YOUR PRINCIPAL PLACE OF BUSINESS IS IN) THE UNITED STATES, PLEASE READ THE BINDING ARBITRATION CLAUSE AND CLASS ACTION WAIVER IN SECTION 15 OF THE MICROSOFT SERVICES AGREEMENT. IT AFFECTS HOW DISPUTES RELATING TO THIS AGREEMENT ARE RESOLVED.**
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/09/2018
|
||||
ms.collection: highpri
|
||||
ms.topic: how-to
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 10/12/2017
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 06/28/2021
|
||||
ms.collection: highpri
|
||||
ms.topic: reference
|
||||
|
||||
@ -12,7 +12,7 @@ metadata:
|
||||
ms.collection: highpri
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 09/08/2021 #Required; mm/dd/yyyy format.
|
||||
ms.localizationpriority: high
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 05/15/2019
|
||||
ms.topic: conceptual
|
||||
---
|
||||
@ -156,6 +156,8 @@ For Windows 10 and Windows 11, the following MDM policies are available in the [
|
||||
1. Windows Update Allow Update Service - [Update/AllowUpdateService](/windows/client-management/mdm/policy-csp-update#update-allowupdateservice). Specifies whether the device could use Microsoft Update, Windows Server Update Services (WSUS), or Microsoft Store. **Set to 0 (zero)**
|
||||
1. Windows Update Service URL - [Update/UpdateServiceUrl](/windows/client-management/mdm/policy-csp-update#update-updateserviceurl). Allows the device to check for updates from a WSUS server instead of Microsoft Update. **Set to String** with the Value:
|
||||
1. **\<Replace>\<CmdID>$CmdID$</CmdID>\<Item>\<Meta>\<Format>chr</Format>\<Type>text/plain</Type>\</Meta>\<Target> \<LocURI>./Vendor/MSFT/Policy/Config/Update/UpdateServiceUrl</LocURI>\</Target>\<Data>http://abcd-srv:8530</Data>\</Item>\</Replace>**
|
||||
28. **Recommendations** </br>
|
||||
a. [HideRecentJumplists](/windows/client-management/mdm/policy-csp-start#hiderecentjumplists) setting in the Start Policy configuration service provider (CSP). To hide a list of recommended apps and files in the Recommended section on the Start menu.
|
||||
|
||||
### <a href="" id="bkmk-mdm-allowedtraffic"></a> Allowed traffic for Microsoft Intune / MDM configurations
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/07/2016
|
||||
ms.collection: highpri
|
||||
ms.topic: conceptual
|
||||
@ -113,6 +113,7 @@ The following table lists management options for each setting, For Windows 10 (
|
||||
| [30. Cloud Clipboard](#bkmk-clcp) | |  | |
|
||||
| [31. Services Configuration](#bkmk-svccfg) | |  |  |
|
||||
| [32. Widgets](#bkmk-widgets) | |  |  |
|
||||
| [33. Recommendations](#33-recommendations) | |  |  |
|
||||
|
||||
|
||||
### Settings for Windows Server 2016 with Desktop Experience
|
||||
@ -1923,6 +1924,16 @@ To turn off Widgets, you can use Group Policy or a custom setting in an MDM solu
|
||||
|
||||
For more information about AllowNewsAndInterests and the “Allow widgets” policy, [review this information](/windows/client-management/mdm/policy-csp-newsandinterests#allownewsandinterests).
|
||||
|
||||
### 33. Recommendations
|
||||
|
||||
The Recommended section on the Start menu displays a list of recommended apps and files.
|
||||
|
||||
To turn off these recommendations, you can use any of the following methods:
|
||||
|
||||
- In Group Policy, set the "Remove Recommended from Start Menu" policy to Enabled under **User Configuration** > **Administrative Templates** > **Start Menu and Taskbar**.
|
||||
- In an MDM solution, such as Microsoft Intune, you can use the [HideRecentJumplists](/windows/client-management/mdm/policy-csp-start#hiderecentjumplists) setting in the Start Policy configuration service provider (CSP).
|
||||
- In the registry, you can set **HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Start_TrackDocs** to 0.
|
||||
- In the UI, you can turn off **Show recommendations for tips, shortcuts, new apps, and more** under **Settings** > **Personalization** > **Start**.
|
||||
|
||||
### <a href="" id="bkmk-allowedtraffic"></a> Allowed traffic list for Windows Restricted Traffic Limited Functionality Baseline
|
||||
|
||||
@ -1933,5 +1944,4 @@ For more information about AllowNewsAndInterests and the “Allow widgets” pol
|
||||
|ocsp.digicert.com/*|
|
||||
|www.microsoft.com/pkiops/*|
|
||||
|
||||
|
||||
To learn more, see [Device update management](/windows/client-management/mdm/device-update-management) and [Configure Automatic Updates by using Group Policy](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc720539(v=ws.10)).
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 01/18/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 05/20/2019
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 12/17/2020
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/31/2017
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 03/31/2017
|
||||
ms.collection: highpri
|
||||
ms.topic: reference
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 06/29/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 06/29/2018
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 07/20/2020
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 05/11/2020
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 12/17/2020
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -6,7 +6,7 @@ ms.technology: itpro-privacy
|
||||
ms.localizationpriority: high
|
||||
author: DHB-MSFT
|
||||
ms.author: danbrown
|
||||
manager: dougeby
|
||||
manager: laurawi
|
||||
ms.date: 12/17/2020
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -47,10 +47,11 @@ Windows Sandbox has the following properties:
|
||||
2. Enable virtualization on the machine.
|
||||
|
||||
- If you're using a physical machine, make sure virtualization capabilities are enabled in the BIOS.
|
||||
- If you're using a virtual machine, run the following PowerShell command to enable nested virtualization:
|
||||
- If you're using a virtual machine, you need to enable nested virtualization. If needed, also update the VM to support nested virtualization. Run the following PowerShell commands on the host:
|
||||
|
||||
```powershell
|
||||
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
|
||||
Update-VMVersion -VMName <VMName>
|
||||
```
|
||||
|
||||
3. Use the search bar on the task bar and type **Turn Windows Features on or off** to access the Windows Optional Features tool. Select **Windows Sandbox** and then **OK**. Restart the computer if you're prompted.
|
||||
|
||||
@ -108,7 +108,7 @@ For info about setting security policies, see [Configure security policy setting
|
||||
| [Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers](network-security-restrict-ntlm-outgoing-ntlm-traffic-to-remote-servers.md)| Describes the best practices, location, values, management aspects, and security considerations for the **Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers** security policy setting. |
|
||||
| [Recovery console: Allow automatic administrative logon](recovery-console-allow-automatic-administrative-logon.md)| Describes the best practices, location, values, policy management, and security considerations for the **Recovery console: Allow automatic administrative logon** security policy setting. |
|
||||
| [Recovery console: Allow floppy copy and access to all drives and folders](recovery-console-allow-floppy-copy-and-access-to-all-drives-and-folders.md)| Describes the best practices, location, values, policy management, and security considerations for the **Recovery console: Allow floppy copy and access to all drives and folders** security policy setting. |
|
||||
| [Shutdown: Allow system to be shut down without having to lg on](shutdown-allow-system-to-be-shut-down-without-having-to-log-on.md)| Describes the best practices, location, values, policy management, and security considerations for the **Shutdown: Allow system to be shut down without having to log on** security policy setting. |
|
||||
| [Shutdown: Allow system to be shut down without having to log on](shutdown-allow-system-to-be-shut-down-without-having-to-log-on.md)| Describes the best practices, location, values, policy management, and security considerations for the **Shutdown: Allow system to be shut down without having to log on** security policy setting. |
|
||||
| [Shutdown: Clear virtual memory pagefile](shutdown-clear-virtual-memory-pagefile.md)| Describes the best practices, location, values, policy management, and security considerations for the **Shutdown: Clear virtual memory pagefile** security policy setting.|
|
||||
| [System cryptography: Force strong key protection for user keys stored on the computer](system-cryptography-force-strong-key-protection-for-user-keys-stored-on-the-computer.md)| Describes the best practices, location, values, policy management, and security considerations for the **System cryptography: Force strong key protection for user keys stored on the computer** security policy setting. |
|
||||
| [System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing](system-cryptography-use-fips-compliant-algorithms-for-encryption-hashing-and-signing.md)| This security policy reference topic for the IT professional describes the best practices, location, values, policy management, and security considerations for this policy setting. |
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user