130 likes | 146 Views
Learn how the City of San Marcos achieved success with Virtual Desktop Integration & view detailed implementation insights. Discover reasons for the move, ROI, costs, and challenges faced during deployment.
E N D
City of San Marcos Virtual Desktop Integration
State CIO Priorities for 2011 • Virtualization(servers, storage, computing, data center) • Cloud computing (software as a service, infrastructure, applications, storage) • Networking(voice and data communications, unified communications) • Legacy application modernization / renovation • Identity and access management • Document/Content/Records/E-mail management (active, repository, archiving, digital preservation) • Social media and networking (Web 2.0 services, wikis, blogs, collaboration • Security enhancement tools • Business Intelligence (BI) and analytics applications • Enterprise Resource Planning (ERP)
Virtualization • How many are doing Server Virtualization? • How many are doing VDI? • Implemented? • Implementing • Evaluating?
NOREX International User Conference • The question was “How many companies are using Virtualization?” • 62 companies in attendance • Out of the 62 – Server Virtualization 100% • Out of the 62 – Virtual Desktop Integration • HAVE IMPLEMENTED – 17 • EVALUATING – 18 • MORE THAN ½ OF USERS ON VIRTUAL DESKTOPS – 1 they had 100%
Reason San Marcos made the Move • Return on Investment • Administration of Technology • Deployment ease • No additional FTEs • “Green” initiative
Return on Investment – 4yrs • 441 - Total number of Workstations • Physical Desktops: $418,950 • 5 Year replacement schedule • Replacement Computer - $950.00 • 2 Gig Ram; 250 Gig hard drive; 2.93 GHz Duo processor; 8x DVD-ROM; 5 year NBD warranty • Virtual Desktop Integration: $399,744 • Cost per device $306.00 = $87,000 – Pano Logic Zero Client • Storage – 12 terabytes = $120,000 (EMC software & licenses) • Servers – 6 @ $10,500 = $63,000 • VMware – Vsphere, View, Converter $129,744 • 24 - CPU licenses • 220 - View Licenses • 1 – Thinapp License
Background • History • Ideas to deal with PC replacements • Meeting with Citrix • Council Remodeling (Dec 2009) • Infrastructure • About 70 Servers • About 440 Desktops • Network Layout(Physical location based Vlans) • Disclaimer
Initial Deployment • Planning test phase • VMware ESX 3.5 • VMware view • Server Base • Using existing Dell 2950 • Additional memory (64GB) • Network Design • Choosing HP Thin Clients • Council 13 stations + about 4 others (Unix Based) • Challenges • Unix based thin client OS (Issues with peripherals) • Choosing Panologic Devices • 3 weeks time limit (inadequate testing) • Building off Test bed
Intermediate Deployment • Separating VDI ESX from Servers • Setting hardware standards for VDI (20GB HDD, Dual Processors, 2GB memory) • Challenges • Inadequate Planning (Storage, Memory, Network) • Testing (Selecting appropriate users for testing) • PC replacement driving VDI deployment • User resistance
Current State • Hardware • 4 Dell R710 running ESXi 4.1 • 96GB memory each • 2 sockets with Quad Core Processors • 8 1G Network ports • 100megs to Desktops • Vlans mimic Physical Network • Pano Broker Vs VMware View • Pano Remote • 35% deployed – about 150 users
Departments Deployed In • 150 Virtual Machines • Fire -Police • Library -Finance • Animal Shelter -Parks & Recreation • Utility Billing -Information Tech. • Engineering -City Clerk • Council Chambers -City Managers • Electric Utility
Applications • ArcGIS Oracle Financials • ePersonality (Payroll) Rescue Connection • Adobe Prof. Maximo • Novus Agenda Laserfiche • Office Prof. 2007 Clean Slate (Fortress) • Fire Programs Active Networks (Class) • Harris North Star (UB) CIS (RMS) • Adobe CS5 Suite Odyssey • Nero 8 Coban (Digital Video) • Scan Doc Omnixx • Doc Shell CuteFTP • Scan all Pro Pontem Cemetery • Visio Spitfire • Tokay RemitPlus
Conclusion • Known Issues • Support of 3 or more monitors • Scheduling of Anti-Virus updates • Selection of employees for beta testing • Link Cloning • Limited to 500 VDI per Pano Broker • Security • Plan/Design/Test before Deployment • Address User concerns (Keep them involved) • Identify issue related/not related to VDI • One Size does not fit all