Exchange E-mail Implementation
Updates
- June 13, 2008 The Research and Grants & Contracts was successfully converted. Details
- December 5, 2007 The Exchange email team has entered into its second phase involving an archiving service and hardware rehabilitation. Support model discussions for primary and individual service plans are on the teams' upcoming agendas. Details
- October 19, 2007 Implementation and policy development work, such as quotas and disk space, continue, to move closer towards the implementation of consolidating 13 Exchange servers as a first major assignment of the project team. Details
- September 14, 2007 Several topics arose during the discussion at the Email - Exchange implementation team table including server redeployment, the migration schedule, email archiving, and the plan for administrative accounts. Details
- August 21, 2007 Updates were given for the five sub teams of the Servers and Services Consolidation project. Details
- April 21, 2007 All of the sub-teams are meeting either weekly or bi-weekly, striving to have their preliminary budgets and design architectures completed by the end of April. Each hopes to have a group-specific timeline in place very soon in order to sequence the projects, identify the overlaps, and make decisions on key policy issues. Two key policies are the naming conventions of email systems and the deleted mail retention period. Details
- March 2, 2007 The group has been busy surveying exchange administrators campus-wide to better understand the topography of the current situation. The group came up with some preliminary plans and discussion with vendors and met with current Exchange areas on campus to answer questions and get a sense of what the expectation is with the service. They decided to use the 2007 Microsoft product because it has the best design with the most offerings. They are also working in conjunction with the Unix Email team to have a better understanding and to recommend an overall plan, and to come up with a fundamental, comprehensive set of requirements to meet customer expectations. The next step is to finalize the requirements document and present it to SSC for leadership for approval. The group will then come up with a final design, budget, and schedule. Details
- February 21, 2007 The Email teams (Exchange and UNIX) are considering how common backend infrastructure can be utilized to provide each service and are developing a list of requirements generated by and tested with the customers. Details
- January 31, 2007 The Servers and Services Consolidation sub-teams are gathering requirements and developing budget plans, with a target completion date of March 31. They are also in the process of collecting more server-related data for planning purposes, such as the server age and brand. Details
- December 20, 2006 Exchange E-mail Implementation Team is developing an implementation project plan, completing initial research with consultants and vendors, and contacting key customers. One consideration is whether the initial installation should utilize Microsoft Exchange 2007, or remain with Exchange 2003.
- October 4, 2006 The Exchange Email Implementation team has launched. Details