Datastore:
Core data store changes make mixed farms incompatible because of differences between the structure of and communications to a XenApp 6 and a XenApp 5 data store. Consequently, mixed farms will most likely cause data store corruption.
XenApp 6.0 is not capable of contacting an IBM DB2 or Access database.
Management consoles:
The new MMC 3.0 Delivery Services Console only works with XenApp 6.0 and is a requirement – it does not work with XenApp 5.
In addition to all the great features available today, XenApp 6 has the following new features and enhancements:
Citrix Receiver The new Citrix Receiver for Windows supports eight languages with expanded support for plug-ins including Single sign-on, WAN acceleration, App-V and EasyCall. There is a new Dazzle-enabled Receiver for Mac. And for mobile devices, users can use Receiver on iPhone, Android or Windows Mobile to access applications hosted on XenApp 6
Upgrade: Installing a new version of a feature or realise item over an existing version.
Migration: A clean, new installation of that feature or realise item.
What’s that men ? Migration is time consuming because of:
(short version)
We have to create new Citrix farm We have to install new servers We are only able to migrate most Citrix Farm settings. (long version)
We have to create new Citrix Farm.
You can migrate the following XenApp object types.
Object Type Description Application All applications are enumerated; however, for the corresponding worker groupbe associated with the application, the application must be d to one of the servers specified in the server mapping file. hat can be resolved on the server in the new farm (account auth are trusted in the new farm) are migrated.When migratinApp 6.5 test/pilot farm, this includes pre-launched applicationsting from a 32-bit XenApp 5 platform, the application path is not translated.
While migrating from xenapp 5 to xenapp6 using powershell cmdlet, you might get the below error:
Exception calling “Open” with “1” argument(s): “Unable to connect to server: ‘Remote COM+ access is not enabled on the server. Goto the source server(xenapp5 server) and in application server role, install com+ network access role and try again. It will work.
The main sad thing in migrating older xenapp versions to xenapp 6.5 is, mixed farms are not supported in xenapp 6.0, 6.5 and there is no direct upgrade from older versions to 6.5. If you have presentation server 4.5 and you want to migrate to xenapp 6.5, we first need to upgrade to xenapp 5, and then to xenapp 6 and then to 6.5. There is no direct upgrade/migrate to xenapp 6.
Inorder to migrate all your settings, applications, policies etc from xenapp 5 to xenapp 6, we need to install xenapp migration tool from mycitrix.com first. Once downloaded and installed, perform the below steps to migrate all your settings, applications, policies etc.
1. On a XenApp 6 server, install the XenApp 6 Migration Tool
(Citrix.XenApp.Migration.Install_x64.msi), including the option to set the PowerShell execution policy to AllSigned
2. On the XenApp 6 server, access the tool via the Start->All Programs->Citrix->XenApp
The XenServer Disaster Recovery (DR) feature is designed to allow you to recover virtual machines (VMs) and vApps from a catastrophic failure of hardware which disables or destroys a whole pool or site. For protection against single server failures, you can use XenServer High Availability to have VMs restarted on an alternate server in the same pool.
Understanding XenServer DR XenServer DR works by storing all the information needed to recover your business-critical VMs and vApps on storage repositories (SRs) that are then replicated from your primary (production) environment to a backup environment.
You can back up a managed server to a XenServer backup file (.xbk) that can then be used to restore the server in case of hardware failure. Note that this will back up just the server itself, but not any VMs that might be running on it.
We recommend that you back up your servers frequently to enable you to recover from possible server and/or software failure. When backing up servers in XenCenter, note the following points:
You enable HA for a resource pool using the Configure HA wizard. The wizard takes you through the HA configuration process, step-by-step, calculating the server failure limit for the pool given the available resources and the HA restart priorities you specify.
To open the Configure HA wizard: in XenCenter, select the pool, click on the HA tab, and then click Configure HA.
Alternatively:
On the Pool menu, click High Availability. Right-click in the Resources pane and then click High Availability on the shortcut menu.
