The Church of Jesus Christ of Latter-day Saints

The odd thing is, at one time I had stuff under Leader and Clerk Resources, but no more. This is odd because technology training is one of the responsibilities of the STS, but since I can't see what anyone else has on their page, I'm flying blind unless I'm sitting next to them.

So, i just took a new computer to one of our buildings to install it. I had done the windows updates and such offsite at my home, set up sophos, mls, and miscellaneous software manually. As soon as it was connected on the network at the church building, the post install scripts kicked in. So, it app...

That maybe new, as all the computers I prepared were supplied incorrectly imaged. This was about 2 years ago now. So dependant on which computer manufacturer, ours are Dell, there well maybe differences now, on how they are scripted. OK, all these were Lenovo's. They might have been left over from ...

I have a similar arrangement with my FMG manager, whereby the computers are delivered to me, then I do the set ups. As long as you have the relevant unit information, that shouldn't make any difference to the scripts Hmm, odd. I received a shipment of computers in August of last year, and none of t...

Yep, that used to be the case. I'm currently going through the process of setting up 8 new Lenovo PC's for our stake and I can verify the church's initialization script asks early on for the unit number. When it finishes, a new user is created called "Unit xxxxxx", where the xxxxxx is the...

Also, I tend to put clerks computers and network printers in the static IP address range. That way, if the dynamic addresses get exhausted, clerks can still get their work done.

The solution in this message worked for me. https://tech.lds.org/forum/viewtopic.ph ... 60#p157230

I don't know if this was resolved, but the length of the network cable can have an effect on the WAP's ability to set up. I usually connect my WAP's to the router with a shorter cable for the first time, then once it's configured by the router, move it out to the installation location.

Craig, I don't know if you ever got this resolved. We had a similar issue with Century link. Our issue was with logging in. We could navigate to lds.org, because it was being served via Akamai, but the login servers were unroutable. Our resolution was to have century link move the meetinghouse to a ...

We had 2 computers fail the windows 10 upgrade and when they rebooted they could not access anything on the internet. Ping of internet addresses worked but ping by name failed to resolve DNS address. We fixed the issue by running the commands found at http://www.velocitymicro.com/SupportArticles/Ar...