6. #E2EVC #BRU
Generalisation
alert!
Most VDI implementations to date are
tactical additions to projects involving
RDS/FAT
Why?
64-bit OS ¦ Resource Isolation | Hardware
Access
23. #E2EVC #BRU
XenClient and DaaS
• Manage Centrally with Local Execution
• Deliver Layered Images Intelligently
• Use Device-Native Management
24. #E2EVC #BRU
• Use of XenClient for
secure remote
access
• Remote deployment
• Validated Endpoint
• @150 users
• 4 types of devices
• Typical delivery time
@ 2 hours
25. #E2EVC #BRU
• Single instance management
• (Pretty) suitable for COPE
• (Pretty) suitable for BYOD (with DP)
• Slightly different user experience
experience
• Bandwidth can be cumbersome
• PvD useful for small # apps
• DaaS - tricky– h/w; multi-tenancy; multi-domain
36. #E2EVC #BRU
New requirements drove:
• Local execution
• Centralized management
• Mirage adopted for 7000
end-points
• Rollout will (should) be 70%
complete by end of August
(4 months to get there)
• Remote Deployment
• 30mins for initial base
image deployment – 12 mins
re-image
• Differential Imaging with
data de-dupe.
• Used with RES Software suite
(could be SCCM, etc.)
• Native as a Service (NaaS)
37. #E2EVC #BRU
• Single instance management
• Suitable for COPE
• Suitable for BYOD
• No changes to user experience
• Bandwidth requirements low
• Can be simply a backup tool
• DaaS - native