The community will undergo maintenance on October 16th at 10:00 PM PDT and will be unavailable for up to one hour.
Not sure about the drive letter solution. I ran into the same issue when attempting to do so these past couple of weeks.
I can confirm that installing Creo 2 locally then moving the folder to the network is a viable option.
The performance hits come when you attempt to access some of the standard files that are located in the Creo install, such as the hole tables. It's practically impossible to detect unless your network is usually slow or congested.
There were other issues we ran into, some of which had easily found remedies from PTC, some of which did not.
Today is the first day of running Creo 2 (with Windchill 10.1) from the network install, so I don't have much data to back up the viability of this method.
In Reply to Dave Clark:
Hello Everyone,
In the past we've always done local installs on everyone's PC. We have customized so much in the last couple of months that doing updates on each PC is a bit of a hassle, so I'd like to install Creo on a network drive.
I'm running setup.exe as an administrator, and it looks like it would install as normal on my C:\ drive, but if I type any other network drive letter, the "Next" button grays out and I can't do it.
I've seen some online postings where folks have said they've installed it locally and then copied the Creo folder to the network. I find it hard to believe that would work, but nothing surprises me anymore.
So, if someone can point me in the right direction, I'd certainly appreciate it.
Also, has anyone noticed if you have any performance hits as a result of running from the network? I figured after Creo starts, it would be the same as running from your local drive.
Thanks, and have a great day.
Dave Clark
Sr. CAD Application Engineer
Dukane Corporation
Intelligent Assembly Solutions Division
2900 Dukane Drive
St. Charles, IL 60174
630-797-4922 (Phone)
630-797-4949 (Fax)
I have ran all versions of Wildfire, Creo 1 and Creo to as a network install and I used the standard installer with no issues. Anything that needs to be installed locally is done when the user first runs Creo. This happens only once and it's simple.
The Network install has many advantages, especially if you have many users. I always install a new build on it's own folder and keep the current build. This allows me to install the new build while everyone is running the current build. When I am done, I update one line on a batch script that points to the new <loadpoint> and the next time the user launches Creo, they get the new build.
I always keep one previous build in case some bug shows up that we did not realize and I need to revert everyone back to the previous build. If this happens, it's as simple as changing the <loadpoint> on the batch script and I am done.
This allows me to install new updated or versions without users having to stop what they are doing.
I recently did this from Creo 1.0 to Creo 2.0. I changed the <loadpoint> on my script and when my users closed Creo 1.0 and relaunched it via the shortcut on their desktop, they were running Creo 2.0
I only had one issue with Wildfire 5 were I had to change the PSF file to point to the FEA folder by typing in the actual path on the PSF file itself. This is no longer needed for Creo 1.0 and Creo 2.0
"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"
David,
Could you help me understand the advantage or need to do what you described?
I have always installed Creo on a Network Server using the built in installer and have no issues. We run Creo Parametric 2.0 and Creo Simulate 2.0 with this process. I don't do anything with registry keys on the server or on the clients.
I simply created a batch script that controls what license each user gets based on their username and put the shortcut to this batch script on their desktop. They double click this "Creo" icon and launch Creo with no issues. The first time you do this the user will have to accept the Creo Viewer installer but that's it. It's a simple one button process and off they go.
What do you mean by "Silent Install"?
I can install a new build or version of Creo while all my users are working. Once I finisht the new install, I simply open my script and change the path to the <loadpoint>. From this point forward when my users double click on that same Creo icon on their desktop, they autoamtically run the latests build or version of Creo on the Network.
When I install Creo on the Network, I use Remote Desktop and run the actual install on the Network Server itself. We use a VMWare Server for this purpose.
I must be missing something because this has always worked.
Any thoughts?
"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"
David
Thank you for taking the time to explain. It's very clear to me now. We do give our users admin rights which is why I never had to worry about it. The information you shared is good to know but it seems I can still benefit from the way I do it since my users have admin rights to their personal computers.
As for the .PSF files, I don't edit them but simply call them out on a script that assignes the correct license to the user who launched Creo based on their username. I have certain users who require a particular license package while others require a different license package. This includes certain extensions like REX and AAX.
Thanks again for sharing and clearning it up for me. Seems that in your situation, you are doing exactly what needs to be done to run things smoothly.
"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"