How AutoCAD tools are distributed today

In most engineering offices tools travel by one of the four routes below. All four work — up to a certain number of people and a certain number of tools. This page is about where that limit sits and how you notice you have passed it.

Four routes, four limits

None of these is a bad solution; each one grew on its own because it solved a real problem. And each one breaks somewhere different.

Network share

A server folder is added to AutoCAD’s support file search path, and everything in it loads at start-up. Shipping a new version means copying a file into the folder — which is why this is the most common route of all.

The moment the share is unreachable, none of the tools are there: on site, at home, when the VPN drops. Start-up also grows with the number of files in the folder, and the folder only ever grows — nobody wants to be the person who deleted a colleague’s tool.

Email and USB

Whoever wrote the tool sends the new version as an attachment or hands it over in person, and everyone copies it onto their own machine. No installation, no waiting for IT.

Nothing anywhere records who copied which version. The person on leave that day never receives the message and keeps working with the old version for months. The gap surfaces when the same drawing produces two different results, and the cause is found days later.

Logon script

IT writes a script that copies the files when a user signs in. It is central, auditable and runs without anyone remembering to do it — of the four routes, this is the one with the soundest administration.

Every change now goes through IT. The engineer who wrote the tool makes the fix in ten minutes and waits three days for it to reach anyone — and by the third day nobody raises a ticket for small fixes any more. The tool stays broken even though it is fixable.

Hands-on, machine by machine

A new engineer starts, or a machine is replaced, and somebody sits down and installs the tools one at a time. It is the surest way to know the setup is correct.

It costs a day, and that machine is already behind a week later. The only record of what is on which machine is the memory of the person who installed it — and that record leaves when they do.

Four signs you have already passed the limit

None of these is urgent on its own, and each has a reasonable explanation. If all four are true, the problem is not the tools — it is the distribution.

You have to ask around to find out who has the current version of a tool.
Engineers disable their own tools so that AutoCAD starts faster.
Nobody touches a tool after the person who wrote it has left.
You have no record that could tell you how many machines a third-party add-in is installed on.

What this product does about it

Tools are packaged and signed; you decide who receives which package; updates reach the engineer’s machine on their own. AutoCAD makes no network call at start-up — packages are already local and load on demand, so start-up does not grow with the number of tools. When the server is down, installed tools keep working.

See how it works, in five steps

See it with your own tools

The demo takes an hour and uses your tools; it does not matter which of the four routes you are coming from. The pilot installation is free.

Request a demo