Skip to main content
D
davehaigh13-Aquamarine
13-Aquamarine
December 3, 2012
Question

m020 to m030 update - bad news

  • December 3, 2012
  • 2 replies
  • 610 views
The bad news is it totally removed the m020 folder under Common Files.

Previously it left that folder so you could go grab your configs & .ui files out of it and place them in the new location.

Fortunately, I have other copies.

David Haigh

    2 replies

    D
    DamianCastillo1-Visitor
    1-Visitor
    December 4, 2012

    I run my Creo install as a Network installation and the clients only have a shortcut that points to a custom batch script I created. Among other things, the batch script will retrieve each users config settings from a network folder that is separate from the Creo install.


    I did this to prevent anyone from loosing their configuration settings when moving from one release to the other. Their personal hard drive could go out and it would not matter. Creo and the user config files all live on the network.


    "Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

    B
    bfrandsen10-Marble
    10-Marble
    December 5, 2012
    We have local installs as our engineers must be able to work from outside the company in Creo on a low bandwidth network, but all configurations are stored on a network drive and copied locally at launch if needed.

    /Bjarne
    Terms & ConditionsAccessibility statement