Sun Update Connection Client 1.0.8 now available

The Sun Update Connection System client, version 1.0.8 is now available as
software update 121118-08 (SPARC) or 121119-08 (x86). Version 1.0.8
is the biggest update we have produced since the initial release of the Sun Update
Connection and includes the following enhancements:
o Sun Update Manager has a brand new user interface which includes a new
look and icons, numerous usability improvements such as better progress
reporting and the ability to print/save installed and available patch lists and
patch README files.
o Support for Solaris Live Upgrade so patches can be added to an inactive
alternate boot environment.
o The Solaris 10 SMF configuration framework is now used to trigger the
installation of patches with special handling requirements (single user mode
or restart-after required) which will improve compatibility and reliability.
o The version 1.0.8 client uses a new Sun-hosted patch server that outsources
content delivery to Akamai. This enables us to provide superior download
performance to our customers worldwide.
For a complete list of the defects corrected in this release please
refer to the patch README file for this patch. Note also that this
update includes fixes that were delivered in prior releases of the
Sun Update Connection client software patch. By installing this update
you may be getting fixes that were previously available but not present
on your system.
Sun Update Connection Hosted application has been refreshed to include
numerous user interface adjustments and fixes that have been suggested by a
customer focus group usability study. Although there are no new features,
the usability of the product is substantially improved.
Thank You,
Sun Update Connection Team

On the SunStudio Patches - I dont believe that this will be fully fixed since part of the problem is the patches themselves. I however do not have access to a SunStudio installed test system at present so I'd be interested to hear feedback from someone who has tried installing these through the SunUC 1.0.8 toolset
Fonts - I believe that greater flexibility will be coming in future releases. Work on the Update Manager gui is still ongoing
Patch server - Yes the SunUC proxy will use the new servers providing it has been upgarded to 1.0.8
Sun4u patch - This is an issue with the patch metadata being incorrect and not the toolset.

Similar Messages

Smpatch vs Sun Update Connection

What does Sun Update Connection offer that I
can't get by just using the 'smpatch' tool on Solaris?
Besides telling Sun all about my machine and its
configuration?
There are no screen shots or lists of specific concrete
features on the web site. It's all very abstract, and I
don't have time to download and install it just to figure out
what it is.
--chris

I shouldn't have said "are no screen shots etc" I should have
said "I can't find any...".
Also, I should have compared Update Connection with
"Sun Update Manager" GUI client. That's what I use
now to download and install patches.
Will the Update Connection client give me something different?
Or are these just two competing products from Sun that
do the same thing?
(By the way maybe this should be a FAQ)
--chris

Welcome to the Sun Update Connection forum.

Welcome to the Sun Update Connection forum. Sun Update Connection services lets you analyze and update your systems and stay up to date from anywhere-while providing easy access to patches and software updates. The Sun Update Connection, System Edition incorporates a number of exciting features. These features* include access to all Solaris 10 software updates (security fixes, device drivers, recommended updates and feature updates) through the following update mechanisms:
� Sun[sm] Update Manager � A client-side application with a graphical user interface (GUI) and command-line interface (CLI) for locally managing updates on your system
� Sun[sm] Update Connection - Sun-hosted Web application for remotely managing updates on one or more of your systems
� Update Connection Proxy - A local caching proxy server which serves updates from Sun to the client systems that are inside your enterprise security domain. (requires use of Sun Update Manager.)
� SunSolve Patch & Updates Portal - A venue for downloading patches and obtaining patch readme's
For more information about these tools, please see the following documentation:
- Sun Update Manager 1.0 Administration Guide
- Sun Update Connection 1.0 Administration Guide
- smpatch(1M) man page
- patchsvr(1M) man page
- Sun Update Connection, System Edition 1.0 Preview
Release: Installation Guide and Release Notes
* Please note that in the future, some features will require a valid Sun Service Plan. Please see the "Get Started" Page for more information.
http://www.sun.com/updateconnection/getstarted
You can also access a Frequently Asked Questions (FAQ) document from the Sun Update Connection services web application by clicking Help or directly at
http://www.sun.com/service/sunupdate/faq.html
And of course, you can post questions here on the Sun Update Connection forum and we will do our best to respond.
Happy updating,
Sun Update Connection Offering Team

.

Sun Update Connection Certificate Update - Install by 23-Feb-2006

Important Notice: Sun Update Connection has updated the certificates we use to secure our communication channels. To ensure continued service, you will need to apply a special software update before February 23, 2006.
The specific patch IDs are:
122231-01 (Solaris SPARC) - http://sunsolve.sun.com/search/document.do?assetkey=1-21-122231-01-1
122232-01 (Solaris x86/x64) - http://sunsolve.sun.com/search/document.do?assetkey=1-21-122232-01-1
After February 23 you can use the following command on your managed systems
to install the appropriate patch to enable management at the Sun Update Connection
application:
smpatch update -i 122231-01 (for SPARC clients)
smpatch update -i 122232-01 (for x86 clients)

Solved it. Solution is to move all of the patches into /var/spool/pkg and run patchadd on each one in there (in the right order).

How Sun Update Connection Proxy really works

Hi,
Apolgies if this question is in the FAQ, but the FAQ link in the header text of this forum gives me a 404.
I've been trawling the docs on Sun Update Connection Proxy and trying to understand how it works with regards caching. The docs are quite detailed in how to set it up, for example how to point to a proxy using http://<proxy-name>:3816 etc., and how to install patchsvr and how to start it.
What seems to be missing from the manuals IMHO (and this all might become blatantly obvious once I've been using it a while) is any details on how the smpatch update process works end-to-end through a proxy, e.g. I know how to change the cache location using the patchsvr command but how and when is anything stored in that location? What are all the files and directories that reside under /var/sadm/spool, and how many of these relate to a proxy (LPS) server?
Is smpatch supposed to clear out the .jar files in there or do I need to set up a job to do that regularly?
Hope someone can point me in the right direction.

Inside /var/sadm/spool there are several directories, I won't describe all of them, but for most purposes this should be enough:
Client:
/var/sadm/spool/cache/Database - stores patchsets (current2, etc)
/var/sadm/spool/cache/xml - stores the MoTD files
/var/sadm/spool/cache/entitlement - stores the entitlement file (note this is generated by the server on each request)
/var/sadm/spool/cache/updatemanager/analysis.results - if you have the swupAuto cron job, this directory is used to hold analysis to speed up UM launch
/var/sadm/spool/cache/ReadMe - holds the patch readme's (mostly for use with UM)
/var/sadm/spool/cache/collection - holds a file containing information about available patchsets
/var/sadm/spool/cache/category - holds a file describing the types of patches (currently Update Tools, Security, Recommended, and Generic)
/var/sadm/spool/sunucLog - holds job_history.log
Proxy:
/var/sadm/spool/patchsvr - this holds all files required for analysis and patches with URL-encoded filenames, the files used to be stored in a more hierarchical directory structure, but this changed a few patch revisions ago.
As for cleaning, in general it is safe to delete all files under /var/sadm/spool/cache/ as all of the patches are stored at /var/sadm/spool/ and most other files should be replaced on a regular basis automatically, however you may want to remove all of the patches too once you have completed your patching sessions - this is not done automatically. On the proxy you might not want to be so thorough - you would normally want to keep the patches (or at least keep the most recent ones - 180 days in this example):
# cd /var/sadm/spool/patchsvr
# ls | grep -v all_signed | xargs rm
# find /var/sadm/spool/patchsvr/ -mtime +180 -exec rm {} \;Does this answer your questions, or do you need further explanation?

Managing patches with Sun Update Connection

I have just started using updatemanager to download and install my patches and found some issues I would like to discuss.
First, the patch that updates the software to version 1.0.3 (121119-03) was not available on updatemanager itself. I found it on the sunsolve site by accident.
Second, from the 20 patches available for me to install, 19 failed. The ones that needed reboot "succeeded" but upon shutdown they failed one by one. Even though the failure reasons were ok, like there is a newer patch revision already installed, I think updatemanager could handle all this dependency and versioning thing automatically, and suppress these patches from the list of available patches or at least show them with different status.
Third, I am not sure how to use Sun Update Connection on a systematic basis for keeping my system up to date. Should I install all patches available or not? I don't want to lose time reading all patch descriptions to find out which patches are necessary or not. Is there a straightforward way?
Am I missing something or is updatemanager really just falling short of my expectations?
-- Douglas

To repeat a comment I made in another thread, I agree with datique on this. UM should have a way to say "ignore this patch, I don't want it and never want to see it again". Of course, it needs to keep track of any dependencies there may be later on down the road. The example I gave in the other thread involved the GigaSwift update being needed on my Blade 100 at home.
This isn't meant as a gripe, but a suggestion. I realize that UM is a new tool, and many things like this need to be (are?) hammered out with community feedback.
Rainer

Sun Update Connection Server Maintenance Notice 2005.12.22

Synopsis: Sun Update Connection Service Maintenance
Start Time: Thur 12 Dec 2005 8:00PM EST (20:00 GMT -5)
End Time: Thur 12 Dec 2005 10:00PM EST (22:00 GMT -5)
NOTICE AND END USER INSTRUCTIONS
The Sun Update Connection will undergo a routine maintenance Thursday, 12/22. Customers connected to the the service during the maintenance may experience a disconnect. and will have to login again.
CONTACTS
If you have additional questions, please send an email to [email protected]

Hi
I am getting following error about every 15 mins since Jan 07, 2006 evening.
Jan 7 21:50:41 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 22:11:40 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 22:31:36 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 22:50:29 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 23:11:24 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 23:31:38 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 23:50:41 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 8 00:11:57 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
I ran /opt/SUNWsrspx/bin/srspxrun -p and got SUCCESSFUL PING. I also ran this /opt/SUNWsrspx/bin/srspxstat and found nothing unusual.
Any suggestion on how to fix it?
Thanks

Sun Update Connection

I have several hundred Solaris 10 boxes (with a current Sun support contract) on an internal (i.e. isolated from the Internet) network. I would like to set up a Sun Update Connection proxy for Solaris patches only. Is it possible to download (and periodically update) the files needed for the proxy server (patches, database, etc.) using a web browser by hand? Moving the proxy server between the Internet and the internal network is not possible.

Thanks. The "Enterprise edition Sun Connection" is the same as "Sun Connection-Customer Satellite", correct? If so, am I also correct that, although the Solaris 10 Update Channel is included with my support contract, the Satellite software needs to be purchased separately?

Sun Update Connection install fails on Patch 119574-02

Just finished installing Solaris 10 (3/05) on my brand new Sun Blade 1500. I then downloaded the latest version of Sun Update Connection, but the installer fails as follows:
# ./installUpdateConnection
Adding patch 119574-02
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
119574-02
Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Patch 119574-02 failed to install due to a failure produced by pkgadd.
See /var/sadm/patch/119574-02/log for details
Patchadd is terminating.The above log file reads as follow:
# cat /var/sadm/patch/119574-02/log
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
/export/home/richard.cross/updateConnection/patches/119574-02/SUNWcsu/install/checkinstall: /export/home/richard.cross/updateConnection/patches/119574-02/SUNWcsu/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
Dryrun complete.
No changes were made to the system.Where have I gone wrong? I haven't done anything to my system between installing Solaris 10 and downloading SUC, so why is it complaining about an existing patch?

Solved it. Solution is to move all of the patches into /var/spool/pkg and run patchadd on each one in there (in the right order).

Need to download Sun Update Connection - Enterprise

Where would I download the Sun Update Connection - Enterprise 1.x .tgz file?

You can download it using this https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SunUCE-OTH-G-F@CDS-CDS_SMI ]
In case you do not already have a license you will need to contact Sales. See http://www.sun.com/service/sunconnection/get.jsp for more information.

Sun Update Connection Service Maintenance - 9th September, 2006

Sun Update Connection Maintenance Outage
Date : 9th September 2006
Start Time: 0700 EST, 1200 BST
End Time : 0730 EST, 1230 BST
Description of maintenance / outage:
The Sun Update Connection will undergo a routine maintenance Saturday 9th September 2006 from 0700 EST to 0730 EST. The Sun Update Connection service will be unavailable during this maintenance.
When the maintenance is complete, a notice will be posted on the Sun Update Connection announcement and FAQ forum at :
http://forum.sun.com/jive/forum.jspa?forumID=335
Thank You,
Sun Update Connection Team

Hi
I am getting following error about every 15 mins since Jan 07, 2006 evening.
Jan 7 21:50:41 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 22:11:40 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 22:31:36 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 22:50:29 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 23:11:24 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 23:31:38 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 7 23:50:41 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
Jan 8 00:11:57 jp-script SRS Proxy[3822]: [ID 728115 daemon.error] File upload failure: exceeded maximum retry count
I ran /opt/SUNWsrspx/bin/srspxrun -p and got SUCCESSFUL PING. I also ran this /opt/SUNWsrspx/bin/srspxstat and found nothing unusual.
Any suggestion on how to fix it?
Thanks

Problems with sun update connection server ?

recently I've been having problems with accessing the update connection web server.
Can't get in with Firefox sometimes - get blank pages, or 401 error pages.
Then today with IE, hitting the help page on the top right, I get:
Sun ONE Application Server - HTTP Status 500 Error
The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
Type: Exception Report
Message: Internal Server Error
Exception
java.lang.RuntimeException: The icon attribute of an Icon component was set to MASTHEAD_MINI_IMAGE. The Theme does not contain an image of that name.
     at com.sun.web.ui.theme.Theme.getIcon(Theme.java:534)
     at com.sun.web.ui.renderer.SucPopupMastheadRenderer.renderEnd(SucPopupMastheadRenderer.java:114)
     at com.sun.web.ui.renderer.AbstractRenderer.encodeEnd(AbstractRenderer.java:235)
     at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:720)
     at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:623)
...

The URL is correct and it works for us no problem. I don't believe anyone else has reported this problem so I guess it must be working for everyone else as well.
Can you detail exactly what error you get, and what browser type/version you are using.
Can you also see if you can access this URL: https://srsnetconnect3.sun.com

Sun VDI 3.0 Patch 3 is now available at SunSolve

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Updated "Selecting the Best Compiler Options" now available

The technical article "Selecting the Best Compiler Options" by Darryl Gove has been updated for Sun Studio 12 Update 1 and is now available at:
http://developers.sun.com/sunstudio/documentation/techart/compiler_flags/
Here's the abstract:
+This article suggests how to get the best performance from an
UltraSPARC or x86/EMT64 (x64) processor running on the latest Solaris
platforms by compiling with the best set of compiler options and the
latest compilers. These are suggestions of things you should try, but
before you release the final version of your program, you should
understand exactly what you have asked the compiler to do.+

Ok sorry I've taken so long to respond. The reply button wouldn't pop up for me to reply!
There was never a dialog box asking for me to select the program from installed programs when I open the pdf from outlook express. But when I opened a pdf from my desktop it asked that question and I had it "always use this program to open this type of file." So I assumed that it was would work when opening from outlook express. But it doesn't.
I've tried unclicking the protected mode button under the preferences general section. And finally I'm not sure how to post screenshots of the attachment thumbnail and dialog. I'm looking all over my keyboard for a button to push I don't have a clue as to what to do! I do have a print Scr button but when I click on it nothing happens. I've tried holding down the shift key and the button and the alt key and print scr button but nothing happens.
Could it be that somehow it's not recognizing ARCO.EXCH.DOCUMENT as that's what it thinks the type of document is?
I've already created an association for pdf files and it'll open them on my desktop, just not in outlook express.

Sun Update Connection Proxy

Hello all!
I have a local Patchserver, configured like this:
patchsrv setup -l
Patch source URL: https://getupdates.sun.com/solaris/
Cache Location: /var/sadm/spool/patchsvr
Web proxy host name: ip-address-of-proxy
Web proxy port number: port-of-proxy
And a Patchmanager refering to it:
smpatch get
patchpro.backout.directory - ""
patchpro.download.directory - /var/sadm/spool
patchpro.install.types - rebootafter:reconfigafter:standard
patchpro.patch.source http://ip-address-of-patchserver:3816/solaris/ https://updateserver.sun.com/solaris/
patchpro.patchset - patchdb
patchpro.proxy.host - ""
patchpro.proxy.passwd **** ****
patchpro.proxy.port - 8080
patchpro.proxy.user - ""
patchpro.sun.passwd **** ****
patchpro.sun.user - ""
smpatch analyze produces the following:
Cannot connect to retrieve detectors: Server returned HTTP response code: 500 for URL: http://ip-address-of-patchserver:3816/solaris/
can anybody help me?
Thanx in advance

The problem is that whilst what Barry Greenberg originally published would have worked at the time (after the reader had gone to the trouble of correcting a few errors), the feature itself was broken shortly afterwards by a newer revision of the patch. As of this time the tools to develop custom baselines have not been and will not be created in the current form of Sun UC software.
The feature to create custom is available in the Sun Connection (formerly Sun UCE, or Aduva) and may be a feature of smpatch/updatemanager in the future, but we are not in a position to be able to tell you as we at this time do not know.
We have actually been campaigning to have this document removed or updated since the beginning of the year, originally due to the errors, but later as a result of major changes that completely broke the previously 'undocumented' feature. The page was meant to have been removed late yesterday in a maintenance push on the BigAdmin site, but as you are aware this has not happened.
Please disregard the document.

Sun Update Connection Client 1.0.8 now available

Similar Messages

Maybe you are looking for