How to centralize the config.pro?

[Thanus_MR]

I want to centralize the config.pro in a shared drive location. Basically, when users launch parametric, it has to use the config.pro from that shared drive. I have gone through few articles and came to know about config,sup and I'm still not clear the concept of this. Please assist me here. Thanks in Advance!

[BR84]

This one is old but still the best:

https://www.youtube.com/watch?v=JyyTCnvyx0k

A couple of new features have been introduced to Creo since the time this video was released, but all can be taken care of in the same manner, as you can see in this video.

Good luck.

[BenLoosli]

There are now alternate folders where the configuration files may be located.

Article - CS384810 - Is it possible to read / load Creo Parametric configuration files (*.pro, *.sup & *.ui) from a location other than <creo_loadpoint>Common Files ext directory ?

[Chris3]

@BenLoosli likely has the best answer for you but to expand on that, most medium to larger companies have startup scripts that do things like setup standards, delete extra files and maybe configure licensing. PTC fairly recently added an environment variable option to point to configuration options. You could define this environment variable in your startup script. More info on startup scripts here:

https://community.ptc.com/sejnu66972/attachments/sejnu66972/installation_licensing/1673/1/ProE%20Launch%20Script.docx 

[Chris3]

If you have more questions like this in the future, you will likely get better responses from the system admin group:

https://community.ptc.com/t5/System-Administration/bd-p/installation_licensing 

This customization group is mainly for how to write custom toolkit applications for Creo.

[BenLoosli]

I asked the moderators to move this thread.

[remy]

to add-up to all that has already been said, the better practice is to keep a config.pro in shared location, to protect is from unwanted alterations.

then on Creo start-up, copy that config to the local location of your choice so that any modification to the config remains local and does not affect the shared one.

This document is still a reference in scripting (after 15 years) : https://community.ptc.com/t5/System-Administration/ProE-Launch-Script-docx/m-p/444745

[Thanus_MR]

Hi @remy  @BenLoosli ,

         Thanks for your suggestions. It helps. Is there any way where we can control it through the environmental variable while we launching the parametric? I saw there's a Enviromental variable Just to let you know, we are using Creo 8.0. Because in our organization the user wont be having the admin access to their machines. As I saw the batch file is removing the config.pro from Common Files/text/Config.pro which might require admin access. Please let me know if there's any other way.

[remy]

Hi

that environment variable has to be PTC_CREO_ALT_SETTINGS_PATH 

according to this article : https://www.ptc.com/en/support/article/CS384810 it has been introduced in 9.0.2.0

[Chris3]

You do this in a startup script. If its a .bat file it would like something like this:

REM ****************************************************************************
REM set the config.pro folder location to a network drive
@set PTC_CREO_ALT_SETTINGS_PATH=N:\Folder\SubFolder\Configs
REM ****************************************************************************

As noted in the article that Ben linked to though, this is a new feature starting with Creo Parametric 9.0.2.0

If you can't move off 8 then you can copy the company config.pro to the load text point. Something like this:

robocopy "%SERVER_DIR%\" "%CREO_LOAD_LOCAL_DIR%\text" /r:0 /NDL /NJH /NJS /nc /ns /if config.pro config.sup creo_parametric_admin_customization.ui

Where Server_DIR is your network location and Creo_Load_Local_DIR is:
<Creo Load Point>Creo X.Y.Z.0\Common Files\text

[anursingh]

Hi @Thanus_MR,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation. 

Thanks,
Anurag 

[BenLoosli]

That is a great guide to customizing the startup of Creo. I have referenced it many times in building my custom Creo launch scripts.

I do have a group level config.pro that I copy to the user's home directory every time Creo is launched. 

We load the following configuration files when we start Creo:

<Creo Loadpoint>/Common Files/text/Config.sup

<Creo Loadpoint>/Common Files/text/Config.pro

c:/users/<username>/config.pro - copied from a common folder on Creo launch

c:/PTC_User/<username>/config.pro