TABLE OF CONTENTS This chapter covers the process of RIPrep and gives an overview of CD (flat) images versus RIPrep images. By using an RIPrep image, it's possible to include applications, drivers, and specific configured desktops to the image and then upload it back to the RIS server. Deploying an RIPrep image can be a fast way to deploy a full business platform to clients. This chapter also covers the prerequisites for RIPrep, how to create RIPrep images, and how to validate RIPrep images. There will also be some common entries that must be changed in the RIPrep SIF. These settings are covered in this chapter.
Highlights:
Overview of RIPrep
RIPrep prerequisites
Creating RIPrep images
Standard changes to be modified in the SIF
Validating RIPrep images
By using RIPrep, it's possible to deploy an image with applications built into it, deploying special drivers or special configurations. This approach gives a full-blown image deployed to clients in a time-saving way. The only two catches are maintains of all images and the dependence of the hardware abstraction layer (HAL); if a computer needs an RIPrep image and the image doesn't have the same HAL, then the image installation will not show in the image list on the OSC screen. By using RIPrep images, it's possible to deploy the same image to multiple computers. This can be done because the RIPrep process strips out unique information in the image (e.g., SID, hostname).
The RIPrep image uses the same file structure as the original...
