1 / 13

Midnight in the Garden of Good and Evil

Midnight in the Garden of Good and Evil. David N. Blank-Edelman <dnb@ccs.neu.edu> Director of Technology College of Computer Science Northeastern University. Credit. significant parts excerpted from CCS MicroNet: Past, Present, Future

jaunie
Télécharger la présentation

Midnight in the Garden of Good and Evil

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Midnight in the Garden of Good and Evil David N. Blank-Edelman <dnb@ccs.neu.edu> Director of Technology College of Computer Science Northeastern University

  2. Credit • significant parts excerpted from CCS MicroNet: Past, Present, Future presentation in progress by Jeff Carpenter, Microcomputer Network Administrator, CCS. • title from book by John Berendt

  3. Why NT? • NT was touted as being more robust/secure than 95 (and MS urged us to go this way) • had sufficient resources & MS support for this effort • Pressure to teach using latest GUI (textbooks already ordered)

  4. Things Working Against Us • had to deploy fast, sans reasonable documentation or testing time • had to deploy in a hostile user environment • had to deploy NT 4.0 before MS had shaken bugs out or ramped up their support • little direct experience with NT prior to deploy (with small staff) • initially did not use “master image” model, forcing modifications to be done by hand • facilities in use almost all the time, had inadequate maintenance/repair access time

  5. CCS MicroNet I

  6. MN1: Problems We Encountered (1) • ab(users) and barricades • user accounts • did not attempt UNIX integration or using painful GUI to enter 1200 accounts • attempt 1: sequence #’s • file permissions & user training

  7. MN1: Problems We Encountered (2) • user accounts (cont.) • attempt 2: single login • server performance/inconsistent machine state • all “users” must be off to make changes • the Registry is not your friend • poison pill • lack of tools • performance problems w/Mac services

  8. What Worked Interactive Machine Building Local NT Printing Services Remote User Authentication What Didn’t Work Non-Lab Printers Remote Profile Access (slow) Automated Machine Building/Re-Building Automated Software Updating CCS MicroNet I

  9. CCS MicroNet II

  10. What Worked LPR Printer Service Automated Client Re-Building Default + Client Registries DHCP FAT Partitions What Didn’t Work Non-Group Accounts Domain Wide Administration Component-ized Registry Segments Remote Administration CCS MicroNet II

  11. CCS MicroNet III

  12. What will work Local Group Accounts Network User Accounts/Profiles Automated Building/Re-Building LPR Printing Centralized Administration CCS MicroNet III • What Will Work • Remote Administration • Multiple Architectures • Multiple Hardware Models • Scaleable • Adaptable

  13. Future Directions • UNIX/NT account & storage integration • Sun NFS • Samba • Messaging • Perl

More Related