Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Custom silent install and uninstall procedures

Esteemed Contributor
Esteemed Contributor

You can create a silent installation package through TEM, which is described in the Teamcenter installation documentation.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX12.0 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink

How to Get the Most from Your Signature in the Community

Re: Custom silent install and uninstall procedures

Pioneer
Pioneer

We install and uninstall TC 10 via SCCM. Here's what we ended up doing:

 

- Our installation runs as the local SYSTEM user. This avoids any UAC / admin rights / account elevation issues with Windows 8 and up.

 

- Because we run as local SYSTEM, Java won't run because Java expects to be running in a user context with temp directories, etc. SYSTEM doesn't have those. So Java won't run ... and thus, TEM won't run

 

- So, we don't even use TEM. We manually install any pre-reqs (like the VC++ stuff), then we COPY a pre-made TC 4-tier client from a golden image to the user's computer. Since it's all Java stuff anyway, you don't really have to "install" it ... nothing goes in the registry, there aren't DLL's to register, etc. A copy works just fine. (Now, we have users who need TC, users who need TC with NX integration, and users who need TC with NX and I-DEAS integration. The only way to handle this without using a TEM install is to build a golden TC 4-tier client image for each variation, so yes we have three images. The script determines which variation the user needs and copies the appropriate one.)

 

- Then we install all the other "outside" stuff, like MS office integration, Vis, SWIM, IPEM, etc.

 

- Then we put shortcuts on the user's desktop.

 

 

 

Re: Custom silent install and uninstall procedures

Builder
Builder

Thanks for your creative idea, I'm really interested in your golden images.

Could you answer afew questions:

1. Which software do you use to create those images?

2. Do you handle Ms office client integration with this method?

3. Is it possible to share your install script?

 

 

Re: Custom silent install and uninstall procedures

Valued Contributor
Valued Contributor

We just went through our TC11 upgrade where we had to uninstall and install 8-9 softwares and we had similar thing. Refer to this slide which was present in the plmworld which was very useful. We followed the same for uninstall using the Windows msi approach - this really unistall softwares very very fast and in a clean way. 

 

Refer to one of the existing post in the community where Larry has pointed to the PLMworld presenataion.

 

Hope this helps.

 

 

Highlighted

Re: Custom silent install and uninstall procedures

Pioneer
Pioneer

sma wrote:

Thanks for your creative idea, I'm really interested in your golden images.

Could you answer afew questions:

1. Which software do you use to create those images?

2. Do you handle Ms office client integration with this method?

3. Is it possible to share your install script?

 

 


1.  We use TEM to build the images. We build it on a clean system.

 

2. MS Office integration has it's own installed so we call it separately after we copy the image.

 

3. Attached. As you can see from the edit history, it took us quite a bit of trial and error to get to where we are now. We did pick up some hints from Larry Carpenter's work as someone else mentioned in this thread. Larry and others have contributed a lot to this topic.

 

 

Re: Custom silent install and uninstall procedures

Pioneer
Pioneer

SRaj wrote:

We followed the same for uninstall using the Windows msi approach - this really unistall softwares very very fast and in a clean way. 

 

Refer to one of the existing post in the community where Larry has pointed to the PLMworld presenataion.

 

Hope this helps. 


This approach works in general, but both the SolidWorks Integration Manager and the JT Translator for SolidWorks are quite resistant to this approach, since neither use .msi packages. Getting these to install or uninstall silently takes a bit of work and I'm still fighting it from time to time. In fact, as recently as SWIM 9.X, it just won't uninstall completely. We resorted to ripping it out forcibly with the DEL command and then manually cleaning out the registry. It's really a piece of junk.

Re: Custom silent install and uninstall procedures

Builder
Builder

tdw wrote:

SRaj wrote:

We followed the same for uninstall using the Windows msi approach - this really unistall softwares very very fast and in a clean way. 

 

Refer to one of the existing post in the community where Larry has pointed to the PLMworld presenataion.

 

Hope this helps. 


This approach works in general, but both the SolidWorks Integration Manager and the JT Translator for SolidWorks are quite resistant to this approach, since neither use .msi packages. Getting these to install or uninstall silently takes a bit of work and I'm still fighting it from time to time. In fact, as recently as SWIM 9.X, it just won't uninstall completely. We resorted to ripping it out forcibly with the DEL command and then manually cleaning out the registry. It's really a piece of junk.


Thanks, Your code is well organized and has propper comments.

Do you change the installed files of NX when establishing the TC+NX Integration?

Is there any DLL registration during integration installation?

Re: Custom silent install and uninstall procedures

Pioneer
Pioneer
There is no .DLL registration to worry about for the TC base client install. MS Office integration and Vis probably have a good number of .DLL things to do, but we use the regular installer for those.

We do alter the start_nxmanager.bat script in the portal directory, but that is because of how we manage NX launch settings, etc, not because we install Teamcenter without TEM.

This message and any attachments may be a confidential attorney-client communication or otherwise be privileged and confidential. If you are not the intended recipient, any review, distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please reply by e-mail and delete this message and all attachments.