Hi,
At my organization, to date individual developers and development teams have been managing their software license needs independently (depending on their personal preferences and needs). We've just done an audit across teams of third party software usage and appear to have 7 company seat licenses and 3 named user licenses for NCrunch - all purchased by different people at different times - in use across the firm.
Unsurprisingly, we have a few more developers interested in obtaining licenses for NCrunch and we're wondering if our best course of action would be to:
a) simply get those developers to purchase a couple more company seat licenses, or
b) whether we could consolidate the existing NCrunch licenses into a single license agreement, upgrade the 3 named user licenses to company seat licenses, and consolidate the management of the licenses (so that they all have the same 'valid from' date - at present, since they were purchased at different times some of them are outside of the 1 year upgrade period, and some are not)
Is option (b) an option? If so, how would we proceed in consolidating the existing licenses?
Cheers
Paul
Remco NCrunch Developer
#7236
21 Apr 2015 22:11 UTC
Hi Paul,
Unfortunately NCrunch licenses are always issued and managed as individual codes, which makes consolidating them problematic. As the named user licenses are a different license class with a different owner, it isn't possible to directly convert them to company seat licenses.
The most economical solution in your situation would be to continue to let the named users work with their own licenses until these reach the end of their maintenance period, then purchase new company seat licenses to replace them.
As the licenses still continue to work beyond the end of their maintenance period (though locked to a range of versions), it is possible to simply delay upgrading some of the licenses so that their issue dates can be aligned. Although this may mean going without the latest version, some organisations choose to do this if they have very regimented purchasing procedures.
A license server is also currently under development which I hope should help with managing licenses in future.
Cheers,
Remco
Unfortunately NCrunch licenses are always issued and managed as individual codes, which makes consolidating them problematic. As the named user licenses are a different license class with a different owner, it isn't possible to directly convert them to company seat licenses.
The most economical solution in your situation would be to continue to let the named users work with their own licenses until these reach the end of their maintenance period, then purchase new company seat licenses to replace them.
As the licenses still continue to work beyond the end of their maintenance period (though locked to a range of versions), it is possible to simply delay upgrading some of the licenses so that their issue dates can be aligned. Although this may mean going without the latest version, some organisations choose to do this if they have very regimented purchasing procedures.
A license server is also currently under development which I hope should help with managing licenses in future.
Cheers,
Remco
Post a reply
Log in to reply.