Unattended installation (Windows)

from Wikipedia, the free encyclopedia
This article should be edited. Details should be given on the talk page. Please help to improve it , and then remove this flag.

In an unattended installation ( English unattended installation ) is the complete setup of a program or installer through, are without during which user input required. The term itself is only of marginal importance outside of Windows , since installation routines that require user input during the process are not common in other operating systems. In addition, automated installation mechanisms have a long tradition under HP-UX , Solaris , Linux or AIX . This form of program installation has been used since Windows 2000 and Windows XP in connection with slipstreaming (the integration of Microsoft Service Packs into the installation medium) and the option, since Windows NT times, of installing the operating system itself using a "setup installation file" (SIF) to automate.

Entries during the installation, such as the desired installation path, a license key that may be required or the acknowledgment of confirmations, are not required in the case of an unattended installation, since these settings are previously specified in a script (a so-called response file ) or with a specific command line parameter. In most cases, the installation time is noticeably reduced, since there is no waiting for input and several installations can be carried out one after the other. If the same software is to be installed on several computers , this automation of the installation can save a considerable amount of time, since it can be configured once, carried out as often as required and, in contrast to the memory image, on a wide variety of systems without taking up any additional work time.

In addition, unattended installation is also used when new computers are sold. In contrast to a full unattended installation , however, a special mode is used here. This allows the OEMs to install all computers with the same software and settings, but the buyer is able to enter data such as his name, the time and the serial number in the last part of the setup when the computer is started up for the first time and thus to individualize the installation .

Installation of a complete operating system

By script

In addition to the option of installing individual programs automatically, the entire operating system can be preconfigured. All system settings (user accounts, desktop background, network settings, etc.) can be stored in a script beforehand. Using a batch script, for example, additional software applications or drivers that are not included in the standard delivery scope of the Windows CD are installed when the operating system is installed.

Once the entire process has been configured, the system can be easily maintained or updated.

This method is particularly suitable in larger companies, where the computers will usually not have the same hardware. Each PC does not have to be looked after individually, because each computer independently processes the prepared script.

Via memory dump

Windows also makes it possible to use the 'SYSPREP.EXE' file (contained on the Windows CD) to prepare a completely installed PC so that it can be transferred to another computer using memory dump software . This method is particularly suitable when setting up new departments or as preparation for training courses in which several identical computers have to be reinstalled.

advantages

The centralization is particularly advantageous. If the data of the unattended installation is updated, for example new hotfixes are integrated, all computers will receive the latest updates during a new installation , so that the previously known security gaps are closed.

Further security is achieved in that all security-relevant aspects can be decided before the computer is installed and then implemented in a script. For example, the necessary installations can be carried out automatically as an administrator, while the user is then only available to the limited user for operation.

Therefore, this method is not only suitable for companies, but is also recommended for the home PC, since without the latest updates the computer could be infected by viruses the first time it comes into contact with the Internet , see W32.Blaster .

Installation of individual programs

There are various options for installing the programs unattended. Each of these methods offers advantages and disadvantages to be weighed up in the individual case.

Through parameters

Many, but not all, programs can be preconfigured using special command line parameters.

General syntax : 

 installationsdatei.exe <parameter1> <parameter2> <parameterN>

Often the available parameters by calling can , (or instead , enter) are displayed. Alternatively, the required information may be available directly in the program documentation, or it can be derived from the knowledge of the Windows Installer used . Often, for example, the switch , / s , / quiet or / q can be used to start an installation in which the program is installed on the hard drive without any further configuration during setup. It is important to pay attention to the upper and lower case of the respective parameter, a lower case parameter does not always apply (e.g. 7-Zip [7z465.exe / s]) so that the parameter / S must be written in upper case for Silent, in order to be recognized and carried out by the application. dateiname.exe /?dateiname.exe -??help/silent

However, the installation can usually hardly be configured using parameters. In addition to the option for unattended installation and the installation path, other configurations can only rarely be set using the switches. If further options of the program are to be preset, this can be implemented by additional Windows registry entries, provided that the corresponding entries are known. Further information can be found under software distribution and the guides listed below.

With Windows Installer switches and MST specifications

With the Windows Installer technology (file names with MSI extension), all parameters can be specified, either by specifying them via command line parameters (for example: "INSTALLLEVEL = 100 REBOOT = ReallySuppress"), or by collecting them in a so-called transform file ( MST extension). The MST files are able to overwrite all tables in the MSI database in order, for example, to determine the exact selection of the components required for installation. As of Windows 2000, MSI files for distributing software within a domain are natively supported ( IntelliMirror feature), but starting via a batch file is also possible: 

msiexec.exe /i <.msi-Datei> /qb- INSTALLLEVEL=300 REBOOT=ReallySuppress /L*v C:\Installationslog.log

In the above example, a log file is also generated, which can then be used for detailed control of the success or failure of the installation. .msi files also support slipstreaming if the updates are released as so-called MSI patch files (.msp extension). This technology brings the installation package itself up to date; H. When installing the updated version, the old version of the files is no longer installed and then patched to the latest, but the latest versions of the files and registry keys are written directly. The actions and any dialogs that the installation package also performs can also be updated.

With snapshots

Furthermore, a snapshot program can record all data and registry database changes that a program creates / changes during installation, so that these only have to be copied to the hard disk for unattended installation.

In the case of complex products, the snapshot process leaves a certain uncertainty as to whether the created package is installed under all circumstances as the original installer of the software manufacturer would have done. Many software companies therefore initially reject support for software errors that occur with snapshot-packaged clients, and require verification with a manual installation.

In any case, the prerequisite is that no components were installed on the computer on which the snapshot was taken that would then be missing on the clients and needed by the installation.

Through scripts

Scripts save the keyboard and mouse inputs to be executed one after the other (for example tab, tab, tab, "C: \ Program1", enter). This allows the configuration of the installation to be precisely planned and saved.

If the software does not offer its own option for automated installation, the inputs to be made can therefore be implemented, for example, by a WSH , VBS script or autoitscript or the Autohotkey offshoot.

With the "automated manual installation" problems arise when unexpected windows appear that were not foreseen in the script. Another difference is that snapshot installations can partially be carried out without having to interrupt work on the client. This procedure does not make sense with manually operated installations, since keyboard entries and mouse clicks by the user would conflict with those of the script.

realization

On the one hand, it is possible to provide the additional data on a separate, arbitrary storage medium , for example on a file server or a floppy disk / CD. On the other hand, the scripts and the additional programs / drivers can be integrated directly on a Windows installation CD .

Since a certain training period is necessary to create an unattended CD, especially if new drivers are to be integrated, several programs have recently been developed to support the creation of an unattended installation (see other programs ). In addition to a simpler configuration, these usually offer additional additions to the Windows system (such as minimizing the installation data).

However, if you create a script completely yourself, see web links , it is advisable to check whether the default settings configured in the script have been selected correctly. If, for example, some parameters are incorrect, the smooth process is no longer guaranteed, the installation would get stuck at one point, as it may be waiting for user input. The installation would therefore have to be canceled and the errors in the script cannot be eliminated, since the PC cannot now be used.

If no other computer is available on which the installation can be tested , it is therefore advisable to first emulate the entire installation using a memory image .

Programs that create an Unattended CD for Windows

  • nLite - For building Windows 2000, XP and Server 2003
  • vLite - For building Windows Vista, Server 2008, and Windows 7
  • XPlode

See also

literature

Deeper insights into the exact process of a Windows installation:

  • Microsoft Windows 2000 Professional. The technical reference, ISBN 3-86063-274-4
  • Microsoft Windows XP Professional - The technical reference (technical information and tools for Windows XP SP2), ISBN 3-86063-960-9 (see also link [1] )

Web links

Individual evidence

  1. ↑ http://linuxwiki.de/AutomatisiertInstallation
  2. ↑ autoitscript
  3. ↑ Autohotkey