update manager alias

This commit is contained in:
Aaron Czechowski
2025-06-03 16:47:25 -07:00
parent 4dca10ac5f
commit 51d668848a
277 changed files with 981 additions and 985 deletions

View File

@ -3,14 +3,14 @@ title: Remove background task resource restrictions
description: Allow enterprise background tasks unrestricted access to computer resources.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 10/03/2017
ms.topic: article
ms.service: windows-client
ms.subservice: itpro-apps
ms.localizationpriority: medium
ms.collection: tier2
ms.reviewer:
ms.reviewer:
---
# Remove background task resource restrictions

View File

@ -1,7 +1,7 @@
---
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 09/20/2021
ms.topic: include
ms.service: windows-client

View File

@ -1,15 +1,11 @@
---
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 09/28/2021
manager: aaroncz
ms.topic: include
ms.service: windows-client
ms.subservice: itpro-apps
ms.localizationpriortiy: medium
ms.collection: tier1
ms.reviewer:
---
**Applies to**:

View File

@ -8,7 +8,7 @@ metadata:
description: Learn about managing applications in Windows client.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 09/27/2024
ms.topic: landing-page
ms.service: windows-client

View File

@ -3,7 +3,7 @@ title: Overview of apps on Windows client devices
description: Learn about the different types of apps that run on Windows. For example, Universal Windows Platform (UWP), Windows Presentation Foundation (WPF), Win32, and Windows Forms apps. This article also includes the best way to install these apps.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 09/03/2024
ms.topic: overview
ms.service: windows-client

View File

@ -3,7 +3,7 @@ title: Per-user services
description: Learn about per-user services, how to change the template service startup type, and manage per-user services through group policy and security templates.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 10/01/2024
ms.topic: how-to
ms.service: windows-client

View File

@ -3,7 +3,7 @@ title: Use the Company Portal app for your private app repo on Windows 11 device
description: Use the Company Portal app in Windows 11 devices to access the private app repository for your organization or company apps. Add apps to an MDM/MAM provider, and deploy the apps to Windows devices using policies. The Company Portal app replaces Microsoft Store for Business private store on Windows 11 devices.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 09/03/2023
ms.topic: article
ms.service: windows-client
@ -57,7 +57,7 @@ To install the Company Portal app, you have some options:
- When the Company Portal app is installed from the Microsoft Store app, by default, it's automatically updated. Users can also open the Microsoft Store app, go to the **Library**, and check for updates.
For more information, see:
- [Endpoint Management at Microsoft](/mem/endpoint-manager-overview)
- [Add Microsoft Store apps to Microsoft Intune](/mem/intune/apps/store-apps-microsoft)
- [What is co-management?](/mem/configmgr/comanage/overview)
@ -70,7 +70,7 @@ To install the Company Portal app, you have some options:
- When the Company Portal app is installed from the Microsoft Store app, by default, it's automatically updated. Users can also open the Microsoft Store app, go to the **Library**, and check for updates.
For more information, see:
- [What is Windows Autopilot](/mem/autopilot/windows-autopilot)
- [Add and assign the Company Portal app for Autopilot provisioned devices](/mem/intune/apps/store-apps-company-portal-autopilot)

View File

@ -3,7 +3,7 @@ title: Keep removed apps from returning during an update
description: When you remove provisioned apps from devices, this article explains how to keep those apps from returning during an update.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 05/25/2018
ms.topic: how-to
ms.service: windows-client
@ -171,7 +171,7 @@ Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned\Microsoft.HEVCVideoExtension_8wekyb3d8bbwe]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned\Microsoft.Messaging_8wekyb3d8bbwe]
```
```
[Get-AppxPackage](/powershell/module/appx/get-appxpackage)
[Get-AppxPackage -allusers](/powershell/module/appx/get-appxpackage)

View File

@ -3,7 +3,7 @@ title: Sideload line of business apps
description: Learn how to sideload line-of-business (LOB) apps in Windows client operating systems. When you sideload an app, you deploy a signed app package to a device.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 09/27/2024
ms.topic: how-to
ms.service: windows-client

View File

@ -3,7 +3,7 @@ title: Service host grouping in Windows 10
description: Learn about the Service Host (SvcHost) service refactoring introduced in Windows 10 version 1703.
author: aczechowski
ms.author: aaroncz
manager: aaroncz
manager: bpardi
ms.date: 07/20/2017
ms.topic: concept-article
ms.service: windows-client
@ -22,19 +22,19 @@ The **Service Host (svchost.exe)** is a shared-service process that serves as a
* Local Service No Network
* Local Service Network Restricted
* Local System
* Local System Network Restricted
* Local System Network Restricted
* Network Service
## Separating SvcHost services
Beginning with Windows 10 Creators Update (version 1703), services that were previously grouped will instead be separated - each will run in its own SvcHost process. This change is automatic for systems with **more than 3.5 GB** of RAM running the Client Desktop SKU. On systems with 3.5 GB or less RAM, we'll continue to group services into a shared SvcHost process.
Beginning with Windows 10 Creators Update (version 1703), services that were previously grouped will instead be separated - each will run in its own SvcHost process. This change is automatic for systems with **more than 3.5 GB** of RAM running the Client Desktop SKU. On systems with 3.5 GB or less RAM, we'll continue to group services into a shared SvcHost process.
Benefits of this design change include:
* Increased reliability by insulating critical network services from the failure of another non-network service in the host, and adding the ability to restore networking connectivity seamlessly when networking components crash.
* Reduced support costs by eliminating the troubleshooting overhead associated with isolating misbehaving services in the shared host.
* Increased security by providing more inter-service isolation
* Increased scalability by allowing per-service settings and privileges
* Increased security by providing more inter-service isolation
* Increased scalability by allowing per-service settings and privileges
* Improved resource management through per-service CPU, I/O and memory management and increase clear diagnostic data (report CPU, I/O and network usage per service).
>**Try This**
@ -48,19 +48,19 @@ Refactoring also makes it easier to view running processes in Task Manager. You
For example, here are the running processes displayed in Task Manager in Windows 10 version 1607:
![Running processes in Task Manager, version 1607.](media/svchost-grouped-processes.png)
![Running processes in Task Manager, version 1607.](media/svchost-grouped-processes.png)
Compare that to the same view of running processes in Windows 10 version 1703:
![Running processes in Task Manager, version 1703.](media/svchost-separated-processes.png)
## Exceptions
Some services will continue to be grouped on PCs running with 3.5 GB or higher RAM. For example, the Base Filtering Engine (BFE) and the Windows Firewall (Mpssvc) will be grouped together in a single host group, as will the RPC Endpoint Mapper and Remote Procedure Call services.
If you need to identify services that will continue to be grouped, in addition to seeing them in Task Manager and using command line tools, you can look for the *SvcHostSplitDisable* value in their respective service keys under
If you need to identify services that will continue to be grouped, in addition to seeing them in Task Manager and using command line tools, you can look for the *SvcHostSplitDisable* value in their respective service keys under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
The default value of **1** prevents the service from being split.
@ -70,19 +70,19 @@ For example, the registry key configuration for BFE is:
## Memory footprint
Separating services increases the total number of SvcHost instances, which increases memory utilization. (Service grouping provided a modest reduction to the overall resource footprint of the services involved.)
Separating services increases the total number of SvcHost instances, which increases memory utilization. (Service grouping provided a modest reduction to the overall resource footprint of the services involved.)
Consider the following example:
|Grouped Services (< 3.5 GB) | Split Services (3.5 GB+)
|--------------------------------------- | ------------------------------------------ |
|--------------------------------------- | ------------------------------------------ |
|![Memory utilization for grouped services.](media/svchost-grouped-utilization.png) |![Memory utilization for separated services](media/svchost-separated-utilization.png) |
> [!NOTE]
> The above represents the peak observed values.
The total number of service instances and the resulting memory utilization varies depending on activity. Instance counts can typically range from approximately 17-21 for grouped services, and 67-74 for separated services.
The total number of service instances and the resulting memory utilization varies depending on activity. Instance counts can typically range from approximately 17-21 for grouped services, and 67-74 for separated services.
> **Try This**
>