/bundles/itninjaweb/img/Breadcrumb_cap_w.png
So...got a Precision 7710 with an M.2 format NVMe drive in it (512GB). Problem is KACE (K2000) will not see it when we try to image. Furthermore, when trying to use an iso or boot disk (even Win10!) it's still not 'seen'...though it does show up in the BIOS as a device.

What driver should we be using to image this drive?
Does KACE even support NVMe?
Any tips for getting Win7 working with NVMe drives?

Thanks in advance


Duncan
0 Comments   [ + ] Show comments

Comments



Answers

0
NVMe drives are not supported with Windows 7 Scripted Installs.  See KB https://support.quest.com/k2000-systems-deployment-appliance/kb/185551

If KBE is unable to see the drives, then you need to add the appropriate drivers for that drive and build a new KBE.
Answered 01/04/2017 by: cserrins
Red Belt

  • Thanks for the comment, but I don't know what the appropriate drivers are...hence my asking the question. And I also know Win7 doesn't officially support NVMe...which is why I asked for tips rather than an actual method.

    Do you know what the appropriate driver is? I have already been to the vendor website and also tried generic Samsung and Intel NVMe drivers - no go.

    Thanks
    • This content is currently hidden from public view.
      Reason: Removed by member request
      For more information, visit our FAQ's.
    • This content is currently hidden from public view.
      Reason: Removed by member request
      For more information, visit our FAQ's.
0
As cserrins notes, that support article is what I used to solve the problem in my environment. I believe I used "samsung nvme drivers v1.4.7.17 whql" but I'm not 100%. Have you tried injecting those drivers?
Answered 01/05/2017 by: JasonEgg
Red Belt

  • I tried Samsung drivers v1.4.7.6 (NVMe Storport miniport driver) - didn't work - but we added them to the KBE and also tried to use them at the F6 prompt, rather than inject them into the image. The reason for this is because
    a. the image is sysprepped
    b. KACE doesn't allow us to write back an amended .wim file
    c. I don't know if the client image (this is not one we have built ourselves) supports further syspreps

    I did find it odd that the Win10 KBE doesn't even see the drive...but I'll see if I can track down the v1.4.7.17 drivers and give them a go.

    The drive in question is SK Hynix and comes up as 'NVMe PC3000 NVMe SK hy' when we fire up the image that came pre-loaded on this units.
    Yes, that's right - Dell shipped these units with Win10 pre-installed on the NVMe drive and it works just fine...yet if we copy the inf and sys files used to the 'Storage' drivers folder the KBE still will not see it.

    Also, to those who have suggested the MS hotfix, that would be nice but you can only install a hotfix once in Windows...and we can't even deploy windows in the first place. Kind of stuck in a catch-22 there...
    • Hi, what version of Windows 10 are you using? v1511 or v1607?
      Can you connect to me on my email?
      • Off the top of my head I am not sure. It's a client-built image - we didn't do it ourselves.

        My colleague has been on the phone to Dell themselves and they were unable to help. Which is a little f*cking ridiculous to be honest. It's a Dell laptop that we're trying to image using a Dell product...and Dell can't help us with this really rather fundamental problem.
      • I should mention that the iso used was one downloaded from MS website this week...so I would imagine it to be the latest?
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.

Share