Maint SU program to allow new computers on the production floor

[smuthcrmnl777]

I would like to create kind of a setup program for my maintenance dept so that when a new computer is issued for a production line they can easily set up the computer without going to me or IT for help.

What I would like to do is have maintenance pick up the computer that needs to be set up and set it on his desk. Take an USB to USB cable and plug the new computer to his desktop. After the computers recognize the new hardware he should run this program from his desktop.

*******
Things I would like this program to do, but not sure if it is possible

Have the program automatically detect a new computer connected?
Can change the computer name of the new computer from the desktop?
Edit a couple of text files.

********

If all of these are possible, I would then create a simple VB program that the maintenance guy would run from his desktop that would simple ask him what is the Line name of the new computer. After doing this, the VB would change the name of the computer and edit the text files to accomodate the changes.

If anyone has any suggestions, I am willing to hear them. If you can offer just bits and pieces to this project, please offer. Everything is much appreciated.

Thank you very much!!

 

[ncotton]

This is possible, but its not straight foward, you should be asking this in the programming forum.
You also need to think about what state is the computer going to be in when this is going to be run. Will windows be pre-installed? Does it need to join a domain, how are the OUs structured. As I say, its not going to be a simple program you are going to have to use a lot of predefinned constants, unless you know how to use resource files and libraries.

and I recommend C# for this kind of thing, not VB.

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[smuthcrmnl777]

I have a ghost file that I run on every new computer that comes in to the shop. It loads everything I need including the programs and files associated with it. I also name the computer something that will never happen in that particular department. It has the Windows Operating system on it and it will not join a domain, but it allows Administrators to share files and folders.

 

[thefourthwall]

have you considered an application such as LANDesk? We use it here with the APM or automatic policy manager (hope i've got that one right)that, after loading a generic ghost image, allows the user to choose what programs he/she needs installed (the APM installs the choices authenticating as the local SYSTEM account).