New
#11
For sake of science and curiosity I will test that when I can and let you know the result.
For sake of science and curiosity I will test that when I can and let you know the result.
I would slipstream the updates using NTLite. To get passsed the slowness of optical installation and where there may not be USB boot support, your next best option would be PXE booting.
PXE Server for Windows (UEFI & BIOS) - Serva
NTLite
Hi Simpilot, thanks for the suggestions.
I am much interested in learning about PXE Booting further, and had a look at Serva as linked but, despite Google existing, the jargon is a little prevalent there. Would you know of any similar program for a layman?
And as for your suggestions SIW2 don't worry have not forgotten am just not able to try them at the minute.
Many thanks
Fox Computers
This may be above your pay grade, but see if this video helps. There are others.
Serva Configuration for PXE Network Boot - Install any OS through LAN 🔥🔥🔥 - YouTube
The PXE booting process uses Windows file sharing or Samba.
Once you get the Serva configuration set up, then installing to all those notebooks is just a matter of going into their boot options and selecting PXE boot from there on out.
I'm pretty sure this is how manufactures do this. They use the network to install a custom slipstreamed version of Windows to all the computers in the factory.
- - - Updated - - -
I don't know why everyone has to use stupid music and WinRAR. 7Zip is a fine compression and will extract RAR archives. Not make them, but extract. 7Z has better compression last I saw.
- - - Updated - - -
Here's another method. Install Windows like a PRO! Windows Deployment Services Tutorial - YouTube
Remember, as always his name is Jeff.
You can really get down and nerdy with PXE in Android using Servers Ultimate. servers ultimate - Android Apps on Google Play
Note: WDS can also mean Wireless Distribution System.
Hi SIW2, hope you are well, sorry for the late update on this case. The parts for the high-performance PC arrived in dribs and drabs. Finally it is all assembled now and ready.
For testing, I installed Windows 10 Pro 64-Bit to a hard drive. At the first OOBE screen I went into Audit Mode, connected to the internet and fully updated it, then sysprep generalize shutdown. I have put this hard drive into the high-performance PC, which has an SSD in it with Windows 7 on with DISM++ installed.
Following your guide, it shows to save the image to f:\install.wim. In my case would this be correct please?
(I have already started capturing, if I have done it wrong I will just reinstall Windows 10 again onto the hard drive and try again according to your future response).
Thanks and best regards
Fox Computers
- - - Updated - - -
DISM++ finished capturing. I found the install.wim in the hard drive with Windows 10.
I am concerned I must appear dense. It would seem looking at it that you just save the install.wim wherever you wish, i.e. C:\Users\TestTower\Documents. But trying to save it there it would not accept it - hence why ask is it correct in my case to save it f:\ and still wonder if it matters that DISM++ has saved it to the very drive it was capturing?
- - - Updated - - -
Going to try the install.wim, found there was no install.wim in the windows media, instead only an install.esd. Fortunately DISM++ can convert.
More info @ How to generate install.esd, or have setup use install.wim - Microsoft Q&A
Still hoping for a response to this :)
Fox Computers
response to what?
It never occurred to me to save the captured wim file to the same partition that has been captured. I dont think there is any harm in doing so, but I normally save it somewhere else.
what is the question?
an .esd is a kind of super compressed wim. It takes up less space which might be useful for some purposes, but is harder to work with, it can't be mounted for example.Going to try the install.wim, found there was no install.wim in the windows media, instead only an install.esd. Fortunately DISM++ can convert.
windows setup.exe in win10 can recognise either .esd or .wim. But win7 windows setup.exe doesnt understand .esd files.
So if you want to use the regular win7 setup.exe, use .wim not .esd
If the .wim is too big it can be split into .swm files.