...
For Windows devices, a user may request to "self-manage" the their device, meaning that the device is exempted will be exempt from all standard IT SU domain management policies. In these instances, the user becomes the primary administrator of assumes primary administrative responsibility for the computer. If any problems ariseIn the event of any loss of access to the system, Technology Services may be unable to assist you with any loss of user data or access to the system, and we provide operating system recovery. We will provide assistance on a "best-effort" basis, but we make no guarantee that the system can be restored to a user-configured state. Technology Services' responsibility Our only obligation will be to return the system to the "base configuration" as defined in the first bullet point in the terms below.
Technology Services will ask for a written agreement to the following terms when opting to self-manage a device:
- Technology Services will install and configure the operating system with access for the primary user (one standard user account and an administrator-level account) which is defined as the "base configuration"
Technology Services will install any licensed software applications requested by the user during setup. NOTE: Some university software cannot be installed on an useroff-managed domain device, such as those that require connection to a license server (MATLAB, SPSS, Tableau)
- The user is solely responsible for their data backup/retrieval on self-managed systems as well as the management of applications not licensed by the university
- The user is solely responsible for maintaining the encryption on the local drive(sdrives (drive encryption is required by SU ITS policy)
- Any security incidents, such as malware/virus infections infection, or other signs of compromise, will result in a non-negotiable wipe and restore of the system back to the base configuration
- If on the campus wired network, the device will be registered on an a private, internal network which can not cannot be reached from external, non-SU networks
- The user must not reuse their NetID password for any local user on the system
- The primary user account should not run with full Administrator-level access on the system
- You may not access or store any "confidential" data on the system, as defined in the university's data classification.
- SU's VPN connection isn't available—connect to campus via RDS if necessary to reach other SU resources.
...