Hi,
one my customer (I developed some macros for them) asked my about "mixed V8i and CONNECT Edition licensing", but I have limited licensing experience and I also did not find such information:
They are SELECT customers and because this company has very restrictive network policy, they have to use checked out xml licensing file. They have no problem with that, they are small team with defined tasks, so different people use different V8i products and once a year a new xml file is checked through web admin interface and checked in at local computers.
The question is what is a right approach when they plan to migrate to CONNECT Edition. For some period they will have to use both versions to ensure everything will be tested properly and the system works fine. When a licence is checked out from SELECTserver, exact product version has to be specified. But what to do when both V8i and CE will be used? Will e.g. MicroStation CE 10.10.00.23 license works also for V8i? Or the license has to be checked twice for the same computer name? Or it cannot be done?
Because this is probably the only one user I know that use the checked out licenses, I have no idea how it works :-(
With regards,
Jan
We are using our own SelectServer (deployed). When I look at the License Management Tool and the License Checkout tab, I only see "MicroStation" listed. We are currently using V8i version for production and the CONNECT version for tool development when V8i is replaced. We are also running V7 for some PDS users. There *is* a separate entry for "MicroStationJ"
Hi Bruce,
Bruce Reeves SRNS said:We are using our own SelectServer (deployed).
this is another situation. They use Bentley hosted server and they check out the licenses for every computer (just a few) every year.
Bruce Reeves SRNS said: I only see "MicroStation" listed
Yes, but when you check out the licenses manually using web admin tool, you have to specify exact product version. And I don't know (and have no way how test it quickly) whether e.g. to define mentioned Updaste 10 version means "only this version" (it will work with CE U10 only) or "this version and any older" (it works with both e.g. CE U10 and V8i SS4).
Regards,
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I just went to the Admin site and tried to check-out a license. Interestingly, I specified an invalid version for MicroStation, and it still let me check-out a license. Another interesting thing was that after the license was checked-out (this time, a with a valid version), the "download" of the license file to my local PC caused our SelectServer to choke, and there was not download...
In a mixed version environment like the one you described, please check out a license for MicroStation two times, one for each version number. This may look like it is using two licenses, but when visiting the Checked Out Licenses page, only one listing will display for the machine with a Details button which shows both versions. If Checkout Restrictions are limiting quantities, you will also find that only one license has been decremented from the quantity available. SELECTserver behaves this way because peak usage for MicroStation is counted by the number of unique machines using the product, not by the number of instances open. This permits multiple instances of MicroStation to be used on the same machine while still counting as one usage. For others reading this post, please note that MicroStation/J also reports usage against a special MicroStationJ license in addition to MicroStation.
Answer Verified By: Jan Šlegr
Hi Jeremy,
thanks a lot for your answer and explanation.
I thought about this approach it maybe the right solution, but for the first sight it looks weird to try to checkout the same product licence twice (so two license files will be created). Will pass this information to the customer.