Это видео недоступно.
Сожалеем об этом.
How to Sysprep and Capture Windows 11 22H2 using Microsoft Deployment Toolkit (MDT and WDS)
HTML-код
- Опубликовано: 7 окт 2022
- Learn how to use the Sysprep and Capture features included with Microsoft Deployment Toolkit to capture a custom reference image of Windows 11 22H2 and then deploy that custom reference golden image over the network. In this example, I go over the process of creating a new deployment share specifically for capturing images, how to use the lite touch script vbs script to initiate the image capture process, and how to then deploy that image.
View the blog post here: www.dannymoran.com/sysprep-ca...
Guide on setting up Microsoft Deployment Toolkit: www.dannymoran.com/deploy-win...
Guide for extracting a WIM out of an ESD: www.dannymoran.com/convert-es...
Hi, I’m Danny, a London based IT consultant and sporadic blogger. You can view all my blog posts at: www.dannymoran.com
Just to say thanks Mr. Danny very clear content, right speed, and free... You are my new unknown / never seen mentor.
Thanks for watching, John!
Thank you for the videos. I learn many from your tutorials.
Glad to hear that! Thanks for watching!
Hi danny, appreciate your videos you've proven to be a saviour in terms of getting me up and running for the first time using MDT. I am having an absolute nightmare however with getting Office built into the reference image, if you are looking for future video ideas :)
I haven't deployed Microsoft Office for a while so I probably won't be much help!
Thanks for watching!
Hi Danny , I'm new to the site but they are great instructional videos , keep up the good work - Mike !
Thanks for watching, Mike!
Much love for this newer version too :D Thanks a lot.
Thanks for watching!
Brilliant tutorial Danny, thank you very much!!!
Thanks for watching!
Thank you very much. Very clear and spot on.
Thanks for watching! Hope it comes in useful!
You are a legend! thanks so much for sharing, you are amazing
Thanks for watching!
Hello ! Nice video, very helpfull, all worked like a charm !
Thanks for watching!
Thank you very much for the videos, I appreciate you very much
Thanks for watching. Hope it comes in useful!
You help me a lot, I thank you
Glad to hear that! Thanks for watching!
I think this tutorial just pulled me out of the depths of imaging depression. My many thanks to you, good sir.
Thanks for watching!
Thank you ! Much appreciated
Hope you found it useful! Thanks for watching!
Hi Danny, wonderful guide. Thank you. Quick issue I am having, when my client PC reboots in the PXE environment to capture the image, it just sticks with a command prompt window open (X:\Windows\System32>). Any thoughts on how to get past this?
Sounds like it could be a driver issue. Try importing the network drivers for your client pc into the drivers folder of your mdt capture deployment share.
Once the drivers have been added, right click the capture deployment share and update it.
This should hopefully fix the issue.
Thanks for watching!
Very clear explanations. Years ago, I ran a small shop and we used Sysprep and that mostly for deployment for readying PCs for pickup. I'm trying to look at similar methods now; however, when it comes to something like Windows 11 Home the base requirement of getting up and going with a connection to the internet before it gets moving seems to be a cutoff that really puts a stop to all of that.. I'm interested in thoughts of a work around that would allow an OEM to proceed, make sure drivers are installed (Yes, I'm aware generalization takes them back out, but with the files there they will re-populate) and then reseal so that the end user can be the one who activates. Is this even a process now?
I don't really have any suggestions as I don't work with Windows 11 Home edition, however, you need to be careful you are not breaking the Windows license conditions.
To deploy OS's correctly you need either a Volume License or be a registered reseller through Microsoft.
Also, like you mentioned, you need to make sure that the end user goes through the OOBE (Out-of-box experience) setup process themselves.
Great video, very clear and easy to understand instructions. I'm getting the same issue others have mentioned. The sysprep starts and then reboots, on the logon screen the administrator account is disabled. I've googled it but unfortunately can't find a solution. I will build a new WDS server when I have time and try again.
This seems to be a randomly occurring issue that happens to a few people. Unfortunately, I have no idea what causes it. It's never actually happened to me, so I've never been able to actually troubleshoot it.
Thanks for watching, Paul.
Hey Danny! Your videos have been a huge help for myself and my organization! Thanks for the very informative videos! I do have a few issues/questions though.
1. Do I do a standard deploy with MDT to the reference pc before sysprep? Or do I need to go into audit mode or some other mode to install everything before the sysprep??…
2. Also we do not use PXE boot as we don’t use DHCP at all so I have to deploy all my images with a usb media instead…is there a way to do this with sysprep and capture as well? I know you mentioned it will automatically reboot to PXE but PXE won’t work, so is there a way for it to boot to USB or something instead?
Thanks! Keep up the great content!!
Hey Danny, this guide worked perfectly using the stock wim from Microsoft. However I wanted to ask, in this video are you logged in as the built in administrator user or just another user account? I'm trying to capture my custom image however when I capture the image it is captured in audit mode thus when deploying the image to other computers they boot into audit mode and the whole deployment breaks because of that.
Since Windows 10, I no longer capture images in audit mode, I just boot Windows normally.
I don't think I used the built-in Administrator account, just another account that was in the Administrators group.
Thanks for watching!
Great video! Question: I get to the restart on the computer being captured....and it stops saying I don't have a 'driver' for the network card so it can't connect to the share after restart.
You should just need to import the network card drivers into your MDT deployment share.
To import the drivers, copy the drivers to your server and then extract them, right click the 'Out-of-Box Drivers' and select 'Import Drivers', and then follow the Import Driver Wizard.
Once the drivers have been imported, right click the deployment share and then update the deployment share.
Once you've done that, it should work fine.
Thanks for watching!
Hi Danny, great guide. Thanks!
after deployment the 'getting ready' screen how long does it normally take? on my testlaptop it's +- 2h and still loading
Looks like there is a bug somewhere along the line as a few people have started to mention this issue.
Looks like Microsoft is aware of this: learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#provisioning-packages-might-not-work-as-expected
Take a look at this link and see if any of the advice here can help. Looks like there are some workarounds, but they don't look elegant: learn.microsoft.com/en-us/answers/questions/1027370/windows-11-sysprep-1.html
Thanks for watching!
@@danny_moran hi Danny, we made a new 21h2 image (with your video as wel ;) ) just to be sure and this is working.
Hi thanks for these videos, i already have the wim file from a sysprep of a win 10 system, to create a deployment for that one. Should i create a new deploymet task and use a Win10 iso to create the boot file or will it works with the win 11 one... ? tanks again.
Import the WIM file for your Windows 10 image into the Operating Systems folder of the deployment share, and then create a new Standard Client Task Sequence and select the imported Windows 10 wim file.
Once you've done the above two steps, you should be able to boot from the existing standard litetouch wim file and select the new task sequence to deploy.
Thanks for watching!
Hey Danny,
Thanks for the efforts here. Quick question, how did you keep the same customized desktop, start menu and task bar of the captured image so that the admin profile used during sysprep copied as default profile and loads to all new profiles?
I never made any changes to keep the desktop icons; I think when the software was installed, it put shortcuts in "C:\Users\Public\Desktop" which will make them appear for anyone who signs into that computer.
The taskbar and start menu are just the Windows 11 deafults.
Thanks for watching!
Hi Danny, did you find any solution for this?
A solution for what? When someone logs into a workstation for the first time, it builds them a new profile, which is basically blank.
If you want to set custom desktop/taskbar/start menu icons, I would look into deploying personalisation settings using group policy rather than setting it up in the initial image.
Thank your for this amazing video. i flowed the installation step by step, and it worked. I'm very happy.
I would like to ask you, if it's possible to make a video on how to install MECM (Microsoft endpoint configuration manager) on a server? Please,
Glad you found the video useful!
This is on my list of videos to create, but not sure when it will get done, unfortunately.
Thanks for watching!
Hello Danny, great video tutorial. Is it necessary to put extracted .wim file into sources folder? If so, is there a way to do it?
No, you don't need to put it into the sources folder in the iso. You just need to import into the Operating Systems folder within MDT.
Thanks for watching!
Awesome Video! been using MDT for about a year now. Are you putting your reference machine in audit mode? Is that still needed? The weird thing that is happening with the win11 images is after deploying they are booting up in audit mode could the above be my issue? Thanks!
I don't used Audit Mode when creating my reference images, and I've never had an issue.
Thanks for watching!
This does have to be done using the Administrator account. This doesn't necessarily mean you need to use Audit mode, but the Administrator account must be enabled.
Thank you a lot for your video! One question please. After doing this procedure on windows 10 home, i am stuck on a restart loop of loading files, after restarting of the sysprep. What should i do please?
I've never tried it using Windows 10 Home edition, and I'm not sure that it's a supported edition.
Thank you very much for the videos, I appreciate you very much. I did exactly the same in your video. Unfortunately, It's stuck at the "Getting ready" windows. Do you have any idea or solution?
Are you deploying to a virtual machine or a physical machine?
I've seen the "getting ready" issue on Hyper-V machines before. In the console window, you need to click view and un-tick enhanced session.
Thanks for watching!
Hello Dany, appreciate your efforts preparing this detailed step-by-step guide. I am facing an issue with accessing the "\\PC-Name\DeploymentShareCapture$". It gives me a network error "Permission Denied" although it's on my local computer. I also can't find the folder anywhere on my pc.
Would appreciate your help identifying what step did I drop. Thanks!
When you create the deployment share, it will ask you to select a location for the folder. It will be stored in whatever location was chosen.
As for the permission issue, I'm not sure. Is it asking you to enter credentials?
Thanks for watching!
Hi danny , in the task sequence i ask for local admin password.
The local admin password should be the same password of the server that the mdt and wds installed or can i choose a password that i want to use?
You can set it to whatever you want.
Thanks for watching!
Thanks to you your video I was able to get lot of questions answered. Everything is finally going smoothly but I running into one roadblock; when it restarts and tries to access the server to save the .wim It fails because it cannot connect. Since I'm not on the domain is not allowing the device to get past that point. Any suggestions?
It should work fine without the device being on the domain.
MDT will authenticate itself while the task sequence is running.
Nice video...very helpful. Would you happen to have a tutorial on creating a default user profile? Thanks!
I don't have any videos on that topic, unfortunately.
Thanks for watching!
Hi danny, im tried to do capture image using the first tutorial of new deployment share you uploaded and and seems that everything is ok because the file of the is created in the capture folder but after the pc is up i cant connect to administrator account , does the sysprep process disable the admin account? If so there is something to do?
Thanks for your respond
The Administrator password should be the same. Did you set a different password in the wizard when you created the deployment task sequence?
@@danny_moran i think i know what is the problem. The mdt is installed on server and in the task i used the local admin password which is not the same as local admin of pc. Thanks for respond
Thanks! I followed this video and successfully captured and deployed the image however, both machines have the same product ID and device ID. Did I miss something? We want to use this capture to deploy 150 machines in the next few weeks.
I don't think this should cause any issues. The device SID's should still be different. I remember someone else mentioning this and then after testing it didn't cause them any issues.
Thanks for watching!
Danny, do we need to add a new boot image to WDS for capturing. When I run the litetouch.vbs, after it executes sysprep and reboots, it PXE boots and brings up a command prompt at X:\WINDOWS\System32. I have a feeling it PXE booted to the boot image I had for other Deployment share.
No, you don't need to add the new boot image wds server.
I think the issue you are having is related to network drivers. Try getting the correct network card drivers for your device and importing them into the drivers folder of your new deployment share.
Once they are imported, right click the deployment share and update it and do a complete regeneration.
After that, try doing the capture again and it should hopefully work.
@@danny_moran Thank you for your reply! I ended up killing that task sequence and then re-updating the deployment share. After that it worked flawlessly. Thanks again!
Glad you managed to get it working! Thanks for watching!
Thanks for this nice explanation.
Can you show me how to do disk partitioning with Deployment wizard ?
Have a look at this guide: www.prajwaldesai.com/create-extra-partition-in-mdt/
Thanks for watching!
Hi, I have a problem because I folow all the steps but when the computer restart it get me a msdos image (x:\windows\system32) and I don't get the image WIM in the server. What is the problem?. Do you know?
Maybe try updating your deployment share.
In deployment workbench, right click your deployment share and then press update deployment share.
Select completely regenerate the boot images, and then keep pressing next through the wizard until it has been regenerated.
Then try and capture again.
Thanks for watching!
I finally successfully did my custom capture and i'm testing it on a pc at the moment. It seems "stuck" on the Getting ready screen. Does this take a long while?
Looks like there is a bug somewhere along the line as a few people have started to mention this issue.
Looks like Microsoft is aware of this: learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#provisioning-packages-might-not-work-as-expected
Take a look at this link and see if any of the advice here can help. Looks like there are some workarounds, but they don't look elegant: learn.microsoft.com/en-us/answers/questions/1027370/windows-11-sysprep-1.html
Thanks for watching!
i can't get the extracted .wim on the mounted .ISO also not in The original .ISO " no storage left" also tried it with "move" in CMD. any ideas?
I'm not sure what you mean.
Do you need to extract the install.wim from the install.esd? See this guide: ruclips.net/video/ZBSQYIttwP0/видео.html
Thanks for watching!
How did add domain to join and OU strings to wizard ?
I have the config I used in the blog post linked in the description. This has the deployment share properties I used. You will just need to modify the values slightly to match your environment.
www.dannymoran.com/deploy-windows-11-with-mdt-and-wds/
Thanks for watching!
After I execute the LiteTouch.vbs file on my reference VM, it reboots but doesn't show the window that comes at 6:22
What happens after it reboots?
MDT standard client task sequence and MDT Sysprep and capture what is difference which is used in which scenario
Standard Client Task Sequence: This has all the steps preconfigured for deploying an operating system.
Sysprep and Capture Task Sequence: This has all the steps preconfigured for capturing an image of an operating system.
Thanks for watching!
Hey Danny, I have a question. I've followed all your steps exactly as you have, except I'm using a standalone MDT which should work just fine. At 6:04 I press 'begin' and the wizard closes but nothing seems to happen for the next half hour and still counting. Is sysprep doing something in the background that I'm not aware of? The progress bars at 6:16 are not appearing for me nor is the machine rebooting at all.
Hey i have the same issues. I also run only one MDT because the Capture Deployment didnt work. I´ve solved the issue this way: Network Boot one Client with the clear W11 Deployment. When the window "Capture" comes up, choose Sysprep this PC. Let the machine do its work. Install everything you need.... Then do the "sysprep thing with generalizes and shutdown". Restart and go in network boot with F12. Then the sysprep comes in automatically and you get the Capture in the "Capture Folder" of your Server.
@@ZucchinilordHD I'm having the same issue as him. By "sysprep thing" you mean the Windows+R and then sysprep, right? WIth generalize and shutdown options enabled. If that's the case then you're my hero and you saved me a lot of troubleshooting time :')
So none of the two progress boxes appear after you press begin? Both the blue MDT progress window and the standard sysprep window? They should appear a couple of seconds after pressing begin. Seems like it's not actually initiating the sysprep sequence.
Are there any logs created here? - C:\MININT\SMSOSD\OSDLOGS
Interesting workaround - Glad you managed to get there in the end.
Thanks for providing a possible solution for other to try.
You should be able to manually sysprep using the below command:
%WINDIR%\system32\sysprep\sysprep.exe /generalize /shutdown /oobe
Can I setup windows deployment toolkit on a regular windows 11 pro machine?
I've never tried doing this. I've always used a Windows Server.
Thanks for watching!
Would you make some intune videos in the future? Thanks for all the videos!
I'm still planning on making Microsoft Endpoint Manager/Intune guides, however, I don't feel I have enough production experience at this stage to accurately provide the best guidance.
Once I've had more usage of the product and done more testing, I should be able to create some guides.
Thanks for watching!
hi danny , when i try to do capture the process in the computer start running and then its doing restart to the computer until i boot from pxe and its start to create the image file to the folder destination and in the end its complete with no yellow background like in the video. this is ok? its supposed to do this?
Does it give an error or say successful?
@@danny_moran its say succesful but with no the yellow background . Its restart and boot from pxe like its do a deploy from the wds
If it says successful, then it should be fine.
The yellow bar is just a warning as I had something disabled, which is what is was warning me about.
Hello Danny,
After running sysprep, the machine restarts and is asking me to install the operating system or open command prompt. Upon canceling this box, It took me to the login windows screen. Here it is creating the new profile named Administrator. Please guide me here to capture the wim file.
Thanks!
A couple of people have had this issue, however, I have no idea what causes it.
I've never experienced this issue myself, so can't really provide much guidance, unfortunately.
Thanks for watching!
Hi Danny, How to update the new SSD driver for this tool recognized SSD in HP Desktop. I run with Offline install USB and it can not recognized SSD driver due to lack of SSD driver.
If you import the driver into the drivers folder within MDT and then regenerate the media, it should then include the driver in the offline media.
Thanks for watching!
@@danny_moran Thank you so much.
Hi!! So to others machines models, to be captured, I will repete all that?
For capturing additional machines, all you need to do is re-run the litetouch.vbs script and follow the wizard.
You only need to setup the capture deployment share once.
Thanks for watching!
@@danny_moran thanks :)
Dear Danny, I followed your steps but after running litetouch.vbs it restarted the comptuer then nothing more happened, anything i was missing? I didn't see what is the ADK and WinPE version you have in your video, can you also advise? I was trying to capture a reference image for Windows 23H2.6
I'm not sure what the issue would be without any logs or error messages.
I haven't personally seen this issue.
This video shows how I setup my MDT instance, and what versions this guide uses: ruclips.net/video/wIp2YTNVjHk/видео.html
Thanks for watching!
Do you have network boot enabled on the computer?
Thank you for your guides. I was able to set up the MDT and deploy clear Win11 on a computer. However, I'm having troubles with capturing my reference image. I've tried it three times with different results.
1 - after running litetouch, the PC rebooted and got stuck at Administrator login saying the account is not allowed. So I chose my account with admin rights and it normally logged back in. Nothing else happened.
2 - during the second attempt I got a red window stating error regarding sysprep. Solved that by removing some user apps.
3 - third time it looked all good, sysprep worked, the PC rebooted and automatically booted into Lite Touch Windows PE, asking me to select a task sequence (offering the 'capture' one) and all the steps I had already done by that time after running the litetouch script. When clicked on begin again, it gave me a lot of errors (unfortunately, I didn't take any pictures). The worst thing is, the PC is broken. No startup repairs work. Even though it shows a Win11 installation as the OS to be repaired , it is not able to do it. And bootrec.exe /scanos shows no OS there. I put a lot of work into the reference computer which seems to be lost. I can do it again but I don't know what might have gone wrong that the process didn't continue as in your video and rather started all again after the restart.
Any help would be appreciated.
The MDT capture process is extremely temperamental and frustrating. You can do the exact same thing multiple times, and sometimes it works fine and sometimes it just doesn't. I try to avoid using reference images, as I find it less hassle to just script the software installs and add them to the deployment task sequence.
Without the error messages that it gives when it doesn't work, it's hard to narrow down what the issue could be, unfortunately.
As for it damaging your reference image, I've never seen it do that, so I wouldn't even know where to start. I would recommend just trying to capture a clean Windows install at first until you get it working, and then once you've got the capture process working, do your modifications to your reference image.
If you can provide any error messages or codes, I could possibly provide some more detailed guidance.
Thanks for watching, and I hope you manage to get it sorted.
@@danny_moran First, thank you for replying here. When I read your message, I had already been almost finished with the reference image again. This time I had issues with sysprep errors - I'll add my tips what helped me later.
This time around after resolving sysprep errors the capture process went flawlessly so I don't have the error messages from before. Honestly, I don't know the difference, the reference image was put together the same way. I thought I won this battle but I was wrong. Now it's getting a bit frustrating.
The reference PC didn't boot into Windows. The be precise, it got stuck at the manufacturer's logo, the spinning circle and message "getting ready" (I have it in my language so I guess this is the translation back to English). The only way out of this was hard restart. After that there was an error message titled "Windows installation" basically saying something about an unexpected restart and error and that the intalation couldn't proceed suggesting I should install again.
So I did install my captured image but it's no surprise that the image is corrupted and I get the same result. It's been spinning for hours and I guess it's never going to be ready. Any repairs using a flash drive with Win11 don't work.
I'll try to capture a clean Win11 install now. I have no idea what might have caused this. I must say that capturing an image of Win10 the old way worked flawlessly. This is frustrating.
Thanks for any help.
How can the computer see or access the Server if it's part of a Workgroup?
Workstations can still access the server if they aren't on the domain, it will just ask for authentication before it allows the connection.
Thanks for watching!
What happens if you leave selected generate a lite touch bootable iso file?
If you leave that selected, it will also generate an iso file in addition to the wim file.
If you're using WDS, then you only need the wim file.
With the iso, you can create a bootable USB drive and bypass WDS/network boot.
Thanks for watching!
Hi,
I have a question
For the user credentials at the windows deployment wizard, I need to specify the domain but I am using a test pc that is not joined to a domain what should I key for the domain?
I tried using my company domain and also the hostname of the PC. When it restarted to the deployment and I tried keying the credentials and both domain doesn't work it says
Invalid credentials . The network path was not found.
Btw after running the vbscript file the PC restarts and I am loaded to the mdt page to key in user credentials instead of the successfully screen with 2 error you got and able to have the wim file in the capture folder.
When it asks for credentials, you should enter the domain name of the environment that your MDT server is on and for the credentials you should use an account that has permissions to the file share on the MDT server.
@danny_moran
So eg my company is using abc domain I have to use abc domain when in the user credentials page am I right?
But now I have another error which is after running the vbscript file without Internet
I have the error of connection could not be made to the deployment share
connection ok possible cause invalid credentials.
I have used the credentials and AD which my company is using when keying in the settings for user credentials when the vb script is run and the network share folder I made it to everyone able to read/ write. Or do I need to have an internet connection for it to be working?
If i am using Internet the pc will restart and go straight to the user credentials to key to start the mdt deployment and when I key in the credentials used it have the invalid credentials network path was not found.
My understanding is that you need to be in the network to access the UNC path of the folder and if I am not connected to any Internet connection how do I access the UNC folder or even valid using the credentials I am keying in the settings when running the vbscript?
Just a quick check you are not connected to any Internet connection or joined to any domain when you are running the steps in the video right?
For the domain, just enter whatever your local active directory domain is called.
The capture process will work exactly the same with or without an internet connection. In this video, I don't think the environment had internet access, however, I have set it up multiple times on networks that have internet access.
For the computer that is being captured, it is not added to the local active directory domain - everything is configured under a local account on the workstation.
When you browse to \\mdtserver\deploymentsharecapture$ it should ask you for a username and password, enter domain credentials which give access to the mdt share on the mdt server. Enter these same credentials when you run the vbs file.
Hi Danny, I'm having trouble with capturing a VM from Hyper-V. When it restarts it gives me an error with Litetouch.wsf stating the value for the attribute is not valid: language. Not sure what this means - Could you help?
I've personally not seen this error before. I've just had a quick Google search and it looks like there are a couple of threads about this. Probably best to do an internet search for the error message and try a couple of the solutions people have posted.
Thanks for watching!
You need to downgrade your version of the ADK, WinPE, and MDT. The latest version from Sept. 2023 is bugged (because of course).
Thanks for providing this information.
Thank you for the video.
However, how did you get the ISO?
I was using the Windows 11 evaluation in this video, you can download it here: www.microsoft.com/evalcenter/evaluate-windows-11-enterprise
You can also download the standard version of Windows 11 here: www.microsoft.com/software-download/windows11
@@danny_moran Thank you for you response
Hey Danny, I keep running into errors after I run litetouch. I get a red failure box with a bunch of errors such as sysprep did not complete, failure 6192 error. Etc Any suggestions?
Is this when you are trying to capture an image or deploy an image?
Have a look at this post as it should provide you with some more information about the issue and potential fixes: www.deploymentresearch.com/fixing-why-sysprep-fails-in-windows-10-due-to-windows-store-updates/
Thanks for watching!
@@danny_moran when I'm trying to capture an image.
I have captured and generalized a custom image and deployed it with MDT. But every Computer has the same Device-ID afterwards. Is this normal? I've checked the SID. They are unique.
By default, the sysprep should generalise and generate new SID's/ID's. As the SID's are unique, that would suggest it did generalise during the sysprep process.
I don't recall ever checking the Device-ID to be honest, I've always just assumed it's generated a new one.
You could always try and manually sysprep one of the deployed images and see if doing a manual sysprep and generalise to see if it generates a new device id, just to confirm if it should be getting reset.
Is it causing you an issue or just something you noticed?
@@danny_moran Hi, thank you for your answer. I dont know if it is an issue. It's something i've noticed. When you do sysprep after deploying a generalized image than it has a new Device-ID.
Hey Danny, Been attempting to learn this for several weeks and was running off the old video till as of today. Resetting my capture as I believe something was causing malfunctions upon the process (still never got an image file to use but have crashed my computer every attempt :D). Anyways im right at 2min where I have the .esd file instead. I created the .wim through your other video but now what do I do. Not understanding if I need to get it into the source files such as your example. Maybe I am just missing a simple step here but been confused for hours now doing guesswork over here.
Once you have the wim file, you should just need to select the folder that the extracted wim file is in, rather than selecting the mounted drive when using the import wizard.
If that doesn't work, you might need to select "Custom image file" at the start of the os import wizard and then just select the new extracted wim file.
Thanks for watching!
@@danny_moran Alright so I was thinking that might of been the answer to use "custom image file" then choose the WIM but next selection is to "not use setup files" or to choose them. Am I correct to say since this is the .WIM it has all setup files needed?
I'm pretty sure you can just select "Setup files not needed" and then continue.
If not, I think you can select the second option and mount the iso file on the server and set the "setup source directory" to the mounted iso drive.
@@danny_moran Well, I finally got it to run with several sysprep issues I had to remove programs with. But when it reboots I get to the microsoft deployment toolkit and nothing happens. Eventually a box will come up saying welcome and to run the deployment wizard to install an os or to exit to command prompt. Any ideas of whats going wrong?
Not come across this before but it sounds like when it is rebooting, it is doing a network boot into your standard deployment share, instead of booting into the capture wizard.
Try going into Windows Deployment Services > Boot images > and then right clicking and disabling all of the boot images in there temporarily and then try the capture again and see if it boots into the correct wizard when it reboots.
You mentioned that you will be leaving a link on how to extract a wim out of esd. Was that in the description or am I missing out something? 😁😁
Looks like I forgot to add it. I've just updated the description with the link.
www.dannymoran.com/convert-esd-to-wim/
Thanks for watching!
@@danny_moran First of all, I would like to thank you for your quick responses. I really appreciate it.
Second, just to follow up on the conversion process to WIM. After completion of converting the ESD to WIM, how do you replace the WIM with the ESD when the mounted drive does not allow me to delete the ESD file?
Once you have the WIM file, you don't need to put it onto the iso.
When importing the operating system, instead of selecting "Full set of source files", select "Custom image file" and then you should be able to just select the WIM file that you extracted and just import that.
@@danny_moran Thank you very much as this worked. I really appreciate your help.
Do you know if there is a way to skip the credentials part of the procedure? After commencing the process for syscapture (by executing the VBS script), it causes an error "possible credential issues". Assuming this might have to do with the creds entered before the beginning the VBS script. Is there a way we can skip this credential checking process?
I'm not sure if that can be skipped and I don't recall seeing that error before. Might be worth trying a quick Google search to see if anyone else has had that issue before.
Hello, my capture won’t join the domain even after inputting all the correct OU information and admin login. I tried adding to the rules also and the unattend.xml. It will install the capture exactly how it was with the local admin account I created to do the capture on, but I need it to join the domain automatically. Any ideas as to why this is happening?
Do you get any error messages saying why the domain join fails?
Check the logs in the following locations to see if any errors are reported.
C:\MININT\SMSOSD\OSDLOGS
C:\Windows\SMSOSD
C:\Windows\TEMP\SMSOSD
C:\Windows\TEMP\DeploymentLogs
@@danny_moran results.XML says the deployment wizard was canceled or did not complete successfully. The deployment will not proceed. That’s the only error I could find
I'm surprised there are no log files on the machine you are trying to deploy. Without the logs, I can't really provide any useful information, unfortunately.
Did you try the deployment multiple times and it fails on all attempts?
Thank you Danny. I got an issue, after start capturing image from Windows10 machine, when it reboots system, it wouldn't come alive. No error - nothing. It will not boot up at all after that. I will rebuild the machine and try again.
Without any error messages, it's hard to suggest what the issue might be.
This doesn't sound like an issue I've encountered.
So all I have to do for a custom image is install windows, install software, make my changes, then sysprep and capture, and boom custom image?
Yes, that's all that's required to make a custom image.
Question. I am trying to capture Windows 11 22H2.. I have my capture sequence set up with the install.wim. When running the sequence it gets to execute sysprep and just reboots the machine before running sysprep. Any ideas?
Are you getting any error messages?
@@danny_moran No. However when running Sysprep manually I was getting a could not validate windows error message. My guess is maybe I need to resolve that error? Looks like it is failing Sysprep and then rebooting due to the task sequence
Yes, sounds like an issue with your Windows install if it is also failing when you are manually running sysprep.
@@danny_moran Resolved that issue by disabling bitlocker encryption on the drive and uninstalling some built in apps via Powershell. I can manually run sysprep now but when running my sysprep and capture task sequence it gets to sysprep does not actually run it and reboots.
@@nathanstall7647 @danny moran mine is doing the same. I run litetouch script file and looks like its running then once it says executing sysprep it automatically reboots the pc i'm trying to capture.
Hoping you see this. Is there a way to set up local admins on a deployment share?
Sorry, I'm not sure what you mean. Can you confirm what you are trying to do?
@@danny_moran currently we capture our images using WDS and have to add admin groups to the reference pc before we capture so techs in those groups will have admin rights for support. Is there a way to add these groups in an deployment in the toolkit?
Why not just deploy an Active Directory security group to the Administrators group on the local pc using Group Policy?
I have a guide on doing this: ruclips.net/video/DdAEZdsIfSs/видео.html
i used this method for capturing a win 10 22h2 image with no success, when i launch littouch the vm restart and nothing happens after :(
When you say nothing happens, does it not boot back into either Windows or the PXE environment?
Are you getting the iso file from Microsoft or creating one from a machine that has it already ?
You can download the iso files from Microsoft:
www.microsoft.com/software-download/windows10
www.microsoft.com/software-download/windows11
Thanks for watching!
@@danny_moran thank you!
@@danny_moran I’m going to set this up at work after testing on a vm 😁🤌
When i run LiteTouch it asks me for my credentials, i type in the account i use in the domain and has rights to the shared folder but it says its wrong credentials.
Its the right credentials, it worked when i typed "mydomain"\myaccountname insted of typing the domain in the domain section.. :P
Try giving the account local administrator permissions on the MDT server and then trying again. This should rule out if any permissions are missing from the account.
Hey man please help 🙏🏽. I followed your guide but when the machine restarts during it says “account disabled by your administrator”.
I then went and enabled the administrators account and logged in then ran the capture. It then said account information incorrect. What’s happening?
I have had people mention this exact issue previously, but I have never experienced or seen it myself personally, and I have no idea what causes it or how to resolve it.
At what stage exactly does this error occur and what is the exact error message? I've tried to Google the error but can't even find any screen shots of this.
Could you possibly upload a video or some pictures somewhere showing the error in more detail?
@@danny_moran at 6:05 in the video when you hit begin mine does everything yours does. Then it restarts the machine and instead of booting into the mdt splash screen it boots back into windows then says account disabled.
Ah, okay, I understand the issue you are having now, but, unfortunately, I don't have a solution for you.
I will do some digging and see if I can replicate this or find out what could be causing this, as I've had a few people mention this to me and I'm curious as to what could be causing the issue.
Are you trying to capture a virtual machine or a physical machine?
@@danny_moran a physical machine. Hp to be exact. Now another thing I noticed is you get two boxes when you hit begin. The generalization phase box doesn’t appear for me. Keep me posted! Trying to help my company figure it out.
Hello, great video. I have followed the steps and keep running into a few problems. First, when running the LiteTouch script, it never asks me where to capture the wim file to. Secondly, the script will run but not capture the image anywhere.
Are you running the LiteTouch script that is within the Capture deployment share?
@@danny_moran yes.
When you created the task sequence, did you select the Sysprep and Capture template? (like at 3:01)
Also, when running the LiteTouch script and select the capture task sequence, what options does it give you? Does it not come up with the Capture Image pane? (like at 5:06)
@@danny_moran yes I’ve selected the correct template. When running the script I get: Computer details, computer backup, locale and time, BitLocker, Credentials, ready.
It will run but not save the wim file anywhere.
You've got a configuration issue somewhere, as those menus shouldn't be appearing. It should only show the ones in the video.
I would recommend double-checking your deployment share properties and making sure they match the settings in the video, as well as deleting the task sequence and re-creating it.
Once you've done that, right-click your deployment share and update it, and then try the LiteTouch script again.
I am getting to a login prompt at the vbs script portion. I have both computers enabled for remote access, am logging in with the known password. What else can I do at this portion to get past the login. I have also mapped the drive back to the host pc.
I'm not sure I fully understand. What error are you getting, and when exactly are you getting the error?
how do fix when getting Unable to Locate Results.xml file
At what point are you getting this error?
@@danny_moran At the end when the yellow screen pops up...
Hi, does this generalize the image?
Yes, the image is generalised during the sysprep process before it is captured.
Thanks for watching!
@@danny_moran Thank you for your response, I really appreciate your help. I followed your steps and captured a win 11 pro image from a laptop that I built to use as a golden image. After installing the Device ID's are identical on all the machines. Is this a problem? how can I fix?
I looked into this a while ago and found that it shouldn't make a difference that the device id's are the same. The security id's will have been updated which is what matters the most.
Sysprep failed for me, do I have to install the OS from MDT for it to work?
No, you can capture images based off installs done using an iso/usb.
Thanks for watching!
@@danny_moran It turns out applications from the Microsoft Store prevent sysprep from happening. I had to use a PowerShell command to remove a "Language Experience Pack" that installs itself automatically.
After selecting an operating system, I want everything to run automatically How do you define it?
I'm not sure exactly what you are referring to. Do you mean skipping some of the options in the deployment wizard when you are deploying an operating system?
Check out this video where you can setup rules to skip some of the steps that aren't needed: ruclips.net/video/wIp2YTNVjHk/видео.html
Yes exactly ,Thank you very much
I tried to capture an image but after the sysprep the computer just goes to a black screen.
At what point after sysprep does it go to a black screen?
Got the capture seemingly to work with only the two WebService class warnings, but then there is no .wim in the Captures folder
Are you looking in the correct deployment share capture folder for the WIM file? I've never seen it capture correctly and not put the file there.
@@danny_moran I did check both deployment shares, I'm confounded myself. Had to go through a lot of troubleshooting just to get to that point in the first place (only the 2 WebClass errors). Downgraded my version of the ADK/MDT/WinPE to an older version to avoid the "language" VBS script error previously mentioned in the comments here, so I wonder if that may have anything to do with it. Spent all day Thursday & Friday trying to deploy a custom image and at this point I'm thinking of just forgetting MDT altogether and making my own custom .iso to boot from WDS
How strange. I'm not really sure what to suggest, unfortunately, as I've never really had any issues capturing images.
Can I also ask questions???
If you have any questions, just leave a comment and I will try and answer them. Thanks for watching!
I thought I had this, but it errored out. Now to troubleshoot the errors and try to figure out where it went wrong lol.
Did it give any error messages or error codes?
Thanks for watching!
@@danny_moran Yes, ZTI ERROR- Unhandled error returned by LTISysprep: the system cannot find the file specified. (-2147024894 0×80070002)
That is the first error. I'll be back in the lab later today to troubleshoot.
I've just done a quick Google search for the error you mentioned, and there are quite a few links with various solutions you could possibly try.
Hopefully, you'll manage to get it working.
Thanks for watching!
please let know below items 1) reference machine administrator account should not have password 2)how to pause or stop during sysprep and capture for any tweaks 3)reference machine has to be modify any registry or custom setting as part of prerequisites 4)sysprep and capture administrator password is mandatory 5) why we have to create 2 deployment share 6) what is difference if we capture image using SCCM build capture reference image operating system image and MDT Sysprep
1) reference machine administrator account should not have password
I always give my reference machines a local administrator password.
---
2) how to pause or stop during sysprep and capture for any tweaks
Before you start the sysprep and capture process, get the machine 100% completed. Once you start the capture process, trying to stop half way will cause issues.
---
3) reference machine has to be modify any registry or custom setting as part of prerequisites
Make any modifications and set any custom settings before starting the capture process.
---
4) sysprep and capture administrator password is mandatory
I always give my reference machines a local administrator password.
---
5) why we have to create 2 deployment share
This isn't a requirement, however, I find it is better to have a dedicated share for deploying images, and a dedicated share for capturing images.
---
6) what is difference if we capture image using SCCM build capture reference image operating system image and MDT Sysprep
They both do basically the same thing when it comes to capturing images. MDT is free, SCCM costs. (if you exclude Windows Server licencing)
---
Thanks for watching!
Thanks a lot, I didn't think of having a dedicated DS for capturing images, I'm always having issues with capturing windows 11 and when I run litetouch.vbs, it starts a few seconds then say all completed then nothing happens:; how come?