7 replies
by cfburgess
Just some thoughts in no particular order.
Installed user base - Try to get users to begin moving "critical files" to a standard location on their machines. Maybe some form of query about the apps actually being used.
Deployment - If possible, push the vendor to provide as much preconfiguration as possible. Turning one on and simply adding a machine name and user is better than building each from scratch. If you can't get vendor buy-in, then, assuming win2k, learn all you can about machineduplication (ghost,pqdi) and sysprep (check mskb). There have been several articles and threads about this lately.
by jeffva
by toltec58
I have worked 2 jobs in the past few months rolling out Win2K workstations for the state of PA. The 1st job used Ghost to replicate in the warehouse before shipping to site. It didn't work well. Best senerio is doing unnatended installs from a network drive.
Have your users save their files to network drive or the desktop. Let the techs export your e-mail client adresses and preferences, etc.
Time tables depend on configs.
by jeffva
by charley
My experience has taught me that the best way to do something like this is to be EXTREMELY methodical. I have a procedure that I use because it works FOR ME. The important thing is to figure out what works for you and run with it. Having said that...
1)FDISK and format the HD on the first new machine you get. Do a BRAND NEW, clean OS (I assume you are using Windows) install. Do all of your configuration building here. Install updated drivers, current DirectX (if necessary) and all of your desktop applications.
2) TEST TEST TEST TEST ad infinitum. you can't test too much. Make SURE that it works.
3) Create and installation image from your KNOWN WORKING machine. I use Symantec's Ghost5, but there are others out there. I use ghost because I've been using it since it was Ghostsoft and I know how to use its command line parameters to do an unattended install.
4) Based on availability of equipment and network configuration, you can: a) burn the image to a CD, along with the necessary imaging software, and use a boot floppy with appropriate command line paramters to do the install. b) put the image on a network server and use a boot floppy, c) use a hard drive duplicator.
5) Correct system settings for individual users.
Voila...you have now deployed your workstations with little or no hassle.
by jeffva
by jeffva
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending