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