Copying user profiles.

 4 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Brett
Basic Member Send Private Message
Posts: 19
Basic Member
We are having an issue with a user that has the Microsoft techs stumped and they want us to delete a users AD profile and re-create it using a different name. We are not sure what kind of issue this will cause in Lawson but this particular user has multiple jobs and reports tied to his Lawson profile. Is it possible to copy a Lawson user profile with all settings, attributes, jobs and reports? We are running Lawson 9.0.1. The issue we are having is not with Lawson but a Microsoft Lync/Polycom phone system locking up shortly after the user logs on.
TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
When you delete the profile in Lawson security, it give you the option to copy the jobs/reports to another user. However, this only covers the jobs & reports, so you may still run into issues with requisitions and other transactions like that which were initiated by the user under the current userid.

Is it possible to delete and re-add the uid in AD, using the same id instead of a different one?

Or, perhaps do a dbdump of the user's records which you are concerned with, and then do a dbimport to bring the data back into Lawson to add/associate them with the new uid.
Brett
Basic Member Send Private Message
Posts: 19
Basic Member
I will be discussing that with our network person this morning. He wants to change the user ID to our current naming convention. The user in question has been with the company for over 20 years. I may see if we can try re-creating it with the same ID first. It this fixes the issue then I will recommend to leave it be. However, I am not the decision maker in that case.
Thank you for the suggestions. I am new at this so let me read up on dbdump and dbimport.
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member

I don't think rngdbdump/importdb or dbdump/dbload will work in this case, as it doesn't address filesystem objects and the like.


In any case, there is a much simpler (and safer) way, using ssoconfig, dumping the environment identity for the user.



First you need to determine if actually deleting the user in AD will solve the issue that is outside Lawson. You can *easily* rename an AD account, such that you don't lose the SID. If you actually fully *delete* the user, you will lose the SID info (short of a resync process from another system of record), and that's going to break many other file ownerships, etc.



If you can avoid a full delete, do so.



In either case (full delete or rename), your Lawson-side process is the same.

Do the following:

1) from a command prompt in RDP (this isn't as clean in LID on the Windows platform), do "ssoconfig -c"

2) enter the password

3) select '5' (Manage Lawson Services)

4) select '4' (Generate identity file template for service)

5) Type name of the environment

6) type a name for the file (it is of XML type, so I'd use the ".xml" extention)

7) select '12' (Exit)

8) Edit the file from step #6, adding info for the user. (Use Security Client to obtain)

9) If you do a rename, modify the 'DOMAIN\UserName'. If a delete is done, modify both the SID and 'DOMAIN\UserName'

10) Load the updated file using 'ssoconfig -l PASSWORD filename.xml'

11) Clear listusermap cache (do a listusermap -? for the correct option)

12) Clear IOS cache



.... This should take care of what you need.



If you have any issues, feel free to call me, and we can discuss further.



Kwane

505-433-7744



TBonney
Veteran Member Send Private Message
Posts: 281
Veteran Member
Thank you for the information Kwane!