mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Merge branch 'master' of https://github.com/MicrosoftDocs/windows-docs-pr into 21H1
This commit is contained in:
greg-lindsay
@ -37,7 +37,7 @@ The Compatibility Administrator tool helps you resolve potential application-com
|
||||
|
||||
The following flowchart shows the steps for using the Compatibility Administrator tool to create your compatibility fixes, compatibility modes, and AppHelp messages.
|
||||
|
||||
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create and work with custom databases for 32-bit applications, and the 64-bit version to create and work with custom databases for 64-bit applications.
|
||||
|
||||
@ -46,11 +46,11 @@ The following sections discuss the boot experience, deployment methods, and tool
|
||||
|
||||
The following diagrams illustrate the two different methods you could use to provide Windows To Go drives to your users. The experiences differ depending on whether the user will be booting the device initially on-premises or off-premises:
|
||||
|
||||
|
||||
|
||||
|
||||
When a Windows To Go workspace is first used at the workplace, the Windows To Go workspace can be joined to the domain through the normal procedures that occur when a new computer is introduced. It obtains a lease, applicable policies are applied and set, and user account tokens are placed appropriately. BitLocker protection can be applied and the BitLocker recovery key automatically stored in Active Directory Domain Services. The user can access network resources to install software and get access to data sources. When the workspace is subsequently booted at a different location either on or off premises, the configuration required for it to connect back to the work network using either DirectAccess or a virtual private network connection can be configured. It is not necessary to configure the workspace for offline domain join. DirectAccess can make connecting to organizational resources easier, but is not required.
|
||||
|
||||
|
||||
|
||||
|
||||
When the Windows To Go workspace is going to be used first on an off-premises computer, such as one at the employee's home, then the IT professional preparing the Windows To Go drives should configure the drive to be able to connect to organizational resources and to maintain the security of the workspace. In this situation, the Windows To Go workspace needs to be configured for offline domain join and BitLocker needs to be enabled before the workspace has been initialized.
|
||||
|
||||
@ -63,7 +63,7 @@ DirectAccess can be used to ensure that the user can log in with their domain cr
|
||||
|
||||
The Image Deployment process can be accomplished either by a centralized IT process for your organization or by individual users creating their own Windows To Go workspaces. You must have local Administrator access and access to a Windows 10 Enterprise or Windows 10 Education image to create a Windows To Go workspace, or you must be using System Center 2012 Configuration Manager Service Pack 1 or later to distribute Windows To Go workspaces to users. The image deployment process takes a blank USB drive and a Windows 10 Enterprise image (WIM) and turns it into a Windows To Go drive.
|
||||
|
||||
|
||||
|
||||
|
||||
The simplest way to provision a Windows To Go drive is to use the Windows To Go Creator. After a single Windows To Go workspace has been created, it can be duplicated as many times as necessary using widely available USB duplicator products as long as the device has not been booted. After the Windows To Go drive is initialized, it should not be duplicated. Alternatively, Windows To Go Workspace Creator can be run multiple times to create multiple Windows To Go drives.
|
||||
|
||||
@ -265,13 +265,13 @@ If you are going to be using a Windows 7 computer as a host-PC, see the wiki art
|
||||
|
||||
Windows supports two types of PC firmware: Unified Extensible Firmware Interface (UEFI), which is the new standard, and legacy BIOS firmware, which was used in most PCs shipping with Windows 7 or earlier version of Windows. Each firmware type has completely different Windows boot components that are incompatible with each other. Beyond the different boot components, Windows supports different partition styles and layout requirements for each type of firmware as shown in the following diagrams.
|
||||
|
||||
|
||||
|
||||
|
||||
This presented a unique challenge for Windows To Go because the firmware type is not easily determined by end users—a UEFI computer looks just like a legacy BIOS computer and Windows To Go must boot on both types of firmware.
|
||||
|
||||
To enable booting Windows To Go on both types of firmware, a new disk layout is provided for Windows 8 or later that contains both sets of boot components on a FAT32 system partition and a new command-line option was added to bcdboot.exe to support this configuration. The **/f** option is used with the **bcdboot /s** command to specify the firmware type of the target system partition by appending either **UEFI**, **BIOS** or **ALL**. When creating Windows To Go drives manually you must use the **ALL** parameter to provide the Windows To Go drive the ability to boot on both types of firmware. For example, on volume H: (your Windows To Go USB drive letter), you would use the command **bcdboot C:\\windows /s H: /f ALL**. The following diagram illustrates the disk layout that results from that command:
|
||||
|
||||
|
||||
|
||||
|
||||
This is the only supported disk configuration for Windows To Go. With this disk configuration, a single Windows To Go drive can be booted on computers with UEFI and legacy BIOS firmware.
|
||||
|
||||
@ -283,7 +283,7 @@ Windows To Go Startup Options is a setting available on Windows 10-based PCs tha
|
||||
|
||||
1. On the Start screen, type, type **Windows To Go Startup Options**, click **Settings** and, then press Enter.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Select **Yes** to enable the startup options.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows 10 features lifecycle
|
||||
title: Windows client features lifecycle
|
||||
description: Learn about the lifecycle of Windows 10 features, as well as features that are no longer developed, removed features, and terminology assigned to a feature.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: plan
|
||||
@ -14,9 +14,11 @@ ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
# Windows 10 features lifecycle
|
||||
|
||||
- Applies to: Windows 10
|
||||
Applies to:
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
Each release of Windows 10 contains many new and improved features. Occasionally we also remove features and functionality, usually because there is a better option.
|
||||
Each release of Windows 10 and Windows 11 contains many new and improved features. Occasionally we also remove features and functionality, usually because there is a better option.
|
||||
|
||||
## Features no longer being developed
|
||||
|
||||
@ -26,7 +28,7 @@ The following topic lists features that are no longer being developed. These fea
|
||||
|
||||
## Features removed
|
||||
|
||||
The following topic has details about features that have been removed from Windows 10.
|
||||
The following topics have details about features that have been removed from Windows 10 or Windows 11. This includes features that are present in Windows 10, but are removed in Windows 11.
|
||||
|
||||
[Windows 10 features we removed](windows-10-removed-features.md)
|
||||
|
||||
|
||||
@ -33,11 +33,11 @@ The Compatibility Fix infrastructure uses the linking ability of APIs to redirec
|
||||
|
||||
The Windows Portable Executable File Format includes headers that contain the data directories that are used to provide a layer of indirection between the application and the linked file. API calls to the external binary files take place through the Import Address Table (IAT), which then directly calls the Windows operating system, as shown in the following figure.
|
||||
|
||||
|
||||
|
||||
|
||||
Specifically, the process modifies the address of the affected Windows function in the IAT to point to the compatibility fix code, as shown in the following figure.
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>For statically linked DLLs, the code redirection occurs as the application loads. You can also fix dynamically linked DLLs by hooking into the GetProcAddress API.
|
||||
|
||||
@ -42,7 +42,7 @@ Before you can use the SUA tool, you must install Application Verifier. You must
|
||||
|
||||
The following flowchart shows the process of using the SUA tool.
|
||||
|
||||
|
||||
|
||||
|
||||
**To collect UAC-related issues by using the SUA tool**
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ You must install Application Verifier before you can use the SUA Wizard. If Appl
|
||||
|
||||
The following flowchart shows the process of using the SUA Wizard.
|
||||
|
||||
|
||||
|
||||
|
||||
**To test an application by using the SUA Wizard**
|
||||
|
||||
|
||||
@ -68,7 +68,7 @@ Windows Server Update Services (WSUS) requires some additional configuration to
|
||||
2. In the **Products** tree, select the **Windows 10** and **Windows 10 LTSB** products and any other Windows 10-related items that you want. Click **OK**.
|
||||
3. From the **Synchronizations** node, right-click and choose **Synchronize Now**.
|
||||
|
||||
|
||||
|
||||
|
||||
WSUS product list with Windows 10 choices
|
||||
|
||||
|
||||
Reference in New Issue
Block a user