kennysarmy Posted September 20, 2019 Posted September 20, 2019 Current OS deployed around the school using WDS/MDT is 2016 LTSB. It's about time I started investigating 1903 EDU, but it's been some time since I created my current image so just checking I've got things right in my head after not touching MDT for a few years! Does this sound right? Add base 1903 OS to MDT Deploy to test VM Customize OS Run SYSPREP Script "LiteTouch.vbs" / Task Sequence "Capture Image" Capture "Gold Image" back to MDT Create task sequence for stripping out "MS_CRAP" Deploy custom WIM and Test As far as my previous notes for Customize the OS go: Install .net 3.5 Install updates Remove Network and Homegroup options from the navigation pane Strip down the Right click start menu (http://www.edugeek.net/forums/windows-10/163286-windows-10-start-menu-working-solution-9.html#post1421421)
RLR Posted September 20, 2019 Posted September 20, 2019 We don't do any sys prepping any more. We just extract the WIM file from the ISO and upload the WIM file to MDT. The ISO contains quite a few different WIMs depending on the version of Windows that you want. For this reason, you need to find out what version of Windows you want to use and extract the correct WIM. You can do this by running: "dism /Get-WimInfo /WimFile:F:\sources\install.wim" This will list all the index numbers for each wim. You can then use the next command to extract the wim file. This command will get wim index number 2. dism /export-image /SourceImageFile:F:\sources\install.wim /SourceIndex:2 /DestinationImageFile:C:\W10\install.wim /Compress:max /CheckIntegrity We then only need to replace the OS Deploy task sequence with the new WIM so everything else is kept the same. Our start menu and task bar is deployed via an XML file at the end of the imaging process. We download the Cumulative Updates from https://www.catalog.update.microsoft.com/Home.aspx and add them to the task sequence. .Net Framework 3.5 is installed as a package also. 1
CHiLL Posted September 20, 2019 Posted September 20, 2019 Ditto @RLR. I haven't used sysprep since Windows 8.1. I just download the ISO from VLSC, extract the WIM use that in SCCM with MDT. The SCCM MDT Task Sequence is clever enough that once the WIM is selected, it lists the specific versions within the WIM and you can select the variant you want, no need to extract the specific version. I don't know about just MDT on it's own though. I create a new SCCM MDT TS for each new version of Windows 10 I deploy and match it with the appropriate MDT Tookkit settings. For image specific settings, I configure those in either unattend.xml, within the TS itself, GP settings or SCCM deployments. 1
kennysarmy Posted September 20, 2019 Author Posted September 20, 2019 Thanks - I'll give that a try. Think I'm a bit old school having needed to run SYSPREP when we rolled out Windows NT !
altecsole Posted September 20, 2019 Posted September 20, 2019 (edited) We don't do any sys prepping any more. We just extract the WIM file from the ISO and upload the WIM file to MDT. The ISO contains quite a few different WIMs depending on the version of Windows that you want. For this reason, you need to find out what version of Windows you want to use and extract the correct WIM. You can do this by running: "dism /Get-WimInfo /WimFile:F:\sources\install.wim" This will list all the index numbers for each wim. You can then use the next command to extract the wim file. This command will get wim index number 2. dism /export-image /SourceImageFile:F:\sources\install.wim /SourceIndex:2 /DestinationImageFile:C:\W10\install.wim /Compress:max /CheckIntegrity We then only need to replace the OS Deploy task sequence with the new WIM so everything else is kept the same. Our start menu and task bar is deployed via an XML file at the end of the imaging process. We download the Cumulative Updates from https://www.catalog.update.microsoft.com/Home.aspx and add them to the task sequence. .Net Framework 3.5 is installed as a package also. This. Install Windows, software, updates and pretty much everything else in your Task Sequence. Sysprep might make the install process quicker, but it'll never be as stable and trouble free as installing from scratch. Edited September 20, 2019 by altecsole 1
garethEds Posted September 23, 2019 Posted September 23, 2019 I am the same - a custom WIM using OSDeploy from David Segura and then pdqdeploy to get the apps out. I just drop a new wim in updated with the updates every month. Gareth 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now