How to deploy Windows 11 21H2 (Microsoft Deployment Toolkit and Windows Deployment Services)

[@danny_moran]

I have uploaded an updated guide on how to deploy Windows 11 22H2: kzbin.info/www/bejne/rXrTY4yKg7udfs0

[@jayanthsept5]

Thank you Danny. I'll try your suggestion for removing error. Really appreciate the way you are helping many IT professionals like me 👍👏

[@danny_moran]

Thanks for watching!

[@Tech215Studios]

Great Video - one suggestion please boost the volume, it’s very hard to hear you. Just some kindly advice - keep up the great work!

[@danny_moran]

Thanks for your feedback. I have recently upgraded my audio hardware, so future videos will have much better audio quality. Thanks for watching!

[@TheBearAndTheBull]

This was fantastic and a nice touch to include the Rules and Bootstrap info to bypass a lot of the input sections would love to learn more to make it completely unattended. Will be using this for my training on VM's.

[@danny_moran]

The automation rules included just scratch the surface of what's possible. There are loads of things you can do and there are quite a few guides online covering additional commands. Thanks for watching!

[@FrankTranDesign]

This is incredible. Thanks for sharing in such a concise manner!

[@danny_moran]

Thanks for watching!

[@double-you5130]

thank you so much. i kept getting stuck and there is sooooooooooooo much support materials out there its very time consuming to go through everything. this is the simples way anyone has ever explained this to me. i did this widn 2012 server ages and ages ago but then i lost interest.. but with windows 11 its a good way to deploy it thanks again : )

[@danny_moran]

Thanks for watching!

[@kurdorrr1840]

Man again , i really like your tutorials : )

[@danny_moran]

Thanks for watching!

[@PaulThomson-fq9gw]

Thankyou very much for this guide, its very clear and instructive and has helped me a lot.

[@danny_moran]

Thanks for watching!

[@Tech215Studios]

Dan I absolutely love your videos, you’ve been amazing. But please boost ur volume in your voice overs. 😚

[@danny_moran]

Thanks for the feedback. I have since upgraded my audio solution, so new videos have much better audio. Thanks for watching!

[@Tech215Studios]

@@danny_moran niiiice!!!

[@B4znyc]

Good video please raise your recorded volume

[@danny_moran]

Thanks for your feedback!

[@elitehaxxor8025]

Wasn't even low.

[@txsla]

i do find it pretty low as well

[@trevormasterson8035]

Hi Danny. Brilliant videos and so helpful. Can I ask if you go to each pc/laptop home site and download drivers or do you get them from device itself using a powershell command. Thank You so much.

[@danny_moran]

To actually get the drivers, I go to the manufacturers website and download the latest drivers for the models of workstation I am using. To install the drivers, I have automated it using MDT. It's something that I forgot to cover in this video, but, the below blog post should contain everything you need to do to get the driver installs automated. I use the "Scenario #3 - Total Control" method. www.deploymentresearch.com/mdt-2013-lite-touch-driver-management/ Thanks for watching!

[@AbdullahOllivierreIT]

Summary of the Video: How to Deploy Windows 11 21H2 using Microsoft Deployment Toolkit (MDT) and Windows Deployment Services (WDS) Step-by-Step Process: 1. Initial Setup: • Clean install Windows Server 2022, added to the domain. • Install the Windows Deployment Services (WDS) role: • Go to Server Manager, add the Windows Deployment Services role. • Select both Deployment and Transport Server options. 2. Download and Install Required Tools: • Download the Microsoft Deployment Toolkit (MDT) and Windows 11 ADKs: • Search and download the latest version of MDT. • Download Windows 11 ADK and the Windows PE add-on. 3. Install the Software: • Install MDT by running the setup and following the default options. • Install the Windows ADK and Windows PE add-on, also using default options. 4. Configure Windows Deployment Services (WDS): • Open WDS from Server Manager, right-click to configure the deployment server. • Integrate with Active Directory, set a path for Remote Install (preferably on a data drive, but C: drive works). • Set PXE server settings to respond to all client computers. 5. Setup MDT Deployment Share: • Open Deployment Workbench from MDT. • Create a new Deployment Share: • Leave default paths and names. • The Deployment Share includes folders for applications, operating systems, drivers, packages, task sequences, and monitoring. 6. Import Windows 11 Operating System: • Mount the Windows 11 ISO file and import the operating system into MDT. • Rename as necessary (e.g., from Windows 10 to Windows 11). 7. Add Applications (e.g., 7-Zip): • Download the application (e.g., 7-Zip MSI file). • Add the application in MDT, specifying the command for a silent install (e.g., msiexec /i /quiet). 8. Create Task Sequence: • Create a new Task Sequence in MDT for deploying Windows 11. • Specify Task Sequence ID and name. • Choose the standard client task sequence template. • Set a product key if necessary, and specify local administrator password. 9. Configure Deployment Share Properties: • Modify Deployment Share properties to suit the deployment (e.g., disabling x86). • Update rules and bootstrap.ini to automate and streamline the deployment process (e.g., specifying domain join settings, skipping unnecessary steps). 10. Update and Generate Boot Image: • Right-click Deployment Share and select "Update Deployment Share". • Choose to completely regenerate the boot image to reflect changes. 11. Import Boot Image into WDS: • In WDS, add the generated boot image (Light Touch PE) to the boot images. 12. Deploy Windows 11: • Boot a device (e.g., virtual machine) to the network and start the deployment process. • Log in with credentials, select the task sequence, and follow the wizard to deploy Windows 11. • Monitor the deployment process in the MDT Workbench. 13. Monitoring Deployment: • View deployment progress and details in the Monitoring section of MDT Workbench. • Confirm successful deployment and software installation (e.g., 7-Zip). The video covers the complete process from setting up a server with necessary roles and software, configuring deployment settings, creating task sequences, and finally deploying Windows 11 using MDT and WDS.

[@danny_moran]

Thanks for watching!

[@Velorreaful]

Amazing tutorial. It helped me so much.🤓

[@danny_moran]

Glad it helped. Thanks for watching!

[@imranahmed2384]

Thanks a lot😊 But can you please briefly explain about how VM takes the PXE mode. Where you have enabled this?

[@danny_moran]

In the settings for the client virtual machine, you can set the boot order. Just set the network adapter to boot before the hard drive. This will tell the virtual machine to boot into the PXE environment. Thanks for watching!

[@chrisgbedessi3276]

Many thanks for sharing this.

[@danny_moran]

Thanks for watching!

[@Roy-cu2iw]

Nice video danny

[@danny_moran]

Thanks for watching!

[@jasoncummings7052]

Very informative and well presented. Thank you. What about environment that have 15 different laptop models? And what about software like O365?

[@danny_moran]

You can use MDT to deploy to any manufacturer and model of desktop or laptop. You can also script the install of Microsoft Office applications by using the Office Deployment Tool. Thanks for watching!

[@alexandresantos1617]

Really want to Thank you for your content. Help me a Lot!! Just One question, if I want to previously customize my deployment tollkit options, like my Domain, my deployment share path, and little options like Default Keyboard and Time Zone, where can I Do It?

[@danny_moran]

If you right click your deployment share, and go to properties, and then rules, you can edit the default rules and the bootstrap.ini file to add those settings. Check timestamp 15:50 for where I add these settings. Remember, once you've updated those settings, you need to update the deployment share and then replace the litetouchpe_x64.wim boot file in your Windows Deployment Server with the newly regenerated one. Thanks for watching!

[@Danielfiks]

Hi, great video. Is the task sequence the same as the unnatended.xml file? I have a standalone wds and I want to skip most of the oobe

[@danny_moran]

They're not the same but they can do similar things. By default, the deployment task sequence should take you to the desktop and auto-complete the oobe. Thanks for watching!

[@gjangkhanh]

Hi Danny, Could we choose the place where Disk partition we should install windows OS into? Example: Users have 2 disk partitions like C: Windows OS and D: Data. WDT should install OS to C drive.

[@danny_moran]

I think there are ways to do this, however, I don't actually remember the last time I deployed an OS to a device with multiple drives. I think it automatically picks 'disk 0' to deploy the OS to. The disk ID would depend on which slot of the motherboard the drive is plugged in to. Thanks for watching!

[@gjangkhanh]

@@danny_moran Yeah, disk 0 slot 0 on mainboard. But how about PC only has disk 0 but multiple partition?

[@danny_moran]

Yes, you can create multiple partitions on the same drive. www.prajwaldesai.com/create-extra-partition-in-mdt/

[@joshyyyboiii2972]

Hi, great video. Very informative! I have a question, how would you deal with multiple boot images? for example in a school if you wanted a student and staff image (same OS just altered settings etc).

[@danny_moran]

The way I would deal with that is by creating multiple task sequences (TS) within your deployment share. Create a TS called "Student" and then create a second TS called "Staff". Once you have both TS's created, you can open the TS and modify the settings to suit your needs. By creating multiple TS's, you only need to have one boot image (litetouchpe_x64.wim) loaded into your Windows Deployment Server and then when you load into that over the network, you can select either the Student TS or the Staff TS, to deploy the correct image you want. Thanks for watching!

[@joshyyyboiii2972]

@@danny_moranBrilliant, thanks for your response it definitely makes sense. I’ll raise my first question as I’m wondering… what if we wanted different operating systems to be available within the MDT menu, I already have a windows 10 image but would like to add windows 11 as an option for beta testing before rolling it out. Would I have to create a completely new deployment share? Or could I use the existing deployment share where the current LiteImage Win10 wim file is stored?

[@danny_moran]

That can all be done using the one existing deployment share. One deployment share can be used for multiple different operating systems such as Windows 10/Windows 11/Windows Server ect. All you need to do is load the install.wim files for the operating system you want to deploy into the Operating Systems folder of your existing deployment share. Once you have imported the OS you want to deploy into the Operating Systems folder of your deployment share, create a new task sequence and select the "standard client task sequence" and then select the new OS you imported. When the new TS has been created with the different version of Windows, all you need to do on the client computer is boot into the same litetouchpe_x64.wim and then it will give you the option to select which version of Windows you want to install.

[@joshyyyboiii2972]

@@danny_moran Hi there, thanks for your reply! and sorry for the late response (I don’t go on KZbin much) this makes a lot of sense. Just one thing though, where would I find the install.wim files for the different OS?

[@danny_moran]

You would need the iso file for whatever version of Windows you want to install. Once you have the iso file, you can then extract the install.wim file from it. In most cases, you can get the iso file from the Microsoft website.

[@kineasx]

I've got to the part of importing the OS into the workbench and I'm getting an error. I have downloaded the latest Win 11 iso from Microsot, mounted it and selected the drive letter for the source directory, however it states the directory specified doesn't contain an install.wim file.

[@danny_moran]

Have you inspected the iso file and checked that there is an install.wim file located in the sources folder? It could be that the iso file has been packaged with an install.esd file and not an install.wim. If this is the case, you will need to copy the install.esd file out of the iso, and then extract the install.wim file out of the install.esd file. Once you've extracted the install.wim, you can then import it into the MDT workbench. Check this video on how to extract the install.wim file out of the install.esd file: kzbin.info/www/bejne/kHO2gox_qdmqhpI Thanks for watching!

[@Tech215Studios]

I’m struggling with the term “Capture” at work when we PXE boot, we have a staff network, and a Student Network. We have multiple images we can install. I’m trying to have a few different DS’s for my small PC flipping business. Does capture mean install windows on a machine, install all the apps then capture like a clone??? Or can I just add the apps I move into my DS folder and pick the exe’s and MSI files in the task sequence?? It’s the only thing I’m struggling with.

[@danny_moran]

Capture is just setting up a reference machine and then making a clone of it, and then deploying that clone to another machine. It's mainly used when you have a lot of the same computers that are the same make and model. You can also just add the apps to your deployment share and then select them during the task sequence, like you said. Thanks for watching!

[@kucingoren666]

great video,possible to integrated multi languagepack with MDT?

[@danny_moran]

Hi, I have never tried it with language packs, so I am unsure about this. Thanks for watching!

[@Doc-Lino]

Great job Danny, and Driver package ? Thank You so much.

[@danny_moran]

Thanks for watching!

[@Doc-Lino]

@@danny_moran ? driver package "Out-of-Box Drivers"

[@nhv88]

Hi - Great guide and it was vevery helpfull to have both video and blog post so I dont miss anything! :) I have a littel issue with my installation when i PXE boot a vm to test it takes very long time to load the .vim file - is there a way to optimize it? :)

[@danny_moran]

What is the size of the file that you imported into WDS? Is shouldn't be very big and need optimising. Also, what's the network speed between the WDS server and the test VM? Is it on the same physical box?

[@nhv88]

@@danny_moran Hi :) Its only 329 mb - its abit weird the actual install after booting in to pe is about 7 minutes including transferring all the Windows 11 files it needs. Its a lab setup on a intel NUC 11gen with ESXI 8 where both server and client is install

[@BEASTYBOY120]

I was able to successfully access the PXE but, but rather than going to the Windows Deployment Toolkit like yours did, mine was stuck on the windows logo. Anyone have pointers?

[@danny_moran]

Sorry, I'm not sure. I don't recall seeing it get stuck at this stage before.

[@BEASTYBOY120]

@@danny_moran I think it has to deal with my deployment share. For some reason even though I modified the properties for only x64 it downloads the x84 from the TFTP server which is why I think it gets stuck in the windows logo

[@chuckthecannibal]

Great videos, very helpful and informative! I'm going off of a comment by Joshyyy boiii below about having multiple Windows images: What if you wanted to put a Linux image on there too, is that possible? Like if I wanted to have a couple of different Windows images plus a Linux image? It doesn't come up often, but I occasionally have to install Linux or dual boot it with Windows for my organizations PCs. I usually just install it from a flash drive, but it'd be nice to have it available over the network.

[@danny_moran]

You can add some linux distro's into WDS so that they can be deployed, however, I've never done it personally so wouldn't really know where to start. Thanks for watching!

[@Jonathan-vx2qj]

What about making this without and Active Directory? Is that possibel too?

[@danny_moran]

Yes, you can do this without Active Directory. Thanks for watching!

[@legolaskejcz]

Why do you speak so quietly in the videos? Volume on headphones at max, everything max but you can barely hear. It makes me want to sleep when listening and I can't focus :( I watch with replays to understand. BTW great job! excellent tutorial

[@danny_moran]

Thanks for your feedback. I have recently upgraded my audio hardware, so future videos will have much better audio quality. Thanks for watching!

[@davoodd1638]

Hi, Fantastic, would u plz make the same video but, with Microsoft Endpoint Configuration Manager? Thanks

[@danny_moran]

This is on my list of things to do, however, I don't have a timeframe on when this will be done. Thanks for watching!

[@elteletubicochinotecosmico2675]

hello, I have an error when I access the Windows Pe tab. The error is as follows: MMC Has Detected an error in a snap-in and will unload it. then it gives me two options: report the error to microsoft and turn off MMC or unload the snap-in and continue , but it closes anyway. I am implementing it on Windows server 2016 v1607. Any solution? Thank you!

[@danny_moran]

Not something I've heard of, but a quick Google search shows something similar to what you have described. Check this Microsoft Docs article to see if it helps: docs.microsoft.com/en-us/answers/questions/758014/index.html

[@mikaelbackstrom]

@@danny_moran this seems to be an issue since Microsoft removed the x86 files from the ADK since MDT still requires them to work correctly. I am a bit surprised actually that we are not seeing a new MDT to deal with this.

[@danny_moran]

Yeah, MDT hasn't been updated in a while. Hopefully, they will release an update when they release version 22H2 of Windows 11 as it hasn't been officially updated for use with Windows 11 yet.

[@joselinrapalo458]

@@danny_moran is there a way to bypass that? because I am having the same issue and can't finish the configuration.

[@danny_moran]

I believe the only way to resolve this is to download and install the older version of the ADK that is for Windows 11 21H2, and not the latest version. You can get it from the Microsoft download page: docs.microsoft.com/en-us/windows-hardware/get-started/adk-install#other-adk-downloads Direct download for ADK for Windows 11 22H1: go.microsoft.com/fwlink/?linkid=2165884 Direct download for Windows PE add-on for the ADK for Windows 11 22H1: go.microsoft.com/fwlink/?linkid=2166133

[@AlchemillaVideo]

Thanks!

[@danny_moran]

Thanks for watching!

[@raymondcorrea1]

Do you know how to automate a computer name in mdt? For example three letter prefix + month and date and last 4 of MAC addresses? For example ABC-DEC08-0AE7

[@danny_moran]

Have a look at the below guide. It sets the computer name to the year and then the mac address. It shouldn't be that difficult to modify it so that it includes the month as well. www.deploymentresearch.com/back-to-basics-custom-computer-naming-in-mdt/ Thanks for watching!

[@ts-cj2ym]

Im still not sure how all the personally user account info for a specific user is done. Stuff like local AD og Azure AD account, users outlook account and so on. Is it done manually?

[@danny_moran]

User configuration is usually completed after the user has first logged in. If the workstation is connected to a local active directory domain, then it is done using Group Policy, but if it is just connected to Azure AD, then it is often done using Microsoft Endpoint Manager/Intune. Thanks for watching!

[@carlosync]

I'm experiencing a problem on the first mdt screen in the 14:25 minute, even doing the script configuration in bootsatrp.ini always pops up this welcome screen and on the next screen appears the DOS asking for the name of the share. Note: I do the update deployment share process. Could you help me?

[@danny_moran]

After you have updated the deployment share, do you replace the wim file within WDS with the newly generated iso file? In the bootstrap, is the DeployRoot path correct? Can you browse to it if you copy and paste the path into file explorer? Also, does the user you specified the credentials for have permission to access the deployment share file share?

[@carlosync]

@@danny_moran Hello, yes it already worked had to update boot image of wds same. Thank you

[@danny_moran]

Glad you got it working! Thanks for watching!

[@sheldonmetoyer2460]

Can you run MDT off of another server or does it have to be on it's on server? (i.e. File server or DC01)

[@danny_moran]

For the best performance, you should run MDT on it's own server. However, it should work fine installing the role onto a server with existing roles installed. Thanks for watching!

[@sheldonmetoyer2460]

@@danny_moran thank you so much, I've been searching up and down to find out if it absolutely has to be on it's own server. We do not have anymore licenses for servers where I work and I just want to test it to make sure I can get it to work before putting it on it's own server. Do you think it'd be best to be best on the domain controller or on the file server? My best guess is file server.

[@danny_moran]

The file server would be the better option. You shouldn't have additional services running on the domain controller, as doing so will increase the attack surface and make your active directory more vulnerable to security threats.

[@jmusac]

Hi, i followed instruction however when i boot pxe imaage i got message "windows deployment services client functionality is being partly deprecated". And there is only reboot option after that.

[@danny_moran]

Sounds like you've loaded the boot.wim file from the Windows 11 iso into your WDS server rather than using the MDT LiteTouchPE_x64.wim Try booting from LiteTouchPE_x64.wim and it should fix the issue. Thanks for watching!

[@jmusac]

@@danny_moran Ok i managed to boot from LiteTouchPE_x64.wim but now i get message x:\deploy\scripts\litetouch.wsf The value for the attribute is not valid: language

[@danny_moran]

Looks like there is an issue with the latest Windows ADK released by Microsoft, which is causing this issue. There is a fix here: www.deploymentresearch.com/fixing-vbscript-support-in-windows-adk-sep-2023-update-build-25398/

[@oxgee666]

where i download both folder, ADK(inside hava: installer, adksetup, userExperienceManifest) , ADKWinPEddons(installer)

[@danny_moran]

You can get the ADK files from here: learn.microsoft.com/en-us/windows-hardware/get-started/adk-install Thanks for watching!

[@praveentadepalli1255]

OS installed successfully on client PC but it's not alowing to create a local user. I'm istalling windows 11 Home single language. Can Plz help me to change deployment rules accoring to my need

[@danny_moran]

I've never tried deploying the Home editon and I don't think it is supported for deployment, so I'm not sure how you would go about doing that.

[@praveentadepalli1255]

For other editions?

[@danny_moran]

I don't add other users through MDT. Once the machine is added to the domain, that's what manages the other user accounts.

[@praveentadepalli1255]

How to change the rule, to add user

[@danny_moran]

You will have to search online to find the command to create new users during the deployment process.

[@JMV21377]

Dan, on the deployed Windows 11 image, the "Domain Admins" is added to the local Administrators group by default. How do I change that or is there a way I can add another user or group to the local Administrators group as this image is being deployed? If I go in there an try to enter my Admin account it's telling me that I need elevated privileges or rights.

[@danny_moran]

Isn't the Domain Admins security group pushed to the local Administrators group for all domain workstations and servers by default? I have a guide on how you can create custom security groups in Active Directory and then push them to the local Administrators group of workstations and servers: kzbin.info/www/bejne/epWkdo2aqK6ZidU At what point is it asking for credentials? As during the deployment process, it should be using and signed into the local Administrator account (hostname\Administrator) and not a Domain account.

[@JMV21377]

@@danny_moran Thanks for the quick response! Yes it pushes Domain Admins security group by default but is there any way for it not to push that group to local Admins? Yes it is using the signed into Admin account and not the Domain account however I'd like to make some changes and although I'm part of an Admin group, I'm not not part of the Domain Admin group where I work. I'm unable to launch Powershell with Admin rights because it tells me I require elevated rights or permissions. By the way your videos are Amazing, I look forward to watching more.

[@danny_moran]

It's not MDT that is pushing the Domain Admins group, it's Active Directory when a workstation gets added to a domain. I think there are ways to stop it from being pushed, but I would advise against it as it will likely cause some other issues. I would recommend speaking with whoever deals with user account security at your organisation and getting them to modify your account permissions or create you a dedicated account to administer workstations so that you can do the required tasks without bypassing the current security process and potentially weakening the organisation's security posture. You should really have this managed centrally through the use of Active Directory security groups and GPOs (or some kind of PIM solution), otherwise, it will likely become a security and audit nightmare and potentially leave devices open to being compromised.

[@JMV21377]

@@danny_moran Thanks Danny! Appreciate the help and feedback!

[@danny_moran]

No problem! Thanks for watching!

[@tobozon4161]

How to deal with MDT failure 5616: Verify BCDBootEx. Followed your step, but I have windows 11 pro iso with multiple versions, and different hardware.

[@danny_moran]

Try and give this a go: support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7 Thanks for watching!

[@tobozon4161]

@@danny_moran yeah, that was it. I found some uefi switch patch, it’s still works. Maybe you should make a video about it. Thank you very much

[@danny_moran]

Glad you got it working!

[@张艾-g8c]

hi,sir. i have a question, how can i using WDS deploy OS on another vm machine which is no disk , I guess I need ISCSI , but I don't know how to start

[@danny_moran]

Without knowing how your environment is configured or what equipment you have, I wouldn't be able to suggest a solution. Thanks for watching!

[@张艾-g8c]

@@danny_moran hi,my current is vm server 2019 ,current process DHCP,DNS,WDS,MDT,iscsi . i want to deploy OS on a diskless client. but not using the client site disk, is using the ISCSI from my server. Results (when deploy on the client, it uses iscsi, not the client's hard drive)

[@danny_moran]

You would be better looking into Virtual Desktop Infrastructure (VDI) and connecting to them using a thin client device or software installed on a workstation. The solution you are proposing leaves you open to a lot of issues, and none of the benefits of a solution such as VDI's.

[@张艾-g8c]

@@danny_moran thk you sir

[@nicoleanne967]

can I have multiple adk versions to be able to deploy win 11 and a win 8/10 for example and be able to generate a unattend file

[@danny_moran]

You can only have one version of the Windows ADK installed, as well as one version of the Windows PE add-on installed. The newer versions of the ADK can also install older operating systems, so it is best to go with the latest version of the ADK that is supported for deployment scenario. I hope that makes sense. Thanks for watching!

[@nicoleanne967]

@@danny_moran Thank you! I will try it in my home lab!

[@PatrickMcCoyJr]

Mine laptop fails with TFTP time out PXE-E32. Any ideas why it's failing?

[@danny_moran]

Sounds like the device you are trying to do the deployment on is unable to communicate with the WDS server correctly. Are both devices on the same network and can they communicate with each other?

[@PatrickMcCoyJr]

I got that to work and now I get a script language error when I load into PXE boot. Someone said the windows 11 adks are broken so trying to use older windows 10 tomorrow

[@PatrickMcCoyJr]

@@danny_moran Not sure that is fixed or not but now the PXE boot which is set in DHCP brings up a DHCP error when it boots but only when they are different vlans. It works perfectly when they are on the same vlan.

[@danny_moran]

If you're crossing subnets for PXE boot, you will need to setup IP helpers or DHCP options on the remote subnet so that it can find the PXE server.

[@PatrickMcCoyJr]

@@danny_moran I’ve set up the dhcp options but that doesn’t seem to help between vlans. When I put the pc on the same vlan as the PXE server it works so I think that the ip helper is going to be needed. Thanks for the feedback.

[@mr63249]

Was the win 11 iso downloaded prior?

[@danny_moran]

Yes, the Windows 11 iso was downloaded before I started. You can complete most of the setup without using the iso file, the part you need it for is when you get to loading the install.wim file into MDT. Thanks for watching!

[@jessestark4789]

Hello! I made it to 14:40. It is asking for a domain but we dont join our computers to an AD we use Azure AD & Intune. Any way around this?

[@danny_moran]

Hi Jesse, When it asks for the User Credentials, it wants the details to be able to connect to the deployment share on your MDT server. If your MDT server is connected to your domain, just enter the username/password for an account which has permission to connect to the deployment share, and your local domain name (this won't connect the deployed machine to the domain). If your MDT server is not connected to your domain, just enter a username/password for a local account on the MDT server and either leave the domain blank or enter the local hostname of your MDT server. To set if the deployed machine is to be added to the domain or left in a workgroup is set during the wizard at 15:01 Thanks for watching.

[@jessestark4789]

@@danny_moran Thank you for a fast response. I noticed at 14:23 when you click on "Run the deployment wizard to install a new operating system" that it takes you straight to the user credentials section. When i click on the "Run deployment Wizard.." it asks me to provide the deployment share path. I thought i was putting in the right thing, but i think this is holding me up for the user credentials part.

[@danny_moran]

On your MDT server, if you right click your deployment share > Properties > Rules > Edit Bootstrap.ini I do this at 15:50 In the bootstrap it should say: [Default] DeployRoot=\\SERVERNAME\DeploymentShare$ Can you check that config option is there, and the servername and deployment share name is correct? You can also input the username, password, and domain in the bootstrap.ini like I do at 15:50 so it doesn't ask you to enter it every time.

[@jessestark4789]

@@danny_moran Thank you again for the help! It appears the root cause of my trouble was my surface dock 2. I switched to a surface dock 1 and was able to get past all the previous steps i was having trouble with.

[@danny_moran]

I'm glad you managed to get it working. For the record, Microsoft Surface's are one of the worst devices to deploy. Especially the ones that don't have a built-in network card and use an external adapter/dock. A few years ago, I had to deploy a handful of them and had nothing but issues. For testing deployments, I would recommend using a different device (something with it's own built-in network card) or at least testing with a different device if you encounter issues. Thanks for watching!

[@LuvxJacqu4li8e]

Its weird mine couldn't find it over the network but it worked if i pointed to yhe iso

[@danny_moran]

Is DHCP setup and working correctly? If the network boot doesn't find the WDS server, it's usually due to DHCP. Thanks for watching!

[@VypeReaper]

How would you deploy it to 10 computers at once? I am assuming that the only thing that would change is the Computer Name, is that correct?

[@danny_moran]

Yes, that's correct. Just network boot all the machines and just give them unique names during the install wizard and you can do them all at the same time. Thanks for watching!

[@VypeReaper]

@@danny_moran Danny, I have subscribed to your channel. You have very good content I need for my interviews. Lastly, can you show us how to connect hosts to the server and use PXE to install Windows unattended? I appreciate your videos.

[@matuskunik2068]

I created the win iso file with media creation tool and i have no install.wim file in source directory, not in win11 nor win10 install media. There is only boot.wim and install.esd which the MDT and WDS is not able to import as OS. I know, that i need convert the esd file to wim file. So you need to do and extra step with this. Come on Microsoft, really?!

[@danny_moran]

Yes, you can only import install.wim files into MDT/WDS. You can easily convert the install.esd file using the PowerShell DISM (Deployment Image Servicing and Management) cmdlets. It's an annoying extra step that you sometimes have to do if your iso image is loaded with the install.esd and not the install.wim file.

[@matuskunik2068]

Yes, it's strange.. The win11 iso file, that i downloaded from MS page have install.wim inside source directory, that works perfect. But ISOs created with their media creation tool, have install.esd file inside. Nobody know why, even MS engineers not. 😂

[@danny_moran]

I'm guessing that has something to do with them attempting to keep the file size as small as possible while trying to pack as much data as possible into it. I have also created a video on how to easily export the WIM files out of an ESD file: kzbin.info/www/bejne/kHO2gox_qdmqhpI

[@Jivin16]

pxe is flashing and not happening

[@danny_moran]

Sounds like your DHCP server isn't giving out the boot options and informing the clients where your boot server is. Is your Windows Deployment Server connected to an active directory domain that is also providing DNS, and are you using a Windows DHCP server on your network to provide the clients with IP addresses?

[@Jivin16]

@@danny_moran thanks Danny for the comments..the server box needed a restart ..