Intalink Work spaces

[Tofflemire]

Hello All,

Last week our company just upgraded to a Windows Server, now when we start Intralink there are no work spaces. We had Intralink to point to C: and this is where the .Proi directory is created. Since the upgrade Intralink creates a new .Proi directory in documents and settings/user/. We did not change any of the Intralink settings, so why is Intralink pointing to this place now. How can I fix this issue?

Thanks in advance for any assistance you provide

Tofflemire

 

[looslib]

Modify the proiclient3.3.bat file with this line:
set PDM_LDB_PATH=c:\



"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[Tofflemire]

Hi Ben,

Thanks, that worked. Now ProE also starts in the wrong directory, is there a fix for ProE batch file?

Tofflemire

 

[looslib]

What do you mean by 'wrong directory'?

When you do a file open, is it looking in your my documnets instead of the start in directory?

WF2 config.pro: file_open_default_folder = working_directory


"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[Tofflemire]

Hi Ben,

Sorry for being a pain. We have a generic batch file that runs every time Intralink is started. This move files from the network to directories on each work station. This does not work if it has to look for user's names (not generic). This ensures that everyone has up to date templates, config.pro and .sup files, color maps.... Also helps to configure new ProE computers. We have users who like to mess with plotter settings and pen weights. The problem is that ProE does not load config.pro, but defaults because it is loading in documents and settings folder. I would like it to load from the C:\.

Tofflemire

 

[looslib]

Why does everyone copy the 'default' files at startup? We have our files on a network server and everyone reads the files from there. No time spent while everything is copied at every startup. We did this with local installs and network installs of Wildfire. We have now gone to almost all network installs. One install and I have 50+ users on the latest build. No wasted time while system management software checks to see if a workstation has the latest build and then does an upgrade if needed. Make network files read-only and only admins can change them.

Split your config.pro into two files. One is in the <proe_loadpoint>\text directory (along with config.sup) and the other is in the start-in directory. The main one in the text directory has your company settings. The start-in one has 1 line of something you don't care if the users change. When they go to Tools-options they get the local file. They can add to it and override the system one, but so what.




"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand