SETTING UP PRO CONFIG.SUP

[dfdills]

I NEED HELP WITH SETTING UP THE COMPANY I WORK FOR. I NEED A DOCUMENT TELLING ME WHERE THE CONFIG.SUP FILE WOULD BE AND HOW TO SET UP MULTI USERS TO USE IT. ALSO HOW SOMEONE CAN LOG ON ANY MACHINE AND HAVE THERE SETTINGS AT THAT MACHINE. I AM NEW TO ADMIN.

DAVE

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[dgschaefer]

The config.sup must be in the 'text' folder of the the Pro|E load point.
Be careful of the options you put in there as these cannot be changed by
files loaded later. So, if you put a mapkey in there, the user will not
be able to have any other mapkeys. Also, don't get carried away trying
to lock things down. I only place things in that file that I absolutely
want everyone to do the same because it affects the integrity or
consistency of the Pro|E data.

You can create a batch file that will copy the company config.pro and
config.sup from a server folder to the local load point/text folder at
Pro|E start up. Set your Pro|E icon to call this batch file and then
the batch file calls Pro|E.

There is a lot more that you can do, I copy the config files, copy the
launch icons, set the working directory and prompt the user to choose
what client they are working on and then load the proper config files
for that client. That system has evolved and grown over time. I'd take
it slow, start with your company configs and go from there.

As far as making it so anyone can log into any machine, log in and use
Pro|E just like their home machine, that's more of a general IT thing.
Generally, you want to make sure each user is mapping the same server
folders with the same drive letters, in particular the folders where you
are storing the user configs and the company configs. For us, company
configs get copied to the local load point and we set the user config
folder as the starting directory so they get loaded as well.

Oh, and turn off your caps lock, you're yelling at us. 😛

Good luck,

Doug Schaefer

[msteffke]

For us, company configs get copied to the local load point and we set
the user config folder as the starting directory so they get loaded as
well.

I agree Doug thats what we do too.

I'll add a little more about user on any machine. Set up a folder on
the network, called users. Under that folder create a folder for every
persons logon username. For example, if you had a user named Charlie
Brown, and his windows login was c_brown you would have a folder on the
network drive of k called k:\users\c_brown. Its important the the
folder you create matches the users actual login name. Then Setup a
shortcut to pro/e or a shortcut to a bat file that copies config files
and starts pro. In that shortcut set "start in" to k:\users\%username%.
This will pick up the users login name and make it working directory in
Pro. Any config.pro or config.win setting in this folder will load
upon startup. When they change a setting or add a mapkey, it saves
back to the config.pro or .win in this networked folder.
I was taught this method back in 1998 either by a ptc AE or a training
class and still do it this way. Maybe theres a better way now but this
still works well for us.



Mark Steffke
Engineering System Administrator
The Delfield Company
Manitowoc Foodservice
T 989.775.9215
Integrity, Commitment to Stakeholders, and Passion for Excellence

[dgschaefer]

Mark,

Good point, that's what we do here as well. I even go as far as to have
the batch file create the user dir if it doesn't exist. That way, the
user's config folder is autmagically created when they first launch
Pro|E and I don't have to do anything for new users. The less I have to
think about, the better. 😛

Doug Schaefer