I am building a linux system to send to a warehouse, the people at this warehouse for the most part will be using the cli. Usually when I do this I set them up in TUI mode and never give them a gui. they log in ( I replaced there shell with a menu of my own ) and they can run select things from a menu. Well, most of our software is now going to a GUI, so I have to provide them with kde or gnome. I have decided to use kde for this ( due to it being lighter weight imo then the new gnome 3 ). To give them access to legacy applications that are written for CLI, I have decided to give them putty. Here is my first question:
with putty I have created a desktop launcher that launches a ssh session based off a config file I have found in my home directory. I would really like to not have to copy this file to every users home directory to give them this ability ( desktop launcher in kde). Is there somewhere that KDE lets me save these configuration files, that apply to all users ? ( if I need to expand more on this let me know).

Remote desktop, Same basic deal. I am using vncviewer to connect to the machines, but I would like to have access to the users desktop sessions. I can enable remote desktop easy enough, but I would not like to have to have a new user configure remote desktop settings there self ( ie if a new user is added to that system the remote desktop settings are off by default I would have to walk the user though setting it up, as well as having them use a password. I do not want to give them the availability to access there own desktops from home..) is there some default location I can set these settings and have it apply to all users ???

Any answers, tips, points in the right direction would be awesome thanks.

If I were you, I'd use a script on login that pulls the config data from shared storage. Here's a nice howto: http://www.linuxfromscratch.org/hint...s-with-kdm.txt Lots of ways to do this.

Another alternative is to mount home as a network share.

You could go full thin client and run the host as a bootp client. Yeah, that reboot will take a while, but you'll have total control over the user experience from a centrally located disk image.

How are the users being authenticated? Local or some kind of centralized auth setup?