Auto Registration and Flash Archives

Auto Registration, a feature of Oracle Solaris, is new in the Oracle Solaris 10 9/10 release. When you install or upgrade your system, configuration data about your system is, on rebooting, automatically communicated through the existing service tag technology to the Oracle Product Registration System.

If you create a flash archive based on a master system that was installed with a release prior to the Oracle Solaris 10 9/10 release, that archive does not include Auto Registration. Auto Registration has no impact on your work with that archive.

If you create a flash archive based on a master system that was installed with the Oracle Solaris 10 9/10 release or a later release, that archive does include Auto Registration unless it was specifically disabled on the master system.

How Does Auto Registration Affect Flash Archives?

For any archive based on the Oracle Solaris 10 9/10 release or a later release, Auto Registration is enabled by default unless it was specifically disabled on the master system. When you install the flash archive or upgrade a clone system with the differential flash archive, configuration data about that installed or upgraded system is, on rebooting, automatically communicated through the existing service tag technology to the Oracle Product Registration System.

Auto Registration uses support credentials and proxy information that you provide before or during an installation or upgrade. The means of providing that credential and proxy information depends on which installation method is used, as shown in the following table.

Table 1-1 Auto Registration Impact