For business: roaming user licensing

from Stardock Forums

In a corporate network with roaming profiles is it possible to give a Fences license to only a subset of users (startin with one for testing) each logging on to various machines? Say we have 5 pcs and 10 users, each user may login to any of the 5 computers having his personal desktop roaming with him. No what happens if we buy only one license for user A? Can he use Fences on all 5 pcs?

fences
7,638 views 5 replies
Reply #1 from Stardock Forums Top

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top


In a corporate network with roaming profiles is it possible to give a Fences license to only a subset of users (startin with one for testing) each logging on to various machines? Say we have 5 pcs and 10 users, each user may login to any of the 5 computers having his personal desktop roaming with him. No what happens if we buy only one license for user A? Can he use Fences on all 5 pcs?
End of quote

Fences licenses are per PC, not per user.

I would be interested in how the settings transfer between PCs, however, as I would like to build more support material around that.

Sean Drohan
Stardock Support Manager

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top

@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. 

Reply #4 from Stardock Forums Top

Quoting woppa, reply 3

@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. 
End of woppa's quote

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:

 

Here:

https://store.stardock.com/corporatepricing

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.

Sean Drohan
Stardock Support Manager