With a growing numbers of workstations to install, you certainly do not want to install and configure each one of them manually. There are many automated or semiautomated approaches as well as several options to perform an installation with minimal to no physical user interaction.
Before considering a fully-automated approach, take into account that the more complex the scenario gets the longer it takes to set up. If a time limit is associated with your deployment, it might be a good idea to select a less complex approach that can be carried out much more quickly. Automation makes sense for huge deployments and those that need to be carried out remotely.
Choose from the following options:
Consider this approach in a small to medium scenario with a static network setup. A network, network installation server, and VNC viewer application are required.
Consider this approach in a small to medium scenario with dynamic network setup through DHCP. A network, network installation server, and VNC viewer application are required.
Consider this approach in a small to medium scenario that should be installed via network and without physical interaction with the installation targets. A network, a network installation server, network boot images, network bootable target hardware, and a VNC viewer application are required.
Consider this approach in a small to medium scenario with static network setup. A network, network installation server, and SSH client application are required.
Consider this approach in a small to medium scenario with dynamic network setup through DHCP. A network, network installation server, and SSH client application are required.
Consider this approach in a small to medium scenario that should be installed via network and without physical interaction with the installation targets. A network, a network installation server, network boot images, network bootable target hardware, and an SSH client application are required.
Consider this approach for large deployments to identical machines. If configured to use network booting, physical interaction with the target systems is not needed at all. A network, a network installation server, a remote controlling application such as a VNC viewer or an SSH client, and an AutoYaST configuration profile are required. If using network boot, a network boot image and network bootable hardware are required as well.
Consider this approach for large deployments to various types of hardware. If configured to use network booting, physical interaction with the target systems is not needed at all. A network, a network installation server, a remote controlling application such as a VNC viewer or an SSH client, and several AutoYaST configuration profiles as well as a rule setup for AutoYaST are required. If using network boot, a network boot image and network bootable hardware are required as well.
Table 2.4. Simple Remote Installation via VNC—Static Network Configuration
Installation Source |
Network |
Preparations |
|
Control and Monitoring |
Remote: VNC |
Best Suited For |
small to medium scenarios with varying hardware |
Drawbacks |
|
Details |
Section 4.1.1, “Simple Remote Installation via VNC—Static Network Configuration” |
Table 2.5. Simple Remote Installation via VNC—Dynamic Network Configuration
Installation Source |
Network |
Preparations |
|
Control and Monitoring |
Remote: VNC |
Best Suited For |
Small to medium scenarios with varying hardware |
Drawbacks |
|
Details |
Section 4.1.2, “Simple Remote Installation via VNC—Dynamic Network Configuration” |
Table 2.6. Remote Installation via VNC—PXE Boot and Wake on LAN
Installation Source |
Network |
Preparations |
|
Control and Monitoring |
Remote: VNC |
Best Suited For |
|
Drawbacks |
Each machine must be set up manually |
Details |
Section 4.1.3, “Remote Installation via VNC—PXE Boot and Wake on LAN” |
Table 2.7. Simple Remote Installation via SSH—Static Network Configuration
Installation Source |
Network |
Preparations |
|
Control and Monitoring |
Remote: SSH |
Best Suited For |
|
Drawbacks |
|
Details |
Section 4.1.4, “Simple Remote Installation via SSH—Static Network Configuration” |
Table 2.8. Remote Installation via SSH—Dynamic Network Configuration
Installation Source |
Network |
Preparations |
|
Control and Monitoring |
Remote: SSH |
Best Suited For |
|
Drawbacks |
|
Details |
Section 4.1.5, “Simple Remote Installation via SSH—Dynamic Network Configuration” |
Table 2.9. Remote Installation via SSH—PXE Boot and Wake on LAN
Installation Source |
Network |
Preparations |
|
Control and Monitoring |
Remote: SSH |
Best Suited For |
|
Drawbacks |
Each machine must be set up individually |
Details |
Section 4.1.6, “Remote Installation via SSH—PXE Boot and Wake on LAN” |
Table 2.10. Simple Mass Installation
Installation Source |
Preferably network |
Preparations |
|
Control and Monitoring |
Local or remote through VNC or SSH |
Best Suited For |
|
Drawbacks |
Applies only to machines with identical hardware |
Details |
Table 2.11. Rule-Based Autoinstallation
Installation Source |
Preferably network |
Preparations |
|
Control and Monitoring |
Local or remote through SSH or VNC |
Best Suited For |
|
Drawbacks |
Complex rule setup |
Details |