cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X

Blocking old version use in the license manager

Blocking old version use in the license manager

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
We are an industrial automation company, providing solutions for global manufacturing.
My role is providing IT support for design and engineering tools globally within our company.
My stake holders are the various product design groups that use engineering and design software within our company.


2. What version of Creo Parametric are you currently running?
We are currently on Creo Parametric 7.0.9.0 with some users still on Creo 4 and Creo 7.0.2.0.

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
We would like an option in the FlexLM License manager to block the use of older versions of Creo Parametric from our environment.

When the majority of our stakeholders would like to move to a later version of Creo parametric, we would like to be able to block the use of the older versions so that everyone in the organization is on the same version. Having users on multiple older versions complicates our support model and prevents these users from being able to open the newer versioned files created by users that have upgraded. We have found it difficult to track and remove older versions from all computers within the company and feel that blocking these versions from obtaining a license would be an acceptable solution. Unfortunately, there doesn't seem to be a way to do this within the current FlexLM license manager for Creo Parametric and this is the reason for this enhancement request.

4. What is the use case for your organization?
We as a company are trying to move towards and MBD approach and would like to upgrade to later versions of our engineering tools at a quicker pace to keep up with the industry and be more competitive. This means we must focus on training for our users and continual improvement of our processes. Limiting the licensing of Creo Parametric to only the versions that have been agreed upon by the majority of the stakeholders in the company would greatly help in this process. It has been communicated to me that FlexLM already offers this ability with other software, we would like to see it for Creo Parametric.

5. What business value would your suggestion represent for your organization?
Being able to block older versions of Creo Parametric from our environment would simplify our support model and the number of hours we spend supporting legacy versions of the tool, including customizations for the older versions and the inability for the old versions to open files created in newer versions of Creo Parametric.

5 Comments
BenLoosli
23-Emerald II

I eliminated this issue by using a network install of Creo. Only 1 install and I can delete it or update it at anytime. I also use a windows batch file to launch a menu which gives the users  a choice of which version of Creo they want or need to run.

smnowak
3-Visitor

Hello,
The option of making our standard version of Creo Parametric server based would not work for us unless, we had replicated servers for the application throughout the world to support all of our users. (We actually used to use this option in the past, when most of our users were in the US). We believe that if the application was served from one location it would be too slow, and replicating it to many locations to address the performance issue would add an unacceptable amount of cost. We are aware of PTC creating a SaaS for Creo Parametric next year is an option, but we do have some automation and customization for Creo within some of our design groups that would likely not work with SaaS.
We still believe that controlling which application version(s) are allowed a license would be the most effective way to address the problem.
Best regards

olivierlp
Community Manager
Status changed to: Acknowledged

Thank you @smnowak for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

StephenW
23-Emerald II

The problem with waiting on PTC to solve the problem is it may not happen at all or it may be years before they implement the change. Especially with SaaS coming, it seems to me that PTC will reduce it's attention on license management improvements in favor of more attention on SaaS.

dnordin
15-Moonstone

While FlexLM license feature names can be created that will only allow a specific version to run, this would be a new capability for Creo Parametric to look for that specific license feature name. For example, looking for "PROE_DesignAdv_7.0.8.0" vs "PROE_DesignAdv". This would require not only a change to Creo Parametric but to PTC's licensing system itself to be able to generate licenses per version. This is assuming the feature name is used to control which versions are run. There may be other license controls that could be used.

 

There are other methods of controlling what Creo Parametric versions are run (removing unwanted versions and installing only approved versions):

Use a system like Microsoft SCCM.
Use domain login scripts.
Use a custom startup script for Creo Parametric.