Guys the manual for eufi enabled scripted install in kace says to partition the pc drive with this script

before installing the OS....

Select disk  0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit

But when I do this and try to do a scripted install, I get this error .....

Windows cannot locate the disk partition specified in the unattend answer file <ImageInstall> setting.

Make sure the setting references a valid partition and restart the installation.


I checked unattend answer file I created in the k2, and the default OSImage setting is...

<InstallToAvailablePartition>true</InstallToAvailablePartition>

Is the OS install not installing in the C: drive or what? Maybe its trying to install

into efi partition ??? which is 200MB.

What am I doing wrong. DO I need to have uefi partition for win10 installs ??

cant I just have a C: drive like in win 7?


1 Comment   [ + ] Show Comment

Comments

  • Are you booting from PXE or using a USB thumb drive?

    Also, check if you are using an NVMe SSD drive, those drives require some special drivers.

    Before starting the deployment, go to recovery tools, open CMD.

    Open DISKPART

    Type LIST DISK, post the results
    Type LIST VOL, post the results
    If this disk 0 is your main drive type:
    SEL DISK 0, hit enter
    Type DETAIL DISK, post the results

    Wit this you should be able to know if the KBE is seeing the hard drive and what type of hard drive is this.

    The Create UEFI partitions script is needed, if the BIOS is set to UEFI, regardless of the OS being installed.
    • Yes it is a PXE boot install. and I have enabled uefi on the device.
      look in the answer section for a picture of the "detail disk" screenshot
      • Type LIST DISK, post the results

        It seems the partitioning is not happening at all, Are you sure Create UEFI Partitions is your only DISKPART Pre Installation task?

        Please make sure the device is UEFI and you are booting in UEFI mode not Legacy, see screenshot.
Please log in to comment

Answers

This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

0