Windows 10: Importing Flash packages into Deployment Workbench for multiple Windows 10 releases

Hi - I'm wondering if anyone else has seen this behaviour and, if so, how they've gotten around it.


I have Deployment Workbench organised into folders representing different releases of our image - our current image is based on 1709 and I'm starting work on a new image based on 1809, so I now have 2 sets of folders within each category - one for the 1709 image and one for the 1809 image.

I've successfully imported the latest security package for Win10 1809, but when I try and import the Jan '19 Flash security package for Win10 1809 the import wizard gives me the following:

Not copying existing package C:\Users\prrobinson\AppData\Local\Temp\MSUexpand\Windows10.0-KB4480979-x64.cab

Copying existing item Package_for_KB4480979 neutral amd64 10.0.1.0 from DS006:\Packages\1709 to DS006:\Packages\1809.


This is, I assume, because I've previously imported the 1709 specific Jan '19 Flash package.

If I try and build my 1809 image with the 1709 Flash package, the build understandably fails with a DISM error.


So my question is this - how do I import and manage the monthly Flash packages for both my current build (based on 1709) and new build (based on 1809) within the same Deployment Share?


Looking forward to hearing from you - and if I need to provide more detail just let me know!

:)

 

Importing Flash packages into Deployment Workbench for multiple Windows 10 releases

Hi - I'm wondering if anyone else has seen this behaviour and, if so, how they've gotten around it.

I have Deployment Workbench organised into folders representing different releases of our image - our current image is based on 1709 and I'm starting work on a new image based on 1809, so I now have 2 sets of folders within each category - one for the 1709
image and one for the 1809 image.

I've successfully imported the latest security package for Win10 1809, but when I try and import the Jan '19 Flash
security package for Win10 1809 the import wizard gives me the following:

Not copying existing package C:\Users\\AppData\Local\Temp\MSUexpand\Windows10.0-KB4480979-x64.cab

Copying existing item Package_for_KB4480979 neutral amd64 10.0.1.0 from DS006:\Packages\1709 to DS006:\Packages\1809.

This is, I assume, because I've previously imported the 1709 specific Jan '19 Flash package.

If I try and build my 1809 image with the 1709 Flash package, the build understandably fails with a DISM error.

So my question is this - how do I import and manage the monthly Flash packages for both my current build (based on 1709) and new build (based on 1809) within the same Deployment Share?

Looking forward to hearing from you - and if I need to provide more detail just let me know!

 

Importing Flash packages into Deployment Workbench for multiple Windows 10 releases

Hi PRRobinson

My name is Sarah Kong and I am an independent adviser that is here to try and help you with your issue.

I know this question is for windows 10 updates but I think it would be best suited to ask in the WDS deployment forums.

The experts there have more experience with imaging.

I have provided the link below.

Have a great day!

https://social.technet.microsoft.com/Forums/en-...

 

Customised Windows 10 deployment on multiple desktops and laptops.


OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx