Using environmental variables, you can change the order of Variables are not set, local installation takes precedence even if Creo finds the (creoagent.exe and Creo platform) is installed locally and the environmental If Creo is started from a network install and Creo Platform Services package \\SERVER\CREO4_Share\Creo\Platform\4\manifests).įor local installation, the above environmental variables are not used. Point to the manifests folder on the Platform location. The environment variable, CREO_AGENT_LDP_LIST must also be set and must However, if the Creo installation structure in the network location is differentįrom the default one, then the environmental variable CREO_AGENT_EXE_PATH Share\), then Creo automatically finds the creoagent executable file relative toĬreo does not require the environmental variable CREO_AGENT_EXE_PATH to If a Creo installation on a custom location (For Example, D:\PTC), is relocated toĪ network drive (For Example, D:\PTC is exported as \\SERVER\CREO4_ Not need to install Creo Platform Services on your client machine. If you access Creo applications from a shared location across the network, you do psf file.įrom the "Creo® Installation and Administration Guide" page 53: New is the Installation of the Platform Agent along with the Creo Agent which is to a different location than for Creo 2.0 and not using the ENV's in the.
The share, registry, net use and installation is taken/adapted from the former Creo 2.0 approach. The environment variables are not needed in this case.
The Agent and the Platform Services are installed then to there default location - in this example to D:\PTC\Creo. Then I installed all the Creo applications to D:\PTC. So the load point for all user is D:\PTC to which they are connected. "D:" to the share "net use \\servername\creoapplication". Our IT is using a Microsoft software distribution for this.īevore on the server I shared \\servername\creoapplication and connected drive letter i.e. The created.reg is given with a silent installation to the clients "regedit /s created.reg". And updated created.reg from the installation on the server: I have "\\" the environment entry ENV=CREO_AGENT_EXE_PATH I used before for Creo 2.0 and CREO_AGENT_LDP_LIST in the parametric.psf. What helped was the admin guide (see below) - all the CS confused me. We moved from Creo 2.0 to Creo 4.0 M040 (shared over the network) in March this year and I had the same trouble with the creoagent.
0 kommentar(er)
