Building a Windows 10 Reference Image Using MDT 2013 Update 1 [Video]
Here we go again. It’s that time to start building your reference image for Windows 10. This video is a long one, but it’s jam packed with everything you need to get yourself up and running with MDT 2013, deploy applications, get Windows Updates from WSUS, capture your deployment for later and automate your deployment by 95%. Also, if you stay tune we will take our reference Windows 10 image and deploy it to see how everything works at end.
why ‘not able to connect to internet’ a private network for a Win 10 reference image??
and why do you not use a sysprep and capture sequence?
This seems counter intuitive to Microsoft way of imaging computers.
Thanks for all your hard work. I have learned alot about MDT and followed thru all the evolutions of the mdt that have been brought out by Microsoft.
I don’t understand why we need to change methodology at this point in the game.
Any input on why the need for having a reference machine on a private network will be greatly appreciated.