1. Successfully Migrating Your XenApp 6.5 Farm to XenApp 7.6
Good morning everyone and thanks for getting up early. I hope everyone has had their caffeinated beverage of choice, coffee, Monster or Red Bull. And no, I don’t mean Red Bull and Vodka .
Welcome to Citrix Synergy This presentation will be covering Successfully Migrating Your XenApp 6.5 Farm to XenApp 7.6
Intro: My name is Kevin Rowell. I am an Escalation Engineer for XenApp and XenDesktop. I have been on the frontlines of support with Citrix for almost 4 years.
During the last quarter of 2014, I was part of the XenApp 6.5 migration project we code name Project Serenity.
As we work thru the presentation, start thinking about your environment, and note any questions you want to bring up. This is a live stream and is also being recorded.
There will be time for you to ask questions at the end of the presentation and we can meet outside to continue with the discussion.
Kevin Rowell - XenApp and XenDesktop Escalation Engineer
Citrix Synergy 2015 – Orlando, Florida

2. Benefits of attending this session
Best Practices for a successful migration
The focus of today will be best practices and provide solutions to the road blocks you will most likely face during a migration from XenApp 6.x to XenApp 7.6.
I have broken this down into three basic sections
Best Practices
Powershell and the Migration scripts
And finally…
Upgrading your XenApp 6.5 hosts
PowerShell and migration scripts
Upgrading XenApp 6.5 Hosts

3. Best Practices, Planning and Preparation
A Healthy DataStore
Migration Scripts
By a show of hands, who is familiar with the importance of building on a solid foundation?
With XenApp this starts with a healthy datastore.
You also need to understand how the migration scripts work.
And what can be migrated.
This will let you properly plan your migration and have a positive outcome.
What is Migrated?

4. A Healthy Datastore IMAHelper Tool Invalid Server Entries Empty Zones
The DataStore is the foundation of XenApp 6.5, so we need to ensure it is in good working order before proceeding any further.
To check your datastore use the IMAHelper tool and the Master Check function.
The Master Check will produce a text report for you to inspect.
Review this and ensure there are no errors and invalid entries as these can cause the export to fail prematurely.
The common entries that will stall an export are:
<>
Invalid server entries
And empty zones
But, you are in luck, the Project team added clues to the command line that will help you in determining your next steps to alleviate any road blocks with the exports
Empty Zones

5. Invalid Server Entries
:34:18:093 Exporting application “Outlook 2013"
:34:18:125 Cannot find server with id 596b-000c b3 (0x Entry not found.)
Let’s take a look at the invalid server entry.
When first attempting the export using the sample datastore, it failed on an invalid server entry.
<>
Here are the last few lines of the log file when the export failed because of the invalid server entry. <> And then aborted.
We ran the Master Check function of the IMAHelper tool and identified the invalid entry.
We next used DSCHECK /Full Servers /clean to remove the invalid server entry. The IMA Helper tool also has the clean function built in, but I wanted to show that this error could be tackled using the command line as well.
:34:18:140 Exporting applications aborted

6. Invalid Zones
:07:24:326 Exporting worker group “AREA_NONPROD_REL"
:07:24: worker groups exported
:07:24:357 Exporting zones
:07:41:002 Error getting data collector for zone AAZONE (0x802D0006)
Next we move on to cover the empty zone error.
In this example the datastore contained an empty zone named AAZONE
<>
This caused the export to fail.
As mentioned earlier, the scripts do contain some clues as to how to resolve the error, as the last entry specifies using the –IgnoreZone switch.
In the example above, using the –IgnoreZones switch allowed the export to complete.
Zones are not used in XA 7.6 and therefore not needed during the import and can be safely ignored for the purposes of getting the data our of the XenApp 6.x farm.
:07:41:002 Exporting zones aborted, you may consider to use the -IgnoreZones switch to work around this problem

7. It is also a recommendation that your XenApp farm be at the latest Hotfix Rollup and Group Policy Modules. Using the CIS site you can quickly identify which hotfixes are recommended as well as gauge the overall health of your farm.
A free offering to help keep your Citrix environment running well.
Over 400 plugins that detect various conditions and offer prescriptive advice. New ones added every week.
Previously known as Tools as a Service (TaaS).
Visit the Citrix Insight Services Team in the Expo Hall to learn more and receive a free gift (while supplies last)

8. Migration Script Concepts and Steps
Policies
Export – XenApp 6.x (IMA)
XenApp Farm (XAFarm)
Import – XenApp 7.6 (FMA)
There are two main object groups for the migration.
Policies and..
<>
XenApp Farm data or XAFarm as it will be referenced though out the presentation, contains the applications, worker groups, servers, etc…
The actions for the migration are broken into two distinct parts:
Exporting from your XenApp 6.x IMA farm and …
Importing into your XenApp 7.6 FMA site.
Let me also define these terms. IMA stands for Independent Management Architecture. FMA stands for FlexCast Management Architecture.

9. The Export Script Modules
The Migration Scripts are broken into two packages based on the action of Export or Import. Both can be downloaded from the Citrix website.
For the Export, the package is ReadIMA.zip
This package contains the PowerShell scripts used to export the:
Policy data and..
The XAFarm data (Apps, servers, workergroups,etc…)

10. Important Files Created by the Export
Do NOT edit the PowerShell scripts or XML files
There are three main objects created during the export. The Policy output, the XAFarm output and the icon data folder.
<>
For the Policy object, an xml file is created to contain the output. In this example the –OutputXmlFile specified was policy.xml.
Following the same logic, the XenApp Farm data creates an XML file specified with the same switch – OutputXmlFile: xafarm.xml
The export scripts output the icon data to the icon data folder.
The folder name is pre-pended with the XML file name used in the Export-XAFarm command data.
You can also embed the icon data in the XML file by using the –EmbedIconData switch
A little history, the XML file from previous versions of XenApp migrations was originally designed to be chopped up as needed by the customer.
In this version, we imbedded the icon files in the XAFarm XML file to use with the automation tools in the Project Serenity site
Because of this, we no longer support editing of the XML file or modifying the powershell scripts.

11. The XenApp Import Script Modules
For the Import to XenApp 7.6, the package is ImportFMA.zip
This package contains the PowerShell scripts used to import the:
Policy data and..
The XAFarm data (Apps, servers, workergroups,etc…)

12. Powershell Essentials
Now that we have covered some of the foundational concepts and steps of a successful migration, let’s move into PowerShell.
Part of Project Serenity, we worked with volunteer administrators of varying levels of PowerShell knowledge. This section is based off of the observations and feedback we received.

13. PowerShell Prerequisites
The Export Scripts MUST be run on a XenApp 6.5 controller
The Import Scripts MUST be run a XA7.6 controller (DDC)
The Export scripts MUST be run from a XA6.5 Controller, the ZDC being recommended. ZDC is short for Zone Data Collector.
The Import Scripts MUST be run on a XA7.6 DDC, which stands for Desktop Delivery Controller.
Must be run under UAC Admin context for proper OS level permissions.
Run As Administrator when launching PowerShell

14. Setting Up Your PowerShell Environment
Do NOT load the XenApp SDK Snap-in:
Asnp Citrix.*
Set-ExecutionPolicy Unrestricted
The PoweShell (PoSH) execution policy must be set to unrestricted (or AllSigned or RemoteSigned depending on your environment)
<>
Graphic
Important NOTE: The XenApp SDK (Software Development Kit) snapin is automatically called when the Export/Import modules are imported. so do not run this a second time. (Asnp Citrix.*)
Loading the snap-in will cause the scripts to fail.

15. Execution Mode Warning
The default action is to NOT run. Be Aware
Depending on the server environment, the user may be prompted to manually allow the scripts to execute.
This is benign and if the Run Once option is chosen the scripts should still run
<>
The Default action is to NOT run. Be aware and choose the R or run option

16. Exporting Data Getting the Data Out of XenApp 6.x
Now that we know how the environment needs to be setup we can move on to moving the bits out of the XenApp farm.
Getting the Data Out of XenApp 6.x

17. Setting Up PowerShell Set-ExecutionPolicy
Using the tab key will help with syntax errors as PoSH will attempt to prefill the commands.
As shown earlier, prepare PoSH by setting the execution policy
<>
Helpful Tip: Using the tab key will help with syntax errors as PoSH will attempt to prefill the commands.
Unrestricted, AllSigned & RemoteSigned

18. Using the Import-Module Command
Using the tab key will help with syntax errors as PoSH will attempt to prefill the commands.
Don’t get confused by the Import-Module!
Import-Module PowerShell Command
To enable the scripts use the native PoSH command “Import-Module”
Importing these modules enables the Citrix SDK and makes the Scripts active for use.
<>
DON’T GET CONFUSED. During the import phase of the migration on XenApp 7.6 you will use the Import- Policy and Import-Xafarm commands whose syntax is very similar.
The Import-Module is a native PoSH command used to bring in script modules, such as the XenApp Migration Scripts.
Helpful Tip: Again, I will stress the use of the tab key will help with syntax errors as PoSH will attempt to prefill the commands.

19. Basic Export Policy Command
Get-Help Export-Policy -Full
Export-Policy -XmlOutputFile policy.xml -LogFile exportpol.log
You must specify an XML output file and will be prompted if the –XmlOutputFile switch is not specified in the command
<>
The logfile is not a requirement, but for troubleshooting it is invaluable.
Use the Get-Help powershell command for full details and examples.

20. Policy Export Help

21. Basic XAFarm Command Syntax
Export-XAFarm -XmlOutputFile xafarm.xml -LogFile exportxaf.log
Again, you must specify an XML output file. As we saw in the Export-Policy example, the system will prompt you to enter one when you execute.
<>
The logfile is not a requirement, but for troubleshooting it is invaluable.

22. XAFarm Export Help Get-Help Export-XAFarm -Full
Use the Get-Help Export-XAFarm –Full powershell command for full details.
This will include parameter/switch list with descriptions and multiple examples.
You will notice the XAFarm Export module is much more verbose.

23. Export Commands XAFarm Filters
-IgnoreAdmins
-IgnoreServers
-IgnoreZones
IgnoreAdmins - Do not export administrator objects (Admins are not an importable object in 7.6)
IgnoreServers - Do not export server objects ***note that having servers in the xml file will be helpful during the import phase when filtering applications depending on your environment.
IgnoreZones - Do not export zone objects (Zones are not an importable object in 7.6)
IgnoreOthers - Do not export configuration logging, load evaluator, load balancing policy, printer driver, and worker group objects. This option was included so that you can proceed with an export when an error exists that would not affect the actual data being used for the import. ***The worker group object needs to be evaluated if used in your environment.
IgnoreApps - Do not export applications; this allows you to export other data to an XML output file and then run the export again to export applications to a different XML output file.
You can also use these parameters to work around issues that could cause the export to fail. For example, if you have a bad server in a zone, the zone export might fail; if you include the -IgnoreZones parameter, the export continues with other objects.
-IgnoreOthers
-IgnoreApps

24. Export Examples From the XenApp 6.x Datastore
Ok, we have covered the scripting files and the basic syntax. Next, I will walk through a few examples of an export. This will include aborted exports mentioned in the healthy datastore section from earlier.
From the XenApp 6.x Datastore

25. Basic Policy Export
Export-Policy –XmlOutputFile policy.xml –Logfile exportpol.log
This first example is a basic Export of the policies.
You will see as highlighted how many objects were processed.
This is also reflected in the log file.

26. Basic Export of Farm Data
Export-XAFarm –XmlOutputFile xafarm.xml –LogFile xafarm.log
This is the basic export command syntax for farm data.

27. Working Around Export Errors
Export-XAFarm –XmlOutputFile xafarm.xml –LogFile exportxaf.log –IgnoreZones
I want to pause briefly here to discuss the XAFarm Export switches. These are mainly available to working around failed export problems. The following example is important because empty zones will cause the export to abort. Using the –IgnoreZone switch should be used in this case to complete the export and move on to the import stage. The other switches we covered can be used in the same manner.

28. Importing Data To the Newly created XA 7.6 Site
Getting the exported configuration data into XA 7.6
To the Newly created XA 7.6 Site

29. Replaced Technologies
Published Desktops
Administrators
Published Content
What gets imported or rather what does not get imported
These Farm objects no longer exist or do not have an equivalent object in XenApp 7.6
Because XenApp 7.6 allows for a richer variation for admin levels, it was a design choice not to attempt to move Administrators.
Streamed Apps
Application Servers
Pre-Launch Apps

30. Planning Your Computer Policy Import
Health Monitoring
Memory Optimization
Load Evaluators
Prompt for Password
For a Comprehensive list visit Citrix eDocs
UNFILTERED policies are Never imported.
When planning your new XenApp 7.6 site, you must understand what objects are not importable.
These objects are highlights of the Computer Policy Objects that do not have a matching component in XenApp 7.6.
To find a complete list of Computer Policy objects that are not imported please refer to out eDocs.
Use this list in your planning phase to craft a successful migration.
NOTE: UNFLITERED policies are Never imported. The features and components that support these settings have either been replaced by new technologies/components or the settings do not apply because of architectural and platform changes.
License Information
Reboot Schedules
Limit Sessions
Virtual IP

31. Planning Your User Policy Export
Auto connect ports
Linger timers
Only policies created in AppCenter are imported.
COM and LPT ports
Shadowing
For a Comprehensive list visit Citrix eDocs
As with the computer policy export, it is good to know what policies will not be available in the new XA7.6 site.
These objects are highlights of the User Policy Objects that do not have a matching component in XenApp 7.6.
To find a complete list of User Policy objects that are not imported please refer to out eDocs.
As before, use this list in your planning. This will help with having a XA7.6 site that functions as you envision.
<>
NOTE: Only policies created in AppCenter (stored in the IMA datastore) will be imported. Policies managed thru Windows AD GPOs will not be imported.
Client printer names
Pre-launch
Citrix polices created in Windows GPOs are NOT imported
Concurrent logon limit
Single Sign-On

32. Policy Filter – Special Considerations
Access Control
Client IP Address
The policy filters will need special attention so that resources are assigned correctly.
The Access Control and Citrix CloudBridge policy filters should work without any changes.
The filters highlighted in orange: Client IP Address, Client Name and OU may require changes to prevent polices from being applied incorrectly.
As stated previously, Worker Groups are not supported in the FMA architecture. These filters will need to be removed and adjusted as required by your environment.
Worker Group
Citrix CloudBridge
Client Name
Organizational unit

33. Getting Ready to Import
Step 1: Install XenApp 7.6 DDC
First you will need to install a new XA7.6 DDC
<>
There must be a location to send all the data, so create a new site
This site does not need to have any Delivery Groups or Machine Catalogues before importing, but does need to be configured as an active site (SQL configured, licensing set and the site tested).
In the following examples, you will see that a delivery group name can be set during the import. The scripts will automatically create a new DG and add the applications to the DG.
Step 2: Configure a basic site

34. Step 3: Copy Exported The Important Files
We next need to copy the two XML files and the icon folder from the XA6.x controller to the newly setup XA7.6 DDC.
Here you can see the xafarm-icons folder along with the policy.xml and xafarm.xml files in the ReadIMA folder on the XA 6.5 server. <>
These are copied to the ImportFMA folder where the migration scripts reside on the XA7.6 DDC.
**Notice the file size of the xafarm.xml file is 121kb.
If the –EmbedIconData switch is used on export or the Project Serenity GUI is used the icon folder will no longer be resident.
**Notice the file size of the xafarm.xml file is 7.5MB with the embedded data.
<>
Now that the export data is on the XA7.6 ddc we can start the import process.

35. Step 4: Run Import Script
Copy Files to XA7.6 DDC
Now that the export data is on the XA7.6 ddc we can start the import process.
Step 4: Run Import Script

36. Setting Up the PowerShell Environment
Import-Module .\ImportXAFarm.psd1
The default action is to NOT run. Be Aware
Once the export files are copied to the ImportFMA folder on the new XenApp 7.6 DDC, you can begin the import.
As we covered earlier, prepare the PowerShell environment on the DDC by running the Set-Execution Policy and importing the Citrix Import modules using the PowerShell native command Import-Module.
NOTE: Don’t forget the security warning prompts. The default action is to not run and will cause the scripts to fail. Always choose R to run the scripts.
Import-Module .\ImportPolicy.psd1

37. Policy Import Example
Import-Policy –XmlInputFile .\policy.xml –LogFile importpol.log
The policy import will be fairly straight forward, taking into account those polices which are not supported.
The Unfiltered polices will not be imported due to new technologies and/or the settings do not apply because of architectural changes.

38. Planning The Import Don’t overcomplicate the import.
A moment to emphasize the planning stage ……
Tip: Don’t overcomplicate the import.
Plan your new FMA site using the import filters and the Project Serenity site. This will require you to run multiple imports changing the filter as laid out in your plan.
It will be better to perform 20 individual import commands than trying to cram it all in one batch script and then try to trouble shoot the errors of your batch file.

39. Import Examples Import-XAFarm -XmlInputFile .\xafarm.xml
-LogFile importxaf.log
-MatchWorkerGroup "Adobe"
-DeliveryGroupName "Adobe"
One of the most common filters will be an Import based on Worker Groups using the [-MatchWorkerGroup] switch
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf.log -MatchWorkerGroup "Adobe" - DeliveryGroupName "Adobe“
This is one of the most useful filters when porting the XAFarm data. Paring this with the – DeliveryGroupName all apps associated with the specified worker group will be place in the new specified delivery group.
The logic of using the –MatchWorkerGroup switch can be applied to some of the other filter switches we will cover shortly.

40. Match Worker Group to Delivery Group
In AppCenter you can see that the Adobe published apps are assigned to the “Adobe” Worker Group.
In the log you can see the non-matching apps getting skipped
Notice during the export that the Word application was skipped as it was disabled. This is the default action for disabled apps. Using the [–IncludeDisabledApps] switch will allow all disabled apps to be imported.
In the log and during the import you will see the import of the matching workergroup apps.

41. Match Worker Group to Delivery Group
The highlighted area shows the admin folder and app creations for “TEST - Adobe Photoshop CC”
Once the command completes, you can open Studio and refresh to see the new delivery group and apps.

42. Using the –MatchAccount Switch
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf_hr.log -DeliveryGroupName “HR" - MatchAccount “HR”
In this example, we used the –MatchAccount filter with the –DeliverygroupName switch to create and specify the target DG.
Any applications that have the AD group “HR” assigned to them will be put into the newly created DG called “HR”
Import-XAFarm -XmlInputFile xafarm.xml
-LogFile importxaf_hr.log -DeliveryGroupName “HR"
-MatchAccount “HR”

43. One to One Account Match
Running the import command, the completed output in PoSH shows that three apps (highlighted red) were created.

44. One to One Account Match
4 total applications were imported. The forth was published Explorer and was in a different folder structure in AppCenter but in the same Delivery Group “HR”.

45. Many to One Account Match
Import-XAFarm -XmlInputFile xafarm.xml
-LogFile importxaf_Sales-Marketing.log
-MatchAccount "(Sales|Marketing)”
-DeliveryGroupName "Sales-Marketing"
In this example, we used the –MatchAccount filter with the –DeliverygroupName switch to create and specify the target DG. Using the regular expressions, the –MatchAccount switch will look for all apps that have assigned groups in the Sales or Marketing groups. Then port these into the Sales-Marketing DG.

46. Many to One Account Match
Notice the use of Regular Expressions
The characters ( ) and | are regular expression meta-characters. The | means “one of” and the strings inside the () are the choices for |.
In this example, we used the –MatchAccount filter with the –DeliverygroupName switch to create and specify the target DG. Using the regular expressions, the –MatchAccount switch will look for all apps that have assigned groups in the Sales or Marketing groups. Then port these into the Sales-Marketing DG.

47. Many to One Account Match
Viewing the AppCenter you can see the assigned groups for the apps

48. Many to One Account Match
Notice the use of Regular Expressions
The characters ( ) and | are regular expression meta-characters. The | means “one of” and the strings inside the () are the choices for |.
In this example, we used the –MatchAccount filter with the –DeliverygroupName switch to create and specify the target DG. Using the regular expressions, the –MatchAccount switch will look for all apps that have assigned groups in the Sales or Marketing groups. Then port these into the Sales-Marketing DG.

49. One to One Folder Match
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf_folder.log -DeliveryGroupName "TestFolder" -MatchFolder "Test,Folder”
In this example, We are matching the contents of the Test,Folder folder structure using the –MatchFolder switch, create a Delivery Group named ‘TestFolder’ and place all apps that match the expression into this DG.

50. One to One Folder Match
The command runs and the Test,Notepad app is imported.
In AppCenter you can see the folder structure and the nested app

51. One to One Folder Match
Refreshing Studio, the new TestFolder DG appears with one app assigned.
Clicking the Applications tab you can see the Test,Folder in the nested the same way it was in AppCenter along with the imported app Test,Notepad.

52. Many to One Folder Match
Import-XAFarm -XmlInputFile xafarm.xml
-LogFile importxaf_MultiFolder.log
-DeliveryGroupName "Admins"
-MatchFolder "Applications/(Admins/Citrix|Admins/MS Tools)"
Notice the use of Regular Expressions
The characters ( ) and | are regular expression meta-characters. The / is not a meta-character. The | means “one of” and the strings inside the () are the choices for |.

53. Many to OneFolder Match
Here is the completed import using the –MatchFolder switch choosing multiple folders using the regular expressions. You can see the highlighted areas that show the applications getting created.
In Studio we can refresh and see the new delivery group “Admins” was created and it contains 3 applications.
Under the Applications tab we can see the original folder structure of AppCenter has been retained.

54. Many to One Folder Match
Here is the completed import using the –MatchFolder switch choosing multiple folders using the regular expressions. You can see the highlighted areas that show the applications getting created.
In Studio we can refresh and see the new delivery group “Admins” was created and it contains 3 applications.
Under the Applications tab we can see the original folder structure of AppCenter has been retained.

55. Using the -MatchServer Switch
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf_server.log
-DeliveryGroupName “ServerXA4" -MatchServer “FTL-MIG-XA4"
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf_multiserver.log
-DeliveryGroupName “ServerGroupB" -MatchServer “(FTL-MIG-XA2|FTL-MIG-XA4)"
You may have apps assigned only to a single or group of servers.
You can user the –MatchServer switch to import these to an appropriate DG.
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf_server.log -DeliveryGroupName “ServerXA4" - MatchServer “FTL-MIG-XA4"
Import-XAFarm -XmlInputFile xafarm.xml -LogFile importxaf_multiserver.log -DeliveryGroupName “ServerGroupB" -MatchServer “(FTL-MIG-XA2|FTL-MIG-XA4)"

56. Upgrading XenApp 6.5 Hosts

57. In-Place Upgrade Recommendations and Prerequisites
Backup your XenApp 6.5 server host before upgrade!!!!!
Session-mode only XA 6.5 servers are valid for in-place upgrades
To upgrade XenApp 6.0 server, first update to XA6.5 Session-mode only host.
I want to take a quick poll from the audience.
By a show of hands, who thinks it would be a prudent step to either snapshot or backup the XenApp host that has 16+ man-hours invested in installation and configuration?
<>
Only XenApp 6.5 session-only hosts are eligible for an in-place upgrade to XA7.6 VDA.
To upgrade XA6.0 you must upgrade to XA6.5 Session-mode only host

58. Session-Host Only!!
Check in AppCenter to see if the XenApp server is a session-only mode server. If the Session-host Mode = enabled.
You can switch the Session Host mode using the Role Manager.
Start the XenApp Server Role Manager
Remove the server From the Farm
After reboot, Start Role Manager and click Configure
Click Add this server to an existing server farm.
Select the appropriate database and shadowing options.
On the Data Collection Options choose “Enable Session-Host mode only”
Note the Session host only dialogue.

59. In-Place Upgrade Known Issue
Log files can be found in the following folder:
"%TEMP%\Citrix\XenDesktop Installation\XenApp 6.5 Uninstall Log Files\"
"Error An error occurred while plugging XML into Internet Information Server. Setup cannot copy files to your IIS Scripts directory. Please make sure that your IIS installation is correct."
Troubleshooting
There is known error in the uninstall portion of the XA6.5 upgrade.
You will see the error in the uninstall log.
This occurs because XML was set to share with IIS during the initial install and .NET was installed.
Cause: The issue occurs on systems where (1) during the initial XenApp 6.5 installation, you indicated that the Citrix XML Service (CtxHttp.exe) should not share a port with IIS, and (2) .NET Framework is installed.

60. Resolution
Remove the Web Server (IIS) role using the Windows Remove Server Roles wizard. (You can reinstall the Web Server (IIS) role later.)
Restart the server.
Using Add/Remove Programs, uninstall the following:
Citrix XenApp 6.5
Microsoft Visual C Redistributable (x64), version
To resolve this uninstall failure, remove the web srever role and reboot.
Next, uninstall Citrix XenApp 6.5 AND Microsoft Visual C Redistributable (x64), version
Restart the server
Then run the XA7.6 Virtual Desktop Agent (VDA) installer for the Server OS.
Restart the server.
Run the XenApp 7.6 installer to install the VDA for Windows Server OS.

61. Automate the process with Project Serenity
I have mentioned Project Serenity throughout this presentation and wanted to highlight some of the exciting aspects of this tool.
Serenity is and online automation tool that will assist you in planning and filtering your migration with the use of an online GUI.
I want to touch on the most exciting and useful aspects of this new tool.
Automate the process with Project Serenity

62. You can create your project and mange your migration.

63. Here you can see the checklist as well as the download location of the most up-to-date migration scripts.
The checklist follows the same actions we covered today and automates many of the command-line actions.

64. Find Out More www.citrix.com/xenapp/upgrade
Citrix Life Cycle Management Agent
Demo and Questions? Visit the Workspace Experience Booth in the Expo Hall
You can find out more and see a demo in the Expo Hall

65. Summary
Let’s review the main points I covered.

66. Common PowerShell Mistakes
NOT setting the execution policy for PoSH
NOT importing the Migration scripts (Import-Module)
NOT copying the generated XML files and icon folder to the target DDC
Some common mistakes when using PowerShell and the scripts.
NOT specifying a Delivery Group on import
– this will dump all farm settings into a single Delivery Group.

67. In-Place Upgrade Hurdles
NOT taking snapshots or backups
Session-mode Only XenApp Hosts
Common mistakes when performing an in-place upgrade of the XenApp 6.5 hosts.
Not backing up or snap shotting prior to the in-place upgrade
Possible In-Place Upgrade Failures

68. 3 Key Takeaways Understand PowerShell Basics Understand the Scripts
Powershell will provide its own hurdles depending on your PoSH skill level.
<>
Get to know and understand how to use the filter switches to best group the farm objects in their new home.
Leverage Project Serenity to take out some of this guesswork with the scripts.
Plan, Plan Plan!! Leverage the Project Serenity site to create you plan.
It is highly recommended that you sandbox the export/import prior to a test environment to help understand how the scripts work.
Plan and Test

69. Resources
Links and Documents

70. Resources
My Blog: Migrating Made Easy Project Serenity IMA Helper Tool
Product Documentation (eDocs)
Session-Only Hosts
DSCHECK
My Blog: Migrating Made Easy
Product Documentation (eDocs)
Project Serenity
IMA Helper Tool
DSCHECK
Session-Only Hosts

71. Questions? ? ? ? ? ? ? ? ? ? ? ? ?

72. Before you leave…
Conference Surveys are available online at starting Thursday, May 14 at 9:00 a.m.
Those who provide feedback by 6pm, Friday, May 15th will receive:
$20 Amazon e-gift card
Name entered in a drawing for a free Trip to Synergy 2016 (5 chances)
Download presentations starting Monday May, 18th from the My Event Planning tool