The goal is to install a clean computer for Intune use or to reinstall a personal PC
A server or a computer with
- A share
- Windows ADK installed
- MDT installed
- A WDS server or a USB key for booting
- A DHCP server
Prerequisites
What you need
- A Windows 11 consumer or business ISO (do not use an ISO made with the Media Creation Tools)
- Installation of Windows ADK Windows 10 ou 11 ,
- Select the following options:
- For the Windows ADK module
- Deployment Tool
- USMT
- For the Windows ADK module
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/adkinstall.png)
- For the additional PE Windows module for the Windows ADK
- WinPE
Creating the Deployment Share
- Launch MDT using the “Deployment Workbench” shortcut, then create a new “Deployment Share”.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/070518_2202_TUTODployer3.png)
- Specify a local path and then validate the following screens (configuration will be done later) with the customsetting.ini and bootstrap.ini files.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/070518_2202_TUTODployer4.png)
Creating Boot Images
Manage Drivers
Create 2 directories in MDT that only manage WINPE drivers
- WinPEx86 => Used for 32-bit WinPE images
- WinPEx64 => Used for 64-bit WinPE images
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/MDT_WinPE_001.png)
Folder creation
- In “Out-of-Box Drivers”, create a new folder
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Dossier-WinPE.png)
- Specify the folder name and validate
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Dossier-WinPE2.png)
Downloading WinPE drivers
WinPE is based on Windows 10, you will need to download drivers for Windows 10
- You can use the Dell Driver pack : Download
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/070618_2215_TUTODployer3.png)
- Extract the cab with 7zip (ignore the 7zip error)
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/070618_2215_TUTODployer4.png)
Importing drivers
- In the WinPE folders of MDT, add the drivers
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/import-drivers-1.png)
Creating profiles
- You then need to create 2 profiles in MDT
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/MDT_WinPE_1001-1024x679.png)
- The profiles will point to the corresponding WinPE driver folders
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/MDT_WinPE_1002-1024x679.png)
Associating profiles in WinPE
- In the properties of the DeploymentShare
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/propertyDP.png)
- Select the WinPE driver profiles for x86 and x64
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/MDT_WinPE_1003-1024x679.png)
Bootstrap.ini
You can modify the bootstrap.ini file
- The path of the deployment share => DeployRoot
- The path of the deployment share => KeyboardLocalePE
- Authentication => UserID, UserDomain et UserPassword
If the authentication account is not specified, a popup asking for authentication will be displayed during deployment.
Exemple file
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | [Settings] Priority=Default [Default] ; Indiquez le chemin UNC de votre deploymentshare DeployRoot=\\dc.leblogosd.lan\MDT ; N'affiche pas l'ecran de bienvenue SkipBDDWelcome=YES ; Passe le clavier en francais KeyboardLocalePE=040c:0000040c ; Si le compte n'est pas indiqué, il faudra renseigner un compte avec des droits sur le partage UserID=UserMDT UserDomain=leblogosd UserPassword=Password1 |
Boot image
The boot images contain a WinPE with the tools to connect to the deployment share.
- To generate the WinPE, right-click on the deploymentShare, then select “Update Deployment Share”
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/u-01.png)
- Select “Completely regenerate the boot images” and validate.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/u-02.png)
- Once the images are generated, you can use them for deployment.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/folderISO.png)
- You will need to use the ISOs or the LiteTouchPE WIMs.
Adding Windows 11 Sources
- In “Operating Systems”, select “Import Operating System”
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Import-OS-01.png)
- Select “Full set of source files”
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Import-OS-02.png)
- Then select your drive (physical or virtual) containing Windows 7 or 10.
- Validate the following screens.
New Task Sequence
You will need to create a task sequence
- Right-click on “Task Sequence”, then select “New Task Sequence”
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/ts-01.png)
- Enter the ID (this will be used to create a folder in the control directory of your DeploymentShare).
- Enter the name.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/mdtoobe01.png)
- Select “Standard Client Task Sequence”.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/mdtoobe02.png)
- Select the OS you want to install.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/mdtoobe03.png)
- The task is now available.
Drivers
- We will simply create a folder for each workstation model we will manage. Another article will detail a more comprehensive driver management.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Dossier-WinPE-1.png)
- Select “Import Drivers”.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/import-drivers.png)
- Select “Import Drivers”.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/import-drivers2.png)
CustomSetting.ini
The customsetting.ini file allows you to configure the MDT wizard and some deployment options.
The file is located in the control folder of your deployment share.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/customsetting.png)
The customsetting.ini file I use
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y _SMSTSOrgName=%TaskSequenceName% SkipTaskSequence=No SkipComputerName=NO OSDComputerName=%SerialNumber% SkipDomainMembership=YES SkipUserData=YES DeploymentType=NEWCOMPUTER SkipProductKey=YES SkipCapture=Yes SkipAdminPassword=Yes AdminPassword=azerty SkipPackageDisplay=Yes SkipBitLocker=YES SkipComputerBackup=Yes SkipLocaleSelection=YES SkipTimeZone=YES TimeZone=105 TimeZoneName=Romance Standard Time SkipRoles=YES SkipApplications=NO SkipAdminAccounts=YES SkipSummary=NO SkipFinalSummary=YES FinishAction=SHUTDOWN |
Applications
We will be able to manage 2 applications for this OOBE mode
- To OOBE mode : Win10_OOBE
- To OEM Activation : Activation_OEM_W10
Application to OOBE Mode
La ligne de commande pour passer en OOBE sera la suivante
1 | c:\windows\system32\sysprep\sysprep.exe /oobe /quit |
Application To OEM Activation
1 2 3 | $ProductKey = ( Get-WmiObject -Class SoftwareLicensingService).OA3xOriginalProductKey cscript "c:\windows\system32\slmgr.vbs" -ipk $ProductKey cscript "c:\windows\system32\slmgr.vbs" -ato |
Create Application
- To add applications, right-click on “Applications” then “New Application”.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Appmdt01.png)
- Select “Application with source files”.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Appmdt02-2.png)
- Specify the Application Name (ModeOOBE ou ActivationOEM)
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Appmdt03.png)
- Select the source directory of your application.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Appmdt04.png)
- Specify the command line for installing your application.
![](https://blog.wuibaille.fr/wp-content/uploads/2023/04/Appmdt05.png)
MDT is now ready to carry out installations in OOBE mode. You can use a boot USB key or a WDS to start your compute
0 Comments