NT Installation Overview

Background

The purpose of this page is to hopefully summarize the steps required to set up a system to automatically distribute NT and Apps in the DTCC student (and possibly staff) labs. More detailed information about a lot of this is available in disjointed format in links from the main NT Implementation Page.

One of these days hopefully I'll fill this in with more info and links so it will all be clearer. It's mainly a skeletal structure now so I don't forget how I got to here!

Oh, by the way, you may want to implement this in stages, to test everything. That's what I did when researching it all. Get a simple unintended install working, then start slowly adding lines to Cmdlines.txt as each portion is proven to work.

How to

Files in $OEM$ directory

$OEM$\Cmdlines.txt items

[Commands]
".\net user administrator whatever"
"cmd /c %Systemroot%\i\preboot.cmd"
Password above is obviously not correct and used as examples! :)

$OEM$\i\apps.cmd

Be sure to make an account "uinstall" valid under NT and UNIX and give it the same password and note that password in apps.cmd file instead of "whatever."

Be sure to configure the custom\custom.lst file with NIW in office resource kit before letting below run.

./net use x: \\hopi\off97 /user:uinstall whatever
x:
setup /L custom\custom.lst /B2 /Q1N
c:
./net use x: /del

$OEM$\i\acls.cmd

Use file in ZAK at "\ZAKAppDist\netsys\i386\$oem$\$$\zak\scripts\ directory as a template. Copy "Yesfile" from same directory. Then make following changes to acls.cmd: Note that this file can change often as needs are encountered. See actual file for comments and commands.

Files parked in $oem$\C structure

None yet.

Files parked in $oem$\$$ structure


Last page update: 03 January 1998
Official URL for this page: http://www.stanton.dtcc.edu/stanton/cs/admin/nt/notes/overview.html
Page Maintained by: Ken Weaverling