Novell to Microsoft Conversion: Business Case

Transcription

1 Novell to Microsoft Conversion: Business Case Presented To: 3/11/ Hamilton Lane, Suite 200 Naperville, IL Voice & Fax:

2 Version History Ver. # Ver. Date Author Description Feb-11 Scott Weyandt Initial Draft Feb-11 Brian Desmond Review and edit Feb-11 Scott Weyandt Additional edits Mar-11 Scott Weyandt Final edits following HACC review Mar-11 Brian Desmond Copy edit Page 2 of 27

3 Table of Contents Executive Summary... 4 Project Overview... 8 Novell to Microsoft Migration Costs Current Costs Microsoft Migration Costs Hardware Software/Licensing Deployment/Migration Costs Deployment Tools Training Cost Summary and Comparison Additional Savings Opportunities Novell to Microsoft Migration Plan Summary Page 3 of 27

4 Executive Summary This document details the findings and recommendations of Moran Technology Consulting (MTC) concerning whether or not (HACC) should migrate from their current and Network Operating System (NOS) Novell GroupWise and Novell Directory Services (NDS) - to Microsoft Exchange Server 2010 and Windows Server 2008 R2 Active Directory. Members of HACC Central IT have been considering whether to undertake this migration for some time. Most recently, the question was raised as a result of a HACC telephony assessment that resulted in a recommendation and commitment to replace HACC s current, legacy telephone infrastructure with a Cisco IP telephony (VoIP) solution. As part of the telephony assessment, recommendations were made for HACC to investigate migrating to Microsoft Exchange Server 2010 ( ) and Active Directory to facilitate a robust, Cisco supported IP telephony integration with (i.e., a unified messaging solution). HACC contracted MTC to assess its current Novell GroupWise and NDS environment and develop a detailed business case that evaluates whether or not to migrate to a Microsoft and directory platform. Over several months and with the direct input and feedback from both HACC Central IT and campus IT resources, MTC has developed a number of deliverables aimed at delivering an accurate assessment of the costs and benefits of migrating to Microsoft. These deliverables include: Cost Comparison and Business Case (HACC Business Case.xlsx) Microsoft Active Directory Design (HACC AD Design.docx) Microsoft Exchange 2010 Design (HACC Exchange 2010 Design.doc) Microsoft Reference Architecture for File, Print, and additional Network Services (HACC Windows Reference Architecture.docx) Novell to Microsoft Migration Plan (HACC Novell to Microsoft Migration Page 4 of 27

5 Plan.mpp) This document presents a summary of the key findings presented in these deliverables. The business case we present here is supported by these documents as is our strong recommendation that HACC migrate from Novell GroupWise and NDS to Microsoft Exchange Server 2010 and Active Directory. MTC recommends that HACC begin to prepare for this migration immediately and initiate the migration in the current calendar year (2011). Our recommendation is based upon a number of key findings: Novell GroupWise currently has only a small and shrinking market share in the corporate and directory market. Additionally, Novell continues to face competition from both on-premise solutions (such as Microsoft Exchange) as well as cloud offerings from both Microsoft (Office 365) and Google (Google Apps). In a 2008 study, Ferris Research found that while Microsoft Exchange had a 65% market share among organizations in the United States and IBM Lotus Domino had a 10% share, the Novell GroupWise share was reported to be negligible (see Ferris Research, Products: Market Shares, Versions Deployed, Migrations, and Software Cost, January 31, 2008). In addition, the future of Novell GroupWise remains a question without any immediate answer. After reporting losses greater than 200 million dollars in the 4 th quarter of 2009, announcing several rounds of layoffs, and losing many of its executives, Novell announced a plan to be purchased by Attachmate Corporation in November of The purchase was just approved by Novell shareholders (February 18, 2011) but depends upon approval of a planned sale of 800 patents to a consortium of companies led by Microsoft and Oracle. The question is no longer if HACC should migrate, but simply when HACC should migrate from Novell to Page 5 of 27

6 Microsoft. An investigation of the total cost of ownership (TCO) of both Novell and Microsoft solutions shows that there are considerable financial reasons to undertake this migration sooner rather than later and avoid further spending on Novell licenses and infrastructure. A migration to Microsoft will reduce HACC s annual spending on licenses for and directory services by roughly $90,000 per year and result in an annualized savings of nearly $60,000 per year (after factoring in initial investment in hardware and services) as shown in the following table. COST COMPARISON (Annualized) Annualized Savings (5yr) Novell $139,973 Microsoft $79,785 Savings $60,188 In addition to the direct savings from migrating to Microsoft Exchange and Active Directory, MTC has identified significant savings opportunities for HACC that build upon the Microsoft licensing and infrastructure purchased for Exchange 2010 and Active Directory equaling a total of $590,000 over five years or $118,000 per year (annualized savings) as shown in the following table. STEP-UP SAVINGS (5 YEAR) Year 1 Year 2 Year 3 Year 4 Year 5 Total Forefront Endpoint Protection $19,471 $27,471 $27,471 $27,471 $27,471 $129,355 Forefront Online Protection for Exchange $41,000 $41,000 $41,000 $41,000 $41,000 $205,000 Exchange Archiving/Compliance/eDiscovery $5,000 $5,000 $5,000 $5,000 $5,000 $25,000 Voic /Unified Messaging $22,116 $54,000 $54,000 $54,000 $47,000 $231,116 Savings $87,587 $127,471 $127,471 $127,471 $120,471 $590,471 As suggested by the HACC telephony assessment, Novell s diminished market share leads to few choices among vendors and products that integrate with and directory services. The primary case in point being that IP telephony vendors such as Cisco do not natively integrate with Novell GroupWise but Page 6 of 27

7 instead required third-party products (often unsupported by Cisco) to integrate with Novell. Page 7 of 27

8 Project Overview In the fall of 2010, MTC was contracted by HACC to perform a thorough and impartial evaluation of its current network operating system and environment (Novell GroupWise and Novell Directory Services). As part of the assessment, HACC requested that MTC identify the pros and cons of converting to a Microsoft NOS (Windows Server Active Directory) and Exchange Server 2010 environment from the current Novell NetWare and GroupWise products. In addition, HACC requested that we develop a project plan that identifies the total cost of a conversion to Microsoft, including: Estimates for hardware and software (licensing and support); Resource, time, and cost estimates for implementing the new solution (upgrade or migration); Knowledge transfer and training of HACC to operate and maintain the new solution. In order to perform this assessment and deliver the required deliverables MTC performed the following key steps: STEP 1: Project Kick-off STEP 2: and Directory Requirements Gathering and Assessment o This step included conducting a requirements survey, workshops, and individual interviews with IT managers and technical resources from: Central IT Gettysburg Campus Harrisburg Campus Lancaster Campus Lebanon Campus York Campus Page 8 of 27

9 o Data was gathered concerning current utilization, administration, hardware, and licensing costs for , directory and desktop systems. STEP 3: and Directory Planning o MTC developed the following deliverables as part of its planning and costing exercise: Cost Comparison and Business Case (HACC Business Case.xlsx) Microsoft Active Directory Design (HACC AD Design.docx) Microsoft Exchange 2010 Design (HACC Exchange 2010 Design.docx) Microsoft Reference Architecture for File, Print, and additional Network Services (HACC Windows Reference Architecture.docx) Novell to Microsoft Migration Plan (HACC Novell to Microsoft Migration Plan.mpp) o Each deliverables was reviewed with HACC representatives for input and feedback and then revised as necessary. o Design documents and planning documents were developed so they could also be used in the actual deployment and implementation of Microsoft Exchange and Active Directory. In addition, MTC conducted a requirements workshop for the design and implementation of Microsoft s identity management solution (Forefront Identity Manager 2010, or FIM). We recommend that FIM be deployed by HACC to integrate HACC s key enterprise systems, such as SunGard Banner, SunGard Luminis, and Blackboard WebCT with its and directory infrastructure. This integration will allow HACC to automatically provision and deprovision both employee and student (Exchange 2010 and Gmail, respectively) and directory accounts (Active Directory) as well as synchronize passwords across these systems and other key HACC applications. Page 9 of 27

10 Interviews with both campus IT and Central IT security suggest that the ability to automatically create and manage employee and students accounts is a critical need and will lead to greater IT security as well as administrative efficiency. MTC has developed a FIM 2010 design and deployment plan (including estimated costs). However, as a FIM deployment is outside of the key focus of the Novell to Microsoft business case these items have not been included in this document. Key documents for this step include: HACC FIM Design (HACC FIM Design.docx) HACC High-level FIM Plan (HACC FIM Plan.mpp) HACC FIM Cost Estimates (HACC FIM Costs.xlsx) Page 10 of 27

11 Novell to Microsoft Migration Costs Current Costs Current HACC annual spending (annualized over 5 years) on its Novell and directory environment is $127,598 per year. These costs include both software licensing ($106,973.20) and hardware ($20,625). The software licensing costs are comprised of: Novell licensing = $88, NotifyLink licensing = $4,000 Symantec Ghost licensing = $14,750 NotifyLink is currently required for mobile devices to synch with GroupWise calendaring but will no longer be required with Exchange Symantec Ghost is currently used for imaging desktops. However, HACC already owns licenses for Microsoft s desktop imaging and software deployment solution, Systems Center Configuration Manager (SCCM). Furthermore, using SCCM as a migration tool will reduce the time and effort to migrate desktops from the current Novell environment to Microsoft Active Directory. Therefore we are recommending that HACC move from using Symantec Ghost to Microsoft SCCM to reduce time and effort when migrating to Microsoft Active Directory as well as reduce annual spend. Current Novell costs also include an annualized cost for Novell GroupWise, NDS, and Novell file server hardware. We have assumed a 4 year hardware refresh cycle in our model. HACC is currently operating with aging Novell hardware. Most or all of this hardware is scheduled to be refreshed in the coming year. There are currently 18 servers in the HACC Novell environment. Based on this information, we have calculated the total cost of Novell hardware at $80,250 per refresh or an annualized cost of $20,625. Page 11 of 27

12 The following table shows the current annual cost for Novell as well as the annual cost of Novell per employee (calculated as full-time equivalent [FTE]). CURRENT COSTS Current Novell Costs Per Year $127,598 Number Employees (FTE) 1,402 Cost -- Per Year/Employee $91.01 Cost -- Per Month/Employee $7.58 Microsoft Migration Costs The cost of migrating to Microsoft Exchange 2010 and Active Directory are comprised of the following: Hardware costs for: o Exchange 2010 o Active Directory o Windows file servers o System Center Configuration Manager Software/Licensing for: o Exchange 2010 o Active Directory o Windows file servers o System Center Configuration Manager Deployment/Migration Services Deployment/Migration Tools Hardware In order to reduce hardware costs, MTC s designs for Exchange 2010, Active Directory, File Services and SCCM have taken advantage of HACC s already existing Page 12 of 27

13 virtualization infrastructure (VMWare ESX) and recommend the use of the Microsoft virtualization platform, Hyper-V, for campus infrastructure. We have also sought to further reduce the total cost of hardware by sharing hardware resources between services wherever possible. For example, each campus location will use a single robust server that will be capable of hosting several virtual servers that will include (but not be limited to): Active Directory Domain Controller Windows File Server System Center Configuration Manager In order to minimize cost and footprint while adhering to industry best practices, the recommended architecture at each site is a single server running Microsoft Windows Hyper-V. Three virtual machines will be hosted on top of Hyper-V at each campus. One virtual machine will be dedicated to the Active Directory RODC role, a second virtual machine will be dedicated to file and print services, and a third virtual machine will be dedicated to SCCM. The recommended host servers are sized to accommodate approximately four additional virtual machines in the future if a campus specific application is required or in the event of a changing business need. environment. The following table shows the total hardware costs for the proposed Microsoft Hardware Exchange Server Role Qty (Servers) $/ Unit Cost CAS/Hub (VMs at Primary, physical at DR) 2 $3,500 $7,000 Mailbox 3 $9,000 $27,000 Total $34,000 Active Directory Server Qty (Servers) $/ Unit Cost Domain Controller 4 $3,500 $14,000 HyperV Host (RODC + File/Print) 4 $8,000 $32,000 Total $46,000 System Center Configuration Manager Page 13 of 27

14 Server Primary Site Server 1 $ 3,500 $3,500 Total $3,500 Additional File Servers Qty (Servers) $/ Unit Cost Central File Servers 1 $7,000 $7,000 Total $7,000 Software/Licensing The Microsoft solution will require minimal server licensing fees for each of the servers (Exchange 2010, Active Directory, File Servers, and SCCM). The following table shows the total cost of licensing. Licenses Server Qty (Server Licenses) $/ Unit Cost Exchange Standard 2 $70 $140 Exchange Enterprise 3 $399 $1,197 System Center Config Manager 1 $57 $57 Windows Server Standard 7 $43 $301 Windows Server Enterprise 8 $139 $1,112 Total $1,337 Deployment/Migration Costs The costs of migrating from Novell to Microsoft included the effort associated with the deployment of Microsoft Exchange 2010, Active Directory and SCCM. We have estimated the number of outside consulting hours that would typically be required for an organization such as HACC to design, plan, deploy Exchange, Active Directory, Windows file and print services and SCCM for Central Administration as well as all campuses (administrative and educational computing). Our estimates assume that the designs and plans we have provided for Exchange 2010 and Active Directory will provide a foundation for this effort. In addition, consulting services are included to deploy migrations tools, develop migration processes, pilot migrations and then transfer knowledge of the environment and Page 14 of 27

15 migration processes to HACC Central IT and Campus resources. Additional planning and technical support hours have also been included; however, it is assumed that HACC resources will complete the migration of mailboxes, user accounts/groups, and machines. The following tables presents our estimates for the consulting hours and costs required for each of the key tasks associated with a migration from Novell to Microsoft. Deployment Services Qty (Hours) $/ Unit Cost Design & Plan (AD & Exchange) 120 $200 $24,000 Design & Plan (System Center) 40 $200 $8,000 Deployment (AD & Exchange) 80 $200 $16,000 Deployment (System Center) 120 $200 $24,000 Migration Processes & Pilot 120 $200 $24,000 Knowledge Transfer 40 $200 $8,000 Additional Services (Tech Support/PM) 120 $200 $24,000 Total 640 $128,000 The hourly rates in the preceding table are based on industry averages and factor in the cost of travel expenses. Deployment Tools As stated earlier, Microsoft System Center Configuration Manager (SCCM) will be deployed as part of the migration (for the migration of desktops/laptops). The costs associated with using SCCM in the migration have been included above (hardware, software, and services). In addition to SCCM, we have proposed using the Quest migration suite for Novell to Microsoft, which includes migration tools for GroupWise to Exchange 2010, NDS to Active Directory, and Novell file services to Windows file services. Quest s tools are the industry leader in this area and will greatly reduce the time and risk involved in this migration. Furthermore, by reducing the amount of consulting time required for the migration, purchasing and using Quest tools will reduce the total cost of the migration. Quest migration tools are priced by the number of seats required for each Page 15 of 27

16 migration tasks. migration tools (GroupWise to Exchange) are priced per mailbox (estimated at $11/mailbox). We have calculated the cost using the total number of current mailboxes. HACC can reduce this cost by cleaning up and excluding unused or unnecessary mailboxes prior to the migration. Migration tools for directory information (user accounts) and files services are priced per user account associated with file services (estimated to be $8/user). The following table shows the estimated costs of the Quest migration tools for GroupWise, NDS, and file services. Licenses Qty (Mailboxes) $/ Unit Cost Quest Migration Tool (GroupWise) 4,249 $ 11 $46,739 Quest Migration Tool (File Servers) 2,000 $ 8 $16,000 Total $62,739 Training The final cost we have included as part of the migration from Novell to Microsoft is for training. We have included budget for two types of training: IT professional training for Active Directory and Exchange administrators. While only Central IT resource will require deep administrative skills for Active Directory and Exchange as they will own the majority of administrative tasks, we have included training for Campus staff that will need to understand basic administrative functions for guest account creation, group management, group policy and SCCM application and OS deployment. We assume that end-user training will consist primarily of web-based help, hand-outs containing abridged cheat sheet information for basic tasks, and a limited number of open sessions at each location that will provide voluntary classroom training on basic use. Page 16 of 27

17 The following table presents our estimated costs for training. Training IT Pro 7 $1,500 $10,500 End User Information Worker 1 $10,000 $10,000 Total $20,500 Cost Summary and Comparison The following table includes all of the one-time costs associated with a migration from Novell to Microsoft. One Time Costs $301,739 Hardware $90,500 Services $128,000 Training $20,500 Tools $62,739 The annual/recurring costs associated with a migration from Novell to Microsoft are as follows: Annual/Recurring Costs $1,337 Software Licenses $1,337 The total proposed Microsoft costs include an annualized cost for Microsoft Exchange, Active Directory, SCCM and file server hardware and licensing as well as annualized costs for Deployment Services and Deployment tools over a 5 year period. We have assumed a 4 year hardware refresh in our model. The following table shows the proposed annual cost for Microsoft as well as the annual cost of Microsoft per employee (calculated as full-time equivalent [FTE]). PROPOSED COSTS Proposed Microsoft Cost Per Year $71, Number Employees (FTE) 1,402 Cost -- Per Year/Employee $51.10 Cost -- Per Month/Employee $4.26 Page 17 of 27

18 An investigation of the total cost of ownership (TCO) of both Novell and Microsoft solutions shows that there are considerable financial benefits to undertaking this migration sooner rather than later to avoid further spending on Novell licenses and infrastructure. A migration to Microsoft will reduce HACC s annual spending on licenses for and directory services by roughly $90,000 per year. The initial costs of the Microsoft deployment and migration (approximately $300,000) is offset by the licensing costs associated with Novell (Novell, Notify, and Ghost) as well as the elimination of hardware costs required for the Novell GroupWise and NDS refresh. Annual savings during standard operating years (2-4) are projected to be roughly $105,000 with a total savings of over $300,000 over 5 years as shown in the following table. COST COMPARISON (5 Year) Year 1 Year 2 Year 3 Year 4 Year 5 Total Novell $189,473 $106,973 $106,973 $106,973 $189,473 $699,866 Microsoft $303,076 $1,337 $1,337 $1,337 $91,837 $398,924 Savings ($113,603) $105,636 $105,636 $105,636 $97,636 $300,942 A migration to Microsoft will result in an estimated annualized savings of nearly $60,000 per year (after factoring in the initial investment in hardware and services) as shown in the following table. COST COMPARISON (Annualized) Annualized Savings (5yr) Novell $139,973 Microsoft $79,785 Savings $60,188 Additional Savings Opportunities In addition, to the direct savings from migrating to Microsoft Exchange and Page 18 of 27

19 Active Directory, MTC has identified significant savings opportunities for HACC that build upon the Microsoft licensing and infrastructure purchased for Exchange 2010 and Active Directory. We recommend that HACC purchase the Microsoft Enterprise Client Access License (ecal). The Microsoft ecal is priced per full time equivelant (FTE) and is approximately $10 per FTE or $14,020 per year. The ecal provide client licenses for all of the following Microsoft products: Exchange Enterprise CAL (includes Archiving and ediscovery tools and Unified Messaging) SharePoint Enterprise CAL Lync CAL (formerly Office Communication Server, includes instant messaging, video conferencing, telephony, and web conferencing) Forefront Security Suite (Desktop/Server anti-virus, Exchange/SharePoint/Lync anti-virus, on-premise anti-spam, hosted (FOPE) anti-spam) Forefront UAG & TMG (application publishing/single Sign-On) System Center Suite (includes Service Manager, Operations Manager for client machines, Data Protection Manager for client machines) Rights Management Services CAL The ecal licensing for each of these products provide HACC with opportunities to either expand services/functionality (e.g., deploying Lync for instant messaging, etc.) or replace current products/service and derive additional savings. The key savings opportunities that we have identified include: Deploying Forefront Endpoint Protection for Desktop and Server antivirus solutions. Replaces current Symantec Antivirus. Current annual costs of Symantec = $27,471; Forefront Online Protection for Exchange for antivirus and spam Page 19 of 27

20 filtering. Replaces current ProofPoint solution. Current annual ProofPoint licensing costs = $41,000; Exchange Enterprise Archiving and ediscovery tools. Replaces current Messaging Architects system, which currently costs $5,000 annually plus hardware; Deploy Microsoft Exchange Unified Messaging instead of deploying Cisco Unity as part of HACC s VoIP deployment. Cost of Cisco Unity = $54,000 each year for 3 years. The total cost of deploying each of these services is detailed in the following table including all hardware, licensing, and services. Summary Hardware Licensing Services Total Forefront EndPoint Protection $ - $ - $ 8,000 $8,000 Forefront Online Protection for Exchange $ - $ 500 $ - $500 Exchange Archiving/Compliance/eDiscovery $ - $ - $ - Voice Mail/Exchange Unified Messaging $ 7,000 $ 884 $ 24,000 $31,884 If HACC selects to purchase the ecal, the annualized savings derived from migrating to Microsoft are reduced by the cost of ecal licensing ($14,020/yr) to $46,168 as shown in the following table. COST COMPARISON (Annualized) Annualized Savings (5yr) Novell $139,973 Microsoft $93,805 Savings $46,168 However, the cost savings we have identified equal a total of over $590,000 over five years or an additional $118,000 per year (annualized savings) as shown below. STEP-UP SAVINGS (5 YEAR) Year 1 Year 2 Year 3 Year 4 Year 5 Total Forefront Endpoint Protection $19,471 $27,471 $27,471 $27,471 $27,471 $129,355 Forefront Online Protection for Exchange $41,000 $41,000 $41,000 $41,000 $41,000 $205,000 Page 20 of 27

21 Exchange Archiving/Compliance/eDiscovery $5,000 $5,000 $5,000 $5,000 $5,000 $25,000 Voic /Unified Messaging $22,116 $54,000 $54,000 $54,000 $47,000 $231,116 Savings $87,587 $127,471 $127,471 $127,471 $120,471 $590,471 Total potential savings for HACC (savings derived from both the Novell to Microsoft migration and the additional savings opportunity presented by purchasing the ecal and implementing Forefront Endpoint, Forefront Online, Exchange ediscovery and Exchange Unified Messaging) equal $821,313 over 5 years. TOTAL POTENTIAL SAVINGS Year 1 Year 2 Year 3 Year 4 Year 5 Total Savings ($40,036) $219,087 $219,087 $219,087 $204,087 $821,313 Annualized total savings are estimated to be greater than $160,000 per year as shown below. TOTAL POTENTIAL SAVINGS (Annualized) Annualized Savings (5yr) Savings $164,263 Page 21 of 27

22 Novell to Microsoft Migration Plan As part of our assessment and business case development, MTC produced detailed migration plan. The plan was utilized to estimate migration costs (e.g., deployment services) as well as to develop a recommended approach and timeframe for performing the migration. The plan we propose is comprised of four (4) key steps: Step 1 - Deployment and Migration Prep Step 2 Implementation Step 3 - Novell to Microsoft Migration Step 4 Knowledge Transfer We estimate that the project could be completed in 140 days (approximately 7 months) and have scheduled it to take advantage of and integrate with already planned IT activities at each of the campuses (e.g., reimaging of lab computers during summer and the rollout of new software for upcoming semesters). Note this time can be reduced as it requires longer periods for preparation and clean-up than are likely required. However, it may also take longer for HACC to implement all of these changes due to change management requirements. Past projects that required end-users (staff and faculty) to use new software, e.g., the deployment of Office 2007, did meet a significant amount of resistance to change among HACC employees. This resistance led to drawn out deployment and training schedules. The following high-level Gantt chart shows the approximate duration of each of the four key phases of the project: The initial phase, Step 1 Deployment and Migration Preparation, is scheduled Page 22 of 27

23 to begin almost immediately. This phase contains two primary activities: Design and Planning and Directory Clean-up It is recommended that HACC Central IT and each of the campuses initiate a process to clean-up unused GroupWise accounts, Novell Directory accounts and groups, and Novell file shares as soon as possible. By identifying and removing all of the unused or unnecessary directory objects and , HACC can simplify the migration and also reduce the cost of migration tools that are priced per mailbox or per user account. It is recommended that design and planning effort be led by an experienced consultant. However, because HACC has already received designs and a plan or deploying Exchange 2010, Active Directory, and Windows file services the duration and amount of effort required to complete and validate designs should be limited. In addition, the plan includes time/effort for a consultant to develop Sytem Center Configuration Manager (SCCM) designs. Step 2 Implementation includes building a test environment for Active Directory, Exchange 2010, and SCCM, building and deploying the production Active Page 23 of 27

24 Directory, Exchange 2010, and SCCM environments, and deploying the required migration tools and developing migration processes. It is estimated that this phase will require approximately 29 business days or 1.5 months of elapsed time. This includes time for hardware procurement following the validation of Active Directory, Exchange and SCCM designs finalized in Step 1. The majority of this work will likely be performed by an experienced consulting firm. HACC resources will likely only be required to assist with minimal networking activities (e.g., providing IPs, cabling, switch port configuration) and providing virtual machines, racking physical servers and possibly loading operating systems. Step 3 - Novell to Microsoft Migration is scheduled to last approximately 43 business days or two months. However, the duration for each location/campus varies by size and level of effort required to perform the migration. The plan calls for the migration to being with Central Administration. Following a successful pilot and migration for Central Administration, the remaining campuses are scheduled to occur concurrently. Page 24 of 27

25 Campus migrations include individual pilots and durations for migration vary considerably (from 3 weeks to almost 6 weeks). Our plan and cost estimates assume that a consulting firm will deploy the migration tools, document the migration process, perform pilot migrations to validate the process and work with Central IT as well as each campus to transfer knowledge and the ability to perform these migrations. While Central IT and campus IT resources will be largely responsible for the actual migrations of mailboxes, users, groups, desktops, and file services we assume consultants will also be available to resolve issues, answer questions, etc. We also propose that lab and classroom desktops be migrated to Active Directory as part of the standard imaging process that each campus conducts on a semester or annual basis. This greatly reduces the number of machines that will need to be migrated separately (i.e., faculty and staff machines). The following Gantt chart reflects the migration at each campus. Page 25 of 27