cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Enable Uninstalling/Disabling Windchill Modules

Enable Uninstalling/Disabling Windchill Modules

Status: Archived Submitted by 15-Moonstone on ‎Mar 16, 2016 09:47 AM
4 Comments (4 New)

A company should be able to make the decision to stop using a module within Windchill and remove it from the system, or at least disable it.

Right now there are ways to work around the problems but all aren't very well supported or recommended by PTC. They are given as "This is not guaranteed to work."

Though with persistent licensing it may not be an issue with upgrades it still feels as though you are locked into to never being able to get rid of any modules once they are installed.

I understand many modules are interlaced through several tables, and you don't always want those objects to go away, but there should be a consistent way to prevent future use of the module.

Example:

https://support.ptc.com/appserver/cs/view/solution.jsp?source=subscription&n=CS210470

See more ideas labeled with:
4 Comments
slapha
15-Moonstone
15-Moonstone
‎Mar 16, 2016 09:52 AM
‎Mar 16, 2016 09:52 AM

This first came up to us when we were given a trial license and installed a module on our development system. The trial expired and we went to update Windchill as a whole and there was no way to update without an updated version of that module. PTC support gave us a way to work around it, and since it was development we could refresh the whole system, but it got me to wonder what happens if you stop maintenance on a module? Is this an ever-growing giant of a system that you're stuck paying for year after year.

It gives us great hesitation to acquiring other "nice to have" modules, that we may decide later on isn't worth funding.

TomU
23-Emerald IV
23-Emerald IV
‎Mar 16, 2016 11:18 AM
‎Mar 16, 2016 11:18 AM

We're in this exact same boat.  We used to have one "everything but the kitchen sink" Pro/e license.  When we migrated from Intralink to Windchill, the VAR installed ProjectLink since this "everything" license was entitled to use it.  Since then we've dropped this old (and vey expensive) Pro/e license, but doing so forced us to purchase a stand-alone seat of ProjectLink instead (and pay maintenance on it forever), since there is no way to uninstall this add-on.  I went round and round with tech support during our upgrade from 9.1 to 10.2 and I was only given two options - 1.) buy one license of ProjectLink or 2.) Do a clean install of Windchill and manually reimport everything!!!

STEVEG
21-Topaz I
21-Topaz I
‎Mar 16, 2016 02:07 PM
‎Mar 16, 2016 02:07 PM

That seems pretty ridiculous to have to go through that.

olivierlp
Community Manager
Community Manager
‎Jan 05, 2022 10:39 AM
‎Jan 05, 2022 10:39 AM
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.