Security Resets and Support Hours

craiggsmith · #1

I just spent a lot of time this morning setting up a new computer only to find that the security token can't be reset until Monday because the regular help desk can't do it, only local unit support which doesn't work weekends. So now I have to decide if I should hook the old one back up and then do it all again next week or just tell them they can't transmit tomorrow.

Why can't the regular help desk do something so simple, or why isn't there a feature in MLS to do it ourselves, or why don't they have some local unit support on weekends? What good is 8-5 during the week? Most of us have day jobs, and most units only use the computer on evenings and weekends. I realize they are open late Tues and Wed, but the reason for that is the reason I can't do my work then; I have to do it when I have long enough window when it isn't used.

I noticed they also cut all support from Saturday evening until Sunday noon. Several weeks ago we were having a Sunday morning meeting with stake leadership to finalize the calendar, and the lds.org calendar went down. There was no one to call and no one was monitoring it. I realize people need to attend church but there are plenty of afternoon options. I'm surprised international units haven't complained.

Sorry for the rant; a little frustrated.

#2

I understand your frustration. However, when I setup new all new PC's in our stake, I followed the procedure that I outlined HERE and didn't need a reset on any of the the security tokens.

#3

If you don't want to, or cannot, follow Mikerowaved's process, or find that a security reset is still needed, there is an alternative. When you know you are going to be swapping computers over the weekend just call LUS and have them do a security reset for the unit in advance. It does not have to be done after the swap, just before the first send/receive on the new computer. The caveat is the next computer to do a send/receive will be the one identified for use with the unit's MLS. This is not normally a problem unless the old computer is used and a send/receive is done before the swap actually occurs. I have done a security reset request on Friday and worked on the swap on Saturday on different occasions with no problem.

craiggsmith · #4

Thanks brethren. Yeah, I was thinking that I should have requested the reset yesterday; I thought I had been able to have them do this on weekends before. The bigger issue is my schedule is often unpredictable and I don't know when I'm going to be able to do things, but it doesn't hurt to have them do it.

But it sounds like if I copy the entire folder over it might work. I will go try that right now. I was wondering about that; this subject keeps coming up and I read through a bunch of posts but it didn't seem like there was a consensus, so I didn't do it. I guess there are no disadvantages?

P.S. I tried to change the subject (and edited my first post a little) but I guess there's no way to change the thread title.

#5

craiggsmith wrote:P.S. I tried to change the subject (and edited my first post a little) but I guess there's no way to change the thread title.

Only moderators/administrators can do that. I changed it to match your post title.

craiggsmith · #6

OK, thanks.

And copying the entire folder seems to have done it according to the clerk. Thanks very much Mikerowaved!

craiggsmith · #7

So has anyone determined which folder is really necessary? Some have said the entire LDS Church folder, some the data folder, and some the units folder. Just curious.

#8

craiggsmith wrote:So has anyone determined which folder is really necessary? Some have said the entire LDS Church folder, some the data folder, and some the units folder. Just curious.

I've always had good success taking it all. Copying from a Windows XP PC, I take the entire "C:\Documents and Settings\All Users\LDS Church" folder, and put it in the "C:\ProgramData\LDS Church" (hidden) folder on the new Windows 7 PC.