I was deploying Windows 7 (XP to 7 upgrade with hardlinking USMT) on machine with 2 physical drives. It was the first machine with 2 physical drives we deployed OS with SCCM on.
The OS image was applied to the wrong physical drive and as you may guess, caused data loss of that employee.
After trying to reproduce the situation, what i've seen was that after the machine boots to WinPE, it decides to switch by himself between the drives.
The first HDD becomes second, and the second first, and that way the image was applied to the wrong destination.
In TS the apply image is set to apply the image to the first available partition.
Is there any way to prevent this kind of behavior other than specifying the image to be applied to specific disk and partition? (Haven't tried that tho if it matters).
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.
I had very unpleasant situation last week.
I was deploying Windows 7 (XP to 7 upgrade with hardlinking USMT) on machine with 2 physical drives. It was the first machine with 2 physical drives we deployed OS with SCCM on.
The OS image was applied to the wrong physical drive and as you may guess, caused data loss of that employee.
After trying to reproduce the situation, what i've seen was that after the machine boots to WinPE, it decides to switch by himself between the drives.
The first HDD becomes second, and the second first, and that way the image was applied to the wrong destination.
In TS the apply image is set to apply the image to the first available partition.
Is there any way to prevent this kind of behavior other than specifying the image to be applied to specific disk and partition? (Haven't tried that tho if it matters).
Thanks in advance,
Dynamitry
Share this post
Link to post
Share on other sites