UW Windows Infrastructure User Support
This document describes how IT support personnel can view and manage UWWI users.
The UW NetID service has recently added a new IT Support Org
functionality to help support new UWWI user delegation features. This
new functionality allows IT support groups to designate a UW NetID as an
IT Support Org, associate Computing Support Staff with this IT Support
Org, invite relevant UW NetIDs to be supported by them, and then view
and manage UW NetIDs which have accepted the invitation to be supported.
This new IT Support Org functionality has lots of room to grow, with
known limitations like no programmatic access, but it does move us
Note that the
UWWI User Limitations document describes limitations that this new
functionality does not override.
Note that there are some
workarounds to setting some UWWI user attributes which may be
- Contact the UW-IT Help Desk
and let them know you'd like to
get an Computing Support Org setup,
in association with a UWWI
Delegated OU. You can find out
more about UW NetID Computing
Support Orgs at
If you have an
existing shared UW NetID which
you use for departmental IT
support (e.g. a shared email
address that users send help
requests to), you can add the
Computing Support Org functionality to
that existing shared UW NetID.
Otherwise, you can request a new
UW NetID that will be your
Computing Support Org. The UW-IT Help
Desk will gather some basic
information from you to complete
creating the Computing Support
including the name of your UWWI
Go to the UW
NetID Support Dashboard and login with your personal UW NetID (*NOT*
your admin UW NetID). Only your personal UW NetID is capable of
performing 2 factor authentication, which some of the features of this
tool will require.
Note: you should see your UWWI
delegated OU listed on this page. If you don't see it listed, then the
process of setting up the computing support group is incomplete, and you
should contact the UW-IT Help Desk again.
You can edit the OU admins, GP admins,
and Computer Joiners associated with your delegated OU from this page,
instead of sending change requests to UWWI Engineering.
Choose the edit link to the right of your Support Org name. Add the UW
NetIDs of Computing Support Staff who should be authorized to view and
manage the UW NetIDs that accept your invitation. These UW NetIDs will
need 2 factor authentication, so if you add any UW NetID which doesn't
currently have this ability, you should start the process of getting it.
Only add personal UW NetIDs, not admin UW NetIDs.
Note that on this edit page you can also permit non-employee UW NetIDs
to be eligible to get an admin UW NetID.
Send an email to all the people you consider supported by your Computing
support organization. This email should include a link with a specially
crafted URL in it. The URL you send is:
where supportOrgName is your Computing Support Org name.
At the UW
NetID Support Dashboard, you should see all the UW NetIDs which
accepted your invitation on the
From the Supported UW NetIDs page, if you select any of the UW NetIDs,
you'll see the basic settings associated with this UW NetID, just like
the user would see if they went the
UW NetID Manage
If you then select the
link, you can see the UWWI user attributes associated with this UW
And finally, if you choose the edit link from the UWWI Settings page,
you can edit that UW NetID's UWWI user attributes.
Note that on the Update UWWI Settings page, you can quickly change from
one UW NetID to another by using the 'Support UW NetID' menu in the
upper right corner.
Viewing and Managing UWWI Users
There are a limited number of UWWI user
attributes displayed via this interface. The
UWWI user attributes in this interface were
chosen because they represented the highest
perceived value for the effort required. We are
certainly open to extending the UWWI user
attributes that are available.
The writable UWWI user attributes available via this interface currently
- homeDrive. This attribute is used to designate which
drive letter to map a Windows home directory to, e.g. "H:"
- homeDirectory. This attribute is used to designated the
UNC path for a Windows home directory, e.g.
- profilePath. This attribute is used to designate a UNC
path for a Windows roaming profile, e.g.
- scriptPath. This attribute is used to designate a UNC
path for a Windows login script, e.g.
- loginShell. This attribute is used to designate a Unix
login shell, e.g. "/bin/bash"
- unixHomeDirectory. This attribute is used to designate a
Unix home directory, e.g. "/users/bart359"
The read-only UWWI user attributes available via this interface currently are:
- displayName. This attribute is read-only, because it is
a managed attribute. There are plans to integrate this with
the UW NetID Display Name.
- distinguishedName. This attribute is read-only, and is
- extensionAttribute1 (displayed in the interface as "Whitepages
Publishing Pref."). This attribute is read-only, because it
is a managed attribute. This attribute designates your
student or employee whitepages publishing preference. This
affects the displayName format.
- extensionAttribute2 (displayed in the interface as
"Support Group"). This attribute is read-only, because it is
a managed attribute. This attribute shows the Exchange
- uidNumber. This attribute is read-only, because it is a
- whenChanged. This attribute is read-only, and is
system-maintained. This attribute shows the last time this
UWWI user was changed.
- whenCreated. This attribute is read-only, and is
system-maintained. This attribute shows when this UWWI user
was created. A value around August 2006 indicates that this
UWWI user has been around since UWWI inception.
- pwdLastSet. This attribute is read-only, and is
system-maintained. This attribute shows when this UWWI
user's password was last set. A value around August 2006
indicates that this UWWI user has been around since UWWI
inception, and if a UWWI user that has been around since
inception is unable to login (and has a space in their
password), then they will need to reset their UW NetID
- accountExpires. This attribute is read-only, because it
is a managed attribute. No UWWI users currently have any
If you'd like to access additional UWWI user attributes via this
interface, please let us know.