Installation of Windows and Configuration Manager steps did not start

[radish]

Traditional bios mode boot method, task sequence set more than 3 steps to format the hard disk

where the disk 1 task sequence operating system partition does the OSDdisk variable

Then the installation of Windows and Configuration Manager steps will not be booted, check the logs to find the cache path corresponding to the folder that can not be properly started to install Windows and Configuration Manager steps .....

After several tests respectively with Hyper-v, Vmware, physical computers have more than 3 hard disk hardware environment, the testing process is very crazy .... The first time I found some laws, I finally found some laws!

Traditional bios mode boot method, task sequence set more than 3 steps to format the hard disk, disk 0 task sequence OS partition made OSDdisk variable
then everything is fine.

Traditional bios mode boot method, task sequence set more than 3 steps to format the hard disk, disk 1 does not contain disk 0 task sequence OS partition made OSDdisk variable, then everything is fine.
will lead to formatting more than 3 hard disk steps task sequence environment tasks will lead to the installation of Windows and Configuration Manager steps boot failure, while formatting 2 hard disk steps below the task sequence environment tasks all normal, oh oh Is not feel very amazing?

Why not do the OSDdisk variable on disk 0? Because the user computer environment disk 0 is not necessarily the disk where the operating system is installed, perhaps disk 1 is solid state, disk 2 solid state or other solid state disk number, there are Powershell scripts to control the installation of eligible disks as the operating system to set the OSDdisk variable, you can easily avoid IT engineers or ordinary users to set the Bios or open the chassis to the solid state disk plugged into the SATA0 interface.

 Does anyone know what's going on or is it a bug? 
 

 

传统bios模式启动方式，任务序列设定3个以上格式化硬盘步骤，

其中磁盘1任务序列操作系统分区做了OSDdisk变量

那么到了安装 Windows 和 Configuration Manager步骤 将不会进行启动，查看日志发现是寻找不到缓存路径对应文件夹导致不能正常启动安装 Windows 和 Configuration Manager步骤.....

经过多次测试分别以Hyper-v、Vmware、物理计算机 都有3个以上硬盘硬件环境，测试过程中很抓狂 ....，终于发现了一些规律！！！

传统bios模式启动方式，任务序列设定3个以上格式化硬盘步骤，磁盘0任务序列操作系统分区做了OSDdisk变量
那么一切都正常。

传统bios模式启动方式，任务序列设定3个以上格式化硬盘步骤，磁盘1以外不包含磁盘0任务序列操作系统分区做了OSDdisk变量，
会导致格式化3个硬盘步骤以上任务序列环境任务时候将导致了安装 Windows 和 Configuration Manager步骤启动失败，而格式化2个硬盘步骤以下任务序列环境任务一切正常，喔哦 是不是觉的很神奇？

为什么不在磁盘0做OSDdisk变量呢？因为用户计算机环境磁盘0不一定是安装操作系统所在磁盘，也许是磁盘1是固态、  磁盘2固态 或者其他固态磁盘编号，有Powershell脚本来控制安装符合条件磁盘作为操作系统设置OSDdisk变量，可以轻松避免IT工程师或者普通用户去设置Bios或者打开机箱把固态磁盘插到SATA0接口上。

 有人知道怎么回事吗或者说是BUG？ 

 

 

Default Win10 x64 LSTC2019.zip smsts.log

[anyweb]

just to be clear, you are trying to install Windows 10 LTSC 2019 on a computer with 3 physical hard discs, correct ? and when you try in that configuration, it fails ?

does the same task sequence work correctly if there is only one hdd ?

[radish]

Yes, the single hard disk and the 2 hard disks OSD task sequence are working fine.

 Suppose a physical computer has 3 hard disks.
Disk number 0 120G HDD
Disk number 1 500G HDD
Disk number 2 250G SSD

The OSD task sequence has 3 formatting steps
where disk number 1 BootFromDisk property is true and is the first boot disk

Then installing the OS to disk number 2 250 SSD will cause this problem and the ccm client installation task sequence will fail to boot!

Let's look at this
Suppose a physical computer has 3 hard disks.
Disk number 0 120G HDD
Disk number 1 500G HDD
Disk number 2 250G SSD

The OSD task sequence has 3 formatting steps, we disable a disk number 0 formatting any step
where disk number 1 BootFromDisk property is true and is the first boot disk

Then the operating system is installed to disk number 1 500G HDD and everything is fine.

Make sure that the problem occurs when using the traditional bios method of booting, formatting more than 3 hard disks when the task sequence steps and the first boot hard disk and the operating system hard disk are not in the same hard disk.

 

 

 

It is worth mentioning that
Suppose a physical computer has 3 hard disks.
Disk number 0 120G HDD
Disk number 1 500G HDD
Disk number 2 250G SSD

The OSD task sequence has 3 formatting steps

where disk number 1 BootFromDisk property is true and is the first boot disk

Then the OS is installed to disk number 1 500G HDD

 

 

 

 

It is worth mentioning that
Suppose a physical computer has 3 hard disks.
Disk number 0 120G HDD
Disk number 1 500G HDD
Disk number 2 250G SSD

The OSD task sequence has 3 formatting steps

where disk number 1 BootFromDisk property is true and is the first boot disk

Then the OS is installed to disk number 1 500G HDD and the task sequence works fine.

Although this approach can be avoided, it also loses the ability to determine the OS to be installed on a qualified drive.

I also have a question: Why does the task sequence work fine when the first boot disk and the OS disk are not the same disk, even though the task sequence has two formatting steps?

The task sequence set up 3 formatting steps, the first boot hard disk and the operating system hard disk is not the same hard disk, is not running properly after the deployment of the CCM client task sequence start, prompting that the cache folder path can not be found, it seems that the variables are reset or the disk drive number is disturbed?

[radish]

 

Uncheck the Do not assign drive numbers to this partition to solve the traditional bios way boot task sequence set 3 hard disk format task sequence
ccm client installation steps did not find the cache path failure problem