locked
USMT with /vsc switch ignore unconditionalExclude patterns RRS feed

  • Question

  • Got a weird situation whereby I am excluding D: (and all other partitions other than C:) using a custom xml file. While testing, I was coming across some locked files, so I added /vsc and it seemed to continue. Once I fleshed out my ScanState.exe parameters, however, I could not exclude the contents of D:. Not until I removed /vsc anyway.

    After testing a few more times I found that /vsc seems to show similar behaviour to /localonly in that it will include all fixed drives regardless of what's specified in the xml files.

    Anyone seen this before? I have searched high and low and have not found any clues to why this is happening.

    <migration urlid=http://www.microsoft.com/migration/1.0/migxmlext/Custom>
         <component type="Documents" context="System">
             <displayName>Exclude D drive</displayName>
             <role role="Data">
                 <rules>
       <unconditionalExclude>
                         <objectSet>
           <pattern type="File">D:\*[*]</pattern>
                         </objectSet>
       </unconditionalExclude>
                 </rules>
             </role>
         </component>
     </migration>

    I had posted this in the Microsoft Assessment and Planning Toolkit Forum after misreading it as the Assessment and Deployment toolkit forum, but couldn't do anything about it. This seems to be a better place for it.
    Wednesday, May 20, 2015 8:44 AM

All replies

  • Maybe add a space between * [*] so it becomes :D:\* [*]

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, May 20, 2015 10:31 PM
  • The pattern itself works as I know it's not including the D drive when I leave off the /vsc switch. It's only when I add /vsc where it picks up the D drive. I tried it again with the space and it was showing the same behaviour though :s
    Saturday, May 23, 2015 5:30 AM
  • What version of USMT are you using?  What does your scanstate cmdline look like?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by Ty Glander Tuesday, May 26, 2015 5:40 PM
    Tuesday, May 26, 2015 5:40 PM
  • I take is you're using at least USMT 4  or above since you're using the Volume Shadow Copy switch. This is from the Common Issues section, see if it helps. You should have a USMTRestore.log in your log folder which could help you figure the problem out. That file can get pretty big but the exclusions should be listed near the beginning.

    Migration Problems

    Problem: Files that I specified to exclude are still being migrated.        

    Cause: There may be another rule that is including the files. If there is a more specific rule or a conflicting rule, the files will be included in the migration.

    Resolution: For more information see Conflicts and Precedence and the Diagnostic Log section in Log Files.

    https://technet.microsoft.com/en-us/library/dd560803(v=ws.10).aspx#Migration


    If this post is helpful please vote it as Helpful or click Mark for answer.

    • Proposed as answer by Ty Glander Tuesday, May 26, 2015 9:49 PM
    Tuesday, May 26, 2015 9:45 PM