First, you should ALWAYS use MDT for building and capturing the master images
of Windows operating systems that you plan on deploying to computers in your environment. The main reason for this is that with MDT
you can preconfigure the default user profile to customize the desktop of the user who will be using the computer you're deploying Windows onto. That's because with MDT
you can configure user settings for the built-in Administrator account and then use the CopyProfile setting during deployment to make these the Default User settings on the target computer.
Why does CopyProfile work with MDT
but not with SCCM
? Because during Lite Touch Installation (LTI) MDT
runs its task sequence in the context of the built-in Administrator account while SCCM
runs its task sequence in the context of the LocalSystem account. Now you could actually make CopyProfile work with SCCM
deployments if you wanted to, but it takes a lot of painful scripting to do this, so why bother if MDT
already does it so easily?