Creating administrative image for Wildfire 2.0

[toocoo3]

Hi,
Ive been doing some research on how to create an adminitrative image install (.msi package) for Wildfire 2.0, but I cant seem to find any information on how its done. We have a multi-user environment here that would make installation of Wildfire on each computer seperately a major pain.

I have come across the option of installing the program onto the server, and creating a shortcut to the exe on the clients machine. I can see this as a easy alternative, but wouldnt this cause noticable lag (our power users would definitely notice any performace decrease)?

Any insight as to how you other admin's are getting it done would be great.

Thanks,
Mark

 

[HDS]

It used to be possible to have a copy of the newest date code on the server and to create a batch file that copied any files that were newer from the server before starting pro. You would still have to install locally the first time but it made updates easy. I have not tried this with Wildfire so I do not know how well it works.

 

[dgallup]

We run with a server install only. The user just has a shortcut on their desktop. The only lag you see is starting the program and that is dependant on your network. If you have gigabit ethernet it won't be noticeable. It takes about 35 seconds to load completely on our 100 mbit ethernet. Once Pro/E is running there is no difference in response.

However, if you record a trail file of your PTCsetup session you can use it to automate installation on other machines. See the WF2 installation guide page 24.

 

[toocoo3]

Hey, thanks a lot guys for the replys. I went ahead and installed it on our server, did a straight copy of the ProE directory, and the copy worked. Seems way too easy compared to the admin install of SolidWorks. One other place I just came across for more material was this page:

http://www.ptcuser.org/2004/downloads.html

The powerpoint and the sample script files are definitely worth the time to look at if anyone else is trying to research this. Thanks again for your help

 

[HDS]

One important note on installing pro/e. The default installation directory has spaces in the names. there are parts of pro/e that do not like this. It is better to install it in something like c:\ptc.