Templates being overwritten with Default IV templates

[bruce.buck]

I can’t tell why this is happening, but every once in awhile our templates get overwritten with the default Inventor template files. You can see in my screenshot below the backups I have of our official templates, and the modify dates. On the right is our template location and the files that get overwritten. The only thing I can think of that is common in each incident, is that it seems to happen right around the time that we're fixing an issue on someone's workstation where an Autodesk product isn't properly deployed (Group policy didn't install Inventor, or AutoCAD, or NavisWorks, etc). After the issue is corrected we go though the step of importing Application options and User commands. Then as soon as they go to start a new document, our company templates are no longer there, but get overwritten with the devault IV ones. There is also an "Old Templates" folder created with copies of our company templates.  Would the deployment of that be causing this, or is there something else going on?

[blair]

I would change the file name from Standard to something else unless you need the standard to be in the short-cut menu. This shows what "Standard" does. Possibly IT is overwriting your modified "Standard" with the default that ships and installs with Inventor. We save our company templates with the following name: Comp_A, Comp_B, Comp_C, Comp_D and Comp_E for our different sized sheets. If you use Comp_C as our main, we would do a Copy and Rename to get it to the file name "Standard". I have included w quick Chronicle link as how Inventor treats the name "Standard" https://chronicle.autodesk.com/Main/Details/8b592e54-69ad-4a17-ad1d-a652609229e6

[bruce.buck]

The only issue with not naming the template "Standard", as I understand it, is that during Import and other operations that use a template (say, importing a STEP file, performing a Shrinkwrap on an assembly), IV looks for the template explicitly named "Standard". If it doesn't find it, it reverts to a default IV template to complete the operation. Since our Part and Assembly templates have custom coordinate systems/orientations, this wouldn't work.

Unless I'm not understanding this situation correctly. Is there a way to have custom-named templates and ensure IV uses those template on internal import/conversion operations?

Also, even if it didn't overwrite them (since they'd be named differently), we still wouldn't want new ones popping up and being made available to designers. We want to ensure everyone is only using the approved template files.

[blair]

When importing a STEP file, in your options there is no default template. You do have the option of choosing the units. On the Shrinkwrap the default shows "Standard.ipt" but you do have the option on the box (drop-down) to select what ever template you choose. We have a number of "Part" templates that have been set to the desired material and units we wish to use for our parts. Much easier to have the proper materials and appearance set for each template.

[bruce.buck]

"When importing a STEP file, in your options there is no default template."

True, but internally IV is using a template file to output the imported geometry.

[bob_holland]

Bruce,

From what I am reading, this only happens after IT has to reinstall on someone's computer.

My guess it that your deployment is installing the default inventor Templates at the same location as all of your users are using.

I suggest that you check and modify your deployment(s) to install your Inventor templates into the default location:

C:\Users\Public\Documents\Autodesk\Inventor 2014\Templates

Please check this information and have a great weekend.

[Roelof.Feijen · Accepted solution]

The best workaround that I found for this issue: http://microconceptstechnical.blogspot.nl/2013/12/inventor-2013-templates-overwritten-on.html

[bruce.buck]

Sorry for the late response, but I wanted to make sure I had time to test the solution. On import of STEP files, and during a Shrinkwrap operation, it appears to maintain our coordinate systems from our custom templates, even though the app options are set to local. So far this seems to be working; I'll report back if anything else comes up.