/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


SDA RSA system deployment issue / OSNotFoundonLocalDrive

08/03/2020 234 views

Hi Everyone,

So I have downloaded new KBE A15 from quest (because Optiplex 7480 needs new network driver), uploaded in sharefolder, recached the drivers and created a new KBE boot environment.

I have also synced the KBE to a RSA located in branch office.

The issue is, KBE boots fine and can reach SDA IP address, but shows this error:

OS: > OSNotFoundonLocalDrive<

Path expected by driver feed: >dell\OSNotFoundonLocalDrive\AIO<

The Driver path does not currently exist on RSA


I have downloaded the Optiplex 7480 AIO drivers from Driver Feeds and is synced.

Any ideas what might be missing?

Thanks!





Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • disregard that message.

    That happens because WMI is not returning an OS while on Windows PE. (a KBE is essentially Windows PE, plus drivers, plus Quest Tools).

    What is the issue?
    • So thats normal. the issue was at first KBE A10 couldn't find NIC drivers so I built A18 KBE now it can detect network card and reach SDA IP address.
      the issue is all post installation tasks are completed but not joined to AD ( I suspect network drivers cannot be found to be installed in Windows)
      previous laptop model are being deployed just fine without any problem.

Answer Chosen by the Author

0

the issue was, KBE was looking in a different folder for postinstall drivers. i found out with driver_feed vbs script. I had to copy the drivers from Optiplex 7480 AIO folder into \AIO folder itself for deployment to be successful.

Answered 08/04/2020 by: narbehd
White Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ