JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11 Automated Installer     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information

Preface

1.  Comparing JumpStart and Automated Installer

Similarities and Differences Between JumpStart and AI

JumpStart to AI Migration Information

2.  Converting Rules and Profile Files

3.  Converting Configuration Files

4.  Installing Oracle Solaris 10 Using JumpStart on an Oracle Solaris 11 Server

Similarities and Differences Between JumpStart and AI

Both JumpStart and AI provide hands-free installation of multiple systems on a network. Clients are network booted, and once the client is booted, the installer takes over.

JumpStart installs the Oracle Solaris 10 OS and earlier versions of the Oracle Solaris OS. AI installs the Oracle Solaris 11 OS.

JumpStart and AI share the following characteristics:

Table 1-1 Comparing JumpStart and AI Steps

Step
JumpStart
AI
Set up an install server.
Use the setup_install_server(1M) command.
Use the installadm create-service command.
Add clients to the installation.
Use the add_install_client(1M) command.
Use the installadm create-client command.
Create derived profiles
Use a begin script.
Use the derived manifests mechanism.
Specify installation instructions.
Use profile files.
Use AI manifest files.
Provision the client.
Use DVDs.
Use a package repository on the Internet or on a local network.
Specify client customizations.
Use rules files to associate clients with profile files.
Use the create-manifest, create-profile, or set-criteria subcommands of the installadm command to associate clients with AI manifests and system configuration profiles.
Specify client configuration.
Use finish scripts and sysidcfg(4) files.
Use SMF system configuration profile files. Use scripts executed by an SMF service that runs once at first boot.