Metadata update deployment/usmt 11

windows/deployment/usmt/usmt-common-migration-scenarios.md

@@ -27,31 +27,31 @@ The following diagram shows a PC-refresh migration, also known as a computer ref
 
 A company has received funds to update the operating system on all of its computers in the accounting department to Windows 10. Each employee will keep the same computer, but the operating system on each computer will be updated. In this scenario, the update is being handled offline, without a network connection. An administrator uses Windows Preinstallation Environment (WinPE) and a hard-link migration store to save each user state to their respective computer.
 
-1. On each computer, the administrator boots the machine into WinPE and runs the ScanState command-line tool, specifying the `/hardlink /nocompress` command-line options. ScanState saves the user state to a hard-link migration store on each computer, improving performance by minimizing network traffic and minimizing migration failures on computers with limited space available on the hard drive.
+1. On each computer, the administrator boots the machine into WinPE and runs the **ScanState** command-line tool, specifying the `/hardlink /nocompress` command-line options. **ScanState** saves the user state to a hard-link migration store on each computer, improving performance by minimizing network traffic and minimizing migration failures on computers with limited space available on the hard drive.
 
 2. On each computer, the administrator installs the company's standard operating environment (SOE) which includes Windows 10 and other company applications.
 
-3. The administrator runs the LoadState command-line tool on each computer. LoadState restores each user state back to each computer.
+3. The administrator runs the **LoadState** command-line tool on each computer. **LoadState** restores each user state back to each computer.
 
 ### Scenario Two: PC-refresh using a compressed migration store
 
 A company has received funds to update the operating system on all of its computers to Windows 10. Each employee will keep the same computer, but the operating system on each computer will be updated. In this scenario, an administrator uses a compressed migration store to save the user states to a server.
 
-1. The administrator runs the ScanState command-line tool on each computer. ScanState saves each user state to a server.
+1. The administrator runs the **ScanState** command-line tool on each computer. **ScanState** saves each user state to a server.
 
 2. On each computer, the administrator installs the company's standard SOE that includes Windows 10 and other company applications.
 
-3. The administrator runs the LoadState command-line tool on each source computer, and LoadState restores each user state back to the computer.
+3. The administrator runs the **LoadState** command-line tool on each source computer, and **LoadState** restores each user state back to the computer.
 
 ### Scenario Three: PC-refresh using a hard-link migration store
 
 A company has received funds to update the operating system on all of its computers to Windows 10. Each employee will keep the same computer, but the operating system on each computer will be updated. In this scenario, an administrator uses a hard-link migration store to save each user state to their respective computer.
 
-1. The administrator runs the ScanState command-line tool on each computer, specifying the `/hardlink /nocompress` command-line options. ScanState saves the user state to a hard-link migration store on each computer, improving performance by minimizing network traffic and minimizing migration failures on computers with limited space available on the hard drive.
+1. The administrator runs the **ScanState** command-line tool on each computer, specifying the `/hardlink /nocompress` command-line options. **ScanState** saves the user state to a hard-link migration store on each computer, improving performance by minimizing network traffic and minimizing migration failures on computers with limited space available on the hard drive.
 
 2. On each computer, the administrator installs the company's SOE that includes Windows 10 and other company applications.
 
-3. The administrator runs the LoadState command-line tool on each computer. LoadState restores each user state back on each computer.
+3. The administrator runs the **LoadState** command-line tool on each computer. **LoadState** restores each user state back on each computer.
 
 ### Scenario Four: PC-refresh using Windows.old folder and a hard-link migration store
 
@@ -61,7 +61,7 @@ A company has decided to update the operating system on all of its computers to
 
 2. On each computer, the administrator installs the company's SOE that includes company applications.
 
-3. The administrator runs the ScanState and LoadState command-line tools successively on each computer while specifying the `/hardlink /nocompress` command-line options.
+3. The administrator runs the **ScanState** and **LoadState** command-line tools successively on each computer while specifying the `/hardlink /nocompress` command-line options.
 
 ## PC-replacement
 
@@ -73,33 +73,33 @@ The following diagram shows a PC-replacement migration. First, the administrator
 
 A company is allocating 20 new computers to users in the accounting department. The users each have a source computer with their files and settings. In this scenario, migration is being handled offline, without a network connection.
 
-1. On each source computer, an administrator boots the machine into WinPE and runs ScanState to collect the user state to either a server or an external hard disk.
+1. On each source computer, an administrator boots the machine into WinPE and runs **ScanState** to collect the user state to either a server or an external hard disk.
 
 2. On each new computer, the administrator installs the company's SOE that includes Windows 10 and other company applications.
 
-3. On each of the new computers, the administrator runs the LoadState tool, restoring each user state from the migration store to one of the new computers.
+3. On each of the new computers, the administrator runs the **LoadState** tool, restoring each user state from the migration store to one of the new computers.
 
 ### Scenario Two: Manual network migration
 
-A company receives 50 new laptops for their managers and needs to reallocate 50 older laptops to new employees. In this scenario, an administrator runs the ScanState tool from the cmd prompt on each computer to collect the user states and save them to a server in a compressed migration store.
+A company receives 50 new laptops for their managers and needs to reallocate 50 older laptops to new employees. In this scenario, an administrator runs the **ScanState** tool from the cmd prompt on each computer to collect the user states and save them to a server in a compressed migration store.
 
-1. The administrator runs the ScanState tool on each of the manager's old laptops, and saves each user state to a server.
+1. The administrator runs the **ScanState** tool on each of the manager's old laptops, and saves each user state to a server.
 
 2. On the new laptops, the administrator installs the company's SOE, which includes Windows 10 and other company applications.
 
-3. The administrator runs the LoadState tool on the new laptops to migrate the managers' user states to the appropriate computer. The new laptops are now ready for the managers to use.
+3. The administrator runs the **LoadState** tool on the new laptops to migrate the managers' user states to the appropriate computer. The new laptops are now ready for the managers to use.
 
 4. On the old computers, the administrator installs the company's SOE, which includes Windows 10, Microsoft Office, and other company applications. The old computers are now ready for the new employees to use.
 
 ### Scenario Three: Managed network migration
 
-A company is allocating 20 new computers to users in the accounting department. The users each have a source computer that contains their files and settings. An administrator uses a management technology such as a sign-in script or a batch file to run ScanState on each source computer to collect the user states and save them to a server in a compressed migration store.
+A company is allocating 20 new computers to users in the accounting department. The users each have a source computer that contains their files and settings. An administrator uses a management technology such as a sign-in script or a batch file to run **ScanState** on each source computer to collect the user states and save them to a server in a compressed migration store.
 
-1. On each source computer, the administrator runs the ScanState tool using Microsoft Configuration Manager, Microsoft Deployment Toolkit (MDT), a sign-in script, a batch file, or a non-Microsoft management technology. ScanState collects the user state from each source computer and then saves it to a server.
+1. On each source computer, the administrator runs the **ScanState** tool using Microsoft Configuration Manager, Microsoft Deployment Toolkit (MDT), a sign-in script, a batch file, or a non-Microsoft management technology. **ScanState** collects the user state from each source computer and then saves it to a server.
 
 2. On each new computer, the administrator installs the company's SOE, which includes Windows 10 and other company applications.
 
-3. On each of the new computers, the administrator runs the LoadState tool using Microsoft Configuration Manager, a sign-in script, a batch file, or a non-Microsoft management technology. LoadState migrates each user state from the migration store to one of the new computers.
+3. On each of the new computers, the administrator runs the **LoadState** tool using Microsoft Configuration Manager, a sign-in script, a batch file, or a non-Microsoft management technology. **LoadState** migrates each user state from the migration store to one of the new computers.
 
 ## Related articles