There may be times when you, for one reason or another, have to perform a manual step as part of creating a reference image. This could be anything from installing a finicky or old piece of software that doesn’t have an unattended installer, making manual changes, or anything else that for whatever reason can’t be automated. When this happens, you need to temporarily pause or suspend the Task Sequence so that you can perform whatever manual steps are needed. So, how do you do that?
In the previous parts of this series, I covered setting up MDT and all the customizations that are necessary to automate the process of creating a reference image. Now that MDT is configured, we can capture our first reference image.
Now that we’ve installed everything, imported the OS, and created a Task Sequence, we need to make some customizations to the CustomSettings.ini and the Bootstrap.ini. Both files can be accessed one of two ways:
Now that you have MDT and the ADK installed, we need to set up a deployment share in MDT. Regardless of whether this is a clean install of MDT on a dedicated box or your existing MDT server, we’re going to start off by creating a new Deployment Share that will be dedicated to reference image creation. Continue reading
When it comes to deploying an operating system to a computer, speed and accuracy are the name of the game. If you’re installing applications that are common across your organization as tasks in your OS deploy or installing the latest Windows updates after the deploy finishes, you can save tons of time by using a reference image.
If you try to manage BitLocker drive encryption on a computer that has had a user type in his/her PIN too many times, you may get this error:
BitLocker Drive Encryption Error
The TPM is defending against dictionary attacks and is in a time-out period.