<div>
Met deals with creating an image you want to deploy to a network booting pxe system that will be directed to boot and install.<br />
You need Windows 10 volume licensed to achieve this.<br />
The image has to include the requisite drivers for the systems into which they will deploy.
</div>


<div>
can you please elaborate on this ?<br />
<br />
You need SCCM installed<br />
You need MDT installed ... on the same machine as SCCM ? <br />
You need to integrate MDT with SCCM<br />
<br />
---what does Zero Touch means in a technical way ? and why ZT exists just with MDT integration with SCCM ?<br />
Do we also need WDS ?
</div>


<div>
You get the machine network boot UUID or the MAC address of the network<br />
Or you merely boot using network boot, the DHCP server option 66 and 68 advertise the IP of the tftp server from which the image is available and the second option directs the bootup what it needs to retrieve to boot the system and run the install or present the menu to the person in front (MDT/mds) ..<br />
How many systems, what is your timeline?<br />
Storage in the system, ssd's will speed up?
</div>


<div>
WDS not mds<br />
Windows deployment service <br />
MDT Microsoft deployment toolkit<br />
<a href="https://www.petri.com/deploy-windows-10-using-mdt-wds-part-1-create-mdt-deployment-share" rel="ugc">https://www.petri.com/deploy-windows-10-using-mdt-wds-part-1-create-mdt-deployment-share</a><br />
WDS and MDT setup<br />
<br />
The DHCP server needs to be running on Windows.<br />
Do you have a test network to avoid getting an existing system that is misconfigured or is erroneously triggered to start from network.<br />
Deals with whether you explicitly define the UUID /MAC address &nbsp;that is authorized to boot and get the OS deployed.<br />
<br />
If it is set to install on any system that network boots, you might wipe/reinstall he OS on he wrong system.
</div>


<div>
ZTD stands for &quot;Zero Touch&quot; meaning you don't have to toucbthe a chine at all.<br />
<br />
If you just use MDT and/or WDS then you usually have to &quot;touch&quot; the workstation being deployed. Even if you only touch it to start the PXE boot or to insert a USB key... So those are &quot;light touch&quot; scenarios.<br />
<br />
With SCCM, the agent can remotely reboot the machine and can prestage the installation. SCCM can even remotely deploy the agent. Meaning that as long as the machine is on the network, an OS deployment can happen... Even from thousands of miles away. True zero touch. <br />
<br />
ZTD only &quot;requires&quot; SCCM. &nbsp; But configuring OSD in SCCM does install and configure WDS in the background. However you should NOT manually install or change WDS. SCCM will manage it.<br />
<br />
MDT is not strictly necessary for ZTD with SCCM but is strongly recommended. SCCMs task sequencing is pretty bare bones and even Microsoft recommends integrating the two... This recommendation is not about ZTD though. Even if you are doing Light Touch Deployments. MDT is just better in so many ways for deployment that layering it on SCCM is a best practice.<br />
<br />
Hope that clears up ZTD specifically for you.
</div>


<div>
Cliff,<br />
<br />

<blockquote>
ZTD only &quot;requires&quot; SCCM. &nbsp; But configuring OSD in SCCM does install and configure WDS in the background. However you should NOT manually install or change WDS. SCCM will manage it.<br />

</blockquote>
<br />
I have SCCM installed..the only place where I see WDS mentioned is on the DIstribution Point properties as shown on the screenshot below.<br />
Even if I tick the checkbox , it will not install it.<br />
<br />
- regarding your point on MDT with SCCM, I am not sure why you say it is recommended , what does it add to SCCM ? Anything missing in SCCM &nbsp;that &nbsp;MDT has ? I know MDT free but SCCM not...you would think SCCM will have everything.<br />
&nbsp;<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2019/12_w49/1437941/sccm.JPG" target="_blank" title="s (83 KB)"><img alt="s" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2019/12_w49/800_1437941/sccm.JPG" /></a>
</div>


sccm.JPG

<div>
My impression is that because MDT is free, the SCCM team didn't feel it necessary to re-invent the wheel and find ways to do what MDT does within SCCM. So instead they just went the &quot;integrate them&quot; route. &nbsp;I don't work for Microsoft nor know anyone still with those teams so any comments I'd make about why would just be speculation and honestly off topic. <br />
<br />
Instead I will just say that yes, MDT has a lot of functionality that SCCM's native OSD does not have. That's an easy Google search and therefore isn't worth cutting and pasting multiple hours worth of reading here.
</div>


<div>
mdt can do a zero touch. you just edit the customsettings.ini and tell it to install this operating system &nbsp;<a href="https://www.reddit.com/r/MDT/comments/cqi8oo/zero_touch_deployment/" rel="ugc">https://www.reddit.com/r/MDT/comments/cqi8oo/zero_touch_deployment/</a> but you also need a way of pxe booting to the litetouch.wim.<br />
You can use WDS or other PXE server to do this. &nbsp;ServerA is one method <a href="https://www.vercot.com/~serva/" rel="ugc">https://www.vercot.com/~serva/</a>&nbsp; <br />
<b>Can someone clarify the ZT Deployment concepts and where MDT and WDS fit in SCCM</b><br />
MDT can add functionality to SCCM as explained above<br />
Without using SCCM you can use WDS and MDT together to do a Light Touch or a Zero Touch installation. MDT needs a pxe server.<br />
SCCM has its own pxe server and can do both ZTI and LTI installations and more (updates/application installs, anti-virus, monitoring and so forth. Each section can be a book unto itself.
</div>


jskfan

<div>
&quot;but you also need a way of pxe booting to the litetouch.wim.&quot;<br />
<br />
That is why MDT without SCCM will never be truly ZERO touch. &nbsp;It may be a single boot touch, but requires some sort of touch. &nbsp;SCCM, with remote agent deployment and the way the agent can pre-provision thebPE environment, can truly be a zero touch 100% remote deployment without getting in a OXE boot loop. <br />
<br />
I've seen even experienced deployment folks get confused. Zero touch isn't about the automation. As you said that can be done with MDT. &nbsp;Zero touch is about literally no on-site adjustments to PXE, pressing F12, or any of that. &nbsp;The only reliable way to achieve that is an agent which MDT doesn't have. SCCM does.
</div>


<div>
The point I want to get to, is if I have SCCM, I do not have to use another tool which is &nbsp;MDT &nbsp;to do Zero Touch OS deployment<br />
<br />
SCCM install prerequisites do not require MDT. &nbsp;<br />
<br />
SCCM Check box about PXE, will be enough to implement ZT OSD ? it stated that it will install WDS in the Background. Though I ticked that Checkbox and did not see any WDS services running.
</div>


<div>
MDT might be needed to build the package without actually installing one and then sysprep/image it using wds to create an image.<br />
<br />
Check whether the role wds got installed.
</div>


<div>
All right..<br />
The take away is if you Have SCCM , it is enough to do ZT OSD without MDT tool.
</div>


<div>
<div class="content wysiwyg-content">
Windows 10 Zero Touch deployment.<br />
<br />
I would like to know exactly what ZT deployment is. in some articles, they mention MDT needs to be installed and integrated with SCCM. So with SCCM by itself we cannot do ZT deployment ?<br />
I have also seen WDS mentioned in some articles. <br />
Can someone clarify the ZT Deployment concepts and where MDT and WDS fit in SCCM ?<br />
<br />
Thank you
</div>
</div>


Windows 10 Zero Touch deployment.

I would like to know exactly what ZT deployment is. in some articles, they mention MDT needs to be installed and integrated with SCCM. So with SCCM by itself we cannot do ZT deployment ?
I have also seen WDS mentioned in some articles. 
Can someone clarify the ZT Deployment concepts and where MDT and WDS fit in SCCM ?

Thank you

Windows 10 Zero Touch deployment.

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Systems Center Configuration Manager (SCCM, formerly known as Systems Management Server) is Microsoft’s system software for managing large groups of not only Microsoft computers, but those running other operating systems, such as Linux, OS-X, and various mobile technologies.