Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
Morning all.
At my place of work we are running Creo 8.
We are still in the early days of setting it up correctly.
I want to save the config.pro file on the network so that all our users accounts point to same same location so that we all use the same configs - at the moment they are on peoples C drives.
I cant seem to find a way to do this.
Can anyone advise please?
Thanks.
Solved! Go to Solution.
Hi,
in Creo 8.0 you have to copy config.pro from network drive to C: drive before you start Creo. You can automate this step by using parametric.bat as Creo startup command.
In Creo 9.0 you can set PTC_CREO_ALT_SETTINGS_PATH variable. Please read https://www.ptc.com/en/support/article/CS384810 document.
Start here for an overview:
About Configuration Files (ptc.com)
You can have multiple config.pro files read at startup. You should consider if the use of a config.sup version would be appropriate for your environment.
Hi, i've read through that but it doesn't seem to help?
I can save the config.pro to a network folder but I am having trouble directing the user accounts to that location on log in.
My log in points to this location on start up (see attached)
I can't seem to change it to a network folder
You can not point the config.pro file to a network location prior to Creo 9.
What you have to do is copy the network config.pro to the user's Creo loadpoint when Creo starts every time. Put the copy command in parametric.bat in their <loadpoint>/bin folder. This way any changes to the network copy get copied to all users every time.
Hi,
in Creo 8.0 you have to copy config.pro from network drive to C: drive before you start Creo. You can automate this step by using parametric.bat as Creo startup command.
In Creo 9.0 you can set PTC_CREO_ALT_SETTINGS_PATH variable. Please read https://www.ptc.com/en/support/article/CS384810 document.
Are you using local copies of Creo or a single network installed copy?
Network installation saves a lot of the hassles of where to put the configuration files plus makes it easier when you have to do an upgrade to a newer build or version. I use a batch file that controls the configuration files and the different builds that the users can use.
Hi, local copies.
I think I'm going to have to put the file on the C drives
If you have to install Creo locally, then your only option, until Creo 9, is to do as Martin said and force a copy of the master network files to each user's local drive. Easy to do, but a PITA.
Running a default company standard config is important but users still need to be able to customize there own work environment. Mapkeys and system colors (very important for color blind users) are 2 reasons to allow users to streamline a their own work environment.