

Copy the customsettings.ini file to the Settings package created in the MDT task sequence wizard earlier.Ĥ. After the wizard completes, the new customsettings.ini file will be saved in the \\server\DeploymentShare$\Control folder.ģ. In the MDT Workbench, select “Database” and then select “Configure Database Rules”Ģ. The information in the customsettings.ini file provides the “rules” that the computer needs for connecting to the database during the deployment.ġ.
Mdt checkbox application wizard series#
So, up to this point in this series we have put most of the pieces in place that are necessary to allow both Dynamic operating system deployments that are driven by the MDT database as well as perform Application Replacement during both Computer Refresh and Computer Replace scenarios.

Setting up a task sequence to use the MDT database. OSD and the MDT Database…connecting all the dots from the previous four posts.Modifying the RetrievePackages stored procedure. Application Replacement #1…this post is the reason I started the series.Assumptions and creating the MDT database.These processes will make your OSD setup much more dynamic. This is the last of a five part series on utilizing the MDT integration into Configuration Manager to improve your Operating System Deployment functionality.
