Script to download drivers for sccm 2012

Note: If you are using a BIOS setup password which you should be , you will need to specify this within the script unless you want me to update the script to look for this run running it from the shell. This should help reduce the overall time to download, extract and create the driver packages in large environments with a wide range of models. Driver package already exists.. 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. Thanks for the help!

Just a quick update for everyone following this: Maurice has been a huge help today and helped me via Teamviewer. That was the problem, now everything is working. Thanks for the feedback by email. I run the script as priority 1 in the deployment type, and the msi as priority 2. I cant seem to find the correct way to do it. I get error with ""The software change returned error code 0x87D". The logs says that the "Application not discovered".

I know there is something wrong with the "Detection rule" The problem you are having is that once the system runs one of the deployment types, it does not run any others. So once it runs the first script, it will ignore the remainder of the deployment types.

The deployment types are more for picking which systems to install on, such as a 32 bit deployment and a 64 bit deployment. This way Using this method will also remove the old version from the available software for users to install. I would love to know because this is how I do all of my deploys. This lead me to a new problem Brian. When I try to superseed Endnote 7. I was going to suggest this as well. I have a similar issue with the Outlook CRM client. I actually use the client version when you right click and hit properties on it.

The other option is check the registry. Remember, when running things in a TS, it's not running as you and thus you can't just expect it to be able to access things on the network. This goes for the driver store in your second script also. It's makes no sense in ConfigMgr to ever access something off of a UNC -- that would mean systems at your remote locations would come back across the WAN.

Place your files into a package and access them from there which will always the set as the current directory and be local. There's no need to use cmd. PowerShell is an. Adding debug logging output to your scripts where the output is added to a local text file.

Then you can see exactly what is failing and hopefully figure out why. As it did not work for me in this instance I have then proceeded to test using the TS method Script 2. I tried with just 'powershell. Do you have a preferred method for installing Printer drivers for a new deployment? Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Configuration Manager - General. Post questions here that are not appropriate for the other Configuration Manager specific forums, AND after you have already searched for your answer.

Sign in to vote. Hi all; I can find all kinds of websites that explain how to deploy drivers during OSD. All and any comments greatly appreciated. Saturday, February 8, AM.