remote access

[jviola]

I will be our new stake technology person soon. We have a very large stake as far as boundaries. From North to South is 2.5 hours and East to West is 2 hours. I would like to be able to remote into the computers when I get a call. What is the church's policy for remoting into church computers? Also, what software are you using to take control?

Thanks,

[russellhltn]

I'll refer you to the http://broadcast.lds.org/ics/techtalk/2012-06-01.html, advance to the 27:20 mark. Also 31:15.

[chmsant]

For those that come along later and don't want to view the video... the answer is no remote access. The church does not have licensing agreements with any vendors at the time of this post. An in-house solution is rumored to be in development, but as we know rumors can take a while to come to reality.

[james_francisco]

The argument that there isn't a licensing agreement is a bit of a red herring since there are a number of Open Source VPN clients that could be used. There is however a legitimate issue of the added infrastructure and maintenance that establishing VPNs throughout the church would entail.

[russellhltn]

The argument that there isn't a licensing agreement is a bit of a red herring since there are a number of Open Source VPN clients that could be used. There is however a legitimate issue of the added infrastructure and maintenance that establishing VPNs throughout the church would entail.

I think that's comparing apples and oranges. Yes, there are free remote access methods, but they typically require someone "outside" getting in though the firewall to the controlled machine. A real headache to do while maintaining security. Particularly when there's any number of APs on the internal network.

The most favored method is one where both the controller and the controlled machines reach out though a common port (like 80) and meet on a server. As far as I know, there's no Open Source software for doing that.

[johnshaw]

PVC allows for display sharing, this is how I do it in a very similar stake to yours. Remote access to me means, I can dial up anytime and access the computer remotely. Helping someone with an issue by sharing a display doesn't fall in that category for me.

[marianomarini]

I will be our new stake technology person soon. We have a very large stake as far as boundaries. From North to South is 2.5 hours and East to West is 2 hours. I would like to be able to remote into the computers when I get a call. What is the church's policy for remoting into church computers? Also, what software are you using to take control?

Thanks,

You can do it if someone is in the other side to switch on and off the Pc.
We use Teamviewer (available for Win, Mac and Linux, and mobile too).

[aebrown]

We use Teamviewer (available for Win, Mac and Linux, and mobile too).

I hope you have a license (which is rather pricey) for Teamviewer. It can be used for free only for personal use, which does not apply to the Church.

[Mikerowaved]

I hope you have a license (which is rather pricey) for Teamviewer. It can be used for free only for personal use, which does not apply to the Church.

That may be debatable. Here's a quote from the TeamViewer FAQ:

How exactly is "private use" defined?

As private use we understand any use of TeamViewer for purposes that are neither directly nor indirectly paid. It is not about whether the service itself is paid but whether the service is rendered within the context of the creation of an added value with some kind of financial compensation.

Examples for an indirect payment:

• a software company sells a software product for which it offers free support via TeamViewer
• teamwork among colleagues within a company
• use in associations and non-profit organizations with non-volunteer (i.e. paid) employees
• access to a company computer for work-related activities

In the above mentioned cases TeamViewer is used for creating an added value, the payment takes place indirectly through salaries or a combination of sales/support activities.

I'm not a lawyer, but it appears there might be some wiggle room for volunteers using the free version within a non-profit organization.

[russellhltn]

If you watch the broadcast from June 1, 2012 (http://broadcast.lds.org/ics/techtalk/2012-06-01.html), and advance to 31:15, you'll get an answer. TeamViewer was specifically called out as a do not use because of licensing issues.