Skip to main content
V
vmcdaniel1-Visitor
1-Visitor
September 22, 2014
Question

Creo 3.0 install and build code identification

  • September 22, 2014
  • 10 replies
  • 3810 views

Hello,


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


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

10 replies

D
davehaigh13-Aquamarine
13-Aquamarine
September 22, 2014
Just got our licensing straightened out so I could get a Creo 3 license file. So I haven't had a chance to look at it.
I was told by PTC at the conference that there were going to be some changes in the install. They indicated it would be for the better.
Adding a maintenance release folder to the parametric path wasn't what I was expecting.

David Haigh
T
TomU23-Emerald IV
23-Emerald IV
September 22, 2014
I actually really like it. I customize the install location for the agent and the help files in order to keep everything for each build together. Makes it much easier to jump between builds.

[cid:image001.png@01CFD65B.E2CFA220]

O
ocorten-212-Amethyst
12-Amethyst
September 23, 2014
Try this:

set CREO3PATH=C:\PTC\Creo 3.0
REM Check and set current build
set CURBUILD=Unknown
REM CURBUILD will be set to the alphabetical latest folder
FOR /F %%i IN ('dir /AD /B /ON "%CREO3PATH%\F*" "%CREO3PATH%\M*") DO (set CURBUILD=%%i)
REM Error message if no build folder has been found
IF NOT EXIST "%CREO3PATH%\%CURBUILD%\Common Files" echo ERROR: No valid Creo 3.0 build found in %CREO3PATH% (%CURBUILD%)


The most annoying part with the build code in the installation path is that it is also in the .psf and .bat files in the Parametric\bin folder which I also maintain through our customization script

Kind regards,

Olaf Corten




Olaf Corten | CAD/PLM Manager

Besi Netherlands B.V. | Ratio 6| 6921RW Duiven| The Netherlands
T: +31 26 3196215 | M: +31 644548554
- | www.besi.com



From: "Uminn, Tom" <->
To: "-" <->
Date: 22-09-2014 17:54
Subject: [proesys] - RE: Creo 3.0 install and build code identification



I actually really like it. I customize the install location for the agent and the help files in order to keep everything for each build together. Makes it much easier to jump between builds.



D
davehaigh13-Aquamarine
13-Aquamarine
September 23, 2014
Unless they have done something different with the thumbviewer and the creo agent, your still not going to be able to have two different maintenance releases on the same computer.

David Haigh
T
TomU23-Emerald IV
23-Emerald IV
September 23, 2014
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.
F
FV_0117-Peridot
September 23, 2014

Hi all,


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.


Feliks.

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.
MikePhillips
MikePhillips12-Amethyst
12-Amethyst
September 23, 2014
Hello Tom,

Can you confirm that Creo Agent does not need to be installed with Creo
Parametric 3.0? When I launch without it installed, I'm not prompted to
initiate the installation (like I see with Creo Parametric 2.0) but I do
see a warning message in the message display error letting me know that the
agent has not started (see image below).



I also get this message.



Regards,


Mike Phillips
Raytheon


R
RandyJones20-Turquoise
20-Turquoise
September 23, 2014
On 09/23/14 14:17, Michael D1 Phillips wrote:
>
> Hello Tom,
>
> Can you confirm that Creo Agent does not need to be installed with Creo Parametric 3.0? When I launch without it installed, I'm not prompted to initiate the installation (like I see with Creo Parametric 2.0) but I do see a warning message in the message display error letting me know that the agent
> has not started (see image below).
>

You need to set the (undocumented for Creo Parametric 3.0) environment variable CREO_AGENT_EXE_PATH
per PTC article CS104032
>
> From: "Uminn, Tom" <->
> To: "Haigh, David A." <->, "-" <->
> Date: 09/23/2014 10:15 AM
> Subject: [proesys] - RE: Creo 3.0 install and build code identification
>
> -----End Original Message-----


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

T
TomU23-Emerald IV
23-Emerald IV
September 23, 2014
Yes, that is correct.

I spent quite a bit of time figuring out how to make it run over the network. I was able to determine that by creating one registry entry and adding one additional file to the install folders I could get it to run. I then shared this with PTC and they came back with this undocumented environment variable.

In my opinion, if they are going to allow you to install it to a network location, then it needs to run correctly after installation without adding additional environment variables.

Tom U.
B
bfrandsen10-Marble
10-Marble
September 26, 2014
By adding a build code folder further up the installation path you can have several maintenance releases installed.
I use this to have current production and newer releases installed on my machine.
C:\Programs\PTC\M110\Creo 2.0\Parametric
C:\Programs\PTC\M120\Creo 2.0\Parametric

Best regards

Bjarne Frandsen | Technology Specialist, MCAD
Phone: +45 9684 4825 | Email: -

[cid:image001.png@01CDCC9C.5B8352F0]

Bang & Olufsen A/S | Peter Bangs Vej 15 | DK-7600 Struer | Denmark
www.bang-olufsen.com
Terms & ConditionsAccessibility statement