Regan S., Pugh D. Apple Training Series(c) Mac OS X v10. 4 System Administration Reference / Lesson Review

Computers & Technology
Education & Reference
Business & Investing
Science & Math

Apple Training Series(c) Mac OS X v10. 4 System Administration Reference
Authors: Regan S., Pugh D.
Published year: 2006
Pages: 28-30/128

Buy this book on amazon.com >>

<< Previous page
Table of contents
Next page >>

Lesson Review

1.	When is it better to use package installation as opposed to drag-and-drop installation?
2.	How is a metapackage different from a package?
3.	What scripts can be run during installation?
4.	Describe the scenarios for how owner and permissions are determined on installed files and folders.
5.	How do you localize installation?

Answers

1.	It's best to use package installation when processes need to be started or stopped , or the install needs to put software in multiple locations throughout the system. Package installation is also preferred when you need to verify that certain components are already on the system or that a certain version of Mac OS X is being used. Another reason to use package installation would be to automate the process of mass software installation. Installer packages allow you to have a professional-looking appearance that is customized to your particular software, is easy to use for users, and can be used to upgrade software.
2.	A metapackage contains other packages and metapackages to install.
3.	These scripts can be run during installation: preinstall, postinstall, preupgrade, postupgrade, preflight, postflight, InstallationCheck, and VolumeCheck.
4.	If authentication is not required, all new files and folders are installed as the user that runs Installer. If authentication is required, ownership is determined by the owner of the files within the package. Permissions always follow the files within the package for new files and folders. Existing folder permissions will not be changed unless Overwrite Permissions is selected in PackageMaker.
5.	Put the resources for each language in its own folder called languagename .proj.

References

Knowledge Base Articles

You can check for new and updated articles in the AppleCare Knowledge Base, at www.apple.com/support.

URLs

Visit the following sites for more information:

Composer: JAMF Software: www.jamfsoftware.com/products/composer

Iceberg: White Box: http://s.sudre.free.fr/Software/Iceberg.html

Introduction to Software Distribution: http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareDistribution/index.html

logGen: LSA Mac OS X Software: www.lsa.umich.edu/lsait/admin/mac/software/index.asp

Pacifist: CharlesSoft: www.charlessoft.com

PackageMaker Pro Tips: www.macdevcenter.com/pub/a/mac/2003/09/16/packagemaker.html

Technical Q&A QA1281: Correcting a PackageMaker version.plist and BundleVersions. plist Problem: http://developer.apple.com/qa/qa2001/qa1281.html

Lesson 4. Delivering Images and Packages

Time	This lesson takes about 2 hours to complete.
Goals	Install Mac OS X and Mac OS X Server on multiple remote or local workstations using ASR images
	Create and deliver custom installation packages for Mac OS X and Mac OS X Server
	Configure Mac OS X Server to store and deliver NetBoot and Network Install images through NetBoot services
	Configure multiple install packages for use with a Network Install image

Learning how to plan your deployment, create and manage images, make custom packages, and check for software revisions is critical to a successful mass deployment operation. But if the method of image delivery does not work well within your environment (network setup, security, physical location of Macs), time may be wasted , networks may get clogged with traffic, and your entire deployment project may suffer as a result.

In this lesson, you will learn how to install Mac OS X v10.4 on multiple computers by delivering your master image both locally and over a network. You will set up your image for NetBoot startup and perform updates with packages and scripts. The methods you learn in this lesson will allow you to automate the process of image delivery so that you can present a low-maintenance, consistent interface to your users.