mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 19:33:37 +00:00
added note about MAM
This commit is contained in:
Justin Hall
@ -36,7 +36,6 @@
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "justinha",
|
||||
"ms.date": "04/05/2017",
|
||||
"_op_documentIdPathDepotMapping": {
|
||||
"./": {
|
||||
"depot_name": "MSDN.win-access-protection"
|
||||
|
||||
@ -5,7 +5,6 @@
|
||||
## [Understand apps in Windows 10](apps-in-windows-10.md)
|
||||
## [Add apps and features in Windows 10](add-apps-and-features.md)
|
||||
## [Repackage win32 apps in the MSIX format](msix-app-packaging-tool.md)
|
||||
### [Learn how to repackage win32 apps in the MSIX format](msix-app-packaging-tool-walkthrough.md)
|
||||
## [Application Virtualization (App-V) for Windows](app-v/appv-for-windows.md)
|
||||
### [Getting Started with App-V](app-v/appv-getting-started.md)
|
||||
#### [What's new in App-V for Windows 10, version 1703 and earlier](app-v/appv-about-appv.md)
|
||||
|
||||
@ -40,7 +40,7 @@ Previous versions of App-V have required you to manually remove your unpublished
|
||||
|
||||
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.
|
||||
|
||||
To learn more about earlier versions of App-V, see [MDOP Information Experience](https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/index).
|
||||
To learn more about earlier versions of App-V, see [MDOP Information Experience](https://docs.microsoft.com/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
The changes in App-V for Windows 10, version 1607 impact existing implementations of App-V in the following ways:
|
||||
|
||||
|
||||
@ -309,7 +309,7 @@ The following table shows local and roaming locations when folder redirection ha
|
||||
The current App-V Client VFS driver can't write to network locations, so the App-V Client detects the presence of folder redirection and copies the data on the local drive during publishing and when the virtual environment starts. After the user closes the App-V application and the App-V Client closes the virtual environment, the local storage of the VFS AppData is copied back to the network, enabling roaming to additional machines, where the process will be repeated. Here's what happens during the process:
|
||||
|
||||
1. During publishing or virtual environment startup, the App-V Client detects the location of the AppData directory.
|
||||
2. If the roaming AppData path is local or ino AppData\\Roaming location is mapped, nothing happens.
|
||||
2. If the roaming AppData path is local or no AppData\\Roaming location is mapped, nothing happens.
|
||||
3. If the roaming AppData path is not local, the VFS AppData directory is mapped to the local AppData directory.
|
||||
|
||||
This process solves the problem of a non-local %AppData% that is not supported by the App-V Client VFS driver. However, the data stored in this new location is not roamed with folder redirection. All changes during the running of the application happen to the local AppData location and must be copied to the redirected location. The process does the following things:
|
||||
@ -399,7 +399,7 @@ The process then configures the client for package or connection group additions
|
||||
|
||||
7. Create the **Registry.dat** file from the package store to **%ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat**.
|
||||
|
||||
8. Register the package with the App-V Kernal Mode Driver at **HKLM\\Microsoft\\Software\\AppV\\MAV**.
|
||||
8. Register the package with the App-V Kernel Mode Driver at **HKLM\\Microsoft\\Software\\AppV\\MAV**.
|
||||
|
||||
9. Invoke scripting from the **AppxManifest.xml** or **DeploymentConfig.xml** file for Package Add timing.
|
||||
|
||||
|
||||
@ -93,7 +93,7 @@ There are 3 types of log files that occur when you sequence multiple apps at the
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
|
||||
@ -80,7 +80,7 @@ Updating multiple apps at the same time requires that you create a **ConfigFile*
|
||||
|
||||
## Update multiple apps with the App-V Sequencer interface
|
||||
|
||||
Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM.
|
||||
Updating multiple apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM.
|
||||
|
||||
### Create your ConfigFile for use by the App-V Sequencer interface
|
||||
|
||||
@ -93,7 +93,7 @@ Updating multipe apps at the same time requires that you create a **ConfigFile**
|
||||
- ```<Installer>```. The file name for the app executable. This will typically be an .exe or .msi file.
|
||||
- ```<Package>```. The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
|
||||
- ```<TimeoutInMinutes>```. The maximum amount of time, in minutes, the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
|
||||
- ```<Cmdlet>```. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
|
||||
- ```<Cmdlet>```. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
|
||||
- ```<Enabled>```. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
|
||||
|
||||
**Example:**
|
||||
@ -147,7 +147,7 @@ There are three types of log files that occur when you sequence multiple apps at
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
|
||||
@ -51,7 +51,7 @@ For this process to work, you must have a base operating system available as a V
|
||||
After you have a VHD file, you must provision your VM for auto-sequencing.
|
||||
|
||||
1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server).
|
||||
2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server).
|
||||
3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```PowerShell
|
||||
@ -123,7 +123,7 @@ After you sequence your packages, you can automatically clean up any unpublished
|
||||
- [Download the **Convert-WindowsImage** tool](https://www.powershellgallery.com/packages/Convert-WindowsImage/10.0)
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.date: 06/15/2018
|
||||
---
|
||||
# Available Mobile Device Management (MDM) settings for App-V
|
||||
|
||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
|
||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
|
||||
|
||||
|Policy name|Supported versions|URI full path|Data type|Values|
|
||||
|---|---|---|---|---|
|
||||
|
||||
@ -182,7 +182,7 @@ Discounting scaling and fault-tolerance requirements, the minimum number of serv
|
||||
|
||||
Ignoring scaling requirements, the minimum number of servers that a fault-tolerant implementation needs to function is four. The management server and Microsoft SQL Server roles support placement in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
|
||||
|
||||
Although there are many fault-tolerance strategies and technologies you can use, not all are applicable to a given service. Additionally, if App-V roles are combined, the resulting incompatabilities could cause certain fault-tolerance options to stop working.
|
||||
Although there are many fault-tolerance strategies and technologies you can use, not all are applicable to a given service. Additionally, if App-V roles are combined, the resulting incompatibilities could cause certain fault-tolerance options to stop working.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ms.date: 04/18/2018
|
||||
|
||||
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. Understanding how the register's format for data works can help you better understand the client, as you can configure many client actions by changing registry entries. This topic lists the App-V client configuration settings and explains their uses. You can use Windows PowerShell to modify the client configuration settings. For more information about using Windows PowerShell and App-V see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
You can use Group Policy to configure App-V client settings by navigating to the **Group Policy managment console** at **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
You can use Group Policy to configure App-V client settings by navigating to the **Group Policy management console** at **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## App-V Client Configuration Settings: Windows PowerShell
|
||||
|
||||
|
||||
@ -46,13 +46,13 @@ For more about adding or upgrading packages, see [How to add or upgrade packages
|
||||
Add-AppvClientConnectionGroup
|
||||
```
|
||||
|
||||
For more information about how to use the **Add-AppvClientConnectionGroup** cmdlet, see [**Add-AppvClientConnectionGroup**](https://docs.microsoft.com/en-us/powershell/module/appvclient/add-appvclientconnectiongroup?view=win10-ps).
|
||||
For more information about how to use the **Add-AppvClientConnectionGroup** cmdlet, see [**Add-AppvClientConnectionGroup**](https://docs.microsoft.com/powershell/module/appvclient/add-appvclientconnectiongroup?view=win10-ps).
|
||||
|
||||
4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:
|
||||
|
||||
- [**Remove-AppvClientPackage**](https://docs.microsoft.com/en-us/powershell/module/appvclient/remove-appvclientpackage?view=win10-ps)
|
||||
- [**Add-AppvClientPackage**](https://docs.microsoft.com/en-us/powershell/module/appvclient/add-appvclientpackage?view=win10-ps)
|
||||
- [**Publish-AppvClientPackage**](https://docs.microsoft.com/en-us/powershell/module/appvclient/publish-appvclientpackage?view=win10-ps)
|
||||
- [**Remove-AppvClientPackage**](https://docs.microsoft.com/powershell/module/appvclient/remove-appvclientpackage?view=win10-ps)
|
||||
- [**Add-AppvClientPackage**](https://docs.microsoft.com/powershell/module/appvclient/add-appvclientpackage?view=win10-ps)
|
||||
- [**Publish-AppvClientPackage**](https://docs.microsoft.com/powershell/module/appvclient/publish-appvclientpackage?view=win10-ps)
|
||||
|
||||
For more information, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
|
||||
@ -95,7 +95,7 @@ You can use the connection group file to configure each connection group by usin
|
||||
|
||||
The priority field is required when a running virtual application initiates from a native application request, such as Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
|
||||
|
||||
If a virtual application is opened using another virtual application, the client will use the orignal virtual application's virtual environment. The priority field is not used in this case.
|
||||
If a virtual application is opened using another virtual application, the client will use the original virtual application's virtual environment. The priority field is not used in this case.
|
||||
|
||||
The following is an example of priority configuration:
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ Here are some important things to know before you get started:
|
||||
- If you add user-published packages in globally entitled connection groups, the connection group will fail.
|
||||
- Track the connection groups where you've used a non-optional package before removing it with the **Unpublish-AppvClientPackage <</span>package> -global** cmdlet.
|
||||
|
||||
In situations where you have a gobally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running **Unpublish-AppvClientPackage <</span>package> -global** cmdlet can unpublish the package from every connection group containing that package. Tracking connection groups can help you avoid unintentionally unpublishing non-optional packages.
|
||||
In situations where you have a globally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running **Unpublish-AppvClientPackage <</span>package> -global** cmdlet can unpublish the package from every connection group containing that package. Tracking connection groups can help you avoid unintentionally unpublishing non-optional packages.
|
||||
|
||||
## How to use Windows PowerShell cmdlets to create user-entitled connection groups
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ After creating the template, you can apply it to all of your new virtual app pac
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
|
||||
@ -413,12 +413,11 @@ To use a custom instance of Microsoft SQL Server, use these parameters:
|
||||
### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
|
||||
|
||||
```SQL
|
||||
Using a custom instance of Microsoft SQL Server example:<br>
|
||||
/appv_server_setup.exe /QUIET<br>
|
||||
/DB_PREDEPLOY_REPORTING<br>
|
||||
/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"<br>
|
||||
/REPORTING_DB_NAME="AppVReporting"<br>
|
||||
/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"<br>
|
||||
/appv_server_setup.exe /QUIET
|
||||
/DB_PREDEPLOY_REPORTING
|
||||
/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
|
||||
/REPORTING_DB_NAME="AppVReporting"
|
||||
/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
|
||||
/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
|
||||
```
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ ms.date: 04/18/2018
|
||||
|
||||
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/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* 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).
|
||||
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**.
|
||||
|
||||
@ -29,7 +29,7 @@ The following table shows the App-V versions, methods of Office package creation
|
||||
|
||||
## Creating Office 2010 App-V using the sequencer
|
||||
|
||||
Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V. Microsoft has provided a detailed recipe through a Knowledge Base article. For detailed instructions about how to create an Office 2010 package on App-V, see [How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://support.microsoft.com/en-us/kb/2830069).
|
||||
Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V. Microsoft has provided a detailed recipe through a Knowledge Base article. For detailed instructions about how to create an Office 2010 package on App-V, see [How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://support.microsoft.com/kb/2830069).
|
||||
|
||||
## Creating Office 2010 App-V packages using package accelerators
|
||||
|
||||
@ -78,13 +78,13 @@ The following table provides a full list of supported integration points for Off
|
||||
|
||||
### Office 2013 App-V Packages Additional Resources
|
||||
|
||||
* [Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/en-us/kb/2772509)
|
||||
* [Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/kb/2772509)
|
||||
|
||||
### 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)
|
||||
* [Known issues when you create or use an App-V 5.0 Office 2010 package](https://support.microsoft.com/en-us/kb/2828619)
|
||||
* [How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://support.microsoft.com/en-us/kb/2830069)
|
||||
* [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)
|
||||
|
||||
### Connection Groups
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ Before you deploy Office with App-V, review the following requirements.
|
||||
|---|---|
|
||||
|Packaging|All Office applications you wish to deploy to users must be in a single package.<br>In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project).|
|
||||
|Publishing|You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user.|
|
||||
|Deploying Office 365 ProPlus, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
|
||||
|Deploying Office 365 ProPlus, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](https://docs.microsoft.com/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
@ -43,7 +43,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
|
||||
|Task|Details|
|
||||
|---|---|
|
||||
|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/en-us/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element).|
|
||||
|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element).|
|
||||
|Modify the **DeploymentConfig.xml** file|Modify the **DeploymentConfig.xml** file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client.<br>For more information, see [Disabling Office 2013 applications](#bkmk-disable-office-apps).|
|
||||
|
||||
## Creating an Office 2013 package for App-V with the Office Deployment Tool
|
||||
@ -255,7 +255,7 @@ Deploy the App-V package for Office 2013 by using the same methods you use for a
|
||||
|
||||
### How to publish an Office package
|
||||
|
||||
Run the following command to publish an Office package globally, wtih the bracketed value replaced by the path to the App-V package:
|
||||
Run the following command to publish an Office package globally, with the bracketed value replaced by the path to the App-V package:
|
||||
|
||||
```PowerShell
|
||||
Add-AppvClientPackage <Path_to_AppV_Package> | Publish-AppvClientPackage –global
|
||||
@ -302,7 +302,7 @@ Use the steps in this section to enable Office plug-ins with your Office package
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you will save the changes, add the Office 2013 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
|
||||
|
||||
>[!NOTE]
|
||||
>To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](https://docs.microsoft.com/en-us/DeployOffice/configuration-options-for-the-office-2016-deployment-tool#excludeapp-element).
|
||||
>To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](https://docs.microsoft.com/DeployOffice/configuration-options-for-the-office-2016-deployment-tool#excludeapp-element).
|
||||
|
||||
#### To disable an Office 2013 application
|
||||
|
||||
@ -408,20 +408,20 @@ This section describes the requirements and options for deploying Visio 2013 and
|
||||
|Goal|Method|
|
||||
|---|---|
|
||||
|Create two different packages and deploy each one to a different group of users|Create and deploy the following packages:<br>A package that contains only Office—deploy to computers whose users need only Office.<br>A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.|
|
||||
|Create just one package for the whole organization, or for users who share computers|Follow these steps:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/en-us/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
|
||||
|Create just one package for the whole organization, or for users who share computers|Follow these steps:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
|
||||
|
||||
## Additional resources
|
||||
|
||||
### Additional resources for Office 2013 App-V Packages
|
||||
|
||||
* [Office 2013 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778)
|
||||
* [Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/en-us/kb/2772509)
|
||||
* [Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/kb/2772509)
|
||||
|
||||
### Additional resources for Office 2010 App-V Packages
|
||||
|
||||
* [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/en-us/kb/2828619)
|
||||
* [How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://support.microsoft.com/en-us/kb/2830069)
|
||||
* [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)
|
||||
|
||||
### Additional resources for Connection Groups
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ Before you deploy Office with App-V, review the following requirements.
|
||||
|-----------|-------------------|
|
||||
| Packaging. | All Office applications that you deploy to users must be in a single package.<br>In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2016 and Microsoft Project 2016 at the same time as Office, you must put them all in the same package. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office). |
|
||||
| Publishing. | You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user. |
|
||||
| Deploying Office 365 ProPlus, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer with Remote Desktop Services. | You must enable [shared computer activation](https://docs.microsoft.com/en-us/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). |
|
||||
| Deploying Office 365 ProPlus, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer with Remote Desktop Services. | You must enable [shared computer activation](https://docs.microsoft.com/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). |
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
@ -43,7 +43,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
|
||||
|Task|Details|
|
||||
|-------------|---------------|
|
||||
| Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool. | With this setting, you can exclude specific Office applications from the package that the Office Deployment Tool creates. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/en-us/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element). |
|
||||
| Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool. | With this setting, you can exclude specific Office applications from the package that the Office Deployment Tool creates. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element). |
|
||||
| Modify the DeploymentConfig.xml file | Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.<br>For more information, see [Disabling Office 2016 applications](#disabling-office-2016-applications). |
|
||||
|
||||
## Creating an Office 2016 package for App-V with the Office Deployment Tool
|
||||
@ -120,7 +120,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
|
||||
| Language element | Specifies which language the applications support. | `Language ID="en-us"` |
|
||||
| Version (attribute of **Add** element) | Optional. Specifies which build the package will use.<br>Defaults to latest advertised build (as defined in v32.CAB at the Office source). | `16.1.2.3` |
|
||||
| SourcePath (attribute of **Add** element) | Specifies the location the applications will be saved to. | `Sourcepath = "\\Server\Office2016"` |
|
||||
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Office 365 ProPlus and **Current** for Visio Pro for Office 365 and Project Online Desktop Client. <br>For more information about update channels, see [Overview of update channels for Office 365 ProPlus](https://docs.microsoft.com/en-us/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
|
||||
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Office 365 ProPlus and **Current** for Visio Pro for Office 365 and Project Online Desktop Client. <br>For more information about update channels, see [Overview of update channels for Office 365 ProPlus](https://docs.microsoft.com/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
|
||||
|
||||
After editing the **configuration.xml** file to specify the desired product, languages, and the location where the Office 2016 applications will be saved to, you can save the configuration file under a name of your choice, such as "Customconfig.xml."
|
||||
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2016 applications that will later be converted into an App-V package. The following is an example command:
|
||||
@ -369,7 +369,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
| Task | Details |
|
||||
|---------------------|---------------|
|
||||
| How do I package and publish Visio 2016 and Project 2016 with Office? | You must include Visio 2016 and Project 2016 in the same package with Office.<br>If you are not deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic. |
|
||||
| How can I deploy Visio 2016 and Project 2016 to specific users? | Use one of the following methods:<br>**To create two different packages and deploy each one to a different group of users**:<br>Create and deploy the following packages:<br>- A package that contains only Office—deploy to computers whose users need only Office.<br>- A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.<br><br>**To create only one package for the whole organization, or to create a package intended for users who share computers**:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/en-us/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project. |
|
||||
| How can I deploy Visio 2016 and Project 2016 to specific users? | Use one of the following methods:<br>**To create two different packages and deploy each one to a different group of users**:<br>Create and deploy the following packages:<br>- A package that contains only Office—deploy to computers whose users need only Office.<br>- A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.<br><br>**To create only one package for the whole organization, or to create a package intended for users who share computers**:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project. |
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ms.date: 09/27/2018
|
||||
|
||||
You can deploy App-V packages using an electronic software distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv)
|
||||
To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/library/gg682125.aspx#BKMK_Appv)
|
||||
|
||||
## How to deploy virtualized packages using an ESD
|
||||
|
||||
|
||||
@ -40,13 +40,13 @@ 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/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* 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).
|
||||
|
||||
In large organizations, you might want to install more than one instance of the server components to get the following benefits.
|
||||
|
||||
* Fault tolerance for situations when one of the servers is unavailable.
|
||||
* High availability to balance server requests. A network load balancer can also help you acheive this.
|
||||
* High availability to balance server requests. A network load balancer can also help you achieve this.
|
||||
* Scalability to support high loads. For example, you can install additional servers behind a network load balancer.
|
||||
|
||||
## App-V standalone deployment
|
||||
@ -107,4 +107,4 @@ For more information, see [About App-V reporting](appv-reporting.md) and [How to
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
|
||||
@ -12,7 +12,7 @@ ms.date: 04/18/2018
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
This checklist outlines the recommended steps and items to consider when deploying App-V features. Use it to organize your priorites while you deploy App-V. You can copy this checklist into a spreadsheet program and customize it for your use.
|
||||
This checklist outlines the recommended steps and items to consider when deploying App-V features. Use it to organize your priorities while you deploy App-V. You can copy this checklist into a spreadsheet program and customize it for your use.
|
||||
|
||||
|Status|Task|References|Notes|
|
||||
|---|---|---|---|
|
||||
|
||||
@ -186,7 +186,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate
|
||||
</Shortcuts>
|
||||
```
|
||||
|
||||
**File Type Associations**: Associates file types with programs to open by default as well as setup the context menu. (MIME types can also be set up with this susbsystem). The following is an example of a FileType association:
|
||||
**File Type Associations**: Associates file types with programs to open by default as well as setup the context menu. (MIME types can also be set up with this subsystem). The following is an example of a FileType association:
|
||||
|
||||
```xml
|
||||
<FileTypeAssociations Enabled="true">
|
||||
@ -252,7 +252,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate
|
||||
</FileTypeAssociations>
|
||||
```
|
||||
|
||||
**URL Protocols**: This controls the URL Protocols integrated into the local registry of the client machine. The following example illustrates the “mailto:” ptrotocol.
|
||||
**URL Protocols**: This controls the URL Protocols integrated into the local registry of the client machine. The following example illustrates the “mailto:” protocol.
|
||||
|
||||
```xml
|
||||
<URLProtocols Enabled="true">
|
||||
|
||||
@ -21,7 +21,7 @@ If you’re already using App-V, performing an in-place upgrade to Windows 10 on
|
||||
>[!IMPORTANT]
|
||||
>You can upgrade your existing App-V installation to App-V for Windows from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade your existing App-V installation to App-V 5.0 SP2 before upgrading to App-V for Windows.
|
||||
|
||||
To learn more about previous versions of App-V, see [MDOP information experience](https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/index).
|
||||
To learn more about previous versions of App-V, see [MDOP information experience](https://docs.microsoft.com/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
## Getting started with App-V for Windows 10 (new installations)
|
||||
|
||||
@ -31,7 +31,7 @@ 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/en-us/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/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 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). |
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ To install the management server on a standalone computer and connect it to the
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
|
||||
2. On the **Getting Started** page, review and accept the license terms, then select **Next**.
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft Udpate, select **Use Microsoft Update when I check for updates (recommended)**. To disable Microsoft Update, select **I don’t want to use Microsoft Update**, then select **Next**.
|
||||
3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft Update, select **Use Microsoft Update when I check for updates (recommended)**. To disable Microsoft Update, select **I don’t want to use Microsoft Update**, then select **Next**.
|
||||
4. On the **Feature Selection** page, select the **Management Server** checkbox, then select **Next**.
|
||||
5. On the **Installation Location** page, accept the default location, then select **Next**.
|
||||
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, then enter the computer running Microsoft SQL's machine name, such as ```SqlServerMachine```.
|
||||
|
||||
@ -78,7 +78,7 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|App-V Sequencer|**Update-Help -Module AppvSequencer**|
|
||||
|App-V Client|**Update-Help -Module AppvClient**|
|
||||
|
||||
* Online in the [Microsoft Desktop Optimization Pack](https://docs.microsoft.com/en-us/powershell/mdop/get-started?view=win-mdop2-ps).
|
||||
* Online in the [Microsoft Desktop Optimization Pack](https://docs.microsoft.com/powershell/mdop/get-started?view=win-mdop2-ps).
|
||||
|
||||
## Displaying the help for a Windows PowerShell cmdlet
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ Enter the **Get-AppvClientPackage** cmdlet to return a list of packages entitled
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Get-AppvClientPackage –Name “ContosoApplication” -Version 2
|
||||
Get-AppvClientPackage –Name "ContosoApplication" -Version 2
|
||||
```
|
||||
|
||||
## Add a package
|
||||
@ -44,13 +44,13 @@ Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been
|
||||
Enter the cmdlet with the application name to publish it to the user.
|
||||
|
||||
```PowerShell
|
||||
Publish-AppvClientPackage “ContosoApplication”
|
||||
Publish-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
To publish the application globally, just add the *-Global* parameter.
|
||||
|
||||
```Powershell
|
||||
Publish-AppvClientPackage “ContosoApplication” -Global
|
||||
Publish-AppvClientPackage "ContosoApplication" -Global
|
||||
```
|
||||
|
||||
## Publish a package to a specific user
|
||||
@ -70,7 +70,7 @@ To use this parameter:
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Publish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
Publish-AppvClientPackage "ContosoApplication" -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
```
|
||||
|
||||
## Add and publish a package
|
||||
@ -90,7 +90,7 @@ Use the **Unpublish-AppvClientPackage** cmdlet to unpublish a package which has
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Unpublish-AppvClientPackage “ContosoApplication”
|
||||
Unpublish-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
## Unpublish a package for a specific user
|
||||
@ -110,7 +110,7 @@ To use this parameter:
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Unpublish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
Unpublish-AppvClientPackage "ContosoApplication" -UserSID S-1-2-34-56789012-3456789012-345678901-2345
|
||||
```
|
||||
|
||||
## Remove an existing package
|
||||
@ -120,7 +120,7 @@ Use the **Remove-AppvClientPackage** cmdlet to remove a package from the compute
|
||||
For example:
|
||||
|
||||
```PowerShell
|
||||
Remove-AppvClientPackage “ContosoApplication”
|
||||
Remove-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
|
||||
@ -45,7 +45,7 @@ This topic explains the following procedures:
|
||||
|
||||
2. Enable the connection group by typing the following command:
|
||||
|
||||
Enable-AppvClientConnectionGroup –name “Financial Applications”
|
||||
Enable-AppvClientConnectionGroup –name "Financial Applications"
|
||||
|
||||
When any virtual applications that are in the member packages are run on the target computer, they will run inside the connection group’s virtual environment and will be available to all the virtual applications in the other packages in the connection group.
|
||||
|
||||
@ -81,11 +81,11 @@ This topic explains the following procedures:
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
<td align="left"><p>Enable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup</p></td>
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup “ConnectionGroupA” -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
<td align="left"><p>Disable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -25,7 +25,7 @@ Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
`Set-AppVClientConfiguration $config`
|
||||
|
||||
`Set-AppVClientConfiguration –Name1 MyConfig –Name2 “xyz”`
|
||||
`Set-AppVClientConfiguration –Name1 MyConfig –Name2 "xyz"`
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
@ -587,7 +587,7 @@ If, during sequencer monitoring, an SxS Assembly (such as a VC++ Runtime) is ins
|
||||
|
||||
**Client Side**:
|
||||
|
||||
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it is included in the package, a traditional Windows Insataller (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation will not occur.
|
||||
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it is included in the package, a traditional Windows Installer (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation will not occur.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -618,7 +618,7 @@ When publishing a virtual application package, the App-V Client will detect if a
|
||||
|
||||
|
||||
|
||||
### Disabling a Dynamic Configuration by using Windows Powershell
|
||||
### Disabling a Dynamic Configuration by using Windows PowerShell
|
||||
|
||||
- For already published packages, you can use `Set-AppVClientPackage –Name Myapp –Path c:\Packages\Apps\MyApp.appv` without
|
||||
|
||||
@ -725,7 +725,7 @@ The following terms are used when describing concepts and actions related to App
|
||||
|
||||
- From the point that users initiate a log-in to when they are able to manipulate the desktop.
|
||||
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in Windows PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage** Windows Powershell commands are initiated.
|
||||
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in Windows PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage** Windows PowerShell commands are initiated.
|
||||
|
||||
- From start to completion of the publishing refresh. In standalone instances, this is the first to last virtual application published.
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ For more information, see [Application publishing and client interaction](appv-a
|
||||
|
||||
## Unsupported scenarios for App-V folder redirection
|
||||
|
||||
The following scenatios aren't supported by App-V:
|
||||
The following scenarios aren't supported by App-V:
|
||||
|
||||
* Configuring %LocalAppData% as a network drive.
|
||||
* Redirecting the Start menu to a single folder for multiple users.
|
||||
|
||||
@ -30,12 +30,12 @@ Review the following articles to learn more about configuring IIS and NLB for co
|
||||
|
||||
* [Achieving High Availability and Scalability - ARR and NLB](https://www.iis.net/learn/extensions/configuring-application-request-routing-arr/achieving-high-availability-and-scalability-arr-and-nlb) describes how to configure IIS 7.0.
|
||||
|
||||
* [Network load balancing overview](<https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831698(v=ws.11)>) will tell you more about how to configure Microsoft Windows Server.
|
||||
* [Network load balancing overview](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831698(v=ws.11)>) will tell you more about how to configure Microsoft Windows Server.
|
||||
|
||||
This information also applies to IIS NLB clusters in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.
|
||||
|
||||
>[!NOTE]
|
||||
>The IIS NLB functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details have changed in Windows Server 2012. To learn how to work with these changes, see [Common management tasks and navigation in Windows](<https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831491(v=ws.11)>).
|
||||
>The IIS NLB functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details have changed in Windows Server 2012. To learn how to work with these changes, see [Common management tasks and navigation in Windows](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831491(v=ws.11)>).
|
||||
|
||||
## Support for clustered file servers when running SCS mode
|
||||
|
||||
@ -54,8 +54,8 @@ The following steps can be used to validate the configuration:
|
||||
|
||||
Review the following articles to learn more about configuring Windows Server failover clusters:
|
||||
|
||||
* [Create a failover cluster](<https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn505754(v=ws.11)>)
|
||||
* [Use cluster shared volumes in a failover cluster](<https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612868(v=ws.11)>)
|
||||
* [Create a failover cluster](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn505754(v=ws.11)>)
|
||||
* [Use cluster shared volumes in a failover cluster](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612868(v=ws.11)>)
|
||||
|
||||
## Support for Microsoft SQL Server mirroring
|
||||
|
||||
@ -63,7 +63,7 @@ Using Microsoft SQL Server mirroring, where the App-V management server database
|
||||
|
||||
Review the following to learn more about how to configure Microsoft SQL Server mirroring:
|
||||
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server)
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server)
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://msdn.microsoft.com/library/ms188712.aspx) (FIX LINK)
|
||||
|
||||
The following steps can be used to validate the configuration:
|
||||
@ -77,7 +77,7 @@ The connection string on the management server can be modified to include ```fai
|
||||
Use the following steps to modify the connection string to include ```failover partner = <server2>```:
|
||||
|
||||
>[!IMPORTANT]
|
||||
>This process involves changing the Windows registry with Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. Always make a backup copy of the registry files (**System.dat** and **User.dat**) before chagning the registry. Microsoft can't guarantee that problems caused by changing the registry can be resolved, so change the registry at your own risk.
|
||||
>This process involves changing the Windows registry with Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. Always make a backup copy of the registry files (**System.dat** and **User.dat**) before changing the registry. Microsoft can't guarantee that problems caused by changing the registry can be resolved, so change the registry at your own risk.
|
||||
|
||||
1. Log in to the management server and open **regedit**.
|
||||
2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**.
|
||||
@ -88,13 +88,13 @@ Use the following steps to modify the connection string to include ```failover p
|
||||
|
||||
Click any of the following links for more information:
|
||||
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server).
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication).
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server).
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://docs.microsoft.com/sql/database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication).
|
||||
* [Deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>).
|
||||
|
||||
## Support for Microsoft SQL Server Always On configuration
|
||||
|
||||
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server).
|
||||
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ Ideally, you should install the sequencer on a computer running as a virtual mac
|
||||
3. Take a “snapshot” of the environment.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Your corporate security team should review and approve the sequencing process plan before implementing it. For security reasons, it's a good idea to keep sequencer operations in a lab separate from the production environment. The sequencing computers must be capapble of connecting to the corporate network to copy finished packages to the production servers. However, because the sequencing computers are typically operated without antivirus protection, they shouldn't remail on the corporate network unprotected. You can protect your sequencing computers by operating them on an isolated network, behind a firewall, or by using virtual machines on an isolated virtual network. Make sure your solution follows your company's corporate security policies.
|
||||
>Your corporate security team should review and approve the sequencing process plan before implementing it. For security reasons, it's a good idea to keep sequencer operations in a lab separate from the production environment. The sequencing computers must be capable of connecting to the corporate network to copy finished packages to the production servers. However, because the sequencing computers are typically operated without antivirus protection, they shouldn't remain on the corporate network unprotected. You can protect your sequencing computers by operating them on an isolated network, behind a firewall, or by using virtual machines on an isolated virtual network. Make sure your solution follows your company's corporate security policies.
|
||||
|
||||
## Planning for App-V client deployment
|
||||
|
||||
|
||||
@ -23,10 +23,10 @@ You can use the App-V Sequencer to create plug-in packages for language packs, l
|
||||
|
||||
## Supported versions of Microsoft Office
|
||||
|
||||
For a list of supported Office products, see [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/en-us/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click).
|
||||
For a list of supported Office products, see [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click).
|
||||
|
||||
>[!NOTE]
|
||||
>You must use the Office Deployment Tool instead of the App-V Sequencer to create App-V packages for Office 365 ProPlus. App-V does not support package creation for volume-licensed versions of Office Professional Plus or Office Standard. Support for the [Office 2013 version of Office 365 ended in Februrary 2017](https://support.microsoft.com/kb/3199744).
|
||||
>You must use the Office Deployment Tool instead of the App-V Sequencer to create App-V packages for Office 365 ProPlus. App-V does not support package creation for volume-licensed versions of Office Professional Plus or Office Standard. Support for the [Office 2013 version of Office 365 ended in February 2017](https://support.microsoft.com/kb/3199744).
|
||||
|
||||
## Using App-V with coexisting versions of Office
|
||||
|
||||
@ -90,7 +90,7 @@ To bypass the auto-registration operation for native Word 2010, follow these ste
|
||||
|
||||
* In Windows 8.1 or Windows 10, enter **regedit**, select **Enter** on the Start page, then select the Enter key.
|
||||
|
||||
If you're prompted for an administrator password, enter the password. If you're propmted for a confirmation, select **Continue**.
|
||||
If you're prompted for an administrator password, enter the password. If you're prompted for a confirmation, select **Continue**.
|
||||
3. Locate and then select the following registry subkey:
|
||||
|
||||
``` syntax
|
||||
|
||||
@ -12,7 +12,7 @@ ms.date: 04/18/2018
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with System Center Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv).
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with System Center Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/library/gg682125.aspx#BKMK_Appv).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
||||
|
||||
@ -190,7 +190,7 @@ You can also use the **Send-AppVClientReport** cmdlet to manually collect data.
|
||||
|
||||
To retrieve report information and create reports using App-V you must use one of the following methods:
|
||||
|
||||
* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](https://docs.microsoft.com/en-us/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
|
||||
* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](https://docs.microsoft.com/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
|
||||
|
||||
* Scripting—You can generate reports by scripting directly against the App-V reporting database. For example:
|
||||
|
||||
@ -198,7 +198,7 @@ To retrieve report information and create reports using App-V you must use one o
|
||||
|
||||
**spProcessClientReport** is scheduled to run at midnight or 12:00 AM.
|
||||
|
||||
To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. Make sure the Microsoft SQL Server Agent is set to **AutoStart**. For more information, see [Autostart SQL Server Agent (SQL Server Management Studio)](https://docs.microsoft.com/en-us/sql/ssms/agent/autostart-sql-server-agent-sql-server-management-studio).
|
||||
To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. Make sure the Microsoft SQL Server Agent is set to **AutoStart**. For more information, see [Autostart SQL Server Agent (SQL Server Management Studio)](https://docs.microsoft.com/sql/ssms/agent/autostart-sql-server-agent-sql-server-management-studio).
|
||||
|
||||
The stored procedure is also created when you use the App-V database scripts.
|
||||
|
||||
|
||||
@ -27,9 +27,9 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature introdu
|
||||
|
||||
**Physically secure your computers**. A security strategy that doesn't consider physical security is incomplete. Anyone with physical access to an App-V server could potentially attack the entire client base, so potential physical attacks or thefts should be prevented at all cost. App-V servers should be stored in a physically secure server room with controlled access. Lock the computer with the operating system or a secured screen saver to keep computers secure when the administrators are away.
|
||||
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/en-us/security/bb291012). (THIS LINK NEEDS TO BE UPDATED)
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/security/bb291012). (THIS LINK NEEDS TO BE UPDATED)
|
||||
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://docs.microsoft.com/en-us/sql/relational-databases/security/password-policy) and [Strong Passwords](https://docs.microsoft.com/en-us/sql/relational-databases/security/strong-passwords). (THIS LINK NEEDS TO BE UPDATED)
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://docs.microsoft.com/sql/relational-databases/security/password-policy) and [Strong Passwords](https://docs.microsoft.com/sql/relational-databases/security/strong-passwords). (THIS LINK NEEDS TO BE UPDATED)
|
||||
|
||||
## Accounts and groups in App-V
|
||||
|
||||
@ -60,7 +60,7 @@ Consider the following additional information:
|
||||
|
||||
The following will help you plan how to ensure that virtualized packages are secure.
|
||||
|
||||
* If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. If thje file or directory is modified by a user when the package is deployed, the modified file or directory will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former occurs if the file or directory does not exist in a virtual file system location; the latter occurs if the file or directory exists in a virtual file system location, such as **%windir%**.
|
||||
* If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. If the file or directory is modified by a user when the package is deployed, the modified file or directory will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former occurs if the file or directory does not exist in a virtual file system location; the latter occurs if the file or directory exists in a virtual file system location, such as **%windir%**.
|
||||
|
||||
## App-V log files
|
||||
|
||||
|
||||
@ -47,4 +47,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
|
||||
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
[Windows PowerShell reference for App-V](https://technet.microsoft.com/en-us/library/dn903534.aspx)
|
||||
[Windows PowerShell reference for App-V](https://technet.microsoft.com/library/dn903534.aspx)
|
||||
|
||||
@ -84,7 +84,7 @@ In your publishing metadata query, enter the string values that correspond to th
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Architecture</th>
|
||||
<th align="left">Operating string string value</th>
|
||||
<th align="left">String value</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
|
||||
@ -8,87 +8,153 @@ ms.pagetype: mobile
|
||||
ms.author: elizapo
|
||||
author: lizap
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 08/23/2018
|
||||
ms.date: 12/12/2018
|
||||
---
|
||||
# Understand the different apps included in Windows 10
|
||||
|
||||
>Applies to: Windows 10
|
||||
|
||||
The following types of apps run on Windows 10:
|
||||
- Windows apps - introduced in Windows 8, primarily installed from the Store app.
|
||||
- Universal Windows Platform (UWP) apps - designed to work across platforms, can be installed on multiple platforms including Windows client, Windows Phone, and Xbox. All UWP apps are also Windows apps, but not all Windows apps are UWP apps.
|
||||
- "Win32" apps - traditional Windows applications.
|
||||
|
||||
Digging into the Windows apps, there are two categories:
|
||||
- System apps - Apps that are installed in the c:\Windows\* directory. These apps are integral to the OS.
|
||||
- Apps - All other apps, installed in c:\Program Files\WindowsApps. There are two classes of apps:
|
||||
- Apps - All other apps, installed in C:\Program Files\WindowsApps. There are two classes of apps:
|
||||
- Provisioned: Installed in user account the first time you sign in with a new user account.
|
||||
- Installed: Installed as part of the OS.
|
||||
- System apps - Apps that are installed in the C:\Windows\* directory. These apps are integral to the OS.
|
||||
|
||||
The following tables list the system apps, installed Windows apps, and provisioned Windows apps in a standard Windows 10 Enterprise installation. (If you have a custom image, your specific apps might differ.) The tables list the app, the full name, show the app's status in Windows 10 version 1607, 1703, and 1709, and indicate whether an app can be uninstalled through the UI.
|
||||
|
||||
Some of the apps show up in multiple tables - that's because their status changed between versions. Make sure to check the version column for the version you are currently running.
|
||||
|
||||
|
||||
## Provisioned Windows apps
|
||||
|
||||
Here are the provisioned Windows apps in Windows 10 versions 1703, 1709, 1803 and 1809.
|
||||
|
||||
> [!TIP]
|
||||
> Want to see a list of the apps installed on your specific image? You can run the following PowerShell cmdlet:
|
||||
> ```powershell
|
||||
> Get-AppxPackage | select Name,PackageFamilyName
|
||||
> Get-AppxProvisionedPackage -Online | select DisplayName,PackageName
|
||||
> You can list all provisioned Windows apps with this PowerShell command:
|
||||
> ```
|
||||
> Get-AppxProvisionedPackage -Online | Format-Table DisplayName, PackageName
|
||||
> ```
|
||||
|
||||
<br>
|
||||
|
||||
| Package name | App name | 1703 | 1709 | 1803 | 1809 | Uninstall through UI? |
|
||||
|----------------------------------------|--------------------------------------------------------------------------------------------------------------------|:----:|:----:|:----:|:----:|:---------------------:|
|
||||
| Microsoft.3DBuilder | [3D Builder](ms-windows-store://pdp/?PFN=Microsoft.3DBuilder_8wekyb3d8bbwe) | x | | | | Yes |
|
||||
| Microsoft.BingWeather | [MSN Weather](ms-windows-store://pdp/?PFN=Microsoft.BingWeather_8wekyb3d8bbwe) | x | x | x | x | Yes |
|
||||
| Microsoft.DesktopAppInstaller | [App Installer](ms-windows-store://pdp/?PFN=Microsoft.DesktopAppInstaller_8wekyb3d8bbwe) | x | x | x | x | Via Settings App |
|
||||
| Microsoft.GetHelp | [Get Help](ms-windows-store://pdp/?PFN=Microsoft.Gethelp_8wekyb3d8bbwe) | | x | x | x | No |
|
||||
| Microsoft.Getstarted | [Microsoft Tips](ms-windows-store://pdp/?PFN=Microsoft.Getstarted_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.HEIFImageExtension | [HEIF Image Extensions](ms-windows-store://pdp/?PFN=Microsoft.HEIFImageExtension_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.Messaging | [Microsoft Messaging](ms-windows-store://pdp/?PFN=Microsoft.Messaging_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.Microsoft3DViewer | [Mixed Reality Viewer](ms-windows-store://pdp/?PFN=Microsoft.Microsoft3DViewer_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.MicrosoftOfficeHub | [My Office](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe) | x | x | x | x | Yes |
|
||||
| Microsoft.MicrosoftSolitaireCollection | [Microsoft Solitaire Collection](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe) | x | x | x | x | Yes |
|
||||
| Microsoft.MicrosoftStickyNotes | [Microsoft Sticky Notes](ms-windows-store://pdp/?PFN=Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.MixedReality.Portal | [Mixed Reality Portal](ms-windows-store://pdp/?PFN=Microsoft.MixedReality.Portal_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.MSPaint | [Paint 3D](ms-windows-store://pdp/?PFN=Microsoft.MSPaint_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.Office.OneNote | [OneNote](ms-windows-store://pdp/?PFN=Microsoft.Office.OneNote_8wekyb3d8bbwe) | x | x | x | x | Yes |
|
||||
| Microsoft.OneConnect | [Paid Wi-Fi & Cellular](ms-windows-store://pdp/?PFN=Microsoft.OneConnect_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.People | [Microsoft People](ms-windows-store://pdp/?PFN=Microsoft.People_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.Print3D | [Print 3D](ms-windows-store://pdp/?PFN=Microsoft.Print3D_8wekyb3d8bbwe) | | x | x | x | No |
|
||||
| Microsoft.SkreenSketch | [Snip & Sketch](ms-windows-store://pdp/?PFN=Microsoft.ScreenSketch_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.SkypeApp | [Skype](ms-windows-store://pdp/?PFN=Microsoft.SkypeApp_kzf8qxf38zg5c) | x | x | x | x | No |
|
||||
| Microsoft.StorePurchaseApp | [Store Purchase App](ms-windows-store://pdp/?PFN=Microsoft.StorePurchaseApp_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.VP9VideoExtensions | | | | | x | No |
|
||||
| Microsoft.Wallet | [Microsoft Pay](ms-windows-store://pdp/?PFN=Microsoft.Wallet_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WebMediaExtensions | [Web Media Extensions](ms-windows-store://pdp/?PFN=Microsoft.WebMediaExtensions_8wekyb3d8bbwe) | | | x | x | No |
|
||||
| Microsoft.WebpImageExtension | [Webp Image Extension](ms-windows-store://pdp/?PFN=Microsoft.WebpImageExtension_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.Windows.Photos | [Microsoft Photos](ms-windows-store://pdp/?PFN=Microsoft.Windows.Photos_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsAlarms | [Windows Alarms & Clock](ms-windows-store://pdp/?PFN=Microsoft.WindowsAlarms_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsCalculator | [Windows Calculator](ms-windows-store://pdp/?PFN=Microsoft.WindowsCalculator_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsCamera | [Windows Camera](ms-windows-store://pdp/?PFN=Microsoft.WindowsCamera_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| microsoft.windowscommunicationsapps | [Mail and Calendar](ms-windows-store://pdp/?PFN=microsoft.windowscommunicationsapps_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsFeedbackHub | [Feedback Hub](ms-windows-store://pdp/?PFN=Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsMaps | [Windows Maps](ms-windows-store://pdp/?PFN=Microsoft.WindowsMaps_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsSoundRecorder | [Windows Voice Recorder](ms-windows-store://pdp/?PFN=Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.WindowsStore | [Microsoft Store](ms-windows-store://pdp/?PFN=Microsoft.WindowsStore_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.Xbox.TCUI | [Xbox TCUI](ms-windows-store://pdp/?PFN=Microsoft.Xbox.TCUI_8wekyb3d8bbwe) | | x | x | x | No |
|
||||
| Microsoft.XboxApp | [Xbox](ms-windows-store://pdp/?PFN=Microsoft.XboxApp_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.XboxGameOverlay | [Xbox Game Bar](ms-windows-store://pdp/?PFN=Microsoft.XboxGameOverlay_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.XboxGamingOverlay | [Xbox Gaming Overlay](ms-windows-store://pdp/?PFN=Microsoft.XboxGamingOverlay_8wekyb3d8bbwe) | | | x | x | No |
|
||||
| Microsoft.XboxIdentityProvider | [Xbox Identity Provider](ms-windows-store://pdp/?PFN=Microsoft.XboxIdentityProvider_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.XboxSpeechToTextOverlay | | x | x | x | x | No |
|
||||
| Microsoft.YourPhone | [Your Phone](ms-windows-store://pdp/?PFN=Microsoft.YourPhone_8wekyb3d8bbwe) | | | | x | No |
|
||||
| Microsoft.ZuneMusic | [Groove Music](ms-windows-store://pdp/?PFN=Microsoft.ZuneMusic_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.ZuneVideo | [Movies & TV](ms-windows-store://pdp/?PFN=Microsoft.ZuneVideo_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>The Store app can't be removed. If you want to remove and reinstall the Store app, you can only bring Store back by either restoring your system from a backup or resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it.
|
||||
|
||||
## System apps
|
||||
|
||||
System apps are integral to the operating system. Here are the typical system apps in Windows 10 versions 1703, 1709, and 1803.
|
||||
|
||||
| Name | Full name |1703 | 1709 | 1803 |Uninstall through UI? |
|
||||
|------------------|-------------------------------------------|:------:|:------:|:------:|-------------------------------------------------------|
|
||||
| Cortana UI | CortanaListenUIApp | x | | |No |
|
||||
| | Desktop Learning | x | | |No |
|
||||
| | DesktopView | x | | |No |
|
||||
| | EnvironmentsApp | x | | |No |
|
||||
| Mixed Reality + | HoloCamera | x | | |No |
|
||||
| Mixed Reality + | HoloItemPlayerApp | x | | |No |
|
||||
| Mixed Reality + | HoloShell | x | | |No |
|
||||
| | InputApp | | x | x |No |
|
||||
| | Microsoft.AAD.Broker.Plugin | x | x | x |No |
|
||||
| | Microsoft.AccountsControl | x | x | x |No |
|
||||
| Hello setup UI | Microsoft.BioEnrollment | x | x | x |No |
|
||||
| | Microsoft.CredDialogHost | x | x | x |No |
|
||||
| | Microsoft.ECApp | | x | x |No |
|
||||
| | Microsoft.LockApp | x | x | x |No |
|
||||
| Microsoft Edge | Microsoft.Microsoft.Edge | x | x | x |No |
|
||||
| | Microsoft.PPIProjection | x | x | x |No |
|
||||
| | Microsoft.Windows. Apprep.ChxApp | x | x | x |No |
|
||||
| | Microsoft.Windows. AssignedAccessLockApp | x | x | x |No |
|
||||
| | Microsoft.Windows. CloudExperienceHost | x | x | x |No |
|
||||
| | Microsoft.Windows. ContentDeliveryManager | x | x | x |No |
|
||||
| Cortana | Microsoft.Windows.Cortana | x | x | x |No |
|
||||
| | Microsoft.Windows. Holographic.FirstRun | x | x | x |No |
|
||||
| | Microsoft.Windows. ModalSharePickerHost | x | | |No |
|
||||
| | Microsoft.Windows. OOBENetworkCaptivePort | x | x | x |No |
|
||||
| | Microsoft.Windows. OOBENetworkConnectionFlow | x | x | x |No |
|
||||
| | Microsoft.Windows. ParentalControls | x | x | x |No |
|
||||
| People Hub | Microsoft.Windows. PeopleExperienceHost | | x | x |No |
|
||||
| | Microsoft.Windows. PinningConfirmationDialog | | x | x |No |
|
||||
| | Microsoft.Windows. SecHealthUI | x | x | x |No |
|
||||
| | Microsoft.Windows. SecondaryTileExperience | x | x | |No |
|
||||
| | Microsoft.Windows. SecureAssessmentBrowser | x | x | x |No |
|
||||
| Start | Microsoft.Windows. ShellExperienceHost | x | x | x |No |
|
||||
| Windows Feedback | Microsoft.WindowsFeedback | * | * | |No |
|
||||
| | Microsoft.XboxGameCallableUI | x | x | x |No |
|
||||
| Contact Support* | Windows.ContactSupport | x | * | |Via Optional Features app |
|
||||
| Settings | Windows.ImmersiveControlPanel | x | x | |No |
|
||||
| Connect | Windows.MiracastView | x | | |No |
|
||||
| Print 3D | Windows.Print3D | | x | |Yes |
|
||||
| Print UI | Windows.PrintDialog | x | x | x |No |
|
||||
| Purchase UI | Windows.PurchaseDialog | | | x |No |
|
||||
| | Microsoft.AsyncTextService | | | x |No |
|
||||
| | Microsoft.MicrosoftEdgeDevToolsClient | | | x |No |
|
||||
| | Microsoft.Win32WebViewHost | | | x |No |
|
||||
| | Microsoft.Windows.CapturePicker | | | x |No |
|
||||
| | Windows.CBSPreview | | | x |No |
|
||||
|File Picker | 1527c705-839a-4832-9118-54d4Bd6a0c89 | | | x |No |
|
||||
|File Explorer | c5e2524a-ea46-4f67-841f-6a9465d9d515 | | | x |No |
|
||||
|App Resolver | E2A4F912-2574-4A75-9BB0-0D023378592B | | | x |No |
|
||||
|Add Suggested folder Dialog box| F46D4000-FD22-4DB4-AC8E-4E1DDDE828FE|| | x |No |
|
||||
> [!TIP]
|
||||
> You can list all system apps with this PowerShell command:
|
||||
> ```
|
||||
> Get-AppxPackage -PackageTypeFilter Main | ? { $_.SignatureKind -eq "System" } | Sort Name | Format-Table Name, InstallLocation
|
||||
> ```
|
||||
|
||||
<br>
|
||||
|
||||
| Name | Package Name | 1703 | 1709 | 1803 | Uninstall through UI? |
|
||||
|----------------------------------|---------------------------------------------|:-----:|:----:|:----:|-----------------------|
|
||||
| File Picker | 1527c705-839a-4832-9118-54d4Bd6a0c89 | | | x | No |
|
||||
| File Explorer | c5e2524a-ea46-4f67-841f-6a9465d9d515 | | | x | No |
|
||||
| App Resolver UX | E2A4F912-2574-4A75-9BB0-0D023378592B | | | x | No |
|
||||
| Add Suggested Folders To Library | F46D4000-FD22-4DB4-AC8E-4E1DDDE828FE | | | x | No |
|
||||
| | InputApp | | x | x | No |
|
||||
| Cortana UI | CortanaListenUIApp | x | | | No |
|
||||
| | Desktop Learning | x | | | No |
|
||||
| | DesktopView | x | | | No |
|
||||
| | EnvironmentsApp | x | | | No |
|
||||
| Mixed Reality + | HoloCamera | x | | | No |
|
||||
| Mixed Reality + | HoloItemPlayerApp | x | | | No |
|
||||
| Mixed Reality + | HoloShell | x | | | No |
|
||||
| | Microsoft.AAD.Broker.Plugin | x | x | x | No |
|
||||
| | Microsoft.AccountsControl | x | x | x | No |
|
||||
| | Microsoft.AsyncTextService | | | x | No |
|
||||
| Hello setup UI | Microsoft.BioEnrollment | x | x | x | No |
|
||||
| | Microsoft.CredDialogHost | x | x | x | No |
|
||||
| | Microsoft.ECApp | | x | x | No |
|
||||
| | Microsoft.LockApp | x | x | x | No |
|
||||
| Microsoft Edge | Microsoft.MicrosoftEdge | x | x | x | No |
|
||||
| | Microsoft.MicrosoftEdgeDevToolsClient | | | x | No |
|
||||
| | Microsoft.PPIProjection | x | x | | No |
|
||||
| | Microsoft.Win32WebViewHost | | | x | No |
|
||||
| | Microsoft.Windows.Apprep.ChxApp | x | x | x | No |
|
||||
| | Microsoft.Windows.AssignedAccessLockApp | x | x | x | No |
|
||||
| | Microsoft.Windows.CapturePicker | | | x | No |
|
||||
| | Microsoft.Windows.CloudExperienceHost | x | x | x | No |
|
||||
| | Microsoft.Windows.ContentDeliveryManager | x | x | x | No |
|
||||
| Cortana | Microsoft.Windows.Cortana | x | x | x | No |
|
||||
| | Microsoft.Windows.Holographic.FirstRun | x | x | | No |
|
||||
| | Microsoft.Windows.ModalSharePickerHost | x | | | No |
|
||||
| | Microsoft.Windows.OOBENetworkCaptivePort | x | x | x | No |
|
||||
| | Microsoft.Windows.OOBENetworkConnectionFlow | x | x | x | No |
|
||||
| | Microsoft.Windows.ParentalControls | x | x | x | No |
|
||||
| People Hub | Microsoft.Windows.PeopleExperienceHost | | x | x | No |
|
||||
| | Microsoft.Windows.PinningConfirmationDialog | | x | x | No |
|
||||
| | Microsoft.Windows.SecHealthUI | x | x | x | No |
|
||||
| | Microsoft.Windows.SecondaryTileExperience | x | x | | No |
|
||||
| | Microsoft.Windows.SecureAssessmentBrowser | x | x | x | No |
|
||||
| Start | Microsoft.Windows.ShellExperienceHost | x | x | x | No |
|
||||
| Windows Feedback | Microsoft.WindowsFeedback | * | * | | No |
|
||||
| | Microsoft.XboxGameCallableUI | x | x | x | No |
|
||||
| | Windows.CBSPreview | | | x | No |
|
||||
| Contact Support* | Windows.ContactSupport | x | * | | Via Settings App |
|
||||
| Settings | Windows.immersivecontrolpanel | x | x | x | No |
|
||||
| Connect | Windows.MiracastView | x | | | No |
|
||||
| Print 3D | Windows.Print3D | | x | | Yes |
|
||||
| Print UI | Windows.PrintDialog | x | x | x | No |
|
||||
| Purchase UI | Windows.PurchaseDialog | | | | No |
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> - The Contact Support app changed to Get Help in version 1709. Get Help is a provisioned app (instead of system app like Contact Support).
|
||||
@ -98,7 +164,7 @@ System apps are integral to the operating system. Here are the typical system ap
|
||||
Here are the typical installed Windows apps in Windows 10 versions 1703, 1709, and 1803.
|
||||
|
||||
| Name | Full name | 1703 | 1709 | 1803 |Uninstall through UI? |
|
||||
|--------------------|------------------------------------------|:----:|:----:|:----:|:----------------------:|
|
||||
|--------------------|------------------------------------------|:----:|:----:|:----:|:---------------------:|
|
||||
| Remote Desktop | Microsoft.RemoteDesktop | x | x | | Yes |
|
||||
| PowerBI | Microsoft.Microsoft PowerBIforWindows | x | | | Yes |
|
||||
| Code Writer | ActiproSoftwareLLC.562882FEEB491 | x | x | x | Yes |
|
||||
@ -127,57 +193,4 @@ Here are the typical installed Windows apps in Windows 10 versions 1703, 1709, a
|
||||
| | Microsoft.VCLibs.120.00.Universal | | x | | Yes |
|
||||
| | Microsoft.VCLibs.140.00.UWPDesktop | | | x | Yes |
|
||||
| | Microsoft.WinJS.2.0 | x | | | Yes |
|
||||
---
|
||||
|
||||
## Provisioned Windows apps
|
||||
|
||||
Here are the typical provisioned Windows apps in Windows 10 versions 1703, 1709, and 1803.
|
||||
|
||||
| Name | Full name | 1703 | 1709 | 1803 | Uninstall through UI? |
|
||||
|---------------------------------|----------------------------------------|:------:|:------:|:------:|:---------------------------:|
|
||||
| 3D Builder | Microsoft.3DBuilder | x | | | Yes |
|
||||
| Alarms & Clock | Microsoft.WindowsAlarms | x | x | x | No |
|
||||
| App Installer | Microsoft.DesktopAppInstaller | x | x | x | Via Settings App |
|
||||
| Calculator | Microsoft.WindowsCalculator | x | x | x | No |
|
||||
| Camera | Microsoft.WindowsCamera | x | x | x | No |
|
||||
| Feedback Hub | Microsoft.WindowsFeedbackHub | x | x | x | Yes |
|
||||
| Get Help | Microsoft.GetHelp | | x | x | No |
|
||||
| Get Office/My Office | Microsoft.Microsoft OfficeHub | x | x | x | Yes |
|
||||
| Get Skype/Skype (preview)/Skype | Microsoft.SkypeApp | x | x | x | Yes |
|
||||
| Get Started/Tips | Microsoft.Getstarted | x | x | x | Yes |
|
||||
| Groove | Microsoft.ZuneMusic | x | x | x | No |
|
||||
| Mail and Calendar | Microsoft.windows communicationsapps | x | x | x | No |
|
||||
| Maps | Microsoft.WindowsMaps | x | x | x | No |
|
||||
| Messaging | Microsoft.Messaging | x | x | x | No |
|
||||
| Microsoft 3D Viewer | Microsoft.Microsoft3DViewer | x | x | x | No |
|
||||
| Movies & TV | Microsoft.ZuneVideo | x | x | x | No |
|
||||
| OneNote | Microsoft.Office.OneNote | x | x | x | Yes |
|
||||
| Paid Wi-FI | Microsoft.OneConnect | x | x | x | Yes |
|
||||
| Paint 3D | Microsoft.MSPaint | x | x | x | No |
|
||||
| People | Microsoft.People | x | x | x | No |
|
||||
| Photos | Microsoft.Windows.Photos | x | x | x | No |
|
||||
| Print 3D | Microsoft.Print3D | | x | x | No |
|
||||
| Solitaire | Microsoft.Microsoft SolitaireCollection| x | x | x | Yes |
|
||||
| Sticky Notes | Microsoft.MicrosoftStickyNotes | x | x | x | No |
|
||||
| Store | Microsoft.WindowsStore | x | x | x | No |
|
||||
| Sway | Microsoft.Office.Sway | * | x | x | Yes |
|
||||
| Voice Recorder | Microsoft.SoundRecorder | x | x | x | No |
|
||||
| Wallet | Microsoft.Wallet | x | x | x | No |
|
||||
| Weather | Microsoft.BingWeather | x | x | x | Yes |
|
||||
| Xbox | Microsoft.XboxApp | x | x | x | No |
|
||||
| | Microsoft.OneConnect | x | x | x | No |
|
||||
| | Microsoft.DesktopAppInstaller | | | x | No |
|
||||
| | Microsoft.StorePurchaseApp | x | x | x | No |
|
||||
| | Microsoft.WebMediaExtensions | | | x | No |
|
||||
| | Microsoft.Xbox.TCUI | | x | x | No |
|
||||
| | Microsoft.XboxGameOverlay | x | x | x | No |
|
||||
| | Microsoft.XboxGamingOverlay | | | x | No |
|
||||
| | Microsoft.XboxIdentityProvider | x | x | x | No |
|
||||
| | Microsoft.XboxSpeech ToTextOverlay | x | x | x | No |
|
||||
---
|
||||
|
||||
>[!NOTE]
|
||||
>The Store app can't be removed. If you want to remove and reinstall the Store app, you can only bring Store back by either restoring your system from a backup or resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it.
|
||||
|
||||
|
||||
---
|
||||
---
|
||||
@ -20,7 +20,7 @@ There are two steps to deploy an app upgrade:
|
||||
1. [Define the supersedence](#define-app-supersedence) - this lets Configuration Manager know that the old version should be replaced by the new version.
|
||||
2. [Deploy the upgrade](#deploy-the-app-upgrade) to your users.
|
||||
|
||||
The following steps walk you through the upgrade deployment process - we have an upgraded version of the Walking Scorer app (moving from version 12.23.2.0 to 12.23.3.0). Becasuse we previously used Configuration Manager to deploy the existing version, we'll use it now to upgrade the app.
|
||||
The following steps walk you through the upgrade deployment process - we have an upgraded version of the Walking Scorer app (moving from version 12.23.2.0 to 12.23.3.0). Because we previously used Configuration Manager to deploy the existing version, we'll use it now to upgrade the app.
|
||||
|
||||
Before you can deploy the upgrade, make sure you import the new version of the app and distribute it to your manage.microsoft.com distribution point.
|
||||
|
||||
@ -42,7 +42,7 @@ Before you can deploy the upgrade, make sure you import the new version of the a
|
||||
> Do **NOT** select **Uninstall**. This tells Configuration Manager to uninstall the old version, but it does **NOT** then install the new version.
|
||||
|
||||
6. Click **OK**.
|
||||
7. If you have other versions of the same app, repeate steps 4-6 for each version. Click **OK** when you're done.
|
||||
7. If you have other versions of the same app, repeat steps 4-6 for each version. Click **OK** when you're done.
|
||||
|
||||
> [!NOTE]
|
||||
> Need to remove a supersedence? (Maybe the new version turned out to be flaky and you don't want users to get it yet.) On the **Supersedence** tab for the *new* version of the app, double-click the older version in the list of supersedence rules, and then change the **New Deployment Type** to **Do not replace**.
|
||||
@ -55,4 +55,4 @@ You don't need to delete the deployment associated with the older version of the
|
||||
|
||||
|
||||
|
||||
If you haven't deployed an app through Configuration Manager before, check out [Deploy applications with System Center Configuration Manager](https://docs.microsoft.com/en-us/sccm/apps/deploy-use/deploy-applications). You can also see how to delete deployments (although you don't have to) and notify users about the upgraded app.
|
||||
If you haven't deployed an app through Configuration Manager before, check out [Deploy applications with System Center Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/deploy-applications). You can also see how to delete deployments (although you don't have to) and notify users about the upgraded app.
|
||||
@ -36,7 +36,6 @@
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "elizapo",
|
||||
"ms.date": "04/05/2017",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
|
||||
@ -1,160 +0,0 @@
|
||||
---
|
||||
title: Learn how to repackage your existing win32 applications to the MSIX format. This walkthrough provides in-depth detail on how the MSIX app packaging tool can be used.
|
||||
description: Learn how to use the MSIX packaging tool with this in-depth walkthrough.
|
||||
keywords: ["MSIX", "application", "app", "win32", "packaging tool"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mikeblodge
|
||||
ms.topic: article
|
||||
ms.date: 08/027/2018
|
||||
---
|
||||
|
||||
# MSIX Packaging tool walkthrough
|
||||
|
||||
Learn how to repackage your legacy win32 application installers to MSIX, without the need for making code changes to your apps. The MSIX Packaging Tool allows you to modernize your app to take adavantage of Microsoft Store or Microsoft Store for Business to deploy apps on Windows 10 in S mode.
|
||||
|
||||
## Terminology
|
||||
|
||||
|
||||
|Term |Definition |
|
||||
|---------|---------|
|
||||
|MPT | MSIX Packaging Tool. An enterprise grade tool that allows to package apps in the enterprise easily as MSIX without app code changes. |
|
||||
|PSF | Package Support Framework. An open source framework to allow the packaging tool and the IT Admin to apply targeted fixes to the app in order to bypass some of the modern environment constrains. Some fixes will be added automatically by the tool and some will be added manually. |
|
||||
|Modification Package | MSIX package to stores app preferences/settings and add-ins, decoupled from the main package. |
|
||||
|Installer | Application installer can be an MSI, EXE, App-V , ClickOnce. |
|
||||
|Project template file | Template file that saves the settings and parameters used for a certain package conversion. Information captured in the template includes general Tooling packaging options, settings in the options menus like exclusion lists, package deployment settings, application install location, package manifest information like Package Family Name, publisher, version and package properties like capabilities and advanced enterprise features. |
|
||||
|
||||
## Creating an Application package
|
||||
|
||||
|
||||
|
||||
When the tool is first launched, you will be prompted to provide consent to sending telemtry data. It's important to note that the diagnostic data you share only comes from the app and is never used to identify or contact you. This just helps us fix things faster for you.
|
||||
|
||||
|
||||
|
||||
Creating an Application package is the most commonly used option. This is where you will create an MSIX package from an installer, or by manual installation of application payload.
|
||||
- If an installer is being used, browse to and select the desired application installer and click **Next**.
|
||||
- This field accepts a valid existing file path.
|
||||
- The field can be empty if you are manually packaging.
|
||||
- If there is no installer (manual packaging) click **Next**.
|
||||
|
||||
*Optionally*
|
||||
- Check the box under "Use Existing MSIX Package", browse, and select an existing MSIX package you'd like to update.
|
||||
- Check the box under "Use installer Preferences" and enter the desired argument in the provided field. This field accepts any string.
|
||||
|
||||
### Packaging method
|
||||
|
||||
- Select the packaging environment by selecting one of the radio buttons:
|
||||
- "Create package on an existing virtual machine" if you plan to do the package creation on a VM. Click **Next**. (You will be presented with user and password fields to provide credentials for the VM if there are any).
|
||||
- "Create package on this computer" if you plan to package the application on the current machine where the tool is installed. Click **Next**.
|
||||
|
||||
### Create package on this computer
|
||||
|
||||
|
||||
|
||||
You've selected to package your application on the current machine where the tool is installed. Nice job! Provide the information pertaining to the app. The tool will try to auto-fill these fields based on the information available from the installer. You will always have a choice to update the entries as needed. If the field as an asterisk*, it's required, but you already knew that. Inline help is provided if the entry is not valid.
|
||||
|
||||
- Package name:
|
||||
- Required and corresponds to package identity Name in the manifest to describe the contents of the package.
|
||||
- Must match the Name subject information of the certificate used to sign a package.
|
||||
- Is not shown to the end user.
|
||||
- Is case-sensitive and cannot have a space.
|
||||
- Can accept string between 3 and 50 characters in length that consists of alpha-numeric, period, and dash characters.
|
||||
- Cannot end with a period and be one of these: "CON", "PRN", "AUX", "NUL", "COM1", "COM2", "COM3", "COM4", "COM5", "COM6", "COM7", "COM8", "COM9", "LPT1", "LPT2", "LPT3", "LPT4", "LPT5", "LPT6", "LPT7", "LPT8", and "LPT9."
|
||||
- Package display name:
|
||||
- Required and corresponds to package <DisplayName> in the manifest to display a friendly package name to the user, in start menu and settings pages.
|
||||
- Field accepts A string between 1 and 256 characters in length and is localizable.
|
||||
- Publisher name
|
||||
- Required and corresponds to package <Publisher Name> that describes the publisher information.
|
||||
- The Publisher attribute must match the publisher subject information of the certificate used to sign a package.
|
||||
- This field accepts a string between 1 and 8192 characters in length that fits the regular expression of a distinguished name : "(CN | L | O | OU | E | C | S | STREET | T | G | I | SN | DC | SERIALNUMBER | Description | PostalCode | POBox | Phone | X21Address | dnQualifier | (OID.(0 | [1-9][0-9])(.(0 | [1-9][0-9]))+))=(([^,+="<>#;])+ | ".")(, ((CN | L | O | OU | E | C | S | STREET | T | G | I | SN | DC | SERIALNUMBER | Description | PostalCode | POBox | Phone | X21Address | dnQualifier | (OID.(0 | [1-9][0-9])(.(0 | [1-9][0-9]))+))=(([^,+="<>#;])+ | ".")))*".
|
||||
- Publisher display name
|
||||
- Reuqired and corresponds to package <PublisherDisplayName> in the manifest to display a friendly publisher name to the user, in App installer and settings pages.
|
||||
- Field accepts A string between 1 and 256 characters in length and is localizable.
|
||||
- Version
|
||||
- Required and corresponds to package <Identity Version> in the manifest to describe the The version number of the package.
|
||||
- This field accepts a version string in quad notation, "Major.Minor.Build.Revision".
|
||||
- Install location
|
||||
- This is the location that the installer is going to copy the application payload to (usually Programs Files folder).
|
||||
- This field is optional but recommended.
|
||||
- Browse to and select a folder path.
|
||||
- Make sure this filed matches Installers Install location while you go through the application install operation.
|
||||
|
||||
### Prepare computer
|
||||
|
||||
|
||||
|
||||
- You are provided with options to prepare the computer for packaging.
|
||||
- MSIX Packaging Tool Driver is required and the tool will automatically try to enable it if it is not enabled.
|
||||
> [!NOTE]
|
||||
> MSIX Packaging tool driver monitors the system to capture the changes that an installer is making on the system which allows MSIX Packaging Tool to create a package based on those changes.
|
||||
- The tool will first check with DISM to see if the driver is installed.
|
||||
- [Optional] Check the box for “Windows Search is Active” and select “disable selected” if you choose to disable the search service.
|
||||
- This is not required, only recommended.
|
||||
- Once disabled, the tool will update the status field to “disabled”
|
||||
- [Optional] Check the box for “Windows Update is Active” and select “disable selected” if you choose to disable the Update service.
|
||||
- This is not required, only recommended.
|
||||
- Once disabled, the tool will update the status field to “disabled”
|
||||
- “Pending reboot” checkbox is disabled by default. You'll need to manually restart the machine and then launch the tool again if you are prompted that pending operations need a reboot.
|
||||
- This not required, only recommended.
|
||||
When you're done preparing the machine, click **Next**.
|
||||
|
||||
### Installation
|
||||
|
||||
|
||||
|
||||
- This is installation phase where the tool is monitoring and capturing the application install operations.
|
||||
- If you've provided an installer, the tool will launch the installer and you'll need to go through the installer wizard to install the application.
|
||||
- Make sure the installation path matches what was defined earlier in the package information page.
|
||||
- You'll need to create a shortcut in desktop for the newly installed application.
|
||||
- Once you're done with the application installation wizard, make sure you finish or close on the installation wizard.
|
||||
- If you need to run multiple installers you can do that manually at this point.
|
||||
- If the app needs other pre-reqs, you need to install them now.
|
||||
- If the application needs .Net 3.5/20, add the optional feature to Windows.
|
||||
- If installer was not provided, manually copy the application binaries to the install location that you've defined earlier in package information.
|
||||
- When you've completed installing the application, click **Next**.
|
||||
|
||||
### Manage first launch tasks
|
||||
|
||||
|
||||
|
||||
- This page shows application executables that the tool captured.
|
||||
- We recommended launching the application at least once to capture any first launch tasks.
|
||||
- If there are multiple applications, check the box that corresponds to the main entry point.
|
||||
- If you don't see the application .exe here, manually browse to and run it.
|
||||
- Click **Next**
|
||||
|
||||
|
||||
|
||||
You'll be prompted with a pop up asking for confirmation that you're finished with application installation and managing first launch tasks.
|
||||
- If you're done, click **Yes, move on**.
|
||||
- If you're not done, click **No, I'm not done**. You'll be taken back to the last page to where you can launch applications, install or copy other files, and dlls/executables.
|
||||
|
||||
### Package support report
|
||||
|
||||
|
||||
|
||||
- Here you'll have a chance to add PSF runtime fixes that might be applicable to the application. *(not supported in preview)*
|
||||
- The tool will make some suggestions and apply fixes that it thinks are applicable.
|
||||
- You'll have the opportunity to add, remove or edit PSF runtime fixes
|
||||
- You can see a list of PSFs provided by the community from Github.
|
||||
- You'll also see a packaging report on this page. The report will call out noteworthy items for example:
|
||||
- If certain restricted capabilities like allowElevation is added
|
||||
- If certain files were excluded from the package.
|
||||
- Etc
|
||||
Once done, click **Next**.
|
||||
|
||||
## Create package
|
||||
|
||||
|
||||
|
||||
- Provide a location to save the MSIX package.
|
||||
- By default, packages are saved in local app data folder.
|
||||
- You can define the default save location in Settings menu.
|
||||
- If you'd like to continue to edit the content and properties of the package before saving the MSIX package, you can select “Package editor” and be taken to package editor.
|
||||
- If you prefer to sign the package with a pre-made certificate for testing, browse to and select the certificate.
|
||||
- Click **Create** to create the MSIX package.
|
||||
|
||||
You'll be presented with the pop up when the package is created. This pop up will include the name, publisher, and save location of the newly created package. You can close this pop up and get redirected to the welcome page. You can also select package editor to see and modify the package content and properties.
|
||||
@ -8,250 +8,30 @@ ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mikeblodge
|
||||
ms.topic: article
|
||||
ms.date: 09/21/2018
|
||||
ms.date: 12/03/2018
|
||||
---
|
||||
|
||||
# Repackage existing win32 applications to the MSIX format
|
||||
|
||||
The MSIX Packaging Tool (Preview) is now available to install from the Microsoft Store. The MSIX Packaging Tool enables you to repackage your existing win32 applications to the MSIX format. You can run your desktop installers through this tool interactively and obtain an MSIX package that you can install on your machine and upload to the Microsoft Store (coming soon).
|
||||
MSIX is a packaging format built to be safe, secure and reliable, based on a combination of .msi, .appx, App-V and ClickOnce installation technologies. You can [use the MSIX packaging tool](https://docs.microsoft.com/windows/msix/packaging-tool/create-app-package-msi-vm) to repackage your existing Win32 applications to the MSIX format.
|
||||
|
||||
> Prerequisites:
|
||||
|
||||
- Participation in the Windows Insider Program
|
||||
- Minimum Windows 10 build 17701
|
||||
- Admin privileges on your PC account
|
||||
- A valid MSA alias (to access the app from the Store)
|
||||
|
||||
## What's new
|
||||
v1.2018.915.0
|
||||
- Updated UI to improve clarity and experience
|
||||
- Ability to generate a template file for use with a command line
|
||||
- Ability to add/remove entry points
|
||||
- Ability to sign your package from package editor
|
||||
- File extension handling
|
||||
|
||||
v1.2018.821.0
|
||||
- Command Line Support
|
||||
- Ability to use existing local virtual machines for packaging environment.
|
||||
- Ability to cross check publisher information in the manifest with a signing certificate to avoid signing issues.
|
||||
- Minor updates to the UI for added clarity.
|
||||
|
||||
v1.2018.807.0
|
||||
- Ability to add/edit/remove file and registry exclusion items is now supported in Settings menu.
|
||||
- Fixed an issue where signing with password protected certificates would fail in the tool.
|
||||
- Fixed an issue where the tool was crashing when editing an existing MSIX package.
|
||||
- Fixed an issue where the tool was injecting whitespaces programmatically to install location paths that was causing conversion failures.
|
||||
- Minor UI tweaks to add clarity.
|
||||
- Minor updates to the logs to add clarity.
|
||||
You can either run your installer interactively (through the UI) or create a package from the command line. Either way, you can convert an application without having the source code. Then, you can make your app available through the Microsoft Store.
|
||||
|
||||
- [Package your favorite application installer](https://docs.microsoft.com/windows/msix/packaging-tool/create-app-package-msi-vm) interactively (msi, exe, App-V 5.x and ClickOnce) in MSIX format.
|
||||
- Create a [modification package](https://docs.microsoft.com/windows/msix/packaging-tool/package-editor) to update an existing MSIX package.
|
||||
- [Bundle multiple MSIX packages](https://docs.microsoft.com/windows/msix/packaging-tool/bundle-msix-packages) for distribution.
|
||||
|
||||
## Installing the MSIX Packaging Tool
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Windows 10, version 1809 (or later)
|
||||
- Participation in the Windows Insider Program (if you're using an Insider build)
|
||||
- A valid Microsoft account (MSA) alias to access the app from the Microsoft Store
|
||||
- Admin privileges on your PC account
|
||||
|
||||
### Get the app from the Microsoft Store
|
||||
|
||||
1. Use the MSA login associated with your Windows Insider Program credentials in the [Microsoft Store](https://www.microsoft.com/store/r/9N5LW3JBCXKF).
|
||||
2. Open the product description page.
|
||||
3. Click the install icon to begin installation.
|
||||
|
||||
This is an early preview build and not all features are supported. Here is what you can expect to be able to do with this preview:
|
||||
|
||||
- Package your favorite application installer interactively (msi, exe, App-V 5.x and ClickOnce) to MSIX format by launching the tool and selecting **Application package** icon.
|
||||
- Create a modification package for a newly created Application MSIX Package by launching the tool and selecting the **Modification package** icon.
|
||||
- Open your MSIX package to view and edit its content/properties by navigating to the **Open package editor** tab. Browse to the MSIX package and select **Open package**.
|
||||
|
||||
## Creating an application package using the Command line interface
|
||||
To create a new MSIX package for your application, run the MsixPackagingTool.exe create-package command in a Command prompt window.
|
||||
|
||||
Here are the parameters that can be passed as command line arguments:
|
||||
|
||||
|
||||
|Parameter |Description |
|
||||
|---------|---------|
|
||||
|-? <br> --help | Show help information |
|
||||
|--template | [required] path to the conversion template XML file containing package information and settings for this conversion |
|
||||
|--virtualMachinePassword | [optional] The password for the Virtual Machine to be used for the conversion environment. Notes: The template file must contain a VirtualMachine element and the Settings::AllowPromptForPassword attribute must not be set to true. |
|
||||
|
||||
Examples:
|
||||
|
||||
- MsixPackagingTool.exe create-package --template c:\users\documents\ConversionTemplate.xml
|
||||
- MSIXPackagingTool.exe create-package --template c:\users\documents\ConversionTemplate.xml --virtualMachinePassword pswd112893
|
||||
|
||||
## Creating an application package using virtual machines
|
||||
|
||||
You can select to perform the packaging steps on a virtual machine. To do this:
|
||||
- Click on Application package and select “Create package on an existing virtual machine” in the select environment page.
|
||||
- The tool will then query for existing Virtual machines and allows you to select one form a drop down menu.
|
||||
- Once a VM is selected the tool will ask for user and password. The username field accepts domain\user entries as well.
|
||||
|
||||
When using local virtual machines as conversion environment, the tool leverages an authenticated remote PowerShell connection to configure the virtual machine. A lightweight WCF server then provides bidirectional communication between the host and target environment.
|
||||
|
||||
Requirements:
|
||||
- Virtual Machine need to have PSRemoting enabled. (Enable-PSRemoting command should be run on the VM)
|
||||
- Virtual Machine needs to be configured for Windows Insider Program similar to the host machine. Minimum Windows 10 build 17701
|
||||
|
||||
|
||||
## Conversion template file
|
||||
|
||||
|
||||
```xml
|
||||
<MsixPackagingToolTemplate
|
||||
xmlns="http://schemas.microsoft.com/appx/msixpackagingtool/template/2018">
|
||||
|
||||
<Settings
|
||||
AllowTelemetry="true"
|
||||
ApplyAllPrepareComputerFixes="true"
|
||||
GenerateCommandLineFile="true"
|
||||
AllowPromptForPassword="false" >
|
||||
|
||||
<ExclusionItems>
|
||||
<FileExclusion ExcludePath="[{CryptoKeys}]" />
|
||||
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Crypto" />
|
||||
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Search\Data" />
|
||||
<FileExclusion ExcludePath="[{Cookies}]" />
|
||||
<FileExclusion ExcludePath="[{History}]" />
|
||||
<FileExclusion ExcludePath="[{Cache}]" />
|
||||
<FileExclusion ExcludePath="[{Personal}]" />
|
||||
<FileExclusion ExcludePath="[{Profile}]\Local Settings" />
|
||||
<FileExclusion ExcludePath="[{Profile}]\NTUSER.DAT.LOG1" />
|
||||
<FileExclusion ExcludePath="[{Profile}]\ NTUSER.DAT.LOG2" />
|
||||
<FileExclusion ExcludePath="[{Recent}]" />
|
||||
<FileExclusion ExcludePath="[{Windows}]\debug" />
|
||||
<FileExclusion ExcludePath="[{Windows}]\Logs\CBS" />
|
||||
<FileExclusion ExcludePath="[{Windows}]\Temp" />
|
||||
<FileExclusion ExcludePath="[{Windows}]\WinSxS\ManifestCache" />
|
||||
<FileExclusion ExcludePath="[{Windows}]\WindowsUpdate.log" />
|
||||
<FileExclusion ExcludePath="[{AppVPackageDrive}]\$Recycle.Bin " />
|
||||
<FileExclusion ExcludePath="[{AppVPackageDrive}]\System Volume Information" />
|
||||
<FileExclusion ExcludePath="[{AppData}]\Microsoft\AppV" />
|
||||
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Microsoft Security Client" />
|
||||
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Microsoft Antimalware" />
|
||||
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Windows Defender" />
|
||||
<FileExclusion ExcludePath="[{ProgramFiles}]\Microsoft Security Client" />
|
||||
<FileExclusion ExcludePath="[{ProgramFiles}]\Windows Defender" />
|
||||
<FileExclusion ExcludePath="[{Local AppData}]\Temp" />
|
||||
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Cryptography" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Cryptography" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware Setup" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Microsoft Security Client" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Microsoft\Windows\CurrentVersion\Explorer\StreamMRU" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\StreamMRU" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\Streams" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\AppV" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\AppV" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Microsoft\AppV" />
|
||||
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Wow6432Node\Microsoft\AppV" />
|
||||
</ExclusionItems>
|
||||
</Settings>
|
||||
|
||||
|
||||
<PrepareComputer
|
||||
DisableDefragService="true"
|
||||
DisableWindowsSearchService="true"
|
||||
DisableSmsHostService="true"
|
||||
DisableWindowsUpdateService ="true"/>
|
||||
<!--Note: this section takes precedence over the Settings::ApplyAllPrepareComputerFixes attribute -->
|
||||
|
||||
<SaveLocation
|
||||
PackagePath="C:\users\user\Desktop\MyPackage.msix"
|
||||
TemplatePath="C:\users\user\Desktop\MyTemplate.xml" />
|
||||
|
||||
<Installer
|
||||
Path="C:\MyAppInstaller.msi"
|
||||
Arguments="/quiet"
|
||||
InstallLocation="C:\Program Files\MyAppInstallLocation" />
|
||||
|
||||
<VirtualMachine Name="vmname" Username="vmusername" />
|
||||
|
||||
<PackageInformation
|
||||
PackageName="MyAppPackageName"
|
||||
PackageDisplayName="MyApp Display Name"
|
||||
PublisherName="CN=MyPublisher"
|
||||
PublisherDisplayName="MyPublisher Display Name"
|
||||
Version="1.1.0.0"
|
||||
MainPackageNameForModificationPackage="MainPackageIdentityName">
|
||||
|
||||
<Applications>
|
||||
<Application
|
||||
Id="MyApp1"
|
||||
Description="MyApp"
|
||||
DisplayName="My App"
|
||||
ExecutableName="MyApp.exe"/>
|
||||
</Applications>
|
||||
|
||||
<Capabilities>
|
||||
<Capability Name="runFullTrust" />
|
||||
</Capabilities>
|
||||
|
||||
</PackageInformation>
|
||||
</MsixPackagingToolTemplate>
|
||||
|
||||
```
|
||||
|
||||
## Conversion template parameter reference
|
||||
Here is the complete list of parameters that you can use in the Conversion template file. When a virtual machine is conversion environment, all file paths(installer, savelocation, etc) should be declared relative to the host, where the tool is running)
|
||||
|
||||
|
||||
|ConversionSettings entries |Description |
|
||||
|---------|---------|
|
||||
|Settings:: AllowTelemetry |[optional] Enables telemetry logging for this invocation of the tool. |
|
||||
|Settings:: ApplyAllPrepareComputerFixes |[optional] Applies all recommended prepare computer fixes. Cannot be set when other attributes are used. |
|
||||
|Settings:: GenerateCommandLineFile |[optional] Copies the template file input to the SaveLocation directory for future use. |
|
||||
|Settings:: AllowPromptForPassword |[optional] Instructs the tool to prompt the user to enter passwords for the Virtual Machine and for the signing certificate if it is required and not specified. |
|
||||
|ExclusionItems |[optional] 0 or more FileExclusion or RegistryExclusion elements. All FileExclusion elements must appear before any RegistryExclusion elements. |
|
||||
|ExclusionItems::FileExclusion |[optional] A file to exclude for packaging. |
|
||||
|ExclusionItems::FileExclusion::ExcludePath |Path to file to exclude for packaging. |
|
||||
|ExclusionItems::RegistryExclusion |[optional] A registry key to exclude for packaging. |
|
||||
|ExclusionItems::RegistryExclusion:: ExcludePath |Path to registry to exclude for packaging. |
|
||||
|PrepareComputer::DisableDefragService |[optional] Disables Windows Defragmenter while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. |
|
||||
|PrepareComputer:: DisableWindowsSearchService |[optional] Disables Windows Search while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. |
|
||||
|PrepareComputer:: DisableSmsHostService |[optional] Disables SMS Host while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. |
|
||||
|PrepareComputer:: DisableWindowsUpdateService |[optional] Disables Windows Update while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. |
|
||||
|SaveLocation |[optional] An element to specify the save location of the tool. If not specified, the package will be saved under the Desktop folder. |
|
||||
|SaveLocation::PackagePath |[optional] The path to the file or folder where the resulting MSIX package is saved. |
|
||||
|SaveLocation::TemplatePath |[optional] The path to the file or folder where the resulting CLI template is saved. |
|
||||
|Installer::Path |The path to the application installer. |
|
||||
|Installer::Arguments |The arguments to pass to the installer. You must pass the arguments to force your installer to run unattended/silently. If the installer is an msi or appv, pass an empty argument ie Installer=””. |
|
||||
|Installer::InstallLocation |[optional] The full path to your application's root folder for the installed files if it were installed (e.g. "C:\Program Files (x86)\MyAppInstalllocation"). |
|
||||
|VirtualMachine |[optional] An element to specify that the conversion will be run on a local Virtual Machine. |
|
||||
|VrtualMachine::Name |The name of the Virtual Machine to be used for the conversion environment. |
|
||||
|VirtualMachine::Username |[optional] The user name for the Virtual Machine to be used for the conversion environment. |
|
||||
|PackageInformation::PackageName |The Package Name for your MSIX package. |
|
||||
|PackageInformation::PackageDisplayName |The Package Display Name for your MSIX package. |
|
||||
|PackageInformation::PublisherName |The Publisher for your MSIX package. |
|
||||
|PackageInformation::PublisherDisplayName |The Publisher Display Name for your MSIX package. |
|
||||
|PackageInformation::Version |The version number for your MSIX package. |
|
||||
|PackageInformation:: MainPackageNameForModificationPackage |[optional] The Package identity name of the main package name. This is used when creating a modification package that takes a dependency on a main (parent) application. |
|
||||
|Applications |[optional] 0 or more Application elements to configure the Application entries in your MSIX package. |
|
||||
|Application::Id |The App ID for your MSIX application. This ID will be used for the Application entry detected that matches the specified ExecutableName. You can have multiple Application ID for executables in the package |
|
||||
|Application::ExecutableName |The executable name for the MSIX application that will be added to the package manifest. The corresponding application entry will be ignored if no application with this name is detected. |
|
||||
|Application::Description |[optional] The App Description for your MSIX application. If not used, the Application DisplayName will be used. This description will be used for the application entry detected that matches the specified ExecutableName |
|
||||
|Application::DisplayName |The App Display Name for your MSIX package. This Display Name will be used for the application entry detected that matches the specified ExecutableName |
|
||||
|Capabilities |[optional] 0 or more Capability elements to add custom capabilities to your MSIX package. “runFullTrust” capability is added by default during conversion. |
|
||||
|Capability::Name |The capability to add to your MSIX package. |
|
||||
|
||||
## Delete temporary conversion files using Command line interface
|
||||
To delete all the temporary package files, logs, and artifacts created by the tool, run the MsixPackagingTool.exe cleanup command in the Command line window.
|
||||
|
||||
Example:
|
||||
- MsixPackagingTool.exe cleanup
|
||||
|
||||
## How to file feedback
|
||||
|
||||
Open Feedback Hub. Alternatively, launch the tool and select the **Settings** gear icon in the top right corner to open the Feedback tab. Here you can file feedback for suggestions, problems, and see other feedback items.
|
||||
|
||||
## Best practices
|
||||
|
||||
- When Packaging ClickOnce installers, it is necessary to send a shortcut to the desktop if the installer is not doing so already. In general, it's a good practice to always send a shortcut to your desktop for the main app executable.
|
||||
- When creating modification packages, you need to declare the **Package Name** (Identity Name) of the parent application in the tool UI so that the tool sets the correct package dependency in the manifest of the modification package.
|
||||
- Declaring an installation location field on the Package information page is optional but *recommended*. Make sure that this path matches the installation location of application Installer.
|
||||
- Performing the preparation steps on the **Prepare Computer** page is optional but *highly recommended*.
|
||||
|
||||
## Known issues
|
||||
1. MSIX Packaging Tool Driver will fail to install if Windows Insider flight ring settings do no match the OS build of the conversion environment. Navigate to Settings, Updates & Security, Windows Insider Program to make sure your Insider preview build settings do not need attention. If you see this message click on the Fix me button to log in again. You might have to go to Windows Update page and check for update before settings change takes effect. Then try to run the tool again to download the MSIX Packaging Tool driver. If you are still hitting issues, try changing your flight ring to Canary or Insider Fast, install the latest Windows updates and try again.
|
||||
2. You cannot edit the manifest manually from within the tool. (edit manifest button is disabled). Please use the SDK tools to unpack the MSIX package to edit the manifest manually.
|
||||
3. Restarting the machine during application installation is not supported. Please ignore the restart request if possible or pass an argument to the installer to not require a restart.
|
||||
|
||||
|
||||
3. Click the install icon to begin installation.
|
||||
@ -68,7 +68,7 @@ For example, this is the registry key configuration for BFE:
|
||||
|
||||
## Memory footprint
|
||||
|
||||
Be aware that separating services increases the total number of SvcHost instances, which increases memory utlization. (Service grouping provided a modest reduction to the overall resource footprint of the services involved.)
|
||||
Be aware that 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:
|
||||
|
||||
|
||||
@ -11,5 +11,20 @@
|
||||
## [Transitioning to modern management](manage-windows-10-in-your-organization-modern-management.md)
|
||||
## [Windows 10 Mobile deployment and management guide](windows-10-mobile-and-mdm.md)
|
||||
## [Windows libraries](windows-libraries.md)
|
||||
## [Troubleshoot Windows 10 clients](windows-10-support-solutions.md)
|
||||
### [Advanced troubleshooting for Windows networking](troubleshoot-networking.md)
|
||||
#### [Advanced troubleshooting Wireless network connectivity](advanced-troubleshooting-wireless-network-connectivity.md)
|
||||
#### [Advanced troubleshooting 802.1X authentication](advanced-troubleshooting-802-authentication.md)
|
||||
##### [Data collection for troubleshooting 802.1X authentication](data-collection-for-802-authentication.md)
|
||||
#### [Advanced troubleshooting for TCP/IP](troubleshoot-tcpip.md)
|
||||
##### [Collect data using Network Monitor](troubleshoot-tcpip-netmon.md)
|
||||
##### [Troubleshoot TCP/IP connectivity](troubleshoot-tcpip-connectivity.md)
|
||||
##### [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)
|
||||
#### [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)
|
||||
#### [Advanced troubleshooting for stop error 7B or Inaccessible_Boot_Device](troubleshoot-inaccessible-boot-device.md)
|
||||
## [Mobile device management for solution providers](mdm/index.md)
|
||||
## [Change history for Client management](change-history-for-client-management.md)
|
||||
|
||||
@ -50,6 +50,10 @@ These tools were included in previous versions of Windows and the associated doc
|
||||
>[!TIP]
|
||||
>If the content that is linked to a tool in the following list doesn't provide the information you need to use that tool, send us a comment by using the **Was this page helpful?** feature on this **Administrative Tools in Windows 10** page. Details about the information you want for a tool will help us plan future content.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Diagnostic Data Viewer](https://docs.microsoft.com/windows/privacy/diagnostic-data-viewer-overview)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,118 @@
|
||||
---
|
||||
title: Advanced Troubleshooting 802.1X Authentication
|
||||
description: Learn how 802.1X Authentication works
|
||||
keywords: advanced troubleshooting, 802.1X authentication, troubleshooting, authentication, Wi-Fi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
ms.sitesec: library
|
||||
author: kaushika-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.author: greg-lindsay
|
||||
---
|
||||
|
||||
# Advanced troubleshooting 802.1X authentication
|
||||
|
||||
## Overview
|
||||
|
||||
This is a general troubleshooting of 802.1X wireless and wired clients. With 802.1X and wireless troubleshooting, it's important to know how the flow of authentication works, and then figuring out where it's breaking. It involves a lot of third party devices and software. Most of the time, we have to identify where the problem is, and another vendor has to fix it. Since we don't make access points or wwitches, it won't be an end-to-end Microsoft solution.
|
||||
|
||||
## Scenarios
|
||||
|
||||
This troubleshooting technique applies to any scenario in which wireless or wired connections with 802.1X authentication is attempted and then fails to establish. The workflow covers Windows 7 - 10 for clients, and Windows Server 2008 R2 - 2012 R2 for NPS.
|
||||
|
||||
## Known Issues
|
||||
|
||||
None
|
||||
|
||||
## Data Collection
|
||||
|
||||
See [Advanced troubleshooting 802.1X authentication data collection](data-collection-for-802-authentication.md).
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
Viewing [NPS authentication status events](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc735320(v%3dws.10)) in the Windows Security [event log](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc722404(v%3dws.11)) is one of the most useful troubleshooting methods to obtain information about failed authentications.
|
||||
|
||||
NPS event log entries contain information on the connection attempt, including the name of the connection request policy that matched the connection attempt and the network policy that accepted or rejected the connection attempt. If you are not seeing both success and failure events, see the section below on [NPS audit policy](#audit-policy).
|
||||
|
||||
Check Windows Security Event log on the NPS Server for NPS events corresponding to rejected ([event ID 6273](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc735399(v%3dws.10))) or accepted ([event ID 6272](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc735388(v%3dws.10))) connection attempts.
|
||||
|
||||
In the event message, scroll to the very bottom, and check the [Reason Code](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd197570(v%3dws.10)) field and the text associated with it.
|
||||
|
||||
|
||||
*Example: event ID 6273 (Audit Failure)*<br><br>
|
||||
|
||||
|
||||
*Example: event ID 6272 (Audit Success)*<br>
|
||||
|
||||
The WLAN AutoConfig operational log lists information and error events based on conditions detected by or reported to the WLAN AutoConfig service. The operational log contains information about the wireless network adapter, the properties of the wireless connection profile, the specified network authentication, and, in the event of connectivity problems, the reason for the failure. For wired network access, Wired AutoConfig operational log is equivalent one.
|
||||
|
||||
On the client side, navigate to **Event Viewer (Local)\Applications and Services Logs\Microsoft\Windows\WLAN-AutoConfig/Operational** for wireless issues. For wired network access issues, navigate to **..\Wired-AutoConfig/Operational**. See the following example:
|
||||
|
||||
|
||||
|
||||
Most 802.1X authentication issues are due to problems with the certificate that is used for client or server authentication (e.g. invalid certificate, expiration, chain verification failure, revocation check failure, etc.).
|
||||
|
||||
First, validate the type of EAP method being used:
|
||||
|
||||
|
||||
|
||||
If a certificate is used for its authentication method, check if the certificate is valid. For server (NPS) side, you can confirm what certificate is being used from the EAP property menu:
|
||||
|
||||
|
||||
|
||||
The CAPI2 event log will be useful for troubleshooting certificate-related issues.
|
||||
This log is not enabled by default. You can enable this log by expanding **Event Viewer (Local)\Applications and Services Logs\Microsoft\Windows\CAPI2**, right-clicking **Operational** and then clicking **Enable Log**.
|
||||
|
||||
|
||||
|
||||
The following article explains how to analyze CAPI2 event logs:
|
||||
[Troubleshooting PKI Problems on Windows Vista](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-vista/cc749296%28v=ws.10%29).
|
||||
|
||||
When troubleshooting complex 802.1X authentication issues, it is important to understand the 802.1X authentication process. The following figure is an example of wireless connection process with 802.1X authentication:
|
||||
|
||||
|
||||
|
||||
If you [collect a network packet capture](troubleshoot-tcpip-netmon.md) on both the client and the server (NPS) side, you can see a flow like the one below. Type **EAPOL** in the Display Filter in for a client side capture, and **EAP** for an NPS side capture. See the following examples:
|
||||
|
||||
|
||||
*Client-side packet capture data*<br><br>
|
||||
|
||||
|
||||
*NPS-side packet capture data*<br>
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> If you have a wireless trace, you can also [view ETL files with network monitor](https://docs.microsoft.com/windows/desktop/ndf/using-network-monitor-to-view-etl-files) and apply the **ONEX_MicrosoftWindowsOneX** and **WLAN_MicrosoftWindowsWLANAutoConfig** Network Monitor filters. Follow the instructions under the **Help** menu in Network Monitor to load the reqired [parser](https://blogs.technet.microsoft.com/netmon/2010/06/04/parser-profiles-in-network-monitor-3-4/) if needed. See the example below.
|
||||
|
||||
|
||||
|
||||
## Audit policy
|
||||
|
||||
NPS audit policy (event logging) for connection success and failure is enabled by default. If you find that one or both types of logging are disabled, use the following steps to troubleshoot.
|
||||
|
||||
View the current audit policy settings by running the following command on the NPS server:
|
||||
```
|
||||
auditpol /get /subcategory:"Network Policy Server"
|
||||
```
|
||||
|
||||
If both success and failure events are enabled, the output should be:
|
||||
<pre>
|
||||
System audit policy
|
||||
Category/Subcategory Setting
|
||||
Logon/Logoff
|
||||
Network Policy Server Success and Failure
|
||||
</pre>
|
||||
|
||||
If it shows ‘No auditing’, you can run this command to enable it:
|
||||
|
||||
```
|
||||
auditpol /set /subcategory:"Network Policy Server" /success:enable /failure:enable
|
||||
```
|
||||
|
||||
Even if audit policy appears to be fully enabled, it sometimes helps to disable and then re-enable this setting. You can also enable Network Policy Server logon/logoff auditing via Group Policy. The success/failure setting can be found under **Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Advanced Audit Policy Configuration -> Audit Policies -> Logon/Logoff -> Audit Network Policy Server**.
|
||||
|
||||
## Additional references
|
||||
|
||||
[Troubleshooting Windows Vista 802.11 Wireless Connections](https://technet.microsoft.com/library/cc766215%28v=ws.10%29.aspx)<br>
|
||||
[Troubleshooting Windows Vista Secure 802.3 Wired Connections](https://technet.microsoft.com/library/cc749352%28v=ws.10%29.aspx)
|
||||
|
||||
@ -0,0 +1,389 @@
|
||||
---
|
||||
title: Advanced troubleshooting for Windows boot problems
|
||||
description: Learn how to troubleshoot when Windows is unable to boot
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
author: kaushika-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.author: elizapo
|
||||
ms.date: 11/16/2018
|
||||
---
|
||||
|
||||
# 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).
|
||||
|
||||
## Summary
|
||||
|
||||
There are several reasons why a Windows-based computer may have problems during startup. To troubleshoot boot problems, first determine in which of the following phases the computer gets stuck:
|
||||
|
||||
| **Phase** | **Boot Process** | **BIOS** | **UEFI** |
|
||||
|--------|----------------------|------------------------------| |
|
||||
| 1 | PreBoot | MBR/PBR (Bootstrap Code) | UEFI Firmware |
|
||||
| 2 | Windows Boot Manager | %SystemDrive%\bootmgr | \EFI\Microsoft\Boot\bootmgfw.efi |
|
||||
| 3 | Windows OS Loader | %SystemRoot%\system32\winload.exe | %SystemRoot%\system32\winload.efi |
|
||||
| 4 | Windows NT OS Kernel | %SystemRoot%\system32\ntoskrnl.exe | |
|
||||
|
||||
|
||||
**1. PreBoot**
|
||||
|
||||
The PC’s firmware initiates a Power-On Self Test (POST) and loads firmware settings. This pre-boot process ends when a valid system disk is detected. Firmware reads the master boot record (MBR), and then starts Windows Boot
|
||||
Manager.
|
||||
|
||||
**2. Windows Boot Manager**
|
||||
|
||||
Windows Boot Manager finds and starts the Windows loader (Winload.exe) on the Windows boot partition.
|
||||
|
||||
**3. Windows operating system loader**
|
||||
|
||||
Essential drivers required to start the Windows kernel are loaded and the kernel starts to run.
|
||||
|
||||
**4. Windows NT OS Kernel**
|
||||
|
||||
The kernel loads into memory the system registry hive and additional drivers that are marked as BOOT_START.
|
||||
|
||||
The kernel passes control to the session manager process (Smss.exe) which initializes the system session, and loads and starts the devices and drivers that are not marked BOOT_START.
|
||||
|
||||
Here is a summary of the boot sequence, what will be seen on the display, and typical boot problems at that point in the sequence. Before starting troubleshooting, you have to understand the outline of the boot process and display status to ensure that the issue is properly identified at the beginning of the engagement.
|
||||
|
||||
<br>
|
||||
[Click to enlarge](img-boot-sequence.md)<br>
|
||||
|
||||
|
||||
|
||||
|
||||
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:
|
||||
>
|
||||
>`Bcdedit /set {default} recoveryenabled no`
|
||||
>
|
||||
>If the F8 options don't work, run the following command:
|
||||
>
|
||||
>`Bcdedit /set {default} bootmenupolicy legacy`
|
||||
|
||||
|
||||
## BIOS phase
|
||||
|
||||
To determine whether the system has passed the BIOS phase, follow these steps:
|
||||
|
||||
1. If there are any external peripherals connected to the computer, disconnect them.
|
||||
2. Check whether the hard disk drive light on the physical computer is working. If it is not working, this indicates that the startup process is stuck at the BIOS phase.
|
||||
3. Press the NumLock key to see whether the indicator light toggles on and off. If it does not, this indicates that the startup process is stuck at BIOS.
|
||||
|
||||
If the system is stuck at the BIOS phase, there may be a hardware problem.
|
||||
|
||||
## Boot loader phase
|
||||
|
||||
If the screen is completely black except for a blinking cursor, or if you receive one of the following error codes, this indicates that the boot process is stuck in the Boot Loader phase:
|
||||
|
||||
- Boot Configuration Data (BCD) missing or corrupted
|
||||
- Boot file or MBR corrupted
|
||||
- Operating system Missing
|
||||
- Boot sector missing or corrupted
|
||||
- Bootmgr missing or corrupted
|
||||
- Unable to boot due to system hive missing or corrupted
|
||||
|
||||
To troubleshoot this problem, use Windows installation media to start the computer, press Shift+F10 for a command prompt, and then use any of the following methods.
|
||||
|
||||
|
||||
### Method 1: Startup Repair tool
|
||||
|
||||
The Startup Repair tool automatically fixes many common problems. The tool also lets you quickly diagnose and repair more complex startup problems. When the computer detects a startup problem, the computer starts the Startup Repair tool. When the tool starts, it performs diagnostics. These diagnostics include analyzing startup log files to determine the cause of the problem. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically.
|
||||
|
||||
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).
|
||||
|
||||
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).
|
||||
|
||||
2. On the **Install Windows** screen, select **Next** > **Repair your computer**.
|
||||
|
||||
3. On the **System Recovery Options** screen, select **Next** > **Command Prompt**.
|
||||
|
||||
4. After Startup Repair, select **Shutdown**, then turn on your PC to see if Windows can boot properly.
|
||||
|
||||
The Startup Repair tool generates a log file to help you understand the startup problems and the repairs that were made. You can find the log file in the following location:
|
||||
|
||||
**%windir%\System32\LogFiles\Srt\Srttrail.txt**
|
||||
|
||||
|
||||
For more information see, [A Stop error occurs, or the computer stops responding when you try to start Windows Vista or Windows 7](https://support.microsoft.com/help/925810/a-stop-error-occurs-or-the-computer-stops-responding-when-you-try-to-s)
|
||||
|
||||
|
||||
### Method 2: Repair Boot Codes
|
||||
|
||||
To repair boot codes, run the following command:
|
||||
|
||||
```dos
|
||||
BOOTREC /FIXMBR
|
||||
```
|
||||
|
||||
To repair the boot sector, run the following command:
|
||||
|
||||
```dos
|
||||
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.
|
||||
|
||||
### Method 3: Fix BCD errors
|
||||
|
||||
If you receive BCD-related errors, follow these steps:
|
||||
|
||||
1. Scan for all the systems that are installed. To do this, run the following command:
|
||||
```dos
|
||||
Bootrec /ScanOS
|
||||
```
|
||||
|
||||
2. Restart the computer to check whether the problem is fixed.
|
||||
|
||||
3. If the problem is not fixed, run the following command:
|
||||
```dos
|
||||
Bootrec /rebuildbcd
|
||||
```
|
||||
|
||||
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
|
||||
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
|
||||
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
|
||||
|
||||
ren c:\\boot\\bcd bcd.old
|
||||
|
||||
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
|
||||
Add installation to boot list? Yes/No/All: Y
|
||||
|
||||
5. Try again to start 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:
|
||||
|
||||
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
|
||||
```
|
||||
|
||||
3. Run the same **attrib** command on the Windows (system drive):
|
||||
```dos
|
||||
attrib-s -h –r
|
||||
```
|
||||
|
||||
4. Rename the Bootmgr file as Bootmgr.old:
|
||||
```dos
|
||||
ren c:\\bootmgr bootmgr.old
|
||||
```
|
||||
|
||||
5. Start a text editor, such as Notepad.
|
||||
|
||||
6. Navigate to the system drive.
|
||||
|
||||
7. Copy the Bootmgr file, and then paste it to the System Reserved partition.
|
||||
|
||||
8. Restart the computer.
|
||||
|
||||
### Method 5: Restore System Hive
|
||||
|
||||
If Windows cannot load the system registry hive into memory, you must restore the system hive. To do this, use the Windows Recovery Environment or use Emergency Repair Disk (ERD) to copy the files from the C:\Windows\System32\config\RegBack to C:\Windows\System32\config.
|
||||
|
||||
If the problem persists, you may want to restore the system state backup to an alternative location, and then retrieve the registry hives to be replaced.
|
||||
|
||||
|
||||
## Kernel Phase
|
||||
|
||||
If the system gets stuck during the kernel phase, you experience multiple symptoms or receive multiple error messages. These include, but are not limited to, the following:
|
||||
|
||||
- A Stop error appears after the splash screen (Windows Logo screen).
|
||||
|
||||
- Specific error code is displayed.
|
||||
For example, "0x00000C2" , "0x0000007B" , "inaccessible boot device" and so on.
|
||||
(To troubleshoot the 0x0000007B error, see [Error code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)](https://internal.support.services.microsoft.com/help/4343769/troubleshooting-guide-for-windows-boot-problems#0x7bstoperror))
|
||||
|
||||
- The screen is stuck at the "spinning wheel" (rolling dots) "system busy" icon.
|
||||
|
||||
- A black screen appears after the splash screen.
|
||||
|
||||
To troubleshoot these problems, try the following recovery boot options one at a time.
|
||||
|
||||
**Scenario 1: Try to start the computer in Safe mode or Last Known Good Configuration**
|
||||
|
||||
On the **Advanced Boot Options** screen, try to start the computer in **Safe Mode** or **Safe Mode with Networking**. If either of these options works, use Event Viewer to help identify and diagnose the cause of the boot problem. To view events that are recorded in the event logs, follow these steps:
|
||||
|
||||
1. Use one of the following methods to open Event Viewer:
|
||||
|
||||
- Click **Start**, point to **Administrative Tools**, and then click
|
||||
**Event Viewer**.
|
||||
|
||||
- Start the Event Viewer snap-in in Microsoft Management Console (MMC).
|
||||
|
||||
2. In the console tree, expand Event Viewer, and then click the log that you
|
||||
want to view. For example, click **System log** or **Application log**.
|
||||
|
||||
3. In the details pane, double-click the event that you want to view.
|
||||
|
||||
4. On the **Edit** menu, click **Copy**, open a new document in the program in
|
||||
which you want to paste the event (for example, Microsoft Word), and then
|
||||
click **Paste**.
|
||||
|
||||
5. Use the Up Arrow or Down Arrow key to view the description of the previous
|
||||
or next event.
|
||||
|
||||
|
||||
### Clean boot
|
||||
|
||||
To troubleshoot problems that affect services, do a clean boot by using System Configuration (msconfig).
|
||||
Select **Selective startup** to test the services one at a time to determine which one is causing the problem. If you cannot find the cause, try including system services. However, in most cases, the problematic service is third-party.
|
||||
|
||||
Disable any service that you find to be faulty, and try to start the computer again by selecting **Normal startup**.
|
||||
|
||||
For detailed instructions, see [How to perform a clean boot in Windows](https://support.microsoft.com/help/929135/how-to-perform-a-clean-boot-in-windows).
|
||||
|
||||
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).
|
||||
>
|
||||
>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
|
||||
problems can be solved. Modify the registry at your own risk.
|
||||
|
||||
*Error code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)*
|
||||
|
||||
To troubleshoot this Stop error, follow these steps to filter the drivers:
|
||||
|
||||
1. Go to Window Recovery Environment (WinRE) by putting an ISO disk of the system in the disk drive. The ISO should be of same version of Windows or a later version.
|
||||
|
||||
2. Open the registry.
|
||||
|
||||
3. Load the system hive, and name it as "test."
|
||||
|
||||
4. Under the following registry subkey, check for lower filter and upper filter items for Non-Microsoft Drivers:
|
||||
|
||||
**HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Class**
|
||||
|
||||
5. For each third-party driver that you locate, click the upper or lower filter, and then delete the value data.
|
||||
|
||||
6. Search through the whole registry for similar items. Process as an appropriate, and then unload the registry hive.
|
||||
|
||||
7. Restart the server in Normal mode.
|
||||
|
||||
For additional troubleshooting steps, see the following articles:
|
||||
|
||||
- [Troubleshooting a Stop 0x7B in Windows](https://blogs.technet.microsoft.com/askcore/2013/08/05/troubleshooting-a-stop-0x7b-in-windows/)
|
||||
|
||||
- [Advanced troubleshooting for "Stop error code 0x0000007B (INACCESSIBLE_BOOT_DEVICE)" errors in Windows XP](https://internal.support.services.microsoft.com/help/324103).
|
||||
|
||||
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.
|
||||
|
||||
2. Run the command:
|
||||
```dos
|
||||
dism /image:C:\ /get-packages
|
||||
```
|
||||
|
||||
3. If there are any pending updates, uninstall them by running the following commands:
|
||||
```dos
|
||||
DISM /image:C:\ /remove-package /packagename: name of the package
|
||||
```
|
||||
```dos
|
||||
Dism /Image:C:\ /Cleanup-Image /RevertPendingActions
|
||||
```
|
||||
|
||||
Try to start the computer.
|
||||
|
||||
If the computer does not start, follow these steps:
|
||||
|
||||
1. Open A Command Prompt window in WinRE, and start a text editor, such as Notepad.
|
||||
|
||||
2. Navigate to the system drive, and search for windows\winsxs\pending.xml.
|
||||
|
||||
3. If the Pending.xml file is found, rename the file as Pending.xml.old.
|
||||
|
||||
4. Open the registry, and then load the component hive in HKEY_LOCAL_MACHINE as a test.
|
||||
|
||||
5. Highlight the loaded test hive, and then search for the **pendingxmlidentifier** value.
|
||||
|
||||
6. If the **pendingxmlidentifier** value exists, delete the value.
|
||||
|
||||
7. Unload the test hive.
|
||||
|
||||
8. Load the system hive, name it as "test".
|
||||
|
||||
9. Navigate to the following subkey:
|
||||
|
||||
**HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Services\\TrustedInstaller**
|
||||
|
||||
10. Change the **Start** value from **1** to **4**
|
||||
|
||||
11. Unload the hive.
|
||||
|
||||
12. Try to start the computer.
|
||||
|
||||
If the Stop error occurs late in the startup process, or if the Stop error is still being generated, you can capture a memory dump. A good memory dump can help determine the root cause of the Stop error. For details, see the following Knowledge Base article:
|
||||
|
||||
- [969028](https://support.microsoft.com/help/969028) How to generate a kernel or a complete memory dump file in Windows Server 2008 and Windows Server 2008 R2
|
||||
|
||||
For more information about page file problems in Windows 10 or Windows Server 2016, see the following Knowledge Base article:
|
||||
|
||||
- [4133658](https://support.microsoft.com/help/4133658) Introduction of page file in Long-Term Servicing Channel and Semi-Annual Channel of Windows
|
||||
|
||||
For more information about Stop errors, see the following Knowledge Base article:
|
||||
|
||||
- [3106831](https://support.microsoft.com/help/3106831) Troubleshooting Stop error problems for IT Pros
|
||||
|
||||
|
||||
If the dump file shows an error that is related to a driver (for example, windows\system32\drivers\stcvsm.sys is missing or corrupted), follow these guidelines:
|
||||
|
||||
- Check the functionality that is provided by the driver. If the driver is a third-party boot driver, make sure that you understand what it does.
|
||||
|
||||
- If the driver is not important and has no dependencies, load the system hive, and then disable the driver.
|
||||
|
||||
- If the stop error indicates system file corruption, run the system file checker in offline mode.
|
||||
- To do this, open WinRE, open a command prompt, and then run the following command:
|
||||
```dos
|
||||
SFC /Scannow /OffBootDir=C:\ /OffWinDir=E:\Windows
|
||||
```
|
||||
For more information, see [Using System File Checker (SFC) To Fix Issues](https://blogs.technet.microsoft.com/askcore/2007/12/18/using-system-file-checker-sfc-to-fix-issues/)
|
||||
|
||||
- If there is disk corruption, run the check disk command:
|
||||
```dos
|
||||
chkdsk /f /r
|
||||
```
|
||||
|
||||
- If the Stop error indicates general registry corruption, or if you believe that new drivers or services were installed, follow these steps:
|
||||
|
||||
1. Start WinRE, and open a Command Prompt window.
|
||||
2. Start a text editor, such as Notepad.
|
||||
3. Navigate to C\Windows\System32\Config\.
|
||||
4. Rename the all five hives by appending ".old" to the name.
|
||||
5. Copy all the hives from the Regback folder, paste them in the Config folder, and then try to start the computer in Normal mode.
|
||||
@ -0,0 +1,326 @@
|
||||
---
|
||||
title: Advanced Troubleshooting Wireless Network Connectivity
|
||||
description: Learn how troubleshooting of establishing Wi-Fi connections
|
||||
keywords: troubleshooting, wireless network connectivity, wireless, Wi-Fi
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
ms.sitesec: library
|
||||
author: kaushika-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.author: greg-lindsay
|
||||
---
|
||||
|
||||
# Advanced troubleshooting wireless network connectivity
|
||||
|
||||
> [!NOTE]
|
||||
> Home users: This article is intended for use by support agents and IT professionals. If you're looking for more general information about Wi-Fi problems in Windows 10, check out this [Windows 10 Wi-Fi fix article](https://support.microsoft.com/en-in/help/4000432/windows-10-fix-wi-fi-problems).
|
||||
|
||||
## Overview
|
||||
|
||||
This is a general troubleshooting of establishing Wi-Fi connections from Windows clients.
|
||||
Troubleshooting Wi-Fi connections requires understanding the basic flow of the Wi-Fi autoconnect state machine. Understanding this flow makes it easier to determine the starting point in a repro scenario in which a different behavior is found.
|
||||
This workflow involves knowledge and use of [TextAnalysisTool](https://github.com/TextAnalysisTool/Releases), an extensive text filtering tool that is useful with complex traces with numerous ETW providers such as wireless_dbg trace scenario.
|
||||
|
||||
## Scenarios
|
||||
|
||||
This article applies to any scenario in which Wi-Fi connections fail to establish. The troubleshooter is developed with Windows 10 clients in focus, but also may be useful with traces as far back as Windows 7.
|
||||
|
||||
> [!NOTE]
|
||||
> This troubleshooter uses examples that demonstrate a general strategy for navigating and interpreting wireless component [Event Tracing for Windows](https://docs.microsoft.com/windows/desktop/etw/event-tracing-portal) (ETW). It is not meant to be representative of every wireless problem scenario.
|
||||
|
||||
Wireless ETW is incredibly verbose and calls out a lot of innocuous errors (rather flagged behaviors that have little or nothing to do with the problem scenario). Simply searching for or filtering on "err", "error", and "fail" will seldom lead you to the root cause of a problematic Wi-Fi scenario. Instead it will flood the screen with meaningless logs that will obfuscate the context of the actual problem.
|
||||
|
||||
It is important to understand the different Wi-Fi components involved, their expected behaviors, and how the problem scenario deviates from those expected behaviors.
|
||||
The intention of this troubleshooter is to show how to find a starting point in the verbosity of wireless_dbg ETW and home in on the responsible components that are causing the connection problem.
|
||||
|
||||
### Known Issues and fixes
|
||||
** **
|
||||
| **OS version** | **Fixed in** |
|
||||
| --- | --- |
|
||||
| **Windows 10, version 1803** | [KB4284848](https://support.microsoft.com/help/4284848) |
|
||||
| **Windows 10, version 1709** | [KB4284822](https://support.microsoft.com/help/4284822) |
|
||||
| **Windows 10, version 1703** | [KB4338827](https://support.microsoft.com/help/4338827) |
|
||||
|
||||
Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update-history webpage for your system:
|
||||
- [Windows 10 version 1809](https://support.microsoft.com/help/4464619)
|
||||
- [Windows 10 version 1803](https://support.microsoft.com/help/4099479)
|
||||
- [Windows 10 version 1709](https://support.microsoft.com/en-us/help/4043454)
|
||||
- [Windows 10 version 1703](https://support.microsoft.com/help/4018124)
|
||||
- [Windows 10 version 1607 and Windows Server 2016](https://support.microsoft.com/help/4000825)
|
||||
- [Windows 10 version 1511](https://support.microsoft.com/help/4000824)
|
||||
- [Windows 8.1 and Windows Server 2012 R2](https://support.microsoft.com/help/4009470)
|
||||
- [Windows Server 2012](https://support.microsoft.com/help/4009471)
|
||||
- [Windows 7 SP1 and Windows Server 2008 R2 SP1](https://support.microsoft.com/help/40009469)
|
||||
|
||||
## Data Collection
|
||||
|
||||
1. Network Capture with ETW. Enter the following at an elevated command prompt:
|
||||
|
||||
```
|
||||
netsh trace start wireless_dbg capture=yes overwrite=yes maxsize=4096 tracefile=c:\tmp\wireless.etl
|
||||
```
|
||||
2. Reproduce the issue.
|
||||
- If there is a failure to establish connection, try to manually connect.
|
||||
- If it is intermittent but easily reproducible, try to manually connect until it fails. Record the time of each connection attempt, and whether it was a success or failure.
|
||||
- If the issue is intermittent but rare, netsh trace stop command needs to be triggered automatically (or at least alerted to admin quickly) to ensure trace doesn’t overwrite the repro data.
|
||||
- If intermittent connection drops trigger stop command on a script (ping or test network constantly until fail, then netsh trace stop).
|
||||
3. Stop the trace by entering the following command:
|
||||
|
||||
```
|
||||
netsh trace stop
|
||||
```
|
||||
4. To convert the output file to text format:
|
||||
|
||||
```
|
||||
netsh trace convert c:\tmp\wireless.etl
|
||||
```
|
||||
|
||||
See the [example ETW capture](#example-etw-capture) at the bottom of this article for an example of the command output. After running these commands, you will have three files: wireless.cab, wireless.etl, and wireless.txt.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
The following is a high-level view of the main wifi components in Windows.
|
||||
|
||||
<table>
|
||||
<tr><td><img src="images/wcm.png"></td><td>The <b>Windows Connection Manager</b> (Wcmsvc) is closely associated with the UI controls (taskbar icon) to connect to various networks, including wireless networks. It accepts and processes input from the user and feeds it to the core wireless service. </td></tr>
|
||||
<tr><td><img src="images/wlan.png"></td><td>The <b>WLAN Autoconfig Service</b> (WlanSvc) handles the following core functions of wireless networks in windows:
|
||||
|
||||
- Scanning for wireless networks in range
|
||||
- Managing connectivity of wireless networks</td></tr>
|
||||
<tr><td><img src="images/msm.png"></td><td>The <b>Media Specific Module</b> (MSM) handles security aspects of connection being established.</td></tr>
|
||||
<tr><td><img src="images/wifi-stack.png"></td><td>The <b>Native Wifi stack</b> consists of drivers and wireless APIs to interact with wireless miniports and the supporting user-mode Wlansvc.</td></tr>
|
||||
<tr><td><img src="images/miniport.png"></td><td>Third-party <b>wireless miniport</b> drivers interface with the upper wireless stack to provide notifications to and receive commands from Windows.</td></tr>
|
||||
</table>
|
||||
|
||||
|
||||
The wifi connection state machine has the following states:
|
||||
- Reset
|
||||
- Ihv_Configuring
|
||||
- Configuring
|
||||
- Associating
|
||||
- Authenticating
|
||||
- Roaming
|
||||
- Wait_For_Disconnected
|
||||
- Disconnected
|
||||
|
||||
Standard wifi connections tend to transition between states such as:
|
||||
|
||||
**Connecting**
|
||||
|
||||
Reset --> Ihv_Configuring --> Configuring --> Associating --> Authenticating --> Connected
|
||||
|
||||
**Disconnecting**
|
||||
|
||||
Connected --> Roaming --> Wait_For_Disconnected --> Disconnected --> Reset
|
||||
|
||||
>Filtering the ETW trace with the [TextAnalysisTool](https://github.com/TextAnalysisTool/Releases) (TAT) is an easy first step to determine where a failed connection setup is breaking down. A useful [wifi filter file](#wifi-filter-file) is included at the bottom of this article.
|
||||
|
||||
Use the **FSM transition** trace filter to see the connection state machine. You can see [an example](#textanalysistool-example) of this filter applied in the TAT at the bottom of this page.
|
||||
|
||||
The following is an example of a good connection setup:
|
||||
|
||||
<pre>
|
||||
44676 [2]0F24.1020::2018-09-17 10:22:14.658 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Disconnected to State: Reset
|
||||
45473 [1]0F24.1020::2018-09-17 10:22:14.667 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Reset to State: Ihv_Configuring
|
||||
45597 [3]0F24.1020::2018-09-17 10:22:14.708 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Ihv_Configuring to State: Configuring
|
||||
46085 [2]0F24.17E0::2018-09-17 10:22:14.710 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Configuring to State: Associating
|
||||
47393 [1]0F24.1020::2018-09-17 10:22:14.879 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Associating to State: Authenticating
|
||||
49465 [2]0F24.17E0::2018-09-17 10:22:14.990 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Authenticating to State: Connected
|
||||
</pre>
|
||||
|
||||
The following is an example of a failed connection setup:
|
||||
|
||||
<pre>
|
||||
44676 [2]0F24.1020::2018-09-17 10:22:14.658 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Disconnected to State: Reset
|
||||
45473 [1]0F24.1020::2018-09-17 10:22:14.667 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Reset to State: Ihv_Configuring
|
||||
45597 [3]0F24.1020::2018-09-17 10:22:14.708 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Ihv_Configuring to State: Configuring
|
||||
46085 [2]0F24.17E0::2018-09-17 10:22:14.710 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Configuring to State: Associating
|
||||
47393 [1]0F24.1020::2018-09-17 10:22:14.879 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Associating to State: Authenticating
|
||||
49465 [2]0F24.17E0::2018-09-17 10:22:14.990 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State: Authenticating to State: Roaming
|
||||
</pre>
|
||||
|
||||
By identifying the state at which the connection fails, one can focus more specifically in the trace on logs just prior to the last known good state.
|
||||
|
||||
Examining **[Microsoft-Windows-WLAN-AutoConfig]** logs just prior to the bad state change should show evidence of error. Often, however, the error is propagated up through other wireless components.
|
||||
In many cases the next component of interest will be the MSM, which lies just below Wlansvc.
|
||||
|
||||
The important components of the MSM include:
|
||||
- Security Manager (SecMgr) - handles all pre and post-connection security operations.
|
||||
- Authentication Engine (AuthMgr) – Manages 802.1x auth requests
|
||||
|
||||
|
||||
|
||||
Each of these components has their own individual state machines which follow specific transitions.
|
||||
Enable the **FSM transition, SecMgr Transition,** and **AuthMgr Transition** filters in TextAnalysisTool for more detail.
|
||||
|
||||
Continuing with the example above, the combined filters look like this:
|
||||
|
||||
<pre>
|
||||
[2] 0C34.2FF0::08/28/17-13:24:28.693 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Reset to State: Ihv_Configuring
|
||||
[2] 0C34.2FF0::08/28/17-13:24:28.693 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Ihv_Configuring to State: Configuring
|
||||
[1] 0C34.2FE8::08/28/17-13:24:28.711 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Configuring to State: Associating
|
||||
[0] 0C34.275C::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition INACTIVE (1) --> ACTIVE (2)
|
||||
[0] 0C34.275C::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition ACTIVE (2) --> START AUTH (3)
|
||||
[4] 0EF8.0708::08/28/17-13:24:28.928 [Microsoft-Windows-WLAN-AutoConfig]Port (14) Peer 0x186472F64FD2 AuthMgr Transition ENABLED --> START_AUTH
|
||||
[3] 0C34.2FE8::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Associating to State: Authenticating
|
||||
[1] 0C34.275C::08/28/17-13:24:28.960 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition START AUTH (3) --> WAIT FOR AUTH SUCCESS (4)
|
||||
[4] 0EF8.0708::08/28/17-13:24:28.962 [Microsoft-Windows-WLAN-AutoConfig]Port (14) Peer 0x186472F64FD2 AuthMgr Transition START_AUTH --> AUTHENTICATING
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.751 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition WAIT FOR AUTH SUCCESS (7) --> DEACTIVATE (11)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7512788 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7513404 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Authenticating to State: Roaming
|
||||
</pre>
|
||||
|
||||
> [!NOTE]
|
||||
> In the next to last line the SecMgr transition is suddenly deactivating:<br>
|
||||
>\[2\] 0C34.2FF0::08/28/17-13:24:29.7512788 \[Microsoft-Windows-WLAN-AutoConfig\]Port\[13\] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)<br><br>
|
||||
>This transition is what eventually propagates to the main connection state machine and causes the Authenticating phase to devolve to Roaming state. As before, it makes sense to focus on tracing just prior to this SecMgr behavior to determine the reason for the deactivation.
|
||||
|
||||
Enabling the **Microsoft-Windows-WLAN-AutoConfig** filter will show more detail leading to the DEACTIVATE transition:
|
||||
|
||||
<pre>
|
||||
[3] 0C34.2FE8::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Associating to State: Authenticating
|
||||
[1] 0C34.275C::08/28/17-13:24:28.960 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition START AUTH (3) --> WAIT FOR AUTH SUCCESS (4)
|
||||
[4] 0EF8.0708::08/28/17-13:24:28.962 [Microsoft-Windows-WLAN-AutoConfig]Port (14) Peer 0x186472F64FD2 AuthMgr Transition START_AUTH --> AUTHENTICATING
|
||||
[0]0EF8.2EF4::08/28/17-13:24:29.549 [Microsoft-Windows-WLAN-AutoConfig]Received Security Packet: PHY_STATE_CHANGE
|
||||
[0]0EF8.2EF4::08/28/17-13:24:29.549 [Microsoft-Windows-WLAN-AutoConfig]Change radio state for interface = Intel(R) Centrino(R) Ultimate-N 6300 AGN : PHY = 3, software state = on , hardware state = off )
|
||||
[0] 0EF8.1174::08/28/17-13:24:29.705 [Microsoft-Windows-WLAN-AutoConfig]Received Security Packet: PORT_DOWN
|
||||
[0] 0EF8.1174::08/28/17-13:24:29.705 [Microsoft-Windows-WLAN-AutoConfig]FSM Current state Authenticating , event Upcall_Port_Down
|
||||
[0] 0EF8.1174:: 08/28/17-13:24:29.705 [Microsoft-Windows-WLAN-AutoConfig]Received IHV PORT DOWN, peer 0x186472F64FD2
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.751 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition WAIT FOR AUTH SUCCESS (7) --> DEACTIVATE (11)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7512788 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7513404 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Authenticating to State: Roaming
|
||||
</pre>
|
||||
|
||||
The trail backwards reveals a **Port Down** notification:
|
||||
|
||||
\[0\] 0EF8.1174:: 08/28/17-13:24:29.705 \[Microsoft-Windows-WLAN-AutoConfig\]Received IHV PORT DOWN, peer 0x186472F64FD2
|
||||
|
||||
Port events indicate changes closer to the wireless hardware. The trail can be followed by continuing to see the origin of this indication.
|
||||
|
||||
Below, the MSM is the native wifi stack. These are Windows native wifi drivers which talk to the wifi miniport drivers. It is responsible for converting Wi-Fi (802.11) packets to 802.3 (Ethernet) so that TCPIP and other protocols and can use it.
|
||||
|
||||
Enable trace filter for **[Microsoft-Windows-NWifi]:**
|
||||
|
||||
<pre>
|
||||
[3] 0C34.2FE8::08/28/17-13:24:28.902 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Associating to State: Authenticating
|
||||
[1] 0C34.275C::08/28/17-13:24:28.960 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition START AUTH (3) --> WAIT FOR AUTH SUCCESS (4)
|
||||
[4] 0EF8.0708::08/28/17-13:24:28.962 [Microsoft-Windows-WLAN-AutoConfig]Port (14) Peer 0x8A1514B62510 AuthMgr Transition START_AUTH --> AUTHENTICATING
|
||||
[0]0000.0000::08/28/17-13:24:29.127 [Microsoft-Windows-NWiFi]DisAssoc: 0x8A1514B62510 Reason: 0x4
|
||||
[0]0EF8.2EF4::08/28/17-13:24:29.549 [Microsoft-Windows-WLAN-AutoConfig]Received Security Packet: PHY_STATE_CHANGE
|
||||
[0]0EF8.2EF4::08/28/17-13:24:29.549 [Microsoft-Windows-WLAN-AutoConfig]Change radio state for interface = Intel(R) Centrino(R) Ultimate-N 6300 AGN : PHY = 3, software state = on , hardware state = off )
|
||||
[0] 0EF8.1174::08/28/17-13:24:29.705 [Microsoft-Windows-WLAN-AutoConfig]Received Security Packet: PORT_DOWN
|
||||
[0] 0EF8.1174::08/28/17-13:24:29.705 [Microsoft-Windows-WLAN-AutoConfig]FSM Current state Authenticating , event Upcall_Port_Down
|
||||
[0] 0EF8.1174:: 08/28/17-13:24:29.705 [Microsoft-Windows-WLAN-AutoConfig]Received IHV PORT DOWN, peer 0x186472F64FD2
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.751 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition WAIT FOR AUTH SUCCESS (7) --> DEACTIVATE (11)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7512788 [Microsoft-Windows-WLAN-AutoConfig]Port[13] Peer 8A:15:14:B6:25:10 SecMgr Transition DEACTIVATE (11) --> INACTIVE (1)
|
||||
[2] 0C34.2FF0::08/28/17-13:24:29.7513404 [Microsoft-Windows-WLAN-AutoConfig]FSM Transition from State:
|
||||
Authenticating to State: Roaming</pre>
|
||||
|
||||
In the trace above, we see the line:
|
||||
|
||||
<pre>
|
||||
[0]0000.0000::08/28/17-13:24:29.127 [Microsoft-Windows-NWiFi]DisAssoc: 0x8A1514B62510 Reason: 0x4</pre>
|
||||
|
||||
This is followed by **PHY_STATE_CHANGE** and **PORT_DOWN** events due to a disassociate coming from the Access Point (AP), as an indication to deny the connection. This could be due to invalid credentials, connection parameters, loss of signal/roaming, and various other reasons for aborting a connection. The action here would be to examine the reason for the disassociate sent from the indicated AP MAC (8A:15:14:B6:25:10). This would be done by examining internal logging/tracing from the AP.
|
||||
|
||||
### Resources
|
||||
|
||||
[802.11 Wireless Tools and Settings](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc755892(v%3dws.10))<br>
|
||||
[Understanding 802.1X authentication for wireless networks](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc759077%28v%3dws.10%29)<br>
|
||||
|
||||
## Example ETW capture
|
||||
|
||||
<pre>
|
||||
C:\tmp>netsh trace start wireless_dbg capture=yes overwrite=yes maxsize=4096 tracefile=c:\tmp\wireless.etl
|
||||
|
||||
Trace configuration:
|
||||
-------------------------------------------------------------------
|
||||
Status: Running
|
||||
Trace File: C:\tmp\wireless.etl
|
||||
Append: Off
|
||||
Circular: On
|
||||
Max Size: 4096 MB
|
||||
Report: Off
|
||||
|
||||
C:\tmp>netsh trace stop
|
||||
Correlating traces ... done
|
||||
Merging traces ... done
|
||||
Generating data collection ... done
|
||||
The trace file and additional troubleshooting information have been compiled as "c:\tmp\wireless.cab".
|
||||
File location = c:\tmp\wireless.etl
|
||||
Tracing session was successfully stopped.
|
||||
|
||||
C:\tmp>netsh trace convert c:\tmp\wireless.etl
|
||||
|
||||
Input file: c:\tmp\wireless.etl
|
||||
Dump file: c:\tmp\wireless.txt
|
||||
Dump format: TXT
|
||||
Report file: -
|
||||
Generating dump ... done
|
||||
|
||||
C:\tmp>dir
|
||||
Volume in drive C has no label.
|
||||
Volume Serial Number is 58A8-7DE5
|
||||
|
||||
Directory of C:\tmp
|
||||
|
||||
01/09/2019 02:59 PM [DIR] .
|
||||
01/09/2019 02:59 PM [DIR] ..
|
||||
01/09/2019 02:59 PM 4,855,952 wireless.cab
|
||||
01/09/2019 02:56 PM 2,752,512 wireless.etl
|
||||
01/09/2019 02:59 PM 2,786,540 wireless.txt
|
||||
3 File(s) 10,395,004 bytes
|
||||
2 Dir(s) 46,648,332,288 bytes free
|
||||
</pre>
|
||||
|
||||
## Wifi filter file
|
||||
|
||||
Copy and paste all the lines below and save them into a text file named "wifi.tat." Load the filter file into the TextAnalysisTool by clicking **File > Load Filters**.
|
||||
|
||||
```
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||
<TextAnalysisTool.NET version="2018-01-03" showOnlyFilteredLines="False">
|
||||
<filters>
|
||||
<filter enabled="n" excluding="n" description="" foreColor="000000" backColor="d3d3d3" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-OneX]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Unknown]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-EapHost]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[]***" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-Winsock-AFD]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-WinHttp]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-WebIO]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-Winsock-NameResolution]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-TCPIP]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-DNS-Client]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-NlaSvc]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-Iphlpsvc-Trace]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-DHCPv6-Client]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-Dhcp-Client]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-NCSI]" />
|
||||
<filter enabled="y" excluding="n" description="" backColor="90ee90" type="matches_text" case_sensitive="n" regex="n" text="AuthMgr Transition" />
|
||||
<filter enabled="y" excluding="n" description="" foreColor="0000ff" backColor="add8e6" type="matches_text" case_sensitive="n" regex="n" text="FSM transition" />
|
||||
<filter enabled="y" excluding="n" description="" foreColor="000000" backColor="dda0dd" type="matches_text" case_sensitive="n" regex="n" text="SecMgr transition" />
|
||||
<filter enabled="y" excluding="n" description="" foreColor="000000" backColor="f08080" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-NWiFi]" />
|
||||
<filter enabled="y" excluding="n" description="" foreColor="000000" backColor="ffb6c1" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-WiFiNetworkManager]" />
|
||||
<filter enabled="y" excluding="n" description="" foreColor="000000" backColor="dda0dd" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-WLAN-AutoConfig]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-NetworkProfile]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-WFP]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[Microsoft-Windows-WinINet]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="[MSNT_SystemTrace]" />
|
||||
<filter enabled="y" excluding="y" description="" foreColor="000000" backColor="ffffff" type="matches_text" case_sensitive="n" regex="n" text="Security]Capability" />
|
||||
</filters>
|
||||
</TextAnalysisTool.NET>
|
||||
```
|
||||
|
||||
## TextAnalysisTool example
|
||||
|
||||
In the following example, the **View** settings are configured to **Show Only Filtered Lines**.
|
||||
|
||||
|
||||
@ -9,13 +9,30 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: jdeckerMS
|
||||
ms.author: jdecker
|
||||
ms.date: 09/12/2017
|
||||
ms.date: 12/06/2018
|
||||
---
|
||||
|
||||
# Change history for Client management
|
||||
|
||||
This topic lists new and updated topics in the [Client management](index.md) documentation for Windows 10 and Windows 10 Mobile.
|
||||
|
||||
## December 2018
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Advanced troubleshooting for TCP/IP](troubleshoot-tcpip.md) | New
|
||||
[Collect data using Network Monitor](troubleshoot-tcpip-netmon.md) | New
|
||||
[Troubleshoot TCP/IP connectivity](troubleshoot-tcpip-connectivity.md) | New
|
||||
[Troubleshoot port exhaustion issues](troubleshoot-tcpip-port-exhaust.md) | New
|
||||
[Troubleshoot Remote Procedure Call (RPC) errors](troubleshoot-tcpip-rpc-errors.md) | New
|
||||
|
||||
## November 2018
|
||||
|
||||
New or changed topic | Description
|
||||
--- | ---
|
||||
[Advanced troubleshooting for Windows-based computer freeze issues](troubleshoot-windows-freeze.md) | New
|
||||
[Advanced troubleshooting for Stop error or blue screen error issue](troubleshoot-stop-errors.md) | New
|
||||
|
||||
## RELEASE: Windows 10, version 1709
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1709 (also known as the Fall Creators Update).
|
||||
|
||||
@ -23,6 +23,9 @@ From its release, Windows 10 has supported remote connections to PCs that are jo
|
||||
|
||||
|
||||
|
||||
>[!TIP]
|
||||
>Starting in Windows 10, version 1809, you can [use biometrics to authenticate to a remote desktop session.](https://docs.microsoft.com/windows/whats-new/whats-new-windows-10-version-1809#remote-desktop-with-biometrics)
|
||||
|
||||
## Set up
|
||||
|
||||
- Both PCs (local and remote) must be running Windows 10, version 1607 (or later). Remote connection to an Azure AD-joined PC that is running earlier versions of Windows 10 is not supported.
|
||||
|
||||
@ -0,0 +1,382 @@
|
||||
---
|
||||
title: Data collection for troubleshooting 802.1X authentication
|
||||
description: Data needed for reviewing 802.1X Authentication issues
|
||||
keywords: troubleshooting, data collection, data, 802.1X authentication, authentication, data
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
ms.sitesec: library
|
||||
author: kaushika-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mikeblodge
|
||||
---
|
||||
|
||||
# Data collection for troubleshooting 802.1X authentication
|
||||
|
||||
Use the following steps to collect data that can be used to troubleshoot 802.1X authentication issues. When you have collected data, see [Advanced troubleshooting 802.1X authentication](advanced-troubleshooting-802-authentication.md).
|
||||
|
||||
## Capture wireless/wired functionality logs
|
||||
|
||||
Use the following steps to collect wireless and wired logs on Windows and Windows Server:
|
||||
|
||||
1. Create C:\MSLOG on the client machine to store captured logs.
|
||||
2. Launch an elevated command prompt on the client machine, and run the following commands to start a RAS trace log and a Wireless/Wired scenario log.
|
||||
|
||||
**Wireless Windows 8.1 and Windows 10:**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg,wireless_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_cli.etl
|
||||
```
|
||||
|
||||
<br>**Wireless Windows 7 and Windows 8:**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_cli.etl
|
||||
```
|
||||
|
||||
<br>**Wired client, regardless of version**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=lan globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wired_cli.etl
|
||||
```
|
||||
|
||||
3. Run the following command to enable CAPI2 logging and increase the size :
|
||||
```
|
||||
wevtutil.exe sl Microsoft-Windows-CAPI2/Operational /e:true
|
||||
wevtutil sl Microsoft-Windows-CAPI2/Operational /ms:104857600
|
||||
```
|
||||
|
||||
4. Create C:\MSLOG on the NPS to store captured logs.
|
||||
|
||||
5. Launch an elevated command prompt on the NPS server and run the following commands to start a RAS trace log and a Wireless/Wired scenario log:
|
||||
|
||||
**Windows Server 2012 R2, Windows Server 2016 wireless network:**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg,wireless_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_nps.etl
|
||||
```
|
||||
|
||||
<br>**Windows Server 2008 R2, Windows Server 2012 wireless network**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_nps.etl
|
||||
```
|
||||
|
||||
<br>**Wired network**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=lan globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wired_nps.etl
|
||||
```
|
||||
|
||||
6. Run the following command to enable CAPI2 logging and increase the size :
|
||||
```
|
||||
wevtutil.exe sl Microsoft-Windows-CAPI2/Operational /e:true
|
||||
wevtutil sl Microsoft-Windows-CAPI2/Operational /ms:104857600
|
||||
```
|
||||
7. Run the following command from the command prompt on the client machine and start PSR to capture screen images:
|
||||
|
||||
> [!NOTE]
|
||||
> When the mouse button is clicked, the cursor will blink in red while capturing a screen image.
|
||||
|
||||
```
|
||||
psr /start /output c:\MSLOG\%computername%_psr.zip /maxsc 100
|
||||
```
|
||||
8. Repro the issue.
|
||||
9. Run the following command on the client PC to stop the PSR capturing:
|
||||
|
||||
```
|
||||
psr /stop
|
||||
```
|
||||
|
||||
10. Run the following commands from the command prompt on the NPS server.
|
||||
|
||||
- To stop RAS trace log and wireless scenario log:
|
||||
|
||||
```
|
||||
netsh trace stop
|
||||
netsh ras set tracing * disabled
|
||||
```
|
||||
- To disable and copy CAPI2 log:
|
||||
|
||||
```
|
||||
wevtutil.exe sl Microsoft-Windows-CAPI2/Operational /e:false
|
||||
wevtutil.exe epl Microsoft-Windows-CAPI2/Operational C:\MSLOG\%COMPUTERNAME%_CAPI2.evtx
|
||||
```
|
||||
|
||||
11. Run the following commands on the client PC.
|
||||
- To stop RAS trace log and wireless scenario log:
|
||||
```
|
||||
netsh trace stop
|
||||
netsh ras set tracing * disabled
|
||||
```
|
||||
|
||||
- To disable and copy the CAPI2 log:
|
||||
```
|
||||
wevtutil.exe sl Microsoft-Windows-CAPI2/Operational /e:false
|
||||
wevtutil.exe epl Microsoft-Windows-CAPI2/Operational C:\MSLOG\%COMPUTERNAME%_CAPI2.evtx
|
||||
```
|
||||
|
||||
12. Save the following logs on the client and the NPS:
|
||||
|
||||
**Client**
|
||||
- C:\MSLOG\%computername%_psr.zip
|
||||
- C:\MSLOG\%COMPUTERNAME%_CAPI2.evtx
|
||||
- C:\MSLOG\%COMPUTERNAME%_wireless_cli.etl
|
||||
- C:\MSLOG\%COMPUTERNAME%_wireless_cli.cab
|
||||
- All log files and folders in %Systemroot%\Tracing
|
||||
|
||||
**NPS**
|
||||
- C:\MSLOG\%COMPUTERNAME%_CAPI2.evtx
|
||||
- C:\MSLOG\%COMPUTERNAME%_wireless_nps.etl (%COMPUTERNAME%_wired_nps.etl for wired scenario)
|
||||
- C:\MSLOG\%COMPUTERNAME%_wireless_nps.cab (%COMPUTERNAME%_wired_nps.cab for wired scenario)
|
||||
- All log files and folders in %Systemroot%\Tracing
|
||||
|
||||
## Save environment and configuration information
|
||||
|
||||
### On Windows client
|
||||
|
||||
1. Create C:\MSLOG to store captured logs.
|
||||
2. Launch a command prompt as an administrator.
|
||||
3. Run the following commands.
|
||||
- Environment information and Group Policy application status
|
||||
|
||||
```
|
||||
gpresult /H C:\MSLOG\%COMPUTERNAME%_gpresult.htm
|
||||
msinfo32 /report c:\MSLOG\%COMPUTERNAME%_msinfo32.txt
|
||||
ipconfig /all > c:\MSLOG\%COMPUTERNAME%_ipconfig.txt
|
||||
route print > c:\MSLOG\%COMPUTERNAME%_route_print.txt
|
||||
```
|
||||
- Event logs
|
||||
|
||||
```
|
||||
wevtutil epl Application c:\MSLOG\%COMPUTERNAME%_Application.evtx
|
||||
wevtutil epl System c:\MSLOG\%COMPUTERNAME%_System.evtx
|
||||
wevtutil epl Security c:\MSLOG\%COMPUTERNAME%_Security.evtx
|
||||
wevtutil epl Microsoft-Windows-GroupPolicy/Operational C:\MSLOG\%COMPUTERNAME%_GroupPolicy_Operational.evtx
|
||||
wevtutil epl "Microsoft-Windows-WLAN-AutoConfig/Operational" c:\MSLOG\%COMPUTERNAME%_Microsoft-Windows-WLAN-AutoConfig-Operational.evtx
|
||||
wevtutil epl "Microsoft-Windows-Wired-AutoConfig/Operational" c:\MSLOG\%COMPUTERNAME%_Microsoft-Windows-Wired-AutoConfig-Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-CredentialRoaming/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-CredentialRoaming_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertPoleEng/Operational c:\MSLOG\%COMPUTERNAME%_CertPoleEng_Operational.evtx
|
||||
```
|
||||
- For Windows 8 and later, also run these commands for event logs:
|
||||
|
||||
```
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-Lifecycle-System/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-Lifecycle-System_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-Lifecycle-User/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-Lifecycle-User_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServices-Deployment/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServices-Deployment_Operational.evtx
|
||||
```
|
||||
- Certificates Store information:
|
||||
|
||||
```
|
||||
certutil -v -silent -store MY > c:\MSLOG\%COMPUTERNAME%_cert-Personal-Registry.txt
|
||||
certutil -v -silent -store ROOT > c:\MSLOG\%COMPUTERNAME%_cert-TrustedRootCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy ROOT > c:\MSLOG\%COMPUTERNAME%_cert-TrustedRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise ROOT > c:\MSLOG\%COMPUTERNAME%_TrustedRootCA-Enterprise.txt
|
||||
certutil -v -silent -store TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-Reg.txt
|
||||
certutil -v -silent -store -grouppolicy TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-Enterprise.txt
|
||||
certutil -v -silent -store CA > c:\MSLOG\%COMPUTERNAME%_cert-IntermediateCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy CA > c:\MSLOG\%COMPUTERNAME%_cert-IntermediateCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise CA > c:\MSLOG\%COMPUTERNAME%_cert-Intermediate-Enterprise.txt
|
||||
certutil -v -silent -store AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-Enterprise.txt
|
||||
certutil -v -silent -store SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-Enterprise.txt
|
||||
certutil -v -silent -store -enterprise NTAUTH > c:\MSLOG\%COMPUTERNAME%_cert-NtAuth-Enterprise.txt
|
||||
certutil -v -silent -user -store MY > c:\MSLOG\%COMPUTERNAME%_cert-User-Personal-Registry.txt
|
||||
certutil -v -silent -user -store ROOT > c:\MSLOG\%COMPUTERNAME%_cert-User-TrustedRootCA-Registry.txt
|
||||
certutil -v -silent -user -store -enterprise ROOT > c:\MSLOG\%COMPUTERNAME%_cert-User-TrustedRootCA-Enterprise.txt
|
||||
certutil -v -silent -user -store TRUST > c:\MSLOG\%COMPUTERNAME%_cert-User-EnterpriseTrust-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy TRUST > c:\MSLOG\%COMPUTERNAME%_cert-User-EnterpriseTrust-GroupPolicy.txt
|
||||
certutil -v -silent -user -store CA > c:\MSLOG\%COMPUTERNAME%_cert-User-IntermediateCA-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy CA > c:\MSLOG\%COMPUTERNAME%_cert-User-IntermediateCA-GroupPolicy.txt
|
||||
certutil -v -silent -user -store Disallowed > c:\MSLOG\%COMPUTERNAME%_cert-User-UntrustedCertificates-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy Disallowed > c:\MSLOG\%COMPUTERNAME%_cert-User-UntrustedCertificates-GroupPolicy.txt
|
||||
certutil -v -silent -user -store AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-3rdPartyRootCA-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-3rdPartyRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -user -store SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-SmartCardRoot-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-SmartCardRoot-GroupPolicy.txt
|
||||
certutil -v -silent -user -store UserDS > c:\MSLOG\%COMPUTERNAME%_cert-User-UserDS.txt
|
||||
```
|
||||
- Wireless LAN client information:
|
||||
|
||||
```
|
||||
netsh wlan show all > c:\MSLOG\%COMPUTERNAME%_wlan_show_all.txt
|
||||
netsh wlan export profile folder=c:\MSLOG\
|
||||
```
|
||||
- Wired LAN Client information
|
||||
|
||||
```
|
||||
netsh lan show interfaces > c:\MSLOG\%computername%_lan_interfaces.txt
|
||||
netsh lan show profiles > c:\MSLOG\%computername%_lan_profiles.txt
|
||||
netsh lan show settings > c:\MSLOG\%computername%_lan_settings.txt
|
||||
netsh lan export profile folder=c:\MSLOG\
|
||||
```
|
||||
4. Save the logs stored in C:\MSLOG.
|
||||
|
||||
### On NPS
|
||||
|
||||
1. Create C:\MSLOG to store captured logs.
|
||||
2. Launch a command prompt as an administrator.
|
||||
3. Run the following commands.
|
||||
- Environmental information and Group Policies application status:
|
||||
|
||||
```
|
||||
gpresult /H C:\MSLOG\%COMPUTERNAME%_gpresult.txt
|
||||
msinfo32 /report c:\MSLOG\%COMPUTERNAME%_msinfo32.txt
|
||||
ipconfig /all > c:\MSLOG\%COMPUTERNAME%_ipconfig.txt
|
||||
route print > c:\MSLOG\%COMPUTERNAME%_route_print.txt
|
||||
```
|
||||
- Event logs:
|
||||
|
||||
```
|
||||
wevtutil epl Application c:\MSLOG\%COMPUTERNAME%_Application.evtx
|
||||
wevtutil epl System c:\MSLOG\%COMPUTERNAME%_System.evtx
|
||||
wevtutil epl Security c:\MSLOG\%COMPUTERNAME%_Security.evtx
|
||||
wevtutil epl Microsoft-Windows-GroupPolicy/Operational c:\MSLOG\%COMPUTERNAME%_GroupPolicy_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-CredentialRoaming/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-CredentialRoaming_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertPoleEng/Operational c:\MSLOG\%COMPUTERNAME%_CertPoleEng_Operational.evtx
|
||||
```
|
||||
- Run the following 3 commands on Windows Server 2012 and later:
|
||||
|
||||
```
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-Lifecycle-System/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-Lifecycle-System_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-Lifecycle-User/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-Lifecycle-User_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServices-Deployment/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServices-Deployment_Operational.evtx
|
||||
```
|
||||
- Certificates store information
|
||||
|
||||
```
|
||||
certutil -v -silent -store MY > c:\MSLOG\%COMPUTERNAME%_cert-Personal-Registry.txt
|
||||
certutil -v -silent -store ROOT > c:\MSLOG\%COMPUTERNAME%_cert-TrustedRootCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy ROOT > c:\MSLOG\%COMPUTERNAME%_cert-TrustedRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise ROOT > c:\MSLOG\%COMPUTERNAME%_TrustedRootCA-Enterprise.txt
|
||||
certutil -v -silent -store TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-Reg.txt
|
||||
certutil -v -silent -store -grouppolicy TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-Enterprise.txt
|
||||
certutil -v -silent -store CA > c:\MSLOG\%COMPUTERNAME%_cert-IntermediateCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy CA > c:\MSLOG\%COMPUTERNAME%_cert-IntermediateCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise CA > c:\MSLOG\%COMPUTERNAME%_cert-Intermediate-Enterprise.txt
|
||||
certutil -v -silent -store AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-Enterprise.txt
|
||||
certutil -v -silent -store SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-Enterprise.txt
|
||||
certutil -v -silent -store -enterprise NTAUTH > c:\MSLOG\%COMPUTERNAME%_cert-NtAuth-Enterprise.txt
|
||||
certutil -v -silent -user -store MY > c:\MSLOG\%COMPUTERNAME%_cert-User-Personal-Registry.txt
|
||||
certutil -v -silent -user -store ROOT > c:\MSLOG\%COMPUTERNAME%_cert-User-TrustedRootCA-Registry.txt
|
||||
certutil -v -silent -user -store -enterprise ROOT > c:\MSLOG\%COMPUTERNAME%_cert-User-TrustedRootCA-Enterprise.txt
|
||||
certutil -v -silent -user -store TRUST > c:\MSLOG\%COMPUTERNAME%_cert-User-EnterpriseTrust-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy TRUST > c:\MSLOG\%COMPUTERNAME%_cert-User-EnterpriseTrust-GroupPolicy.txt
|
||||
certutil -v -silent -user -store CA > c:\MSLOG\%COMPUTERNAME%_cert-User-IntermediateCA-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy CA > c:\MSLOG\%COMPUTERNAME%_cert-User-IntermediateCA-GroupPolicy.txt
|
||||
certutil -v -silent -user -store Disallowed > c:\MSLOG\%COMPUTERNAME%_cert-User-UntrustedCertificates-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy Disallowed > c:\MSLOG\%COMPUTERNAME%_cert-User-UntrustedCertificates-GroupPolicy.txt
|
||||
certutil -v -silent -user -store AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-3rdPartyRootCA-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-3rdPartyRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -user -store SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-SmartCardRoot-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-SmartCardRoot-GroupPolicy.txt
|
||||
certutil -v -silent -user -store UserDS > c:\MSLOG\%COMPUTERNAME%_cert-User-UserDS.txt
|
||||
```
|
||||
- NPS configuration information:
|
||||
|
||||
```
|
||||
netsh nps show config > C:\MSLOG\%COMPUTERNAME%_nps_show_config.txt
|
||||
netsh nps export filename=C:\MSLOG\%COMPUTERNAME%_nps_export.xml exportPSK=YES
|
||||
```
|
||||
3. Take the following steps to save an NPS accounting log.
|
||||
1. Open **Administrative tools > Network Policy Server**.
|
||||
2. On the Network Policy Server administration tool, select **Accounting** in the left pane.
|
||||
3. Click **Change Log File Properties**.
|
||||
4. On the **Log File** tab, note the log file naming convention shown as **Name** and the log file location shown in **Directory** box.
|
||||
5. Copy the log file to C:\MSLOG.
|
||||
|
||||
4. Save the logs stored in C:\MSLOG.
|
||||
|
||||
## Certification Authority (CA) (OPTIONAL)
|
||||
|
||||
1. On a CA, launch a command prompt as an administrator. Create C:\MSLOG to store captured logs.
|
||||
2. Run the following commands.
|
||||
- Environmental information and Group Policies application status
|
||||
|
||||
```
|
||||
gpresult /H C:\MSLOG\%COMPUTERNAME%_gpresult.txt
|
||||
msinfo32 /report c:\MSLOG\%COMPUTERNAME%_msinfo32.txt
|
||||
ipconfig /all > c:\MSLOG\%COMPUTERNAME%_ipconfig.txt
|
||||
route print > c:\MSLOG\%COMPUTERNAME%_route_print.txt
|
||||
```
|
||||
- Event logs
|
||||
|
||||
```
|
||||
wevtutil epl Application c:\MSLOG\%COMPUTERNAME%_Application.evtx
|
||||
wevtutil epl System c:\MSLOG\%COMPUTERNAME%_System.evtx
|
||||
wevtutil epl Security c:\MSLOG\%COMPUTERNAME%_Security.evtx
|
||||
wevtutil epl Microsoft-Windows-GroupPolicy/Operational c:\MSLOG\%COMPUTERNAME%_GroupPolicy_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-CredentialRoaming/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-CredentialRoaming_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertPoleEng/Operational c:\MSLOG\%COMPUTERNAME%_CertPoleEng_Operational.evtx
|
||||
```
|
||||
- Run the following 3 lines on Windows 2012 and up
|
||||
|
||||
```
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-Lifecycle-System/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-Lifecycle-System_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServicesClient-Lifecycle-User/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServicesClient-Lifecycle-User_Operational.evtx
|
||||
wevtutil epl Microsoft-Windows-CertificateServices-Deployment/Operational c:\MSLOG\%COMPUTERNAME%_CertificateServices-Deployment_Operational.evtx
|
||||
```
|
||||
- Certificates store information
|
||||
|
||||
```
|
||||
certutil -v -silent -store MY > c:\MSLOG\%COMPUTERNAME%_cert-Personal-Registry.txt
|
||||
certutil -v -silent -store ROOT > c:\MSLOG\%COMPUTERNAME%_cert-TrustedRootCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy ROOT > c:\MSLOG\%COMPUTERNAME%_cert-TrustedRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise ROOT > c:\MSLOG\%COMPUTERNAME%_TrustedRootCA-Enterprise.txt
|
||||
certutil -v -silent -store TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-Reg.txt
|
||||
certutil -v -silent -store -grouppolicy TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise TRUST > c:\MSLOG\%COMPUTERNAME%_cert-EnterpriseTrust-Enterprise.txt
|
||||
certutil -v -silent -store CA > c:\MSLOG\%COMPUTERNAME%_cert-IntermediateCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy CA > c:\MSLOG\%COMPUTERNAME%_cert-IntermediateCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise CA > c:\MSLOG\%COMPUTERNAME%_cert-Intermediate-Enterprise.txt
|
||||
certutil -v -silent -store AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-3rdPartyRootCA-Enterprise.txt
|
||||
certutil -v -silent -store SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-Registry.txt
|
||||
certutil -v -silent -store -grouppolicy SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-GroupPolicy.txt
|
||||
certutil -v -silent -store -enterprise SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-SmartCardRoot-Enterprise.txt
|
||||
certutil -v -silent -store -enterprise NTAUTH > c:\MSLOG\%COMPUTERNAME%_cert-NtAuth-Enterprise.txt
|
||||
certutil -v -silent -user -store MY > c:\MSLOG\%COMPUTERNAME%_cert-User-Personal-Registry.txt
|
||||
certutil -v -silent -user -store ROOT > c:\MSLOG\%COMPUTERNAME%_cert-User-TrustedRootCA-Registry.txt
|
||||
certutil -v -silent -user -store -enterprise ROOT > c:\MSLOG\%COMPUTERNAME%_cert-User-TrustedRootCA-Enterprise.txt
|
||||
certutil -v -silent -user -store TRUST > c:\MSLOG\%COMPUTERNAME%_cert-User-EnterpriseTrust-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy TRUST > c:\MSLOG\%COMPUTERNAME%_cert-User-EnterpriseTrust-GroupPolicy.txt
|
||||
certutil -v -silent -user -store CA > c:\MSLOG\%COMPUTERNAME%_cert-User-IntermediateCA-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy CA > c:\MSLOG\%COMPUTERNAME%_cert-User-IntermediateCA-GroupPolicy.txt
|
||||
certutil -v -silent -user -store Disallowed > c:\MSLOG\%COMPUTERNAME%_cert-User-UntrustedCertificates-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy Disallowed > c:\MSLOG\%COMPUTERNAME%_cert-User-UntrustedCertificates-GroupPolicy.txt
|
||||
certutil -v -silent -user -store AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-3rdPartyRootCA-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy AuthRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-3rdPartyRootCA-GroupPolicy.txt
|
||||
certutil -v -silent -user -store SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-SmartCardRoot-Registry.txt
|
||||
certutil -v -silent -user -store -grouppolicy SmartCardRoot > c:\MSLOG\%COMPUTERNAME%_cert-User-SmartCardRoot-GroupPolicy.txt
|
||||
certutil -v -silent -user -store UserDS > c:\MSLOG\%COMPUTERNAME%_cert-User-UserDS.txt
|
||||
```
|
||||
- CA configuration information
|
||||
|
||||
```
|
||||
reg save HKLM\System\CurrentControlSet\Services\CertSvc c:\MSLOG\%COMPUTERNAME%_CertSvc.hiv
|
||||
reg export HKLM\System\CurrentControlSet\Services\CertSvc c:\MSLOG\%COMPUTERNAME%_CertSvc.txt
|
||||
reg save HKLM\SOFTWARE\Microsoft\Cryptography c:\MSLOG\%COMPUTERNAME%_Cryptography.hiv
|
||||
reg export HKLM\SOFTWARE\Microsoft\Cryptography c:\MSLOG\%COMPUTERNAME%_Cryptography.txt
|
||||
```
|
||||
3. Copy the following files, if exist, to C:\MSLOG: %windir%\CAPolicy.inf
|
||||
4. Log on to a domain controller and create C:\MSLOG to store captured logs.
|
||||
5. Launch Windows PowerShell as an administrator.
|
||||
6. Run the following PowerShell cmdlets. Replace the domain name in ";.. ,DC=test,DC=local"; with appropriate domain name. The example shows commands for ";test.local"; domain.
|
||||
|
||||
```powershell
|
||||
Import-Module ActiveDirectory
|
||||
Get-ADObject -SearchBase ";CN=Public Key Services,CN=Services,CN=Configuration,DC=test,DC=local"; -Filter * -Properties * | fl * > C:\MSLOG\Get-ADObject_$Env:COMPUTERNAME.txt
|
||||
```
|
||||
7. Save the following logs.
|
||||
- All files in C:\MSLOG on the CA
|
||||
- All files in C:\MSLOG on the domain controller
|
||||
|
||||
@ -35,8 +35,6 @@
|
||||
"breadcrumb_path": "/windows/windows-10/breadcrumb/toc.json",
|
||||
"ms.technology": "windows",
|
||||
"ms.topic": "article",
|
||||
"ms.author": "dongill",
|
||||
"ms.date": "04/05/2017",
|
||||
"feedback_system": "GitHub",
|
||||
"feedback_github_repo": "MicrosoftDocs/windows-itpro-docs",
|
||||
"feedback_product_url": "https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app",
|
||||
|
||||
BIN
windows/client-management/images/NPS_sidepacket_capture_data.png
Normal file
BIN
windows/client-management/images/NPS_sidepacket_capture_data.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 237 KiB |
BIN
windows/client-management/images/auditfailure.png
Normal file
BIN
windows/client-management/images/auditfailure.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 220 KiB |
BIN
windows/client-management/images/auditsuccess.png
Normal file
BIN
windows/client-management/images/auditsuccess.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
BIN
windows/client-management/images/authenticator_flow_chart.png
Normal file
BIN
windows/client-management/images/authenticator_flow_chart.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 381 KiB |
BIN
windows/client-management/images/boot-sequence-thumb.png
Normal file
BIN
windows/client-management/images/boot-sequence-thumb.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
windows/client-management/images/boot-sequence.png
Normal file
BIN
windows/client-management/images/boot-sequence.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 195 KiB |
BIN
windows/client-management/images/bugcheck-analysis.png
Normal file
BIN
windows/client-management/images/bugcheck-analysis.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
BIN
windows/client-management/images/capi.png
Normal file
BIN
windows/client-management/images/capi.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 514 KiB |
BIN
windows/client-management/images/check-disk.png
Normal file
BIN
windows/client-management/images/check-disk.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
BIN
windows/client-management/images/clientsidepacket_cap_data.png
Normal file
BIN
windows/client-management/images/clientsidepacket_cap_data.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 284 KiB |
BIN
windows/client-management/images/comparisontable.png
Normal file
BIN
windows/client-management/images/comparisontable.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 120 KiB |
BIN
windows/client-management/images/controlset.png
Normal file
BIN
windows/client-management/images/controlset.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 91 KiB |
BIN
windows/client-management/images/eappropertymenu.png
Normal file
BIN
windows/client-management/images/eappropertymenu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 164 KiB |
BIN
windows/client-management/images/etl.png
Normal file
BIN
windows/client-management/images/etl.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 931 KiB |
BIN
windows/client-management/images/eventviewer.png
Normal file
BIN
windows/client-management/images/eventviewer.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 424 KiB |
BIN
windows/client-management/images/loadhive.png
Normal file
BIN
windows/client-management/images/loadhive.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 73 KiB |
BIN
windows/client-management/images/miniport.png
Normal file
BIN
windows/client-management/images/miniport.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.5 KiB |
BIN
windows/client-management/images/msm.png
Normal file
BIN
windows/client-management/images/msm.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.1 KiB |
BIN
windows/client-management/images/msmdetails.png
Normal file
BIN
windows/client-management/images/msmdetails.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
windows/client-management/images/nm-adapters.png
Normal file
BIN
windows/client-management/images/nm-adapters.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 98 KiB |
BIN
windows/client-management/images/nm-start.png
Normal file
BIN
windows/client-management/images/nm-start.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
BIN
windows/client-management/images/pendingupdate.png
Normal file
BIN
windows/client-management/images/pendingupdate.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
BIN
windows/client-management/images/revertpending.png
Normal file
BIN
windows/client-management/images/revertpending.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
BIN
windows/client-management/images/rpc-error.png
Normal file
BIN
windows/client-management/images/rpc-error.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
BIN
windows/client-management/images/rpc-flow.png
Normal file
BIN
windows/client-management/images/rpc-flow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
BIN
windows/client-management/images/screenshot1.png
Normal file
BIN
windows/client-management/images/screenshot1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
windows/client-management/images/sfc-scannow.png
Normal file
BIN
windows/client-management/images/sfc-scannow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.7 KiB |
BIN
windows/client-management/images/tat.png
Normal file
BIN
windows/client-management/images/tat.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 177 KiB |
BIN
windows/client-management/images/tcp-ts-1.png
Normal file
BIN
windows/client-management/images/tcp-ts-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
BIN
windows/client-management/images/tcp-ts-10.png
Normal file
BIN
windows/client-management/images/tcp-ts-10.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 455 KiB |
BIN
windows/client-management/images/tcp-ts-11.png
Normal file
BIN
windows/client-management/images/tcp-ts-11.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 80 KiB |
BIN
windows/client-management/images/tcp-ts-12.png
Normal file
BIN
windows/client-management/images/tcp-ts-12.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
BIN
windows/client-management/images/tcp-ts-13.png
Normal file
BIN
windows/client-management/images/tcp-ts-13.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
BIN
windows/client-management/images/tcp-ts-14.png
Normal file
BIN
windows/client-management/images/tcp-ts-14.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 284 KiB |
BIN
windows/client-management/images/tcp-ts-15.png
Normal file
BIN
windows/client-management/images/tcp-ts-15.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
BIN
windows/client-management/images/tcp-ts-16.png
Normal file
BIN
windows/client-management/images/tcp-ts-16.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
BIN
windows/client-management/images/tcp-ts-17.png
Normal file
BIN
windows/client-management/images/tcp-ts-17.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
BIN
windows/client-management/images/tcp-ts-18.png
Normal file
BIN
windows/client-management/images/tcp-ts-18.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 245 KiB |
BIN
windows/client-management/images/tcp-ts-19.png
Normal file
BIN
windows/client-management/images/tcp-ts-19.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 164 KiB |
BIN
windows/client-management/images/tcp-ts-2.png
Normal file
BIN
windows/client-management/images/tcp-ts-2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
BIN
windows/client-management/images/tcp-ts-20.png
Normal file
BIN
windows/client-management/images/tcp-ts-20.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
BIN
windows/client-management/images/tcp-ts-21.png
Normal file
BIN
windows/client-management/images/tcp-ts-21.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
BIN
windows/client-management/images/tcp-ts-22.png
Normal file
BIN
windows/client-management/images/tcp-ts-22.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 136 KiB |
BIN
windows/client-management/images/tcp-ts-23.png
Normal file
BIN
windows/client-management/images/tcp-ts-23.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 503 KiB |
BIN
windows/client-management/images/tcp-ts-24.png
Normal file
BIN
windows/client-management/images/tcp-ts-24.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 395 KiB |
BIN
windows/client-management/images/tcp-ts-25.png
Normal file
BIN
windows/client-management/images/tcp-ts-25.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 84 KiB |
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user