×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Creating administrative image for Wildfire 2.0

Creating administrative image for Wildfire 2.0

Creating administrative image for Wildfire 2.0

(OP)
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

RE: Creating administrative image for Wildfire 2.0

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.

RE: Creating administrative image for Wildfire 2.0

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.

RE: Creating administrative image for Wildfire 2.0

(OP)
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

RE: Creating administrative image for Wildfire 2.0

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.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources