Not ideal in an Enterprise environment.Īnother challenge with the OOB WIM – it contains 11 Indexes.
#WINDOWS 10 1809 ISO DEC INSTALL#
en-gb and you DO NOT install the en-gb Language Features, your users will be prompted to install it when they first log in. TIP: If you specify a language or locale in the “Specialize” pass of your unattend.xml e.g. It makes sense, the LCU might include updates to the aforementioned so we should be installing it first. It is recommended to install the Language Pack before installing Features on Demand and then the SSU/ LCU. For example, a common task performed when servicing a WIM is installing Language Packs or Features on Demand. We can simply import the default Install.wim from the Windows 10 boot media into SCCM and use that as our image for our Task Sequence.but here it comes The Challenge
It will cut down your post OSD remediation by a mile. Offline Servicing in SCCM is a great way to keep your WIM updated with the latest SSU/LCU and other Security Updates.
David Segura has a great tool called #OSBuilder which should demand your attention. There are nicer ways to service the WIM if you look after a larger environment. We cover installing some Features on demand to get the en-gb language features and the latest SSU/LCU.
#WINDOWS 10 1809 ISO DEC UPGRADE#
We will be looking at only the install.wim but considerations should be made to the upgrade media too. This post covered the basics for modifying and servicing the WindWIM. Not having looked at this before, I thought I would take the time to consider it for the new WindWIM used in our OSD Task Sequences. My good friend Leon over at posed a topic over chat re: Offline Servicing a WIM with SCCM.
0 kommentar(er)
