Easy win2k install on 20 computers (with same configuration)
Hi, I got to install on 20 computers with the same configuration win2k. Witch is the easyest way to do this? Thanks. . . .
Hi,
I got to install on 20 computers with the same configuration win2k.
Witch is the easyest way to do this?
Thanks...
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Depends on your environment. If you have Active Directory, then use a combo of Sysprep (similar hardware) / Syspart (dissimilar hardware) and RIS.
If not, then use a deployment solution such as Ghost, Altiris, LanDesk, ettcc
Build the image, install the software, test the software, build a default profile, test again, image the master machine, and then deploy.
If not, then use a deployment solution such as Ghost, Altiris, LanDesk, ettcc
Build the image, install the software, test the software, build a default profile, test again, image the master machine, and then deploy.
Symantec Ghost and SysPrep.
Possibly Remote Installation Services (RIS) too.
[edit] hehe, I see DS3 has beat me to it [/edit]
Possibly Remote Installation Services (RIS) too.
[edit] hehe, I see DS3 has beat me to it [/edit]
LOL
French roast coffee makes me move fast
French roast coffee makes me move fast
If all 20 PCs are exactly the same spec, it's probably easiest to install one locally with all the drivers, apps etc. and then use Ghost to copy to all the other machines (bear in mind you will still need to go around and give each machine a unique name on the network). The advantage of using Ghost (or whatever) is that each machine on the network looks and works identically (in theory).
If you keep a copy of the Ghost image, it's also useful when a machine starts misbehaving - just reimage the machine and hey presto! It works again - most of the time!
Rgds
AndyF
If you keep a copy of the Ghost image, it's also useful when a machine starts misbehaving - just reimage the machine and hey presto! It works again - most of the time!
Rgds
AndyF
Originally posted by AndyFair:
Quote:If all 20 PCs are exactly the same spec, it's probably easiest to install one locally with all the drivers, apps etc. and then use Ghost to copy to all the other machines (bear in mind you will still need to go around and give each machine a unique name on the network). The advantage of using Ghost (or whatever) is that each machine on the network looks and works identically (in theory).
If you keep a copy of the Ghost image, it's also useful when a machine starts misbehaving - just reimage the machine and hey presto! It works again - most of the time!
Don't forget
new machine SIDs, too.
Quote:If all 20 PCs are exactly the same spec, it's probably easiest to install one locally with all the drivers, apps etc. and then use Ghost to copy to all the other machines (bear in mind you will still need to go around and give each machine a unique name on the network). The advantage of using Ghost (or whatever) is that each machine on the network looks and works identically (in theory).
If you keep a copy of the Ghost image, it's also useful when a machine starts misbehaving - just reimage the machine and hey presto! It works again - most of the time!
Don't forget
new machine SIDs, too.
If ghost is the desired solution then http://service1.symantec.com/SUPPORT/gho...v=&osv_lvl=
Altiris, IIRC, uses Sidgen.
And SID maintenance is done the MS way through sysprep, which I should mention is the only supported method.
Altiris, IIRC, uses Sidgen.
And SID maintenance is done the MS way through sysprep, which I should mention is the only supported method.