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.
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