We are trying to image a Lenovo T470 with an image provided by a client. It's Win7, but we have slipstreamed the necessary NVMe drivers and it works OK on an X270 deployment (the X270 uses the same Samsung NVMe drive as it's T470 sibling). 

However, when we try to deploy to a T470 (using the same KBE, image and installation tasks) it fails immediately, before it even acknowledges the first pre-install task, with the wscript error above. If we click Continue, it will do so but will throw up the same error a little further down. We can click 'Continue' again at which point it will skip down the rest of the task list and claim that it completed OK.

The laptops (T470) come factory configured with 1 disk, 3 partitions. C:\ Windows, D:\ Recovery and a 100MB hidden system partition. The X270 has the same arrangement...but it deploys just fine.

I tried to remove the two extra partitions but I was unable to remove the system partition (not surprising really...) but the Recovery one deleted. The deployment then failed with the same error...only this time it complained about drive D:\ (as opposed to E:\).

It definitely seems like this is related to the partition structure in some way, but we can't figure out how / why. 

Do any fellow IT black belts (OK, maybe green at a push...) have any ideas on this??

Thanks
Answer Summary:
Cancel
4 Comments   [ + ] Show Comments

Comments

  • Having the issue now on a T470, am going to disable the SD Card in the bios and see if Kace can work around it.
  • We found that if we let KACE go through past the first step or two then, once it has formatted the disk, we just power it down. Literally just hold the power button in for a few seconds. Then try the image operation again and it works.
  • I am having the same problem only on the T470. We have 15 different Lenovo models with various hardware and this is the only one that has an issue imaging in the K2. I have tried all the suggestions listed here. I went into the bios and disabled the SD Card and Memory Card, no good. I went to recovery and ran disk part from the command line using:
    select vol 2
    remove all dismount
    Exit

    This got us by the error, but then it would not boot back into Windows after the imaging task. Without manually entering the disk part command,
    the error pop up occurs before our first task, so it is built into the K2
    With over 350 systems of this model, it is quite impractical to quit and start over.
    Anyone have any other suggestions?
    Thanks!
    • Hi...once it finishes imaging, but will not boot into windows, have you tried rebuilding the boot files? We had a client image that would deploy fine, but would not boot. We boot to Windows repair cmd prompt, manually type in the repair command, and then it works:

      It's basically:
      bcdboot C:\Windows
      ...but there are a few other flags you can add:

      https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di

      It worked for us, hopefully might work for you too.
      • Thanks for your comment. There is something that the K2000 doesn't like in the UEFI BIOS. The only way I can get this model to image is to change it from UEFI to legacy. The No Disk error continues to pop up regardless of what action you take and like I said previous, we have over 15 Lenovo models with both legacy and UEFI and none of them have this issue. These came from the factory with Secure Boot turned on, which the K2000 also does not like. Since the techs will need to turn that off, they will just have to switch to legacy mode. We also use Windows Deployment Services and have no issues with any model. I'll open a ticket and see if support can determine why on this model. Thanks again!
  • Try the full bcd command to add the UEFI files to the hidden S: system partition:
    bcdboot C:\Windows /s S: /f ALL

    You could also try changing the SATA operation mode from RAID to AHCI - we found AHCI to be the more reliable.
    Also, are you at the latest version of KACE? Some major improvements were made in the last big update.

    You may have to image under BIOS and then swap to UEFI after running the bcd command.

    KACE / UEFI / Win10 imaging is a total ball-ache to be honest...
Please log in to comment

Answer Chosen by the Author

0
We found that if we let KACE go through past the first step or two then, once it has formatted the disk, we just power it down. Literally just hold the power button in for a few seconds. Then try the image operation again and it works.

Bizarre. Don't you just love computers??
Answered 08/15/2017 by: Duncan_H
Senior Yellow Belt

Please log in to comment

Community Chosen Answer

2
Heres an answer from Quest support

Lenovo and it's card readers are famous culprits forthis, this does not happen with any other manufacturer despite having cardreaders. For some reason those card readers will take Letter assignments inWinPE, disrupting the Deployments (the partitioning tasks).

Option 1, disable card reader from the BIOS. - i cant see where this is in the BIOS

 

Option 2 follow this KB:

"Operating System not Found error when Card Readerinstalled"

https://support.quest.com/kace-systems-deployment-appliance/kb/134650

 

Please confirm KBE PE10 is being used, and it was builtwith PE10 drivers ONLY on it.

See:

https://support.quest.com/kace-systems-deployment-appliance/kb/184391

 

Boot to the KBE go to Recovery Options > open CMD >Open DISKPART, and do a LIST DISK, grab a screenshot, if DISK 0 is your harddrive, then do DETAIL DISK, and grab a screenshot. (see my screenshot attachedas an example)

 

NOTE: If you only have one partition that means youshould be deploying to a Legacy BIOS enabled machine.

And if you are PXE booting, you must be PXE booting toNIC IPV4 legacy. (see my screenshot attached).

Your three PRE tasks should be:

-Create Single Partition

-Format C: as NTFS

-Install MBR

 

Answered 10/03/2017 by: Itchy12
White Belt

  • I am not able to see these attached screenshots you mention.
    • Looks like it wont let me upload a pic?or even paste it into the html form
  • After testing it solved it for me to use a WinPE image that only had built in drivers for Windows 10 installations. We never saw the issue on Windows 7.
Please log in to comment

Answers

1
I figured out why this is happening as I just got a T570 (same as T470 just smaller screen) and got the same error.  It's looking at the SD Card slot, seeing a drive with no disk in it.  That's why your drive letter changed after removing a partition.  This is true, there is no disk in it.  The big question is just why is KACE getting hung up on a removeable drive.
Answered 06/30/2017 by: swalker804
Senior White Belt

  • Thanks...never even considered the SD card! But yes, you're right...though that really does beg the question of why KACE gets hung up on it.
    We have imaged plenty of other units with SD card slots and it never complained then...weird.

    Cheers.
Please log in to comment
Answer this question or Comment on this question for clarity