Hi
I hope everyone is well and can advise. I've been using MDT for about 3 years, for Windows 7 onwards. I'm trying to build a Windows 10 Reference build I'm on MDT 2013 Update 1, and I have built a task sequence as per the advise here:
All is well when I deploy the task sequence to a virtual machine until it gets to sysprep. The MDT Monitoring node is showing the task sequence at 92% completed (step name Executing Sysprep ) but it is not progressing.
On the VM, it is sat at a login screen, and if I try to log in, I cannot do so - the admin account is disabled. The MDT logs are not copied to the log share, because the TS isn't completed, and I can't access the logs on the hard disk of the vm, as I keep getting told the admin account is locked.
I need to know how to either add a local account into the VM, so that I can log onto it and look at the logs, or I need to know how to let the sysprep process complete, so thathe wim file is created and copied.
Yesterday I also read this thread about enabling the admin account
I have checked the xml file and the RunSynchronousCommand is present in the file.
Is this something that I am doing wrong, or has anyone else had the same issue.
How do I add an second Admin account to the Task Sequence, so that I can access the VM to look at the logs. Ultimately I need to understand why sysprep is not working as it normally does. It is probably because the admin account it locked out/disabled. I should also mention that I can run reference builds on the other task sequences for several different operating systems successfully, (I've updated my wim files on all Operating systems successfully in September using reference builds), and as far as I can tell the Task Sequence for the Windows 10 Reference build is the same as the Windows 8.1 Task Sequence.
Any advise gratefully accepted, we can't roll Windows 10 out until I masterthe Reference build.
Regards
John
Regards, John