I have been using the BIOS updates in the task sequence successfully for years. We started imaging the "Surface Pro for Business 11th Edition with Intel" models, and when I download the drivers, all I get is the "Microsoft Surface Pro for Business (11th Edition)" available to download. When I try to image with that, the ApplyDriverPackage.log shows "-validation failed with empty list of matched driver packages, script execution will be terminated." Running "wmic computersystem get model" returns the model ending "with Intel" and no parentheses. Is my model name going to work with that driver package that I need to tweak the powershell script, or will this model be added as a driver package? I'm using Driver Automation Tool v10.0.0.42. Thanks so much for a great utility!
edit: If that package will work, I could just rename the driver package, right? I'll test that too.
I have been using the BIOS updates in the task sequence successfully for years. We started imaging the "Surface Pro for Business 11th Edition with Intel" models, and when I download the drivers, all I get is the "Microsoft Surface Pro for Business (11th Edition)" available to download. When I try to image with that, the ApplyDriverPackage.log shows "-validation failed with empty list of matched driver packages, script execution will be terminated." Running "wmic computersystem get model" returns the model ending "with Intel" and no parentheses. Is my model name going to work with that driver package that I need to tweak the powershell script, or will this model be added as a driver package? I'm using Driver Automation Tool v10.0.0.42. Thanks so much for a great utility!
edit: If that package will work, I could just rename the driver package, right? I'll test that too.