RE: USMT issues with D Drive

We actually had this problem (similar anyway) and opened an incident with
microsoft. It turns out you need to set a working directory for the files to
decompress in otherwise it decompresses on the csidl_personal. They have
corrected this somewhat with the new version 2.6.1 but older versions of
office still cause this behavior. To set a working director you need to add
it to your loadstate syntax. I use this:

cd workingdir
md %computername%
cd %computername%
\\servername\sharename\usmt\bin\loadstate
\\servername\sharename\migration\%computername% /v:1


"eschloss" wrote:

> Our enterprise image in the past had 2 partitions, a C drive and a D drive.
> The new image we will be deploying has just a C drive. I have been testing
> the USMT 2.6 to migrate user data to the new machines.
> My setup is as follows:
> USMT files are at \\server\backup\USMT\bin
> data is backup up to \\server\backup\USMT\Data
> The scanstate runs. When loadstate runs, all data from the D drive of the
> old machine is left in a folder at \\server\backup\USMT\%csidl_personal% and
> never put on the local drive.
> I tried adding the following lines to my custom inf:
>
> [Copy This State]
> copyfiles=DDriveCopyFiles
>
> [DDriveCopyFiles]
> D:\*\*.doc, C:\D_Drive
>
> etc to add all of the desired file types. This does copy the data to
> c:\D_Drive, but I also end up with a duplicated folder structure from the D
> Drive. All folders are created, even if they are empty.
>