Driver download automation tool no models found






















Hello, I have downloaded the the latest Driver Automation Tool version 6. All is working fine. However the HP Driver Catalogue is not populating. Looking at the logs I see the following errors:. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. There have been a few changes in the CAB file. Well, grabbed the bull by the horns and went through the invoke-Driverdownload. After adding that to my custom package, everything seems to work.

Could this be addressed in a future release? I am running it as the credentials with sccm permissions. Any help would be greatly appreciated. Thank you. Love the new update, except for one thing. I cannot seem to change the proxy config in the UI. Version 1.

Maurice has been working in the IT industry for the past 20 years and currently working in the role of Senior Cloud Architect with CloudWay. Most recently his focus has been on automation of deployment tasks, creating and sharing PowerShell scripts and other content to help others streamline their deployment processes. Save my name, email, and website in this browser for the next time I comment. You cannot call a method on a null-valued expression. Please refer to our tools section and look at the Driver Automation Tool as this post entry is quite old.

I tell you what, if we could get something like this to work with Lenovo and IBM server drivers in my world, I would be on a new level. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Can you ensure that you are running at least PowerShell 4. Nice script, thanks for sharing. When parsing the xml catalog, it seems the xs-win10 pack points to a card reader driver instead of the driver pack. Looks like a typo. Hi Ben. Let me see if anything has changed.

I found the issue here. An update to the code is to follow on the MS Script Library shortly. It will be added as v1. Yes, clearly Lenovo needs to correct the inconsistency. I think there maybe some issue with xml file as I am not seeing all Lenovo models in pick list. At present manually interrogating the XML only results in the following;. Thanks a lot for the quick response Maurice.

I guess I will have to do the win7 drivers manually. First off, great tool! Is there something different about the HP model request? Just wonder for troubleshooting purposes. If you are selecting the Windows 10 or as the OS, HP is the only manufacturer currently using this method. If you select Windows 10 or previous OSes you should be able to select the other manufacturers.

How often is the driver XML updated? Thank you, this tool is a great time saver! The Acer downloads are taken from a web scrape so they are real time and the Microsoft downloads are manually updated at the moment. Is there any difference in your internet access policies between the two?. There is not. Both are exempted from filtering. Different content filter, but the same result. With regards to the MS information, we can download the file in a browser using DownloadLinks.

Can you please mail me over the log [email protected] so I can see what is happening?. The script has been tested in Windows 10, R2 and with no issues. Still loving this tool, but am having an issue with downloading the device lists.

I was able to pull all but Microsoft a few weeks ago. I did a bit of troubleshooting for the MS issue. I cannot see the file with lower case letters. Could I be having an XML format issue or a filename issue?

Nice tool, I really want to use it but I receive always the same error when the script tries to import the drivers. New-Item : Object reference not set to an instance of an object. Yes I have. The strange thing is, the driver packages are created and do contain the drivers. With a previous version of your tool I received the same error but the driver packages were empty.

I have just updated the script to allow for these. Ran into an issue with a few of the Dell models we use. There is no error in the GUI, but it never downloads, extracts, and imports the drivers. Effected models are the Optiplex , Optiplex , and Optiplex I have found the issue, it applies to models with multiple sub-models, such as , M, AIO etc. I have just removed a wildcard on this line —. Well Liked Process and Brain saver allowing more Coffee time, we have a total of 13 Dell models across 3 OS platforms using x86 and x64 on each this is going to same me whole bunch of time every quarter when we run updates against hardware.

I will pass on this feedback though. Truly next level tool this, on have one problem when I put in my server name it keeps saying sccm server specified not found — I am an admin on the box and in configMgr.

I presume when you say it wont connect to your server you are running the script remotely?. This appears to be for different versions, like ATG and XFR, but the tool does not distinguish between these in the list. Also, I had 2 models which did not download the driver cabs E, E Next update in 30 seconds.. Unfortunately in some cases the model naming convention is not standardized, however I will add in exception rules where required.

I am also working to add in another Dell XML feed for BIOS updates not currently listed in the tool and additional package checks, all of which will be in the next build in a couple of days.

I am excited about the prospects of this utility. I am testing it in my CM test environment which is running I am running into some issues and notice a few flaws in the UI of the tool. Would you prefer an email communication vs posting my findings here? I am not sure if this is working or not. I had to force quit Powershell but the driver package does show up in ConfigMgr.

I am not sure if this is normal or not. Btw thanks for this tool, it will really help a lot. Please let me know the OS you had selected and I will run through this to see can I replicate the issue.

Thanks for providing this tool. However, I am running into an issue when trying to use it. Site Server populates just fine. We have a physical firewall for the whole campus, so Windows Firewall is disabled. I enabled PS Remoting, no change. So I was able to run it successfully on a different computer.

Start-BitsTransfer : The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. Mana gement. You cannot call a method on a null-valued expression. I presume you are running the account as a different user on the machine?. If so can you log on interactively on the machine and test the script?. That did it! We use standard credentials to log in with an admin login to run things as needed.

Logging in as the admin account allowed everything to work, including reading the XMLs. Thanks for all your help! I was able to manually download it and change the name to match the script to install. It will be posted in the morning — version 2. First — great tool. However, newer laptops, like the Dell Latitude E and E all prompt errors like below when importing.

Any help would be appreciated! Verify that the driver exists in the specified location and that the SMS Provider computer has Read permissions to the specified shared folder. I will pass your feedback for the T to be added.

The issue has to do with the folder structure of the Dell drivers. When the drivers are attempted to be added, the script attempts to add the directory as a driver package. To solve the problem change line to include the -File filter so only files are included in the list and the directory object themselves are excluded. Any known issues with the Lenovo side of things? Dell works fine for me but I get this from Lenovo:.

I tried downloading the Mz drivers without issue. Perhaps you could email me the full log so I can see what was going on?. One problem though, in my case it downloads the cab-file successfully, it also creates the folder structure successfully both in the driver repository and in MDT, but neither folders contain any files, so something seems to go wrong with the extraction.

There was an issue with a large number of HP driver packages not performing a silent extract up to a couple of days ago, so you might clear out any previously download files and directories then try it again as HP have since resolved this issue. Your note section is actually editable from within the GUI. What gives? How can I manipulate this script, to import drivers into MDT model folder instead of revision folder? If you take a look at lines you will see the section that is used to create the structure within your MDT deployment share.

It would simply be a matter of rearranging the variables to suit your own naming convention. Hi Andrew. Driver Automation Tool. Set theme jekyll-theme-cayman. View code. Version history: 6. Graphical redesign, improved layout, HP individual driver downloads 6. SCCM custom folder code optimisation. Bits enabled by default, can be disabled by setting the option manually and then closing the GUI to commit the save.

Additional error handling. Current download will use latest Windows 10 build download link until build numbers are available in the XML Data grid updates for both Models and Package Management sections to clearer highlight selected values 6.



0コメント

  • 1000 / 1000