Go to main content

Customizing Automated Installations With Manifests and Profiles

Exit Print View

Updated: November 2020
 
 

Associating System Configuration Profiles With Install Services

Like manifests, system configuration profiles must be associated with install services in order to be applied during installation.

When you create a profile instance, you are required to name a service for that instance. Thus, the command creates both the profile and its association with the service.

For example:

$ installadm create-profile -n solaris11_4-sparc -f ./profile-sparc-ent.xml \
-p sparc-ent
–n

Specifies the name of the service.

–f

Identifies the the XML file on which the profile instance is based.

–p

Specifies the name of the profile instance.

If you do not use this option, then the profile instance name is based on the base file name that is specified by the –f option, thus profile-sparc-ent.

The profile configuration is applied to all clients of the service unless you specify client criteria. See Defining Criteria for Manifests and Profiles.

For additional options when creating profiles, see the installadm(8) man page.

To remove the association between a profile and a service, simply delete the profile.

$ installadm delete-profile -p sparc-ent -n solaris11_4-sparc