Author Topic: Custom Autocad Installations  (Read 395 times)

0 Members and 1 Guest are viewing this topic.


  • Mosquito
  • Posts: 1
Custom Autocad Installations
« on: February 16, 2019, 01:20:13 AM »
Hi everyone. 

We would like to mimic the way autocad is setup from certain computers to others.  If anyone has experience with this can you offer some input?

Could we just copy the files in the Autodesk main program directory to another computer and would it work okay? The computers are different.



  • Bull Frog
  • Posts: 286
  • 30 + years of using Autocad
Re: Custom Autocad Installations
« Reply #1 on: February 17, 2019, 05:22:44 PM »
There are a number of methods, we use a lisp that has all the paths, printers and loads correct menus and toolbars. Just copy files may  not work. Our files are held on a server not local. You may want to look at Config, Profiles and make an ARG file which you can import on another computer.
A man who never made a mistake never made anything


  • Seagull
  • Posts: 14442
  • Every Student their own Lesson
Re: Custom Autocad Installations
« Reply #2 on: February 18, 2019, 09:13:21 AM »
User Profiles as suggested, or cloning a virtual machine...
Be your Best

Michael Farrell


  • Swamp Rat
  • Posts: 1439
Re: Custom Autocad Installations
« Reply #3 on: February 18, 2019, 09:29:02 AM »
Network hosting of the CUIx and lisp routines is highly beneficial. This allows all users to be on the same settings and basic setup.

One tremendous downside....when the network is down and if AutoCAD is opened or a drawing is opened it will unload all of the customizations. A sure fire method would be to have a network hosted setup with a routine that parses for updated files and then locally copies them.


  • Water Moccasin
  • Posts: 2392
Re: Custom Autocad Installations
« Reply #4 on: February 18, 2019, 02:05:34 PM »
IMHO, if the network is down you have bigger problems.

Another benefit from network located files is that it provides some protection against the acad.lsp/vlx type viruses (provided the location is read-only).
If you are going to fly by the seat of your pants, expect friction burns.

try {GreatPower;}
   catch (notResponsible)