mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Merge pull request #7315 from lizgt2000/metaplanning
meta deploy planning
This commit is contained in:
Stephanie Savell
GitHub
commit
7e9119f64f
@ -4,9 +4,10 @@ description: The Microsoft Application Compatibility Toolkit (ACT) helps you see
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Application Compatibility Toolkit (ACT) Technical Reference
|
||||
|
||||
@ -4,10 +4,11 @@ description: Learn how to apply filters to results from the Standard User Analyz
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Applying Filters to Data in the SUA Tool
|
||||
|
||||
@ -4,10 +4,11 @@ description: The Compatibility Administrator tool provides a way to query your c
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Available Data Types and Operators in Compatibility Administrator
|
||||
|
||||
@ -4,9 +4,10 @@ description: Learn about best practice recommendations for using Windows To Go,
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Best practice recommendations for Windows To Go
|
||||
|
||||
@ -4,10 +4,11 @@ ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
description: The Compatibility Administrator tool helps you resolve potential application-compatibility issues before deploying a new version of Windows.
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Compatibility Administrator User's Guide
|
||||
|
||||
@ -4,11 +4,12 @@ ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
description: Learn how to deploy your compatibility fixes into an application-installation package or through a centralized compatibility-fix database.
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-mar2020
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Compatibility Fix Database Management Strategies and Deployment
|
||||
|
||||
@ -4,11 +4,12 @@ description: Find compatibility fixes for all Windows operating systems that hav
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista
|
||||
|
||||
@ -4,9 +4,10 @@ description: The Compatibility Administrator tool uses the term fix to describe
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Creating a Custom Compatibility Fix in Compatibility Administrator
|
||||
|
||||
@ -4,10 +4,11 @@ description: Windows® provides several compatibility modes, groups of compatibi
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Creating a Custom Compatibility Mode in Compatibility Administrator
|
||||
|
||||
@ -4,10 +4,11 @@ description: Create an AppHelp text message with Compatibility Administrator; a
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Creating an AppHelp Message in Compatibility Administrator
|
||||
@ -29,7 +30,7 @@ The Compatibility Administrator tool enables you to create an AppHelp text messa
|
||||
|
||||
A blocking AppHelp message prevents the application from starting and displays a message to the user. You can define a specific URL where the user can download an updated driver or other fix to resolve the issue. When using a blocking AppHelp message, you must also define the file-matching information to identify the version of the application and enable the corrected version to continue.
|
||||
|
||||
A non-blocking AppHelp message does not prevent the application from starting, but provides a message to the user including information such as security issues, updates to the application, or changes to the location of network resources.
|
||||
A non-blocking AppHelp message doesn't prevent the application from starting, but provides a message to the user that includes information such as security issues, updates to the application, or changes to the location of network resources.
|
||||
|
||||
## Searching for Existing Compatibility Fixes
|
||||
|
||||
@ -50,17 +51,17 @@ The Compatibility Administrator tool has preloaded fixes for many common applica
|
||||
## Creating a New AppHelp Message
|
||||
|
||||
|
||||
If you are unable to find a preloaded AppHelp message for your application, you can create a new one for use by your custom database.
|
||||
If you're unable to find a preloaded AppHelp message for your application, you can create a new one for use by your custom database.
|
||||
|
||||
**To create a new AppHelp message**
|
||||
|
||||
1. In the left-side pane of Compatibility Administrator, below the **Custom Databases** heading, right-click the name of the database to which you will apply the AppHelp message, click **Create New**, and then click **AppHelp Message**.
|
||||
1. In the left-side pane of Compatibility Administrator, below the **Custom Databases** heading, right-click the name of the database to which you'll apply the AppHelp message, click **Create New**, and then click **AppHelp Message**.
|
||||
|
||||
2. Type the name of the application to which this AppHelp message applies, type the name of the application vendor, browse to the location of the application file (.exe) on your computer, and then click **Next**.
|
||||
|
||||
The wizard shows the known **Matching Information**, which is used for program identification.
|
||||
|
||||
3. Select any additional criteria to use to match your applications to the AppHelp message, and then click **Next**.
|
||||
3. Select any other criteria to use to match your applications to the AppHelp message, and then click **Next**.
|
||||
|
||||
By default, Compatibility Administrator selects the basic matching criteria for your application.
|
||||
|
||||
@ -68,9 +69,9 @@ If you are unable to find a preloaded AppHelp message for your application, you
|
||||
|
||||
4. Click one of the following options:
|
||||
|
||||
- **Display a message and allow this program to run**. This is a non-blocking message, which means that you can alert the user that there might be a problem, but the application is not prevented from starting.
|
||||
- **Display a message and allow this program to run**. This message is non-blocking, which means that you can alert the user that there might be a problem, but the application isn't prevented from starting.
|
||||
|
||||
- **Display a message and do not allow this program to run**. This is a blocking message, which means that the application will not start. Instead, this message points the user to a location that provides more information about fixing the issue.
|
||||
- **Display a message and do not allow this program to run**. This message is blocking, which means that the application won't start. Instead, this message points the user to a location that provides more information about fixing the issue.
|
||||
|
||||
5. Click **Next**.
|
||||
|
||||
|
||||
@ -4,10 +4,11 @@ description: Learn about deployment considerations for Windows To Go, such as th
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Deployment considerations for Windows To Go
|
||||
|
||||
@ -4,10 +4,11 @@ description: You can disable and enable individual compatibility fixes in your c
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Enabling and Disabling Compatibility Fixes in Compatibility Administrator
|
||||
|
||||
@ -1,13 +1,14 @@
|
||||
---
|
||||
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.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.technology: itpro-fundamentals
|
||||
---
|
||||
# Windows client features lifecycle
|
||||
|
||||
|
||||
@ -4,10 +4,11 @@ description: On the user interface for the Standard User Analyzer (SUA) tool, yo
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Fixing Applications by Using the SUA Tool
|
||||
|
||||
@ -1,12 +1,13 @@
|
||||
---
|
||||
title: Plan for Windows 10 deployment (Windows 10)
|
||||
description: Find resources for your Windows 10 deployment. Windows 10 provides new deployment capabilities and tools, and introduces new ways to keep the OS up to date.
|
||||
ms.prod: w10
|
||||
description: Find resources for your Windows 10 deployment. Windows 10 provides new deployment capabilities and tools, and introduces new ways to keep the OS up to date.
|
||||
ms.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: dougeby
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Plan for Windows 10 deployment
|
||||
|
||||
@ -4,10 +4,11 @@ description: The Compatibility Administrator tool enables the creation and the u
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator
|
||||
|
||||
@ -4,10 +4,11 @@ description: Learn why you should use compatibility fixes, and how to deploy and
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Managing Application-Compatibility Fixes and Custom Fix Databases
|
||||
|
||||
@ -1,18 +1,18 @@
|
||||
---
|
||||
title: Prepare your organization for Windows To Go (Windows 10)
|
||||
description: Though Windows To Go is no longer being developed, you can find info here about the the “what”, “why”, and “when” of deployment.
|
||||
description: Though Windows To Go is no longer being developed, you can find info here about the “what”, “why”, and “when” of deployment.
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Prepare your organization for Windows To Go
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
@ -24,15 +24,14 @@ The following information is provided to help you plan and design a new deployme
|
||||
|
||||
## What is Windows To Go?
|
||||
|
||||
|
||||
Windows To Go is a feature of Windows 10 Enterprise and Windows 10 Education that enables users to boot Windows from a USB-connected external drive. Windows To Go drives can use the same image that enterprises use for their desktops and laptops, and can be managed the same way. Offering a new mobility option, a Windows To Go workspace is not intended to replace desktops or laptops, or supplant other mobility offerings.
|
||||
Windows To Go is a feature of Windows 10 Enterprise and Windows 10 Education that enables users to boot Windows from a USB-connected external drive. Windows To Go drives can use the same image that enterprises use for their desktops and laptops, and can be managed the same way. Offering a new mobility option, a Windows To Go workspace isn't intended to replace desktops or laptops, or supplant other mobility offerings.
|
||||
|
||||
Enterprise customers utilizing Volume Activation Windows licensing will be able to deploy USB drives provisioned with Windows To Go workspace. These drives will be bootable on multiple compatible host computers. Compatible host computers are computers that are:
|
||||
|
||||
- USB boot capable
|
||||
- Have USB boot enabled in the firmware
|
||||
- Meet Windows 7 minimum system requirements
|
||||
- Have compatible processor architectures (for example, x86 or AMD64) as the image used to create the Windows To Go workspace. ARM is not a supported processor for Windows To Go.
|
||||
- Have compatible processor architectures (for example, x86 or AMD64) as the image used to create the Windows To Go workspace. ARM isn't a supported processor for Windows To Go.
|
||||
- Have firmware architecture that is compatible with the architecture of the image used for the Windows To Go workspace
|
||||
|
||||
Booting a Windows To Go workspace requires no specific software on the host computer. PCs certified for Windows 7 and later can host Windows To Go.
|
||||
@ -46,7 +45,7 @@ The following scenarios are examples of situations in which Windows To Go worksp
|
||||
|
||||
- **Continuance of operations (COO).** In this scenario, selected employees receive a USB drive with a Windows To Go workspace, which includes all of the applications that the employees use at work. The employees can keep the device at home, in a briefcase, or wherever they want to store it until needed. When the users boot their home computer from the USB drive, it will create a corporate desktop experience so that they can quickly start working. On the very first boot, the employee sees that Windows is installing devices; after that one time, the Windows To Go drive boots like a normal computer. If they have enterprise network access, employees can use a virtual private network (VPN) connection or DirectAccess to access corporate resources. If the enterprise network is available, the Windows To Go workspace will automatically be updated using your standard client management processes.
|
||||
|
||||
- **Contractors and temporary workers.** In this situation, an enterprise IT pro or manager would distribute the Windows To Go drive directly to the worker where they can be assisted with any necessary additional user education needs or address any possible compatibility issues. While the worker is on assignment, they can boot their computer exclusively from the Windows To Go drive and run all applications in that environment until the end of the assignment when the device is returned. No installation of software is required on the worker's personal computer.
|
||||
- **Contractors and temporary workers.** In this situation, an enterprise IT pro or manager would distribute the Windows To Go drive directly to the worker where they can be assisted with any necessary other user education needs or address any possible compatibility issues. While the worker is on assignment, they can boot their computer exclusively from the Windows To Go drive and run all applications in that environment until the end of the assignment when the device is returned. No installation of software is required on the worker's personal computer.
|
||||
|
||||
- **Managed free seating.** The employee is issued a Windows To Go drive that is then used with the host computer assigned to that employee for a given session (this could be a vehicle, workspace, or standalone laptop). When the employee leaves the session, the next time they return they use the same USB flash drive but use a different host computer.
|
||||
|
||||
@ -55,55 +54,45 @@ The following scenarios are examples of situations in which Windows To Go worksp
|
||||
- **Travel lightly.** In this situation you have employees who are moving from site to site, but who always will have access to a compatible host computer on site. Using Windows To Go workspaces allows them to travel without the need to pack their PC.
|
||||
|
||||
> [!NOTE]
|
||||
> If the employee wants to work offline for the majority of the time, but still maintain the ability to use the drive on the enterprise network, they should be informed of how often the Windows To Go workspace needs to be connected to the enterprise network. Doing so will ensure that the drive retains its access privileges and the workspace's computer object is not potentially deleted from Active Directory Domain Services (AD DS).
|
||||
> If the employee wants to work offline for the majority of the time, but still maintain the ability to use the drive on the enterprise network, they should be informed of how often the Windows To Go workspace needs to be connected to the enterprise network. Doing so will ensure that the drive retains its access privileges and the workspace's computer object isn't potentially deleted from Active Directory Domain Services (AD DS).
|
||||
|
||||
|
||||
## Infrastructure considerations
|
||||
|
||||
## Infrastructure considerations
|
||||
|
||||
|
||||
Because Windows To Go requires no additional software and minimal configuration, the same tools used to deploy images to other PCs can be used by an enterprise to install Windows To Go on a large group of USB devices. Moreover, because Windows To Go is compatible with connectivity and synchronization solutions already in use—such as Remote Desktop, DirectAccess and Folder Redirection—no additional infrastructure or management is necessary for this deployment. A Windows To Go image can be created on a USB drive that is identical to the hard drive inside a desktop. However, you may wish to consider making some modifications to your infrastructure to help make management of Windows To Go drives easier and to be able to identify them as a distinct device group.
|
||||
Because Windows To Go requires no other software and minimal configuration, the same tools used to deploy images to other PCs can be used by an enterprise to install Windows To Go on a large group of USB devices. Moreover, because Windows To Go is compatible with connectivity and synchronization solutions already in use—such as Remote Desktop, DirectAccess and Folder Redirection—no other infrastructure or management is necessary for this deployment. A Windows To Go image can be created on a USB drive that is identical to the hard drive inside a desktop. However, you may wish to consider making some modifications to your infrastructure to help make management of Windows To Go drives easier and to be able to identify them as a distinct device group.
|
||||
|
||||
## Activation considerations
|
||||
|
||||
|
||||
Windows To Go uses volume activation. You can use either Active Directory-based activation or KMS activation with Windows To Go. The Windows To Go workspace counts as another installation when assessing compliance with application licensing agreements.
|
||||
|
||||
Microsoft software, such as Microsoft Office, distributed to a Windows To Go workspace must also be activated. Office deployment is fully supported on Windows To Go. Please note, due to the retail subscription activation method associated with Microsoft 365 Apps for enterprise, Microsoft 365 Apps for enterprise subscribers are provided volume licensing activation rights for Office Professional Plus 2013 MSI for local installation on the Windows To Go drive. This is available to organizations who purchase Microsoft 365 Apps for enterprise or Office 365 Enterprise SKUs containing Microsoft 365 Apps for enterprise via volume licensing channels. For more information about activating Microsoft Office, see [Volume activation methods in Office 2013](/DeployOffice/vlactivation/plan-volume-activation-of-office).
|
||||
|
||||
You should investigate other software manufacturer's licensing requirements to ensure they are compatible with roaming usage before deploying them to a Windows To Go workspace.
|
||||
You should investigate other software manufacturer's licensing requirements to ensure they're compatible with roaming usage before deploying them to a Windows To Go workspace.
|
||||
|
||||
> [!NOTE]
|
||||
> Using Multiple Activation Key (MAK) activation is not a supported activation method for Windows To Go as each different PC-host would require separate activation. MAK activation should not be used for activating Windows, Office, or any other application on a Windows To Go drive.
|
||||
> Using Multiple Activation Key (MAK) activation isn't a supported activation method for Windows To Go as each different PC-host would require separate activation. MAK activation should not be used for activating Windows, Office, or any other application on a Windows To Go drive.
|
||||
|
||||
|
||||
|
||||
See [Plan for Volume Activation](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj134042(v=ws.11)) for more information about these activation methods and how they can be used in your organization.
|
||||
See [Plan for Volume Activation](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj134042(v=ws.11)) for more information about these activation methods and how they can be used in your organization.
|
||||
|
||||
## Organizational unit structure and use of Group Policy Objects
|
||||
|
||||
You may find it beneficial to create other Active Directory organizational unit (OU) structures to support your Windows To Go deployment: one for host computer accounts and one for Windows To Go workspace computer accounts. Creating an organizational unit for host computers allows you to enable the Windows To Go Startup Options using Group Policy for only the computers that will be used as Windows To Go hosts. Setting this policy helps to prevent computers from being accidentally configured to automatically boot from USB devices and allows closer monitoring and control of those computers that can boot from a USB device. The organizational unit for Windows To Go workspaces allows you to apply specific policy controls to them, such as the ability to use the Store application, power state controls, and line-of-business application installation.
|
||||
|
||||
You may find it beneficial to create additional Active Directory organizational unit (OU) structures to support your Windows To Go deployment; one for host computer accounts and one for Windows To Go workspace computer accounts. Creating an organizational unit for host computers allows you to enable the Windows To Go Startup Options using Group Policy for only the computers that will be used as Windows To Go hosts. Setting this policy helps to prevent computers from being accidentally configured to automatically boot from USB devices and allows closer monitoring and control of those computers which have the ability to boot from a USB device. The organizational unit for Windows To Go workspaces allows you to apply specific policy controls to them, such as the ability to use the Store application, power state controls, and line-of-business application installation.
|
||||
|
||||
If you are deploying Windows To Go workspaces for a scenario in which they are not going to be roaming, but are instead being used on the same host computer, such as with temporary or contract employees, you might wish to enable hibernation or the Windows Store.
|
||||
If you're deploying Windows To Go workspaces for a scenario in which they're not going to be roaming, but are instead being used on the same host computer, such as with temporary or contract employees, you might wish to enable hibernation or the Windows Store.
|
||||
|
||||
For more information about Group Policy settings that can be used with Windows To Go, see [Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)
|
||||
|
||||
## Computer account management
|
||||
|
||||
|
||||
If you configure Windows To Go drives for scenarios where drives may remain unused for extended period of time such as use in continuance of operations scenarios, the AD DS computer account objects that correspond to Windows To Go drives have the potential to become stale and be pruned during maintenance operations. To address this issue, you should either have users log on regularly according to a schedule or modify any maintenance scripts to not clean up computer accounts in the Windows To Go device organizational unit.
|
||||
If you configure Windows To Go drives for scenarios where drives may remain unused for extended periods of time such as used in continuance of operations scenarios, the AD DS computer account objects that correspond to Windows To Go drives have the potential to become stale and be pruned during maintenance operations. To address this issue, you should either have users log on regularly according to a schedule or modify any maintenance scripts to not clean computer accounts in the Windows To Go device organizational unit.
|
||||
|
||||
## User account and data management
|
||||
|
||||
|
||||
People use computers to work with data and consume content - that is their core function. The data must be stored and retrievable for it to be useful. When users are working in a Windows To Go workspace, they need to have the ability to get to the data that they work with and to keep it accessible when the workspace is not being used. For this reason we recommend that you use folder redirection and offline files to redirect the path of local folders (such as the Documents folder) to a network location, while caching the contents locally for increased speed and availability. We also recommend that you use roaming user profiles to synchronize user specific settings so that users receive the same operating system and application settings when using their Windows To Go workspace and their desktop computer. When a user signs in using a domain account that is set up with a file share as the profile path, the user's profile is downloaded to the local computer and merged with the local profile (if present). When the user logs off the computer, the local copy of their profile, including any changes, is merged with the server copy of the profile. For more information, see [Folder Redirection, Offline Files, and Roaming User Profiles overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh848267(v=ws.11)).
|
||||
People use computers to work with data and consume content - that is their core function. The data must be stored and retrievable for it to be useful. When users are working in a Windows To Go workspace, they need to be able to get to the data that they work with and to keep it accessible when the workspace isn't being used. For this reason we recommend that you use folder redirection and offline files to redirect the path of local folders (such as the Documents folder) to a network location, while caching the contents locally for increased speed and availability. We also recommend that you use roaming user profiles to synchronize user specific settings so that users receive the same operating system and application settings when using their Windows To Go workspace and their desktop computer. When a user signs in using a domain account that is set up with a file share as the profile path, the user's profile is downloaded to the local computer and merged with the local profile (if present). When the user logs off the computer, the local copy of their profile, including any changes, is merged with the server copy of the profile. For more information, see [Folder Redirection, Offline Files, and Roaming User Profiles overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh848267(v=ws.11)).
|
||||
|
||||
Windows To Go is fully integrated with your Microsoft account. Setting synchronization is accomplished by connecting a Microsoft account to a user account. Windows To Go devices fully support this feature and can be managed by Group Policy so that the customization and configurations you prefer will be applied to your Windows To Go workspace.
|
||||
|
||||
## Remote connectivity
|
||||
|
||||
|
||||
If you want Windows To Go to be able to connect back to organizational resources when it is being used off-premises a remote connectivity solution must be enabled. Windows Server 2012 DirectAccess can be used as can a virtual private network (VPN) solution. For more information about configuring a remote access solution, see the [Remote Access (DirectAccess, Routing and Remote Access) Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn636119(v=ws.11)).
|
||||
|
||||
## Related topics
|
||||
@ -116,6 +105,3 @@ If you want Windows To Go to be able to connect back to organizational resources
|
||||
[Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)
|
||||
|
||||
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.yml)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -4,10 +4,11 @@ description: Compatibility Administrator can locate specific executable (.exe) f
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Searching for Fixed Applications in Compatibility Administrator
|
||||
|
||||
@ -4,9 +4,10 @@ description: You can access the Query tool from within Compatibility Administrat
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Searching for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator
|
||||
|
||||
@ -4,9 +4,10 @@ description: Ensure that the data, content, and resources you work with in the W
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Security and data protection considerations for Windows To Go
|
||||
|
||||
@ -4,10 +4,11 @@ description: On the user interface for the Standard User Analyzer (SUA) tool, yo
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Showing Messages Generated by the SUA Tool
|
||||
|
||||
@ -5,10 +5,11 @@ ms.custom: seo-marvel-apr2020
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# SUA User's Guide
|
||||
|
||||
@ -4,10 +4,11 @@ description: The tabs in the Standard User Analyzer (SUA) tool show the User Acc
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Tabs on the SUA Tool Interface
|
||||
|
||||
@ -4,10 +4,11 @@ description: Learn how to test your application-mitigation packages, including h
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Testing Your Application Mitigation Packages
|
||||
|
||||
@ -4,9 +4,10 @@ description: As the Windows operating system evolves to support new technology a
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Understanding and Using Compatibility Fixes
|
||||
|
||||
@ -4,10 +4,11 @@ description: This section provides information about using the Compatibility Adm
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Using the Compatibility Administrator Tool
|
||||
|
||||
@ -4,10 +4,11 @@ description: Learn how to deploy customized database (.sdb) files using the Sdbi
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Using the Sdbinst.exe Command-Line Tool
|
||||
|
||||
@ -4,10 +4,11 @@ description: The Standard User Analyzer (SUA) tool can test applications and mon
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Using the SUA Tool
|
||||
|
||||
@ -4,10 +4,11 @@ description: The Standard User Analyzer (SUA) wizard, although it doesn't offer
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Using the SUA wizard
|
||||
|
||||
@ -4,9 +4,10 @@ description: You can use the Events screen to record and view activities in the
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Viewing the Events Screen in Compatibility Administrator
|
||||
|
||||
@ -4,10 +4,11 @@ description: Windows 10 will be compatible with most existing PC hardware; most
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Windows 10 compatibility
|
||||
|
||||
@ -4,10 +4,11 @@ description: There are new deployment options in Windows 10 that help you simpl
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Windows 10 deployment considerations
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
title: Deprecated features in Windows client
|
||||
description: Review the list of features that Microsoft is no longer developing in Windows 10 and Windows 11.
|
||||
ms.date: 07/21/2022
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-fundamentals
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
|
||||
@ -4,10 +4,11 @@ description: Review the infrastructure requirements for deployment and managemen
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Windows 10 infrastructure requirements
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Features and functionality removed in Windows client
|
||||
description: In this article, learn about the features and functionality that have been removed or replaced in Windows client.
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
@ -9,6 +9,7 @@ manager: dougeby
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
ms.collection: highpri
|
||||
ms.technology: itpro-fundamentals
|
||||
---
|
||||
|
||||
# Features and functionality removed in Windows client
|
||||
|
||||
@ -4,9 +4,10 @@ description: Windows To Go is a feature in Windows 10 Enterprise and Windows 10
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
ms.prod: windows-client
|
||||
author: aczechowski
|
||||
ms.topic: article
|
||||
ms.technology: itpro-deploy
|
||||
---
|
||||
|
||||
# Windows To Go: feature overview
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user