New install of Lawson -- Migrate Current System

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

Ari

Veteran Member

Posts: 49

New Poster

Engaged Reader

Avid Reader

4/13/2012 5:21 PM

We are moving our current version of Lawson that is on a WIndows 2003 server to Windows 2008 R2. This requires a complete new install of Lawson. We are currently on version 9.0.1.9 of the environment with LSF9 security. We have hired a 3rd party Lawson Certified installer to do the install and the initial environment set up. We will also need to move/migrate our current Product Lines and Data to the new environment. The 3rd party installer will also help us with this process. They have told us that they should be able to accomplish this with no disruption to the users except possibly a loss of Jobs or Job information. They have told us that sometimes the Job migration process does not work very well and some users may need to recreate some or all of their Jobs.

My question is, does anyone know if this is in fact an issue with the lawson utilities\processes that Job migration is problematic?

Kwane McNeal

Veteran Member

Posts: 479

4/13/2012 5:38 PM

If you're not upgrading anything, and only reinstalling to obtain the change in bitmode, then you shouldn't lose ANYTHING, and if you do it right, you won't have to even recompile your applications.

I'm not sure who your installer is, but it sounds like they may be doing more work than needed, or you are upgrading something of some sort.

Feel free to call me offline if you have any specific questions on it.

Kwane
505-433-RSGI (-7744)

Greg Moeller

Veteran Member

Posts: 1498

MVP

New Poster

Engaged Reader

Avid Reader

4/13/2012 5:39 PM

I can't speak directly to your question, but as a general rule anytime we upgrade Lawson we always make our users create new job definitions. It has been recommended by GSC whenever you have an issue, to have the user create a new job definition anyway, so we figure that this is as good of a chance as we (as IT staff) can get to force the issue.

Brian Allen

Veteran Member

Posts: 104

New Poster

4/13/2012 5:42 PM

Migrating jobs is generally only an issue when moving jobs between environments that are on different releases. For instance, when moving jobs from 9.0.0 applications to 9.0.1 applications, Lawson screens may change and may have moved or new parameters which can caused job (setup) corruption. Lawson recommends recreating the jobs when moving between versions. Moving jobs between servers on the same release should not be a problem.

SP

Veteran Member

Posts: 122

4/13/2012 8:03 PM

Kwane is correct. Unless you are actually "upgrading" some Lawson
component (i.e going from ESP8 -> ESP9, or MSP5 -> MSP6, etc...) then it
sounds like a waste of time.

On Fri, Apr 13, 2012 at 1:29 PM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> S3 Systems
> Administration Forum Notification A message was posted to a thread you
> are tracking. *New install of Lawson -- Migrate Current System* Posted by:
> *Ari*
> 04/13/2012 12:21 PM We are moving our current version of Lawson that is
> on a WIndows 2003 server to Windows 2008 R2. This requires a complete new
> install of Lawson. We are currently on version 9.0.1.9 of the environment
> with LSF9 security. We have hired a 3rd party Lawson Certified installer to
> do the install and the initial environment set up. We will also need to
> move/migrate our current Product Lines and Data to the new environment. The
> 3rd party installer will also help us with this process. They have told us
> that they should be able to accomplish this with no disruption to the users
> except possibly a loss of Jobs or Job information. They have told us that
> sometimes the Job migration process does not work very well and some users
> may need to recreate some or all of their Jobs.
>
> My question is, does anyone know if this is in fact an issue with the
> lawson utilities\processes that Job migration is problematic?
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...rate-current-system/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

Ari

Veteran Member

Posts: 49

New Poster

Engaged Reader

Avid Reader

4/13/2012 9:10 PM

OK. Thanks for the answers.

We are in fact not upgrading anything, and only reinstalling to obtain the change in bitmode. The environment should be, I believe, the same at 9.0.1.9.

We will be changing from MKS to LUU but I can't imagine that would affect the jobs.

I believe our installer was just warning us there could be a problem, but it sounds like that should not be an issue.