@sdRohan We use a combination of roaming profiles with folder redirection. So three folders of the user profile are located on a network share and never travel to the disk of a pc. These are "Desktop" with all the links, data files and folders a given user puts on his desktop, second we have "AppData\roaming" containing all these settings files of many programs and then the personal "Documents" folder.
All the rest of a typical "C:\Users\<username>" folder content (except for the "AppData\Local" folder) is stored on the server but synchronized to a pc's disk the moment the user logs on or off. So notably the user's registry hive with all the settings travels that way back and forth between server and clients.
This way a per user license can travel with the user's settings to any pc the user logs on like e.g. Microsoft 365 does in a shared computer context.
I am familiar with the concept, just not how well Fences will function under it.
That said, the license.sig for Fences is in ProgramData so that should not be affected by user profiles and their location.
Again, it's per PC, not user. I might add that it is important for any deployment that you use the single key \ multi activation corp product:
And for deployment, you use a single generic email, stardock@[yourDomain.com] as a proper-named email address always ends with a support ticket to change them for their transient nature.
Stardock Support Manager