I finally got around to installing the non-beta release of V7 that requires a license key for V7. I ordered that quite a while ago so I already had it. When adding the V7 license to my account it then wanted the V6 license key as this was an upgrade. But, I’ve been using V6 for years and the system already had a V6 license for me. Luckily I could look it up in my email but I found it a bit weird that it wanted the license key for a product already registered to me on that exact account. It’s not a huge deal but I wondered if it was just a random glitch or if there is some reason it couldn’t just find my info and trust me that I have a valid upgrade path. 
Yes, the V7 upgrade license addition asks for the V6 license key as a qualifier, no matter which method the license is added.
I don’t know if that is just a double check, or if there is a technical reason we need you to enter it.
For people that have multiple licenses then we certainly need to know which specific license you want used for the upgrade.
For the special case of a single user license in a Cloud Zoo Personal list, then that is the only obvious case. There might be exceptions for that too.
It’s certainly not intended to be punitive.
This is something I thought about a while back which would certainly make things go smoother. There are quite a few edge cases in order to make this work well for the vast majority of users. Special modifications would also need to be made to our validation infrastructure by @Brian.
That all makes sense. I suppose I was just thinking from the perspective of me, someone with a single license of Rhino. In that case if you have only one license and it’s already in the system then it seems most efficient to automatically bring up that one license and recognize that it’s a valid upgrade path. But, I can understand that not everyone has such a simple account and it’d take time to add something like that to the system. Perhaps time is better spent on other things. It’s only a minor inconvenience and only when a person upgrades. That only happens every 2-3 years so really it’s not much of an issue. Carry on, happy holidays!
Haha.
I like this idea a lot. The cynic in me assumes someone will report it as a bug once it’s implemented. But here’s the YouTrack issue with your request: https://mcneel.myjetbrains.com/youtrack/issue/WWW-1271
1 Like