Vojtěch Morávek, Senior Systems Engineer, VMware Virtualization Forum 2014, Prague, 22.10.2014 Jestliže SlideShare nezobrazí prezentaci korektně, můžete si ji stáhnout ve formátu .ppsx nebo .pdf (kliknutím na tlačitko v dolní liště snímků).

1. Migrace z překonaných
desktopových technologií na
VMware Horizon 6
Vojtěch Morávek,
Senior Systems Engineer

2. Deliver Virtual Desktops or Just Applications
Through a Single Platform
Single, Secure Platform
2
Virtual
Desktops
Packaged
ThinApps
RDS
Hosted Apps
RDS
Session-Based
Desktops
CONFIDENTIAL

3. RDS Based Desktop and App Remoting
Reduce TCO for Windows Application Access
• Overview
– Integrated delivery of applications and full
desktops running on Microsoft Windows Remote
Desktop Session Hosts (RDSH).
– Seamless access to Windows Apps from mobile
devices
– Utilize the standard View Clients (Win, Mac, IOS
& Android) with PCoIP™
• Benefits
– Low TCO with a classic Terminal Services model,
and favorable licensing from Microsoft.
– Great, high performance, cross-platform user
experience with View Clients, PCoIP™ and the
Workspace Portal.
App App
CONFIDENTIAL 3

4. Easy Access to All Windows and Online Resources
4
Hosted RDS Apps
Packaged ThinApps
SaaS Apps
Virtual Desktops
Citrix XenApp
One login | One experience | Any device
CONFIDENTIAL

5. XenApp 6.5 and Horizon 6 Components Comparison
5
Citrix
XenApp VMware
Horizon
License
Server
MS
RDS
Hosts
with
VMware
Horizon
Agent
MS
RDS
Hosts
with
Citrix
XenApp
Horizon
Workspace
Horizon
View
Connection
Servers
XenApp
Web
Interface
Remote
Desktop
Services
Web
Portal
License
Server
Connection
Brokering
Session
Monitoring
None
XenApp
Data
Collectors
on
RDS
Hosts
XenApp
Load
Manager
on
RDS
Host
CONFIDENTIAL

6. XenApp 6.5 and Horizon 6 Components Comparison
CONFIDENTIAL 6

7. XenApp to Horizon Migration Approaches
Replace
CONFIDENTIAL 7
Migrate healthy XenApp Remote
Desktop Session Hosts with installed
applications to Horizon.
Replace XenApp Web Interface or
StoreFront with the Workspace Portal.
Replace Citrix Receiver and HDX with
the View Client for Horizon and PCoIP.
Implement new Horizon Remote
Desktop Session Hosts with
installed applications.
Replace XenApp Web Interface or
StoreFront with the Workspace Portal.
Replace Citrix Receiver and HDX with
the View Client for Horizon and PCoIP.
One web portal for Horizon with View
virtual desktops, SaaS applications,
and XenApps.
Replace XenApp Web Interface or
StoreFront with the Workspace Portal.
Maintain existing XenApp Remote
Desktop Session Hosts and
Citrix Receiver.
Integrate
Integrate XenApp with Horizon
Migrate
Migrate XenApp to Horizon
Replace XenApp with Horizon

8. Which Approach is Right for Me?
Project Steps Integrate Migrate Replace
Single Web Portal for Remote Apps, Virtual Desktops and SaaS Apps ✔ ✔ ✔
Replacing Citrix XenApp is the goal ✗ ✔ ✔
Significant changes to locations or number of users to be supported ✔ ✔ ✔
Applications to be published require significant changes ✔ ✔ ✔
Existing RDS Hosts are on old version of Windows Server ✔ ✗ ✔
Existing RDS Hosts are unstable ✗ ✗ ✔
There are niche XenApp features that must be maintained ✔ ✗ ✗
Existing client devices are incompatible with Horizon ✔ ✔ ✔
✔ = use caution
CONFIDENTIAL 8

9. Major Components Required
CONFIDENTIAL 9

10. Major Project Steps
• Integrate XenApp with the VMware Workspace Portal
– Deploy the VMware Workspace Portal
– Implement the Citrix Integration Broker
– Configure the Workspace Portal for XenApp
– Decommission Citrix Web Interface or StoreFront
• Migrate or Replace XenApp with Horizon 6
– Deploy VMware Horizon with View
– Deploy the VMware Workspace Portal (optional)
– Prepare Remote Desktop Services Hosts
– Create RDSH Farms and Application Pools. Entitle Users
– Decommission XenApp
10
Integrate
XenApp with the Workspace Portal
Migrate or Replace
XenApp with Horizon 6
CONFIDENTIAL

11. Migration Assessment: Look before you Leap!
CONFIDENTIAL 11

12. Major Assessment Topics
• Business Requirements
• XenApp Infrastructure
• Published Applications and Desktop Sessions
• RDSH Servers
• Users and User Requirements
• Client Devices
• Supporting Systems
CONFIDENTIAL 12

13. Business Requirements
• What are the business goals?
– Single Vendor for VDI and Hosted Apps
– Single Web Portal
– Greenfield
– Tied to new application
– Secure remote access
• Is the migration related to another
business initiative?
– Merger or acquisition
– Corporate relocation
– New way of doing business
• Are there major business changes that will
impact the project?
– Major staff changes (downsize or upsize)
CONFIDENTIAL 13

14. Citrix XenApp Infrastructure
• XenApp version(s) in use
• XenApp Farms
• Major XenApp features in use
• Terminal Servers / RDSH Servers by Farm
• Published Applications and Desktop Sessions by Farm
• Supporting servers
– License Server
– Databases
– Web Interface / StoreFront
CONFIDENTIAL 14

15. Published Applications and Desktop Sessions
• Application inventory: perceived versus actual
• Application demand
– Priority applications
– Applications that can be decommissioned
• Application requirements
– Supported OS
– Device support
• Applications by RDSH Server
• Desktop sessions
– use cases
– configuration
• Users and groups entitled to each application
and desktop session
CONFIDENTIAL 15

16. Terminal Servers / RDSH Servers
• Inventory:
– Name
– Windows Server OS version
– Terminal Server / RDSH Server version
– Location
– XenApp Farm membership
– Supporting RDS License Server
– Major system specifications
• Identify:
– Ideal migration candidates
– Systems running outdated server OS (pre 2008 R2)
– Servers with resource or stability issues
CONFIDENTIAL 16

17. Users and User Requirements
• Identify Users by:
– Application and Desktop Session entitlement
– Location
– Use Case
• Establish User Requirements:
– Remote access
– Printing
– Drive or Communication Port Redirection
– Preferred client devices
CONFIDENTIAL 17

18. Client Devices and Supporting Systems
• Client Devices
– Devices in use
• Thin Clients
• Zero Clients
• Mobile
• PC
– Planned new devices
– Peripherals (printers, USB)
• Supporting Systems
– Virtual Infrastructure
– Load balancers
– Network
– Storage
CONFIDENTIAL 18

19. Customer Example #1: Printing Company
• Business Goals:
– Single Web Portal for SaaS applications and hosted apps
– Support iPad rollout
– Maintain support for legacy printing systems
• XenApp Infrastructure:
– Version 5.0
– Two Farms / Eight Terminal Servers
– No web interface or load balancing
• Published Applications and Desktop Sessions
– No desktop sessions
– Office 2007 suite to be phased out and replaced by SaaS application
– Need to maintain support for printing press control software which requires serial controller
– Printing press software entitled to groups: Printers, Facilities, and TSAdmins
CONFIDENTIAL 19

20. Customer Example #1: Printing Company (Continued)
• Terminal Servers / RDSH Servers
– Eight Terminal Servers running Windows Server 2003 (TRMSRV1 – 8)
– Location: Ohio Datacenter
– Physical Servers with two dual core CPUs, 32GB RAM, serial controller card
– Two servers: TRMSRV3 and TRMSRV8 have failing components
• Users and User Requirements
– User Groups: Printers and Facilities
– Must support access from corporate LAN and WAN (no remote)
• Client Devices and Supporting Systems
– Must support access from iPad and PCs
– No special client device support required
– No load balancer in use.
– Terminal Servers are physical (no SAN)
CONFIDENTIAL 20

21. Solution Example #1: Printing Company
• Implement VMware Workspace Portal to support SaaS application initiative
• Keep XenApp 5.0 and 2003-based Terminal Servers to support legacy printing software
• Integrate XenApp with the Workspace Portal
• Phase out Office 2007
• Decommission four Terminal Servers (TRMSRV3, 5, 7 and 8)
CONFIDENTIAL 21

22. Customer Example #2: Law Firm
• Business Goals:
– Single vendor for VDI and hosted apps
– Support merger with smaller firm that uses XenApp
– Phase out San Francisco datacenter
• XenApp Infrastructure:
– Versions 6.0 and 6.5
– Six Farms / 24 RDSH Servers (16 running XA 6.0, 8 on 6.5)
– Two Citrix Web interfaces and load balancers in use
• Published Applications and Desktop Sessions
– Three desktop session profiles: lawyer desktop, support staff desktop, IT desktop
– Office 2010 and 2013 (2010 being replaced)
– Time keeping software
– Legal research software
CONFIDENTIAL 22

23. Customer Example #2: Law Firm (Continued)
• 24 RDSH Servers
– Four running Windows Server 2008
• SVR2008-36,39,40 and 41
• eight CPUs, 64 GB RAM each
– 14 running Windows Server 2008 R2
• SVR2008-72 – 85
• eight CPUs, 64 GB RAM each
– Six running 2012 R2
• SVR2012-11 – 16
• sixteen CPUs, 128 GB RAM each
– All RDSH servers are virtual (vSphere 5.1)
– Locations:
• New Jersey (half of the 2008 R2 RDSH and all 2012 RDSH)
• San Francisco (all 2008 RDSH and half of the 2008 R2 RDSH)
– Customer plans to deploy six new RDSH servers running 2012 R2
CONFIDENTIAL 23

24. Customer Example #2: Law Firm (Continued)
• Users and User Requirements
– User Groups: Lawyers, Support Staff, IT
– Must support access from corporate LAN, WAN and remote via VPN
– Network printing
• Client Devices
– Must support access from all major tablets and smartphones (IOS, Android)
– Must prevent access to local drives and USB-based storage
• Supporting Systems
– F5 load balancer
– vSphere 5.1 Infrastructure
– View 5.2 for Virtual Desktops in New Jersey datacenter
CONFIDENTIAL 24

25. Solution Example #2: Law Firm
• Upgrade Horizon View 5.2 to Horizon 6 in New Jersey datacenter
• Deploy VMware Workspace Portal in NJ to replace Citrix Web Interface
• Migrate New Jersey XenApp infrastructure to Horizon
• Deploy eight new RDSH running Windows Server 2012 R2 to NJ datacenter
– Two to replace the Server 2008 based systems and six for additional capacity
– New servers will be deployed with Office 2013 to replace Office 2010
• Phase out San Francisco RDSH Servers
• Decommission XenApp and Citrix Web Interface
CONFIDENTIAL 25

26. Best Practices, Gotchas, Things to Consider
• Use Workspace Portal to facilitate the Migration
– Provides “front end” to make XenApp migrations seamless to end users
– First integrate Workspace with XenApp then Migrate to Horizon
• Choosing the best migration approach
– Is the simple way always the better way?
– Gradual vs. one-time migrations
• Garbage Out, Garbage In
– Moving problems from Citrix XenApp into Horizon 6
• Feature & functionality parity
– Wants versus Needs
– 3rd party integration may be required to bridge feature/functionality gaps
CONFIDENTIAL 26

27. Best Practices, Gotchas, Things to Consider
• Common to have multiple XenApp environments
– Typically aggregated with Citrix Store Front or Web Interface
– Workspace Portal and Integration Broker support multiple farms
• Hybrid XenApp and Horizon View environments
– In most cases, plan on XenApp sticking around…
• Should XenApp farms match Horizon 6 with View RDS Farms?
– Application silos and load-managed server groups
– Putting “all the apps” on every server – is this the right thing to do?
– Consolidate multiple XenApp versions on fewer Horizon RDS Farms
CONFIDENTIAL 27

28. Best Practices, Gotchas, Things to Consider
• VMware Workspace Portal does not support XenDesktop
• VMware Workspace Portal does not proxy or tunnel XenApp
• Netscaler load balancers can be used for Horizon
• Don’t forget Horizon View maximums
– Large environments using desktops & applications may exceed Pod limits
– Cloud Pod Architecture currently not supported in HWS
• Optimize the RDSH Servers
– Makes a difference – implement RDS optimization best practices
CONFIDENTIAL 28

29. Announcing the Citrix XenApp to VMware Horizon Migration Tool
29
MS RDSH Servers with XenApp 5, 6 or 6.5
and the VMware Horizon 6 Agent for View
CONFIDENTIAL

30. Citrix XenApp to Horizon 6 Migration Tool
• Automatically creates View RDSH Farms
and Application Pools
• Can also migrate to existing RDSH Farms
• Option to verify applications on each RDSH
• Supports Citrix XenApp 5.0, 6.0 and 6.5
– Also supports mixed 4.5/5.0 farms
• Requires Oracle Java JRE v7
• Install tool on one host in each XenApp
Farm
CONFIDENTIAL 30

31. Migration Demo #1: Automatically Migrate XenApp 6.0 to Horizon
31
Citrix XenApp 6.0
Windows Server 2008 R2
Horizon View 6
Connection Servers
RDSH Farm
In Easy Mode, the Migration Tool
automatically creates the RDSH Farm,
then copies the application and desktop
configurations plus user entitlements.
CONFIDENTIAL

32. Migration Tool Demo Video #1
32

33. Migration Demo #2: Migrate Application to Existing Farm
33
Citrix XenApp 5.0 and 4.5 (mixed farm)
Windows Server 2008 (non-R2) and 2003
Horizon View 6
Connection Servers
Existing RDSH Farm
Window Server 2012
In Advanced Mode, the Migration Tool
Is able to selectively migrate application
and desktop configurations plus user
entitlements to existing RDSH Farms
CONFIDENTIAL

34. VMware Operating System Optimization Tool
• Automates optimizing virtual desktops and Microsoft RDSH Servers for Horizon View
• Based on VMware’s OS Optimization Guides
• Tunes Windows and disables unnecessary services and features
• Templates for Windows 7 and 8 and Windows Server 2008 and 2012
• Templates can be customized
• Supports local and remote systems
• Get it here: https://labs.vmware.com/flings/vmware-os-optimization-tool
CONFIDENTIAL 34

35. Děkuji za pozornost