Update review date on reviewed articles

windows/deployment/usmt/getting-started-with-the-user-state-migration-tool.md

@@ -8,7 +8,7 @@ ms.service: windows-client
 author: frankroj
 ms.topic: conceptual
 ms.subservice: itpro-deploy
-ms.date: 08/30/2024
+ms.date: 01/29/2025
 appliesto:
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>

windows/deployment/usmt/migrate-application-settings.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 08/30/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/migration-store-types-overview.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/offline-migration-reference.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -50,7 +50,7 @@ For exceptions to what can be migrated offline, see [What Does USMT Migrate?](us
 
 ## What offline environments are supported?
 
-All currently supported 
+All currently supported
 
 The following table defines the supported combination of online and offline operating systems in USMT.
 
@@ -183,9 +183,9 @@ The following XML example illustrates some of the elements discussed earlier in
 ```xml
 <offline>
      <winDir>
-          <path>C:\Windows</path> 
+          <path>C:\Windows</path>
-          <path>D:\Windows</path> 
+          <path>D:\Windows</path>
-          <path>E:\</path> 
+          <path>E:\</path>
      </winDir>
      <failOnMultipleWinDir>1</failOnMultipleWinDir>
 </offline>

windows/deployment/usmt/understanding-migration-xml-files.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-best-practices.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-choose-migration-store-type.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-command-line-syntax.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

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

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-configxml-file.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -496,7 +496,7 @@ The following sample `Config.xml` file contains detailed examples about items th
               </changeGroup>
             </mappings>
           </localGroups>
-          
+
       -->
   </ProfileControl>
 </Configuration>

windows/deployment/usmt/usmt-conflicts-and-precedence.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -79,7 +79,7 @@ Specifying `migrate="no"` in the `Config.xml` file is the same as deleting the c
    <objectSet>
       <pattern type="File">%CSIDL_PERSONAL%\* [*.doc] </pattern>
    </objectSet>
-</include> 
+</include>
 ```
 
 ### How does USMT process each component in an .xml file with multiple components?
@@ -116,7 +116,7 @@ In the following example, mp3 files aren't excluded from the migration. The mp3
      <objectSet>
           <pattern type="File"> C:\* [*.mp3]</pattern>
      </objectSet>
-</exclude>  
+</exclude>
 ```
 
 ### \<include\> and \<exclude\> rules precedence examples
@@ -185,11 +185,11 @@ The destination computer contains the following files:
 A custom **.xml** file contains the following code:
 
 ```xml
-<include> 
+<include>
-   <objectSet> 
+   <objectSet>
-      <pattern type="File">c:\data\* [*]</pattern> 
+      <pattern type="File">c:\data\* [*]</pattern>
-   </objectSet> 
+   </objectSet>
-</include> 
+</include>
 ```
 
 For this example, the following information describes the resulting behavior if the code is added to the custom **.xml** file.

windows/deployment/usmt/usmt-custom-xml-examples.md

@@ -8,7 +8,7 @@ ms.service: windows-client
 author: frankroj
 ms.topic: conceptual
 ms.subservice: itpro-deploy
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 appliesto:
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
@@ -120,7 +120,7 @@ The following sample is a custom **.xml** file named `CustomFile.xml` that migra
 <component type="Documents" context="User">
         <displayName>My Video</displayName>
         <role role="Data">
-            <detects>           
+            <detects>
                 <detect>
                     <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_MYVIDEO%")</condition>
                 </detect>
@@ -251,8 +251,8 @@ The behavior for this custom **.xml** file is described within the `<displayName
     <rules>
          <include>
             <objectSet>
-                 <script>MigXmlHelper.GenerateDrivePatterns ("\Requests\* [*] ", "Fixed")</script>            
+                 <script>MigXmlHelper.GenerateDrivePatterns ("\Requests\* [*] ", "Fixed")</script>
-                 <script>MigXmlHelper.GenerateDrivePatterns ("*\Requests\* [*] ", "Fixed")</script>            
+                 <script>MigXmlHelper.GenerateDrivePatterns ("*\Requests\* [*] ", "Fixed")</script>
             </objectSet>
           </include>
     </rules>
@@ -264,7 +264,7 @@ The behavior for this custom **.xml** file is described within the `<displayName
   <role role="Data">
     <rules>
          <include>
-            <objectSet>                 
+            <objectSet>
                  <pattern type="File"> C:\*\Presentations\* [*]</pattern>
                  <pattern type="File"> C:\Presentations\* [*]</pattern>
            </objectSet>

windows/deployment/usmt/usmt-customize-xml-files.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-determine-what-to-migrate.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-estimate-migration-store-size.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-exclude-files-and-settings.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-extract-files-from-a-compressed-migration-store.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-faq.yml

@@ -11,12 +11,12 @@ metadata:
   ms.mktglfcycl: deploy
   ms.sitesec: library
   audience: itpro
-  ms.date: 01/09/2024
+  ms.date: 01/29/2025
   ms.topic: faq
 title: Frequently Asked Questions
 summary: |
   **Applies to:**
-  
+
   - Windows 11
   - Windows 10
 
@@ -30,13 +30,13 @@ sections:
           How much space is needed on the destination computer?
         answer: |
           The destination computer needs enough available space for the following items:
-          
+
           -   Operating system
-          
+
           -   Applications
-          
+
           -   Uncompressed store
-          
+
       - question: |
           Can the files and settings be stored directly on the destination computer or is a server needed?
         answer: |
@@ -47,13 +47,13 @@ sections:
           - Directly on the destination computer.
 
           To store it directly on the destination computer:
-          
+
           1.  Create and share the directory `C:\store` on the destination computer.
-          
+
           1.  Run the **ScanState** tool on the source computer and save the files and settings to `\\<DestinationComputerName>\store`
-          
+
           1.  Run the **LoadState** tool on the destination computer and specify `C:\store` as the store location.
-          
+
       - question: |
           Can data be migrated between operating systems with different languages?
         answer: |
@@ -80,7 +80,7 @@ sections:
           How can a folder or a certain type of file be excluded from the migration?
         answer: |
           The **\<unconditionalExclude\>** element can be used to globally exclude data from the migration. For example, this element can be used to exclude all MP3 files on the computer or to exclude all files from `C:\UserData`. This element excludes objects regardless of any other **\<include\>** rules that are in the **.xml** files. For an example, see **\<unconditionalExclude\>** in the [Exclude files and settings](usmt-exclude-files-and-settings.md) article. For the syntax of this element, see [XML elements library](usmt-xml-elements-library.md).
-          
+
       - question: |
           What happens to files that were located on a drive that don't exist on the destination computer?
         answer: |
@@ -91,22 +91,22 @@ sections:
           - C:\\ is the system drive on the destination computer.
 
           the file is migrated to `C:\data\File.pst`. This behavior holds true even when **\<locationModify\>** rules attempt to move data to a drive that doesn't exist on the destination computer.
-          
+
   - name: USMT .xml Files
     questions:
       - question: |
           Where are there examples of USMT **.xml** files?
         answer: |
           The following articles include examples of USMT **.xml** files:
-          
+
           -   [Exclude files and settings](usmt-exclude-files-and-settings.md)
-          
+
           -   [Reroute files and settings](usmt-reroute-files-and-settings.md)
-          
+
           -   [Include files and settings](usmt-include-files-and-settings.md)
-          
+
           -   [Custom XML examples](usmt-custom-xml-examples.md)
-          
+
       - question: |
           Can custom **.xml** files that were written for USMT 5.0 be used?
         answer: |
@@ -121,9 +121,9 @@ sections:
           Why must the **.xml** files be included with both the `ScanState.exe` and `LoadState.exe` commands?
         answer: |
           The **.xml** files aren't copied to the store as in previous versions of USMT. Because the **ScanState** and **LoadState** tools need the **.xml** files to control the migration, the same set of **.xml** files must be specified for the `ScanState.exe` and `LoadState.exe` commands. If a particular set of mig\*.xml files were used in the **ScanState** tool, either called through the `/auto` option, or individually through the `/i` option, then the same option should be used to call the exact same mig\*.xml files in the **LoadState** tool. However, the `Config.xml` file doesn't need to be specified, unless files and settings that were migrated to the store need to be excluded. For example, the **Documents** folder might be migrated to the store, but not to the destination computer. To do this type of migration, modify the `Config.xml` file and specify the updated file with the `LoadState.exe` command. **LoadState** migrates only the desired files and settings.
-          
+
           If an **.xml** file is excluded from the `LoadState.exe` command, then all of the data in the store that was migrated with the missing **.xml** files are migrated. However, the migration rules that were specified for the `ScanState.exe` command don't apply. For example, if a `MigApp.xml` file that has a rerouting rule such as `MigsysHelperFunction.RelativeMove("c:\data", "%CSIDL_PERSONAL%")` is excluded, USMT doesn't reroute the files. Instead, it migrates them to `C:\data`.
-          
+
       - question: |
           Which files can be modified and specified on the command line?
         answer: |
@@ -133,20 +133,20 @@ sections:
           What happens if the **.xml** files aren't specified on the command line?
         answer: |
           -   **ScanState**
-          
+
               If no files are specified with the `ScanState.exe` command, all user accounts and default operating system components are migrated.
-          
+
           -   **LoadState**
-          
+
               If no files are specified with the `LoadState.exe` command, all data that is in the store is migrated. However, any target-specific migration rules that were specified in **.xml** files with the `ScanState.exe` command doesn't apply. For example, if a `MigApp.xml` file that has a rerouting rule such as `MigsysHelperFunction.RelativeMove("c:\data", "%CSIDL_PERSONAL%")` is excluded, USMT doesn't reroute the files. Instead, it migrates them to `C:\data`.
-          
+
   - name: Conflicts and Precedence
     questions:
       - question: |
           What happens when there are conflicting XML rules or conflicting objects on the destination computer?
         answer: |
           For more information, see [Conflicts and precedence](usmt-conflicts-and-precedence.md).
-          
+
 
 additionalContent: |
 

windows/deployment/usmt/usmt-general-conventions.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -73,21 +73,21 @@ The XML helper functions in the [XML elements library](usmt-xml-elements-library
  The encoded location is composed of the node part, optionally followed by the leaf enclosed in square brackets. This format makes a clear distinction between nodes and leaves.
 
   For example, specify the file
-  
+
   `C:\Windows\Notepad.exe`
-  
+
   as
-  
+
   **c:\\Windows\[Notepad.exe\]**
-  
+
   Similarly, specify the directory
-  
+
   `C:\Windows\System32`
-  
+
   as
-  
+
   **c:\\Windows\\System32**
-  
+
   Note the absence of the **\[\]** characters in second example.
 
   The registry is represented in a similar way. The default value of a registry key is represented as an empty **\[\]** construct. For example, the default value for the `HKLM\SOFTWARE\MyKey` registry key is **HKLM\\SOFTWARE\\MyKey\[\]**.

windows/deployment/usmt/usmt-hard-link-migration-store.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-how-it-works.md

@@ -8,7 +8,7 @@ ms.service: windows-client
 author: frankroj
 ms.topic: conceptual
 ms.subservice: itpro-deploy
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 appliesto:
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
@@ -33,7 +33,7 @@ When the **ScanState** tool runs on the source computer, it goes through the fol
     There are three types of components:
 
     - Components that migrate the operating system settings.
-  
+
     - Components that migrate application settings.
 
     - Components that migrate users' files.

windows/deployment/usmt/usmt-how-to.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-identify-application-settings.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-identify-file-types-files-and-folders.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-identify-operating-system-settings.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-identify-users.md

@@ -9,7 +9,7 @@ author: frankroj
 ms.topic: conceptual
 ms.localizationpriority: medium
 ms.subservice: itpro-deploy
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 appliesto:
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
   - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>

windows/deployment/usmt/usmt-include-files-and-settings.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -25,12 +25,12 @@ The following **.xml** file migrates a single registry key.
 ```xml
 <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
      <component type="Application" context="System">
-          <displayName>Component to migrate only registry value string</displayName> 
+          <displayName>Component to migrate only registry value string</displayName>
           <role role="Settings">
           <rules>
                <include>
                     <objectSet>
-                         <pattern type="Registry">HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Cache [Persistent]</pattern> 
+                         <pattern type="Registry">HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Cache [Persistent]</pattern>
                     </objectSet>
                </include>
           </rules>
@@ -95,8 +95,8 @@ The following **.xml** file migrates all files and subfolders of the `Engineerin
     <rules>
          <include>
             <objectSet>
-         <script>MigXmlHelper.GenerateDrivePatterns ("\EngineeringDrafts\* [*] ", "Fixed")</script>            
+         <script>MigXmlHelper.GenerateDrivePatterns ("\EngineeringDrafts\* [*] ", "Fixed")</script>
-         <script>MigXmlHelper.GenerateDrivePatterns ("*\EngineeringDrafts\* [*] ", "Fixed")</script>            
+         <script>MigXmlHelper.GenerateDrivePatterns ("*\EngineeringDrafts\* [*] ", "Fixed")</script>
        </objectSet>
           </include>
     </rules>
@@ -114,7 +114,7 @@ The following **.xml** file migrates all files and subfolders of the `Engineerin
   <role role="Data">
     <rules>
          <include>
-            <objectSet>                 
+            <objectSet>
 <pattern type="File"> C:\*\EngineeringDrafts\* [*]</pattern>
 <pattern type="File"> C:\EngineeringDrafts\* [*]</pattern>
        </objectSet>
@@ -149,7 +149,7 @@ The following **.xml** file migrates `.mp3` files located in the specified drive
     </rules>
   </role>
 </component>
-</migration> 
+</migration>
 ```
 
 ## Migrate a specific file

windows/deployment/usmt/usmt-loadstate-syntax.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 04/30/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-log-files.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-migrate-efs-files-and-certificates.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-migrate-user-accounts.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-migration-store-encryption.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-overview.md

@@ -7,7 +7,7 @@ author: frankroj
 ms.reviewer: kevinmi,warrenw
 manager: aaroncz
 ms.author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: overview
 ms.collection:
   - highpri

windows/deployment/usmt/usmt-plan-your-migration.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-recognized-environment-variables.md

@@ -7,7 +7,7 @@ ms.reviewer: kevinmi,warrenw
 manager: aaroncz
 ms.author: frankroj
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.collection:
   - highpri

windows/deployment/usmt/usmt-reference.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-requirements.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 04/30/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-reroute-files-and-settings.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -70,7 +70,7 @@ The following custom **.xml** file reroutes **.mp3** files located in the fixed
     </rules>
   </role>
 </component>
-</migration> 
+</migration>
 ```
 
 ## Reroute a specific file
@@ -83,8 +83,8 @@ The following custom **.xml** file migrates the `Sample.doc` file from `C:\Engin
 <displayName>Sample.doc into the Documents folder</displayName>
     <role role="Data">
       <rules>
-        <include> 
+        <include>
-          <objectSet>     
+          <objectSet>
                  <pattern type="File"> C:\EngineeringDrafts\ [Sample.doc]</pattern>
           </objectSet>
         </include>

windows/deployment/usmt/usmt-resources.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -23,7 +23,7 @@ appliesto:
 - Microsoft Visual Studio
 
   - The User State Migration Tool (USMT) XML schema (the `MigXML.xsd` file) can be used to validate the migration **.xml** files using an XML authoring tool such as Microsoft Visual Studio.
-  
+
     For more information about how to use the schema with an XML authoring environment, see the environment's documentation.
 
 - [Ask the Directory Services Team blog](https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/bg-p/AskDS).

windows/deployment/usmt/usmt-scanstate-syntax.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 04/30/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-technical-reference.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-test-your-migration.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-topics.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-troubleshooting.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-utilities.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-what-does-usmt-migrate.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/18/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/usmt-xml-elements-library.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:
@@ -95,7 +95,7 @@ The following example is from the `MigApp.xml` file:
    <location type="Registry">%HklmWowSoftware%\Microsoft\Office\16.0\Common\Migration\Office [Lang]</location>
    <attributes>DWORD</attributes>
    <bytes>00000000</bytes>
-</object> 
+</object>
 ```
 
 ## \<bytes\>
@@ -127,7 +127,7 @@ The following example is from the `MigApp.xml` file:
    <location type="Registry">%HklmWowSoftware%\Microsoft\Office\16.0\Common\Migration\Office [Lang]</location>
    <attributes>DWORD</attributes>
    <bytes>00000000</bytes>
-</object> 
+</object>
 ```
 
 ## \<commandLine\>
@@ -1070,10 +1070,10 @@ Example:
                </externalProcess>
          </rules>
    </role>
-<!-- Migrate 
+<!-- Migrate
    all doc files from the system
    all power point files
-   all visio design files 
+   all visio design files
    all my c++ program files -->
    <extensions>
       <extension>DOC</extension>
@@ -1126,18 +1126,18 @@ Syntax:
 For example, to migrate all \*.doc files from the source computer, specifying the following code under the **\<component\>** element:
 
 ```xml
-<extensions> 
+<extensions>
-        <extension>doc</extension> 
+        <extension>doc</extension>
-<extensions> 
+<extensions>
 ```
 
 is the same as specifying the following code below the **\<rules\>** element:
 
 ```xml
-<include> 
+<include>
-        <objectSet> 
+        <objectSet>
-                <script>MigXmlHelper.GenerateDrivePatterns ("* [*.doc]", "Fixed")</script> 
+                <script>MigXmlHelper.GenerateDrivePatterns ("* [*.doc]", "Fixed")</script>
-        </objectSet> 
+        </objectSet>
 </include>
 ```
 
@@ -1202,7 +1202,7 @@ The following example is from the `MigUser.xml` file:
          <path type="File">%CSIDL_MYVIDEO%</path>
       </paths>
       <role role="Data">
-         <detects>           
+         <detects>
             <detect>
                <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_MYVIDEO%")</condition>
             </detect>
@@ -1702,11 +1702,11 @@ The following example is from the `MigUser.xml` file:
          <path type="File">%CSIDL_MYMUSIC%</path>
       </paths>
    <role role="Data">
-      <detects>           
+      <detects>
       <detect>
          <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_MYMUSIC%")</condition>
       </detect>
-   </detects>           
+   </detects>
    <rules>
       <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
          <objectSet>
@@ -1846,11 +1846,11 @@ The following example is from the `MigUser.xml` file. For more examples, see the
       <path type="File">%CSIDL_STARTMENU%</path>
    </paths>
    <role role="Settings">
-      <detects>           
+      <detects>
          <detect>
             <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_STARTMENU%")</condition>
          </detect>
-      </detects>           
+      </detects>
    <rules>
       <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
          <objectSet>
@@ -1901,11 +1901,11 @@ The following example is from the `MigUser.xml` file:
          <path type="File">%CSIDL_MYMUSIC%</path>
       </paths>
    <role role="Data">
-      <detects>           
+      <detects>
       <detect>
          <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_MYMUSIC%")</condition>
       </detect>
-   </detects>           
+   </detects>
    <rules>
       <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'>
          <objectSet>
@@ -1969,7 +1969,7 @@ Examples:
 To migrate the Sample.doc file from any drive on the source computer, use **\<script\>** as follows. If multiple files exist with the same name, all such files get migrated.
 
 ```xml
-<script>MigXmlHelper.GenerateDrivePatterns("* [sample.doc]", "Fixed")</script> 
+<script>MigXmlHelper.GenerateDrivePatterns("* [sample.doc]", "Fixed")</script>
 ```
 
 For more examples of how to use this element, see [Exclude Files and Settings](usmt-exclude-files-and-settings.md), [Reroute Files and Settings](usmt-reroute-files-and-settings.md), and [Custom XML Examples](usmt-custom-xml-examples.md).
@@ -2171,7 +2171,7 @@ For example:
 
 ```xml
 <variable name="QuickTime5or6DataSys">
-  <text>%CSIDL_COMMON_APPDATA%\QuickTime</text> 
+  <text>%CSIDL_COMMON_APPDATA%\QuickTime</text>
 </variable>
 ```
 
@@ -2204,7 +2204,7 @@ The following **.xml** file excludes all `.mp3` files from migration. For additi
              <unconditionalExclude>
                         <objectSet>
     <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mp3]", "Fixed")</script>
-                        </objectSet> 
+                        </objectSet>
              </unconditionalExclude>
             </rules>
         </role>

windows/deployment/usmt/usmt-xml-reference.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/verify-the-condition-of-a-compressed-migration-store.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto:

windows/deployment/usmt/xml-file-requirements.md

@@ -6,7 +6,7 @@ manager: aaroncz
 ms.author: frankroj
 ms.service: windows-client
 author: frankroj
-ms.date: 01/09/2024
+ms.date: 01/29/2025
 ms.topic: conceptual
 ms.subservice: itpro-deploy
 appliesto: