In the properties of a given package, you can set your data source to update on a schedule.
Just go to the Data Source tab, then check the Update Distribution points on a schedule box, and I'm sure you can select an appropriate schedule from there.
Do not add all your NIC drivers to your boot image, it’s overkill and unnecessary increase the size of the boot image. In the case of a vanilla deployment or after a build and capture, you use Operating System Images to import the WIM files.
To add drivers to the boot image : We will now import the Windows 10 WIM file for Windows 10 deployment. In an Upgrade task Sequence, you will need to have the Full media imported in Operating System Upgrade Packages.[/su_box] We will start by importing the default Install.
In Configmgr 2012, The option is replaced with deployment Type means ,you can have multiple deployment types (Both Local install and Virtual package) for single application.
One important thing in any OSD project, is to make sure that every machines deployments are up to date.
Before deploying Windows 10, make sure that your Software Update Point is configured to include Windows 10 patches.
You can monitor this process in the SCCM Console : [su_box title=”Important note” style=”glass” title_color=”#F0F0F0″]If you have created any custom boot images in previous version, you won’t be able to manage it (customize, add drivers, ect…) through the SCCM console. Other version could still be used but you’ll have to manage them outside the console using DISM.[/su_box] Before launching your first boot image you must include your Windows 10 drivers into the boot image.
Our rule of thumb about drivers is to try to boot a certain model and if it fails, add the drivers.