Windows 10: Can I deploy custom Windows 10 Home image on multiple devices?

First, all of my devices have licensed and activated on each device. I also have Office 365 which includes multiple accounts I can assign. I’m not attempting to sidestep payment or steal licenses, etc.


The problem is I have the curse of perfectionism and I want all settings for Windows, Office, and other programs to be identical...and the same for my storage devices on each pc. i.e. OS + apps on C:, docs and cache on D:, both of which are SSDs.


I have:

2 desktops and 1 laptop at home and

1 desktop and 1 laptop at work


My idea is to use Easeus migration tool to create the ISO copies.


Questions are...will this work, is it legal, and is there a better way to do what I want to do?

:)

 

Deploy And Customize Windows 10 Image

Hi,

I have been looking all over the internet, study and trying to understand how to customize my own image.

For Example:

Lets say I have 10-30 computers to manage and all of them need to be the same - applications, drivers, settings, etc..

so the solution is customize an image from a "reference computer" and deploy that image using WDS server.

I was confusing because there was so many methods and tools for accomplish that.

what I need is someone to describe all of this in some simple steps.

Thank you !

 

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

 

WIN10 activation of deployed image (Multiple PCs)


Hello tenforums!

After spending some 60 hours I taught myself how to image a hard disk, and spread it over the network using a switch and a master computer. My setup:

• 1 master PC with win10 image
• 1 switch
• 1 router with TFTP/DHCP
• 23 receiving PCs
• Clonezilla DRBL software for image deploying

I want my image to skip OOBE, as I already created an user account with the required software. I figured out how to skip OOBE with the unattend xml file, thanks to karis videos.

Now that I will deploy it to multiple computers (23 to be exact) I was wondering, how do we activate all of the 23 computers windows 10? Surely there is an easier way to do that than to insert the keys manually each time we spread the image and start every computer up. Then there are also keys for visual studio, etc.

What would be the best or easiest possible method to use?