New
#1
Saving bandwidth when installing W10 in multiple computers
Hi,
I run a small computer repair shop and I have been testing W10 IP for some weeks now in anticipation of a slew of customers wanting my help to install W10 / upgrade to W10 on their computers.
I know about creating an ISO image from an ESD file in order to have myself a copy of W10 32 bit and W10 64bit. I already have a VM of each ready to upgrade to RTM on release and ready to copy and create the two ISO images I will need.
Would this be the normal way to do deployments / upgrades or is there a better way by simply copying the "$windows.~bt" folder from one machine to another? Apart from the x32 x64 aspect of the upgrade files in the said folder, are there any other tings in that folder that relate its contets to a specific machine (e.g. upgrade scripts and log files, drivers, AMD/Intel designation, etc.). What, if any are the benefits / drawbacks of each method (if the copy method indeed works).
Also, If I let the machines use the "download" option instead, is there a way to force the machines to only use the local network to obtain the files via the P2P feature in order to try and save my bandwidth. If so I could fire up the appropriate VM and somehw point the machine to its copy of the files. Perhaps a registry file to limit it and then another file to revert to standard as part of my build effort.
The key thing is to minimise bandwidth and speed up the download phase on my meagre connection but at the same time to leave the finished computer in a "normal" state for the end user upon return so the updates work corretly for them in their own envronment (and their own broadband connections).
Thanks for any tips
Cheers,
Paul.