ownload the Windows Assessment and Deployment Kit (ADK) for Windows 10 to get the new and improved deployment tools used to automate a large-scale deployment of Windows 10. The Windows ADK includes:
Windows 10 build 10240 has been released to the Fast Ring. That’s what I’m running on my laptop now. There were heavy rumors yesterday that this is the to Release To Manufacturing (RTM) build and is the one to be publically available on July 29th. But there is no hard confirmation on this by Microsoft yet Build 10240 now available for Windows Insiders in Fast and Slow rings.
“Over the past few days we’ve been preparing our release pipelines and processes, and this build is one step closer to what customers will start to receive on 7/29 …
On Monday we announced that builds from here on will only be available through Windows Update, so to get this one you can either wait and it will be installed automatically.”
Here’s how you prepare to roll it out in your company.
In a previous blog post I wrote about the update you needed for your KMS server to be able to activate Windows 10 clients. Read about that in KB3058168: Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows
Meanwhile Microsoft has also published the Windows 10 client KMS activation which keys can be found here Appendix A: KMS Client Setup Keys
Operating system edition
KMS Client Setup Key
Windows 10 Professional: W269N-WFGWX-YVC9B-4J6C9-T83GX
Windows 10 Professional N: MH37W-N47XK-V7XM9-C7227-GCQG9
Windows 10 Enterprise: N: NPPR9-FWDCX-D2C8J-H872K-2YT43
Windows 10 Enterprise N: DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4
Windows 10 Education: NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
Windows 10 Education N: 2WH4N-8QGBV-H22JP-CT43Q-MDWW
Windows 10 Enterprise 2015 LTSB: WNMTR-4C88C-JK8YV-HQ7T2-76DF9
Windows 10 Enterprise 2015 LTSB N: 2F77B-TNFGY-69QQF-B8YKP-D69TJ
Do note this is the key you use when you activate the Windows 10 Client against a KMS server. It is not the KMS license server key. That one you’ll need to obtain from your valid Microsoft licenses.
Windows 10 will be available on July 29th 2015. Microsoft has prepared for this by already making an Update(KB3058168) that enables Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012 Key Management Service (KMS) hosts to activate a “later version of Windows”. This must means Windows 10. I do not know if this means that is even for Windows Server 2016. Windows 10 will be activated by a KMS server running this update but it might.
Select the version you need for the KMS server or servers you use and install them.
Microsoft has released a free ebook of “Introducing Windows 10 for IT Professionals, Preview Edition”. You can download the ebook here. Special thanks to Mark Swinkels
All drivers are stored in the so called DriverStore, which is located under %SYSTEMDRIVE%\Windows\System32\DriverStore.
With the built-in command line tool pnputil you can add or remove drivers.
How does it work?
Deploying Windows 10 with MDT 2013 Update 1 Preview
Next you need the MDT 2013 Update 1 Preview. To get the preview, you need to first join the MDT Group on Microsoft Connect, if you’re not a member already. Then, prior to downloading the actual preview bits, you’ll need to grab the Windows ADK for Windows 10 Technical Preview, which is a prerequisite for running MDT.
The Build number which the best to use is the Windows 10 Technical Preview with build number 9926 
So i installed some apps automaticly 
Doing some bug check/feature check Keep you posted
The Enterprise Client Management team is happy to announce the availability of the Microsoft Deployment Toolkit (MDT) 2013 Update 1 Preview!
What’s new with MDT 2013 Update 1 Preview:
To Do List:
(New members must first join the MDT group of the Client Management program on Connect.)
Windows 10 ADK supports Windows 7, Windows 8.1 and Windows 10 deployments.
Windows Image Configuration Designer (WICD), pronounced Wicked ? 🙂 Is supposed to be able to build a customized mobile or desktop image, and also create provisioning packages that allow you to customize a Windows device, without re-imaging.
New upcoming version of MDT is in development, not much info presented yet, but a few items were mentioned in the session:
Windows 10 Deployment and Upgrade Support, as well as updated Task Sequence binaries
Removed deprecated components from Deployment Workbench, and making OSD more accessibility compliant.
MDT documentation will be on TechNet (removed legacy help file and DOCX)
1. Mount boot.wim file
Dism /Mount-Image /ImageFile:”D:\DeploymentShare\Operating Systems\Windows Server Technical Preview\sources\boot.wim” /index:1 /MountDir:D:\offline
2. Copy the dism.exe and DISM folder from the Windows 10 Technical Preview boot.wim file to your deployment share, in my case D:\DeploymentShare\Tools\x64.
The dism.exe file and DISM folder are found in the X:\Windows\System32 on your boot image (once booted), or D:\Offline\Windows\System32 if you just mounted the boot.wim.
3. Unmount the image|
Dism /Unmount-Image /MountDir:”D:\Offline” /Discard
4. Edit the Task Sequence
After copying the files, add two run command line actions to your Windows 10 Technical Preview and Server vNext Preview task sequence after Preinstall – Enable Bitlocker (Offline)
Copy WTP dism.exe
cmd /c copy %deployroot%\tools\%architecture%\dism.exe x:\windows\system32\ /y
Copy WTP DISM subsystem
cmd /c copy %deployroot%\tools\%architecture%\dism\* x:\windows\system32\dism /y
5. Deploy Machines
If you try to PXE boot a Windows 10 or Server vNext Technical Preview VM running on Hyper-V in Windows Server 2012 R2, you are greeted by a nice error message: Boot Failed. EFI Network. Failed Secure Boot Verification.
Until there is an update available turn off secure boot for the Gen 2 VM.
