Patching Strategy

We just went live last week with Landmark -Full TM, TA, ER, Performance suite and LSF - Payroll Benefits GL and Asset Management

Now I am trying to figure out how to stay up on patches/cu's when released and I'm struggling with the notifications to know when/what is being released.

Anyone who has been doing this a while have any insight they would like to share?

We are an AMS customer for our first year and they will be applying for us, but I need to monitor and identify when we want to take patches/cu's

Any input would be greatly appreciated.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

I did come up with a quarterly patching strategy along with calendar view and documented process for downloading release notes, etc... if anyone is interested, I'd be happy to email them to you.

moellerg

I'm interested in your offer to share! moellerg@genesishealth.com

todd-brown

We have been on Lawson since 2001. This ought to be a good discussion.

unknown

Always good to share a strategy that is working for you. Since we've gone to MSP 12 (S3) and TM 11, we have been applying patches at a high rate that is not comfortable to us.

todd-brown

We don't apply patches unless we encounter an issue with something. It is almost impossible to stay current on individual patches. Plus these patches sometimes break as much as they fix. So you have to be real careful. We usually try and stay relatively current with ESP/MSP's

d-hofmann

We are on S3 9.0.1.13 & Landmark 10.1.0.1 currently.

We apply ESP & MSP to S3 once a year, staying with in 2 releases to stay in support compliance.

CTP's are applied only for items that are broken.

Landmark Environment updates once a year (to the latest) and Critial updates when items are broken.

CTP's and Critical Update are generally only when recommended by Lawson Support.

We require full testing and signoff to move updates and patches to production.

Our maintenance window for Production is bi-weekly.

We have learned the hard way how vital testing and signoff is because not all patches are compatible with everything.

Most Critical Updates, have CTP dependencies that must be met.

Recently we have moved from Quarterly Operating system patches to Monthly Operating system patches. But we also put them in Test first, before moving them to production.

unknown

We are on S3 10.0.6 APPS 10.0.6, MSCM10.0.1.6.7, RQC 10.00.00.06.17 and & Landmark 10.1.1.29 currently as of 4/15/16 already INFOR has env 10.0.9 out and we do not have all the bugs worked out from 9 to 10. CTP's are applied only for items that are broken and there have been many for version 10

Landmark Environment is new to us probably will try yearly

CTP's and Critical Update are generally only when recommended by Lawson Support.

We require full testing and signoff to move updates and patches to production.

Our maintenance window for Production is weekly as needed Monday - Wednesday we try never on Thurs or Friday.

We have learned the hard way how vital testing and signoff is because not all patches are compatible with everything.

With V10 now you have all the DSP.jars that may need updated to along with environment or landmark. We are also on Smartofffice and seems like that always needs to be updated. My end users hate Mingle just an extra step that is not needed for healthcare end users, that is also now in picture with ver10. Now I have to really go to the Compatibilty matrix which is a nightmare to read. But we are going to try to upgrade yearly env . Hopes this helps some.

unknown

Annette, I'd be very interested in seeing what you've come up with: mburgett@adena.org

Copyright © 2025 Infor. All rights reserved.