UWNetIDs

There are many options for using UWNetIDs and "centrally" maintained passwords with Windows. However, where possible we recommend using the UW Windows Infrastructure (UWWI).

Additional options are summarized with further details given below. Neither of them is the definitive solution and each has limitations. In addition to these valid options, you may notice in the UW forest, or have heard of, what seems to be another option: the labs domain. This domain has a specific purpose associated with the central computing labs and use outside of that purpose isn't supported. The labs domain has an end of life set for July 2007, and has been replaced by the UW Windows Infrastructure service.

Summaries

• UW Windows Infrastructure
  • Windows account has UWNetID password.
  • Only requires a trust to UWWI.
  • Authorization groups tied to UWWI user accounts that are auto-provisioned from institutional data. These include groups based on affiliations (e.g. student, staff, faculty), and course groups.
  • No ability to manage UWWI user accounts at this time.
  • For more details
• Kerberos realm trust option
  • Setup does NOT require UW Forest membership.
  • Authentication won't work for ALL services.
  • Users have two DISTINCT accounts and passwords (local domain and UW NetID, but only need to know about their UW NetID.
  • There IS an account per each user in your local domain.
  • For more details
• Scripted account creation
  • Setup does NOT require UW Forest membership.
  • DOES require your own IIS server (unless you modify the example script).
  • The example script creates accounts in your local domain.
  • For more details.