mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 03:43:39 +00:00
Merge branch 'public' into patch-6
This commit is contained in:
Daniel Simpson
GitHub
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: article
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
author: msfttracyp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 04/26/2018
|
||||
|
||||
@ -42,7 +42,7 @@ Previous versions of App-V have required you to manually remove your unpublished
|
||||
|
||||
### App-V is now a feature in Windows 10
|
||||
|
||||
With Windows 10, version 1607 and later releases, App-V is now included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
|
||||
With Windows 10, version 1607 and later releases, App-V is now included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
|
||||
|
||||
To learn more about earlier versions of App-V, see [MDOP Information Experience](https://docs.microsoft.com/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
|
||||
@ -346,7 +346,7 @@ This process will recreate both the local and network locations for AppData and
|
||||
|
||||
In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers through the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are input as PowerShell commands on the computer running the App-V Client.
|
||||
|
||||
This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012, see [Integrating Virtual Application Management with App-V 5 and Configuration Manager 2012 SP1](https://www.microsoft.com/en-us/download/details.aspx?id=38177).
|
||||
This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012, see [Integrating Virtual Application Management with App-V 5 and Configuration Manager 2012 SP1](https://www.microsoft.com/download/details.aspx?id=38177).
|
||||
|
||||
The App-V application lifecycle tasks are triggered at user sign in (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured (after the client is enabled) with Windows PowerShell commands. See [App-V Client Configuration Settings: Windows PowerShell](appv-client-configuration-settings.md#app-v-client-configuration-settings-windows-powershell).
|
||||
|
||||
@ -799,7 +799,7 @@ App-V packages contain the Manifest file inside of the App-V Package file, which
|
||||
|
||||
### Examples of dynamic configuration files
|
||||
|
||||
The following example shows the combination of the Manifest, Deployment Configuration, and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is show the combination of the files only, not to be a complete description of the specific categories available in each file. For more information, download the [App-V Sequencing Guide](https://www.microsoft.com/en-us/download/details.aspx?id=27760).
|
||||
The following example shows the combination of the Manifest, Deployment Configuration, and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is show the combination of the files only, not to be a complete description of the specific categories available in each file. For more information, download the [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760).
|
||||
|
||||
#### Manifest
|
||||
|
||||
|
||||
@ -62,5 +62,5 @@ Using Group Policy, you can turn on the **Enable automatic cleanup of unused App
|
||||
## Related topics
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186)
|
||||
- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/download/details.aspx?id=41186)
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 06/25/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# About the connection group virtual environment
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to convert a package created in a previous version of App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to create a connection croup with user-published and globally published packages
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to create a connection group
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to create a custom configuration file by using the App-V Management Console
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to create a package accelerator by using Windows PowerShell
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to create a package accelerator
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to create a virtual application package using an App-V Package Accelerator
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Create and apply an App-V project template to a sequenced App-V package
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Creating and managing App-V virtualized applications
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 07/10/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to customize virtual applications extensions for a specific AD group by using the Management Console
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to delete a connection group
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to delete a package in the Management Console
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to deploy the App-V databases by using SQL scripts
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to deploy the App-V server using a script
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
@ -32,7 +32,7 @@ ms.topic: article
|
||||
1. Download the App-V server components. All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
|
||||
|
||||
* The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home).
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
2. Copy the App-V server installation files to the computer on which you want to install it.
|
||||
3. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
|
||||
4. Review and accept the license terms, and choose whether to enable Microsoft updates.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying App-V for Windows 10
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
@ -86,7 +86,7 @@ The following table provides a full list of supported integration points for Off
|
||||
|
||||
### Office 2010 App-V Packages
|
||||
|
||||
* [Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/en-us/download/details.aspx?id=38399)
|
||||
* [Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/download/details.aspx?id=38399)
|
||||
* [Known issues when you create or use an App-V 5.0 Office 2010 package](https://support.microsoft.com/kb/2828619)
|
||||
* [How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://support.microsoft.com/kb/2830069)
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying Microsoft Office 2016 by using App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying App-V packages by using electronic software distribution (ESD)
|
||||
@ -30,7 +30,7 @@ To learn how to configure the App-V client to enable only administrators to publ
|
||||
|
||||
## Related topics
|
||||
|
||||
- [App-V and Citrix integration](https://www.microsoft.com/en-us/download/details.aspx?id=40885)
|
||||
- [App-V and Citrix integration](https://www.microsoft.com/download/details.aspx?id=40885)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying the App-V Sequencer and configuring the client
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying the App-V server
|
||||
@ -45,7 +45,7 @@ App-V offers the following five server components, each of which serves a specif
|
||||
All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
|
||||
|
||||
* The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home).
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
|
||||
In large organizations, you might want to install more than one instance of the server components to get the following benefits.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# App-V Deployment Checklist
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# About App-V dynamic configuration
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to enable only administrators to publish packages by using an ESD
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to Enable Reporting on the App-V Client by Using Windows PowerShell
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Enable the App-V in-box client
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Application Virtualization (App-V) for Windows 10 overview
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Getting started with App-V for Windows 10
|
||||
@ -18,7 +18,7 @@ ms.topic: article
|
||||
|
||||
Microsoft Application Virtualization (App-V) for Windows 10 delivers Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service in real time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
|
||||
|
||||
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise). If you're new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. To learn what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/WindowsForBusiness/windows-for-enterprise). If you're new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. To learn what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
|
||||
If you’re already using App-V, performing an in-place upgrade to Windows 10 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md).
|
||||
|
||||
@ -35,13 +35,13 @@ To start using App-V to deliver virtual applications to users, you’ll need to
|
||||
|
||||
| Component | What it does | Where to find it |
|
||||
|------------|--|------|
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For more details, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).<br><br>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package that can be downloaded from the following locations:<br><br> If you have a Microsoft Developer Network (MSDN) subscription, use the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215) to download the MDOP ISO package.<br><br> If you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home), download it from the [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx).<br><br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components.|
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For more details, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).<br><br>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package that can be downloaded from the following locations:<br><br> If you have a Microsoft Developer Network (MSDN) subscription, use the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215) to download the MDOP ISO package.<br><br> If you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home), download it from the [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx).<br><br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components.|
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices, allowing users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10, version 1607. <br><br>To learn how to enable the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must run the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows 10, version 1607](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). |
|
||||
|
||||
For more information about these components, see [High Level Architecture for App-V](appv-high-level-architecture.md).
|
||||
|
||||
If you're new to App-V, it's a good idea to read the documentation thoroughly. Before deploying App-V in a production environment, you can ensure installation goes smoothly by validating your deployment plan in a test network environment. You might also consider taking a class about relevant technologies. To get started, see the [Microsoft Training Overview](https://www.microsoft.com/en-us/learning/default.aspx).
|
||||
If you're new to App-V, it's a good idea to read the documentation thoroughly. Before deploying App-V in a production environment, you can ensure installation goes smoothly by validating your deployment plan in a test network environment. You might also consider taking a class about relevant technologies. To get started, see the [Microsoft Training Overview](https://www.microsoft.com/learning/default.aspx).
|
||||
|
||||
## Getting started with App-V
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# High-level architecture for App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to install the publishing server on a remote computer
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to install the reporting server on a standalone computer and connect it to the database
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Install the App-V Sequencer
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to load the Windows PowerShell cmdlets for App-V and get cmdlet help
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Maintaining App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/24/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to manage App-V packages running on a stand-alone computer by using Windows PowerShell
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Operations for App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ You should read and understand the following information before reading this doc
|
||||
|
||||
- [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
|
||||
|
||||
- [App-V Sequencing Guide](https://www.microsoft.com/en-us/download/details.aspx?id=27760)
|
||||
- [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760)
|
||||
|
||||
**Note**
|
||||
Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk <strong>*</strong> review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# App-V Planning Checklist
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning to Use Folder Redirection with App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning for the App-V server deployment
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning for App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning for high availability with App-V Server
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning for deploying App-V with Office
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning to Deploy App-V for Windows 10
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Preparing your environment for App-V
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/18/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# App-V for Windows 10 prerequisites
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to Publish a Connection Group
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 09/27/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# How to publish a package by using the Management console
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
# Release Notes for App-V for Windows 10, version 1607
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/16/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# About App-V reporting
|
||||
@ -30,7 +30,7 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
|
||||
To confirm SQL Server Reporting Services is running, enter <https://localhost/Reports> in a web browser as administrator on the server that will host App-V Reporting. The SQL Server Reporting Services Home page should appear.
|
||||
2. Install the App-V reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
|
||||
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at [Application Virtualization SSRS Reports](https://www.microsoft.com/en-us/download/details.aspx?id=42630).
|
||||
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at [Application Virtualization SSRS Reports](https://www.microsoft.com/download/details.aspx?id=42630).
|
||||
|
||||
> [!NOTE]
|
||||
>If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 03/08/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/16/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# App-V security considerations
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/16/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/16/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
# App-V Supported Configurations
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
# Upgrading to App-V for Windows 10 from an existing installation
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ This topic provides information about using the Application Virtualization (App-
|
||||
|
||||
## Obtain the client management console
|
||||
|
||||
The client management console is separate from the App-V client itself. You can download the client management console from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41186).
|
||||
The client management console is separate from the App-V client itself. You can download the client management console from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=41186).
|
||||
|
||||
> [!NOTE]
|
||||
> To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: lomayor
|
||||
ms.author: dansimp
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mobile
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
author: msfttracyp
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: msfttracyp
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 10/24/2017
|
||||
ms.reviewer:
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mobile
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
author: msfttracyp
|
||||
ms.date: 07/21/2017
|
||||
ms.reviewer:
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
author: msfttracyp
|
||||
title: Remove background task resource restrictions
|
||||
description: Allow enterprise background tasks unrestricted access to computer resources.
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
ms.date: 10/03/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -4,9 +4,9 @@ description: Windows 10 application management
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
manager: dansimp
|
||||
author: dansimp
|
||||
ms.localizationpriority: high
|
||||
ms.date: 09/26/2017
|
||||
---
|
||||
|
||||
# Windows 10 application management
|
||||
|
||||
@ -9,7 +9,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
author: msfttracyp
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.date: 12/03/2018
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Per-user services in Windows 10 and Windows Server
|
||||
title: Per-user services in Windows 10 and Windows Server
|
||||
description: Learn about per-user services introduced in Windows 10.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mobile
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
author: msfttracyp
|
||||
ms.date: 09/14/2017
|
||||
ms.reviewer:
|
||||
@ -92,7 +92,7 @@ Revision=1
|
||||
|
||||
If a per-user service can't be disabled using a the security template, you can disable it by using Group Policy preferences.
|
||||
|
||||
1. On a Windows Server domain controller or Windows 10 PC that has the [Remote Server Administration Tools (RSAT)](https://www.microsoft.com/en-us/download/details.aspx?id=45520) installed, click **Start**, type GPMC.MSC, and then press **Enter** to open the **Group Policy Management Console**.
|
||||
1. On a Windows Server domain controller or Windows 10 PC that has the [Remote Server Administration Tools (RSAT)](https://www.microsoft.com/download/details.aspx?id=45520) installed, click **Start**, type GPMC.MSC, and then press **Enter** to open the **Group Policy Management Console**.
|
||||
|
||||
2. Create a new Group Policy Object (GPO) or use an existing GPO.
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: How to keep provisioned apps that were removed from your machine fr
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
author: msfttracyp
|
||||
ms.date: 05/25/2018
|
||||
ms.reviewer:
|
||||
|
||||
@ -4,7 +4,7 @@ description: Sideload line-of-business apps in Windows 10.
|
||||
ms.assetid: C46B27D0-375B-4F7A-800E-21595CF1D53D
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -5,7 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mobile
|
||||
ms.author: tracyp
|
||||
ms.author: dansimp
|
||||
author: msfttracyp
|
||||
ms.date: 07/20/2017
|
||||
ms.reviewer:
|
||||
|
||||
@ -22,6 +22,10 @@
|
||||
##### [Troubleshoot port exhaustion](troubleshoot-tcpip-port-exhaust.md)
|
||||
##### [Troubleshoot Remote Procedure Call (RPC) errors](troubleshoot-tcpip-rpc-errors.md)
|
||||
### [Advanced troubleshooting for Windows startup](troubleshoot-windows-startup.md)
|
||||
#### [How to determine the appropriate page file size for 64-bit versions of Windows](determine-appropriate-page-file-size.md)
|
||||
#### [Generate a kernel or complete crash dump](generate-kernel-or-complete-crash-dump.md)
|
||||
#### [Introduction to the page file](introduction-page-file.md)
|
||||
#### [Configure system failure and recovery options in Windows](system-failure-recovery-options.md)
|
||||
#### [Advanced troubleshooting for Windows boot problems](advanced-troubleshooting-boot-problems.md)
|
||||
#### [Advanced troubleshooting for Windows-based computer freeze](troubleshoot-windows-freeze.md)
|
||||
#### [Advanced troubleshooting for stop error or blue screen error](troubleshoot-stop-errors.md)
|
||||
|
||||
@ -14,8 +14,8 @@ ms.topic: troubleshooting
|
||||
|
||||
# Advanced troubleshooting for Windows boot problems
|
||||
|
||||
>[!NOTE]
|
||||
>This article is intended for use by support agents and IT professionals. If you're looking for more general information about recovery options, see [Recovery options in Windows 10](https://support.microsoft.com/help/12415).
|
||||
> [!NOTE]
|
||||
> This article is intended for use by support agents and IT professionals. If you're looking for more general information about recovery options, see [Recovery options in Windows 10](https://support.microsoft.com/help/12415).
|
||||
|
||||
## Summary
|
||||
|
||||
@ -58,14 +58,14 @@ Here is a summary of the boot sequence, what will be seen on the display, and ty
|
||||
|
||||
Each phase has a different approach to troubleshooting. This article provides troubleshooting techniques for problems that occur during the first three phases.
|
||||
|
||||
>[!NOTE]
|
||||
>If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle:
|
||||
> [!NOTE]
|
||||
> If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle:
|
||||
>
|
||||
>`Bcdedit /set {default} recoveryenabled no`
|
||||
> `Bcdedit /set {default} recoveryenabled no`
|
||||
>
|
||||
>If the F8 options don't work, run the following command:
|
||||
> If the F8 options don't work, run the following command:
|
||||
>
|
||||
>`Bcdedit /set {default} bootmenupolicy legacy`
|
||||
> `Bcdedit /set {default} bootmenupolicy legacy`
|
||||
|
||||
|
||||
## BIOS phase
|
||||
@ -98,11 +98,10 @@ The Startup Repair tool automatically fixes many common problems. The tool also
|
||||
|
||||
To do this, follow these steps.
|
||||
|
||||
>[!NOTE]
|
||||
>For additional methods to start WinRE, see [Entry points into WinRE](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre).
|
||||
> [!NOTE]
|
||||
> For additional methods to start WinRE, see [Windows Recovery Environment (Windows RE)](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference#span-identrypointsintowinrespanspan-identrypointsintowinrespanspan-identrypointsintowinrespanentry-points-into-winre).
|
||||
|
||||
1. Start the system to the installation media for the installed version of Windows.
|
||||
**Note** For more information, see [Create installation media for Windows](https://support.microsoft.com/help/15088).
|
||||
1. Start the system to the installation media for the installed version of Windows. For more information, see [Create installation media for Windows](https://support.microsoft.com/help/15088).
|
||||
|
||||
2. On the **Install Windows** screen, select **Next** > **Repair your computer**.
|
||||
|
||||
@ -132,8 +131,8 @@ To repair the boot sector, run the following command:
|
||||
BOOTREC /FIXBOOT
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>Running **BOOTREC** together with **Fixmbr** overwrites only the master boot code. If the corruption in the MBR affects the partition table, running **Fixmbr** may not fix the problem.
|
||||
> [!NOTE]
|
||||
> Running **BOOTREC** together with **Fixmbr** overwrites only the master boot code. If the corruption in the MBR affects the partition table, running **Fixmbr** may not fix the problem.
|
||||
|
||||
### Method 3: Fix BCD errors
|
||||
|
||||
@ -152,20 +151,25 @@ If you receive BCD-related errors, follow these steps:
|
||||
```
|
||||
|
||||
4. You might receive one of the following outputs:
|
||||
|
||||
- Scanning all disks for Windows installations. Please wait, since this may take a while...Successfully scanned Windows installations. Total identified Windows installations: 0
|
||||
```dos
|
||||
Scanning all disks for Windows installations. Please wait, since this may take a while ...
|
||||
Successfully scanned Windows installations. Total identified Windows installations: 0
|
||||
The operation completed successfully.
|
||||
```
|
||||
|
||||
- Scanning all disks for Windows installations. Please wait, since this may take a while... Successfully scanned Windows installations. Total identified Windows installations: 1
|
||||
```dos
|
||||
Scanning all disks for Windows installations. Please wait, since this may take a while ...
|
||||
Successfully scanned Windows installations. Total identified Windows installations: 1
|
||||
D:\Windows
|
||||
Add installation to boot list? Yes/No/All:
|
||||
```
|
||||
|
||||
If the output shows **windows installation: 0**, run the following commands:
|
||||
|
||||
```dos
|
||||
bcdedit /export c:\bcdbackup
|
||||
|
||||
attrib c:\\boot\\bcd -h -r –s
|
||||
attrib c:\\boot\\bcd -r –s -h
|
||||
|
||||
ren c:\\boot\\bcd bcd.old
|
||||
|
||||
@ -174,39 +178,41 @@ bootrec /rebuildbcd
|
||||
|
||||
After you run the command, you receive the following output:
|
||||
|
||||
Scanning all disks for Windows installations. Please wait, since this may take a while...Successfully scanned Windows installations. Total identified Windows installations: 1{D}:\Windows
|
||||
```dos
|
||||
Scanning all disks for Windows installations. Please wait, since this may take a while ...
|
||||
Successfully scanned Windows installations. Total identified Windows installations: 1
|
||||
{D}:\Windows
|
||||
Add installation to boot list? Yes/No/All: Y
|
||||
```
|
||||
|
||||
5. Try again to start the system.
|
||||
5. Try restarting the system.
|
||||
|
||||
### Method 4: Replace Bootmgr
|
||||
|
||||
If methods 1 and 2 do not fix the problem, replace the Bootmgr file from drive C to the System Reserved partition. To do this, follow these steps:
|
||||
If methods 1, 2 and 3 do not fix the problem, replace the Bootmgr file from drive C to the System Reserved partition. To do this, follow these steps:
|
||||
|
||||
1. At a command prompt, change the directory to the System Reserved partition.
|
||||
|
||||
2. Run the **attrib** command to unhide the file:
|
||||
```dos
|
||||
attrib-s -h -r
|
||||
attrib -r -s -h
|
||||
```
|
||||
|
||||
3. Run the same **attrib** command on the Windows (system drive):
|
||||
```dos
|
||||
attrib-s -h –r
|
||||
attrib -r -s -h
|
||||
```
|
||||
|
||||
4. Rename the Bootmgr file as Bootmgr.old:
|
||||
```dos
|
||||
ren c:\\bootmgr bootmgr.old
|
||||
ren c:\bootmgr bootmgr.old
|
||||
```
|
||||
|
||||
5. Start a text editor, such as Notepad.
|
||||
5. Navigate to the system drive.
|
||||
|
||||
6. Navigate to the system drive.
|
||||
6. Copy the Bootmgr file, and then paste it to the System Reserved partition.
|
||||
|
||||
7. Copy the Bootmgr file, and then paste it to the System Reserved partition.
|
||||
|
||||
8. Restart the computer.
|
||||
7. Restart the computer.
|
||||
|
||||
### Method 5: Restore System Hive
|
||||
|
||||
@ -267,16 +273,16 @@ For detailed instructions, see [How to perform a clean boot in Windows](https://
|
||||
If the computer starts in Disable Driver Signature mode, start the computer in Disable Driver Signature Enforcement mode, and then follow the steps that are documented in the following article to determine which drivers or files require driver signature enforcement:
|
||||
[Troubleshooting boot problem caused by missing driver signature (x64)](https://blogs.technet.microsoft.com/askcore/2012/04/15/troubleshooting-boot-issues-due-to-missing-driver-signature-x64/)
|
||||
|
||||
>[!NOTE]
|
||||
>If the computer is a domain controller, try Directory Services Restore mode (DSRM).
|
||||
> [!NOTE]
|
||||
> If the computer is a domain controller, try Directory Services Restore mode (DSRM).
|
||||
>
|
||||
>This method is an important step if you encounter Stop error "0xC00002E1" or "0xC00002E2"
|
||||
> This method is an important step if you encounter Stop error "0xC00002E1" or "0xC00002E2"
|
||||
|
||||
|
||||
**Examples**
|
||||
|
||||
>[!WARNING]
|
||||
>Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these
|
||||
> [!WARNING]
|
||||
> Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these
|
||||
problems can be solved. Modify the registry at your own risk.
|
||||
|
||||
*Error code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)*
|
||||
@ -307,11 +313,11 @@ For additional troubleshooting steps, see the following articles:
|
||||
|
||||
To fix problems that occur after you install Windows updates, check for pending updates by using these steps:
|
||||
|
||||
1. Open a Command Prompt winodw in WinRE.
|
||||
1. Open a Command Prompt window in WinRE.
|
||||
|
||||
2. Run the command:
|
||||
```dos
|
||||
dism /image:C:\ /get-packages
|
||||
DISM /image:C:\ /get-packages
|
||||
```
|
||||
|
||||
3. If there are any pending updates, uninstall them by running the following commands:
|
||||
@ -319,7 +325,7 @@ To fix problems that occur after you install Windows updates, check for pending
|
||||
DISM /image:C:\ /remove-package /packagename: name of the package
|
||||
```
|
||||
```dos
|
||||
Dism /Image:C:\ /Cleanup-Image /RevertPendingActions
|
||||
DISM /Image:C:\ /Cleanup-Image /RevertPendingActions
|
||||
```
|
||||
|
||||
Try to start the computer.
|
||||
|
||||
@ -0,0 +1,129 @@
|
||||
---
|
||||
title: How to determine the appropriate page file size for 64-bit versions of Windows
|
||||
description: Learn how to determine the appropriate page file size for 64-bit versions of Windows.
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
ms.topic: troubleshooting
|
||||
author: Deland-Han
|
||||
ms.localizationpriority: medium
|
||||
ms.author: delhan
|
||||
ms.date: 8/28/2019
|
||||
ms.reviewer:
|
||||
manager: dcscontentpm
|
||||
---
|
||||
|
||||
# How to determine the appropriate page file size for 64-bit versions of Windows
|
||||
|
||||
Page file sizing depends on the system crash dump setting requirements and the peak usage or expected peak usage of the system commit charge. Both considerations are unique to each system, even for systems that are identical. This means that page file sizing is also unique to each system and cannot be generalized.
|
||||
|
||||
## Determine the appropriate page file size
|
||||
|
||||
Use the following considerations for page file sizing for all versions of Windows and Windows Server.
|
||||
|
||||
### Crash dump setting
|
||||
|
||||
If you want a crash dump file to be created during a system crash, a page file or a dedicated dump file must exist and be large enough to back up the system crash dump setting. Otherwise, a system memory dump file is not created.
|
||||
|
||||
For more information, see [Support for system crash dumps](introduction-page-file.md#support-for-system-crash-dumps) section.
|
||||
|
||||
### Peak system commit charge
|
||||
|
||||
The system commit charge cannot exceed the system commit limit. This limit is the sum of physical memory (RAM) and all page files combined. If no page files exist, the system commit limit is slightly less than the physical memory that is installed. Peak system-committed memory usage can vary greatly between systems. Therefore, physical memory and page file sizing also vary.
|
||||
|
||||
### Quantity of infrequently accessed pages
|
||||
|
||||
The purpose of a page file is to *back* (support) infrequently accessed modified pages so that they can be removed from physical memory. This provides more available space for more frequently accessed pages. The "\Memory\Modified Page List Bytes" performance counter measures, in part, the number of infrequently accessed modified pages that are destined for the hard disk. However, be aware that not all the memory on the modified page list is written out to disk. Typically, several hundred megabytes of memory remains resident on the modified list. Therefore, consider extending or adding a page file if all the following conditions are true:
|
||||
|
||||
- More available physical memory (\Memory\Available MBytes) is required.
|
||||
|
||||
- The modified page list contains a significant amount of memory.
|
||||
|
||||
- The existing page files are fairly full (\Paging Files(*)\% Usage).
|
||||
|
||||
## Support for system crash dumps
|
||||
|
||||
A system crash (also known as a “bug check” or a "Stop error") occurs when the system cannot run correctly. The dump file that is produced from this event is called a system crash dump. A page file or dedicated dump file is used to write a crash dump file (Memory.dmp) to disk. Therefore, a page file or a dedicated dump file must be large enough to support the kind of crash dump selected. Otherwise, the system cannot create the crash dump file.
|
||||
|
||||
>[!Note]
|
||||
>During startup, system-managed page files are sized respective to the system crash dump settings. This assumes that enough free disk space exists.
|
||||
|
||||
|System crash dump setting |Minimum page file size requirement|
|
||||
|-----------|-------------------|
|
||||
|Small memory dump (256 KB) |1 MB|
|
||||
|Kernel memory dump |Depends on kernel virtual memory usage|
|
||||
|Complete memory dump |1 x RAM plus 257 MB*|
|
||||
|Automatic memory dump |Depends on kernel virtual memory usage. For details, see Automatic memory dump.|
|
||||
|
||||
\* 1 MB of header data and device drivers can total 256 MB of secondary crash dump data.
|
||||
|
||||
The **Automatic memory dump** setting is enabled by default. This is a setting instead of a kind of crash dump. This setting automatically selects the best page file size, depending on the frequency of system crashes.
|
||||
|
||||
The Automatic memory dump feature initially selects a small paging file size. It would accommodate the kernel memory most of the time. If the system crashes again within four weeks, the Automatic memory dump feature sets the page file size as either the RAM size or 32 GB, whichever is smaller.
|
||||
|
||||
Kernel memory crash dumps require enough page file space or dedicated dump file space to accommodate the kernel mode side of virtual memory usage. If the system crashes again within four weeks of the previous crash, a Complete memory dump is selected at restart. This requires a page file or dedicated dump file of at least the size of physical memory (RAM) plus 1 MB for header information plus 256 MB for potential driver data to support all the potential data that is dumped from memory. Again, the system-managed page file will be increased to back this kind of crash dump. If the system is configured to have a page file or a dedicated dump file of a specific size, make sure that the size is sufficient to back the crash dump setting that is listed in the table earlier in this section together with and the peak system commit charge.
|
||||
|
||||
### Dedicated dump files
|
||||
|
||||
Computers that are running Microsoft Windows or Microsoft Windows Server usually must have a page file to support a system crash dump. System administrators now have the option to create a dedicated dump file instead.
|
||||
|
||||
A dedicated dump file is a page file that is not used for paging. Instead, it is “dedicated” to back a system crash dump file (Memory.dmp) when a system crash occurs. Dedicated dump files can be put on any disk volume that can support a page file. We recommend that you use a dedicated dump file if you want a system crash dump but you do not want a page file.
|
||||
|
||||
## System-managed page files
|
||||
|
||||
By default, page files are system-managed. This means that the page files increase and decrease based on many factors, such as the amount of physical memory installed, the process of accommodating the system commit charge, and the process of accommodating a system crash dump.
|
||||
|
||||
For example, when the system commit charge is more than 90 percent of the system commit limit, the page file is increased to back it. This continues to occur until the page file reaches three times the size of physical memory or 4 GB, whichever is larger. This all assumes that the logical disk that is hosting the page file is large enough to accommodate the growth.
|
||||
|
||||
The following table lists the minimum and maximum page file sizes of system-managed page files in Windows 10.
|
||||
|
||||
|Minimum page file size |Maximum page file size|
|
||||
|---------------|------------------|
|
||||
|Varies based on page file usage history, amount of RAM (RAM ÷ 8, max 32 GB) and crash dump settings. |3 × RAM or 4 GB, whichever is larger. This is then limited to the volume size ÷ 8. However, it can grow to within 1 GB of free space on the volume if required for crash dump settings.|
|
||||
|
||||
## Performance counters
|
||||
|
||||
Several performance counters are related to page files. This section describes the counters and what they measure.
|
||||
|
||||
### \Memory\Page/sec and other hard page fault counters
|
||||
|
||||
The following performance counters measure hard page faults (which include, but are not limited to, page file reads):
|
||||
|
||||
- \Memory\Page/sec
|
||||
|
||||
- \Memory\Page Reads/sec
|
||||
|
||||
- \Memory\Page Inputs/sec
|
||||
|
||||
The following performance counters measure page file writes:
|
||||
|
||||
- \Memory\Page Writes/sec
|
||||
|
||||
- \Memory\Page Output/sec
|
||||
|
||||
Hard page faults are faults that must be resolved by retrieving the data from disk. Such data can include portions of DLLs, .exe files, memory-mapped files, and page files. These faults might or might not be related to a page file or to a low-memory condition. Hard page faults are a standard function of the operating system. They occur when the following items are read:
|
||||
|
||||
- Parts of image files (.dll and .exe files) as they are used
|
||||
|
||||
- Memory-mapped files
|
||||
|
||||
- A page file
|
||||
|
||||
High values for these counters (excessive paging) indicate disk access of generally 4 KB per page fault on x86 and x64 versions of Windows and Windows Server. This disk access might or might not be related to page file activity but may contribute to poor disk performance that can cause system-wide delays if the related disks are overwhelmed.
|
||||
|
||||
Therefore, we recommend that you monitor the disk performance of the logical disks that host a page file in correlation with these counters. Be aware that a system that has a sustained 100 hard page faults per second experiences 400 KB per second disk transfers. Most 7,200 RPM disk drives can handle about 5 MB per second at an IO size of 16 KB or 800 KB per second at an IO size of 4 KB. No performance counter directly measures which logical disk the hard page faults are resolved for.
|
||||
|
||||
### \Paging File(*)\% Usage
|
||||
|
||||
The \Paging File(*)\% Usage performance counter measures the percentage of usage of each page file. 100 percent usage of a page file does not indicate a performance problem as long as the system commit limit is not reached by the system commit charge, and if a significant amount of memory is not waiting to be written to a page file.
|
||||
|
||||
>[!Note]
|
||||
>The size of the Modified Page List (\Memory\Modified Page List Bytes) is the total of modified data that is waiting to be written to disk.
|
||||
|
||||
If the Modified Page List (a list of physical memory pages that are the least frequently accessed) contains lots of memory, and if the **% Usage** value of all page files is greater than 90, you can make more physical memory available for more frequently access pages by increasing or adding a page file.
|
||||
|
||||
>[!Note]
|
||||
>Not all the memory on the modified page list is written out to disk. Typically, several hundred megabytes of memory remains resident on the modified list.
|
||||
|
||||
## Multiple page files and disk considerations
|
||||
|
||||
If a system is configured to have more than one page files, the page file that responds first is the one that is used. This means that page files that are on faster disks are used more frequently. Also, whether you put a page file on a “fast” or “slow” disk is important only if the page file is frequently accessed and if the disk that is hosting the respective page file is overwhelmed. Be aware that actual page file usage depends greatly on the amount of modified memory that the system is managing. This means that files that already exist on disk (such as .txt, .doc, .dll, and .exe) are not written to a page file. Only modified data that does not already exist on disk (for example, unsaved text in Notepad) is memory that could potentially be backed by a page file. After the unsaved data is saved to disk as a file, it is backed by the disk and not by a page file.
|
||||
@ -0,0 +1,111 @@
|
||||
---
|
||||
title: Generate a kernel or complete crash dump
|
||||
description: Learn how to generate a kernel or complete crash dump.
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
ms.topic: troubleshooting
|
||||
author: Deland-Han
|
||||
ms.localizationpriority: medium
|
||||
ms.author: delhan
|
||||
ms.date: 8/28/2019
|
||||
ms.reviewer:
|
||||
manager: dcscontentpm
|
||||
---
|
||||
|
||||
# Generate a kernel or complete crash dump
|
||||
|
||||
A system crash (also known as a “bug check” or a "Stop error") occurs when Windows can't run correctly. The dump file that is produced from this event is called a system crash dump.
|
||||
|
||||
A manual kernel or complete memory dump file is useful when you troubleshoot several issues because the process captures a record of system memory at the time of a crash.
|
||||
|
||||
## Set up page files
|
||||
|
||||
See [Support for system crash dumps](determine-appropriate-page-file-size.md#support-for-system-crash-dumps) for the page file size requirement for system crash dump.
|
||||
|
||||
## Enable memory dump setting
|
||||
|
||||
You must be logged on as an administrator or a member of the Administrators group to complete this procedure. If your computer is connected to a network, network policy settings may prevent you from completing this procedure.
|
||||
|
||||
To enable memory dump setting, follow these steps:
|
||||
|
||||
1. In **Control Panel**, select **System and Security** > **System**.
|
||||
|
||||
2. Select **Advanced system settings**, and then select the **Advanced** tab.
|
||||
|
||||
3. In the **Startup and Recovery** area, select **Settings**.
|
||||
|
||||
4. Make sure that **Kernel memory dump** or **Complete memory dump** is selected under **Writing Debugging Information**.
|
||||
|
||||
5. Restart the computer.
|
||||
|
||||
>[!Note]
|
||||
>You can change the dump file path by edit the **Dump file** field. In other words, you can change the path from %SystemRoot%\Memory.dmp to point to a local drive that has enough disk space, such as E:\Memory.dmp.
|
||||
|
||||
### Tips to generate memory dumps
|
||||
|
||||
When the computer crashes and restarts, the contents of physical RAM are written to the paging file that is located on the partition on which the operating system is installed.
|
||||
|
||||
Depending on the speed of the hard disk on which Windows is installed, dumping more than 2 gigabytes (GB) of memory may take a long time. Even in a best case scenario, if the dump file is configured to reside on another local hard drive, a significant amount of data will be read and written to the hard disks. This can cause a prolonged server outage.
|
||||
|
||||
>[!Note]
|
||||
>Use this method to generate complete memory dump files with caution. Ideally, you should do this only when you are explicitly requested to by the Microsoft Support engineer. Any kernel or complete memory dump file debugging should be the last resort after all standard troubleshooting methods have been completely exhausted.
|
||||
|
||||
## Manually generate a memory dump file
|
||||
|
||||
### Use the NotMyFault tool
|
||||
|
||||
If you can log on while the problem is occurring, you can use the Microsoft Sysinternals NotMyFault tool. To do this, follow these steps:
|
||||
|
||||
1. Download the [NotMyFault](https://download.sysinternals.com/files/NotMyFault.zip) tool.
|
||||
|
||||
2. Select **Start**, and then select **Command Prompt**.
|
||||
3. At the command line, run the following command:
|
||||
|
||||
```cmd
|
||||
notMyfault.exe /crash
|
||||
```
|
||||
|
||||
>[!Note]
|
||||
>This operation generates a memory dump file and a D1 Stop error.
|
||||
|
||||
### Use NMI
|
||||
|
||||
On some computers, you cannot use keyboard to generate a crash dump file. For example, Hewlett-Packard (HP) BladeSystem servers from the Hewlett-Packard Development Company are managed through a browser-based graphical user interface (GUI). A keyboard is not attached to the HP BladeSystem server.
|
||||
|
||||
In these cases, you must generate a complete crash dump file or a kernel crash dump file by using the Non-Maskable Interrupt (NMI) switch that causes an NMI on the system processor.
|
||||
|
||||
To do this, follow these steps:
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/help/322756) in case problems occur.
|
||||
|
||||
1. In Registry Editor, locate the following registry subkey:
|
||||
**HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl**
|
||||
|
||||
2. Right-click **CrashControl**, point to **New**, and then click **DWORD Value**.
|
||||
|
||||
3. Type NMICrashDump, and then press Enter.
|
||||
|
||||
4. Right-click **NMICrashDump**, and then select **Modify**.
|
||||
|
||||
5. In the **Value data** box, type **1**, and then select **OK**.
|
||||
|
||||
6. Restart the computer.
|
||||
|
||||
7. Hardware vendors, such as HP, IBM, and Dell, may provide an Automatic System Recovery (ASR) feature. You should disable this feature during troubleshooting. For example, if the HP and Compaq ASR feature is enabled in the BIOS, disable this feature while you troubleshoot to generate a complete Memory.dmp file. For the exact steps, contact your hardware vendor.
|
||||
|
||||
8. Enable the NMI switch in the BIOS or by using the Integrated Lights Out (iLO) Web interface.
|
||||
|
||||
>[!Note]
|
||||
>For the exact steps, see the BIOS reference manual or contact your hardware vendor.
|
||||
|
||||
9. Test this method on the server by using the NMI switch to generate a dump file. You will see a STOP 0x00000080 hardware malfunction.
|
||||
|
||||
### Use the keyboard
|
||||
|
||||
[Forcing a System Crash from the Keyboard](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-keyboard)
|
||||
|
||||
### Use Debugger
|
||||
|
||||
[Forcing a System Crash from the Debugger](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-debugger)
|
||||
|
||||
BIN
windows/client-management/images/out-of-memory.png
Normal file
BIN
windows/client-management/images/out-of-memory.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
BIN
windows/client-management/images/task-manager-commit.png
Normal file
BIN
windows/client-management/images/task-manager-commit.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user