Windows 10 1709 (Fall Creators Update) Changes to Media (ISO) on VLSC – ATTENTION!!

Microsoft Windows 10 1709 (a.k.a. Fall Creators Update a.k.a. FCU) was launched today.

Like on my previous post, you can download the installation media (ISO) from the usual relevant distribution channels: the Volume Licensing Service Center (VLSC), Windows Update for Business, Windows Server Update Services and Visual Studio Subscriptions (MSDN).

Now…for the ISOs that you download from VLSC or MSDN, you need to be aware on some changes.

Instead of separated media packages for each SKU (WIndows 10 Pro; Windows 10 Enterprise; Windows 10 Education), the Windows 10 v1709 that you download, will include in the ISO a single WIM file with all this version.

So, when using this ISO in tools such as Microsoft Deployment Toolkit (MDT) or Microsoft System Center Configuration Manager (SCCM) make sure you select the appropriate image index in you task sequence.

Here’s the index table for your reference and…save you some time:

Image Name	Index
Windows 10 Education	1
Windows 10 Education N	2
Windows 10 Enterprise	3
Windows 10 Enterprise N	4
Windows 10 Pro	5
Windows 10 Pro N	6

VDISM – Easy WIM Servicing and Control

So…although you’re a geek and you really like to create your own scripts for managing your WIM files, sometimes you feel that a GUI app would be just great and it would really be a time saver.

Some of you may already know a tool called GImageX but from my experience I think this one its superior.

VDISM, available throungh SourceForge website, it’s a fenomenal tool with a very simple interface that gives you access through a graphical interface to all things you need for servicing WIM files.
It’s really really easy to use and so intuitive that you will probably will not use command-line anymore.

Features:

• Driver Servicing
• Package Servicing
• Unattend Servicing
• Windows Edition Servicing
• Appx Servicing
• Application Servicing
• WIM Boot Entry Servicing
• Append Image Servicing
• Apply Image Servicing
• Capture Image Servicing
• Delete Image Servicing
• Export Image Servicing
• Image Info Servicing
• List Image Servicing
• Mount Image Servicing
• Split Image Servicing
• International Servicing
• Provisioning Package Servicing
• Default Associations

Go ahead and try this great tool: SourceForge – VDISM

Windows Deployment - Back to Basics - DISM - Drivers Management

Here's a post just to review some basic DISM (Deployment Image Servicing and Management tool) commands that are always useful when managing your base image:

Injecting drivers to boot.wim

DISM.exe /Mount-Wim /WimFile:C:\Mount\boot.wim /Index:1 /MountDir:C:\Mount\BootWIM

DISM.exe /Image:C:\Mount\BootWIM /Add-Driver /Driver:C:\Mount\Drivers /recurse

DISM.exe /Unmount-Wim /MountDir:C:\Mount\BootWIM /Commit

Viewing drivers on wim file

DISM.exe /Mount-Wim /WimFile:C:\Mount\boot.wim /Index:1 /MountDir:C:\Mount\BootWIM

DISM.exe /image:C:\Mount\BootWim /Get-Drivers

WDS - Injecting VMware VMXNET3 Driver Error

I'm creating a new WDS + MDT infrastructure almost from scratch and I'm using VMware for deployment and image creation.
Because I'm using VMware VMXNET3 for network and VMware ParaVirtual SCSI for storage I needed to inject this 2 drivers on my Windows Deployment Servers (WDS) boot image for installing the created images.

Doing this on MDT when creating the boot images for the litetouch deployment has no issue, but for the boot.wim for installing images (extracted for the sources\boot.wim of Windows DVD) something goes wrong.
For some unknown although the VMware ParaVirtual driver gets easily inject, the VMXNET3 driver don't.
Not really investigated the reason, but has a workaround, follow this easy steps.

So what we're going to do it's to inject the drivers on boot.wim file using DISM:

1. First copy the file from a DVD/ISO (it's located on "...\sources\boot.wim") and copy it to a local drive (ex.: D:\Temp\)


2. Than you'll need to mount the WIM file:
   DISM /Mount-Image /ImageFile:D:\Temp\boot.wim /Index:2 /MountDir:D:\Temp\MountPoint


3. Now, you're ready to inject the VMware VMXNET3 Driver (or any other drivers), you just need to point to the *.inf file:
   DISM /Image:D:\Temp\MountPoint /Add-Driver /Driver:D:\Temp\Drivers\VMwareVMXNET3\vmxnet3ndis6.inf


4. Drivers injected, now unmount and commit changes:
   DISM /Unmount-Image /MountDir:D:\Temp\MountPoint /Commit

And you're done!

Now you just need to publish that boot.wim on your WDS and deploy images.