How to use system center sccm to install operating system on m.2 nvme SSD

When the friends use Microsoft sccm to install the operating system on the computer, will they encounter this situation, that is, they used to be mechanical hard drives or solid state drives with SATA interfaces, so when formatting the hard drive, it is a good choice in the sccm task sequence . As long as your boot hard disk is plugged into the sata interface, select the disk number. But now with the price of m.2 nvme disks becoming more affordable, most companies choose hard disks with this interface. But there is no dedicated option in sccm. So how should the system be installed in the m.2 nvme disk? it is good. Now we start:
1. First, we need to pour the nvme driver into Windows PE, which is the "boot image package", so that Windows PE can recognize the nvme disk. This is a very important step.

2. In order to increase the versatility, we add two groups in the "Task Sequence Editor" to determine whether there is an nvme disk in the computer, and what is the disk number of this disk automatically assigned by the system.
First add "Judging and formatting the SATA hard disk group", in the "Options" on the right we add conditions. Select wmi query and add the sentence Select from Win32_DiskDrive where Model like "%NVMe%"
This sentence means to determine whether there is an NVMe hard disk in the computer, and if not, execute this group. Because I chose "If unconditional holds." If there are nvme disks, this group will not be executed.

If there is no nvme disk in the computer, I usually insert the sata disk into the sata0 port. The following statement is a normal format for disk 0.
3. Add another "Judging and formatting nvme hard disk" group, the judgment condition is also Select from Win32_DiskDrive where Model like "%NVMe%". Only the condition is changed to "Run this group/step if the following conditions are met:". This will run this group when there is an nvme disk in the computer.

When there is an nvme disk, we don't know what the disk number is automatically assigned to the nvme disk when entering windows pe, so we also need the following statement to determine the disk number allocated by the system to correctly install the system on the nvme disk.

The query statement here is Select * from Win32_DiskDrive where Model like "%NVMe%" and Index=0. It means that there is an nvme disk and the disk number is 0. Then it will execute the

same statement as the disk number 1 below, just change and index=0 to and index=1. In my experience, if there are both nvme disk and sata hard disk in the computer, and the hard disk is plugged into the sata0 port, when entering windows pe, the system will assign the disk number 0 to the sata hard disk and the disk number 1 to the nvme hard disk. For safety's sake, I also added a statement to judge the nvme disk number as 2.
So far we are done.
To sum up, I personally feel that learning wmi statements is still more important. Replace with other wmi statements here to determine your motherboard model, because the disk numbers assigned by different motherboards still have certain rules.
Another great god wrote a powershell statement to the effect of setting the disk number of the nvme disk to 0. PowerShell -ExecutionPolicy Bypass -Command "(New-Object -COMObject Microsoft.SMS.TSEnvironment).Value('OSDDiskIndex') = (Get-PhysicalDisk | Where-Object BusType -eq'NVMe').DeviceID "
I haven't tried this . Please test it yourself. .