After imaging a machine with MDT, it does not get group policy settings until after rebooting. This posed a problem for certain workflows where some settings were needed immediately. The easiest workaround I could find was to create a provisioning package with Windows Configuration Designer. However Microsoft's documentation regarding silent installs lacks the depth needed to be successful (see blue note here). Below are the steps I took to successfully deploy provisioning packages silently with
One of the biggest slowdowns when reimaging an entire lab of computers is the naming process in MDT. Of course, you could simply do a refresh deployment but often you just want to completely wipe everything on the machine and start fresh but also keep the same computer name.
This can easily be done using a UserExit.vbs script in just a couple steps.
- Open up your MDT deployment share and add the following two