RE: Which support files should be located on the network?

[eleonard]

I am wondering what file paths I should NOT point to a network. I have messed my support file search path up many times and I am now trying not to mess everybody else's up.
My goal is to get as much information pointing to the network to ensure standards compliance.

What do you suggest?

Emily

[amy.stuart]

I am not quite sure what you are trying to look for in your support path. But the only network folder I have my support path locating is my "Drafting library" which contains my templates, blocks, and tool palettes.

I do have my template folder searching to my "template" folder in my drafting library so when i hit qnew (or the white sheet of paper) it goes directly to my company standard template.

[Mike.Perry]

Hi Emily

Please note I have *moved* this thread from the CAD Standards forum to this one, as I feel this particular forum is a more appropriate place for such a topic.

Thanks, Mike

Forum Manager

[Mike.Perry]

Hi

If you have not, try searching this actual forum - you should be able to find lots of helpful / useful information on this subject.

Example:

RE: Managing CAD Standards via Network

Setting up AutoCAD 2007 in a network environment

Have a good one, Mike

[Robert.Hall]

I am not quite sure what you are trying to look for in your support path. But the only network folder I have my support path locating is my "Drafting library" which contains my templates, blocks, and tool palettes.

I do have my template folder searching to my "template" folder in my drafting library so when i hit qnew (or the white sheet of paper) it goes directly to my company standard template.

I do the same, however, I am starting to question myself.
When the network is slow, AutoCad freezes up looking while looking for the
appropriate block files. It runs much faster if I have the blocks stored on the
local drive.

[jonathanschade]

I am going through the same thing. I have 85+ workstations that all have information on their local hardrives, that I want to me centralized.
If you rename the main directory of AutoCAD "Cocuments and Settings/User/Application Data/Autodesk/AutoCAD 2006/R16.2/enu/Support" and then open AutoCAD again, you will find that some of the folders have been re-built.
Currently I have just 3 files in my local Support folder - Commands.atc, Inches.pss and Shapes.atc. I know that the Inches.pss was re-built, and I think that AutoCAD asked for each of the other files.
I have take all of the other files and placed them on the network for centralized support.
I hope this makes sense and helps

[Mr Cory]

I put the two enu folders on the network (all users, users) <my 2 cents worth >

[madcadder]

Part of my job is to support our NJ, Chicago, and LA offices. To keep CAD standardized to the best I can.

I started out with everything loading from the server here in Tampa. Guess what? That was a nightmare. Imagine a 4K+ cad machine taking over 45 seconds for the FILE menu to display.

All this was caused by a DWT, a CUI & MNL, and 4 LSP files, and a few BMPs loading from here.
I tried it with syncing to their local on startup and shut-down for all but the DWT. Didn't fix.
Added the DWT. Didn't fix.
When I moved everything to an "AutoCAD Working Files" folder local to their machine and removed any network path I was finally able to see some normal speed.

So, What I learned is to load everything from the local machine and figure out a method to sync those machines as needed.

[Mr Cory]

The only delays we have is the cui command, opening the dia box take 20 sec atleast

[Mlabell]

I keep all plotting files, toolbars, cui(load lisp from central cui), blocks, palettes, and fonts pointed to the server. That way everything is easily controlled from my desktop. I then lock all the folders, and files giving me total control, and the inability for any variance from standard usage. I agree cui is brutal to load but that is an acad issue not server and should only occur the first time you enable the command after opening CAD. I have a user base of 20, and a server with a single drive at 100 Gb. Structure has worked pretty good here so far with minimal bumps.