Apple Remote Desktop 2.2 - Manual (Page 29)

Chapter 2 Setting Up 29
To install the client software for the first time:
1 Create the custom client install package.
For detailed instructions, see “Creating a Custom Client Installer” on page 36.
2 Copy and install the package on the client computers.
There are several ways to do this. For example, you can:
• Distribute the package by removable media, such as a CD
• Copy the installer to the clients over the network using file sharing
• Copy the installer to the clients using command-line tools like scp (if ssh is enabled),
and use Apple’s command-line installation tool, “installer,” to install the package
remotely. This process is described in detail in “Upgrading Existing Mac OS X 10.2
Client Software Using ssh” on page 29.
Upgrading Existing Client Software On Mac OS X 10.2
For Mac OS X 10.2 Jaguar computers using Apple Remote Desktop client software
version 1.2 or later, you can use the Upgrade Client Software feature to update client
software with Remote Desktop’s built-in features. If you choose not to use Remote
Desktop’s Upgrade Client feature, you can use the process described in “Installing the
Client Software on Mac OS X 10.2 for the First Time,” above, to upgrade Jaguar clients
manually.
Upgrading Existing Mac OS X 10.2 Client Software Using ARD
To upgrade ARD clients, find them in your ARD computer lists, or with a network scan.
To upgrade existing computers:
1 Open Remote Desktop.
2 Select a computer list.
3 Select one or more computers in the Remote Desktop window.
4 Choose Manage > Upgrade Client Software.
Upgrading Existing Mac OS X 10.2 Client Software Using ssh
You may not be able to use Apple Remote Desktop’s administration software to
upgrade existing Jaguar clients to ARD 2. The clients may have software older than
version 1.2, for example. If the clients have ssh enabled (called Remote Login in System
Preferences), and are available on the network, you can still upgrade the client
computers.
You still need to use the ARD administration software to create a custom installer
package. You also need the login name and password of a user with administrator
privileges on the client computer.
Warning: Custom installer packages that create login names contain sensitive
password data. Take care to store such custom installers securely.