Implementation TurboFloat Server questions

Hi all,

we are checking of the use of the TFServer for some of our clients.

1)In the documentation you mention that it is better to create a TFS on your infrastructure, but is this available already?"For most customers, we would say no, don't run the TurboFloat Server on your own computers. A majority of customers should create a TurboFloat Server instance on our infrastructure"

2)When we are using Named-user licensing for some product keys, is there a method that the client's IT department can enter the usernames or import them (sometimes many hundreds). But also for changes it is better to be done by the IT department of our client (new employees or employees leaving the company).

3)When we are using per seat licensing, is there a way to find out how many users are logged in (kind of statistics), but also a kind of log to see the average usage?

4)What is the best way to cope with clients with a (non-persistent) VDI environment (for both TurboActivate as TurboFloat)?

5)For the future; we are planning to have about 5 applications, some of the companies will have a mix of apps for a mix of users. So eg user1 is using app1/app2 and user2 is using app1/app4 etc.I understand that we should define various products for this, but is there an easier solution e.g. to prevent the client has to maintain 5 different TF servers etc.

6) I assume we can use both TA and TFS in our application. First check if there is TFS, if not then ask for email/key for activation via TA?

>> "In the documentation you mention that it is better to create a TFS on your infrastructure, but is this available already?"

Soon. No hard date.

>> "When we are using Named-user licensing for some product keys, is there a method that the client's IT department can enter the usernames or import them (sometimes many hundreds). "

No. You would need to implement that using our web API. Or, take the names when they purchase the license.

Or just not limit it to specific usernames.

>> "When we are using per seat licensing, is there a way to find out how many users are logged in (kind of statistics), but also a kind of log to see the average usage?"

The customers will be able to see broad numbers. You will not be able to see anything.

With the hosted version of TFS the user will be able to see real time information.

>> "What is the best way to cope with clients with a (non-persistent) VDI environment (for both TurboActivate as TurboFloat)?"

Always use TurboFloat on VMs / containers / hypervisors / sandboxes and every other word/rebranding that exists for VM.

>> "For the future; we are planning to have about 5 applications, some of the companies will have a mix of apps for a mix of users. So eg user1 is using app1/app2 and user2 is using app1/app4 etc.I understand that we should define various products for this, but is there an easier solution e.g. to prevent the client has to maintain 5 different TF servers etc."

Custom license fields: https://wyday.com/limelm/help/license-features/

>> "6) I assume we can use both TA and TFS in our application. First check if there is TFS, if not then ask for email/key for activation via TA?"

Yep.

Thanks for your quick response;

1) Can you give us an idea, Q1/Q1 or so? Is there already some docs for it?

2) OK, Is this supported in the Hosted version? This because some of the clients will have about 10k staff and about 300-500 will be using our software (its an addin in excel), so that will be a lot of work inputting the names and above all maintaining it because there is a lot of employee turnover. i guess the best way is then to create a special web-page for this.

3) OK

4) OK

5) We already use Custom License fields but those are per productkey right? So for the mix of users versus apps we can't use this, am I correct in this?

6) OK

>> "2) OK, Is this supported in the Hosted version? This because some of the clients will have about 10k staff and about 300-500 will be using our software (its an addin in excel), so that will be a lot of work inputting the names and above all maintaining it because there is a lot ofemployee turnover. i guess the best way is then to create a special web-page for this. "

Or don't do per-seat licensing. They can sill restrict access to the TFS to within their organization.

You're trying to fit a square peg in a round hole. Just use the round peg (regular per-user session or per-instance lease issuance without limiting to specific usernames).

>> "5) We already use Custom License fields but those are per productkey right?"

Correct.

>> "So for the mix of users versus apps we can't use this, am I correct in this?"

I'm not exactly sure what you're trying to do, so I can't really answer that one way or another.

Reply
Discard post