Tech Forum

I have a ward clerk at one of our buildings saying he can't login to the computer because the clock has the wrong time. If he tries to change the time, he is getting a permissions error. As a Stake Tech Specialist, do I have an account on these machines with the rights to make this change? Do I just need to have the clerk contact Church support?

Sorry, haven't been doing this very long and don't really have a lot of info on what I can and can't do. If I have an account on these machines, I don't know what it is or the password anyways.

Thanks

How far off is the clock? If it's a few days, I don't think that's the issue. If it's off by decades, that's a problem.

I'd go into the BIOS and set the clock there.

If this is a Windows machine, the logins available depend on how it was set up. If this is a Chromebook, I'm not sure if you have an account or not.

I am not sure about the clock issue.

When i provision a machine for our stake i always create a local admin account that the stake technology team knows. When the unit account prompts for a password change and then the password is changed by someone and they forgot what it was changed to you have a way to login and reset the password.

If that fails or you never setup the account then call the global service center and they can help you access the Administrator account based on you telling them the serial number of the computer.

Good luck

bblater wrote: ↑Sun Aug 18, 2024 6:29 pm If he tries to change the time, he is getting a permissions error.

Back in Win 7 days, some people would use the Windows "set time and date" on the taskbar as a handy reference calendar (such as what date next month's fast Sunday would fall on). But it was much too easy to accidently set the computer's date ahead. If not noticed before starting MLS, it would create a serious problem as MLS would have a hissy fit if one attempted to set the date back to what it should be. As a result, many computers were set up to not allow users to set time/date.

But with the death of MLS, that's not really a concern anymore. And I don't think with Win10 it's as easy to make the same mistake.