Migrating user to LSF9

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

Migrating user to LSF9; Issues with Lawson Migration Tool
Topic Started: Jul 1 2009, 01:17 PM (170 Views)
bgodwin	Jul 1 2009, 01:17 PM Post #1
Advanced Member Posts: 52 Group: Members Member #796 Joined: November 9, 2006	We are in implementation for lsf9 from 8.0.3.7 (windows enviro). Our vendor experienced a problem when the lawson tool would not allow the backslash in the user id field. Our rd30 record for EMSS users will often show the domain backslash network user id (UFP\bgodwin - EMSS security) versus bgodwin for my UMC domain user account for lawson business use security. When the domain and backslash are removed, the user id is no longer unique. The tool arbitrarily changed some to be unique and kicked out some to an error log. We had various issues and are trying this migration again. This time, we plan to alter the xml file to change the ID's ourselves and insure uniqueness before it gets uploaded to lsf. Should we expect issues merely because user id's ARE changing or can these migration tools cope with this? I'm assuming that the tool will make note of which ID's changed and make sure that all other pieces parts get changed (i.e. process flow tasks that were mapped to that id would get switched to their new id). We only have to change 67 uses and in each case I'm going to change the id on the user that is NOT attached to their laua business user account. I'll pick on the record that is used for EMSS..since they are all tied to one LAUA user for security...hoping that this will make life easier... Any suggesitons or cautions - we will attempt this next week.



atsekhan	Jul 10 2009, 10:29 AM Post #2
Newbie Posts: 5 Group: Members Member #14,885 Joined: June 23, 2009	The migration tool will not "remmeber" the records you have done before. In fact, it does not "synchronize" users, but rather add/modify all of the ones that are listed in 803. More importantly, it does not delete the ones that exist in 9.0, but no longer are in 803. Going back to your question - I usually suggest fixing 803 to the point that conversion works as needed. For that you may create a copy of LOGAN803 and automate modification of that via scripts before running 80->90 environment migration. I also suggest making copies of GEN/LOGAN/LDAP before doing environment migration and restore all of those before next migration, so you will not deal with issues related to updates and deletions. I also do quite a few custom migration processes as in many cases it is not feasible just to use Lawson migration scripts. In fact, it proved in some cases to be useful to do user migration specifically by running a script (written by us) that generates XML file for LOADUSERS instead of using lawson routines for that. We modify our script depending on custom reauirements in a particular installation (such as domain references in your case).


« Previous Topic · UPGRADE: 8.1 Tech / LSF 9.0 · Next Topic »