System Migration Guy Randy Fleegman Guy Fleegmanershonconsortium net

System Migration Guy “Randy” Fleegman Guy. Fleegman@ershonconsortium. net Senior System Engineer Ershon Consortium

Overview • Team • Purpose • Network before migration • Network proposed solution • Conclusions and Recommendations

Migration Team • Guy Fleegman - Lead • Allen Gamble • Terry Hoitz • Gene Mauch

Purpose • Chose networking • • Two years maintaining network/PC’s Co-op with network consultants • Compatibility issues with Novell client • • Wasted time on phone support Downloading patches from Novell site or software manufacturer’s site

Network Before Migration • • • 2 Novell 4. 11 Servers • • File/application servers 1 at each office 1 NT Server • Exchange, Proxy, Intranet 1 NT Small Business Server • Inherited from merger 1 NT Terminal Server • Citrix for remote connectivity Mix of Windows 9 x and some 2000 workstations

Proposed Solution • • • 2 Windows 2012 Servers • 1 at each location 1 ESXI Server • Exchange, Proxy, Intranet 1 Small Business Server 1 Terminal Server Upgrade all workstations to Windows 10

Proposed Solution • Purchase new Dell Server • • Dual 4. 8 GHz RAID 0: 5 5 TB drives 32 GB RAM Tape drive for backups • Purchase additional Windows 10 licenses

Deliverables • Test Environment with two Novell 4. 11 Servers, an ESXI Server setup as a Domain Controller, a Windows 2012 Server with Active Directory installed, and a Windows 10 Professional Workstation • Migrate data and users from Novell Servers to Windows 2012 Server • Setup ESXI Server as either a PDC, BDC, or a member server • Uninstall Novell client from company’s client PC’s • Configure Microsoft Client for Windows 2012 Server on workstations

Questions?