Tuesday, June 03, 2008 3:15 AM
I'm looking at SS to lock down a shared machine running a flight simulator program.
I need to maintain desktop and system settings, prevent program changes and installations, while allowing logon and logoff scripts to record usage by username.
I believe using multiple "limited accounts" and SS locked profiles and system restrictions can accomplish this goal.
Any thoughts from experience users would be appreciated. I'm just trying to identify pitfalls in this approach? Thanks
Wednesday, June 04, 2008 3:52 AMModerator
Hi Tom, do you mean you would like to block the usage of the flight simulator program on certain users? If so, can we just simply add the program exe to block list in User Settings?
Sunday, June 08, 2008 2:20 PM
No all users will be using the Simulator program.
My goal is to maintain system settings, prevent installation of programs, and restrict administration rights to one or two users. We also will be using logon, and logoff scripts to record each username, logon and logoff time and date. This allows us to track usage for billing purposes.
The scripts will need to write to a file, so I would like to avoid drive protection (however, I could always partition the drive and write to a different partition).
It just seems SS will handle most of the goals without drive protection and I was looking for a review of this approach from more experienced users, to point out any oversights I might be making...