Jump to content

3rd party Win 10 deploy tools

superatticman

By superatticman
in O/S Deployment

 Share

Recommended Posts

superatticman

superatticman

Posted
Posted

Hi all

 

Are there any recommended 3rd party deploy tools suitable for a small-medium size environment? We literally just want to deploy W10 via a USB stick (have a surplus of fast USB3 16Gb modules) but obviously want to streamline the process and get rid of all the 'home install' options. Being able to slipstream drivers and Windows Updates desirable too. Environment doesn't justify WDS etc. Most of their other software is cloud based.

 

Cheers

3s-gtech

3s-gtech

Posted
Posted
WDS is one of quickest services to deploy out, having done it twice in quick succession here (different subnets) - it doesn't take a lot to justify it and it's ace. Not sure of the right solution if you're set on using the sticks though!
dhicks

dhicks

Posted
Posted
Environment doesn't justify WDS etc.

 

Turns out the "etc" part might not be neccesary - you can set up WDS on a non-domain joined Windows server, then set up Windows install images complete with unattend.xml files to automate the install. I've got as far as setting up the new server, installing the WDS service and importing the latest Windows 10 image, I'd be interested to hear if there's a different option.

LeMarchand

LeMarchand

Posted
Posted

I find that W10 isn't too bad for finding drivers. It won't help skip the tedious setup steps but I'd be tempted to use a Ventoy disk, maybe with an extra partition for "difficult" drivers, (or even a standard MS Bootable install disk) and just install W10 from that if you want to avoid WDS etc.

 

I did find a way to make a "bootable from USB" full image, but it was quite complex. Guess it depends on how often you image.

  • Thanks 1
superatticman

superatticman

Posted
  • Author
Posted
I find that W10 isn't too bad for finding drivers. It won't help skip the tedious setup steps but I'd be tempted to use a Ventoy disk, maybe with an extra partition for "difficult" drivers, (or even a standard MS Bootable install disk) and just install W10 from that if you want to avoid WDS etc.

 

I did find a way to make a "bootable from USB" full image, but it was quite complex. Guess it depends on how often you image.

 

Yes...I think in this case, its probably worth just getting on with the standard install.

 

Regarding drivers, it would appear that the automatic installation of drivers appears to have changed about a fortnight ago? Unless any polices has specifically been configured, was usually the case that Windows 10 would start automatically adding drivers regardless of whether you had initiated W/U or not? Appears now that any drivers are now in the 'optional' updates and need to be manually agreed to. A bit of a pain if you ask me. Must be a setting somewhere to drag them down without needing to literally tick every box.

LeMarchand

LeMarchand

Posted
Posted
Regarding drivers, it would appear that the automatic installation of drivers appears to have changed about a fortnight ago? Unless any polices has specifically been configured, was usually the case that Windows 10 would start automatically adding drivers regardless of whether you had initiated W/U or not? Appears now that any drivers are now in the 'optional' updates and need to be manually agreed to. A bit of a pain if you ask me. Must be a setting somewhere to drag them down without needing to literally tick every box.

 

I've not noticed this (and have been using ISO install on some machines I can't get to PXE boot of late). I have noticed on some models that I had to go to the "optional" bit but generally most of the "main" drivers were auto-installed (display, network etc); it tends to be the IME stuff and possibly SD card readers that have to be chosen. It's still rare that I've had to actually search for and download a driver - but I may just be lucky!*

 

*On newer kit, at least. Ancient laptops are sometimes a bit harder - though the Bluetooth on some early HP 250s is the only thing I've had to give up on.

Dan2025

Dan2025

Posted
Posted

At my new place they use Macrium reflect which is pretty good for what we need. My old place moved to SCCM shortly after I left.

 

Just a case of getting a device to the point you want it without joining domain/anti virus if you don't use defender.

Then having a bootable USB with the software on and another with the images on.

 

May look at alternatives in the future but prior to this I'd done it manually for years.

Duke5A

Duke5A

Posted
Posted
Hi all

 

Are there any recommended 3rd party deploy tools suitable for a small-medium size environment? We literally just want to deploy W10 via a USB stick (have a surplus of fast USB3 16Gb modules) but obviously want to streamline the process and get rid of all the 'home install' options. Being able to slipstream drivers and Windows Updates desirable too. Environment doesn't justify WDS etc. Most of their other software is cloud based.

 

Cheers

 

I'm using WDS in my basement because it's that easy. As long as you have a 1Gb switched network and a Windows Server install somewhere. Right-Click add drivers to the console and various install WIMs. If you're absolutely set on using USB sticks then use Rufus to transfer an ISO to it and make it bootable. Inject your drivers via command line DISM into the install WIM. I seem to remember someone sharing a GUI frontend for DISM here that made things pretty easy.

superatticman

superatticman

Posted
  • Author
Posted (edited)
I'm using WDS in my basement because it's that easy. As long as you have a 1Gb switched network and a Windows Server install somewhere. Right-Click add drivers to the console and various install WIMs. If you're absolutely set on using USB sticks then use Rufus to transfer an ISO to it and make it bootable. Inject your drivers via command line DISM into the install WIM. I seem to remember someone sharing a GUI frontend for DISM here that made things pretty easy.

 

Probably this video here.

 

Explains how to easily inject drivers into your WIM. Will give this a go.

 

I suppose you can in theory put as many drivers as possible into your .wim? This can allow you to use it with different models etc. Just how intelligent is the installation process when it comes to selecting the correct driver? I guess it may get it wrong and you could end up with problems?

 

You can even 'export' all installed drivers via powershell and then use these to inject to the .wim The only problem here is that it will export absolutely everything including the stuff that is already on the installation media. Probably better off only using the drivers you actually need.

Edited by superatticman

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...