It happens sometimes where you just need to create a new boot.wim. This could be from injecting new drivers in my case... doh
1. So, to start off install ADK if you havnt done so already.
- visit my page HERE to see how to install the ADK
2. Start Deployment Tool Line as Admin

3. In this instance I was creating a x64 boot.wim and the command to run for this was
COPYPE.CMD amd64 c:\WINPE64\
FYI, Here are all the commands for the different architectures (you are welcome);
COPYPE.CMD x86 c:\WINPE86\ COPYPE.CMD amd64 c:\WINPE64\ COPYPE.CMD arm c:\WINPEARM\
4. Once run, navigate to the 'C:\WINPE64\Media\Sources' folder and copy the boot.wim to a share for use with SCCM.

5. In the SCCM console go to the Software Library workspace. Open Operating Systems>Boot Images. Right click and choose ‘Add Boot Image’.
6. Select the location of the boot.wim file and click Next.
7. Enter a name for the boot image and click Next. Continue through the wizard to completion.
8 . Ensure you select ‘Deploy this boot image from the PXE enable distribution point’ from the boot image properties.

9. Finally, distribute the boot image to a DP.
Comments