Thanks for your input Glen. This script it self is in it's infant stages and this is where I appreciate the input of those that use kix on a much regular basis.

I would like to note on a couple of things because I wasn't clear at all in the initial post.

Drive Mappings: Right now every one gets the M: drive because right now it's assumed that they would not cross departments. Yes there is this possibility, but for right now this script just assumes they are not crossing departments. I figured before I had to invent the wheel on that I would figure out how many users needed access to other department shares and work with it at that point.

Screen Resolution: We have a new app that needs to have the screen resolution set, but not forced on to where the users can't change it. After a few hours of research I noticed a lot of people's pain by forcing on a screen resolution and the push they got back from the end user community. Our plan is to get the user the optimal work environment first and if they have to change the resolution for whatever reason it falls on them to make sure all of their work is completed accordingly

Application Installation:

I think the more I learn about kixtart the more that this will evolve into what your suggesting. A centralized file server with scheduled tasks to install the client software at a more appropriate time. Or an email to IT staff letting them know that this machine does not have this patch installed. Get a hold of the user and do it when it's appropriate.

Other Items:

I'm not sure what you mean by the training PCs. We have a set of training PC's that I want a certain things to happen while anybody is logged into them. I guess what I'm wondering is how could i do it different / better than $training = @hostname? They are on the same domain as the rest of my machines, so again just looking for advice.

Thanks again!