Stay updated with announcements, get answers from the community, and share your feature suggestions with us.
You can also submit a request or send us an email at email@example.com.
Sarah Alkire October 08, 2013 • 121 • Announcements / Announcements
On October 31, 2013, the School of Nursing is ending Moodle course service(https://dev.moodle.washington.edu). The opportunity to transition our courses to an integrated, UW IT supported learning management system (Canvas) is one of the main reasons for the decommissioning of Moodle. Some students are still accessing content in Moodle, so care is being taken to provide a graceful exit.
We have identified two main types of users; however, there may be other incidental access to the old Moodle site as well. The main people accessing content on Moodle are students completing "Incomplete" grades and students accessing discussion boards, papers, or other content in preparation for certification.
The plan is to keep Moodle online until October 31, 2013 to give everyone the opportunity to copy or download materials they might need from courses prior to Autumn 2012. All users will need to transition their content before the decommission date to avoid losing access to content.
WHAT YOU SHOULD DO
Sarah Alkire August 01, 2013 • Announcements / Announcements
What and When:
On August 1 2013, we'll remove support for the NTLMv1 authentication protocol from both the NETID domain controllers and at the domain level.
What you need to do:
If you have a service that is unable to support Kerberos or NTLMv2 authentication and uses user accounts that aren't NETID domain user accounts, then you can turn on support for NTLMv1 at your OU level as a workaround. If you do this, we strongly recommend that you begin exploring alternatives as the threat profile for NTLMv1 has greatly increased.
If your service requires NETID domain authentication and NLTMv1, we'd be happy to explore alternative solutions with you. Based on an audit over a 24 hour period, we are unaware of any such services.
At service inception in 2006, the NETID domain did not support NTLMv1 authentication. Due to customer requests, in 2007 NTLMv1 support was added after obtaining an exception to UW policies via the UW Privacy Assurance and System Security (PASS) Council. Growing pressures due to UW identity assurance initiatives and a greatly increased threat profile based on cloud-based NTLMv1 cracking tools mean it is time for NTLMv1 to be retired.
As implied above, we've audited NTLMv1 use via NETID domain user accounts for a 24 hour period and found no use of concern. So we believe this change to be of minimal impact.
We are unable to verify the configuration in domains trusting the NETID domain, and a configuration mismatch between trusting domains and the NETID domain is the most likely source of potential issues, but default settings make the possibility of problems unlikely. If you'd like to audit your own Windows domain for NTLMv1 use, if all of your DCs are WS2008 or better, we can share a PowerShell script with you that will extract relevant events over a 24 hour period. If your DCs are at a prior OS level, it is not possible to differentiate NTLMv1 use from NTLMv2 use without doing network captures.
Another possible source of issues are non-domain joined computers running Windows XP or previous in a default configuration. In that case, the configuration settings will be incompatible. Windows XP is no longer in mainstream support from Microsoft, and extended support ends in a year, so this potential source of problem should also be limited.
More background information about the LMCompatibilityLevel setting is available at http://technet.microsoft.com/en-us/magazine/2006.08.securitywatch.aspx.
Sarah Alkire May 16, 2013 • Announcements / Announcements
Sarah Alkire April 25, 2013 • Announcements / Announcements
Earlier today (4/25/13), TIER reported a SONNET network outage. The root cause is still under investigation, but the issue has been resolved.
TIER support is in the process of contacting all users that reported the outage. All users that are experiencing the problem will need to logout, reboot the computer and re-login to become functional on the network.
Thank you for your patience, and again our apologies for the inconvenience.