1 / 14

2013 Trend Infrastructure Migration

2013 Trend Infrastructure Migration. Anthony Phillips Office of Information Security and Compliance anthony@ksu.edu. 2013 Trend Infrastructure Migration. Why did we decide to migrate to a completely new server infrastructure ? When did the migration start, when will it be finished?

kyle
Download Presentation

2013 Trend Infrastructure Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2013 Trend Infrastructure Migration Anthony Phillips Office of Information Security and Compliance anthony@ksu.edu

  2. 2013 Trend Infrastructure Migration Why did we decide to migrate to a completely new server infrastructure? When did the migration start, when will it be finished? What is being migrated? Who is impacted? What effects have we seen? What comes next?

  3. Why did we decide to migrate to a completely new server infrastructure? • 8 x OSCE servers, 5 x TMSM, 3 x SmartScan servers, 2 x Control Manager servers • Variety of hardware, versions, patch levels, functionality • Plethora of firewall rules • Not scalable or maintainable – something is always broken • Is it Trend or is it us?

  4. Why did we decide to migrate to a completely new server infrastructure? • 23,334 clients with not all servers reporting accurately • 14,336 Windows clients • 8,968 Mac clients • No ability to add mobile clients

  5. When did the migration start?When will it be finished? • New Servers - 4 x OSCE = 10.6, 2 x TMSM = 2.0, • 3 x SmartScan = 2.6, 1 x CM = 6.0 • First new OSCE server brought online Nov. 2012 • All 4 new OSCE servers, 3 SmartScan servers, 1 CM running by May • Began migration and client testing in June • Official migration started Aug. 5, 2013 • Target shutdown date – Nov. 1, 2013

  6. When did the migration start?When will it be finished?

  7. When did the migration start?When will it be finished?

  8. When did the migration start?When will it be finished?

  9. What is being migrated? • All new clients – Installers at http://www.k-state.edu/its/antivirus/ updated Aug. 2 • OS01 – 129.130.255.187, OS02 – 255.188, OS03 – 255.189, OS04 – 255.189 • All existing clients installed against central servers • TOS1, TOS2, TOS3, OffCampus, Campus01, Campus02, Campus03, AV01 • All departmental servers reporting to central Control Manager • Old: TCMP – 129.130.13.187, TCMC – 129.130.13.188 • New: ksu-cm.ads.campus – 10.130.69.59 • NOT clients installed against departmental servers

  10. What is being migrated?

  11. What is being migrated?

  12. Who is impacted?What effects have we seen? • Clients campus-wide including: • ResNet • Faculty / Staff / Students • Off Campus • A few endpoint issues: • Windows 8 high CPU utilization • Windows 8 slow ODBC connections • Broken Web Reputation Services

  13. What comes next? • Spin down old OSCE / TMSM servers • Migrate departmental OSCE and CM servers to new CM • Spin down old CM servers • Close network firewall ports • Develop and document reporting capability • Maintain and monitor infrastructure • Mobile clients ?

  14. Suggestions?Questions?

More Related