deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 05:47:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

minor changes

Browse Source
This commit is contained in:
Greg Lindsay 2017-04-14 16:40:01 -07:00
parent 30b924bf40
commit cf91420f4b
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
windows/deploy/change-history-for-deploy-windows-10.md
View File

@ -17,7 +17,7 @@ This topic lists new and updated topics in the [Deploy Windows 10](index.md) doc
| [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md) | Updated: The "refresh" and "replace" procedures were swapped in order so that it would not be necessary to save and restore VMs. Also a missing step was added to include the State migration point role. |
| [Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md)| Updated with minor fixes. |
| [What's new in Windows 10 deployment](deploy-whats-new.md)| New |
| [Manage Windows upgrades with Upgrade Readiness](deploy-whats-new.md)| Updated child topics under this node to include new feature and user interface changes. |
| [Manage Windows upgrades with Upgrade Readiness](manage-windows-upgrades-with-upgrade-readiness.md)| Updated child topics under this node to include new feature and user interface changes. |
## February 2017
| New or changed topic | Description |

2
windows/deploy/windows-10-poc-sc-config-mgr.md
View File

@ -788,7 +788,7 @@ In this first deployment scenario, we will deploy Windows 10 using PXE. This sce
![contoso.com\Computers](images/poc-computers.png)
In the replace procedure, PC1 will not be migrated to a new operating system. It is simplest to perform this procedure before performing the refresh procedure. After refreshing PC1, the operating system will be replaced. This replace procedure does not replace the operating system on PC1 but rather replaces PC1 with another computer, migrating users and settings from PC1 to the new computer.
In the replace procedure, PC1 will not be migrated to a new operating system. It is simplest to perform this procedure before performing the refresh procedure. After refreshing PC1, the operating system will be new. The next (replace) procedure does not install a new operating system on PC1 but rather performs a side-by-side migration of PC1 and another computer (PC4), to copy users and settings from PC1 to the new computer.
### Create a replace task sequence