What Install Data Needed to Sync Between Campuses

Background

Stanton and Wilmington use separate local servers to handle unattended installs for obvious performance reasons. To keep things as simple as possible, most files should remain identical on each server. Therefore if editing ainstall.cmd on one server, for example, it should be duplicated on the other, even if the option being added is for a single site only.

However, there are a few files that refer to campus specific stuff and need to remain unique.

Currently (as of Jan 2000), Stanton's install server share is \\fortress\setupnt and Wilmington's is \\citadel\setupnt

Campus Specific Files

• $oem$\$$\timeserv.ini
  Points to closest ntp server. Campus specific
• $oem$\$$\postboot.cmd
  Should remain identical except for "NET USE" commands which should share the closest install server.
• $oem$\$$\i\servars.reg
  Defines %homebox% var, which should point to local samba server
• $oem$\$$\i\setupdir.reg
  Defines what local host NT setup files are located on.

Campus Specific Directories

• ie\standard\
  Containts standard installation of INternet Explorer 5. Generate this with the IEAK and store here. Campus specific information includes what campus config file (.ins) to read off of web server, bookmarks, etc.
• ie\library\
  Campus specific restricted library IE install. Generate it with IEAK.

Last page update: 05-Jan-00
Official URL for this page: http://www.dtcc.edu/cs/admin/nt/sync/
Page Maintained by: Ken Weaverling