Accounts

    * Created from out database
    * Data from the registrar: UP TO TWO-DAY DELAY FROM REGISTRATION TIME UNTIL THE ACCOUNT IS ACTIVE
    * Only registered regular students get accounts 
    * Only for classes taught "in" CS -- excludes 310

Passwords

    * Minimum 8 characters
    * Minimum 3 character classes
    * Please teach your students to pick a good password 

Printing

    * Printers in 1359
    * Student paper quota: 150 pages/class
    * Consultants/TAs fill the printer with paper 

Rosters

    * Class rosters in /p/course/rosters
    * Only accessable to the instructor and the instructor's "-tas" group (e.g., hasti:cs302-tas)
    * We don't manage the -tas group 

Class Mailing Lists

    * If requested by the instructor, managed by DoIT
    * Use CAMPUS email addresses, not the CS email addresses
    * Archives on our web server, if configured to include lists@cs.wisc.edu 

Newuser (activating new accounts)

    * Windows: Use the "New User" login button
    * Unix: Login as "newuser", password "newuser"
    * Only once per account
    * AFTER we have the registration data 

Unix Orientation Sessions

    * For new unix users
    * Only need to attend one session
    * Includes running newuser, minimal orientation to unix 

Windows XP:

    * AFS drive mappings:
      k:   /afs/cs/i386_winxp   
      p:   /afs/cs/p   project space
      s:   /afs/cs/s   software
      w:   /afs/cs   cs.wisc.edu afs root
      u:   current user's AFS home directory
    * login panel
    * windows profiles
    * screen locking (bathroom breaks) 

Handin Program

    * 302 has their own handing program
    * CSL supports a general-purpose handin program for other classes 

Good Problem Reports

    * the name of the computer
    * the user's login name
    * what program
    * what error message (exact, if possible)
    * what input files (what directory)
    * when it started to fail
    * when it last worked, if ever
    * what the user changed?