As long as I've used Pro/E (17+ years), there was generally a company "config.pro" (and perhaps other files) and a separate user-customizable "config.pro" (and perhaps other files). The loadpoints were specified in a path statement, usually in a batch file. This allowed the company to set certain standards, yet allowed users to customize mapkeys and other settings that did not compromise the company standard settings.
Are people still doing this?
This is the way I've set up the systems here, and all the ex-Solidworks users are trying to tell me it's the "wrong way", and that it should all be networked. I'm trying to explain to them that having a local (C:) folder and a "config.pro" file that is specific to each user allows them to individually customize their configuration and performance, and it's falling on completely deaf ears. And that putting that on the network in a single file is pointless. Might as well then roll EVERYTHING into a company "config.pro" file and call it a day, but that means they' cannot customize anything. Or, if they want to customize things, then we need to clutter up our network drive with individual folders, and then have individual path statements in the "config.pro" to get to things like their syscol.scl, tree.cfg, and .dtl files. If it's in a local directory, say: "C:\FRANK\(C) PROE\(C) CONFIGS" then I need to only push this out once, and the paths always work regardless of them changing mapkeys or settings.
I think it's far easier to have the users have control their own files at the local level, than trying to do it all at the network level.
Thoughts?