? If your multicasting, network congestion shouldnt be an issue (assuming that you are putting the same image on all machines), right? Or am I missing something here?
________________________________
From: [EMAIL PROTECTED] on behalf of Brian Desmond
Sent: Fri 7/16/2004 11:13 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Summer Maintenance
You got it Steve. I don't know if you've ever done this before, but be prepared to
have a handful of them screw up and need reimaging with a floppy disk. Also, don't
think of doing em all at once. 100 - 150 is enough to saturate your network.
--Brian
-----Original Message-----
From: Steve Rochford [mailto:[EMAIL PROTECTED]
Sent: Fri 7/16/2004 8:08 AM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [ActiveDir] Summer Maintenance
I love comments like "The result is that as the imaged computers are
powered up, the admin will type in each unique computer name and walk
away."
We're re-imaging about 1000 student computers this summer and I'm not
intending to go anywhere near most of them so typing in anything is a
no-no! As others have said, Ghost will happily rename and join to the
domain and it will also work with sysprep so you can have the best of
both worlds :-)
Steve
-----Original Message-----
From: Brad Corob [mailto:[EMAIL PROTECTED]
Sent: 15 July 2004 05:00
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Summer Maintenance
2) Regardless of how you image the computers, using sysprep is the
*only* supported way of using imaged workstations on a network. Look
into it if you haven't used it. I find it quite simple to use and
extrememly
effective. The sysprep process can be automated. I typically find it
most
useful to automate all of the mini-setup answers except for computer
name.
The result is that as the imaged computers are powered up, the admin
will type in each unique computer name and walk away.
You can also join a domain during the sysprep process (automated or
not).
One caveat here is the default 10-computer limit each user account can
create in AD ("but it worked fine when we tested it!"). The suggested
method is to create a designated account for Sysprep imaging and
delegate the appropriate rights to your Computer OU's.
If joining the computer to the domain during sysprep doesn't work for
you, you can also script the process. Technet gives an example script
here:
http://www.microsoft.com/technet/community/scriptcenter/compmgmt/scrcm31
.msp
x
but MSDN actually documents the WMI method here:
http://msdn.microsoft.com/library/en-us/wmisdk/wmi/joindomainorworkgroup
_met
hod_in_class_win32_computersystem.asp
Particularly helpful is the AccountOU parameter, as it will allow you to
specify the OU in which to place the computer object to further ease
your post-deployment admin tasks.
[The script method works wonders in large deployments when you can't
join a domain during the Sysprep process, for example, if this
particularly vexing, poorly documented, almost-12-month-old and
as-yet-unfixed "issue" plagues your environment like the spawn of Satan:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086130.htm
No, I'm not bitter. Not one bit.]
-Brad
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
<<winmail.dat>>
