Some things to keep in mind for Exchange in the Cloud
These are some notes from internal UIT testing, as we continue to work to configure the environment these recommendations may change, but it is an attempt to stream of consciousness gather information for when more official documentation will be needed - Lee
Students
- Students could become a temp to a full-time employee.
- We need to be able to move people back and forth from the cloud as needed.
- o365 if someone prefers it, even if they are faculty or staff
Hybrid GAL
- delegates cannot be separate from their primaries
- e2010sp2 has hierarchical address list support
- can use in an on-prem environment
- didn't implement it online
- shared smtp you can do free-busy and you can do look-up
- delegate
- resources can be in either place.
- cannot change PWD in the cloud
- no there isn't a way to suppress the password
- we need to have a way to redirect it to tufts
- DIRSYnc controls GAL population. The pilot currently only syncs with the test OU but will for production sync with the entire AD environment.
Load Balancing for O365
- web profile: very similar rotation
- for the active client (mac, active sync, outlook) all will go through an exchange proxy on the MSFT back-end that one is going to be a different operation
- public folders: for a mailbox in the cloud, they will not see on-prem public folders
The business implications
- Users Must reset their Tufts Passwords here @ Tufts
- Student workers may have reasons to move back and forth with the cloud depending on who they work with (calendar delegation, or need for public folders)