Title: Important notice to obtain new patches
Date: 2009/02/03
Perform the following 3 steps in the given order.

>
> 1) Apply the latest smpatch certificate patches
> S10: SPARC 121118-15; x86 121119-15
> S9: SPARC 140476-01; x86 140477-01
> S8: SPARC 140475-01
>
> 2) Update Manager: select the collection "Current Available Updates, after 01/2009"
> smpatch users: run "smpatch set patchpro.patchset=current2"
>
> 3)If you are using a Local Patch Server, make sure the patchsigning3 alias is added to the server configuration file. Alter the patchSigningCertAlias property in the file /var/patchsvr/lps/WEB-INF/applicationContext-lps.xml file to
> patchsigning:patchsigning2:patchsigning3
> Then restart the patchsvr with
> patchsvr stop
> patchsvr start
>
> More information about these changes is available at
> http://forums.sun.com/ann.jspa?annID=75

Title: Attention all Sun Connection users
Date: 2009/01/13
The following patches for Sun Update Connection clients are available and are necessary to validate patch downloads.
>
> Solaris 10 (Sparc) 121118-15 Solaris 10 (x86) 121119-15
> Solaris 9 (Sparc) 140476-01 Solaris 9 (x86) 140477-01
> Solaris 8 (Sparc) 140475-01
>
> These patches deliver an updated public certificate into the smpatch keystore which will be required to validate patches signed after the expiry of the current patch signing certificate. Run
>
> smpatch update
>
> After applying the patch, the default patchset name will become current2. The current2 patchset contains all the patches available today, and will also deliver the newly signed patches once they become available.
>
> Sun Update Connection Proxy (Local Patch Server) users:
>
> A patch will be available shortly to make use of the new certificates. If you wish, you may alter the patchSigningCertAlias property in the file /var/patchsvr/lps/WEB-INF/applicationContext-lps.xml to
>
> patchsigning:patchsigning2:patchsigning3
>
> After installing the above patch on your system to make use of this new certificate. A restart of patchsvr will be required to pick up the changes.

Title: Attention all Sun Connection Hosted users
Date: 2008/02/29
Users of Sun Update Manager, smpatch, and Sun Connection Enterprise (UCE) are not affected by this EOL announcement, but should continue to read on to determine if their systems are enabled for hosted management.
>
> Sun Connection Hosted Customers: On March 1, 2008, https://sunconnection.sun.com/ will reach End of Service Life. You will still be able to receive updates via Sun Update Manager, smpatch and UCE. We suggest that you check your systems to ensure the Sun Connection Hosted transport mechanism is disabled.
>
> To see if your system has been enabled for hosted management, check the value of your system by using the following command:
>
> # /usr/lib/cc-ccr/bin/ccr -g cns.service.swupPortalMgmt.status
>
> This command will return a value of "disabled", "enabled", or "". If the value is "disabled" or "", thank you for checking, no further action is required. If "enabled", please take action by performing one of the following steps:
>
> You can disable the transport mechanism from Update Manager to Sun Connection hosted by applying the patch 121081-08 (sparc) or 121082-08 (x86) which will be available on Feb. 29, 2008. If you want more control, you can also disconnect your system from Sun Connection Hosted and shutdown the associated daemons on your system(s) via either one of these two options.
>
> 1) From the Hosted Management Portal
> [Note: This option will not be available once Sun Connection Hosted has been shutdown.]
> a) Go to https://updates.sun.com/ and login to the Hosted management site with your Sun Online Account.
> b) Select the Systems tab
> c) For each system listed, click the Edit System Settings icon (second icon to the right of the system name)
> d) Scroll to the bottom of the Edit Your System Settings page and click the Delete System button
> e) When asked for confirmation click Continue
>
> This option will unregister your systems from the Portal and send a job down to your system telling it to disable the portal management functionality.
>
> 2) Disable Hosted Management functionality from the client
> a) From a terminal window on the target client system, su to root
> b) Execute the following command to shutdown the local Hosted daemons:
>
> # /usr/lib/cc-cfw/framework/lib/cc-client-adm stop
>
> c) Execute the following command to prevent the daemons from being restarted at system boot
>
> # /usr/lib/cc-cfw/framework/lib/cc-client-adm disable
>
> Once complete, either option will disassociate your client system with Sun Connection Hosted.