Originally Posted by
Coloradomrg
On our server I have a folder called "ACAD Program Files". Within that folder are many other folders with specific jobs. Only myself and the system admin have write access to this folder, others can only read. The permissions are set through windows user profiles. Similar to the link you quoted, I author tool palletes and revisions directly to my tool pallete folder on the server, and everyone else has their tool pallete location directed to this folder. I keep all files that are needed for the office on the server. Blocks, lisps, .pc3 and .ctb files, fonts, etc... This ensures that everyone has access to the same information all the time, but only I have write permission to this "company" information.
I do something similar, but go a step further by also incorporating user-customizations located on user's personal network space which is linked to their Windows profile.
Even our CUI setup incorporates these user-level customizations (i.e., workspaces, etc.), so that when someone hops into a meeting in the conference room, and logs into the laptop, all of their personal settings, and customizations are made available, regardless of location (or even which office they're in).
To keep the user's LISP customizations simple, we just:
Code:
((lambda (user / file)
(if (setq file (findfile (strcat user ".lsp")))
(load file)
)
)
(getvar 'loginname)
)
Some additional goodies are included for laptop users like myself for Offline Files, etc..