1. Vmware View Pilot at UNC
Brad Sharp, Manager of Technology Operations
Phillip Wyperd, Desktop Support Manager

2. Agenda Background Pilot Lessons Learned Moving Forward Demonstration
Q&A

3. Initial Brainstorm Network Impact Scalability Printing
Patch Management
USB Support
Lab Environment
On Campus
Off Campus
Administrative Environment
Faculty Offices
Apple Platform
Persistent
Non-Persistent
Dual Screen Support
Reporting
Portability
Multimedia
Thick Client
Classroom Environment
Thin Client
Disk Storage
Security

4. Success of server implementation
Why Vmware View?
Success of server implementation
80 Physical to Virtual Conversions
150 Total Virtual Servers
ESX Familiarity

5. Hardware Backend ESX Hosts 3 HP Proliant BL465G5 Blade Servers
2 Quad Core AMD 2.7 Ghz Processors, 32 GB Ram
Fibre Channel Card
Storage
EVA 4100
2TB of Disk Space
1 300 GB LUN
1 500 GB LUN
View Servers
1 Virtual Center Server
2 View Manager Servers
1 View Security Server

6. The Plan Internal Processes Faculty/ Staff Offices
Utimaco Management
New Technology Testing
Technical Support
Faculty/ Staff Offices
Thick Client
Thin Client
Off Campus
PC/Mac
Student Owned Computer
On Camus
Off Campus
PC/Mac
Lab Environment
Thick Client
Thin Client

7. The Pilot Internal Processes Faculty/ Staff Offices
Deployed 20 Machines
Student Owned Computer
Deploying to 30 machines
Faculty/ Staff Offices
Deployed 15 Machines
Lab Environment
Deployed 5 Thick Clients
Deployed 4 Thin Clients

8. Pilot lessons learned

9. Project Team 6 Project Team Members Communication amongst team members
FAQ
Useful links
VM admin docs

10. Base Image Build the base for all future Parent images
Gain Team consensus of essential software
Limit image size.
Utilize performance guides for View
VM view articles and Tcpdump.com KB articles.
Turn off non-essential services.
GPO check lists.
RDP access.
Delete windows updates temp files.

11. Parent Images Setup specific profile settings
Install specific software
App-V userinit string error
Release IP address prior to provisioning

12. Provisioning Desktops
How many desktops
Parent image size
ESX host hardware
Persistent vs. non persistent
Determine the scope:

13. Provisioned Desktop Lessons Learned
Capacity example:
(13 desktops, 3 parent VMs, 3 replicas used up a 300 GB LUN.)

14. Provisioning Desktops lessons learned
Keep vSphere organized
VMs and Templates view
Desktops provision in the same location as the parent
Use naming schemes

15. Provisioning Desktops lessons learned
View Composer
View Manger Admin Guide
AD Containers & QuickPrep
The very useful VM naming pattern
Delete upon first use

16. PCoIP Multi-media was improved over RDP
Very specific parent configurations to achieve success
Symantec End-Point needed special ports opened
Remove security login banner from GPO
True multi-monitor support?
Match Resolution of view composer to Parent image

17. DCHP
DCHP scope configurations.

18. Location based Printing
Pharos Uni-Print
User startup script assign spool to generic printer.
Client hostname determined printer spool

19. Client Hardware
THICK THIN 0

20. Thick Thick clients: 15 Dell Optiplex GX 520s
Windows XP with Microsoft Steady State.
Interacts with Symantec ghost.

21. HP 5630 HP 5545 HP 5730 HP Thin Clients Windows PE Easy Deployment
Linux Based
Fast
Scalable management solution
HP 5545
Higher end features
HP 5730

22. Wyse Wyse Thin Client Low Cost New OS Requires management server
No PCoIP support

23. Zero Client Panologic Looks Cool Low power usage No PCoIP Support
Requires management server and proprietary software
Did not work with our Juniper VPN product

24. Thin Client Recommendations
Thick Client
Recommended on existing old hardware
Wyse
Not recommended
Panologic HP
5630 OK
5545 Better
5730 Best

25. Thin App vs App-V
Microsoft APP-V VS

26. ThinApp Positives Easy to create packages Quick launch time
USB software
Negatives
Lack of License management
User access
Duplicate effort to create packages

27. App-V Positives License Management AD integration Negatives
Server management
Client software

28. Recommendations Microsoft APP-V
Stream Software to Labs and Virtual Labs
ThinApp
Utilize USB Drives for cleanup utilities

29. Lab Monitors End User Experience:
Great pilot end user group
Provided quality feed back
High usage of multi-media caused concerns

30. Most students did not notice a difference Expanded pilot environment
Student Computer Lab
Student Computer Lab End User Experience:
Most students did not notice a difference
Expanded pilot environment

31. Microsoft Licensing VECD Licensing Scenarios VECD to VDA July 1, 2010
No one at Microsoft understands VDA Licensing

32. VDA Licensing
Additional License not Required for Software Assurance Licensing
VDA Licenses Required for all Thin Clients and 3rd Party Owned Devices
Total Licenses Required = Total Devices not Qualified for SA that will be used to access Virtual Machines
Single VDA License allows concurrent access for up to 4 VMs
Licenses can be reassigned to a new user after 90 days
Before a user can access their virtual machine, they must assign their Windows VDA license to a device.

33. Moving Forward

34. General Recommendations
VDI is an emerging technology
Hesitant to put all eggs in one basket
Implement Internal production virtual desktops for shared technologies
Implement Remote Lab for one online class during fall semester
Investigate refreshing a lab with Thin Clients during FY2011
Investigate Thin Clients in faculty offices for secondary machines

35. Remote Lab Deployment Identified an online Sociology Class
Purchase VDA Licenses
Utilizing VMWare Security Server for access to machines
Provide specialized software for students
Survey Faculty and Students on end user experience

36. Remote Lab Demo
UNC Remote Lab

37. Questions? Brad Sharp, Manager of Technology Operations
Phillip Wyperd, Desktop Support Manager