mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
fix note error
This commit is contained in:
parent
ed799bca60
commit
76b7dd8d3c
@ -11,7 +11,6 @@ ms.pagetype: appcompat
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -42,11 +41,8 @@ The following flowchart shows the steps for using the Compatibility Administrato
|
|||||||
>[!IMPORTANT]
|
>[!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.
|
>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.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## In this section
|
## In this section
|
||||||
|
|
||||||
|
|
||||||
<table>
|
<table>
|
||||||
<colgroup>
|
<colgroup>
|
||||||
<col width="50%" />
|
<col width="50%" />
|
||||||
@ -73,14 +69,3 @@ The following flowchart shows the steps for using the Compatibility Administrato
|
|||||||
</tr>
|
</tr>
|
||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -11,7 +11,6 @@ ms.pagetype: appcompat
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -76,12 +75,3 @@ If you are unable to find a preloaded compatibility fix for your application, yo
|
|||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -323,19 +323,7 @@ If you choose to not use the Windows To Go startup options or are using a PC run
|
|||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
[Windows To Go: feature overview](windows-to-go-overview.md)
|
[Windows To Go: feature overview](windows-to-go-overview.md)<br>
|
||||||
|
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)<br>
|
||||||
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
|
[Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)<br>
|
||||||
|
|
||||||
[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.md)
|
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -11,7 +11,6 @@ ms.pagetype: appcompat
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -31,7 +30,6 @@ You can disable and enable individual compatibility fixes in your customized dat
|
|||||||
|
|
||||||
## Disabling Compatibility Fixes
|
## Disabling Compatibility Fixes
|
||||||
|
|
||||||
|
|
||||||
Customized compatibility databases can become quite complex as you add your fixes for the multiple applications found in your organization. Over time, you may find you need to disable a particular fix in your customized database. For example, if a software vendor releases a fix for an issue addressed in one of your compatibility fixes, you must validate that the vendor's fix is correct and that it resolves your issue. To do this, you must temporarily disable the compatibility fix and then test your application.
|
Customized compatibility databases can become quite complex as you add your fixes for the multiple applications found in your organization. Over time, you may find you need to disable a particular fix in your customized database. For example, if a software vendor releases a fix for an issue addressed in one of your compatibility fixes, you must validate that the vendor's fix is correct and that it resolves your issue. To do this, you must temporarily disable the compatibility fix and then test your application.
|
||||||
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
@ -66,4 +64,5 @@ You can enable your disabled compatibility fixes at any time.
|
|||||||
2. On the **Database** menu, click **Enable Entry**.
|
2. On the **Database** menu, click **Enable Entry**.
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||||
|
@ -11,7 +11,6 @@ ms.pagetype: appcompat
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -172,13 +171,5 @@ You can export any of your search results into a tab-delimited text (.txt) file
|
|||||||
2. Browse to the location where you intend to store the search results file, and then click **Save**.
|
2. Browse to the location where you intend to store the search results file, and then click **Save**.
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -11,13 +11,11 @@ ms.pagetype: appcompat
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
# Understanding and Using Compatibility Fixes
|
# Understanding and Using Compatibility Fixes
|
||||||
|
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
|
||||||
- Windows 10
|
- Windows 10
|
||||||
@ -31,7 +29,6 @@ As the Windows operating system evolves to support new technology and functional
|
|||||||
|
|
||||||
## How the Compatibility Fix Infrastructure Works
|
## How the Compatibility Fix Infrastructure Works
|
||||||
|
|
||||||
|
|
||||||
The Compatibility Fix infrastructure uses the linking ability of APIs to redirect an application from Windows code directly to alternative code that implements the compatibility fix.
|
The Compatibility Fix infrastructure uses the linking ability of APIs to redirect an application from Windows code directly to alternative code that implements the compatibility fix.
|
||||||
|
|
||||||
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.
|
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.
|
||||||
@ -49,7 +46,6 @@ Specifically, the process modifies the address of the affected Windows function
|
|||||||
|
|
||||||
## Design Implications of the Compatibility Fix Infrastructure
|
## Design Implications of the Compatibility Fix Infrastructure
|
||||||
|
|
||||||
|
|
||||||
There are important considerations to keep in mind when determining your application fix strategy, due to certain characteristics of the Compatibility Fix infrastructure.
|
There are important considerations to keep in mind when determining your application fix strategy, due to certain characteristics of the Compatibility Fix infrastructure.
|
||||||
|
|
||||||
- The compatibility fix is not part of the Windows operating system (as shown in the previous figure). Therefore, the same security restrictions apply to the compatibility fix as apply to the application code, which means that you cannot use compatibility fixes to bypass any of the security mechanisms of the operating system. Therefore, compatibility fixes do not increase your security exposure, nor do you need to lower your security settings to accommodate compatibility fixes.
|
- The compatibility fix is not part of the Windows operating system (as shown in the previous figure). Therefore, the same security restrictions apply to the compatibility fix as apply to the application code, which means that you cannot use compatibility fixes to bypass any of the security mechanisms of the operating system. Therefore, compatibility fixes do not increase your security exposure, nor do you need to lower your security settings to accommodate compatibility fixes.
|
||||||
@ -65,7 +61,6 @@ There are important considerations to keep in mind when determining your applica
|
|||||||
|
|
||||||
## Determining When to Use a Compatibility Fix
|
## Determining When to Use a Compatibility Fix
|
||||||
|
|
||||||
|
|
||||||
The decision to use compatibility fixes to remedy your compatibility issues may involve more than just technical issues. The following scenarios reflect other common reasons for using a compatibility fix.
|
The decision to use compatibility fixes to remedy your compatibility issues may involve more than just technical issues. The following scenarios reflect other common reasons for using a compatibility fix.
|
||||||
|
|
||||||
### Scenario 1
|
### Scenario 1
|
||||||
@ -88,15 +83,14 @@ In the situation where an application is either unimportant to your organization
|
|||||||
|
|
||||||
## Determining Which Version of an Application to Fix
|
## Determining Which Version of an Application to Fix
|
||||||
|
|
||||||
|
|
||||||
You can apply a compatibility fix to a particular version of an application, either by using the "up to or including" clause or by selecting that specific version. This means that the next version of the application will not have the compatibility fix automatically applied. This is important, because it allows you to continue to use your application, but it also encourages the vendor to fix the application.
|
You can apply a compatibility fix to a particular version of an application, either by using the "up to or including" clause or by selecting that specific version. This means that the next version of the application will not have the compatibility fix automatically applied. This is important, because it allows you to continue to use your application, but it also encourages the vendor to fix the application.
|
||||||
|
|
||||||
## Support for Compatibility Fixes
|
## Support for Compatibility Fixes
|
||||||
|
|
||||||
|
|
||||||
Compatibility fixes are shipped as part of the Windows operating system and are updated by using Windows Update. Therefore, they receive the same level of support as Windows itself.
|
Compatibility fixes are shipped as part of the Windows operating system and are updated by using Windows Update. Therefore, they receive the same level of support as Windows itself.
|
||||||
|
|
||||||
You can apply the compatibility fixes to any of your applications. However, Microsoft does not provide the tools to use the Compatibility Fix infrastructure to create your own custom fixes.
|
You can apply the compatibility fixes to any of your applications. However, Microsoft does not provide the tools to use the Compatibility Fix infrastructure to create your own custom fixes.
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)
|
[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)
|
||||||
|
@ -11,7 +11,6 @@ ms.pagetype: appcompat
|
|||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.date: 04/19/2017
|
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -46,15 +45,5 @@ Compatibility Administrator enables you to copy your compatibility fixes from on
|
|||||||
If you open the **Events** screen and then perform the copy operation, you can see a description of the action, along with the time stamp, which enables you to view your fix information without confusion.
|
If you open the **Events** screen and then perform the copy operation, you can see a description of the action, along with the time stamp, which enables you to view your fix information without confusion.
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
[Creating a Custom Compatibility Mode in Compatibility Administrator](creating-a-custom-compatibility-mode-in-compatibility-administrator.md)
|
[Creating a Custom Compatibility Mode in Compatibility Administrator](creating-a-custom-compatibility-mode-in-compatibility-administrator.md)<br>
|
||||||
|
|
||||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -41,19 +41,13 @@ PCs that meet the Windows 7 or later [certification requirements](https://go.mi
|
|||||||
|
|
||||||
## <a href="" id="bkmk-wtgdif"></a>Differences between Windows To Go and a typical installation of Windows
|
## <a href="" id="bkmk-wtgdif"></a>Differences between Windows To Go and a typical installation of Windows
|
||||||
|
|
||||||
|
|
||||||
Windows To Go workspace operates just like any other installation of Windows with a few exceptions. These exceptions are:
|
Windows To Go workspace operates just like any other installation of Windows with a few exceptions. These exceptions are:
|
||||||
|
|
||||||
- **Internal disks are offline.** To ensure data isn’t accidentally disclosed, internal hard disks on the host computer are offline by default when booted into a Windows To Go workspace. Similarly if a Windows To Go drive is inserted into a running system, the Windows To Go drive will not be listed in Windows Explorer.
|
- **Internal disks are offline.** To ensure data isn’t accidentally disclosed, internal hard disks on the host computer are offline by default when booted into a Windows To Go workspace. Similarly if a Windows To Go drive is inserted into a running system, the Windows To Go drive will not be listed in Windows Explorer.
|
||||||
|
|
||||||
- **Trusted Platform Module (TPM) is not used.** When using BitLocker Drive Encryption a pre-operating system boot password will be used for security rather than the TPM since the TPM is tied to a specific computer and Windows To Go drives will move between computers.
|
- **Trusted Platform Module (TPM) is not used.** When using BitLocker Drive Encryption a pre-operating system boot password will be used for security rather than the TPM since the TPM is tied to a specific computer and Windows To Go drives will move between computers.
|
||||||
|
|
||||||
- **Hibernate is disabled by default.** To ensure that the Windows To Go workspace is able to move between computers easily, hibernation is disabled by default. Hibernation can be re-enabled by using Group Policy settings.
|
- **Hibernate is disabled by default.** To ensure that the Windows To Go workspace is able to move between computers easily, hibernation is disabled by default. Hibernation can be re-enabled by using Group Policy settings.
|
||||||
|
|
||||||
- **Windows Recovery Environment is not available.** In the rare case that you need to recover your Windows To Go drive, you should re-image it with a fresh image of Windows.
|
- **Windows Recovery Environment is not available.** In the rare case that you need to recover your Windows To Go drive, you should re-image it with a fresh image of Windows.
|
||||||
|
|
||||||
- **Refreshing or resetting a Windows To Go workspace is not supported.** Resetting to the manufacturer’s standard for the computer doesn’t apply when running a Windows To Go workspace, so the feature was disabled.
|
- **Refreshing or resetting a Windows To Go workspace is not supported.** Resetting to the manufacturer’s standard for the computer doesn’t apply when running a Windows To Go workspace, so the feature was disabled.
|
||||||
|
|
||||||
- **Upgrading a Windows To Go workspace is not supported.** Older Windows 8 or Windows 8.1 Windows To Go workspaces cannot be upgraded to Windows 10 workspaces, nor can Windows 10 Windows To Go workspaces be upgraded to future versions of Windows 10. For new versions, the workspace needs to be re-imaged with a fresh image of Windows.
|
- **Upgrading a Windows To Go workspace is not supported.** Older Windows 8 or Windows 8.1 Windows To Go workspaces cannot be upgraded to Windows 10 workspaces, nor can Windows 10 Windows To Go workspaces be upgraded to future versions of Windows 10. For new versions, the workspace needs to be re-imaged with a fresh image of Windows.
|
||||||
|
|
||||||
## <a href="" id="bkmk-wtgroam"></a>Roaming with Windows To Go
|
## <a href="" id="bkmk-wtgroam"></a>Roaming with Windows To Go
|
||||||
@ -97,9 +91,7 @@ For more information about designing and planning your Windows To Go deployment,
|
|||||||
The devices listed in this section have been specially optimized and certified for Windows To Go and meet the necessary requirements for booting and running a full version of Windows 10 from a USB drive. The optimizations for Windows To Go include the following:
|
The devices listed in this section have been specially optimized and certified for Windows To Go and meet the necessary requirements for booting and running a full version of Windows 10 from a USB drive. The optimizations for Windows To Go include the following:
|
||||||
|
|
||||||
- Windows To Go certified USB drives are built for high random read/write speeds and support the thousands of random access I/O operations per second required for running normal Windows workloads smoothly.
|
- Windows To Go certified USB drives are built for high random read/write speeds and support the thousands of random access I/O operations per second required for running normal Windows workloads smoothly.
|
||||||
|
|
||||||
- Windows To Go certified USB drives have been tuned to ensure they boot and run on hardware certified for use with Windows 7 and later.
|
- Windows To Go certified USB drives have been tuned to ensure they boot and run on hardware certified for use with Windows 7 and later.
|
||||||
|
|
||||||
- Windows To Go certified USB drives are built to last. Certified USB drives are backed with manufacturer warranties and should continue operating under normal usage. Refer to the manufacturer websites for warranty details.
|
- Windows To Go certified USB drives are built to last. Certified USB drives are backed with manufacturer warranties and should continue operating under normal usage. Refer to the manufacturer websites for warranty details.
|
||||||
|
|
||||||
As of the date of publication, the following are the USB drives currently certified for use as Windows To Go drives:
|
As of the date of publication, the following are the USB drives currently certified for use as Windows To Go drives:
|
||||||
@ -110,13 +102,9 @@ Using a USB drive that has not been certified is not supported
|
|||||||
|
|
||||||
|
|
||||||
- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://go.microsoft.com/fwlink/p/?LinkId=618714))
|
- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://go.microsoft.com/fwlink/p/?LinkId=618714))
|
||||||
|
|
||||||
- IronKey Workspace W500 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w500.html](https://go.microsoft.com/fwlink/p/?LinkId=618717))
|
- IronKey Workspace W500 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w500.html](https://go.microsoft.com/fwlink/p/?LinkId=618717))
|
||||||
|
|
||||||
- IronKey Workspace W300 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w300.html](https://go.microsoft.com/fwlink/p/?LinkId=618718))
|
- IronKey Workspace W300 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w300.html](https://go.microsoft.com/fwlink/p/?LinkId=618718))
|
||||||
|
|
||||||
- Kingston DataTraveler Workspace for Windows To Go ([http://www.kingston.com/wtg/](https://go.microsoft.com/fwlink/p/?LinkId=618719))
|
- Kingston DataTraveler Workspace for Windows To Go ([http://www.kingston.com/wtg/](https://go.microsoft.com/fwlink/p/?LinkId=618719))
|
||||||
|
|
||||||
- Spyrus Portable Workplace ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720))
|
- Spyrus Portable Workplace ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720))
|
||||||
|
|
||||||
We recommend that you run the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Portable Workplace.
|
We recommend that you run the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Portable Workplace.
|
||||||
@ -127,7 +115,6 @@ Using a USB drive that has not been certified is not supported
|
|||||||
> You must use the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Secure Portable Workplace. For more information about the Spyrus Deployment Suite for Windows To Go please refer to [http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720).
|
> You must use the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Secure Portable Workplace. For more information about the Spyrus Deployment Suite for Windows To Go please refer to [http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- Spyrus Worksafe ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720))
|
- Spyrus Worksafe ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720))
|
||||||
|
|
||||||
**Tip**
|
**Tip**
|
||||||
@ -152,9 +139,7 @@ Using a USB drive that has not been certified is not supported
|
|||||||
When assessing the use of a PC as a host for a Windows To Go workspace you should consider the following criteria:
|
When assessing the use of a PC as a host for a Windows To Go workspace you should consider the following criteria:
|
||||||
|
|
||||||
- Hardware that has been certified for use with Windows 7or later operating systems will work well with Windows To Go.
|
- Hardware that has been certified for use with Windows 7or later operating systems will work well with Windows To Go.
|
||||||
|
|
||||||
- Running a Windows To Go workspace from a computer that is running Windows RT is not a supported scenario.
|
- Running a Windows To Go workspace from a computer that is running Windows RT is not a supported scenario.
|
||||||
|
|
||||||
- Running a Windows To Go workspace on a Mac computer is not a supported scenario.
|
- Running a Windows To Go workspace on a Mac computer is not a supported scenario.
|
||||||
|
|
||||||
The following table details the characteristics that the host computer must have to be used with Windows To Go:
|
The following table details the characteristics that the host computer must have to be used with Windows To Go:
|
||||||
@ -249,37 +234,17 @@ In addition to the USB boot support in the BIOS, the Windows 10 image on your W
|
|||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Additional resources
|
## Additional resources
|
||||||
|
|
||||||
|
|
||||||
- [Windows 10 forums](https://go.microsoft.com/fwlink/p/?LinkId=618949)
|
- [Windows 10 forums](https://go.microsoft.com/fwlink/p/?LinkId=618949)
|
||||||
|
|
||||||
- [Windows To Go Step by Step Wiki](https://go.microsoft.com/fwlink/p/?LinkId=618950)
|
- [Windows To Go Step by Step Wiki](https://go.microsoft.com/fwlink/p/?LinkId=618950)
|
||||||
|
|
||||||
- [Tips for configuring your BIOS settings to work with Windows To Go](https://go.microsoft.com/fwlink/p/?LinkId=618951)
|
- [Tips for configuring your BIOS settings to work with Windows To Go](https://go.microsoft.com/fwlink/p/?LinkId=618951)
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
[Deploy Windows To Go in your organization](https://go.microsoft.com/fwlink/p/?LinkId=619975)<br>
|
||||||
- [Deploy Windows To Go in your organization](https://go.microsoft.com/fwlink/p/?LinkId=619975)
|
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)<br>
|
||||||
|
[Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)<br>
|
||||||
- [Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
[Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)<br>
|
||||||
|
[Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)<br>
|
||||||
- [Prepare your organization for Windows To Go](prepare-your-organization-for-windows-to-go.md)
|
[Best practice recommendations for Windows To Go](best-practice-recommendations-for-windows-to-go.md)
|
||||||
|
|
||||||
- [Deployment considerations for Windows To Go](deployment-considerations-for-windows-to-go.md)
|
|
||||||
|
|
||||||
- [Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)
|
|
||||||
|
|
||||||
- [Best practice recommendations for Windows To Go](best-practice-recommendations-for-windows-to-go.md)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user