Manual TurboActivate on Terminal Server

Hey Felix,

The difference between TA_USER and TA_SYSTEM is where the activation files are stored (either on a per-user basis or throughout the whole system). It main difference is simply whether your app, or your app's installer, will ever ask for "elevated" or admin permission to make the TA_SYSTEM call. If not, then you can always use the TA_USER.

Is it also possible to activate system wide? So that the activation has to be done just once and its system wide active?

Yes, use TA_SYSTEM in CheckAndSavePKeys().

Oh great thank you. Thats exactly what I needed.

But this leads me to another issue.

For testing reasons I am activating now with one user and the TA_USER constant (to see the actual difference with the TA_SYSTEM constant). And on my Windows 7 system the application is also activated for other users...Thats not intended I think?

I am using TurboActivate 3.2.2.

Between different Tests I call Deactivate() to reset the Initialization of course.

Do you have any Idea what else could go wrong?

For testing reasons I am activating now with one user and the TA_USER constant (to see the actual difference with the TA_SYSTEM constant). And on my Windows 7 system the application is also activated for other users...Thats not intended I think?

That's intended. Once you use TA_SYSTEM, and it succeeds, then TurboActivate will always use system level activations from that point forward.

I am using TurboActivate 3.2.2.

This is unrelated to the version of TurboActivate you're using. However, you might want to update to the latest version. A large number of features and fixes have been implemented since 3.2.2 (the current version, as of me writing this, is 3.4.4)