You may notice in many cases that the method of driver installation utilizing the FMSCUG Driver Installer results in very large packages, in some cases up to 4GB depending on the model, while other times the package may be more around the 400MB mark. For smaller packages, this is fine, however if you are like most SCCM administrators, you don't want to take up the space and/or kill WAN links distributing large packages for each model. There is a solution - and it's called 7-Zip!
Welcome to the Fargo-Moorhead System Center User Group! The purpose of this site is not to replace existing resources, but rather to provide IT professionals in the Fargo-Moorhead and surrounding area a centralized place to find those resources and be able to ask for help from other community members who may have shared the same or similar experiences in their environments. If you are in the area and use System Center Configuration Manager or administer GPO in your environment, please sign up! It’s quick and free, and even sharing something you feel is small may help someone who is just beginning and stuck in a rut. Initial focus will be around systems management, but the scope of topics certainly won't be limited to just that. Have fun!
Where: 200 45th St S, Fargo ND 58104
Wild Rice Room (Use the Northwest '200' entrance, park anywhere)Date and Time:Thursday, December 8, 2016 -19:00 to 21:00
I would like to announce the general availability of the FMSCUG driver installer, which is free for use within your task sequences to automatically launch scripted driver installs. This application gives you a new option for installing drivers which allows you to utilize your vendor's EXE format drivers (or other formats really), avoiding timely imports into SCCM, and allows you to utilize the power of scripting in order to install the drivers with any logging/switches you want.
Just writing this to let any who are wondering know - I was able to install 1511 onto a SQL Server 2016 instance - so far so good it appears! The Microsoft notes only say 1606 is supported with SQL 2016, but wanted to give it a try. Will update this post if anything changes!
Writing this to help any out who may be encountering this issue. I upgraded the ADK in my test lab this weekend, and when I imported the new boot images into the console, it failed with the following message: "The specified file can not be imported. Make sure the file is not read only and you have read and write access to it." The fix for me? Reboot after you update the ADK. Once I rebooted, I was able to successfully import the new boot WIM.
Just finished up the initial version of a project I started over the weekend I am calling FMBIDST (short for Boot Image Driver Servicing Tool); It's a GUI for DISM (with a few things like retries, etc. on errors). You can use this to add drivers into your boot images without having to wait on the SCCM console or having to remember DISM commands.
Link to the ZIP file with 32-bit and 64-bit installers in this post
This write up is mostly a problem description, along with a conceptual solution which is working but being tested at the moment. This testing is being done with OS X 10.11.5 El Capitan.