![]() Using the scriptįor demonstrating how the script works, I’ve imported a test boot image named ‘Boot Image with DaRT’. This will allow for future re-distribution actions without having to re-run this script. The script will make above mentioned changes to the original boot image file specified in the Image Path property of the Data Source tab. Additionally, another required DaRT file named DaRTConfig.dat will be added into the mounted boot image.Īt the end if all of the above was successful, the script will dismount and commit all changes made to the boot image. The boot image will then be mounted to the temporary location specified as parameter input and DaRT components expanded into the mounted boot image. All of these three installations path locations are key for the functionality of the script, if any of them can’t be located due to one of the components are not installed, the script will fail.Īfter this the specified boot image will attempted to be located through the SMS Provider and backed up. Next, the Microsoft DaRT installation path is queried. Once located, it will attempt to find the Microsoft MDT installation path, also by querying the registry. When executing the script, it will first attempt to locate the Windows ADK installation path from the registry on the local system. Optional: When added to the command line, the script will attempt to update the distribution points where the boot image is distributed to.Required: Specify a temporary empty folder where the boot image can be mounted for adding the DaRT components.P01000AB (also known as the Image ID in the ConfigMgr console) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |