Multiple user accounts on clerk computers

[Aczlan]

But that doesn't fix the problem. If someone is logged in to MLS and leaves the computer with MLS running, any other users of the computer who want to use MLS have a real problem until they can find that person. They can't use MLS because that other user has it open. And it's not a good idea to force that user session to close -- the effects on the MLS database are unpredictable.

I can see where that would be a problem. I was assuming that it was like the mission MLS program (at least I think it was called MLS) which was rolled out in 2005 or 2006. That allowed multiple people to use the database at the same time. That made it easier for us because the Historian could enter baptisms, while the Secretary was entering transfers and I was entering reimbursements or other financial stuff.

I stand corrected.

Aaron Z

[russellhltn]

I was assuming that it was like the mission MLS program (at least I think it was called MLS) which was rolled out in 2005 or 2006. That allowed multiple people to use the database at the same time.

If things have changed, they haven't told us. Given the possibility of corrupting data, I don't think we'd want to experiment until we've been told it's supported.

[donaldbrooksby]

If things have changed, they haven't told us. Given the possibility of corrupting data, I don't think we'd want to experiment until we've been told it's supported.

Perhaps not...don't forget, if there were multiple logins...IF...the clerk would have all the passwords for each group login. They can log in to that user and close out their instance of MLS. Also, from task manager, in an admin login, you can also log people out of their user accounts. This forces a safe shutdown of programs in that user unless they had a letter or something open that they haden't saved previously. It is a simple way of "User Management"

[russellhltn]

Also, from task manager, in an admin login, you can also log people out of their user accounts. This forces a safe shutdown of programs in that user unless they had a letter or something open that they haden't saved previously.

I wouldn't consider task manager as a "safe shutdown" method. It depends in part on how the app is coded and if Task Manager will give it the time it needs to safely close the database. Again, I wouldn't do it unless told it was a supported way of doing it. Otherwise, it may come back and corrupt your data at some point.

[donaldbrooksby]

I wouldn't consider task manager as a "safe shutdown" method. It depends in part on how the app is coded and if Task Manager will give it the time it needs to safely close the database. Again, I wouldn't do it unless told it was a supported way of doing it. Otherwise, it may come back and corrupt your data at some point.

Just in case you haven't tried, when you have a User showing up in Task manager, the Logoff function is there to log them off (not kill the process) which waits for normal shutdown of apps that are running then a safe shutdown of that User's login. So it isn't abrupt as you would force a program to shutdown by killing the process from the Applications tab. That is definitely a harsh way of getting a program to shutdown. However any way around this, of course there isn't a policy that would allow for it, so no big deal.

Just like if you were in MLS, not logged out, and started the Shutdown process of the OS/Computer. Hopefully MLS shuts down properly at that point, or it would be devastating to that database too if it didn't properly close those tables... If MLS doesn't see the API call from the OS Shutdown to safely shutdown the running program, that will definitely do it and, policy or not, there is your point to only run this from a single user.

[russellhltn]

Hopefully MLS shuts down properly at that point

The operative word is "Hopefully". A properly coded program would do that. But we're dealing with a program written for a vary narrow audience using limited resources. I'm not slamming the writers, but I get the impression they're doing the best they can just to make sure the core functions operate correctly. I'm not sure as I have enough faith to trust my unit's data that they've coded for graceful "unattended" shutdown, much less tested it.

But if you want to try it, let me know how it goes.

[shawndowler]

My Stake Technology Specialist insisted on setting up individual accounts on our new Windows 7 machine. The directive came from the Stake President who insist on separate accounts for each authorized computer user because the report of blocked websites from the Church firewall apparently will show the name of the user who was logged in at the time and he doesn't want the report to just say "Clerk." I showed them all the policies, but I defer to their authority.

[Mikerowaved]

But there are definite benefits that can come from scaling back the permissions on the Clerk account to not be a full administrator. That seems worthy of some research, even if it's not an officially supported configuration yet.

It's been a few months since you suggested some research probably needs to be done on this. Has anyone done just that who can report their findings here? I'm specifically interested in hearing from those who have tried running MLS under either XP or 7 as a "regular" user for an extended period of time and dealt with things like program updates and such.