mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
remove articles
This commit is contained in:
Aaron Czechowski
parent
7e683fb0ca
commit
3f9eb83d02
@ -11487,7 +11487,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/plan/windows-10-compatibility.md",
|
||||
"redirect_url": "/windows/deployment/planning/windows-10-compatibility",
|
||||
"redirect_url": "/windows/compatibility/",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
|
||||
@ -1179,6 +1179,16 @@
|
||||
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-and-feature-update-reports-overview",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/planning/windows-10-compatibility.md",
|
||||
"redirect_url": "/windows/compatibility/",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/update/plan-determine-app-readiness.md",
|
||||
"redirect_url": "/windows/compatibility/windows-11/testing-guidelines",
|
||||
"redirect_document_id": true
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -36,8 +36,6 @@
|
||||
href: update/plan-define-readiness.md
|
||||
- name: Evaluate infrastructure and tools
|
||||
href: update/eval-infra-tools.md
|
||||
- name: Determine application readiness
|
||||
href: update/plan-determine-app-readiness.md
|
||||
- name: Define your servicing strategy
|
||||
href: update/plan-define-strategy.md
|
||||
- name: Delivery Optimization for Windows client updates
|
||||
@ -53,6 +51,8 @@
|
||||
href: planning/windows-10-infrastructure-requirements.md
|
||||
- name: Plan for volume activation
|
||||
href: volume-activation/plan-for-volume-activation-client.md
|
||||
- name: Windows compatibility cookbook
|
||||
href: /windows/compatibility/
|
||||
- name: Features removed or planned for replacement
|
||||
items:
|
||||
- name: Windows client features lifecycle
|
||||
|
||||
@ -15,7 +15,7 @@ metadata:
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 04/01/2024
|
||||
ms.date: 07/12/2024
|
||||
localization_priority: medium
|
||||
|
||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
||||
@ -34,10 +34,10 @@ landingContent:
|
||||
url: update/plan-define-readiness.md
|
||||
- text: Define your servicing strategy
|
||||
url: update/plan-define-strategy.md
|
||||
- text: Determine application readiness
|
||||
url: update/plan-determine-app-readiness.md
|
||||
- text: Plan for volume activation
|
||||
url: volume-activation/plan-for-volume-activation-client.md
|
||||
- text: Windows compatibility cookbook
|
||||
url: /windows/compatibility/
|
||||
|
||||
- title: Prepare
|
||||
linkLists:
|
||||
|
||||
@ -1,45 +0,0 @@
|
||||
---
|
||||
title: Windows 10 compatibility (Windows 10)
|
||||
description: Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10.
|
||||
manager: aaroncz
|
||||
ms.author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/28/2022
|
||||
---
|
||||
|
||||
# Windows 10 compatibility
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10.
|
||||
|
||||
For full system requirements, see [Windows 10 specifications](https://go.microsoft.com/fwlink/p/?LinkId=625077). Some driver updates may be required for Windows 10.
|
||||
|
||||
Existing desktop (Win32) application compatibility is also expected to be strong, with most existing applications working without any changes. Those applications that interface with Windows at a low level, those applications that use undocumented APIs, or those that do not follow recommended coding practices could experience issues.
|
||||
|
||||
Existing Windows Store (WinRT) apps created for Windows 8 and Windows 8.1 should also continue to work, because compatibility can be validated against all the apps that have been submitted to the Windows Store.
|
||||
|
||||
For web apps and sites, modern HTML5-based sites should also have a high degree of compatibility and excellent performance through the new Microsoft Edge browser, while older web apps and sites can continue to use Internet Explorer 11 and the Enterprise Mode features that were first introduced in Windows 7 and Windows 8.1 and are still present in Windows 10. For more information about Internet Explorer and Enterprise Mode, see the [Internet Explorer 11 Deployment Guide for IT Pros.](/internet-explorer/ie11-deploy-guide/)
|
||||
|
||||
## Recommended application testing process
|
||||
|
||||
Historically, organizations have performed extensive, and often exhaustive, testing of the applications they use before deployment of a new Windows version, service pack, or any other significant update. With Windows 10, organizations are encouraged to use more optimized testing processes, which reflect the higher levels of compatibility that are expected. At a high level:
|
||||
|
||||
- Identify mission-critical applications and websites, those applications and websites that are essential to the organization's operations. Focus testing efforts on this subset of applications, early in the Windows development cycle (for example, with Windows Insider Program builds) to identify potential issues. Report any issues you encounter with the Windows Feedback tool, so that these issues can be addressed prior to the next Windows release.
|
||||
|
||||
- For less critical applications, apply an "internal flighting" or pilot-based approach, by deploying new Windows upgrades to groups of machines, growing gradually in size and potential impact, to verify compatibility with hardware and software. Reactively address issues before you expand the pilot to more machines.
|
||||
|
||||
## Related articles
|
||||
|
||||
|
||||
[Windows 10 servicing options](../update/waas-servicing-strategy-windows-10-updates.md)
|
||||
|
||||
[Windows 10 deployment considerations](windows-10-deployment-considerations.md)
|
||||
|
||||
[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
@ -69,7 +69,7 @@ In either of these scenarios, you can make various configuration changes to the
|
||||
For computers using the [General Availability Channel](../update/waas-overview.md#general-availability-channel), you can deploy these upgrades by using various methods:
|
||||
|
||||
- Windows Update or Windows Update for Business, for devices where you want to receive updates directly from the Internet.
|
||||
- Windows Server Update Services (WSUS), for devices configured to pull updates from internal servers after they're approved (deploying like an update).
|
||||
- Windows Server Update Services (WSUS), for devices configured to pull updates from internal servers after they're approved (deploying like an update).
|
||||
- Configuration Manager task sequences.
|
||||
- Configuration Manager software update capabilities (deploying like an update).
|
||||
|
||||
@ -79,5 +79,4 @@ The upgrade process is also optimized to reduce the overall time and network ban
|
||||
|
||||
## Related articles
|
||||
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)<br>
|
||||
[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md)
|
||||
|
||||
@ -97,4 +97,3 @@ Windows 10 Enterprise and Windows 10 Enterprise LTSC installations use different
|
||||
|
||||
[Windows 10 servicing options](../update/waas-servicing-strategy-windows-10-updates.md)<br>
|
||||
[Windows 10 deployment considerations](windows-10-deployment-considerations.md)<br>
|
||||
[Windows 10 compatibility](windows-10-compatibility.md)<br>
|
||||
@ -1,63 +0,0 @@
|
||||
---
|
||||
title: Determine application readiness
|
||||
description: How to test your apps to identify which need attention prior to deploying an update in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# Determine application readiness
|
||||
|
||||
Before you deploy a Windows client update, you should know which apps will continue to work without problems, which need their own updates, and which just won't work and must be replaced. If you haven't already, it's worth [classifying your apps](plan-define-readiness.md) with respect to their criticality in your organization.
|
||||
|
||||
## Validation methods
|
||||
|
||||
You can choose from various methods to validate apps. Exactly which ones to use depends on the specifics of your environment.
|
||||
|
||||
|
||||
|Validation method |Description |
|
||||
|---------|---------|
|
||||
|Full regression | A full quality assurance probing. Staff that know the application well and can validate its core functionality should do this validation. |
|
||||
|Smoke testing | The application goes through formal validation. That is, a user validates the application following a detailed plan, ideally with limited, or no knowledge of the application they're validating. |
|
||||
|Automated testing | Software performs tests automatically. The software lets you know whether the tests have passed or failed, and provides detailed reporting for you automatically. |
|
||||
|Test in pilot | You preselect users to be in the pilot deployment group and carry out the same tasks they do on a day-to-day basis to validate the application. Normally you use this method in addition to one of the other validation types. |
|
||||
|Reactive response | Applications are validated in late pilot, and no specific users are selected. These applications normally aren't installed on many devices and aren't handled by enterprise application distribution. |
|
||||
|
||||
Combining the various validation methods with the app classifications you've previously established might look like this:
|
||||
|
||||
|
||||
|Validation method |Critical apps |Important apps |Not important apps |
|
||||
|---------|---------|---------|---------|
|
||||
|Full regression | x | | |
|
||||
|Smoke testing | | x | |
|
||||
|Automated testing | x | x | x |
|
||||
|Test in pilot | x | x | x |
|
||||
|
||||
|
||||
### Identify users
|
||||
|
||||
Since your organization no doubt has a wide variety of users, each with different background and regular tasks, you have to choose which users are best suited for validation testing. Some factors to consider include:
|
||||
|
||||
- **Location**: If users are in different physical locations, can you support them and get validation feedback from the region they're in?
|
||||
- **Application knowledge**: Do the users have appropriate knowledge of how the app is supposed to work?
|
||||
- **Technical ability**: Do the users have enough technical competence to provide useful feedback from various test scenarios?
|
||||
|
||||
You could seek volunteers who enjoy working with new features and include them in the pilot deployment. You might want to avoid using core users like department heads or project managers. Current application owners, operations personnel, and developers can help you identify the most appropriate pilot users.
|
||||
|
||||
### Identify and set up devices for validation
|
||||
|
||||
In addition to users, it's important to carefully choose devices to participate in app validation as well. For example, ideally, your selection includes devices representing all of the hardware models in your environment.
|
||||
|
||||
There's more than one way to choose devices for app validation:
|
||||
|
||||
- **Existing pilot devices**: You might already have a list of devices that you regularly use for testing updates as part of release cycles.
|
||||
- **Manual selection**: Some internal groups like operations have expertise to help choose devices manually based on specifications, usage, or records of past support problems.
|
||||
- **Data-driven analysis**: With appropriate tools, you can use diagnostic data from devices to inform your choices.
|
||||
@ -8,7 +8,7 @@ author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.localizationpriority: medium
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 12/31/2017
|
||||
@ -19,7 +19,7 @@ ms.date: 12/31/2017
|
||||
Having worked through the activities in the planning phase, you should be in a good position to prepare your environment and process to deploy Windows client. The planning phase left you with these useful items:
|
||||
|
||||
- A clear understanding of necessary personnel and their roles and criteria for [rating app readiness](plan-define-readiness.md)
|
||||
- A plan for [testing and validating](plan-determine-app-readiness.md) apps
|
||||
- A plan for [testing and validating](/windows/compatibility/windows-11/testing-guidelines) apps
|
||||
- An assessment of your [deployment infrastructure](eval-infra-tools.md) and definitions for operational readiness
|
||||
- A [deployment plan](create-deployment-plan.md) that defines the rings you want to use
|
||||
|
||||
@ -35,7 +35,7 @@ Your infrastructure probably includes many different components and tools. You n
|
||||
|
||||
1. Review all of the infrastructure changes that you've identified in your plan. It's important to understand the changes that need to be made and to detail how to implement them. This process prevents problems later on.
|
||||
|
||||
2. Validate your changes. You validate the changes for your infrastructure's components and tools, to help you understand how your changes could affect your production environment.
|
||||
2. Validate your changes. You validate the changes for your infrastructure's components and tools, to help you understand how your changes could affect your production environment.
|
||||
|
||||
3. Implement the changes. Once the changes have been validated, you can implement the changes across the wider infrastructure.
|
||||
|
||||
@ -166,11 +166,11 @@ You can also create and run scripts to perform additional cleanup actions on dev
|
||||
|
||||
In the plan phase, you determined the specific infrastructure and configuration changes that needed to be implemented to add new capabilities to the environment. Now you can move on to implementing those changes defined in the plan phase. You need to complete these higher-level tasks to gain those new capabilities:
|
||||
|
||||
- Enable capabilities across the environment by implementing the changes. For example, implement updates to relevant ADMX templates in Active Directory. New Windows versions come with new policies that you use to update ADMX templates.
|
||||
- Enable capabilities across the environment by implementing the changes. For example, implement updates to relevant ADMX templates in Active Directory. New Windows versions come with new policies that you use to update ADMX templates.
|
||||
|
||||
- Validate new changes to understand how they affect the wider environment.
|
||||
|
||||
- Remediate any potential problems that have been identified through validation.
|
||||
- Remediate any potential problems that have been identified through validation.
|
||||
|
||||
## Prepare users
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user