Re: 4.1.1-LCF-008 (Endpint v41108)

If we state that 41110 fixes the problem, then there should be a defect or
APAR that was fixed to resolve this problem. Each defect and APAR has a
record associated with it that explains the cause of the problem, as
identified by the developer who fixed it, and his remedy. There should also
be a test plan in the record indicating how he tested his fix.

I'd suggest going back to support and asking them to explain their
rationale and they should be able to do this for you.


Gary R. Hamilton
Team Leader
Senior Software Engineer
IBM Software Group - Tivoli Software (UK)
Global Response Team - Europe/Middle East/Africa
+44(0)1753-780-988
mobile: +44(0)780-820-3714
e-mail:hamilgar@xxxxxxxxxx
____________________________________________
AskTivoli -  http://www-3.ibm.com/software/sysmgmt/products/support/
Web PMR submission - http://www-3.ibm.com/software/support/probsub.html


                                                                           
             "Bontrager, Greg"                                             
             <greg.bontrager@e                                             
             ds.com>                                                    To 
             Sent by:                  "'tme10@xxxxxxxxxxxxxxxx'"          
             owner-tme10@lists         <tme10@xxxxxxxxxxxxxxxx>            
             .us.ibm.com                                                cc 
                                                                           
                                                                   Subject 
             31/01/2005 20:47          [tme10] 4.1.1-LCF-008 (Endpint      
                                       v41108)                             
                                                                           
             Please respond to                                             
                   tme10                                                   
                                                                           
                                                                           
                                                                           




Recently, we implemented a 4.1.1 Framework Upgrade up to LCF Patch 008
(v41108).  Afterwards, when the Endpoint restarts (via a reboot or service
restart) on a notebook/desktop detached from the network, customers
witnessed an lcfd.exe exception pop-up error.  The same error was logged in
the Application event log.  This error caused us to back out of the
upgrade.


Tivoli states that patch LCF 0010 fixes this problem, but my customer will
not let me proceed without details on how/what it fixed.  Has anyone seen
this issue?  How did it manifest itself?  It seems to be a non-consistent
problem, so any information that you can share would be helpful.


Greg Bontrager
EDS
248-265-9579