/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi

We recently got a batch of refurbished Lenovo machines to deploy for a project. They come with vanilla Windows 10 on there so I know they can take Windows 10, but when I try to deploy Win 10 via K2000 it fails after creating partitions 'Windows cannot locate the disk and partition specified in the unattended answer file...'

I've checked the config of the scripted install and the variable I would have thought to cause this 'InstallToAvailablePartition' is set to true - should that not instruct Windows to grab whatever the primary partition is set to?
Windows 10 is installing fine to Dell machines from this scripted install, and I can install Windows 7 to these Levono machines from my Win 7 scripted install - which is pointing me towards something like a UEFI or secure boot setting but I can't find anything in the BIOS.

Has anyone got any ideas? I'm admin of this system but it's not my primary job function and I've already lost a day trying to work it out without breaking it (if the 50 Lenovo's have to go with Win 7 then so be it but Win 7 is a slow process because of updates)

Thanks
2 Comments   [ + ] Show comments

Comments

  • Hi, Have you confirmed that the Lenovo drivers are in the correct folder?? This sounds like a driver problem to me.
  • I ran into this problem yesterday while testing a deployment using VMware. Windows setup started, and I could see the hard drive was found, so I know the hard disk controller and NIC drivers were available. My coworker had just created a new KACE boot environment, so that was certainly a possible issue. It turned out the VM was set to the default BIOS, and when I changed it to UEFI the install ran as expected. I don't know if this is applicable to physical computers vs VMware.
    • I couldn't get these things to image for me no matter what BIOS was set to, but it was a HDD / Partition fault, in the end I just created a new scripted install and did away with the efi partitions and left it as a single partition and it installed to that. I'd like to know why it wouldn't work with the efi partitions like the dells do but hey, I got the machines imaged. Should have posted an update here really..
Please log in to comment


Answers

2
Sounds like you don't have the correct drivers in the boot environment.  You can check this by booting to the kbe, then go to Recovery | Command Prompt.  Use diskpart to select the disk and list partitions.  More than likely when you use the list disk command it won't find the disk.  If this is the case it is definitely drivers.  Quest support site has a KB on how to add drivers to a kbe.
Answered 04/24/2018 by: cserrins
Red Belt

  • When I list disk it's seeing the disk. Running a summary pulls down all the info on the machine also.
    • You mention it fails after creating the partitions, are you formatting the drives? I would try your preinstall tasks manually and see if they work that way.
Please log in to comment