And I have setup the customsettings to not skip the admin password and enter it in the Windows Deployment Wizard. I have tried setting the admin password in the TS then in customsettings setting it to skip, I have tried what was outlined in this article. My MDT Image is activating the Administrator account, but not setting the password at all. I know this isn’t a support forum, but thought I would ask anyway. It goes without saying that this is a big problem as having to manually log in breaks the “no-touch” part of what was once a truly no-touch process with MDT 2008.Which brings me to my question: how can we get MDT 2010 to stop overwriting our custom-named administrator account before the first post-OS-installation reboot?Many thanks for any help you might provide.Like. After the OS installation is complete, the box reboots when it tries to do its first AutoAdminLogin as the user Batman, we get an error message indicating bad username and password because an account of that name no longer exists.įrom there we can manually log in as Administrator and re-rename the account back to Batman, and it resumes the build process with the task sequences. In MDT 2010, however, somewhere in the OS installation process MDT seems to be reversing the custom naming of the admin account and changing it back to Administrator. In MDT 2008, we would provide the account name Batman and its password for the AutoAdminLogin process for all subsequent reboots, and it worked like a charm. Back when we were first building out MDT 2008, we used N-Lite to change (among other things) the built-in administrator account name from Administrator to, let’s say, Batman.

We are nearly finished, but we have a pretty major snag. You just might be able to help me outAt my job we are in the process of migrating from MDT 2008 to MDT 2010 (we are only deploying XP SP3). Handy if your security manager tells you to start using a new admin password immediatly as there’s just one setting to change.

Mdt change administrator account name