This new system has been designed for high reliability, with two front-end proxy servers that are distributing the queries over a cluster of three back-end servers. The servers are distributed across Soda, Sutardja-Dai and Warren Halls.
For the most part we hope that this transition will be transparent, other than faster queries. However, there is one notable change to mention: We are taking this opportunity to retire the current separate LDAP password and instead passing all authentication through to our Windows Active Directory servers.
**Beginning Thursday, January 16th, 2014 at 7am, wherever you previously used your EECS LDAP password, you will now use your EECS Windows AD password. The current LDAP passwords will be archived and retired. The means you will have one less password to remember!**
Most people will not be affected by this change. But based on recent logs, any people who have been using their LDAP password will receive a second email notification after this with more information.
Here are the answers to some questions we are anticipating:
Q. What is my Windows password?
A. We can’t tell you what your password is, but your Windows password is the same password you use to login to a Windows workstation in EECS, map a network drive from an EECS fileserver, or authenticate to the EECS-Secure or EECS-Open wireless networks.
You can check now to see if you know your current Windows password by making a Remote Desktop Connection to winterm.eecs.berkeley.edu. Login as firstname.lastname@example.org to see if you know your password.
Q. I don’t know my Windows password. How do I reset it?
A. Please visit the helpdesk in 395 Cory with a picture ID.
If you are off-campus and cannot come in person, send an email to email@example.com and we will send you a special link where you can change your password.
Please direct any other questions to IRIS at firstname.lastname@example.org.
[2014-01-16 08:59:41 | Robert McNicholas]
The transition to the new LDAP infrastructure has been completed. A misconfiguration on one back-end node resulted in sporadic authentication errors for some users between 7am-8am but has been resolved.
Please send any problem reports to email@example.com.