02-27-2017 06:39 AM
I am tasked with imaging 1800 N23 for the school district using SCCM. I have created a stand alone USB to do this (because of UEFI) but the HD assignment in the BIOS changes between seeing the hard drive as drive 0 or drive 1. If it were consistent if would not be a challange, but it can change with each boot. This required me to build two USB key, one for drive 0 and one for drive 1, and stopping the task sequence to check where the hard drive is assigned. If not, the USB key get repartitioned and the TS fails.
Anyone else seen this? Anyone have a solution? Are these devices not approbiate for the enterprise (if they can't be easily imaged)? The only other devices i have seen this issue on were disposable devices which did not last even three years.
02-28-2017 11:49 AM
I would suggest trying using the current Win10 ADK for build 1607. With later builds of 10 we have been seeing that the drive number swapping around at every boot went away. The problem is that previous capabilities to target drives relied on INT13 calls in Legacy BIOS. Now with UEFI we don't have the INT13 capabilities.
03-03-2017 07:21 AM
Looks like using the 1607 WinPE is going to resolve the issue. Now I have to upgrade our existing SCCM 1511 installation to support 1607 for this one model. Good thing I am being paid by the hour.
03-07-2017 11:32 AM
03-09-2017 12:47 PM
I created two USB drives in SCCM Tasksequence - one that installs the OS on Drive 0 and the other installs on Drive 1. Both have a stop before initiating. At the stop I open a command prompt and check the drive assignment with Diskpart. Usually, I can switch to the appropiate USB (drive 0 or 1) and then initiate the imaging.
HOWEVER, now I have encountered devices that CHANGE THE HARD DRIVE ASSIGNMENT after I switch the USB key, partitioning and formating the USB before failing because it just wiped out the source image. It take ~20 minutes to recover and rebuild the USB key so this is getting very frustrating.
I did get some USB dongles and the same WinPE operates when PxE booting to the server, but they take 3 times as long to image. As I said, I have 1800 of these things to image and cannot afford to triple the imaging time.
Has any one else tried to image the N23 in this manner, or seen this issue? I looked at updating the BIOs but they are coming in with the latest version.
Nice little consumer machine, just not ready for the Enterprise, IME.