I think I've read all the doc's my brain can digest, but still can't find the answer to this question:
Network license pool has 2 PDSS and 2 PDSU licenses.
The question is, should Dynamic licensing recognise that User C or User D could have their allocated PDSU license swapped for a PDSS license, thus releasing PDSU license for User A?
This appears to be an issue we are seeing just now, such that PDSP/PDSU licenses are in use (by say AutoCAD users) and preventing access to those who need to use Inventor Cable & Harness.
if user C&D already have a PrDSU license already the only way for them to grab a lower suite license is to close out of inventor
the dynamic & cascading licensing only goes up and does not go back down until you close out of the program
Darren is exactly right, as usual. This is true for any product. Licenses will always cascade up, but cannot move down once a lower license becomes available, or a higher end feature is no longer being used.
This would be a nice wish-list item... but yeah, as Darren said, you gotta close out and relaunch to free one up.
You might be able to use an adskflex.opt options file to restrict what users are allowed different suites, so that you can better gauge what you want. Otherwise, close and relaunch is the way.
Great answers. Thanks Darren / Travis.
Can I now ask a supplementary question?!
Assume the site only has PDSS and PDSU network licenses. We've already established there is no mechanism to pass-back a higher-value license when a suitable, lower-value license becomes available.
Can you think of a mechanism or protocol to deal with a situation where someone with a need to run Cable & Harness in Inventor is prevented from doing so until someone using basic AutoCAD gives up the PDSU license they inadvertantly collected because it was the only one available at the time?
(Is there a mechanism in Inventor to determine which license you have got?)
I was thinking about an options file, but it restricts access by feature code (amongst other things). As far as I know, all the products in say PDSP are covered by the same feature code - therefore I can't restrict a user to access "just" AutoCAD - he gets restricted to PDSP or PDSU - not the individual components of each suite.
Assuming I'm right (I hope you'll tell me I'm not!) it seems as though efficient license utilisation is not really practical in a multi-dicipline environment.
Darren makes a good point. If you have users that never need to use the more expensive license, you might be able to use the option to reserve those seats for specific engineers. That would ensure that they grab the license first instead of the lower suite, leaving the lower suite to the other users. Might be doable...
Thanks for your help so far.
Unfortunately, all users need access to all products.
If I could break down the usage into distinct groups I might have a chance of making an options file work. However, I think the real problem is that the applications don't automatically revert to the lower-license levels.
In an ideal world, we'd just have 4xPDSU licenses, but there's a huge cost differential. I guess we just have to find a way to work with it. Any suggestions are welcome.
:-) If only that was the answer. I know Inventor Professional is included with PDSP 2014 - but the site runs 2013, and it's not just 4 seats, it's more like 44 over multiple sites. I'll stick with 4 for this example because it's just as valid.
It's the principle of the licensing that I'm stuck with. How to let all users use all the products they have bought?
It's unlikely they'll all want to run Alias simultaneously (still only in PDSU) but quite likely that half the users will start Inventor in the morning - the other half start AutoCAD thereby getting the more expensive licenses. If some of the early Inventor users now need Alias, they can't! And no user can tell what license type they have aquired when starting their application - so even an email round the office(s) to ask if someone could release a PDSU license is pointless.
Tell me I'm wrong - please! This just looks like a huge black hole in dynamic licensing.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register