I agree with Pieter about the pgp file. Let the users use there own, they are more productive that way and a line is a line, no matter what you use to call the line command. The good thing about autocad is that there are many ways to achieve the same thing...
The other thing to consider is files that are shared by all users, standard (templates, blocks, etc...). Put them on a network somewhere and control the order of the search paths on each users computer. Build and use profiles as an easy and consistent way to deploy the same information to each computer. Therefore when something needs correcting/updating you correct it in one location and everyone gets it at relatively the same time. However plan your directory structure in advance (with rhyme and reason...) if possible with future growth in mind. Once you have your directory structure and files in place, restrict the permissions on who has access to this area from a "write" perspective.
Training goes a long way in providing the person the ability to make knowledgable choices about the way they draft. If your users understand the system and understand the way they do work, they will start asking "Can you write a program to do this repetitious task?"
Some users will draft sloppily out of ignorance (these people are trainable) and some will do sloppy work out of pure laziness (run as far and as fast as you can away from these, they are usually the brown nosers). Know the difference... and don't waste your time.
Of course above all, be a change agent... People don't want to change anything unless they a) Know how it will effect them and b) What's in it for them.
Let them know upfront how these changes will help them with their work processes. Happy trained users make the life of a support person so much better because then you actually have time to write some programs, maybe?
