/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Just got a new installation disk of Windows 10 x64 Enterprise v1803, and was going to get started creating a sysprepped image of it to start pushing it out.

I installed it one of my test machines with no problems.  Ran Sysprep_Executor with no problems (other than having to manually stop the new Windows Defender security software), and sysprep then shut the computer down.  I use a USB key to boot the computers into the KBE.  When I booted into the KBE, I double-checked the partitions before imaging, to make sure they were using the correct drive letters (Created the image on a BIOS machine, so there was S: for System Partition and C for Boot Partition).  The Imaging process gave no errors, but something weird happened. 

I tried deploying the image back to the machine.  It automatically uses diskpart to create the S and C partitions.  When it tries to apply the image, it takes less than 30 seconds.  The image deployment job then gives the dreaded "setup_post_install_tasks.vbs" error.

At this point, I know something is wrong.  I open a command prompt, and see that the two partitions have been created, but there is almost nothing on the C drive!  There is a KACE folder, and then a file called kcleanup.exe

I went through the exact same imaging process with Windows 10 x64 Enterprise v1709 with no problem.  Something has changed between 1709 and 1803 that prevents the imaging process from working.

Here is what I'm using

SDA Model K2100S, Version: 5.1.84
Sysprep Creator 4.1.1.0

What can I do to get a working WIM file using Sysprep Creator ?

Thanks

6 Comments   [ - ] Hide Comments

Comments

  • You are supposed to create the initial installation with a K2000 scripted install so that only 1 partition gets created.
    • I believe UEFI boot builds two partitions.
  • I believe I have the same problem that eahelms has. The image process takes about 44 seconds till fail and that is after it supposedly applies the image which cant happen that fast. The fail error is the same too at the "setup_post_install_tasks.vbs" error. The image file is 3.96GB in size. The image capture time seems right for the file size so not sure where the problem occurs. This is my first UEFI image process attempt. Been imaging bios boot for years with Kace.
  • I've created a scripted unattended installation task of Windows 10v1803 x64 Enterprise that I installed on a UEFI machine. Here is the diskpart task I use to create all the partitions needed:

    Select disk 0
    Clean
    Convert gpt
    Create partition efi size=100
    Format quick fs=FAT32 label="System"
    Assign letter=s
    Create partition msr size=16
    Create partition primary
    Format quick fs=NTFS label="Windows"
    Assign letter=c
    Exit

    I then have a midinstall task that repairs the BCD

    bcdboot C:\windows
    bcdedit /set {bootmgr} device partition=s:
    bcdedit /set {memdiag} device partition=s:
    bcdedit /set {default} device partition=c:
    bcdedit /set {default} osdevice partition=c:
    Bcdedit /set {FWbootmgr} displayorder {Bootmgr} /addfirst

    The scripted install creates a local user account that is a member of the local Administrators group. I login, and I install the May MS updates on the OS. and then restart.

    At this point, I run sysprep_executor, which I created using sysprep_creator. When it's done, it shuts the computer down. I then boot to the KBE (open a command prompt, to make sure the S drive is mapped to the system partition, and the C drive is mapped to the boot partition) and then capture the image. I tell it to capture both the S drive and C drive as a WIM file.
  • EAHELMS,

    Yesterday, I finally played with 1803 to update my base images. I initially ran into this exact issue... I could deploy previously created images just fine, but 1803 just would...not...work.

    Creating a brand new KBE with the newest Windows 10 APK fixed things for us.

    https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install#winADK
  • Will try that tomorrow, jguthrie, and see if that works.
  • Worked like a charm - thanks!
Please log in to comment

Answer this question or Comment on this question for clarity

Answers

0
"(Created the image on a BIOS machine, so there was S: for System Partition and C for Boot Partition)."

Are you sure this is not UEFI?
https://support.quest.com/kace-systems-deployment-appliance/kb/186950/uefi-image-process

C is the NTFS Big OS parition
S is the small FAT32 parition

What tasks are you using (Pre and Mid level)

What version of Windows 10 1803?

Sounds like the image wasn't properly captured in the first place.
Answered 05/16/2018 by: Channeler
Tenth Degree Black Belt

Please log in to comment
0
Created the following pre-install task for UEFI
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

There is no mid-install task needed.

Imported the Windows 10 (1803) disk into SDA as new source media using Media Manager. Created scripted install using the new source media. Created UEFI boot USB. Later Created the automated deployment. Works great!
Answered 05/18/2018 by: egholm52
White Belt

Please log in to comment