MDT 2013 - Windows 10 1703 - AutoAdminLogon Bug

So, it seems that’s a little bug when using MDT 2013 and Windows 10 1703 (Creators Update).

Basically, the autoadminlogon stops working and during the task sequence you’ll be asked for Administrator password.

To workaround this you can do the following:

1. Open customsettings.ini file
2. Add the following line: SkipAdminPassword = YES
3. Add the following line: AdminPassword = “youradministratorpassword”

And it’s all done!

MDT 2013 Update 2 - Bug When Changing Application Command Line?

So today I'll talk about something odd that happen just yesterday.
I've published a new application in MDT and added it to my task sequence (TS).

After that I've noticed that I had to change the msi file name so just went to DeploymentShare\Applications, changed the file name and also changed the install command-line in MDT to match the new file name.

Basically the changes was from a filename with spaces to a filename with "underscores".
After testing the TS, I've received a return code error (1639 - invalid command line argument).

Double-checked everything and after looking at ZTIApplications.log file I've found out something strange.
It seems the TS for some reason didn't assume my install command-line changes. And it was running the command without underscores and with spaces:

So...for my surprise, and to solve this issue, I had to go to my TS again, select the application and the browse for published applications and select that one (Cirrato Client) again.

This solve this issue that I don't remember to see in previous MDT versions.


Hope this helps people having the same same strange behavior! ;)