• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Prevent Command Line Access

 2 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
andrew
New Member Send Private Message
Posts: 0
New Member
6/6/2012 12:33 PM
windows 2003, sql 2005, still LAUA,

We are trying to prevent users from accessing the command line. We found a small "hole" in our setup.

When we setup a new user, use their AD login information and login to LID (interface desktop)  -they go to a command prompt.

1. Once they do that lawson creates the print folder under LAUNT and we place a profile.bat file that automatically redirects them to a default token (which is fine).

The issue is the initial Login for the user - they still see the command line.

Now the chances that
1. Users still have LID on desktop is remote
2. users knows server name and port number is remote

BUT: for audit, there still is a remote chance that they can get to the command line.

The only way around this, is for the Lawson Admin to login as the user first (so the LAUNT is created) and the add the Profile.bat file

Does anyone have a different solution, so we can assure our audit team that no user (except admins) can get to a command line ?

apprecaite any assistance

Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
6/6/2012 1:28 PM
Usually in the cases I've seen, I.T. removes LID from user(s) desktop and prevents installation of LID on the user(s) desktop with corporate I.T. policy by putting them in an group which disallows/preventing launching or installation of LID; also preventing telnet-ing into Lawson environment. Also I.T. could use a port number for LID that is unknown to the user.
andrew
New Member Send Private Message
Posts: 0
New Member
6/6/2012 3:37 PM
Thank you for your reply.
Yes have done a majority of those things - Did not think about GP rule. WIll look inot that option.

Appreciate it.