/build/static/layout/Breadcrumb_cap_w.png

Driver Feed Builder 2.5 does not work with KACE K2000 Version 3.7.120251

Hi,


I´m updated our KACE K2000 to Version 3.7.120251.

After that the new Driver Feed Builder 2.5 with Windows 10 Support shows a notice "Incompatible Version. K2000 must be at version 3.7.113224 or higher."

Everyone else with that notice. And is there a Fix for this?


Best regards

Thorsten

EDIT:

Screenshots from K2000 Version, Driver Feed Builder Version and Message from Builder.


Asked 8 years ago 1615 views
3 Comments   [ + ] Show comments
  • Just tested this on the latest 3.7.120251 version with the driver feed builder 2.5 and had no issues. Can you provide screenshots of your K2 version? It's in the About K2000 version in the bottom left hand corner. Also, can you show us a screenshot of the K2 Driver Feed Builder version?

    See if you can also manually mount the drivers_postinstall share on the Windows 10 box. If you can, then trun the builder while it's mounted and see if you still get an error. - KACE_Irwin 8 years ago
  • No Problem. I´ve added the Screenshots to the Question - Gerhart 8 years ago
    • Thanks Thorsten. Can you mount the drivers_postinstall share and go into the feed tools and see if there is a file called drvstr.cfg? If it's there, can you let us know and post the timestamp?

      If you are able to mount the drivers_postinstall, see if you can also manually mount the drivers_postinstall share on the Windows 10 box. If you can, then run the builder while it's mounted and see if you still get an error. - KACE_Irwin 8 years ago
  • Hi KACE_Irwin, i will try this as soon as possible and report the results here. - Gerhart 8 years ago

Answers (0)

Be the first to answer this question

 
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