Steve, I know of IT technicians who split the Creo install into three packages if that helps?
Printable View
Steve, I know of IT technicians who split the Creo install into three packages if that helps?
It might do if it means it can be deployed automatically to the required workstations.
We've been trying to get Creo to work with @TimB's help, which we have done now.
We installed the Creo package onto a client PC 1st. Then built a clean packagebuild PC - ran the application wizard. Copied the whole of the PTC folder from the 1st PC to the packagebuild PC - ran it & did second scan and it imported fine. (2.5GB)
We've only pushed it out to 15 Macs (which are Bootcamped on Win7) at the moment and seems to be working fine. We had @TimB visit us beginning to the week and we've noticed a couple graphics glitches which we're trying to correct, but it doesn't affect the useability at all. Something probably due to the bootcamp mac driver.
You'll need to set the permissions for users to be able to run scripts. In the RMMC, under Reg policies, User Policies, select usertype you want to change, Software Restrictions and leave "Disable the command prompt ticked, but the sub option "Disable the command prompt script processing" change to No.
Set the shortcut properties to Start In N:\ so it'll default to their home directory first.
Seems to run ok for us though! Looks a very impressive & very powerful programs. Working motors/physics on models you've made.
Many thanks for that. I daresay it won't be too long before we get asked to look at this.