ACCOUNT ISSUES RELATED TO KERBEROS CHANGEOVER
                                       
   Below are steps for the op's to use in resolving account problems.
   First there are four types of problems related to the transition you
   could face, these are:
    1. The user did not read the /etc/issue file on umbc7 and is not
       using the kerberos password set up for them. Look at the section
       on Getting people to read the login messages
    2. Another problem may be that the username on umbc7 did not exist in
       our ph account database. If that was the case we did NOT setup
       the account to work. In this case we want to verify the user is a
       legitimate user and add them to the ph database. A list of
       accounts with this problem is here.
    3. None of the above. In that case take down the following
       information: umbc7 account name,daytime phone, and ssn. Mail that
       information to systems@umbc.edu and one of the full time staff
       will handle things.
    4. The user is able to log in but is not able to change their
       password when prompted. In this case the problem is either they
       are not entering in the proper "old password", they should use
       what they just entered to get logged in, or they can't come up
       with a valid new password.
       
Steps to use when diagnosing a problem.

    1. Verify the username does not show up on this list . If it does,
       then jump to the section. below on what to do when no PH entry
       exists.
    2. Look up their ph entry on umbc4, determine if the inst_created
       date is prior to 8/15/94. If so, tell the user to try their umbc8
       password. If they do not know thier umbc8 password you may use the
       kadmin to reset the password.
    3. Otherwise If the inst_created date was 8/15/94 or after, or if
       they don't have an inst_created field tell them to try using their
       SSN.
    4. If that doesn't work then send a message to systems. giving the
       account name, ssn, and daytime phone number where the user can be
       contacted at. One of the systems staff will contact the user
       
What to do when no PH entry exists If no ph extry exists for the user they will
have to manually be added. Send a message to systems. giving the account name,
ssn, and daytime phone number where the user can be contacted at.

  NOTES TO SYSTEMS ON ADDING THE USER.
  
Once the user has been authorized to get an account by jack or stephanie you
need to get the UID number assigned to that user in the /etc/passwd file on
umbc7. Use the command grep username /etc/passwd, the UID is the third field,
just to the right of the password field containing an asterisk. With the uid,
ssn, and name we can go forward.

    1. Sign onto umbc4
    2. run the ~asa/bin/register script as you would a new user. Enter in
       the SSN and name. Then for account type select Research. After you
       enter "y" to proceed you will be asked if this is an existing
       research account, if so, you will be prompted for the uid and
       account name to use.
    3. After registering the user, run the kadmin program to change
       their kerberos password to their ssn, this can be run from any
       kerberos based machine, including umbc7.
    4. From umbc7's console, run the script /usr/site/etc/forcepassword
       username