1 reply
Last time I had a problem like this we resolved it by changing the security rights settings for the application itself.
Dont currently have a Win2K PC on hand so cant give specifics on how to get to it but I think it is just a case of logging on as an administrator, then locating the executable file for the program (via my computer etc), right hand click to bring up the menu and look at the properties settings for the file, one should have security settings and you just change the setting toallow it to be run by any user in local mode (or what other level you want it to).
This is not a general policy setting but one for that specific file. The windows equivalent of the Unix/Linux CHMOD settings.
This discussion is closed to new replies.
Trending Security posts
Sort by Trending