Making a server for cloning a computer on many machines

Exactly what Windows 7 image did you capture?
How many computers do want to deploy the image to?

I don't know how to do such a thing but this information would be helpful to members that do know how to do such a thing. If it can be done.

What method do you intend to use to properly activate 22 computers with Ultimate?

I have went back to the ranch and requested more help with your request.
Just hang in there.

The procedure is fairly simple, although as often in computing it looks more complicated than what it really is. Basic knowledge of Windows Server, AD (Active Directory) domain services and WDS (Windows Deployment Services) are needed.

From https://technet.microsoft.com/en-us/...(v=ws.10).aspx

Introduction to Windows Deployment Services

Windows Deployment Services is the updated and redesigned version of Remote Installation Services (RIS). You can use it to install Windows to computers over a network instead of installing each operating system directly from a CD or DVD. To use Windows Deployment Services, you should have a working knowledge of common desktop deployment technologies and networking components, including Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory® Domain Services.

To implement this technology, first you install and configure Windows Deployment Services. Then, add the default images from the \Sources directory of the installation DVD to the server. This includes the Windows installation image (Install.wim) and the Windows PE boot image (Boot.wim). The Boot.wim file contains Windows PE and the Windows Deployment Services client. The client is Setup.exe with some additional functionality needed for network deployments.

After you have at least one of each image on the server, you are ready to deploy Windows images. Now, when you boot a computer using Preboot eXecution Environment (PXE), the Windows Deployment Services server responds to the PXE requests and loads the Boot.wim file into the RAM of the computer. Then, you can select which Windows image to install on the computer. You can also perform more advanced tasks like creating Windows images using capture images, creating discover images for computers that are not capable of PXE booting, and configuring an unattended installation.

(Notice please: the above quote is from article about Windows Server 2003 and 2008. I used the quote because it still is in my opinion the best summary about WDS in all MS TechNet I have found.)

You start with setting up a Windows Server and an AD domain controller. Your idea about using Windows 7 as deployment server will not work. You can set up your server using the free Windows Server 2016 Technical Preview 4 server operating system, free download at https://www.microsoft.com/en-us/serv...s-server-2016/

On our sister site the Ten Forums I have posted some videos about installing and setting up Windows Server 2016 and setting up an AD domain controller. These short videos might be useful for you if you have no previous experience in using Windows Server operating systems:

• Windows Server 2016 Part 1 - Install and setup - Windows 10 Forums
• Windows Server 2016 Part 2 - Setup an AD Domain Controller - Windows 10 Forums
• Windows Server 2016 Part 3 - Add Domain Users - Windows 10 Forums
• Windows Server 2016 Part 4 - Join Windows PC to a Domain - Windows 10 Forums
• Windows Server 2016 Part 5 - Rename a local domain - Windows 10 Forums

All videos from thread Windows 10 instructional videos by Ten Forums members - Windows 10 Forums

When you have WS2016 running and the domain created, next step is to install WDS. This Microsoft TechNet article will give you detailed instructions in installing WDS and deploying your Windows image over the network: https://technet.microsoft.com/en-us/.../jj648426.aspx

Good luck!

Kari

Thank you Mr. Kari for coming to help.

baratanich said:

Windows 7 ultimate.
The size of the image is 170 Gb.

around 22 computers.

My only doubts regarding this particular case is the incredible size of the image OP mentioned (170 GB). That sounds unrealistic, in many ways.

For instance I have difficulties to even think of a combination of applications that would need as much space, not to mention the time needed; transfer with Gigabit Ethernet in ideal theoretical conditions without any whatsoever overhead, it would take 23 minutes, but in a bit more realistic scenario let's say the average transfer speed would be 150 Mbps, it would take over 2 and a half hours. Per machine. Only the transfer, excluding the time needed for Windows setup.

I have watched all 5 of your tutorials. Very impressive. Well done.
Makes me want to try Windows 10 server and I don't even need it.
I have a extra Intel 240gb ssd I'm not using.
I surly well look deeper into things farther.

Once again; job well done.