mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-16 07:17:24 +00:00
enhanced Acrolinx score
This commit is contained in:
parent
5b75b2ba2c
commit
abb34bdde2
@ -74,7 +74,7 @@ If the following considerations apply to your organization, you should avoid thi
|
|||||||
|
|
||||||
- **Will you be able to track which applications are installed on which computer?**
|
- **Will you be able to track which applications are installed on which computer?**
|
||||||
|
|
||||||
You might determine that your initial set of compatibility fixes is not comprehensive, and that you must deploy an updated version of the compatibility-fix database to resolve the other issues. If you deployed the initial set by using the application-installation package, you will be required to locate each client computer that is running the application and replace the compatibility fix.
|
You might determine that your initial set of compatibility fixes isn't comprehensive, and that you must deploy an updated version of the compatibility-fix database to resolve the other issues. If you deployed the initial set by using the application-installation package, you'll be required to locate each client computer that is running the application and replace the compatibility fix.
|
||||||
|
|
||||||
### Deploying Fixes Through a Centralized Compatibility-Fix Database
|
### Deploying Fixes Through a Centralized Compatibility-Fix Database
|
||||||
|
|
||||||
@ -88,7 +88,7 @@ This approach tends to work best for organizations that have a well-developed de
|
|||||||
|
|
||||||
- Do you have centralized resources that can manage and update the centralized compatibility-fix database?
|
- Do you have centralized resources that can manage and update the centralized compatibility-fix database?
|
||||||
|
|
||||||
Ensure that you have identified the appropriate owners for the deployment process, for the applications, and for the database updates, in addition to determining the process by which compatibility issues can be deployed to specific computers.
|
Ensure that you've identified the appropriate owners for the deployment process, for the applications, and for the database updates, in addition to determining the process by which compatibility issues can be deployed to specific computers.
|
||||||
|
|
||||||
### Merging Centralized Compatibility-Fix Databases
|
### Merging Centralized Compatibility-Fix Databases
|
||||||
|
|
||||||
@ -98,7 +98,7 @@ If you decide to use the centralized compatibility-fix database deployment strat
|
|||||||
|
|
||||||
1. Verify that your application-compatibility testers are performing their tests on computers with the latest version of your compatibility-fix database. For example, Custom DB1.
|
1. Verify that your application-compatibility testers are performing their tests on computers with the latest version of your compatibility-fix database. For example, Custom DB1.
|
||||||
|
|
||||||
2. If the tester determines that an application requires an extra compatibility fix that is not a part of the original compatibility-fix database, the tester must create a new custom compatibility database with all of the required information for that single fix, for example, Custom DB2.
|
2. If the tester determines that an application requires an extra compatibility fix that isn't a part of the original compatibility-fix database, the tester must create a new custom compatibility database with all of the required information for that single fix, for example, Custom DB2.
|
||||||
|
|
||||||
3. The tester applies the new Custom DB2 information to the application and then tests for both the functionality and integration, to ensure that the compatibility issues are addressed.
|
3. The tester applies the new Custom DB2 information to the application and then tests for both the functionality and integration, to ensure that the compatibility issues are addressed.
|
||||||
|
|
||||||
|
@ -40,7 +40,7 @@ You can use SUA in either of the following ways:
|
|||||||
|
|
||||||
|Topic|Description|
|
|Topic|Description|
|
||||||
|--- |--- |
|
|--- |--- |
|
||||||
|[Using the SUA wizard](using-the-sua-wizard.md)|The Standard User Analyzer (SUA) wizard works much like the SUA tool to evaluate User Account Control (UAC) issues. However, the SUA wizard does not offer detailed analysis, and it cannot disable virtualization or elevate your permissions.|
|
|[Using the SUA wizard](using-the-sua-wizard.md)|The Standard User Analyzer (SUA) wizard works much like the SUA tool to evaluate User Account Control (UAC) issues. However, the SUA wizard doesn't offer detailed analysis, and it can't disable virtualization or elevate your permissions.|
|
||||||
|[Using the SUA Tool](using-the-sua-tool.md)|By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.|
|
|[Using the SUA Tool](using-the-sua-tool.md)|By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.|
|
||||||
|
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Using the SUA wizard (Windows 10)
|
title: Using the SUA wizard (Windows 10)
|
||||||
description: The Standard User Analyzer (SUA) wizard, although it does not offer deep analysis, works much like the SUA tool to test for User Account Control (UAC) issues.
|
description: The Standard User Analyzer (SUA) wizard, although it doesn't offer deep analysis, works much like the SUA tool to test for User Account Control (UAC) issues.
|
||||||
ms.assetid: 29d07074-3de7-4ace-9a54-678af7255d6c
|
ms.assetid: 29d07074-3de7-4ace-9a54-678af7255d6c
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: laurawi
|
||||||
@ -27,14 +27,14 @@ ms.topic: article
|
|||||||
- Windows Server 2012
|
- Windows Server 2012
|
||||||
- Windows Server 2008 R2
|
- Windows Server 2008 R2
|
||||||
|
|
||||||
The Standard User Analyzer (SUA) wizard works much like the SUA tool to evaluate User Account Control (UAC) issues. However, the SUA wizard does not offer detailed analysis, and it cannot disable virtualization or elevate your permissions.
|
The Standard User Analyzer (SUA) wizard works much like the SUA tool to evaluate User Account Control (UAC) issues. However, the SUA wizard doesn't offer detailed analysis, and it can't disable virtualization or elevate your permissions.
|
||||||
|
|
||||||
For information about the SUA tool, see [Using the SUA Tool](using-the-sua-tool.md).
|
For information about the SUA tool, see [Using the SUA Tool](using-the-sua-tool.md).
|
||||||
|
|
||||||
## Testing an Application by Using the SUA wizard
|
## Testing an Application by Using the SUA wizard
|
||||||
|
|
||||||
|
|
||||||
Install Application Verifier before you can use the SUA wizard. If Application Verifier is not installed on the computer that is running the SUA wizard, the SUA wizard notifies you. In addition, install the Microsoft® .NET Framework 3.5 or later before you can use the SUA wizard.
|
Install Application Verifier before you can use the SUA wizard. If Application Verifier isn't installed on the computer that is running the SUA wizard, the SUA wizard notifies you. In addition, install the Microsoft® .NET Framework 3.5 or later before you can use the SUA wizard.
|
||||||
|
|
||||||
The following flowchart shows the process of using the SUA wizard.
|
The following flowchart shows the process of using the SUA wizard.
|
||||||
|
|
||||||
@ -50,7 +50,7 @@ The following flowchart shows the process of using the SUA wizard.
|
|||||||
|
|
||||||
4. Click **Launch**.
|
4. Click **Launch**.
|
||||||
|
|
||||||
If you are prompted, elevate your permissions. The SUA wizard may require elevation of permissions to correctly diagnose the application.
|
If you're prompted, elevate your permissions. The SUA wizard may require elevation of permissions to correctly diagnose the application.
|
||||||
|
|
||||||
If a **Permission denied** dialog box appears, click **OK**. The application starts, despite the warning.
|
If a **Permission denied** dialog box appears, click **OK**. The application starts, despite the warning.
|
||||||
|
|
||||||
@ -76,7 +76,7 @@ The following flowchart shows the process of using the SUA wizard.
|
|||||||
|
|
||||||
The SUA wizard closes the issue as resolved on the local computer.
|
The SUA wizard closes the issue as resolved on the local computer.
|
||||||
|
|
||||||
If the remedies do not fix the issue with the application, click **No** again, and the wizard may offer another remedies. If the other remedies do not fix the issue, the wizard informs you that there are no more remedies available. For information about how to run the SUA tool for more investigation, see [Using the SUA Tool](using-the-sua-tool.md).
|
If the remedies don't fix the issue with the application, click **No** again, and the wizard may offer another remedies. If the other remedies don't fix the issue, the wizard informs you that there are no more remedies available. For information about how to run the SUA tool for more investigation, see [Using the SUA Tool](using-the-sua-tool.md).
|
||||||
|
|
||||||
## Related articles
|
## Related articles
|
||||||
[SUA User's Guide](sua-users-guide.md)
|
[SUA User's Guide](sua-users-guide.md)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user