Logos Install on Azure Joined Devices

Hello,

I work at a Bible school and we'd like to see about having Logos installed automatically on all school-owned devices. I would think we could install the base program through an Azure deployment and then have instructors or students log in with their accounts to finalize the install. Sadly, I don't see an option to do that via Logos documentation.

The problem we are hitting is that every end-users needs an Admin to come and help them install Logos. It's becoming an administrative nightmare. Let me know if you've had any luck or workaround for this.

Thanks,
Kyle

Find more posts tagged with

Desktop App

Comments

JT (alabama24)

Welcome! [:)] Sorry you are having troubles. [:s]

The problem we are hitting is that every end-users needs an Admin to come and help them install Logos. It's becoming an administrative nightmare. Let me know if you've had any luck or workaround for this.

Your best bet is to contact Logos directly. However, my guess is that this would be an unsupported installation method. Logos is designed for "one user," and is not meant to be able to be managed by a network administrator.

Keep Smiling 4 Jesus :)

I would think we could install the base program through an Azure deployment and then have instructors or students log in with their accounts to finalize the install.

Welcome [:D]

A thought for Azure deployment is .NET Framework, which is used by Logos (& Verbum). Classic Paint .Net from https://www.getpaint.net is free, which uses .NET Framework (can verify .NET Framework installation plus is useful for digital photo editing, which can include screen shots of Logos & Verbum). User first time login script could cause current stable install web page to open in a web browser => https://www.logos.com/install (for user to download & install application that is designed for "per user" installation)

Another thought is including Logos Web App => https://app.logos.com & Verbum Web App => https://app.verbum.com in browser bookmarks/shortcuts.

Logos & Verbum software tends to have stable release update every six weeks. Logos Wiki has => Logos Release History (user maintained).

The problem we are hitting is that every end-users needs an Admin to come and help them install Logos. It's becoming an administrative nightmare.

Logos Help Center (LHC) includes:

I work at a Bible school and we'd like to see about having Logos installed automatically on all school-owned devices.

Logos Bible Software ("LBS") has a license issue on school-owned devices: As of 15 Mar 2019, Faithlife Corporation Terms of Service includes:

Faithlife Terms of Service">
LBS Licenses may ONLY be used on devices owned by the licensee in whose name the LBS License is registered. Each LBS License is granted for use by one human user only, even where the LBS License is registered in the name of an institution such as a church. We reserve the right to monitor use of the Services subject to LBS Licenses to detect, prevent and disable excessive simultaneous logins on different devices indicating use of the Services by more than one human user. We do not offer site-licenses, shared licenses, co-op licenses, or library licenses.

FYI: suggest changing your Faithlife Profile Display Name => https://faithlife.com/account/edit from email address (unless like more spam email).

Keep Smiling [:)]

Kyle Ziber

https://community.logos.com/discussion/comment/1180131#Comment_1180131

Thanks for your response! I appreciate all of the info. I was worried about the licensing as well, but most of our devices are used by individuals and registered to them, even though owned by the school. We are moving from on-prem managed devices to Azure Managed and were looking for a way to let the non-admin users install Logos without Admin intervention on each install. It doesn't look like the Help Center articles apply for this case. I reached out to Logos directly as well and they said they do not have a basic Seeded install for users to log into their accounts from. I was hoping this was the case, so we could pre-install the bits for our users during the Autopilot Phase.