How do you distribute Creo Parametric config and setup files at an enterprise level to end users?

[Prabhu]

Hi,

I want to understand what ways you have employed to distribute Creo Parametric config and setup files at an enterprise level to end users.

We use SCCM to distribute / deploy base Creo Parametric application, but to distribute config and setup files, we use windows batch script that gets invoked once a day at end users' machines.  The setup files are kept at few regional servers (as repositories) and the batch script copies (robocopy, syncdirs) these files into the end user's device.

We have not opted for packaging Config and setup files through SCCM as these files are changed or new files are introduced frequently.  And the need is to get them distributed as immediately as possible.

Our requirements:

Config and Setup files are maintained at one network location (mother repository).

These files should be replicated to Regional specific repositories.

The files then should be pushed from each Regional Repositories to end users located in respective region.

Any change done at the mother repository (introducing new files, change / deleting existing files) should be sensed and the same should be deployed on all end users' machines as immediately as possible.

Am assuming that am not alone.  This need could be for any application with a bunch of Configuration or Settings files.

How do you guys manage this?

Thanks.

[Catalina]

Hi @Prabhu 

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Best regards,

[Chris3]

My company just uses a startup script. We are only one physical location though.

I have been to a number of PTC/User conferences where this has been talked about. Most companies just have a startup script that copies the files that they need to the client machine before launching Creo.

The bigger organizations will have custom written programs with UIs that allow the users to go in a check off what license options they need and then that program also copies down the company settings.

[Prabhu]

Thanks for your response @Chris3 

I agree to your view - this has been handled by scripts only by most of the admins.  I guess there has to be some standard application that could do this job.  Am not sure if any such tool had been deployed successfully.

Thanks again.

[Cipruss]

Hello,

We use start script which copies all necessary files when Creo is launched, it also determines:

• Which license user should take out.
• From which server load files.
• Sets system variables.
• Calls install script if no Creo found or we are updating to newer version.
• Collects last sessions trail file, keeps last 10 on users PC.
• Calls purge.bat
• Cleans working directory from unnecessary files.
• Cleans embedded browser cache.
• Collects traceback.log files. 

Then I have separate scripts to distribute config files to servers. Those I launch whenever I do any changes. Same for installation files and setup files for silent installer.

/Girts

[Prabhu]

Hi @Cipruss ,

Thanks a lot for your response..  You had very well detailed all the actions that your script takes and I could relate to them very well.

Nevertheless, all I have been hearing in this thread so far is managing this task through scripts.  And that is how we too manage our users and it serves very well.

Am not sure if there is any application that can do this task - something more configurable (like what to push, when to push, upgrade scenarios, etc.,).

Thanks again.

[Srinivasan_Iyer]

Hi Prabhu,

Please refer to the points 3 and 4 in the link. Hope this helps.

About Configuration Files