Why updating deployment share
MDT can allow you to deploy Windows with very limited interaction from start to finish.
It can work by booting from a CD, a USB, or when paired with Windows Deployment Services on Windows Server, MDT can be used across the network starting with PXE boot.
You only need Deployment Tools, Windows PE, and USMT (optional).
You might also include ICD with the installer for options to customize Windows 10 images.
The task sequence is a procedural order of steps that the deployment process will automate for you.
You can choose which OS is installed, applications used, and various settings, including custom settings to script parts of your imaging.
As far as getting MDT up and running though, we can proceed with the minimum structure in these areas.
Lastly, when you have an operating system, drivers, and applications available, you can tie them all together using a Task Sequence.
You will proceed forward by importing operating systems, which can be from your install DVDs or ISO files or from captured images. Each one of these areas could be its own future topic with different options and best practices.
Once you are all done, your tree will be much more populated. Right-click on each share and explore the properties of that share with which features you will use in your environment.
After you finish modifying any rules or settings on the share, right-click it again and choose Update Share.
You know…every time you have to install an OS, you have to search for drivers on the vendor page because the drivers are not included on the installation media.
When deploying with MDT, the most common error message is the one for the network card drivers: “A connection to the deployment share “…” could not be made.