Peter, Awhile since I played with this but seem to remember, max installs is only enforced for parent/Child relations on CI.
So software item is made a parent, and each deployment is a child up to the max installs. Was a bit tedious to manage, but maybe easier with some later enhancements by HP and some stuff seen in this forum of late.
"An example of when you may not set a Ci to unique is where you have 500 mice of the same model, you would like to keep a track of these, but it would create to much administrative overhead to record the serial number etc.. of each mouse (in which case you would have 500 unique mouse Ci's of the same model). So to make this easier you would create one Ci, set it to not unique, and set max installations to 500 This way you can relate this ci to 500 pc's once you attempt to relate it to pc 501 you will get a message saying no more relations can be made until max installations increased. This can also be used for license management."
My problem is I want this to happen and its not.
Under what circumstances should I get the message refered to above?
I seem to remember there is some history to this along the way. I think it was 1 out with the count at some SPs along the way, ie you needed to have one more than allowed before it worked, and may even only work when to add the child to anothor parent. I think the parent needs to be a unique CI as well.