I use AutoPkgr (mac program, https://github.com/lindegroup/autopkgr/releases ) to automatically check for updates, download, and generate packages out of Driver Packs and Bios updates ( https://github.com/jeremylarose/autopkg-recipes ) daily. … Then I use Salt ( https://docs.saltstack.com/en/latest/ ) to deploy them, with this simple state…

{% set model = grains[‘productname’] %}

‘c:\salt\drivers{{ model }}.exe’:
file.managed:

• source: ‘salt://win/drivers/win10/{{ model }}.exe’
• makedirs: True

install_drivers:
cmd.run:

• name: ‘“c:\salt\drivers{{ model }}.exe”’
• onchanges:
• file: ‘c:\salt\drivers{{ model }}.exe’

@Wayne-Workman

1. Be on a Mac, version 10.8 or higher
2. download AutoPkgr… https://github.com/lindegroup/autopkgr/releases
3. Open AutoPkgr and install Git and AutoPkg with the provided buttons
4. In the “Add a repo URL manually” box, add the following to get many Dell drivers and software … https://github.com/jeremylarose/autopkg-recipes.git
5. right click on any pkg you want and click “Create Override”… this is to protect you from any malicious changes ( https://github.com/lindegroup/autopkgr/wiki/Overrides-and-Trust-Info )
6. now you can right click on the created local recipe (Recipe identifier changes to local.pkg…) and click run this “Run this Recipe Only” to create that package at ~/Library/AutoPkg/Cache

that’s it, although…

7. you’ll likely want to checkmark all the packages you want and setup a schedule to run automatically
8. you’ll likely want to create your own recipes for different models, which you can essentially duplicate the ones I already have created and modify, or just ask and I can probably do it real quick

bonus…

9. I created a PkgOrganizer PostProcessor that will organize them in a PkgOrganizer folder, to add that…
10. in AutoPkgr, click “Folders and Integration” then click “Configure AutoPkg” button and paste this into the postprocesser… com.github.jeremylarose.SharedProcessors/PkgOrganizer

Now you have silent installers to do whatever your want with. I find this tool extremely handy, saves alot of work. Its also amazing for macs with munki.

@fog_rob I am experiencing this issue as well, not related to clients whatsoever, the web interface just doesn’t auto-encrypt the plaintext password in the web interface.

@jackiejack you don’t need another machine… install virtualbox on your current machine… you can export it when you get everything good to a network share somewhere

@jackiejack definitely start from scratch. Its quick enough, and if this is your image your gonna use on a bunch of machines, you want it to be perfect… plus it’ll be easier to document all the steps you do.

@jackiejack you could use a physical machine, but virtualbox is easier and transerable… your machine doesn’t matter. I actually use virtualbox on a mac… from some notes… “install Windows using Audit Mode* in virtual box with 4gb ram, 2 processors, 50gb dynamic hard drive, bridged adapter”

@jackiejack yes, first thing you do is go into audit mode… do the windows updates in the virtualbox before sysprep (be sure to select bridged network adaptor) so you’ll be able to upload to fog. Put network drivers for all models in c:\windows\inf folder somewhere. You could install software before sysprep if you want. The only software we install before sysprep is Microsoft Office and do the rest post image.

@jackiejack PDQ is more of a remote deployment type deal, but I suppose it could work. Puppet is open source. I found Salt easier to use, which is open source as well, but beware that you need to know what your doing with these and make sure they are secure because they give ALOT of control, but if in place and once properly setup, can be used to automate everything. A simple free solution is create silent installers in a central network share and combine PDQ for remote deployment (free if you just run bat files from the central share) and WPI (http://www.majorgeeks.com/files/details/windows_post_install_wizard_(wpi).html) for locally running post installs/configs. The trick is, you have to create silent installers for everything. You may also have luck with Fog for post config and software.

I would actually put the minimal amount of software and configuration on the image as possible… create the image with virtualbox and snapshot before every sysprep so you go go back and do windows updates regularly. Use a tool like WPI, or even better, config management tool like salt/puppet for post software install/config… but yes, you have the right idea… make sure to put the network drivers for each model on the image as well

I’ve had luck with sysprep up until 1703, anyone else having issues or have successfully sysprepped Windows 10 Enterprise 1703?

I get the same exact error, every time, for every machine and then after rebooting once, it works every time. This just happened all of a sudden. Wireshark doesn’t see any tftp servers.

@Quazz said in Post Sysprep Driver Install:

But say you work repair service where every possible model under the sun gets dumped for you to fix, then you need a broader solution.

warning with snappy driver installer… the project was hijacked and now includes malware… therefore a fork was generated called snappy driver installer origin…

https://sourceforge.net/projects/snappy-driver-installer-origin/