I am looking for some way to map the network share in Creo so will try to read related config.pro and startup files from network share and no need to copy on local system.
Creo always reads the config.pro from the <loadpoint>/text folder, no need to copy it to local disk.
For other special config.pro settings, put them in the start-in folder.
If you need multiple project specific config.pro files, use multiple icons for each one with different start-in folders.
Set the variables in the config.pro to point to shared/network disk locations.
I run a setup.bat file from the parametric.bat that sets our environment variables for using Creo across the network.
The Creo image is only installed once on the network drive.
We have installed Creo on each individual user system, so I am looking for the way to read the config.pro from network share and not the text folder.
We dont have any plan to copy this configuration files every time on user system before start of Creo using batch file which delays the start up of Creo.
Creo reads config files in this order:
If you don't want to copy config files (which isn't that hard), then set the start in field to your network location where your config files are located. If you want to use a config.sup file, however, it must be in the <loadpoint>/text folder, Creo won't read it from anywhere else.
Even if all the machines have Creo installed individually.
You could have a "short cut" on the network, that is copied to the desktops. with a copy "\\ command included for the config.pro If your only overwriting the config file that really would not add any noticeable time executing Creo.
I run a .bat file that roughly does:
-sets local load and start points
-sets system drive
-sets/creates local working directory
-sets print/plot directories
-sets local cache, trail, and program file locations, and modelcheck file locations
then it verifies any file I desire located on the local machine is the latest from the network. if not, it gets over written.
This way admin has some control. Too often users will save modified config.pro's to the start directory and not their local work directory and this destroys consistency.
If this gets too far out of hand, I add to the .sup file - then no one can change that given variable.
all this takes about, uhmm 2 seconds on a slow day. a little longer if the directories need to be created for new users.
Just my 2.5 pennies
something you may want to review:
Thank you for sharing that launch doc Ron St.Pierre! I was looking for an easy way to set environment variables for alternate cache location in Creo, and stumbled onto this thread with your launch script doc. Your solution for creating local cache directories through the Creo launch file was perfect. A lot of other great scripts here too, with really terrific explanations on how they work.
I'll be using this doc a lot. Can't thank you enough for posting it.
It seems there have been a couple of helpful answer.
Anything you have verified to be useful for your intent?
If yes, please consider getting back to the thread and mark the answer as Correct Answer, to signal to community that there is an answer.