Systems Deployment Question
USMT 4.0 on K2 Scan Captures C and D partitions
I'm not new to the K2 but I am new to USMT. I decided to start using USMT to capture user profiles so that I can then deploy an image to a new machine and have the user's profile deployed along with it as documented in K2 documentation.
The problem I experienced is that I noticed upon capturing the user profile that it was 8GB in size. I looked at the source workstation and the profile is only 3.6MB in size. I captured this from a Windows 7 machine and deployed it to another Windows 7 machine. When I finished the deployment and checked the machine I noticed right away what it did.
It captured the majority of the D partition on the source machine which has lots of data that I didn't specify or want captured. I selected the option to scan all profiles and exclude everything but the user profile that I wanted. That part worked fine, but on top of capturing the user profile from the C partition it also captured the D partition.
How can this be prevented?