Advice required for training room setup

[green biro]

Hi all.

I wonder if anyone could advise a 'best practice' for the following scenario
or point us in the direction of a good 'deployment' document.

We have a training room with a master trainer's PC and 12 student's PCs. We
would like to maintain two images in order to train on either Software A or
Software B. Both these images will need regular updating as the
manufacturer is continually releasing patches for the softwares and it is
imperative that we train on the latest versions.

All the student machines require network access because students need to be
able to connect to their email and other network resources.

Ideally we would like to have the following 'procedures' available to us.
- Restore trainer's machine to latest Software A image, run patches and
updates and save new Software A image.
- Restore trainer's machine to latest Software B image, run patches and
updates and save new Software B image.
- Restore all student machines from latest trainer's software A image and
reset IP addresses / computer names and rejoin network
- Restore all student machines from latest trainer's software B image and
reset IP addresses / computer names and rejoin network

Our engineers who have Norton Ghost at their disposal tell us it can't be
done because of problems with SID. We would be surprised if this was a
complete showstopper - hence the request for guidance.

Thanks in advance for any assistance.

GB

 

[Dusko Savatovic]

Hi GB,

I'm working in a Learning Solutions division of my company and here's what
we do:

1. Get good PC's that open easily. We use PC's housed in HP CMT (Convertible
Mini Tower) cases. Each PC is equipped with two HD's. However, only one HD
is powered during the course. The other HD has power cable disconnected.
This enables us to have two configurations because sometimes we run two
courses per day (morning and afternoon/evening shifts). It typically takes
less then 10 minutes to switch configurations in a 12 seat + Instructor
classroom. Of course, HD's are set for cable select master/slave settings.
BTW, you can use toggle switches to toggle power to HD's, but you need to
custom build them. I did that for PC's we used previously.

2. Symantec Ghost Enterprise edition is a great tool and we use it.
Especially because of it's multicasting (Ghostcast server) capabilities. To
address SID problem you have several solutions:
a - sysprep machines before taking images. This is recommended by Microsoft.
b - use freeware Newsid from www.sysinternals.com
c - use ghstwalk.exe that comes with Symantec Ghost.

3. To address software updates, you can use several solutions:
a - another component of Ghost, it's called AI (AutoInstall).
b - WinInstall LE - free from
http://downloads.ondemandsoftware.com/download/installs/wininstallle.exe
c - Windows Server 2003 Active Directory - Software Installation policy
d - some other commercial product.

4. To address IP addresses:
a - use DHCP service in your Windows Server 2003.
b - use script. You can change IP address with netsh command and have this
command in a simple batch file.
Here are some examples:

File:SetAutoIP.vbs
==========
' Sets IP address for
' automatic Ip configuration. Runs:
' netsh -f AAA.txt

Set WshShell = WScript.CreateObject("WScript.Shell")

WshShell.Run "netsh -f AAA.txt", 1, true

==================
File:AAA.txt
======
pushd interface ip

# Interface IP Configuration for "Local Area Connection"

set address name="Local Area Connection" source=dhcp
set dns name="Local Area Connection" source=dhcp register=PRIMARY
set wins name="Local Area Connection" source=dhcp

popd
# End of interface IP configuration

=========
File:SetIP.vbs
=========
' Sets IP address for each computer in the classroom
' To revert back to automatic Ip configuration, run
' netsh -f AAA.txt

Set objNet = WScript.CreateObject("WScript.Network")
Set WshShell = WScript.CreateObject("WScript.Shell")

CompName = left(UCase(objNet.ComputerName), 3)

Select Case CompName
Case "LON"
WshShell.Run "netsh -f LON.txt", 1, true
Case "GLA"
WshShell.Run "netsh -f GLA.txt", 1, true
Case "VAN"
WshShell.Run "netsh -f VAN.txt", 1, true
Case "DEN"
WshShell.Run "netsh -f DEN.txt", 1, true
' Add as many names as you wish
Case else
WshShell.Run "netsh -f AAA.txt", 1, true
End Select

============
File:LON.txt
============
pushd interface ip

# Interface IP Configuration for "Local Area Connection"

set address name="Local Area Connection" source=static addr=192.168.2.200
mask=255.255.255.0
set dns name="Local Area Connection" source=static addr=192.168.2.200
register=PRIMARY

popd
# End of interface IP configuration
=========================


5. We also use a lot of virtual machines. Sometimes Microsoft VPC and
sometimes VMWare. They both work great.

HTH
Dusko Savatovic