ConfigMgr Task Sequence OSD Multiple Physical Drives | SCCM

In this post, we learn about ConfigMgr Task Sequence OSD Multiple Physical Drives. Let’s try to understand how can we use conditions in the Task sequence to install operating systems via SCCM Task Sequence on a machine having dual drives.

The below articles will give you an idea about the scenario which I have faced in installing a windows OS on a machine having two physical Hard drives. The conditions can be customized according to the environment and requirements.

Introduction

We are taking an example of a system with a dual drive (or more) configuration, an NVMe drive, and either a SATA mechanical disk or SATA SSD. In some cases, the SATA disk may be enumerated as Disk 0 and the NVMe drive as Disk 1 or vice versa. 

This can be confirmed by booting to WinPE, executing the DiskPart utility, and selecting disk 0 and/or disk 1, followed by the command detail disk.  Note the type of disk displayed, which will either be SATA or NVMe.

In a default standard SCCM OSD task sequence, disk 0 will be formatted and partitioned depending on the partition scheme assigned (MBR or GPT). As newer models are getting released the SATA mechanical disks or even SATA SSD disks are getting replaced with NVMe disks.

Info on Dual Drives

To check the drives on your machine use the below command in PowerShell.

wmic diskdrive get index,model

You can also check the information on the dual drive using disk management, and open diskmgmt.msc right-click on the disk for which you want information as in my case I want information on disk 1, you can get info in the General tab.

Similarly, if you have a dual drive one with NVMe and another with SATA mechanical or SATA SDD it will show accordingly.

Solution

Ideally, the Windows OS should be installed on the NVMe disk for better performance ( Why it should be installed on the NVMe disk is a different topic ), there are many ways to achieve it you can add dynamic variables inside the OSD task sequence, you can use scripts to achieve it.

If you are aware of your environment and know the hardware which is being used with their configurations then it can be simply achieved by a WMI condition. Below are the steps which you can add to your task sequence to achieve it:

I created two groups with Format and Partition conditions as below, I am aware of the models which are procured in my environment, but to be on detect if the NVMe disk is at 0 or 1 the two groups are created

The first group will format and partition if NVMe is at disk 0 and make it an OS disk and the other disk as a data disk, in the second group if NVMe is found at disk 1 that will be configured as an OS disk, and the other one as data disk.

You can add two conditions first one on getting info on disk drive details and the second one on the models on which you want to perform this step.

WMI conditions

Let’s check the WMI conditions to check the disk types and avoid issues with SCCM task Sequence.

Select * from Win32_DiskDrive where Model like "%NVMe%" and Index=0

Select * from Win32_ComputerSystem where Model like "%Model%"

Verification

You can go through the smsts.log during the Image build to find out if the conditions which you have configured are meeting your requirement.

• Location of smsts.log before the hard drive is formatted

x:\windows\temp\smstslog\smsts.log

The location of smsts.log after the hard drive is formatted and partitioned.

x:\smstslog\smsts.log

Let’s look into the results now.

Result

You can customize the condition according to your environment and requirement.

References

• https://www.anoopcnair.com/sccm-osd-task-sequence-ultimate-guide/

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…