Harry M Johnston
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Hi all,
We're using a task sequence to upgrade Windows 10, and on one of our clients the task sequence aborted after the system was restarted because it couldn't load the task sequencing environment. It turned out that it had been stored on the D: drive, which was an external USB drive that was BitLocker-To-Go encrypted. When the task sequence was started, the D: drive was unlocked, but once the system rebooted it was no longer available. Presumably we'd have run into the same problem if the USB drive had been removed during the task sequence.
Is there any way to force SCCM to put the task sequence environment on the C: drive? Or any other solution to prevent this scenario from happening?
Thanks,
Harry.
We're using a task sequence to upgrade Windows 10, and on one of our clients the task sequence aborted after the system was restarted because it couldn't load the task sequencing environment. It turned out that it had been stored on the D: drive, which was an external USB drive that was BitLocker-To-Go encrypted. When the task sequence was started, the D: drive was unlocked, but once the system rebooted it was no longer available. Presumably we'd have run into the same problem if the USB drive had been removed during the task sequence.
Is there any way to force SCCM to put the task sequence environment on the C: drive? Or any other solution to prevent this scenario from happening?
Thanks,
Harry.
