![]() 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) Required: Package ID property of the boot image where DaRT should integrated, e.g.Required: Specify the name of the Primary Site server, required for locating the boot image information (if the SMS Provider role is located on another server than your Primary Site server, specify that server name instead).Below is a list of the parameters and their usage: Running this script successfully, requires a couple of parameter input. You can find the script in our SCConfigMgr github repository:Īdd-CMBootImageDaRTComponent.ps1 Script information Usually, the Primary Site server would be a suitable server for all of these components to be installed, however if you decide to run the script against my recommendations, ensure these requirements are installed before attempting to run the script. Below is a list of what you’d need to have installed on your Primary Site server: ![]() Script requirementsīefore you run the script, there’s a few requirements that needs to be in place for it to fully function. This post will not cover any of the benefits of doing this integration, it’s merely a way of contributing the script that I put together that has been published in our SCConfigMgr github repository for some time now. Some time back I found myself integrating DaRT a little bit more than I would allow myself for manually going through those guides, hence here’s the PowerShell way of doing all of this. Over the years it’s been relatively common to include Microsoft DaRT into your boot image used for OSD in ConfigMgr and several blog posts have explained the process with a step-by-step approach. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |