Task Sequence installs Windows to wrong drive

Task Sequence installs Windows to wrong drive

When deploying install.wim (from DVD) using System Center Configuration Manager 2012, you will see that the installation is done on drive D: instead of the expected drive C:.

Even though the Task Sequence reported that the installation was done on C:

image

image

You will be able to use different methods around this problem, but the fastest and easiest way will often be to use the Task Sequence variable OSDPreserveDriveLetter.

Set the variable to FALSE as shown here:

image

Insert the variable immediately before  Apply Operating System

And the result after using OSDPreserveDriveLetter = False:

image

This is actually a problem with more to it than you might think, so read this post if you want to know more and also other possible solutions.

How to Ensure that Windows Installs on C: During a System Center 2012 Configuration Manager OSD Task Sequence

+ posts

Table of Contents

Share this post
Search blog posts
Search
Authors
Modern Workplace consultant and a Microsoft MVP in Enterprise Mobility.

Modern Workplace consultant and a Microsoft MVP in Windows and Devices.

Infrastructure architect with focus on Modern Workplace and Microsoft 365 security.

Cloud & security specialist with focus on Microsoft backend products and cloud technologies.

Cloud & security specialist with focus on Microsoft 365.

Cloud & Security Specialist, with a passion for all things Cybersecurity

Cloud and infrastructure security specialist with background in networking.

Infrastructure architect with focus on design, implementation, migration and consolidation.

Infrastructure consultant with focus on cloud solutions in Office365 and Azure.

Modern workplace and infrastructure architect with a focus on Microsoft 365 and security.

follow us in feedly
Categories

Follow on SoMe