Skip to main content
P
ptc-30063451-Visitor
1-Visitor
November 8, 2012
Question

Creo2 install from network

  • November 8, 2012
  • 2 replies
  • 985 views
We are updating to Creo2 next week and I was wondering if any admins have had luck installing the software from the network rather than storing a copy of the software on each machine?

Thanks,

Take care,

JEREMY HANDLER
Mechanical Engineer
1+760-591-7318
Jeremy.handler@hunterindustries.com

[Description: cid:024EB480-3C46-43E4-9814-8F315F22E2FA]

1940 Diamond Street
San Marcos, CA 92708 USA
Hunterindustries.com
[Description: Grren] Consider the environment. Consider the impacts.


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.

2 replies

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
November 8, 2012
Installing from the network and running it from a network location are two different things. We are running it from a network location. We install it on one computer long enough to copy the program files to a network location and then uninstall it. The only machines that actually have it installed are laptops that need to run it when disconnected from the network. (Technically we could just use offline files to keep the program data available, but there are so few laptops that it's just easier to install it for those.)

Tom U.
A
amedina1-Visitor
1-Visitor
November 8, 2012
This is the PSF I used. I have it locally, but I don't see why having it on
the network would be terrible other than the lag and its a 3gig install. 🙂

Insteady I intall in one machine, then just copy the install folder to the
network and have everyone run a copy script to a specific location on their
machines. This kills about an hour. Then run the psf it it sets all the env
vars and it just runs. Any changes can be automatically distributed. Have
the users start pro/e from a shortcut to a batch file on the network. If
you want to add new vars or change or add files you can just modify that
one batch file that everyone is pointing to. I like how it has worked so
far on WF4 and already tested this on CPW2 (Creo Proe Whatever) actually I
just call it CP2.

You notice how they added spaces to their install folders? Fools? Just
stick to no spaces and let us all move on with our life. Nah they just had
to add spaces so that now you have to escape characters in some scripts but
not in others and quote commands and blah blah. make your life more
difficult just to show that they can change something. Its just an
observation.


// PTC - PSF file: parametric
//
PRODUCT=Creo Parametric
DESC=DESIGNER
SHIPCODE=M020
CREO_COMMON_FILES=Common Files\M020
// License file info
ENV=PTC_D_LICENSE_FILE-=7788@server
ENV=CREOPMA_FEATURE_NAME=PROE_Foundation (158)
//
ENV=PTC_DOCS=help file location
//
ENV=ILINK_CMD_NAME=proilink3.4.bat
ENV=INTRALINK_CMD=%INTRALINK_DIR%\bin\%ILINK_CMD_NAME%
//
ENV=MECH_LP=%PRO_DIRECTORY%\mech
ENV=MECH_HOME=%MECH_LP%\%PRO_MACHINE_TYPE%
PSF=%MECH_LP%\install\nt\mech.psf
ENV=PRO_MECH_COMMAND="%CREOAPP_DIRECTORY%\bin\parametric.exe"
"%CREOAPP_DIRECTORY%\bin\CP2_1.psf"
//
ENV=RPC_TIMEOUT=31536000
ENV=PTCNMSPORT=1239
ENV=NMSD_TIMEOUT=300
ENV=PRO_COMM_MSG_EXE=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\pro_comm_msg.exe
ENV=PROE_START=%CREOAPP_DIRECTORY%\bin\parametric.exe
ENV=CDRS_DATA=%PRO_DIRECTORY%
ENV=PRO_IMAGE_CONVERTER=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\convert_image.exe
ENV=GALAXYHOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%
ENV=PROGUIDE_DIRECTORY=%PRO_DIRECTORY%\uifdoc
ENV=SPG_DIRECTORY=%PRO_DIRECTORY%
ENV=PRO_USRMAIN=%PRO_DIRECTORY%\usrprog\umain\usrmain.c
ENV=PROTABLE_DIRECTORY=%PRO_DIRECTORY%\protable
ENV=PROTAB=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\protab.exe
ENV=ZIP_EXEC=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\zip.exe
ENV=CLHOME=%PRO_DIRECTORY%\text\pcldata
ENV=PVIEW_PROEPVIEW_HOME=%PRO_DIRECTORY%\prodview
ENV=CV_ENV_HOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\CV140
ENV=VC_VCONF_START=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\ptcvconf.exe
ENV=DEBUG_HLP_DLL_PATH=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\lib\dbghelp.dll
RUN="%MECH_LP%\install\nt\pro_mech_env.bat"
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\nms\nmsd.exe" -noservice -timeout
%NMSD_TIMEOUT% &
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\xtop.exe"
ENV=MEDI_HOME=%MECH_HOME%
ENV=MOZILLA_FIVE_HOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\MOZILLA
ENV=CREO_APP=PMA
ENV=DBG_NCPOST_PATH=%CREOAPP_DIRECTORY%\bin
ENV=PATH+=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\deflib
ENV=PATH-=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\lib
ENV=PATH-=%INTRALINK_DIR%\%PRO_MACHINE_TYPE%\illib
ENV=PATH+=%PRO_DIRECTORY%\libs\dfor\lib
//
//-FROM SYSTEM VARIABLES
//
ENV=MAN_CHM_INDEX=C:/ptc/CP2/MKSTOO~1/etc/chm/tkutil.idx;C:/ptc/CP2/MKSTOO~1/etc/chm/tkapi.idx;C:/ptc/CP2/MKSTOO~1/etc/chm/tcltk.idx;C:/ptc/CP2/MKSTOO~1/etc/chm/tkcurses.idx
ENV=MAN_HTM_PATHS=C:/ptc/CP2/MKSTOO~1/etc/htm/perl;C:/ptc/CP2/MKSTOO~1/etc/htm/perl/pod;C:/ptc/CP2/MKSTOO~1/etc/htm/perl/ext;C:/ptc/CP2/MKSTOO~1/etc/htm/perl/lib
ENV=MAN_TXT_INDEX=C:/ptc/CP2/MKSTOO~1/etc/tkutil.idx;C:/ptc/CP2/MKSTOO~1/etc/tkapi.idx;C:/ptc/CP2/MKSTOO~1/etc/tcltk.idx;C:/ptc/CP2/MKSTOO~1/etc/tkcurses.idx
ENV=PATH+=C:\ptc\CP2\MKSTOO~1\bin64;C:\ptc\CP2\MKSTOO~1\bin;C:\ptc\CP2\MKSTOO~1\bin\X11;C:\ptc\CP2\MKSTOO~1\mksnt;
ENV=TERMINFO=C:\ptc\CP2\MKSTOO~1\usr\lib\terminfo
ENV=TERMCAP=C:\ptc\CP2\MKSTOO~1\etc\termcap
ENV=ROOTDIR=C:/ptc/CP2/MKSTOO~1
ENV=NUTCROOT=C:\ptc\CP2\MKSTOO~1
ENV=TERM=nutc
Terms & ConditionsCookie settingsAccessibility statement