An update from the SEAS Computing Office
Your EECS e-mail account will migrate to your Google Apps for Harvard (g.harvard.edu) account, provided you’re entitled to one. There will be no change in email addresses. As with seas.harvard.edu addresses, your eecs.harvard.edu or cs.harvard.edu email address will continue to function. If you have specific needs or concerns, please let us know.
Existing EECS mailman lists will be moved to the HUIT mailman server infrastructure.
DNS and DHCP
Historically, networks with addresses 140.247.6x.* have been dedicated EECS research groups and managed by EECS-specific DNS and DHCP servers. These networks will be replaced by more secure networks internal to Harvard. Where needed, individual hosts will be given publicly routable addresses. DNS and DHCP services will be provided by HUIT’s client management system, and updates will be handled primarily by the HUIT desktop support group.
The virtual machines that host EECS web sites will migrate to the AWS cloud, and they will no longer be able to connect to personal home directories or research group storage. Therefore any web content in these locations will need to be migrated to AWS along with the virtual machines.Although no other changes to existing websites are currently planned, there are other hosting options available within Harvard, and we’d be happy to help you take advantage of them.
Authentication for EECS login accounts will be consolidated with the SEAS identity management system based on Active Directory.
Home Directories and Data Storage
Home Directories and Data Storage - EECS home directories will remain as they are for the time being. Access to HPC systems in the FAS RC area will require a separate FAS RC account with a home directory of its own. Research group directories will be moved to storage provided by FAS RC, but they will still be accessible to all hosts used by EECS researchers.