How to automate the installation of software and OS on working computers?

Question

System administration

Good day!
In general, the situation, there are many HP desks, as well as laptops. On the day you have to interrupt about 2-3 OS, this is usually either W8.1 Enterprise or W7 Enterprise. Both OSes have two different sets of software. How could it be possible to speed up the process of rolling the OS with firewood and software, except for PXE (system administrators will not bother to provide it to us in any way), and the ability to make adjustments to program assemblies is desirable.

Answer 1

Acronis True Image or its analogues, or along the way Pavel Perminov , but there is something suspicious, based on the question that Acronis will be better for you

Answer 2

It is very easy to automate - you set such a task to the system administrator, and that's it.

Answer 3

You can solve it in several ways or combine them depending on your realities
. We make several policies with different software packages for your needs.
2 Use the Microsoft System Deployment Tool (I don’t really know anything about it, I never used it seriously)
3 Make a reference machine, install all the software, prepare the machine for the first use using Sysprep, capture / deploy the image with your favorite imaging tool. In the reference image, you can install all drivers from all computer configurations; the first time you run the deployed image, the system will install only those devices that it finds.
4 Use automated task execution scripts, such as AutoIt. Not a complete solution, a lot will have to be completed by hand
5 Use bat scripts and so on. Quite a strange solution, but perhaps some problems can be solved

Answer 4

If all machines are identical in terms of system logic, then any HDD imaging tool.
It's closer to me like this:
1. We take out the hard disk from the finished PC and put it into the line machine
2. sudo dd if=/dev/sd? of=~/ready.img
3. We put as many disks from non-ready machines as we like into the same machine and do:
4. cat (or pv) ~/ready.img | tee >(dd of=/dev/sd?) >(dd of=/dev/sd?) | ddof=/dev/sd?
5. On the now ready machines, we change the names and network settings, if necessary.
+Theoretically, there are some automation tools for Windows. WAIK seems to be called. With it, you can make an image of the finished disk and use it during installation. He, like, will be able to immediately edit the names of the computers and other garbage.

Answer 5

If you need just small-scale mechanization without using server solutions - study the answer file for Win - it will automate the OS rolling forward.
If drivers are integrated into the OS distribution kit, this will solve the problem of their rolling after deployment.
Well, the software can be deployed using the PDQDeploy utility - it is shareware.

Answer 6

preparing ready-made images and deploying them over the network. soft-bodied have several options for the second act. You can google it yourself, I can leave the links. the first knee (TFTP), the second through the microsoft system center. there is also a third one. maybe someone will remind you. I got something out of my head.
images are prepared in 2 ways. either through deployment on a virtual machine, installing and updating everything and fooling, or through integration into a software image. consume a lot of information. so it's easier for you to google on the issue of interest.

Answer 7

I would recommend looking into the Microsoft Deployment Toolkit.
It allows you to include the required software and create both images with included software (thick image) and without it (thin image).
Or installing software through chocolatey - just add everything you need with scripts.
Well, after that, if something in the process does not suit you, study Windows Deployment Scenarios and Tools and choose what you like.
The second option is MDT with Windows Deployment Services. Even without PXE - you can create a USB boot that connects to your images on the WDS server and you can boot the right one.
WDS - a role for Windows Server 2008 and higher (it is written that it works since 2003 as an additional package, but I would use later versions to deploy W7 and W8)