We do offer site licenses at our business store here:, this will make it easier for you as you only need one single site license to cover your users, not individually licensed per user. I would like to find out more technical details about how licensing works (I already understand the purchase requirements-1 license per user, per platform) I appreciate any help anyone can provide. I'm also wondering if installing 1Password for Windows on the base image is even an option since those machines get refreshed when the user logs off and the base image is shared between many virtual workstations.
local file in the user folder, HKCU registry hive, HKLM registry hive, etc)? I'm trying to determine if a ThinApp package is feasible in regard to licensing. If we decide to purchase licenses for some of our users, will they be able to enter license information into the ThinApp instance they are running and have it be retained between 1Password/Windows sessions? I guess a better question would be, where is the the licensing information that a user enters saved (ie. I'm currently testing 1Password as a VMware ThinApp package, which captures the installation and lets us deploy it to individual users as necessary. While we use floating pool linked clone desktops (that get refreshed automatically when a user logs off of the machine), users' profiles are saved between Windows sessions, which means their experience is consistent whether they are logging into the "workstation-1" workstation or the "workstation-20" workstation. I would like to find out more technical details about how licensing works (I already understand the purchase requirements-1 license per user, per platform).
0 kommentar(er)
