mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
More work
This commit is contained in:
parent
e544f2a370
commit
51e7684de2
@ -6690,6 +6690,11 @@
|
||||
"redirect_url": "/windows/client-management/client-tools/windows-version-search",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/manage-corporate-devices.md",
|
||||
"redirect_url": "/windows/client-management/manage-windows-10-in-your-organization-modern-management",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/client-management/add-an-azure-ad-tenant-and-azure-ad-subscription.md",
|
||||
"redirect_url": "/azure/active-directory/fundamentals/active-directory-access-create-new-tenant",
|
||||
|
@ -1,28 +1,22 @@
|
||||
---
|
||||
title: Windows 10 default media removal policy
|
||||
description: In Windows 10, version 1809, the default removal policy for external storage media changed from Better performance to Quick removal.
|
||||
title: Windows default media removal policy
|
||||
description: In Windows 10 and later, the default removal policy for external storage media changed from Better performance to Quick removal.
|
||||
ms.prod: windows-client
|
||||
author: vinaypamnani-msft
|
||||
ms.author: vinpa
|
||||
ms.date: 11/25/2020
|
||||
ms.date: 04/11/2023
|
||||
ms.topic: article
|
||||
ms.custom:
|
||||
- CI 111493
|
||||
- CI 125140
|
||||
- CSSTroubleshooting
|
||||
ms.localizationpriority: medium
|
||||
manager: kaushika
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-manage
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
---
|
||||
|
||||
# Change in default removal policy for external storage media in Windows 10, version 1809
|
||||
# Change in default removal policy for external storage media in Windows
|
||||
|
||||
Windows defines two main policies, **Quick removal** and **Better performance**, that control how the system interacts with external storage devices such as USB thumb drives or Thunderbolt-enabled external drives. Beginning in Windows 10 version 1809, the default policy is **Quick removal**.
|
||||
|
||||
In earlier versions of Windows, the default policy was **Better performance**.
|
||||
Windows defines two main policies, **Quick removal** and **Better performance**, that control how the system interacts with external storage devices such as USB thumb drives or Thunderbolt-enabled external drives. Beginning in Windows 10 version 1809, the default policy is **Quick removal**. In earlier versions of Windows, the default policy was **Better performance**.
|
||||
|
||||
You can change the policy setting for each external device, and the policy that you set remains in effect if you disconnect the device and then connect it again to the same computer port.
|
||||
|
||||
@ -30,13 +24,14 @@ You can change the policy setting for each external device, and the policy that
|
||||
|
||||
You can use the storage device policy setting to change the manner in which Windows manages storage devices to better meet your needs. The policy settings have the following effects:
|
||||
|
||||
* **Quick removal**: This policy manages storage operations in a manner that keeps the device ready to remove at any time. You can remove the device without using the Safely Remove Hardware process. However, to do this, Windows cannot cache disk write operations. This may degrade system performance.
|
||||
* **Better performance**: This policy manages storage operations in a manner that improves system performance. When this policy is in effect, Windows can cache write operations to the external device. However, you must use the Safely Remove Hardware process to remove the external drive. The Safely Remove Hardware process protects the integrity of data on the device by making sure that all cached operations finish.
|
||||
> [!IMPORTANT]
|
||||
> If you use the **Better performance** policy, you must use the Safely Remove Hardware process to remove the device. If you remove or disconnect the device without following the safe removal instructions, you risk losing data.
|
||||
- **Quick removal**: This policy manages storage operations in a manner that keeps the device ready to remove at any time. You can remove the device without using the Safely Remove Hardware process. However, to do this, Windows cannot cache disk write operations. This may degrade system performance.
|
||||
- **Better performance**: This policy manages storage operations in a manner that improves system performance. When this policy is in effect, Windows can cache write operations to the external device. However, you must use the Safely Remove Hardware process to remove the external drive. The Safely Remove Hardware process protects the integrity of data on the device by making sure that all cached operations finish.
|
||||
|
||||
> [!NOTE]
|
||||
> If you select **Better performance**, we recommend that you also select **Enable write caching on the device**.
|
||||
> [!IMPORTANT]
|
||||
> If you use the **Better performance** policy, you must use the Safely Remove Hardware process to remove the device. If you remove or disconnect the device without following the safe removal instructions, you risk losing data.
|
||||
|
||||
> [!NOTE]
|
||||
> If you select **Better performance**, we recommend that you also select **Enable write caching on the device**.
|
||||
|
||||
To change the policy for an external storage device:
|
||||
|
||||
@ -45,16 +40,16 @@ To change the policy for an external storage device:
|
||||
1. In File Explorer, identify the letter or label that is associated with the device (for example, **USB Drive (D:)**).
|
||||
1. Right-click **Start**, then select **Disk Management**.
|
||||
1. In the lower section of the Disk Management window, right-click the label of the device, and then select **Properties**.
|
||||
|
||||
|
||||

|
||||
|
||||
|
||||
1. Select **Policies**.
|
||||
|
||||
> [!NOTE]
|
||||
> Some recent versions of Windows may use a different arrangement of tabs in the disk properties dialog box.
|
||||
>
|
||||
|
||||
> [!NOTE]
|
||||
> Some recent versions of Windows may use a different arrangement of tabs in the disk properties dialog box.
|
||||
>
|
||||
> If you do not see the **Policies** tab, select **Hardware**, select the removable drive from the **All disk drives** list, and then select **Properties**. The **Policies** tab should now be available.
|
||||
|
||||
|
||||
1. Select the policy that you want to use.
|
||||
|
||||
|
||||

|
||||
|
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Manage the Settings app with Group Policy (Windows 10 and Windows 11)
|
||||
title: Manage the Settings app with Group Policy
|
||||
description: Find out how to manage the Settings app with Group Policy so you can hide specific pages from users.
|
||||
ms.prod: windows-client
|
||||
author: vinaypamnani-msft
|
||||
ms.date: 09/14/2021
|
||||
ms.reviewer:
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: vinpa
|
||||
ms.topic: article
|
||||
@ -17,32 +17,28 @@ appliesto:
|
||||
|
||||
# Manage the Settings app with Group Policy
|
||||
|
||||
You can now manage the pages that are shown in the Settings app by using Group Policy. When you use Group Policy to manage pages, you can hide specific pages from users. Before Windows 10, version 1703, you could either show everything in the Settings app or hide it completely.
|
||||
To make use of the Settings App group policies on Windows server 2016, install fix [4457127](https://support.microsoft.com/help/4457127/windows-10-update-kb4457127) or a later cumulative update.
|
||||
You can manage the pages that are shown in the Settings app by using Group Policy. When you use Group Policy to manage pages, you can hide specific pages from users.
|
||||
|
||||
>[!NOTE]
|
||||
>Each server that you want to manage access to the Settings App must be patched.
|
||||
> [!NOTE]
|
||||
> To make use of the Settings App group policies on Windows server 2016, install fix [4457127](https://support.microsoft.com/help/4457127/windows-10-update-kb4457127) or a later cumulative update. Each server that you want to manage access to the Settings App must be patched.
|
||||
|
||||
If your company uses one or the PolicyDefinitions folder of the Domain Controllers used for Group Policy management, to centrally manage the new policies, copy the ControlPanel.admx and ControlPanel.adml file to [Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store).
|
||||
If your organization uses the [Central Store](/troubleshoot/windows-client/group-policy/create-and-manage-central-store) for Group Policy management, to manage the policies, copy the ControlPanel.admx and ControlPanel.adml file to PolicyDefinitions folder.
|
||||
|
||||
This policy is available for both User and Computer depending on the version of the OS. Windows Server 2016 with KB 4457127 applied will have both User and Computer policy. Windows 10, version 1703, added Computer policy for the Settings app. Windows 10, version 1809, added User policy for the Settings app.
|
||||
This policy is available for both User and Computer configurations.
|
||||
|
||||
Policy paths:
|
||||
|
||||
**Computer Configuration** > **Administrative Templates** > **Control Panel** > **Settings Page Visibility**.
|
||||
|
||||
**User Configuration** > **Administrative Templates** > **Control Panel** > **Settings Page Visibility**.
|
||||
- **Computer Configuration** > **Administrative Templates** > **Control Panel** > **Settings Page Visibility**.
|
||||
- **User Configuration** > **Administrative Templates** > **Control Panel** > **Settings Page Visibility**.
|
||||
|
||||

|
||||
|
||||
## Configuring the Group Policy
|
||||
|
||||
The Group Policy can be configured in one of two ways: specify a list of pages that are shown or specify a list of pages to hide. To do this, add either **ShowOnly:** or **Hide:** followed by a semicolon-delimited list of URIs in **Settings Page Visibility**. For a full list of URIs, see the URI scheme reference section in [Launch the Windows Settings app](/windows/uwp/launch-resume/launch-settings-app#ms-settings-uri-scheme-reference).
|
||||
The Group Policy can be configured in one of two ways: specify a list of pages that are shown or specify a list of pages to hide. To do this, add either **ShowOnly:** or **Hide:** followed by a semicolon-delimited list of URIs in **Settings Page Visibility**. For a full list of URIs, see the URI scheme reference section in [Launch the Windows Settings app](/windows/uwp/launch-resume/launch-settings-app#ms-settings-uri-scheme-reference).
|
||||
|
||||
>[!NOTE]
|
||||
> [!IMPORTANT]
|
||||
> When you specify the URI in the Settings Page Visibility textbox, don't include **ms-settings:** in the string.
|
||||
|
||||
Here are some examples:
|
||||
For example:
|
||||
|
||||
- To show only the Ethernet and Proxy pages, set the **Settings App Visibility** textbox to **ShowOnly:Network-Proxy;Network-Ethernet**.
|
||||
- To hide the Ethernet and Proxy pages, set the **Settings App Visibility** textbox to **Hide:Network-Proxy;Network-Ethernet**.
|
||||
|
@ -135,11 +135,11 @@ It may take some time for this change to replicate to all domain controllers.
|
||||
|
||||
When a user is configured with a mandatory profile, Windows starts as though it was the first sign-in each time the user signs in. To improve sign-in performance for users with mandatory user profiles, apply the Group Policy settings shown in the following table.
|
||||
|
||||
| Group Policy setting | Windows 10 | Windows Server 2016 |
|
||||
|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------------------|
|
||||
| Computer Configuration > Administrative Templates > System > Logon > **Show first sign-in animation** = Disabled |  |  |
|
||||
| Computer Configuration > Administrative Templates > Windows Components > Search > **Allow Cortana** = Disabled |  |  |
|
||||
| Computer Configuration > Administrative Templates > Windows Components > Cloud Content > **Turn off Microsoft consumer experience** = Enabled |  |  |
|
||||
| Group Policy setting | Windows 10 | Windows Server 2016 |
|
||||
|-----------------------------------------------------------------------------------------------------------------------------------------------|:----------:|:-------------------:|
|
||||
| Computer Configuration > Administrative Templates > System > Logon > **Show first sign-in animation** = Disabled | ✅ | ✅ |
|
||||
| Computer Configuration > Administrative Templates > Windows Components > Search > **Allow Cortana** = Disabled | ✅ | ✅ |
|
||||
| Computer Configuration > Administrative Templates > Windows Components > Cloud Content > **Turn off Microsoft consumer experience** = Enabled | ✅ | ❌ |
|
||||
|
||||
> [!NOTE]
|
||||
> The Group Policy settings above can be applied in Windows Professional edition.
|
||||
|
@ -9,8 +9,6 @@ items:
|
||||
href: mandatory-user-profile.md
|
||||
- name: Windows 10 default media removal policy
|
||||
href: change-default-removal-policy-external-storage-media.md
|
||||
- name: Group Policies that apply only to Windows 10 Enterprise and Windows 10 Education
|
||||
href: group-policies-for-enterprise-and-education-editions.md
|
||||
- name: Manage Device Installation with Group Policy
|
||||
href: manage-device-installation-with-group-policy.md
|
||||
- name: Manage the Settings app with Group Policy
|
||||
|
@ -1,15 +1,14 @@
|
||||
---
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
title: Windows Libraries
|
||||
description: All about Windows Libraries, which are containers for users' content, such as Documents and Pictures.
|
||||
ms.prod: windows-client
|
||||
author: vinaypamnani-msft
|
||||
ms.author: vinpa
|
||||
ms.manager: dongill
|
||||
manager: aaroncz
|
||||
ms.reviewer:
|
||||
ms.technology: itpro-manage
|
||||
ms.topic: article
|
||||
author: vinaypamnani-msft
|
||||
description: All about Windows Libraries, which are containers for users' content, such as Documents and Pictures.
|
||||
ms.date: 09/15/2021
|
||||
ms.date: 04/11/2023
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
@ -95,14 +94,14 @@ While library files themselves can't be redirected, you can redirect known folde
|
||||
|
||||
The following table shows which locations are supported in Windows libraries.
|
||||
|
||||
|Supported Locations|Unsupported Locations|
|
||||
|---|---|
|
||||
|Fixed local volumes (NTFS/FAT)|Removable drives|
|
||||
|Shares that are indexed (departmental servers*, Windows home PCs)|Removable media (such as DVDs)<br><br>Network shares that are accessible through DFS Namespaces or are part of a failover cluster|
|
||||
|Shares that are available offline (redirected folders that use Offline Files)|Network shares that aren't available offline or remotely indexed <br><br>Network Attached Storage (NAS) devices|
|
||||
||Other data sources: SharePoint, Exchange, etc.|
|
||||
| Supported Locations | Unsupported Locations |
|
||||
|--|--|
|
||||
| Fixed local volumes (NTFS/FAT) | Removable drives |
|
||||
| Shares that are indexed (departmental servers*, Windows home PCs) | Removable media (such as DVDs)<br><br>Network shares that are accessible through DFS Namespaces or are part of a failover cluster |
|
||||
| Shares that are available offline (redirected folders that use Offline Files) | Network shares that aren't available offline or remotely indexed <br><br>Network Attached Storage (NAS) devices |
|
||||
| | Other data sources: SharePoint, Exchange, etc. |
|
||||
|
||||
\* For shares that are indexed on a departmental server, Windows Search works well in workgroups or on a domain server that has similar characteristics to a workgroup server. For example, Windows Search works well on a single share departmental server with the following characteristics:
|
||||
\* For shares that are indexed on a departmental server, Windows Search works well in a workgroup or on a domain server that has similar characteristics to a workgroup server. For example, Windows Search works well on a single share departmental server with the following characteristics:
|
||||
|
||||
- Expected maximum load is four concurrent query requests.
|
||||
- Expected indexing corpus is a maximum of one million documents.
|
||||
@ -120,7 +119,7 @@ The following library attributes can be modified within Windows Explorer, the Li
|
||||
|
||||
The library icon can be modified by the administrator or user by directly editing the Library Description schema file.
|
||||
|
||||
See the [Library Description Schema](/windows/win32/shell/library-schema-entry) topic on MSDN for information on creating Library Description files.
|
||||
See [Library Description Schema](/windows/win32/shell/library-schema-entry) for information on creating Library Description files.
|
||||
|
||||
## See also
|
||||
|
||||
|
@ -5,7 +5,7 @@ ms.prod: windows-client
|
||||
author: vinaypamnani-msft
|
||||
ms.author: vinpa
|
||||
ms.date: 04/30/2018
|
||||
ms.reviewer:
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.topic: troubleshooting
|
||||
ms.technology: itpro-manage
|
||||
@ -16,40 +16,39 @@ appliesto:
|
||||
|
||||
# What version of Windows am I running?
|
||||
|
||||
To determine if your device is enrolled in the [Long-Term Servicing Channel](/windows/deployment/update/waas-overview#servicing-channels) (LTSC, formerly LTSB) or the [General Availability Channel](/windows/deployment/update/waas-overview#servicing-channels) (SAC) you'll need to know what version of Windows 10 you're running. There are a few ways to figure this out. Each method provides a different set of details, so it's useful to learn about all of them.
|
||||
The [Long-Term Servicing Channel](/windows/deployment/update/waas-overview#servicing-channels) (LTSC, formerly LTSB) build of Windows doesn't contain many in-box applications, such as Microsoft Edge, Microsoft Store, Cortana (you do have some limited search capabilities), Microsoft Mail, Calendar, OneNote, Weather, News, Sports, Money, Photos, Camera, Music, and Clock. It's important to remember that the LTSC model is primarily for specialized devices.
|
||||
|
||||
In the [General Availability Channel](/windows/deployment/update/waas-overview#servicing-channels), you can set feature updates as soon as Microsoft releases them. This servicing modal is ideal for pilot deployments and to test Windows feature updates and for users like developers who need to work with the latest features immediately. Once you've tested the latest release, you can choose when to roll it out broadly in your deployment.
|
||||
|
||||
To determine if your device is enrolled in the Long-Term Servicing Channel or the General Availability Channel, you'll need to know what version of Windows you're running. There are a few ways to figure this out. Each method provides a different set of details, so it's useful to learn about all of them.
|
||||
|
||||
## System Properties
|
||||
|
||||
Click **Start** > **Settings** > **System** > click **About** from the bottom of the left-hand menu
|
||||
|
||||
You'll now see **Edition**, **Version**, and **OS Build** information. Something like this:
|
||||
Select **Start** > **Settings** > **System**, then select **About**. You'll then see **Edition**, **Version**, and **OS Build** information.
|
||||
|
||||

|
||||
|
||||
## Using Keyword Search
|
||||
|
||||
You can type the following in the search bar and press **ENTER** to see version details for your device.
|
||||
You can type the following in the search bar and press **ENTER** to see version details for your device.
|
||||
|
||||
**"winver"**
|
||||
- **"winver"**:
|
||||
|
||||

|
||||

|
||||
|
||||
**"msinfo"** or **"msinfo32"** to open **System Information**:
|
||||
- **"msinfo"** or **"msinfo32"** to open **System Information**:
|
||||
|
||||

|
||||

|
||||
|
||||
> [!TIP]
|
||||
> You can also use `winver` or `msinfo32` commands at the command prompt.
|
||||
|
||||
## Using Command Prompt or PowerShell
|
||||
|
||||
At the Command Prompt or PowerShell interface, type **"systeminfo | findstr /B /C:"OS Name" /B /C:"OS Version"** and then press **ENTER**
|
||||
- At the PowerShell or Command Prompt, type `systeminfo | findstr /B /C:"OS Name" /B /C:"OS Version"` and then press **ENTER**
|
||||
|
||||

|
||||

|
||||
|
||||
At the Command Prompt or PowerShell, type **"slmgr /dlv"**, and then press ENTER. The /dlv command displays the detailed licensing information. Notice the output displays "EnterpriseS" as seen in the image below:
|
||||
- At the PowerShell or Command Prompt, type `slmgr /dlv`, and then press ENTER. The /dlv command displays the detailed licensing information. Notice the output displays "EnterpriseS" as seen in the image below:
|
||||
|
||||

|
||||
|
||||
## What does it all mean?
|
||||
|
||||
The Long-term Servicing Channel is available only in the Windows 10 Enterprise LTSB edition. This build of Windows doesn't contain many in-box applications, such as Microsoft Edge, Microsoft Store, Cortana (you do have some limited search capabilities), Microsoft Mail, Calendar, OneNote, Weather, News, Sports, Money, Photos, Camera, Music, and Clock. It's important to remember that the LTSC model is primarily for specialized devices.
|
||||
|
||||
In the General Availability Channel, you can set feature updates as soon as Microsoft releases them. This servicing modal is ideal for pilot deployments and to test Windows 10 feature updates and for users like developers who need to work with the latest features immediately. Once you've tested the latest release, you can choose when to roll it out broadly in your deployment.
|
||||

|
||||
|
@ -14,13 +14,15 @@ appliesto:
|
||||
---
|
||||
|
||||
# How Mobile Device Management Providers support eSIM Management on Windows
|
||||
|
||||
The eSIM Profile Management Solution places the Mobile Device Management (MDM) Provider in the front and center. The whole idea is to use an already-existing solution that customers are familiar with and use to manage devices. The expectations from an MDM are that it will use the same sync mechanism that it uses for device policies to push any policy to the eSIM profile, and be able to use Groups and Users the same way. This way, the eSIM profile download and the installation happen in the background without impacting the end user. Similarly, the IT admin would use the same method of managing the eSIM profiles (Assignment/de-assignment, etc.) the same way as they currently do device management.
|
||||
If you are a Mobile Device Management (MDM) Provider and want to support eSIM Management on Windows, perform the following steps:
|
||||
|
||||
If you are a Mobile Device Management (MDM) Provider and want to support eSIM Management on Windows, perform the following steps:
|
||||
|
||||
- Onboard to Azure Active Directory
|
||||
- Contact mobile operators directly or contact orchestrator providers. Windows provides the capability for eSIM profiles to be managed by MDM providers in the case of enterprise use cases. However, Windows does not limit how ecosystem partners might want to offer this to their own partners and/or customers. As such, the eSIM profile management capability is something that can be supported by integrating with the Windows OMA-DM. This makes it possible to remotely manage the eSIM profiles according to the company policies. Contact mobile operators directly or contact orchestrator providers. Windows provides the capability for eSIM profiles to be managed by MDM providers in the case of enterprise use cases. However, Windows does not limit how ecosystem partners might want to offer this capability to their own partners and/or customers. As such, the eSIM profile management capability is something that can be supported by integrating with the Windows OMA-DM. This characteristic makes it possible to remotely manage the eSIM profiles according to the company policies. As an MDM provider, if you are looking to integrate/onboard to a mobile operator on a 1:1 basis, contact them and learn more about their onboarding. If you would like to integrate and work with only one MDM provider, contact that provider directly. If you would like to offer eSIM management to customers using different MDM providers, contact an orchestrator provider. Orchestrator providers act as proxy handling MDM onboarding and as a mobile operator onboarding. Their role is to make the process as painless and scalable as possible for all parties. Potential orchestrator providers you could contact include:
|
||||
- [HPE Device Entitlement Gateway](https://www.hpe.com/emea_europe/en/solutions/digital-communications-services.html)
|
||||
- [IDEMIA The Smart Connect - Hub](https://www.idemia.com/smart-connect-hub)
|
||||
- [HPE Device Entitlement Gateway](https://www.hpe.com/emea_europe/en/solutions/digital-communications-services.html)
|
||||
- [IDEMIA The Smart Connect - Hub](https://www.idemia.com/smart-connect-hub)
|
||||
- Assess solution type that you would like to provide your customers
|
||||
- Batch/offline solution
|
||||
- IT Admin can manually import a flat file containing list of eSIM activation codes, and provision eSIM on LTE enabled devices.
|
||||
@ -28,4 +30,6 @@ The eSIM Profile Management Solution places the Mobile Device Management (MDM) P
|
||||
- Real-time solution
|
||||
- MDM automatically syncs with the Operator backend system for subscription pool and eSIM management, via sim vendor solution component. IT Admin can view subscription pool and provision eSIM in real time.
|
||||
- Operator is notified of the status of each eSIM profile and has visibility on which devices are being used
|
||||
**Note:** End users don't notice the solution type. The choice between the two is made between the MDM and the Mobile Operator.
|
||||
|
||||
> [!NOTE]
|
||||
> End users don't notice the solution type. The choice between the two is made between the MDM and the Mobile Operator.
|
||||
|
@ -37,7 +37,7 @@ landingContent:
|
||||
- text: Enterprise settings, policies, and app management
|
||||
url: windows-mdm-enterprise-settings.md
|
||||
- text: Windows Tools/Administrative Tools
|
||||
url: client-tools/administrative-tools-in-windows-10.md
|
||||
url: client-tools/administrative-tools-in-windows.md
|
||||
- text: Create mandatory user profiles
|
||||
url: client-tools/mandatory-user-profile.md
|
||||
|
||||
|
@ -1,43 +0,0 @@
|
||||
---
|
||||
title: Manage corporate devices
|
||||
description: You can use the same management tools to manage all device types running Windows.
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
ms.author: vinpa
|
||||
ms.prod: windows-client
|
||||
author: vinaypamnani-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/14/2021
|
||||
ms.topic: article
|
||||
ms.technology: itpro-manage
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
---
|
||||
|
||||
# Manage corporate devices
|
||||
|
||||
You can use the same management tools to manage all Windows devices. And your current management tools, such as Group Policy, Windows Management Instrumentation (WMI), PowerShell scripts, and so on, will continue to work for Windows 10 and Windows 11.
|
||||
|
||||
## In this section
|
||||
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [Manage Windows in your organization - transitioning to modern management](manage-windows-10-in-your-organization-modern-management.md) | Strategies for deploying and managing Windows devices, including deploying Windows in a mixed environment |
|
||||
| [Connect to remote Azure Active Directory-joined PC](client-tools/connect-to-remote-aadj-pc.md) | How to use Remote Desktop Connection to connect to an Azure AD-joined PC |
|
||||
| [Manage Windows and Microsoft Store tips, tricks, and suggestions](/windows/configuration/manage-tips-and-suggestions) | Options to manage user experiences to provide a consistent and predictable experience for employees |
|
||||
| [New policies for Windows](client-tools/new-policies-for-windows-10.md) | New Group Policy settings added in Windows |
|
||||
| [Group Policies that apply only to Windows Enterprise and Windows Education](client-tools/group-policies-for-enterprise-and-education-editions.md) | Group Policy settings that apply only to Windows Enterprise and Education |
|
||||
| [Introduction to configuration service providers (CSPs) for IT pros](/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers) | How IT pros and system administrators can take advantage of many settings available through CSPs to configure devices running Windows in their organizations |
|
||||
|
||||
## Learn more
|
||||
|
||||
[How to bulk-enroll devices with On-premises Mobile Device Management in Microsoft Configuration Manager](/mem/configmgr/mdm/deploy-use/bulk-enroll-devices-on-premises-mdm)
|
||||
|
||||
[Azure AD, Microsoft Intune and Windows - Using the cloud to modernize enterprise mobility](https://blogs.technet.microsoft.com/enterprisemobility/2015/06/12/azure-ad-microsoft-intune-and-windows-10-using-the-cloud-to-modernize-enterprise-mobility/)
|
||||
|
||||
[Microsoft Intune End User Enrollment Guide](/samples/browse/?redirectedfrom=TechNet-Gallery)
|
||||
|
||||
[Windows and Azure Active Directory: Embracing the Cloud](https://go.microsoft.com/fwlink/p/?LinkId=615768)
|
||||
|
||||
Microsoft Virtual Academy course: [Configuration Manager & Windows Intune](/training/)
|
Loading…
x
Reference in New Issue
Block a user