Greetings,
In our company we run an XPSP3 system image onto desktops and laptops. On some of these machines the User Profile gets damaged, forcing Windows to load a new profile, or rather, a TEMP profile.
Recently I noticed that running Chkdsk /f on these computers, rendered a correction in the file system: "Correcting errors in the uppercase file". See also http://support.microsoft.com/kb/940830.
I have googled a bit and what seems to be a possible scenario is that the guys who do our image sysprep minipe, does it with a tool that creates the NTFS partition of the image with a tool (maybe FDISK) thats has a version higher than recommended. This makes sense since the image loads the W7 bootloader when in progress.
The question is whether there could be a relation between these disk errors and the frequent, but not overwhelming, creation of Temp profiles on some computers?
In our company we run an XPSP3 system image onto desktops and laptops. On some of these machines the User Profile gets damaged, forcing Windows to load a new profile, or rather, a TEMP profile.
Recently I noticed that running Chkdsk /f on these computers, rendered a correction in the file system: "Correcting errors in the uppercase file". See also http://support.microsoft.com/kb/940830.
I have googled a bit and what seems to be a possible scenario is that the guys who do our image sysprep minipe, does it with a tool that creates the NTFS partition of the image with a tool (maybe FDISK) thats has a version higher than recommended. This makes sense since the image loads the W7 bootloader when in progress.
The question is whether there could be a relation between these disk errors and the frequent, but not overwhelming, creation of Temp profiles on some computers?