Lock CUI
As in CUIx content (workspaces)? Set the CUIx as Enterprise and keep it in a network location with limited rights.
As in Options dialog settings (system variables)? Create an initialization procedure called by an ACAD.lsp file, again located in a network location with limited rights. Of course, some of those are per-drawing which will need to be dealt with as well.
Either way there will be ways for clever users to get around it. The best implementations will make using them almost transparent such that its much more convient to do it right than to do it wrong.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
Accepted solution
Essentially correct. You may need to add partial CUIx files to the one you are using as Enterprise to support various things like the OOTB AutoCAD and Express tools functions.
Each user should have their own Main CUIx stored on their computer or a personal folder on the network. That will allow them to save their personal workspace settings e.g. Properties docked left instead of floating right; Layers floating right instead of docked left, and so on. You can force them to only use the workspaces you have defined in the Enterprise, but that creates a LOT of grumbling.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
Great advice provided by everybody previously! We essentially use the custom.cuix for the user and a business unit.cuix for the enterprise. Loaded into the Enterprise is the standard acad.cuix, acetmain.cuix etc which makes the OOTB cuix's read only.
Your clever users will learn quickly that if the load the enterprise as the main they can then edit it, one edit will the effect all referencing.
Just a thought but what about hosting the CUI's on a shared network location in a folder where users only have read options and no write. Then even if the switch the enterprise and main they still won't be able to edit it.
You could then look at DFS as a replication solution for your standard content and share from one master location to all, this will aid the update process.
To load everything, we then use a drag and drop LISP that loads a profile on demand, preconfigured for AutoCAD. This loads the cuix's needed and writes to the custom.cuix a copy of the master workspace to the custom.cuix, essentially it's a copy of the master which is editable. If that were to become corrupt, select the master which is read only and overwrite that for the user workspace.
Your clever users will learn quickly that if the load the enterprise as the main they can then edit it, one edit will the effect all referencing.
Just a thought but what about hosting the CUI's on a shared network location in a folder where users only have read options and no write. Then even if the switch the enterprise and main they still won't be able to edit it.
You could then look at DFS as a replication solution for your standard content and share from one master location to all, this will aid the update process.
To load everything, we then use a drag and drop LISP that loads a profile on demand, preconfigured for AutoCAD. This loads the cuix's needed and writes to the custom.cuix a copy of the master workspace to the custom.cuix, essentially it's a copy of the master which is editable. If that were to become corrupt, select the master which is read only and overwrite that for the user workspace.
