I copied in notes from the help file, just to aid me in future editing ...
I do the same thing but I place this code in a external file and then have that file loaded through the user's ACADDOC.lsp file by the use of the StartUP function; allowing me to change and add system vars in one place at anytime that I need to. Just by doing that has cut my cad management headaches in half.
we have our cui's pointed to a unc path for our lisp files that are part of the enterprise cui.... so that me or my buddy can fix stuff on the fly this also prevents the need to "push" stuff to end users, although i'd like to know how to do that....
anyways.
Check out this thread by Se7en. I think that is what is he teaching. I don't know, at times it is all Greek to me.
I set my office up similar to what butzers09silverado describes (keep as much stuff on the network as possible) but i do still have to install some things like updates to custom company software, replace a DLL, or even install new or updated programs, i need the power that an installer offers; sometimes a BAT or LSP file just doesn't cut it.
NSIS (that link) is an installer compiler (It makes installers). I use the NSIS installer language to write a "program" which i compile into an installer (You know what an installer is, Its the thing you download when you want to install a program...it asks you all those annoying questions like: do you agree, install this or that component, install this here, etc., etc.).
Does that help make `it' less `Greek'?