bascast.blogg.se

1. #WINDOWS 10 1809 ISO SIZES INSTALL#
2. #WINDOWS 10 1809 ISO SIZES 64 BIT#
3. #WINDOWS 10 1809 ISO SIZES DRIVERS#
4. #WINDOWS 10 1809 ISO SIZES UPGRADE#
5. #WINDOWS 10 1809 ISO SIZES WINDOWS 10#

PS C:\WIM> Dism /Image:”C:\Mountwim” /Get-Packages Lets mount it in the folder C:\Mountwimĭism / Image : "C:\Mountwim" / Get - Packages

#WINDOWS 10 1809 ISO SIZES 64 BIT#

We want en-gb not en-us Language Features so head back over to the VLSC and download the FOD Disk 1.Ģ – Download the “Windows 10 Features On Demand (Updated Sept ’18) 64 Bit MultiLanguage Disk 1”Ĥ – Find the “en-gb” language feature CABs and copy them out to a folder, e.g. PS C:\WIM> dism /get-wiminfo /wimfile:install.wim The /delete image option syntax should look similar to:. We are only interested in the Enterprise Index (3). The /delete-image option does not apply to VHDs.Īs we have eluded to above. It does not delete the stream data and does not optimize the. The “/delete-image” command option, as per Microsoft, “deletes only the metadata entries and XML entries. Lets go one step further, lets check the version of Windows for the Index we are interested in:-ĭism / get - wiminfo / wimfile : install.

#WINDOWS 10 1809 ISO SIZES WINDOWS 10#

Name : Windows 10 Enterprise for Virtual Desktopsĭescription : Windows 10 Enterprise for Virtual Desktops wimĭeployment Image Servicing and Management toolĭescription : Windows 10 Pro for Workstationsĭescription : Windows 10 Pro N for Workstations From a Command Prompt, type:-ĭism / get - wiminfo / wimfile : install. In this example we use C:\WIM Examining the WIM Indexes The assumption is you are using the VLSC.Ģ – Download the Latest Windows 10 ISO (1809 Nov 18)Ĥ – Navigate to the mounted ISO: (drive):\sources and copy out install.wim to a new folder on your local disk.

#WINDOWS 10 1809 ISO SIZES DRIVERS#

DISM lets you enumerate drivers and packages, modify configuration settings, add and remove drivers, add Windows features and more. It comes as part of your OS and is accessible from a PowerShell or Command Prompt window. The Deployment Image Servicing and Management (DISM) tool is very powerful. The updates will iterate through each Index taking more than enough time out of your available day.

If you choose to Offline Service the original WIM, I hope you like coffee. Not ideal in an Enterprise environment.Īnother challenge with the OOB WIM – it contains 11 Indexes.

#WINDOWS 10 1809 ISO SIZES 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 SIZES 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.