Installing Patches - LawsonGuru.com - LawsonGuru.com Forums -

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3288
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1348
Roger French	1311
mark.cook	1244

bgodwin

Veteran Member

Posts: 143

12/19/2006 5:30 PM

We are in implementation stages doing CRP. There are quite a few patches that we've held off on doing until after CRP. I've seen some comments that clients hesitate to install patches unless absolutely necessary - In general do most people install every patch that is out there or do they only install ones affecting issues that they've experienced?

I assumed as a new client that we'd want to keep on top of all fixes and therefore set the game plan to install every patch out there especially since the text of the patch fix is not always clear and something could be broke that we have yet to realize.

Any advise on how these are accomplished would be tremendously appreciated.

Karl Kemp

Basic Member

Posts: 20

12/19/2006 6:23 PM

My experience has been that we only applied patches (CTP's) when we ran into an issue etc.

If we installed every patch that came along, w\e would constantly be doing so and thus would require a single individual to do testing and documenting the changes etc.

Also, our experience has been that we have been Lawson's Q/A team on the majority of the CTP's we've installed, as they generally have fixed one thing but broken something else. Be very aware that this WILL happen, and happen OFTEN.

Ben Coonfield

Veteran Member

Posts: 146

12/20/2006 11:07 AM

I think it would be a good idea to install MSPs as soon as practical after they are relased, but not individual CTPs. We review CTPs as they are released and install those that address issues we are encountering, or those that address year-end, or particularly critical risks relating to functions we are using.

John Henley

Senior Member

Posts: 3348

12/20/2006 11:51 PM

Beverly, I would agree with Karl and Ben. You should only install CTPs that are really required (and make sure you test all affected programs!) You will eventually pick up the benefits of the other CTPs as they get rolled into MSPs.

Mark Petereit

Advanced Member

Posts: 21

7/1/2008 1:12 PM

Users in each of our functional areas take the responsibility for monitoring patch releases that effect their part of the system. I review the list of "Documents added or updated" in Lawson's knowledge base regularly (daily if possible) to see if there are any issues addressed that we are experiencing. I also query the CTP database at least once a week and review all patches released since the last time I checked.

If I find something that fixes an issue we're experiencing, I forward the CTP to my IS liason who logs the CTP and requests that it be added to the upcoming patch application schedule in our dev system. IS tests in dev, then schedules CTP for application in our test system.

Once appied in our Test system, the users are responsible for testing. IS also notifies user representatives from other departments if a patch could effect their area as well so they can perform their own testing. When all affected users have signed off, the patch is scheduled for application in our production system.

User representatives from each functional area meet with IS biweekly to discuss patches and other development. Patches are routinely moved up and down in priority and rescheduled as needed.

Mark Petereit
HRIS Analyst
McLeod Health
Florence, South Carolina

Walter

Advanced Member

Posts: 22

7/2/2008 12:27 PM

We're an iSeries installation and I would love to be able to pick and choose the patches to be installed. However, we were told that on a iSeries, you need to install all application patches AND in the order they were issued. (we're at 8.1.0.2 and apparently it's no different und LSF9) It's a huge pain, but having said that, we maintain a tight schedule for patch installation ... once a month. This probably causes more testing by the users than they'd like, but if we run into a situation where we absolutely need a patch, we don't have a huge backlog to deal with.

We also came up with some customized programming to automate as much of the install process as possible.

Adam

Basic Member

Posts: 4

7/31/2008 5:40 PM

Before applying CPTs it is good to get a patch preview. This will show you all the forms that are affected by that patch. This would help you with your testing of the patches.