Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com
Answertopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

SUSE Linux Enterprise Desktop Deployment Guide
Previous Page Home Next Page

2.2 Deploying up to 100 Workstations

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:

Simple Remote Installation via VNC—Static Network Configuration

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.

Simple Remote Installation via VNC—Dynamic Network Configuration

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.

Remote Installation via VNC—PXE Boot and Wake on LAN

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.

Simple Remote Installation via SSH—Static Network Configuration

Consider this approach in a small to medium scenario with static network setup. A network, network installation server, and SSH client application are required.

Remote Installation via SSH—Dynamic Network Configuration

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.

Remote Installation via SSH—PXE Boot and Wake on LAN

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.

Simple Mass Installation

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.

Rule-Based Autoinstallation

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

  • Setting up an installation source

  • Booting from the installation media

Control and Monitoring

Remote: VNC

Best Suited For

small to medium scenarios with varying hardware

Drawbacks

  • Each machine must be set up individually

  • Physical access is needed for booting

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

  • Setting up the installation source

  • Booting from the installation media

Control and Monitoring

Remote: VNC

Best Suited For

Small to medium scenarios with varying hardware

Drawbacks

  • Each machine must be set up individually

  • Physical access is needed for booting

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

  • Setting up the installation source

  • Configuring DHCP, TFTP, PXE boot, and WOL

  • Booting from the network

Control and Monitoring

Remote: VNC

Best Suited For

  • Small to medium scenarios with varying hardware

  • Completely remote installs; cross-site deployment

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

  • Setting up the installation source

  • Booting from the installation media

Control and Monitoring

Remote: SSH

Best Suited For

  • Small to medium scenarios with varying hardware

  • Low bandwidth connections to target

Drawbacks

  • Each machine must be set up individually

  • Physical access is needed for booting

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

  • Setting up the installation source

  • Booting from installation media

Control and Monitoring

Remote: SSH

Best Suited For

  • Small to medium scenarios with varying hardware

  • Low bandwidth connections to target

Drawbacks

  • Each machine must be set up individually

  • Physical access is needed for booting

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

  • Setting up the installation source

  • Configuring DHCP, TFTP, PXE boot, and WOL

  • Booting from the network

Control and Monitoring

Remote: SSH

Best Suited For

  • Small to medium scenarios with varying hardware

  • Completely remote installs; cross-site deployment

  • Low bandwidth connections to target

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

  • Gathering hardware information

  • Creating AutoYaST profile

  • Setting up the installation server

  • Distributing the profile

  • Setting up network boot (DHCP, TFTP, PXE, WOL)

    or

    Booting the target from installation media

Control and Monitoring

Local or remote through VNC or SSH

Best Suited For

  • Large scenarios

  • Identical hardware

  • No access to system (network boot)

Drawbacks

Applies only to machines with identical hardware

Details

Section 5.1, Simple Mass Installation

Table 2-11 Rule-Based Autoinstallation

Installation Source

Preferably network

Preparations

  • Gathering hardware information

  • Creating AutoYaST profiles

  • Creating AutoYaST rules

  • Setting up the installation server

  • Distributing the profile

  • Setting up network boot (DHCP, TFTP, PXE, WOL)

    or

    Booting the target from installation media

Control and Monitoring

Local or remote through SSH or VNC

Best Suited For

  • Varying hardware

  • Cross-site deployments

Drawbacks

Complex rule setup

Details

Section 5.2, Rule-Based Autoinstallation

SUSE Linux Enterprise Desktop Deployment Guide
Previous Page Home Next Page

 
 
  Published under the terms of the Open Publication License Design by Interspire