migrating dual partitions (XP Pro SP3) to a single partition (Win

[ob1andonly]

Hi All,

We are attempting to migrate machines with a dual partition setup (C: and
D:) running XP Pro SP3 to a single partition setup (C:) running Win 7
Enterprise. The user's shell folders have been redirected to the D:
partition via login script during first time login (not via GP). Therefore,
the My Documents folder on a given XP machine would look like this:
D:\data\username\My Documents.

The problem we are experiencing is the duplication of these shell folders
upon running loadstate on the destination machine. Cookies, Desktop,
Favorites, and My Documents are all being transferred to the correct location
in Win 7, but are also being dropped into the C:\data\username location as
well. So, on the new machine, we would see C:\data\username\Cookies,
C:\data\username\Desktop, etc. for each user even though the files are
already in the correct location.

Is there a way to prevent this?

I tried folder redirection to no avail and I didn't glean much information
from the logs. Below are my scanstate and loadstate commands.

scanstate \\server\sharetest /i:migapp.xml /i:miguser.xml
/i:ExcludeFoldersCertificates.xml /config:config.xml /o /v:5
/listfiles:\\server\share\test\USMT_Logs\%computername%-FileTransferList.txt
/l:\\server\share\test\USMT_Logs\%computername% /c /r:3 /w:15
/ue:%computername%\* /localonly

loadstate \\server\share\test /i:migapp.xml /i:miguser.xml
/i:ExcludeFoldersCertificates.xml /config:config.xml /v:5
/l:\\server\share\test\USMT_Logs\%computername% /c /r:3 /w:15
/ue:%computername%\*

Thanks,

[ob1andonly]

FYI - I am using USMT 4.0

[JR--]

So the issue is the files on D:\ are also getting migrated by some other
component -

likely this component

<!-- This component migrates user files with known extension-->
<component type="Documents" context="System">
<displayName _locID="miguser.userdata">User Data</displayName>

a few ways to workaround this - one change is to remove the
generateDrivepatterns helper function - and replace with a more specific rule

<script>MigXmlHelper.GenerateDrivePatterns ("*
[*.qdf]", "Fixed")</script>

<pattern type="File">C:\* [*.qdf]</pattern>

Or

In this component there is already an exclude section - just add a more
specific rule - maybe something like

D:\data\* [*]

[ob1andonly]

Thanks a lot, JR. I tried the first workaround you suggested and it works
perfectly!

Cheers,

[jimc84]

Guys, I have a very similar issue but i can't remove the
generateDrivepatterns helper function as i want to target all Documents that
may be located on both partitions outside of the Profile directories
(Desktop, My Documents etc.). So, i tried the other option you suggested,
adding an exclude rule for the folder in question but to no avail, it still
created that folder on the C:\ drive. Any other ideas??

[JR--]

Hey Jim -

sorry for delay -

enable diagnostic logging -
ex.
SET MIG_ENABLE_DIAG=gather.txt

Then run your gather - once complete search the gather.txt log for the file
or folder in question - find the name of the Component that is moving this
file or folder - also take note of the migration rule that moves it - from
here you should be able to modify the rules to stop it from moving - if not
post the rule you see in the log and we can give you something

Oh - this component name should match what you have in your xml rules -