Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
Later this year, we will deploy Windchill for the first time. (currently using Intralink 3.4)
When users launch Pro/E, they will need to register the one-and-only Windchill server.
I would like to automate this in our launch script.
For example, can I specify the server in config.pro?
Or set an environment variable?
Other?
Gerry
I understand that it is indeed a set-once occurrence.
Unfortunately, I have a considerable number of "unsophisticated" users who will ignore the instructions or fail to follow them correctly.
I am hoping to avoid a bunch of unnecessary helpdesk calls.
Gerry
In Reply to Jeff Horacek:
Registering the server is a set once occurrence. I don't want to rain on Gerry's approach, but a mapkey is a little overkill unless you have multiple servers. Most places don't. We simply register the server once, and then each day when the user starts Pro/E and they want to access their workspace they're asked for their login credentials...done.
Thanks to all that replied.
I was hoping for a simple (and central) method such as an entry in config.pro, but the life of an admin is rarely simple.
The alterntives are not ideal, but one of them should work for us.
Thanks again.
Gerry
In Reply to Gerry Champoux:
Later this year, we will deploy Windchill for the first time. (currently using Intralink 3.4)
When users launch Pro/E, they will need to register the one-and-only Windchill server.
I would like to automate this in our launch script.
For example, can I specify the server in config.pro?
Or set an environment variable?
Other?