updating image then capture again?

[chekmate1984]

Hi all

 

One school i just took over today have a image from 1709!

 

They reimage then do update etc.

 

I was thinking to apply image to a VM, put it back to workgroup, apply windows updates, software updates then do a capture. Would that work?

 

 

The previous company have removed the softwares folder, so currently will take time getting licenses for likes of smart notebook and numerous others. It will be a temp solution as we have around 30 devices to reimage by Tuesday!

[ThatBoringBloke]

I assume that you're just talking about doing a WDS image?

I've had issues tring to apply updates to an exiating image before, even when its never been domain joined.

Personally I'd go for a fresh lightweight image then deploy the software as needed.

[chekmate1984]

Thanks, i have had issues in past too was just hoping there be a work around but guess your right probably easier to just do light weight one first then add softwares via gpo as we go along

[howartp]

If you've only just taken over today, why the sudden need to update by Tuesday?

 

Yes they need updating but you need to get a good idea of your existing network before you go and reimage every machine then realise the important finance software was on that machine in the PE office that you just flattened.

[chekmate1984]

First thing i was told was the school has 30 laptops which was purchased year ago and nothing was done to it, part of msp agreement was to work on that first as priority. Luckily they are only for classrooms and not for admin staff or teachers so its not end of world if softwares are missing.

 

If i had my way yes i wouldve known network and know what software before i deploy as i feel i have to work on this again after few weeks for either software installs or reimage with the final image.

 

I am tempted to just dploy old image for now even if its 1709 and then reimage after few months once i get the new image sorted and maybe configure wsus for the updates in hope it does the 5 years worth of updates

[KK20]

plus it might be easier for you to look at getting WUFB to do all the hard work for you - easier than generating a brand new image, testing, rolling out etc. 1709 is so old that I doubt an extra month will make much of a difference in the scheme of things, plus its not your fault if the entire thing falls over tomorrow.

 

As for imaging, we are still OLD SKOOL for our windows 10, we have a lightweight audit mode "golden sample" that is created with the very base software we need (stuff that we have issues installing via GPO reliably - not much). This is then captured in a generalised state into FOG. FOG reboots the PCs if we trigger them (or trigger the PC rooms etc) and PXE boot and images them appropriately. 15 minutes later there is a domain logon ready on the PC with its correct name, OU, GPO software and all from the comfort of my desk. It has worked for me since W7 days. WUFB then triggers updates for the delta updates since the image was created.

 

This is not the modern way of doing things but it works for us. I would certainly look at scrapping WSUS if you are starting fresh, WUFB means no WSUS maintenance and it works.

Edited October 7, 2022 by KK20

[ITGuyNW]

I've done the VM thing before of keeping one VM, update, save, capture etc but I find it corrupts after a while. Now I just do a fresh image every year, customise the wim using wimwitch, add to WDS, boot using MDT, install the couple of bits I want embedded, capture then PDQ installs the rest when I image a machine.

[chekmate1984]

I have managed to create a new image, captured via WDS, imported to MDT

 

On MDT imported new drivers as have some new machines. Regen the boot file, compressed and from WDS did a replace

 

When i now boot up to WDS i get below error. I get this on a test VM and physical desktop/laptop.

 

Have i missed anything? it used to work fine before so assuming linked to driver update and updating the boot image as i cant get as far as loading MDT so dies within WDS

 

 

[ITGuyNW]

What drivers did you import? I generally only use audio, network and graphics. If you imported anything such as intel storage drivers it throws wobblers such as above.

[chekmate1984]

I sadly did all drivers that were in the dell driver deployment packs.

 

Can i delete all drivers and just import ones above then?