I use SCCM 2007 and USMT4 to manage our Windows 7 SP1 x64 machines. The build is changing to a single partition (C:\) instead of a C and D drive. When a current machine is rebuilt I have been asked to move all files/folders (with some exceptions) to a new folder on the C drive called C:\Migrated_Data.
I can successfully exclude folders from both the C and D partitions and move the data to the C:\Migrated_Data folder. However, the Migrated_Data folder is created with System and Hidden permissions set. Unless these permissions are removed (attrib -s -h) the folder would not be visible to users.
I would like to understand why USMT is doing this but after a few days of searching I cannot find an answer to this problem. I could run the attrib -s -h c:\Migrated_Data command within an OSD task sequence step but I would prefer to stop USMT creating the root folder with these permissions.
All subsequent folders are not set to hidden.
I use the standard MigApp.xml and MigDocs.xml (which I have customised ---- see below) and a custom XML file to migrate application data for the CAD packages we use. I have tried recreating the config.xml (scanstate.exe /genconfig:config.xml) but that has made no difference.
Any help / pointers you could provide would be greatly appreciated.
<?xml version="1.0" encoding="UTF-8"?>
-<migrationurlid="http://www.microsoft.com/migration/1.0/migxmlext/migdocs"><!-- This component migrates data in system context -->
-<componentcontext="System"type="Documents"><displayName>MigDocSystem</displayName>
-<rolerole="Data">
-<rules><!-- GenerateDocPatterns takes 3 arguments 1. generate patterns for scattered files inside %ProgramFiles% 2. generate include patterns (FALSE generates exclude patterns) 3. generate patterns for system drive only -->
-<excludefilter="MigXmlHelper.IgnoreIrrelevantLinks()">
-<objectSet><script>MigXmlHelper.GenerateDocPatterns("FALSE","FALSE","FALSE")</script></objectSet></exclude><!-- Example: <exclude> <objectSet> <pattern type="File">%CSIDL_COMMON_VIDEO%\* [*]</pattern> </objectSet> </exclude> -->
-<contentModifyscript="MigXmlHelper.MergeShellLibraries('TRUE','TRUE')">
-<objectSet><patterntype="File">* [*.library-ms]</pattern></objectSet></contentModify>
-<mergescript="MigXmlHelper.SourcePriority()">
-<objectSet><patterntype="File">* [*.library-ms]</pattern></objectSet></merge>
-<include>
-<objectSet><script>MigXmlHelper.GenerateDocPatterns('false','true','false')</script></objectSet></include>
-<unconditionalExclude>
-<objectSet><patterntype="File">D:\EVARCHIVE\* [*]</pattern><patterntype="File">C:\EVARCHIVE\* [*]</pattern><patterntype="File">C:\DrvInst\* [*]</pattern><patterntype="File">D:\_SMSTaskSequence\* [*]</pattern><patterntype="File">C:\_SMSTaskSequence\* [*]</pattern><patterntype="File">C:\Oracle\* [*]</pattern><patterntype="File">C:\ThinInst\* [*]</pattern><patterntype="File">C:\Intel\* [*]</pattern><patterntype="File">C:\PerfLogs\* [*]</pattern><patterntype="File">C:\Support\* [*]</pattern><patterntype="File">C:\SWTOOLS\* [*]</pattern></objectSet></unconditionalExclude></rules></role></component><!-- This component migrates data in user context -->
-<componentcontext="User"type="Documents"><displayName>MigDocUser</displayName>
-<rolerole="Data">
-<rules>
-<excludefilter="MigXmlHelper.IgnoreIrrelevantLinks()">
-<objectSet><script>MigXmlHelper.GenerateDocPatterns("FALSE","FALSE","FALSE")</script></objectSet></exclude><!-- Example: <exclude> <objectSet> <pattern type="File">%CSIDL_MYVIDEO%\* [*]</pattern> </objectSet> </exclude> -->
-<contentModifyscript="MigXmlHelper.MergeShellLibraries('TRUE','TRUE')">
-<objectSet><patterntype="File">* [*.library-ms]</pattern></objectSet></contentModify>
-<mergescript="MigXmlHelper.SourcePriority()">
-<objectSet><patterntype="File">* [*.library-ms]</pattern></objectSet></merge>
-<include>
-<objectSet><script>MigXmlHelper.GenerateDocPatterns('false','true','false')</script><patterntype="File">D:\* [*]</pattern></objectSet></include>
-<locationModifyscript="MigXmlHelper.Move('C:\Migrated_Data')">
-<objectSet><patterntype="File">D:\* [*]</pattern></objectSet></locationModify>
-<unconditionalExclude>
-<objectSet><patterntype="File">D:\EVARCHIVE\* [*]</pattern></objectSet></unconditionalExclude></rules></role></component></migration>
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi,
I use SCCM 2007 and USMT4 to manage our Windows 7 SP1 x64 machines. The build is changing to a single partition (C:\) instead of a C and D drive. When a current machine is rebuilt I have been asked to move all files/folders (with some exceptions) to a new folder on the C drive called C:\Migrated_Data.
I can successfully exclude folders from both the C and D partitions and move the data to the C:\Migrated_Data folder. However, the Migrated_Data folder is created with System and Hidden permissions set. Unless these permissions are removed (attrib -s -h) the folder would not be visible to users.
I would like to understand why USMT is doing this but after a few days of searching I cannot find an answer to this problem. I could run the attrib -s -h c:\Migrated_Data command within an OSD task sequence step but I would prefer to stop USMT creating the root folder with these permissions.
All subsequent folders are not set to hidden.
I use the standard MigApp.xml and MigDocs.xml (which I have customised ---- see below) and a custom XML file to migrate application data for the CAD packages we use. I have tried recreating the config.xml (scanstate.exe /genconfig:config.xml) but that has made no difference.
Any help / pointers you could provide would be greatly appreciated.
Share this post
Link to post
Share on other sites