Solved Making a server for cloning a computer on many machines

[baratanich]

Hi,

I have captured an image of a machine that I would like to deploy on multiple computers. I know that I can go to every single machine with my image and deploy it!

I wanna know if it is possible to use one of the machines that are running windows 7 as a server and copy the wim file to that server to deploy the image from the server instead of the Hard drive.

*all the computers are connected to a lan switch*

Thank you for your help!

 

[Layback Bear]

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.

 

[baratanich]

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

around 22 computers.

 

[Layback Bear]

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

 

[baratanich]

I have a Volume License and I activated the captured WIM.
I have another captures that is on a 30 day trail. I wanna try to install that one first then will deploy the licensed image.

I am asking about how to make a server?

 

[Layback Bear]

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

 

[Kari]

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/library/dd744343(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/server-cloud/products/windows-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/library/jj648426.aspx

Good luck!

Kari

 

[Layback Bear]

Thank you Mr. Kari for coming to help.

 

[Kari]

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.

 

[Layback Bear]

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.

 

[Kari]

A local domain running in Windows Server OS is practical even in relatively small networks. You can for instance login with any domain account to any of the joined machines, without separately setting up that account on each PC. This adds to security; each user profile is stored on server, user has access to all integrated apps on any machine. Applications and updates can be installed from server, and so on.

Centralized group policies is another added security feature; set up group policies on server and they are applied to all domain users on all machines.

 

[baratanich]

Thank you so much for your help!
the machine I captured is full of games that is why the size of the image is HUGE :sarc:
I watched the tutorials and made an AD successfully but i found out that doing it from my external hard-disk is faster then the server
So I finished around 7 machines and connected them to the domain successfully. Doing the rest slowly one by one.

Thank you again for those tutorials.

 

[Kari]

Thank you so much for your help!
the machine I captured is full of games that is why the size of the image is HUGE :sarc:
I watched the tutorials and made an AD successfully but i found out that doing it from my external hard-disk is faster then the server
So I finished around 7 machines and connected them to the domain successfully. Doing the rest slowly one by one.

Thank you again for those tutorials.

I must be honest with you: Your 170 GB image you want to deploy to over 20 machines being full of games, there's no way I am going to believe you that's not piracy. I know no games that will sell "volume licenses", allowing this.

I am ashamed and disappointed for assisting piracy.

 

[baratanich]

I was talking about windows volume license!

Before calling others criminals if you knew a little about games you would also know that gaming is done through clients like steam or origin nowadays and multiplayer doesn't work without purchasing the game. I am ashamed for taking assistance from someone like you!

you can send me a ticket on my paypal and get some money for your technical support instead of flaming me for the little help you gave me.

 

[Kari]

There's no way you 170 GB image deployed to over 20 computers is legit. Please do not even try to convince me.

 

[baratanich]

I don't even care about doing so!