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.

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

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