Automatic Install script

Forum|Forum|16 years ago
February 24, 2010
14 replies
3458 views

We have had a network install of Pro/E for sometime, howeversome users are unhappy with the time it takes for Pro/E to start, andit seems to take a little longer with every release of Wildfire.

Sowe are looking again atlocal client installs, we are not entertaining the idea of taking a DVD to everyone's computer but are looking for other options, so what is everyone doing? Options I can think of include:

- Silent install (i.e as per TPI 103331), if so, how do you manage different scenarios (including whether or not Pro/E is already installed etc)

- network software roll-out tools (e.g. LANDesk) if so how are you using them exactly.

Are there any other methods? Or should we just stick with a network install?

thanks,

Peter

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

General

Show previous replies

P

ptc-4166591

1-Visitor

Running the ptcsetup after cloning can be considered an optionally step if the source installation is what is desired.. The other connections the installer makes (registry entries) are unnecessary, especially if you are coming from a network installation like Peter. A lot of companies use custom start shortcuts/ bat files. You can set path env var there or script it to system. After trying all these methods over the years, this is my current approach. Another benefit is you can remove a lot of junk files from the installation this way.

Shane Brenner

D

davehaigh

13-Aquamarine

Running ptcsetup adds paths to your environment and sets up file types and icons for various ProE file types. Neither of which is absolutely necessary. However if you don't have them users could run into problems with things like the command-line purge.

Added Environment paths:
P:\wf4-m130\proeWildfire 4.0\bin
P:\wf4-m130\proeWildfire 4.0\mech\bin

A Few of the Registry Entries:
My Computer\HKEY_CURRENT_USER\Software\PTC
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\proe.exe
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\asmFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dgmFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\drwFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\frmFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\gphFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\layFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\mfgFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\mrkFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\phaFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\picFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\proeFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\prtFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\psFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\repFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\secFile
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\xasFile

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550

A

ArturPonurski

1-Visitor

trail file method combined with batch file (to remove old version of
Pro/e) that is our plan to go to Wf4 M120

J

JoshuaHouser