Domain member installation doesn't allow optional directory

Thomas Fortner
Thomas Fortner Member Posts: 5 ✭✭
edited November 2024 in English Forum

When installing into a local account, the installer allow me to install into any directory I have write access to, such as C:\Logos5. However, when installing to the same computer with a domain account (administrator or domain user) the option to install to an optional directory doesn't exist. Instead, it installs into the profile in AppData\Local\Logos4. This is a huge waste of space because each domain user account gets the same library files downloaded into each profile directory. The same 8GB download chokes Internet access as well.

With a local account the installer permits installation into any directory I have write access to, but only local accounts can use it. Switching back to a domain account prompts new downloads into the profile.

Surely there must be a solution for this bizarre behavior.

Comments

  • JT (alabama24)
    JT (alabama24) MVP Posts: 36,523

    I'm not a windows user, so much of what you wrote went over my head... however... It sounds like you are trying to install Logos onto multiple user accounts on a single computer. Is that right? Logos isn't really designed to do that. Logos is designed for ONE user.

    macOS, iOS & iPadOS |Logs| Install
    Choose Truth Over Tribe | Become a Joyful Outsider!

  • This is a huge waste of space because each domain user account gets the same library files downloaded into each profile directory. The same 8GB download chokes Internet access as well.

    Welcome [:D]

    Is one Logos.com account being shared by many users ?

    Logos wiki => http://wiki.logos.com/Logos_Speaks includes => Logos’ EULA—Single user (Bob Pritchett, CEO)

    When installing into a local account, the installer allow me to install into any directory I have write access to, such as C:\Logos5. However, when installing to the same computer with a domain account (administrator or domain user) the option to install to an optional directory doesn't exist. Instead, it installs into the profile in AppData\Local\Logos4.

    In a domain, application data folder for an account can be redirected.  Also GPO can be used to block or allow execution from %AppData% or %localAppData%, which can be useful in defending from cryptolocker exploit.

    Caution: Logos is designed to be exclusively used by one user.  Anticipate trying to use one Logos installation in more than one account at the same time to be problematic.  

    Keep Smiling [:)]

  • Thomas Fortner
    Thomas Fortner Member Posts: 5 ✭✭

    No this is a virtual machine, and it is not shared by anyone. Domain accounts are subject to corruption via the NTUSER.DAT file. When this happens, login attempts fail and the entire Logos installation is lost. A burp in the domain controller can cause the NTUSER.DAT to become corrupt, or sometimes it becomes corrupt because it gets too big. There are no Microsoft tools for managing or recovering the file, so all you can do is delete the profile, and your Logos installation with it.

    I have the same issue on my Dell notebook. The NTUSER.DAT became corrupt and my domain logon failed. It seems the more files in the profile, the most likely corruption of the NTUSER.DAT becomes. I use a local account on my notebook because the domain account is now a "temporary profile" only.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    Hi Thomas,

    I can see that it would be frustrating if you can't install Logos into the folder of your choice, but I'm confused by some of what you're saying:

    when installing to the same computer with a domain account (administrator or domain user) the option to install to an optional directory doesn't exist

    I'm not able to test this fully, as I already have Logos installed on my domain account, and I'd have to remove it to test installing in an alternative folder. However, I did try and test installation of Verbum.exe (which works in exactly the same was as Logos.exe), and that allowed me to change the folder. I wonder whether you already have Logos installed on your domain account (or perhaps vestiges of it?), and that's why it's not allowing you change the installation location.

    This is a huge waste of space because each domain user account gets the same library files downloaded into each profile directory.

    Logos installations are not designed to be shared by multiple users, and ONLY offers a per-account install option, regardless of where you install it. Installing it in a folder than can be access by multiple accounts is not supported, and could easily lead to problems. I really wouldn't recommend it.

    There are no Microsoft tools for managing or recovering the file, so all you can do is delete the profile, and your Logos installation with it.

    This isn't entirely true. Or at least you can work around it in the very rare occasions when it happens. Even if you can't log in with your domain account, you'll be able to retrieve your files using a local account (possibly needing to change the file permissions). When you create a new profile, you won't need to download those files (or the index) again, by following the instructions here: http://wiki.logos.com/Quick_Installation_onto_multiple_computers 

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Graham Criddle
    Graham Criddle MVP Posts: 33,282

    However, when installing to the same computer with a domain account (administrator or domain user) the option to install to an optional directory doesn't exist

    For clarity - are you saying that when using a domain account the option to run a custom install and change the destination folder - as outlined at http://wiki.logos.com/Install_in_different_folder_or_drive - does not exist?

  • Thomas Fortner
    Thomas Fortner Member Posts: 5 ✭✭

    When as a domain administrator, who is also a local administrator, the LogosSetup.exe doesn't ask for an installation path. I tried it several times, and this was consistent in both the virtual machine and my notebook. By default it installs in the profile folder without asking.

    What started all this was my domain controller had a disk fail and I had to replace the drives, reinstall the OS and reload the apps. When I logged into my domain user account on my notebook, NTUSER.DAT was corrupt. I recovered all my data (and had copies on the domain controller) and deleted the NTUSER.DAT file. The next login returned the "temporary profile" desktop, so I deleted the entire profile and logged in again. It creates a corrupt NTUSER.DAT file every time. So, I created a new account and Logos began reinstalling from the Internet. The 8GB process takes several hours, and the program attempts to push down all 8GB every time I start up Logos because the NTUSER.DAT file get corrupted during the installation. I use a local account as a work around, but need the remote file systems on the domain controller, which a local account doesn't have.

    So, I suppose I could be in violation of the letter of the EULA because I have several accounts with Logos installations, but only one user, as they are all my accounts.

  • JT (alabama24)
    JT (alabama24) MVP Posts: 36,523

    I don't think you are in violation... Logos is designed for ONE user, and you can install it on as many computers as you would like for your own, personal use. It does sound like you are attempting an unsupported method of installation... And your windoweese has gone completely over my head. Are you doing this because of a hard drive failure?

    macOS, iOS & iPadOS |Logs| Install
    Choose Truth Over Tribe | Become a Joyful Outsider!

  • When as a domain administrator, who is also a local administrator, the LogosSetup.exe doesn't ask for an installation path. I tried it several times, and this was consistent in both the virtual machine and my notebook. By default it installs in the profile folder without asking.

    Curious if domain or local administrator account name is administrator ?

    I wonder whether you already have Logos installed on your domain account (or perhaps vestiges of it?), and that's why it's not allowing you change the installation location.

    Does registry key HKCU\Software\Logos4 already exist for domain and local administrator ?

    So, I suppose I could be in violation of the letter of the EULA because I have several accounts with Logos installations, but only one user, as they are all my accounts.

    Thankfully one user can have many Logos installations.  Caution: have learned having Logos library prioritization open in more than one installation and making changes can have sync surprises.

    Currently have 5 Logos 5 / Verbum 5 installations on four computers.  Thankfully can use three installations at once when "checking" in new purchases with Library tagging and rating syncing.  One installation downloads updates automatically.  In the other two, am using scan command to quickly copy resources.

    Keep Smiling [:)]

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    When as a domain administrator, who is also a local administrator, the LogosSetup.exe doesn't ask for an installation path. I tried it several times, and this was consistent in both the virtual machine and my notebook. By default it installs in the profile folder without asking.

    I am a domain administrator on my domain, but I can install Verbum (which is the Catholic version of Logos) in any folder I choose. I think it very likely then that the reason you can't install in your chosen folder is not because you are a domain admin, but because you already have Logos installed on that account (or Logos thinks you do).

    You've clearly got Logos installed, as you say that it keeps downloading your resources. You'll need to remove that installation before you can reinstall in the folder of your choosing. Personally, I'd also try and fix your profile problems before re-installing Logos, as that's obviously not helping.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!