-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driver Automation Tool 6.3.0 - Driver package download - Version #172
Comments
Oh hell dell is starting to make me crazy |
Biggest problem with this is the driver pack wont update. Since the Version number never changes. Workaround could be as easy as changing Version number to 0. |
The problem is this bit of code: (($DriverCab).Split("-")[2]).Trim(".cab") Example: Results: |
If you replace the line: With something like |
+1 on this issue. my change is probably too simplistic though!
We're only dealing with Dell hardware and Windows 10 so I've probably broken a bunch of other functions! EDIT - I didn't like that so changed to:
Still entirely possible it will cause other issues, but its working for now! |
I like the solution suggested by @Alslinet, but unless that's the only model you have, it'll think that every Dell model has that same version. This is tested and working for me. All 14 Dell models now/still have the correct version number. |
@skywayskase, you are right, i forgot to add that part in before posting. Then realized i would need som further changes. Here is the code. You should be able to identify which part of the script it is that has changed from this. I commented the parts that are changed. I really need to learn how to do pull requests, see this pastebin for the changes i think will fix this, its the same fix, just for every model this time, should be anyway: |
It looks as though Dell is listing some of the driver pack releases as "Version 1.0, A13".
Example: http://downloads.dell.com/published/pages/latitude-12-5290-2-in-1-laptop.html
This results in the Driver Package version being set as "1" when imported into SCCM.
The text was updated successfully, but these errors were encountered: