I'm working on my Creo 3 install batch file. I am using David's tokenizing ptcstatus.batin Creo 2.0 to identify the buildecode allowing me to copy files down to clients to standardize the configuration.
Creo 3.0 installs to a path with the build code in it. C:\Program Files\PTC\Creo 3.0\http://communities.ptc.com/message/250391#250391
Thanks for you thoughts, Vaughn
Does anybody have any experience withhow Microsoft SCCM ( system center configuration manager) handles maintenance code beingadded to the path of the start up commands? Our IT department seems to be unhappy that every new maintenance release is going to be at the different location, comparing with Creo 2.0 where startup commands were at the fixed location and common files were at the maintenance related location. I should add that IT is pushing Windows 8.1 for the new workstations and my attempt to run Creo 3.0 Parametric from the shared drive had miserably failedwith the workstation running Windows 8.1 and domain security policies to be at the quite restrictive level.
Thanks in advance.
In Reply to Tom Uminn:
The Creo Agent no longer needs to be installed. It will run from wherever the files are placed (locally or network location). The newer thumbnail viewer should work fine with previous releases, so I typically let that automatically update to the latest.