Are you sure kdm, gnome or another desktop was installed? You might be having trouble because (from your example, at least) you're trying to use the kdm desktop, when only gnome is available. (This shouldn't be a problem, because kde shouldn't be an option unless it's installed.)
My general reaction would be to call the technician back, and give him/her an opportunity to right their mistake. If they give you a hard time, stop payment on the check, see your supervisor, find a new tech, or a large brick to hit him/her in the head with. If someone else set up the system, the least you should expect is the ability to log in. If that's not working, then the tech isn't doing their job. If you get a hard time from that person, it's time to raise hell, in whatever way is appropriate.
One thing that might be a possibility, is that the tech doesn't "approve of" Linux. To some IT personnel, Windows is the "only way", and they see Linux as a way to stifle their qualifications. (It's bass-ackwards, but sadly true.) In other words, your tech might see linux as an excuse for management not to send him/her to those "valuable" Windows 2003 classes which the tech might see as necessary to their ability to find a better job.
Plainly put, for various reasons, your tech might want the Linux installation to fail. One thing that might make this obvious is the fact that they are still using 7.0, instead of a newer version. This is not necessarily true, but it's a consideration. (The tech might also view 7.0 as better tested, a legitimate reason.)
Basically, I'm suggesting that you should separate your tech from Linux. There's simply no good reason for this, and you need to know why it happened, and react accordingly. The hard part is separating incompetence from intentional undermining.