Migrating to the latest version of XenApp. Alfons Steger, Senior Systems Engineer CE Rob Sanders, Product Specialist Desktop Virtualisation EMEA

Transcription

1 Migrating to the latest version of XenApp Alfons Steger, Senior Systems Engineer CE Rob Sanders, Product Specialist Desktop Virtualisation EMEA

2

3 Agenda Why? How? Now What? Keep in mind!

4 Why?

5 Migration strategy prior to XenApp 6 XenApp v.existing Web Interface Mixed-mode XenApp v.new Join farm with new server to create mixed-mode farm Web Interface will automatically point users to new servers Transfer roles to new servers Decommission old servers

6 Architectural changes Changes to the core foundation Microsoft changed the Terminal Services foundation between Windows Server 2008 and Windows Server 2008 R2 Huge impact on APIs that XenApp was built upon Introduction of Worker/Controller architecture Introduced under the covers in XenApp 6.0 Extended and fully implemented in XenApp Iron Cove

7 Worker/Controller model Controller role Similar XenApp to XenApp 6 and 6 server earlier Full IMA stack All servers XML Service are identical Every Data Collector server receives functionality all dynamic farm data Every server Worker can role trigger a farm RDS election Session and Host become only a Zone Data Collector Reduced IMA stack Data No Store XML becomes Service bottleneck No Data Collector functionality

8 How?

9 Migration strategy since XenApp 6 XenApp v.existing Web Interface XenApp v.new Create new farm Aggregate farms in Web Interface Migrate settings and applications Decommission old farm

10 Introducing the XenApp Migration Center Migrate settings from one XenApp farm to another Perform a full migration or select settings to be migrated Two migration techniques Direct: Export settings in one step from source farm to destination farm Indirect: Settings from the source farm are exported in XML files and later imported in the destination farm Direct migration is recommended Network connection between source and destination farm Same farm administrator credentials in both farms

11 Release history XenApp Migration Center v1 Migrate to a XenApp 6.0 farm PowerShell cmdlets only, no GUI XenApp Migration Center v2 Migrate to a XenApp Iron Cove farm Extended PowerShell cmdlets GUI for simplified migration options

12

13 Source farm requirements Supported XenApp versions XenApp 5.0 on Windows Server 2003 with HRP5 XenApp 5.0 on Windows Server 2008 XenApp 6.0 on Windows Server 2008 R2 XenApp Iron Cove on Windows Server 2008 R2 Farm administrator account with view-only permissions Full administrator permissions are recommended DCOM Group Access

14 Additional requirements for source farms Direct migration Network COM+ access Indirect migration.net Framework 3.5 SP1 MSI 3.0 PowerShell

15 Destination farm requirements XenApp Iron Cove farm Farm administrator account with full administrative rights Domain admin account highly recommended Local Admin or Power User accounts will work Write access needed to working directory C:\Users\<username>\AppData\Local\Citrix\Citrix.XenApp.Migration Migration data and log files resides here

16 Working directory C:\Users\<username>\AppData\Local\Citrix\Citrix.XenApp.Migration Data XML files containing the data for each object type Logs XML and text log files of the migration processes UILogs Logs from the Migration Center MigrationOptions.xml Configuration settings (Delete to start fresh)

17 Installation for indirect migration Install Migration Center on source server The tool needs to be installed from the media \Administration\Delivery Services Console\setup\Citrix.XenApp.Migration.Install_x64.msi \Administration\Delivery Services Console\setup\Citrix.XenApp.Migration.Install_x86.msi Migration Center GUI application can only be used from the target XenApp Iron Cove server Use the PowerShell cmdlets to export the settings from the source farms

18 Architecture Source Environment Target XenApp Iron Cove Environment XenApp /2008 MFCOM Server MFCOM XenApp MFCOM Exporter XenApp Migration Application XenApp Migration Commands XenApp 6.0 and Iron Cove XACOM Server XACOM XenApp XACOM Exporter = PowerShell XenApp PowerShell Importer XenApp Commands

19 What can we migrate with all XA versions? The following items may be migrated with any supported version of XenApp used for the source farm Applications Application and server folders Load evaluators Policies (IMA/Farm policies only and not GPO policies in Active Directory) Server settings Farm settings Farm administrators HMR tests (Any custom test executables will need to be copied over) Session printers (Printer paths will not be validated)

20 Settings and data that will not migrate Printer drivers and related settings Drivers, driver replication settings, and driver mappings Configuration Logging This is a historical log of administrative changes performed in the legacy farm so there is no reason to migrate this information Server registry settings Seamless flags and other registry settings will not come over Zones This is related to the structure of a farm which is not practical to migrate

21 Settings specific to XenApp 6.0 and Iron Cove Pre-launched Apps Load Balancing Policies Worker Groups XA6 X X Iron Cove X X X Pre-launched Apps Starts an invisible session in the background once the Plug-in/Receiver is launched to facilitate faster launching of published applications Load Balancing Policies Configures preferred servers for users Worker Groups Is a logical collection of XenApp servers that perform a common task or share common settings

22

23 Now What?

24 Post-migration steps Attaching load evaluators to worker groups with policies Associating application folders with published applications Associating servers or OUs with worker groups Assigning server objects to folders Assigning zones Configuring printer settings Setup Configuration Logging within the new farm Copying Health Monitoring and Recovery test executables to new farm

25 Accessing multiple farms Web Interface to aggregate all XenApp farms Modify WebInterface.conf file for greater control Default location: C:\inetpub\wwwroot\citrix\%site%\conf Use Farm#Groups parameter to target a specific farm for specific groups Assign groups to all your farms, not just the new one! Farm1 must be a XenApp 6.0 or newer farm!

26 Keep in mind!

27 Things to keep in mind Direct modifications to the data store The tool should ideally be run during a maintenance window with no users connected to the XenApp Iron Cove farm. As always, data store backups are essential! Published Application paths Application paths will be transferred over exactly as specified in the source farm. If the path specified in the source farm does not exist for the installed applications in the XenApp Iron Cove farm, the applications will not launch. This is especially true for 32-bit XenApp 5 servers and their applications being migrated to 64-bit XenApp Iron Cove. The -X86ApplicationList PowerShell switch may be used to force a x86 path. Tool may be run multiple times as needed Changes to previously migrated settings will be reflected

28 Before starting the migration Update any configured FTAs If the source farm uses file type associations for published applications, ensure they are updated by running the Update file types from registry option in AppCenter. Run DSCheck on the source farm with appropriate switches to ensure consistency DSCheck /full apps DSCheck /full groups DSCheck /full servers DSCheck /full folders DSCheck /full printers

29 Using the GUI versus PowerShell GUI Provides an easy-to-use wizard interface that walks admins through the various steps required to migrate Imports all objects from the source farm Imports all property values for the objects Supports direct migration only PowerShell Provides a series of cmdlets which must be fully understood and executed in the correct order Provides the ability to important all objects from the source farm or selectively include or exclude specific ones Provides the ability to important all property values from the source farm with the option to override if desired Supports both direct and indirect migrations

30

31 PowerShell execution policy (1 of 2) The tool will not start without the proper execution policy and will throw an error from the GUI or PowerShell prompt

32 PowerShell execution policy (2 of 2) Execution policy settings determine what PowerShell modules and scripts can run on the server Restricted (default setting - no scripts will run, only built-in cmdlets) AllSigned (All scripts, local and remote, must be signed) RemoteSigned (Local scripts can run but remote ones must be signed) Unrestricted (Unsigned scripts can run though it will warn for Internet scripts) Bypass (Nothing is blocked and no warnings. Not ideal for production) Run the following statement at both the x86 and x64 PowerShell prompts to set the suggested level Set-ExecutionPolicy AllSigned

33 Best practices Migrate after hours and/or in phases Reading and writing large amounts of farm data (and generating potentially excessive network traffic) is best done with no users connected to either farm. Migrate in a 1:1 fashion A one-to-one mapping with the farms is the only supported use of the tool. That is, while you can technically do it, it is not supported or recommended to migrate settings from multiple source farms into a single destination XenApp Iron Cove farm.

34 Troubleshooting the migration Once the migration process is started, it will typically only fail on one or more objects/sections (it s not a boolean process where it either all works or all fails). Running DSCheck after the migration (especially when troubleshooting) is a good idea.

35 Common issues XenApp is not installed or the installation is corrupt, MFCOM is not running, a DCOM permissions issue is present, a firewall misconfiguration, etc.

36 Known issue with MFCOM After uninstalling the migration tool on a XenApp 5 server the Discovery process fails in the Delivery Services Console This problem is due to the nature of MFCOM registration and will not be fixed (as it is an issue with MFCOM which is deprecated and not the tool itself). To resolve the issue, reinstall the tool or repair/reinstall the Delivery Services Console. CTX outlines the issue.

37 Feedback und Präsentationen Ihre Meinung ist uns wichtig. Bitte nehmen Sie sich einige Minuten Zeit, unseren Online Feedbackbogen auszufüllen. Den Link dazu erhalten Sie einige Tage nach der Veranstaltung. Im Anschluss an den Fragebogen haben Sie Zugriff auf die Downloadseite der Präsentationen.

38