Stake Technology Standards

I've recently been called as a Stake Technology Specialist and one of my goals is to implement standards for the units so it's easier for the next person called. Please give me feedback on the following.

1. Google Desktop: I recently setup a new computer with Google Desktop preconfigured. Originally I was going to uninstall it but do like its RSS capabilities. I left it installed but changed the RSS feeds to LDS News and LDS Tech News. The option to automatically add a feed was turned off. Is there a procedure or standard related to Google Desktop?

2. Remote Access: I've read the other threads related to remote access but my questions relate to standards. pcAnywhere is a logical choice since Symantec antivirus software is also used. Symantec has a software donations program but not sure how to interpret the requirements. Below is a link that describes the program.

http://www.symantec.com/about/profile/r ... ations.jsp

Do the requirement apply to the local units or LDS church headquarters?

What is the recommended way to setup remote access?

Do Windows user accounts need to be created for those who can remote connect?

Sorry for the long post.

Thanks,
Rick Perryman

I am sure that there will be several answers after mine, but there is a policy on unit computers (can be found here: https://tech.lds.org/wiki/index.php/Let ... es_archive) and I know that the GSD will say absolutely not to any remote access.

CzechRM wrote:I am sure that there will be several answers after mine, but there is a policy on unit computers (can be found here: https://tech.lds.org/wiki/index.php/Let ... es_archive) and I know that the GSD will say absolutely not to any remote access.

I might be mistaken, but I believe I have seen mention that remote access is allowed for diagnostic purposes (Stake Tech. Spec. to fix something on a ward computer) but not for anything else.

rlperryman wrote:Google Desktop: I recently setup a new computer with Google Desktop preconfigured. Originally I was going to uninstall it but do like its RSS capabilities. I left it installed but changed the RSS feeds to LDS News and LDS Tech News. The option to automatically add a feed was turned off. Is there a procedure or standard related to Google Desktop?

None that I'm aware of. I thought there was a requirement that all software must be approved by the stake, but I can't find that language at the moment. I would certainly ask questions to insure that it's being used in accordance with church callings and not just personal interest.

Regarding Remote Access. The only thing official I've seen is found in .pdf]Policy and Guidelines for Computers Used by Clerks for Church Record Keeping where it talks about "for diagnostic purposes".

rlperryman wrote:1. Google Desktop: I recently setup a new computer with Google Desktop preconfigured. Originally I was going to uninstall it but do like its RSS capabilities. I left it installed but changed the RSS feeds to LDS News and LDS Tech News. The option to automatically add a feed was turned off. Is there a procedure or standard related to Google Desktop?

There are no standards specific to Google Desktop. Broadband connections for administrative computers are fairly new, so it hasn't been an issue until recently.

So Google Desktop would simply fall under the normal rules for any software installed on an administrative computer for security and licensing.

rlperryman wrote:2. Remote Access: I've read the other threads related to remote access but my questions relate to standards. pcAnywhere is a logical choice since Symantec antivirus software is also used. Symantec has a software donations program but not sure how to interpret the requirements. Below is a link that describes the program.

http://www.symantec.com/about/profile/r ... ations.jsp

Do the requirement apply to the local units or LDS church headquarters?

What is the recommended way to setup remote access?

Regarding the Symantec donations program, I can't imagine that any Church unit would qualify, since the second requirement is that any applicant "have a non-religious primary purpose." So you would have to use local stake budget funds to purchase this, if your stake president approves.

I've never set up remote access, and I've never seen any standards. Perhaps someone else has experience they can share.

rlperryman wrote:Do Windows user accounts need to be created for those who can remote connect?

As others have indicated, remote access is for diagnostic purposes. I'm not sure what you're intending to use the remote access for, but it seems like you would be the only one doing remote diagnostic work, and you should already have set up a separate account (the instructions on mls.lds.org for maintaining MLS computers tell the Stake Technology Specialist to create a Windows account for himself).

rlperryman wrote:Sorry for the long post.

No need to apologize -- feel free to ask any questions that will help you in your calling.

Welcome to LDSTech!

rmrichesjr wrote:I might be mistaken, but I believe I have seen mention that remote access is allowed for diagnostic purposes (Stake Tech. Spec. to fix something on a ward computer) but not for anything else.

I stand corrected. It must have been the GSD does not "support" the software if installed.

Something I forgot to ask is does this involve the Admin computer or the FHC computers? They fall under very different rules and policies. So far, everyone has addressed Administrative computers.

RussellHltn wrote:Something I forgot to ask is does this involve the Admin computer or the FHC computers? They fall under very different rules and policies. So far, everyone has addressed Administrative computers.

That's because the initial post asked about "standards for the units," which seems to point to unit Administrative computers.